[Touch-packages] [Bug 1844879] Re: Behaviour change in systemd 243 breaks libvirt autopkgtest

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 243-2ubuntu1

---
systemd (243-2ubuntu1) focal; urgency=medium

  * Merge to Ubuntu from experimental
  * Refresh patches:
- Dropped changes:
  * Cherrypick ask-password: prevent buffer overrow when reading from 
keyring.
File: 
debian/patches/ask-password-prevent-buffer-overrow-when-reading-fro.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=6d6e9cbd4fc6e018031a4762e88f2c3aa19e24e8
  * random-util: eat up bad RDRAND values seen on AMD CPUs.
File: debian/patches/+rdrand-workaround-on-amd.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?h=ubuntu-eoan=6ab88231efca4b04b26de6cfb5d671be154aabe0
- Remaining changes:
  * Recommend networkd-dispatcher
File: debian/control

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d1e3b2c7e4757119da0d550b0b3c0a6626a176dc
  * Enable EFI/bootctl on armhf.
File: debian/control

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=043122f7d8a1487bfd357e815a6ece1ceea6e7d1
  * debian/control: strengthen dependencies.
File: debian/control

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d1ecf0c372f5212129c85ae60fddf26b2271a1fe
  * Add conflicts with upstart and systemd-shim
File: debian/control

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=83ed7496afc7c27be026014d109855f7d0ad1176
  * Specify Ubuntu's Vcs-Git
File: debian/control

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=fd832930ef280c9a4a9dda2440d5a46a6fdb6232
  * Ubuntu/extra: ship dhclient-enter hook.
Files:
- debian/extra/dhclient-enter-resolved-hook
- debian/rules

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=f3398a213f80b02bf3db0c1ce9e22d69f6d56764

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=258893bae8cbb12670e4807636fe8f7e9fb5407a

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=0725c1169ddde4f41cacba7af3e546704e2206be
  * udev-udeb: ship modprobe.d snippet to force scsi_mod.scan=sync in d-i.
Files:
- debian/extra/modprobe.d-udeb/scsi-mod-scan-sync.conf
- debian/udev-udeb.install

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=eb6d8a2b9504917abb7aa2c4035fdbb7b98227f7
  * debian/extra/start-udev: Set scsi_mod scan=sync even if it's builtin to 
the kernel (we previously only set it in modprobe.d)
Files:
- debian/extra/start-udev

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=6b72628f8de991e2c67ac4289fc74daf3abe7d14
  * debian/extra/units/systemd-resolved.service.d/resolvconf.conf:
drop resolvconf.conf drop-in, resolved integration moved to resolvconf 
package.
  * debian/extra/wrap_cl.py: add changelog formatter
Files:
- debian/extra/wrap_cl.py
- debian/gbp.conf

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=26e69bceab9cec8df64cdca18cd71e7c0874f8b3
  * debian/gbp.conf: Set tag format to ubuntu/*
  * debian/gbp.conf: Change debian-branch to ubuntu-eoan
  * libnss-resolve: do not disable and stop systemd-resolved
File: debian/libnss-resolve.postrm

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=95577d14e84e19b614b83b2e24985d89e8c2dac0
  * core: Revert strict mount namespacing/sandboxing, until LXD allows the 
needed mounts.
File: 
debian/patches/Revert-namespace-be-more-careful-when-handling-namespacin.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=030919ba5e4931d6ee576d0259fae67fe4ed9770
  * Add "AssumedApparmorLabel=unconfined" to timedate1 dbus service file
File: 
debian/patches/debian/UBUNTU-Add-AssumedApparmorLabel-unconfined-to-timedate1-dbus.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=5ad0879e10bbe3d641f940260b93c7eb2cf4624c
  * Re-add support for /etc/writable for core18
File: 
debian/patches/debian/UBUNTU-Support-system-image-read-only-etc.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a5b5fca66c1127068e4ce0cc9ab497814211f4f7
  * Improve autopkgtest success rate, by bumping up timeouts
File: debian/patches/debian/UBUNTU-bump-selftest-timeouts.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c05586d9da033bbfd6b6a74e10b87520843c7c48
  * core: set /run size to 10%, like initramfs-tools does.
File: 

[Touch-packages] [Bug 1845314] Re: udisks2 fails to install in a container with systemd 243

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 243-2ubuntu1

---
systemd (243-2ubuntu1) focal; urgency=medium

  * Merge to Ubuntu from experimental
  * Refresh patches:
- Dropped changes:
  * Cherrypick ask-password: prevent buffer overrow when reading from 
keyring.
File: 
debian/patches/ask-password-prevent-buffer-overrow-when-reading-fro.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=6d6e9cbd4fc6e018031a4762e88f2c3aa19e24e8
  * random-util: eat up bad RDRAND values seen on AMD CPUs.
File: debian/patches/+rdrand-workaround-on-amd.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?h=ubuntu-eoan=6ab88231efca4b04b26de6cfb5d671be154aabe0
- Remaining changes:
  * Recommend networkd-dispatcher
File: debian/control

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d1e3b2c7e4757119da0d550b0b3c0a6626a176dc
  * Enable EFI/bootctl on armhf.
File: debian/control

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=043122f7d8a1487bfd357e815a6ece1ceea6e7d1
  * debian/control: strengthen dependencies.
File: debian/control

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d1ecf0c372f5212129c85ae60fddf26b2271a1fe
  * Add conflicts with upstart and systemd-shim
File: debian/control

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=83ed7496afc7c27be026014d109855f7d0ad1176
  * Specify Ubuntu's Vcs-Git
File: debian/control

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=fd832930ef280c9a4a9dda2440d5a46a6fdb6232
  * Ubuntu/extra: ship dhclient-enter hook.
Files:
- debian/extra/dhclient-enter-resolved-hook
- debian/rules

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=f3398a213f80b02bf3db0c1ce9e22d69f6d56764

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=258893bae8cbb12670e4807636fe8f7e9fb5407a

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=0725c1169ddde4f41cacba7af3e546704e2206be
  * udev-udeb: ship modprobe.d snippet to force scsi_mod.scan=sync in d-i.
Files:
- debian/extra/modprobe.d-udeb/scsi-mod-scan-sync.conf
- debian/udev-udeb.install

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=eb6d8a2b9504917abb7aa2c4035fdbb7b98227f7
  * debian/extra/start-udev: Set scsi_mod scan=sync even if it's builtin to 
the kernel (we previously only set it in modprobe.d)
Files:
- debian/extra/start-udev

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=6b72628f8de991e2c67ac4289fc74daf3abe7d14
  * debian/extra/units/systemd-resolved.service.d/resolvconf.conf:
drop resolvconf.conf drop-in, resolved integration moved to resolvconf 
package.
  * debian/extra/wrap_cl.py: add changelog formatter
Files:
- debian/extra/wrap_cl.py
- debian/gbp.conf

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=26e69bceab9cec8df64cdca18cd71e7c0874f8b3
  * debian/gbp.conf: Set tag format to ubuntu/*
  * debian/gbp.conf: Change debian-branch to ubuntu-eoan
  * libnss-resolve: do not disable and stop systemd-resolved
File: debian/libnss-resolve.postrm

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=95577d14e84e19b614b83b2e24985d89e8c2dac0
  * core: Revert strict mount namespacing/sandboxing, until LXD allows the 
needed mounts.
File: 
debian/patches/Revert-namespace-be-more-careful-when-handling-namespacin.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=030919ba5e4931d6ee576d0259fae67fe4ed9770
  * Add "AssumedApparmorLabel=unconfined" to timedate1 dbus service file
File: 
debian/patches/debian/UBUNTU-Add-AssumedApparmorLabel-unconfined-to-timedate1-dbus.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=5ad0879e10bbe3d641f940260b93c7eb2cf4624c
  * Re-add support for /etc/writable for core18
File: 
debian/patches/debian/UBUNTU-Support-system-image-read-only-etc.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a5b5fca66c1127068e4ce0cc9ab497814211f4f7
  * Improve autopkgtest success rate, by bumping up timeouts
File: debian/patches/debian/UBUNTU-bump-selftest-timeouts.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c05586d9da033bbfd6b6a74e10b87520843c7c48
  * core: set /run size to 10%, like initramfs-tools does.
File: 

[Touch-packages] [Bug 1849158] Re: Include the systemd package version in journal output

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 243-2ubuntu1

---
systemd (243-2ubuntu1) focal; urgency=medium

  * Merge to Ubuntu from experimental
  * Refresh patches:
- Dropped changes:
  * Cherrypick ask-password: prevent buffer overrow when reading from 
keyring.
File: 
debian/patches/ask-password-prevent-buffer-overrow-when-reading-fro.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=6d6e9cbd4fc6e018031a4762e88f2c3aa19e24e8
  * random-util: eat up bad RDRAND values seen on AMD CPUs.
File: debian/patches/+rdrand-workaround-on-amd.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?h=ubuntu-eoan=6ab88231efca4b04b26de6cfb5d671be154aabe0
- Remaining changes:
  * Recommend networkd-dispatcher
File: debian/control

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d1e3b2c7e4757119da0d550b0b3c0a6626a176dc
  * Enable EFI/bootctl on armhf.
File: debian/control

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=043122f7d8a1487bfd357e815a6ece1ceea6e7d1
  * debian/control: strengthen dependencies.
File: debian/control

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d1ecf0c372f5212129c85ae60fddf26b2271a1fe
  * Add conflicts with upstart and systemd-shim
File: debian/control

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=83ed7496afc7c27be026014d109855f7d0ad1176
  * Specify Ubuntu's Vcs-Git
File: debian/control

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=fd832930ef280c9a4a9dda2440d5a46a6fdb6232
  * Ubuntu/extra: ship dhclient-enter hook.
Files:
- debian/extra/dhclient-enter-resolved-hook
- debian/rules

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=f3398a213f80b02bf3db0c1ce9e22d69f6d56764

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=258893bae8cbb12670e4807636fe8f7e9fb5407a

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=0725c1169ddde4f41cacba7af3e546704e2206be
  * udev-udeb: ship modprobe.d snippet to force scsi_mod.scan=sync in d-i.
Files:
- debian/extra/modprobe.d-udeb/scsi-mod-scan-sync.conf
- debian/udev-udeb.install

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=eb6d8a2b9504917abb7aa2c4035fdbb7b98227f7
  * debian/extra/start-udev: Set scsi_mod scan=sync even if it's builtin to 
the kernel (we previously only set it in modprobe.d)
Files:
- debian/extra/start-udev

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=6b72628f8de991e2c67ac4289fc74daf3abe7d14
  * debian/extra/units/systemd-resolved.service.d/resolvconf.conf:
drop resolvconf.conf drop-in, resolved integration moved to resolvconf 
package.
  * debian/extra/wrap_cl.py: add changelog formatter
Files:
- debian/extra/wrap_cl.py
- debian/gbp.conf

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=26e69bceab9cec8df64cdca18cd71e7c0874f8b3
  * debian/gbp.conf: Set tag format to ubuntu/*
  * debian/gbp.conf: Change debian-branch to ubuntu-eoan
  * libnss-resolve: do not disable and stop systemd-resolved
File: debian/libnss-resolve.postrm

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=95577d14e84e19b614b83b2e24985d89e8c2dac0
  * core: Revert strict mount namespacing/sandboxing, until LXD allows the 
needed mounts.
File: 
debian/patches/Revert-namespace-be-more-careful-when-handling-namespacin.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=030919ba5e4931d6ee576d0259fae67fe4ed9770
  * Add "AssumedApparmorLabel=unconfined" to timedate1 dbus service file
File: 
debian/patches/debian/UBUNTU-Add-AssumedApparmorLabel-unconfined-to-timedate1-dbus.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=5ad0879e10bbe3d641f940260b93c7eb2cf4624c
  * Re-add support for /etc/writable for core18
File: 
debian/patches/debian/UBUNTU-Support-system-image-read-only-etc.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a5b5fca66c1127068e4ce0cc9ab497814211f4f7
  * Improve autopkgtest success rate, by bumping up timeouts
File: debian/patches/debian/UBUNTU-bump-selftest-timeouts.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c05586d9da033bbfd6b6a74e10b87520843c7c48
  * core: set /run size to 10%, like initramfs-tools does.
File: 

[Touch-packages] [Bug 1830865] Re: Integer overflow in bson_ensure_space (bson.c:613)

[Alex Murray]

** Information type changed from Private Security to Public Security

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

Title:
  Integer overflow in bson_ensure_space (bson.c:613)

Status in whoopsie package in Ubuntu:
  Fix Released

Bug description:
  Dear Ubuntu Security Team,

  I would like to report an integer overflow vulnerability in whoopsie.
  In combination with issue 1830858, this vulnerability may enable an
  local attacker to read arbitrary files on the system.

  I have attached a proof-of-concept which triggers the vulnerability. I
  have tested it on an up-to-date Ubuntu 18.04. Run it as follows:

  bunzip2 PoC.tar.bz2
  tar -xf PoC.tar
  cd PoC
  make
  ./killwhoopsie2

  The PoC works by creating a file named
  `/var/crash/killwhoopsie.crash`, just over 2GB in size. It then
  creates a file named `/var/crash/killwhoopsie.upload`, which prompts
  whoopsie to start processing the .crash file.

  This is the source location of the integer overflow bug:

  http://bazaar.launchpad.net/~daisy-
  pluckers/whoopsie/trunk/view/698/lib/bson/bson.c#L613

  The problem is that the types of pos, bytesNeeded, and b->dataSize are
  all int. My PoC triggers an integer overflow in the calculation of pos
  + bytesNeeded, which causes bson_ensure_space to return immediately on
  line 614 without allocating more space. This leads subsequently to a
  heap buffer overflow on line 738:

  http://bazaar.launchpad.net/~daisy-
  pluckers/whoopsie/trunk/view/698/lib/bson/bson.c#L738

  Please let me know when you have fixed the vulnerability, so that I
  can coordinate my disclosure with yours. For reference, here is a link
  to Semmle's vulnerability disclosure policy:
  https://lgtm.com/security#disclosure_policy

  Thank you,

  Kevin Backhouse

  Semmle Security Research Team

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1830865/+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 1845046] Re: Bluetooth headphones/speaker default to low quality headset mode and fails to switch to A2DP when selected

[Rob Frohne]

I spent 45 minutes playing with this problem this morning.  I restarted
my computer this morning, but nothing helped.  Now, after work, where
the computer was in suspended, but not restarted, and used periodically,
and it works just fine.  I did connect another headset to see if it was
a Sony problem, and now both headsets work as expected.  I do know that
A2DP is deactivated if you select the microphone on the headset, but
this morning I switched that back and forth several times with no
effect.  Fortunately, or unfortunately as it may be, I cannot now
duplicate the results I had this morning, and I can't figure out why.
It may have happened when I connected the headset to bluetooth again to
test this evening.  I cannot remember if I disconnected the headset and
reconnected it this morning.

Rob

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

Title:
  Bluetooth headphones/speaker default to low quality headset mode and
  fails to switch to A2DP when selected

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Whenever I turn on my headphones theyll connect to my computer but im
  able to hear the input audio from my microphone and low quality output
  audio. I have to disconnect the headphones in the bluetooth devices
  and reconnect for it to fix the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  litleck1398 F pulseaudio
   /dev/snd/controlC0:  litleck1398 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 23 17:07:59 2019
  InstallationDate: Installed on 2019-09-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: WH-1000XM3
  Symptom_Type: High background noise, or volume is too low
  Title: [WH-1000XM3, playback] Background noise or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2019
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.0.19
  dmi.board.name: 01NYPT
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.0.19:bd02/12/2019:svnAlienware:pnAlienwareAuroraR5:pvr1.0.19:rvnAlienware:rn01NYPT:rvrA00:cvnAlienware:ct3:cvrNotSpecified:
  dmi.product.family: Alienware
  dmi.product.name: Alienware Aurora R5
  dmi.product.sku: 0729
  dmi.product.version: 1.0.19
  dmi.sys.vendor: Alienware

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1845046/+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 1838525] Re: LVM setup fails to install grub on virtio storage

[vmware-gos-Yuhua]

Verified: this issue is fixed in GA iso

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

Title:
  LVM setup fails to install grub on virtio storage

Status in debian-installer package in Ubuntu:
  Invalid
Status in grub2 package in Ubuntu:
  Fix Released
Status in lvm2 package in Ubuntu:
  Invalid
Status in debian-installer package in Debian:
  New

Bug description:
  [Impact]

   * Any Eoan installation that depends on latest installer will face
  this issue when final user chooses LVM full disk partitioning type.

   * Grub won't be able to install due to bad bootdevice variable in the
  installer. It will try to install grub to "/dev/mapper" and will fail.
  The default boot option will also be "/dev/mapper".

  [Test Case]

   * Download netboot files from current installer (vmlinuz and initrd
  files).

   * Create a KVM guest running from these files, with a NIC connected
  to the internet.

   * Initiate a network installation inside the KVM guest, choosing the
  Entire Disk - LVM partitioning option.

   * Wait installation to finish and to start the grub-install phase. It
  will ask where to install grub, having, as default, "/dev/mapper". By
  default, it might simply try to grub-install /dev/mapper, which will
  also fail.

   * That happens because /dev/disk/by-id/ has an unexpected (by the
  installer) symlink added by lvm2 package that grub-installer (used by
  debian-installer) does not expect (when using grub-mkdevice command).

  [Simplified Test Case]

   * To add a PV + VG + LVM in a KVM guest to an empty virtio disk, for
  example, and to check if the command:

  grub-mkdevicemap --no-floppy -m -

  lists /dev/vdX1 in front of /dev/vdX. This will be a sign that:

  /dev/disk/by-id/*lvm* file exists and will be enough to confuse
  installer.

  [Regression Potential]

  There are 3 alternatives to fix this and I have chosen the one I
  believe has the smaller potential for any type of regression. Comment
  #30 describes what caused the regression and these 3 alternatives:

  (1) To revert this change for current release, since this rule was
  added to "make navigation a bit easier using PV UUIDs", as the commit
  says. We would worry about installer changes in the next release.

  (2) Another possibility would be to change the logic inside "grub-
  mkdevicemap.c: make_device_map()->grub_util_iterate_devices()" to
  ignore all symlinks from /dev/disk/by-id/ containing lvm-pv-uuid-*. We
  would not have to worry about this in the next release if using
  debian-installer.

  (3) Another option would be to change grub-installer package/logic.
  Unfortunately, a few days before the full freeze, I don't think
  messing with the installer would be a good option to avoid regressions
  (potential regression item would grow in significance).

  => I'm choosing (2) because ubuntu foundations already faced a similar
  situation, when grub-mkdevicemap.c file was removed from grub2 code
  and they re-added it by using a quilt patch, assuming it was the
  easiest and better to maintain. I'm doing something similar, patching
  the patch that creates grub-mkdevicemap.c file again to ignore
  /dev/disk/by-id/lvm-pv-uuid-* files (like it already does for other
  symlinks, actually).

  [Other Info]

  Comment #26 has the TL;DR version of the problem.
  
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1838525/comments/26

  [Original Description]

  The Eoan debian-installer ISO fails to install GRUB on LVM installs
  with virtio storage, as it runs grub-install with /dev/mapper as a
  target (a directory), even if instructed to target a device.

  The following steps to reproduce have been prepared running the
  20190730 build, but this has been broken since about June 18, 2019.
  Steps to reproduce:

  $ md5sum eoan-server-amd64.iso
  f591e30485e5f0b5117f6c116e538c42  eoan-server-amd64.iso
  $ qemu-img create -f raw disk1.img 8G
  Formatting 'disk1.img', fmt=raw size=8589934592
  $ kvm -m 1024 -boot d -cdrom eoan-server-amd64.iso -drive 
file=disk1.img,if=virtio

  Proceed with all the defaults. In the "Partition disk" step select
  "Guided - use entire disk and set up LVM". Go ahead accepting the
  defaults. At the "Install the GRUB boot loader" step select "/dev/vda"
  as the target device. The installer will actually run `grub-install
  --force /dev/mapper` and fail after a while. The wrong command is
  visible both in the d-i screen and by running `ps` on a different
  console.

  Full installer syslog: http://paste.ubuntu.com/p/qtZy86dTp6/

  It's interesting how this doesn't happen when not using virtio. If
  from the commands above the "if=virtio" option is dropped then
  everything works as expected. In this case the target block device is
  called /dev/sda instead of /dev/vda.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1850444] Re: Selecting A2DP profile but only get mono

[Daniel van Vugt]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1845046, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** Summary changed:

- Cannot connect headset to A2DP anymore
+ Selecting A2DP profile but only get mono

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

** This bug has been marked a duplicate of bug 1845046
   Bluetooth headphones/speaker default to low quality headset mode and fails 
to switch to A2DP when selected

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

Title:
  Selecting A2DP profile but only get mono

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

Bug description:
  As of October 29, I can no longer connect to my Sony MDR-1000x headphones 
using A2DP.  The gnome sound manager has the setting, but when I select it and 
use the test button, it is only mono.  I tried the gnome extension 
https://extensions.gnome.org/extension/906/sound-output-device-chooser/ and the 
option is always grayed out there. I tried to make A2DP the default using the 
method described here: 
https://medium.com/@overcode/fixing-bluetooth-in-ubuntu-pop-os-18-04-d4b8dbf7ddd6
  I tried to install some tools to try and get a better idea what might be 
going on.  In case it was a recent update, here are the last few days of my 
update log:
  Start-Date: 2019-10-21  08:19:53
  Commandline: aptdaemon role='role-commit-packages' sender=':1.375055'
  Install: linux-image-5.3.0-19-generic:amd64 (5.3.0-19.20, automatic), 
linux-modules-extra-5.3.0-19-generic:amd64 (5.3.0-19.20, automatic), 
linux-headers-5.3.0-19-generic:amd64 (5.3.0-19.20, automatic), 
linux-modules-5.3.0-19-generic:amd64 (5.3.0-19.20, automatic), 
linux-headers-5.3.0-19:amd64 (5.3.0-19.20, automatic)
  Upgrade: linux-headers-generic:amd64 (5.3.0.18.21, 5.3.0.19.22), 
linux-libc-dev:amd64 (5.3.0-18.19, 5.3.0-19.20), linux-image-generic:amd64 
(5.3.0.18.21, 5.3.0.19.22), linux-signed-generic:amd64 (5.3.0.18.21, 
5.3.0.19.22), linux-generic:amd64 (5.3.0.18.21, 5.3.0.19.22)
  End-Date: 2019-10-21  08:21:37

  Start-Date: 2019-10-21  11:42:11
  Commandline: aptdaemon role='role-commit-packages' sender=':1.1749'
  Upgrade: libaspell15:amd64 (0.60.7-3, 0.60.7-3ubuntu0.1), aspell:amd64 
(0.60.7-3, 0.60.7-3ubuntu0.1), libexiv2-14:amd64 (0.25-4ubuntu2, 
0.25-4ubuntu2.1)
  Remove: linux-modules-extra-5.0.0-32-generic:amd64 (5.0.0-32.34), 
linux-modules-5.0.0-32-generic:amd64 (5.0.0-32.34), 
linux-image-5.0.0-32-generic:amd64 (5.0.0-32.34)
  End-Date: 2019-10-21  11:42:26

  Start-Date: 2019-10-22  06:19:40
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: libopenjp2-7:amd64 (2.3.0-2, 2.3.0-2build0.19.10.1)
  End-Date: 2019-10-22  06:19:41

  Start-Date: 2019-10-22  19:12:43
  Commandline: aptdaemon role='role-commit-packages' sender=':1.375112'
  Upgrade: google-chrome-stable:amd64 (77.0.3865.120-1, 78.0.3904.70-1), 
xsltproc:amd64 (1.1.33-0ubuntu1, 1.1.33-0ubuntu1.1), libxslt1.1:amd64 
(1.1.33-0ubuntu1, 1.1.33-0ubuntu1.1), libxslt1.1:i386 (1.1.33-0ubuntu1, 
1.1.33-0ubuntu1.1)
  End-Date: 2019-10-22  19:12:59

  Start-Date: 2019-10-24  07:00:54
  Commandline: aptdaemon role='role-commit-packages' sender=':1.660642'
  Upgrade: firefox-locale-en:amd64 (69.0.3+build1-0ubuntu1, 
70.0+build2-0ubuntu0.19.10.1), firefox:amd64 (69.0.3+build1-0ubuntu1, 
70.0+build2-0ubuntu0.19.10.1), linux-firmware:amd64 (1.183, 1.183.1)
  End-Date: 2019-10-24  07:01:58

  Start-Date: 2019-10-29  06:33:22
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: libwbclient0:amd64 (2:4.10.7+dfsg-0ubuntu2, 
2:4.10.7+dfsg-0ubuntu2.2), samba-libs:amd64 (2:4.10.7+dfsg-0ubuntu2, 
2:4.10.7+dfsg-0ubuntu2.2), libsmbclient:amd64 (2:4.10.7+dfsg-0ubuntu2, 
2:4.10.7+dfsg-0ubuntu2.2)
  End-Date: 2019-10-29  06:33:25

  Start-Date: 2019-10-29  07:22:22
  Commandline: /usr/sbin/synaptic
  Requested-By: frohro (1000)
  Install: bluez-tests:amd64 (5.50-0ubuntu4), bluez-tools:amd64 
(2.0~20170911.0.7cb788c-2build1), bluetooth:amd64 (5.50-0ubuntu4)
  End-Date: 2019-10-29  07:22:28

  Start-Date: 2019-10-29  07:44:42
  Commandline: apt install pulseaudio pulseaudio-utils pavucontrol 
pulseaudio-module-bluetooth
  Requested-By: frohro (1000)
  Install: pavucontrol:amd64 (3.0-4)
  End-Date: 2019-10-29  07:44:48

  Nothing I tried solves the issue.  It was working a few days ago.

  Thanks,

  Rob

  ProblemType: Bug
  DistroRelease: 

[Touch-packages] [Bug 1850502] Re: Bluetooth disconnects intermittently on ubuntu 19.10 [RTL8822BE]

[Daniel van Vugt]

Thanks for the bug report. Your log suggests problems with wifi (wlp2s0)
around the same time as bluetooth. This isn't surprising since both may
be sharing radio frequencies (~2.4GHz) and the same chip in your laptop.

To avoid these problems please either:

  * Turn off wifi and use ethernet; or

  * Avoid using multiple Bluetooth devices at once; or

  * Use only 5GHz wifi networks, not 2.4GHz; or

  * Install a different type of wifi card in the laptop.


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

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

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

Title:
  Bluetooth disconnects intermittently on ubuntu 19.10 [RTL8822BE]

Status in linux package in Ubuntu:
  Invalid

Bug description:
  My Bluetooth speaker is disconnecting few minutes after playing
  youtube videos on google chrome  [no issues when playing videos in
  mpv], also I have noticed that ubuntu detecting my speaker as
  Bluetooth keyboard instead of speaker !!

  Please find the log below

  
  Oct 29 22:48:56 Asus-VivoBook wpa_supplicant[822]: wlp2s0: 
CTRL-EVENT-BEACON-LOSS 
  Oct 29 22:49:29 Asus-VivoBook wpa_supplicant[822]: message repeated 3 times: 
[ wlp2s0: CTRL-EVENT-BEACON-LOSS ]
  Oct 29 22:49:37 Asus-VivoBook acpid: input device has been disconnected, fd 18
  Oct 29 22:49:37 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (II) 
config/udev: removing device AA:AA:AA:AA:AA:AA
  Oct 29 22:49:37 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (**) Option 
"fd" "68"
  Oct 29 22:49:37 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (II) event15 
- AA:AA:AA:AA:AA:AA: device removed
  Oct 29 22:49:37 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (II) 
UnloadModule: "libinput"
  Oct 29 22:49:37 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (II) 
systemd-logind: releasing fd for 13:79
  Oct 29 22:49:37 Asus-VivoBook bluetoothd[819]: Unable to get io data for 
Headset Voice gateway: getpeername: Transport endpoint is not connected (107)
  Oct 29 22:49:37 Asus-VivoBook gsd-media-keys[1956]: Unable to get default sink
  Oct 29 22:49:46 Asus-VivoBook kernel: [ 2399.077733] input: AA:AA:AA:AA:AA:AA 
as /devices/virtual/input/input19
  Oct 29 22:49:46 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (II) 
config/udev: Adding input device AA:AA:AA:AA:AA:AA (/dev/input/event15)
  Oct 29 22:49:46 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (**) 
AA:AA:AA:AA:AA:AA: Applying InputClass "libinput keyboard catchall"
  Oct 29 22:49:46 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (II) Using 
input driver 'libinput' for 'AA:AA:AA:AA:AA:AA'
  Oct 29 22:49:46 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (II) 
systemd-logind: got fd for /dev/input/event15 13:79 fd 69 paused 0
  Oct 29 22:49:46 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (**) 
AA:AA:AA:AA:AA:AA: always reports core events
  Oct 29 22:49:46 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (**) Option 
"Device" "/dev/input/event15"
  Oct 29 22:49:46 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (**) Option 
"_source" "server/udev"
  Oct 29 22:49:46 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (II) event15 
- AA:AA:AA:AA:AA:AA: is tagged by udev as: Keyboard
  Oct 29 22:49:46 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (II) event15 
- AA:AA:AA:AA:AA:AA: device is a keyboard
  Oct 29 22:49:46 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (II) event15 
- AA:AA:AA:AA:AA:AA: device removed
  Oct 29 22:49:46 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (**) Option 
"config_info" "udev:/sys/devices/virtual/input/input19/event15"
  Oct 29 22:49:46 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (II) XINPUT: 
Adding extended input device "AA:AA:AA:AA:AA:AA" (type: KEYBOARD, id 14)
  Oct 29 22:49:46 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (**) Option 
"xkb_model" "pc105"
  Oct 29 22:49:46 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (**) Option 
"xkb_layout" "us"
  Oct 29 22:49:46 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (WW) Option 
"xkb_variant" requires a string value
  Oct 29 22:49:46 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (WW) Option 
"xkb_options" requires a string value
  Oct 29 22:49:46 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (II) event15 
- AA:AA:AA:AA:AA:AA: is tagged by udev as: Keyboard
  Oct 29 22:49:46 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (II) event15 
- AA:AA:AA:AA:AA:AA: device is a keyboard

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bluez 5.50-0ubuntu4
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 29 22:41:48 2019
  InstallationDate: Installed on 2019-10-22 (6 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release 

[Touch-packages] [Bug 1845046] Re: Bluetooth headphones/speaker default to low quality headset mode instead of high quality A2DP and can't be easily changed in Settings

[Daniel van Vugt]

I wonder if there's something special about Sony...

* This bug was reported against Sony WH-1000XM3
* A duplicate bug was reported against Sony MDR-1000x
* I also encountered the bug once using Sony SRS-XB2 speakers

** Summary changed:

- [WH-1000XM3, playback] Hearing input and output audio until disconnecting and 
reconnecting
+ Bluetooth headphones/speaker default to low quality headset mode instead of 
high quality A2DP and can't be easily changed in Settings

** Summary changed:

- Bluetooth headphones/speaker default to low quality headset mode instead of 
high quality A2DP and can't be easily changed in Settings
+ Bluetooth headphones/speaker default to low quality headset mode and fails to 
switch to A2DP when selected

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

Title:
  Bluetooth headphones/speaker default to low quality headset mode and
  fails to switch to A2DP when selected

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Whenever I turn on my headphones theyll connect to my computer but im
  able to hear the input audio from my microphone and low quality output
  audio. I have to disconnect the headphones in the bluetooth devices
  and reconnect for it to fix the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  litleck1398 F pulseaudio
   /dev/snd/controlC0:  litleck1398 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 23 17:07:59 2019
  InstallationDate: Installed on 2019-09-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: WH-1000XM3
  Symptom_Type: High background noise, or volume is too low
  Title: [WH-1000XM3, playback] Background noise or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2019
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.0.19
  dmi.board.name: 01NYPT
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.0.19:bd02/12/2019:svnAlienware:pnAlienwareAuroraR5:pvr1.0.19:rvnAlienware:rn01NYPT:rvrA00:cvnAlienware:ct3:cvrNotSpecified:
  dmi.product.family: Alienware
  dmi.product.name: Alienware Aurora R5
  dmi.product.sku: 0729
  dmi.product.version: 1.0.19
  dmi.sys.vendor: Alienware

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1845046/+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 1850444] Re: Cannot connect headset to A2DP anymore....

[Daniel van Vugt]

** Tags added: a2dp

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

Title:
  Cannot connect headset to A2DP anymore

Status in bluez package in Ubuntu:
  New

Bug description:
  As of October 29, I can no longer connect to my Sony MDR-1000x headphones 
using A2DP.  The gnome sound manager has the setting, but when I select it and 
use the test button, it is only mono.  I tried the gnome extension 
https://extensions.gnome.org/extension/906/sound-output-device-chooser/ and the 
option is always grayed out there. I tried to make A2DP the default using the 
method described here: 
https://medium.com/@overcode/fixing-bluetooth-in-ubuntu-pop-os-18-04-d4b8dbf7ddd6
  I tried to install some tools to try and get a better idea what might be 
going on.  In case it was a recent update, here are the last few days of my 
update log:
  Start-Date: 2019-10-21  08:19:53
  Commandline: aptdaemon role='role-commit-packages' sender=':1.375055'
  Install: linux-image-5.3.0-19-generic:amd64 (5.3.0-19.20, automatic), 
linux-modules-extra-5.3.0-19-generic:amd64 (5.3.0-19.20, automatic), 
linux-headers-5.3.0-19-generic:amd64 (5.3.0-19.20, automatic), 
linux-modules-5.3.0-19-generic:amd64 (5.3.0-19.20, automatic), 
linux-headers-5.3.0-19:amd64 (5.3.0-19.20, automatic)
  Upgrade: linux-headers-generic:amd64 (5.3.0.18.21, 5.3.0.19.22), 
linux-libc-dev:amd64 (5.3.0-18.19, 5.3.0-19.20), linux-image-generic:amd64 
(5.3.0.18.21, 5.3.0.19.22), linux-signed-generic:amd64 (5.3.0.18.21, 
5.3.0.19.22), linux-generic:amd64 (5.3.0.18.21, 5.3.0.19.22)
  End-Date: 2019-10-21  08:21:37

  Start-Date: 2019-10-21  11:42:11
  Commandline: aptdaemon role='role-commit-packages' sender=':1.1749'
  Upgrade: libaspell15:amd64 (0.60.7-3, 0.60.7-3ubuntu0.1), aspell:amd64 
(0.60.7-3, 0.60.7-3ubuntu0.1), libexiv2-14:amd64 (0.25-4ubuntu2, 
0.25-4ubuntu2.1)
  Remove: linux-modules-extra-5.0.0-32-generic:amd64 (5.0.0-32.34), 
linux-modules-5.0.0-32-generic:amd64 (5.0.0-32.34), 
linux-image-5.0.0-32-generic:amd64 (5.0.0-32.34)
  End-Date: 2019-10-21  11:42:26

  Start-Date: 2019-10-22  06:19:40
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: libopenjp2-7:amd64 (2.3.0-2, 2.3.0-2build0.19.10.1)
  End-Date: 2019-10-22  06:19:41

  Start-Date: 2019-10-22  19:12:43
  Commandline: aptdaemon role='role-commit-packages' sender=':1.375112'
  Upgrade: google-chrome-stable:amd64 (77.0.3865.120-1, 78.0.3904.70-1), 
xsltproc:amd64 (1.1.33-0ubuntu1, 1.1.33-0ubuntu1.1), libxslt1.1:amd64 
(1.1.33-0ubuntu1, 1.1.33-0ubuntu1.1), libxslt1.1:i386 (1.1.33-0ubuntu1, 
1.1.33-0ubuntu1.1)
  End-Date: 2019-10-22  19:12:59

  Start-Date: 2019-10-24  07:00:54
  Commandline: aptdaemon role='role-commit-packages' sender=':1.660642'
  Upgrade: firefox-locale-en:amd64 (69.0.3+build1-0ubuntu1, 
70.0+build2-0ubuntu0.19.10.1), firefox:amd64 (69.0.3+build1-0ubuntu1, 
70.0+build2-0ubuntu0.19.10.1), linux-firmware:amd64 (1.183, 1.183.1)
  End-Date: 2019-10-24  07:01:58

  Start-Date: 2019-10-29  06:33:22
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: libwbclient0:amd64 (2:4.10.7+dfsg-0ubuntu2, 
2:4.10.7+dfsg-0ubuntu2.2), samba-libs:amd64 (2:4.10.7+dfsg-0ubuntu2, 
2:4.10.7+dfsg-0ubuntu2.2), libsmbclient:amd64 (2:4.10.7+dfsg-0ubuntu2, 
2:4.10.7+dfsg-0ubuntu2.2)
  End-Date: 2019-10-29  06:33:25

  Start-Date: 2019-10-29  07:22:22
  Commandline: /usr/sbin/synaptic
  Requested-By: frohro (1000)
  Install: bluez-tests:amd64 (5.50-0ubuntu4), bluez-tools:amd64 
(2.0~20170911.0.7cb788c-2build1), bluetooth:amd64 (5.50-0ubuntu4)
  End-Date: 2019-10-29  07:22:28

  Start-Date: 2019-10-29  07:44:42
  Commandline: apt install pulseaudio pulseaudio-utils pavucontrol 
pulseaudio-module-bluetooth
  Requested-By: frohro (1000)
  Install: pavucontrol:amd64 (3.0-4)
  End-Date: 2019-10-29  07:44:48

  Nothing I tried solves the issue.  It was working a few days ago.

  Thanks,

  Rob

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bluez 5.50-0ubuntu4
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 29 07:52:45 2019
  InstallationDate: Installed on 2019-04-19 (193 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20FES0EX00
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro
  SourcePackage: bluez
  UpgradeStatus: Upgraded to eoan on 2019-10-18 (11 days ago)
  dmi.bios.date: 06/26/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1GET91W (1.70 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FES0EX00
  dmi.board.vendor: LENOVO
  

[Touch-packages] [Bug 1850432] Re: acrually i wanted the graphics driver for my intel 3000 graphics driver for 2nd gen core i3 processor

[Daniel van Vugt]

As Timo said, you already have the latest graphics driver installed for
Intel. It is called 'modeset'.

If there is a particular problem you are trying to fix then please
update this bug to describe that problem.

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

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

Title:
  acrually i wanted the graphics driver for my intel 3000 graphics
  driver for 2nd gen core i3 processor

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  acrually i wanted the graphics driver for my intel 3000 graphics
  driver for 2nd gen core i3 processor

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 29 20:09:47 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:0591]
  InstallationDate: Installed on 2019-10-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Dell Inc. Inspiron 3421
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=UUID=caaedd10-467d-46ef-9bc9-df58fb08f913 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0WF4PW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A13
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd12/14/2015:svnDellInc.:pnInspiron3421:pvrNotSpecified:rvnDellInc.:rn0WF4PW:rvrA13:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3421
  dmi.product.sku: Inspiron 3421
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1850432/+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 1849950] Re: Gnome Shell window shortcuts maximize, windowed and hide (Super + Up / Down / H) don't work if upgrading from Unity

[Daniel van Vugt]

Just clarifying for future-me and others that there is no "fix" to look
for.

** Changed in: gsettings-desktop-schemas (Ubuntu)
   Status: Fix Released => Won't Fix

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

Title:
  Gnome Shell window shortcuts maximize, windowed and hide (Super + Up /
  Down / H) don't work if upgrading from Unity

Status in GNOME Shell:
  Fix Released
Status in gsettings-desktop-schemas package in Ubuntu:
  Won't Fix

Bug description:
  Happens on Ubuntu 19.10, and did also not work on Ubuntu 19.04 (and
  probably also previous versions), if I recall correctly.

  I am not sure, whether this is an upstream bug of GNOME or just Ubuntu
  related.

  Bug report for GNOME: https://gitlab.gnome.org/GNOME/gnome-
  shell/issues/1829

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1849950/+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 1849856] Re: ip commands error with mellanox devices in switchdev mode

[Terry Rudd]

Is there further work to do on this given the apparent resolution of the
problem?

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

Title:
  ip commands error with mellanox devices in switchdev mode

Status in iproute2 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Kernel: using 5.0.0-23-generic from hwe-edge

  Configuring a mellanox connectx device with configured VF's into
  switchdev (rather than legacy) mode result in the ip cli tool erroring
  when trying to query the interface state:

  $ sudo ip link
  Error: Buffer too small for object.
  Dump terminated

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: iproute2 4.15.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  Date: Fri Oct 25 14:55:36 2019
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: iproute2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1849856/+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 1834566] Re: Samsung Notebook 9 Pro - Internal Speaker Playback problem - HDA Intel - Realtek ALC298

[Filipe Garrett]

Here to also report that this issue persists on a newer Samsung laptop.
The model in question is the Notebook 7 Force NP760XBE(Style S51 Pro on
some countries) running 19.10. In my case, the speakers work fine,
though. The problem only manifests itself through headphones: very faint
and distorted sound.

I've reported it everywhere support-wise and posted it as a question here, on 
Launchpad:
https://answers.launchpad.net/ubuntu/+question/685478

My alsa-info output file could be found here: http://alsa-
project.org/db/?f=f7aa21f8fde284a2b2eb1d08524b6eb67d45bdfb

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

Title:
  Samsung Notebook 9 Pro - Internal Speaker Playback problem - HDA Intel
  - Realtek ALC298

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Unable to get system speakers working running 19.04.  At max volume,
  sound is barely perceptible through headphones.  Pavucontrol shows
  sounds is present, but no amount of adjustments makes a difference.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  robert 3355 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jun 28 00:44:13 2019
  InstallationDate: Installed on 2019-06-05 (22 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: None of the above
  Title: [930MBE, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02AHK.029.190425.PS
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP930MBE-K04US
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9872A0S-C01-G001-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02AHK.029.190425.PS:bd04/25/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn930MBE:pvrP02AHK:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP930MBE-K04US:rvrSGL9872A0S-C01-G001-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A:
  dmi.product.family: Notebook 9 Series
  dmi.product.name: 930MBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PAHK
  dmi.product.version: P02AHK
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834566/+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 1726129] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path

[El jinete sin cabeza]

** Tags added: 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/1726129

Title:
  nautilus crashed with SIGSEGV in widget_needs_widget_path

Status in Nautilus:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  https://gitlab.gnome.org/GNOME/nautilus/issues/1190

  ---

  https://errors.ubuntu.com/problem/7c06cf06fd970ce31033f0d775b3adf97559e4ea

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Budgie:GNOME
  Date: Sun Oct 22 15:30:05 2017
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2017-10-19 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  ProcCmdline: nautilus --new-window
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fe0115bd2a4:mov0x380(%rax),%rax
   PC (0x7fe0115bd2a4) ok
   source "0x380(%rax)" (0x0380) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: nautilus crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1726129/+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 1751667] Re: classic snap does not run on live session

[Zygmunt Krynicki]

Based on the discussion in this bug report I'm marking this as fix
released.

** Changed in: snapd (Ubuntu)
   Status: In Progress => Fix Released

** Also affects: snapd
   Importance: Undecided
   Status: New

** Changed in: snapd
   Status: New => Fix Released

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

Title:
  classic snap does not run on live session

Status in snapd:
  Fix Released
Status in apparmor package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  Fix Released

Bug description:
  I'm testing Ubuntu Budgie's classic snap called "ubuntu-budgie-
  welcome" which is available in the beta channel.

  Ubuntu Budgie 18.04 daily ISO 25/02/2018

  The snap works just fine on a normal install.  However this classic
  snap fails on the Ubuntu Budgie live session. As snaps become more
  prevalent - snaps - including classic snaps should work on live
  sessions.

  For Ubuntu Budgie, the classic snap is very important because it
  presents the user vital info about the distro and instructions on how
  to install.

  Copying the .desktop launcher from the menu I see the following issue
  in a terminal:

  ubuntu-budgie@ubuntu-budgie:~$ env 
BAMF_DESKTOP_FILE_HINT=/var/lib/snapd/desktop/applications/ubuntu-budgie-welcome_budgie-welcome.desktop
 /snap/bin/ubuntu-budgie-welcome.budgie-welcome %U
  snap-confine has elevated permissions and is not confined but should be. 
Refusing to continue to avoid permission escalation attacks

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: snapd 2.31.1+18.04
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  CurrentDesktop: Budgie:GNOME
  Date: Sun Feb 25 23:28:38 2018
  LiveMediaBuild: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180225)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1751667/+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 1822218] Re: clear crashed with SIGSEGV in __libc_start_main()

[Zygmunt Krynicki]

** Changed in: snapd (Ubuntu)
 Assignee: Zygmunt Krynicki (zyga) => (unassigned)

** Changed in: snapd (Ubuntu)
   Status: In Progress => Confirmed

** Also affects: snapd
   Importance: Undecided
   Status: New

** Changed in: snapd
   Status: New => Confirmed

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

Title:
  clear crashed with SIGSEGV in __libc_start_main()

Status in snapd:
  Confirmed
Status in ncurses package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  I got this error after installing Anaconda 3.7 from their repo.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: ncurses-bin 6.1+20181013-2ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 28 20:59:47 2019
  ExecutablePath: /usr/bin/clear
  InstallationDate: Installed on 2019-03-28 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190325)
  LocalLibraries: /snap/core/6673/lib/x86_64-linux-gnu/libc-2.23.so
  ProcCmdline: clear
  SegvAnalysis:
   Segfault happened at: 0x7f30b32e98df <__libc_start_main+415>:mov
0x18(%r13),%rax
   PC (0x7f30b32e98df) ok
   source "0x18(%r13)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: ncurses
  Stacktrace:
   #0  0x7f30b32e98df in __libc_start_main () from 
/snap/core/current/lib/x86_64-linux-gnu/libc.so.6
   No symbol table info available.
   #1  0x560c895582aa in ?? ()
   No symbol table info available.
  StacktraceTop:
   __libc_start_main () from /snap/core/current/lib/x86_64-linux-gnu/libc.so.6
   ?? ()
  Title: clear crashed with SIGSEGV in __libc_start_main()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1822218/+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 1850009] Re: Issue with detecting new state in dhclient-enter-hooks.d/resolved

[Ivan Brawley]

This bug is also being handled in #1805183. Comment #9 has a much better
patch (along the same lines as mine but also captures STDERR from
md5sum). Though it doesn't have Eoan included in the list of affected
versions.

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

Title:
  Issue with detecting new state in dhclient-enter-hooks.d/resolved

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 19.10 I noticed that resolving hostnames stopped
  working.

  Quick release, which package and version info:

  root@caret:~# lsb_release -r
  Release:19.10
  root@caret:~# dpkg -S /etc/dhcp/dhclient-enter-hooks.d/resolved
  systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved
  root@caret:~# apt-cache policy systemd
  systemd:
Installed: 242-7ubuntu3
Candidate: 242-7ubuntu3
Version table:
   *** 242-7ubuntu3 500
  500 http://au.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  
  The file /etc/resolv.conf was pointing to the local instance of 
systemd-resolved however there was no search line, indicating something wasn't 
quite right.

  Restarting the systemd-resolved service did recreate /etc/resolv.conf
  with expected search line.

  After much debugging, I've worked out what was going wrong.

  The dhcp hook file /etc/dhcp/dhclient-enter-hooks.d/resolved has a bug
  in the resolver state change logic.

  This may also impact on tickets 1805183, 1832050, 1832053 and maybe
  others.

  When doing the md5sum of the old and new state, the command is wrong.
  It isn't sending STDOUT (and optionally STDERR) to the temp file but
  rather putting the md5sum command into the background and then
  creating an empty file for both states. Which obviously isn't
  different, so systemd-resolved doesn't restart.

  Quick diff of a working version (I'm not capturing STDERR but one can
  with "2>&1")

  === BEGIN PATCH ===
  *** .brk-resolved-20191027  2019-10-27 11:19:56.210069032 +1030
  --- resolved2019-10-27 11:30:17.156381734 +1030
  ***
  *** 30,36 
  mkdir -p $statedir

  oldstate="$(mktemp)"
  !   md5sum $statedir/isc-dhcp-v4-$interface.conf 
$statedir/isc-dhcp-v6-$interface.conf &> $oldstate
  if [ -n "$new_domain_name_servers" ] ; then
  cat <$statedir/isc-dhcp-v4-$interface.conf
[Resolve]
  --- 30,36 
  mkdir -p $statedir

  oldstate="$(mktemp)"
  !   md5sum $statedir/isc-dhcp-v4-$interface.conf 
$statedir/isc-dhcp-v6-$interface.conf > $oldstate
  if [ -n "$new_domain_name_servers" ] ; then
  cat <$statedir/isc-dhcp-v4-$interface.conf
[Resolve]
  ***
  *** 55,61 
  fi

  newstate="$(mktemp)"
  !   md5sum $statedir/isc-dhcp-v4-$interface.conf 
$statedir/isc-dhcp-v6-$interface.conf &> $newstate
  if ! cmp $oldstate $newstate; then
  systemctl try-reload-or-restart systemd-resolved.service
  fi
  --- 55,61 
  fi

  newstate="$(mktemp)"
  !   md5sum $statedir/isc-dhcp-v4-$interface.conf 
$statedir/isc-dhcp-v6-$interface.conf > $newstate
  if ! cmp $oldstate $newstate; then
  systemctl try-reload-or-restart systemd-resolved.service
  fi
  ===  END  PATCH ===

  Also, the script removes the script removes the $oldstate file but
  doesn't remove the $newstate file.

  Not sure how this made it through QA testing... But breaking DHCP
  client shouldn't happen like this.

  ivan.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: network-manager 1.20.4-2ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  Date: Sun Oct 27 11:48:33 2019
  InstallationDate: Installed on 2017-04-21 (918 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  IpRoute:
   default via 172.16.1.14 dev enp0s5 
   150.101.89.32/28 dev enp0s5 scope link 
   169.254.0.0/16 dev enp0s5 scope link metric 1000 
   172.16.1.0/24 dev enp0s5 proto kernel scope link src 172.16.1.120
  IwConfig:
   lono wireless extensions.
   
   enp0s5no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=false
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=vt100
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (0 days ago)
  nmcli-con:
   
  nmcli-dev:
   DEVICE  TYPE  STATE  

[Touch-packages] [Bug 1624320] Re: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries

[Vinicius]

This affects me since version 18.04 LTS and the workaround by Vincent Fortier 
(th0ma7) on #8 solves it. But I'll be much thankful if this bug is fixed on the 
next LTS release (20.04). It impacts me on every production instance.
I also vote to change to "Insanely broken and wrong".

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

Title:
  systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing
  entries

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  systemd-resolved, or more precisely the hook script
  /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf, causes
  resolvconf to add 127.0.0.53 to the set of nameservers in
  /etc/resolv.conf alongside the other nameservers.  That makes no sense
  because systemd-resolved sets up 127.0.0.53 as a proxy for those other
  nameservers.  The effect is similar to bug 1624071 but for
  applications doing their own DNS lookups.  It breaks any DNSSEC
  validation that systemd-resolved tries to do; applications will
  failover to the other nameservers, bypassing validation failures.  And
  it makes failing queries take twice as long.

  /etc/resolv.conf should have only 127.0.0.53 when systemd-resolved is
  active.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624320/+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 1844853] Re: IBus no longer works in Qt applications after upgrade

[Bug Watch Updater]

** Changed in: glib
   Status: New => Fix Released

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

Title:
  IBus no longer works in Qt applications after upgrade

Status in GLib:
  Fix Released
Status in ibus:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Confirmed
Status in ibus package in Ubuntu:
  Fix Released
Status in ibus package in Debian:
  Confirmed

Bug description:
  Kubuntu Release 18.04.3 LTS

  Expected behavior:
  ibus continues working as before after applying security update 
1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5.

  Observed behavior:
  ibus is not usable anymore in Qt applications.

  After updating ibus and the related packages ibus-gtk, ibus-gtk3, 
libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 
1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using 
shift-space no longer changes the selected input method and even when i switch 
to the mozc input method in a gtk application, i can not use it in any Qt 
applications.
  When starting qtconfig in a terminal, I also get the following message:

  Bus::open: Connect ibus failed! 
  IBusInputContext::createInputContext: no connection to ibus-daemon

  This bug was not present in version 1.5.17-3ubuntu5 and I also
  confirmed that downgrading the packages to version 1.5.17-3ubuntu4
  restores ibus functionality in Qt applications.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu5.1
  ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 21 07:58:56 2019
  InstallationDate: Installed on 2019-06-28 (84 days ago)
  InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1844853/+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 1845494] Re: gdb 8.1-0ubuntu3.1 freezes before call main function while debugging 32bit application

[Christian Biesinger]

This might be this GDB bug (patch available there too):
https://sourceware.org/bugzilla/show_bug.cgi?id=23210#c6

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

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

Title:
  gdb 8.1-0ubuntu3.1 freezes before call main function while debugging
  32bit application

Status in gdb package in Ubuntu:
  Confirmed

Bug description:
  gdb 8.1ubuntu3.1 run binary 64bit without problem.
  If compile for 32bit target (g++ -m32 ..) then it can't load libraries
  before call main(), i mean it gets frozen.
  gdb 8.1-0ubuntu3 works with 32 and 64 bit binaries without problem.

  Here is log:
  g++ -m32 -o test test.cpp
  gdb ./test

  GNU gdb (Ubuntu 8.1-0ubuntu3.1) 8.1.0.20180409-git
  Copyright (C) 2018 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from ./test...(no debugging symbols found)...done.
  (gdb) run
  Starting program: /tmp/test
  warning: Breakpoint address adjusted from 0xf7fd9be0 to 0xf7fd9be0.
  warning: Breakpoint address adjusted from 0xf7fda195 to 0xf7fda195.
  warning: Breakpoint address adjusted from 0xf7fdbd1c to 0xf7fdbd1c.
  warning: Breakpoint address adjusted from 0xf7fdb924 to 0xf7fdb924.
  warning: Breakpoint address adjusted from 0xf7fe99b3 to 0xf7fe99b3.
  warning: Breakpoint address adjusted from 0xf7fea401 to 0xf7fea401.
  warning: Breakpoint address adjusted from 0xf7fea706 to 0xf7fea706.
  exit()
  ^C
  Program received signal SIGINT, Interrupt.
  0xf7fd9be0 in ?? () from /lib/ld-linux.so.2

  lsb_release -a
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04
  Codename: bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1845494/+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 1659534] Re: userdel doesn't supports extrausers

[Zygmunt Krynicki]

I inspected snapd and noticed that we don't invoke "userdel" or
"deluser" in any production code. We have some tests that do use it and
we now support --extrausers there.

I'm inclined to mark the snappy task as fix released, given that we
inherit the relevant tools from core and core18 snaps which in turn are
fed with updates from the archive. While in the past we carried this
patch locally in a package override, given that it is now fixed in both
Xenial and Bionic I cannot imagine anything else we'd have to do in the
context of this issue.

With this rationale I'm marking it as fix released. Please reopen if
there's more relevant work to be done.

** Changed in: snappy
   Status: In Progress => Fix Released

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

Title:
  userdel doesn't supports extrausers

Status in Snappy:
  Fix Released
Status in shadow package in Ubuntu:
  Fix Released
Status in shadow source package in Xenial:
  Fix Released
Status in shadow source package in Bionic:
  Fix Released
Status in shadow source package in Cosmic:
  Confirmed

Bug description:
  TEST CASE:
  - run userdel --extrausers foo on a ubuntu core system

  REGRESSION POTENTIAL:
  - low, this option will only take effect when "userdel --extrauser" is used.

  On an Ubuntu Core system is impossible to delete an user from the
  extrausers db:

  root@localhost:/# userdel --extrausers alice
  userdel: unrecognized option '--extrausers'

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1659534/+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 1850432] Re: acrually i wanted the graphics driver for my intel 3000 graphics driver for 2nd gen core i3 processor

[Timo Aaltonen]

Why? The default for your GPU is 'modeset'.

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

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

Title:
  acrually i wanted the graphics driver for my intel 3000 graphics
  driver for 2nd gen core i3 processor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  acrually i wanted the graphics driver for my intel 3000 graphics
  driver for 2nd gen core i3 processor

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 29 20:09:47 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:0591]
  InstallationDate: Installed on 2019-10-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Dell Inc. Inspiron 3421
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=UUID=caaedd10-467d-46ef-9bc9-df58fb08f913 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0WF4PW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A13
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd12/14/2015:svnDellInc.:pnInspiron3421:pvrNotSpecified:rvnDellInc.:rn0WF4PW:rvrA13:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3421
  dmi.product.sku: Inspiron 3421
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1850432/+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 1647285] Re: SSL trust not system-wide

[Kevin]

@dwmw2,

I figured out the issue. Long story short, freeipa (which is our CA),
when we enroll a PC into the realm, it adds the freeIPA cert to
/etc/ssl/certs/ca-certificates.crt like it should, however it also adds
other information that it shouldn't.

This results in p11-kit-trust.so blowing parsing errors.

You can read the entire bug report here if you want.

https://pagure.io/freeipa/issue/8106

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

Title:
  SSL trust not system-wide

Status in ca-certificates package in Ubuntu:
  Confirmed
Status in nss package in Ubuntu:
  Confirmed
Status in p11-kit package in Ubuntu:
  Confirmed
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  When I install a corporate CA trust root with update-ca-certificates,
  it doesn't seem to work everywhere. Various things like Firefox,
  Evolution, Chrome, etc. all fail to trust the newly-installed trusted
  CA.

  This ought to work, and does on other distributions. In p11-kit there
  is a module p11-kit-trust.so which can be used as a drop-in
  replacement for NSS's own libnssckbi.so trust root module, but which
  reads from the system's configured trust setup instead of the hard-
  coded version.

  This allows us to install the corporate CAs just once, and then file a
  bug against any package that *doesn't* then trust them.

  See https://fedoraproject.org/wiki/Features/SharedSystemCertificates
  for some of the historical details from when this feature was first
  implemented, but this is all now supported upstream and not at all
  distribution-specific. There shouldn't be any significant work
  required; it's mostly just a case of configuring and building it to
  make use of this functionality. (With 'alternatives' to let you
  substitute p11-kit-trust.so for the original NSS libnssckbi.so, etc.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1647285/+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 1849856] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1849856

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

** Tags added: disco

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

Title:
  ip commands error with mellanox devices in switchdev mode

Status in iproute2 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Kernel: using 5.0.0-23-generic from hwe-edge

  Configuring a mellanox connectx device with configured VF's into
  switchdev (rather than legacy) mode result in the ip cli tool erroring
  when trying to query the interface state:

  $ sudo ip link
  Error: Buffer too small for object.
  Dump terminated

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: iproute2 4.15.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  Date: Fri Oct 25 14:55:36 2019
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: iproute2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1849856/+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 1849856] Re: ip commands error with mellanox devices in switchdev mode

[James Page]

Managed to figure out why this was happening - I had the NUM_VFS in the
card firmware configured to 127 (the maximum value) - reducing this to a
lower number allowed me to successfully switch the cards into switchdev
mode at which point the ip tools all worked again.

The clue that pointed to this appeared when using the proposed 5.3 hwe
edge kernel:

  [  694.027106] infiniband (null): mlx5_ib_alloc_counters:5452:(pid
47479): couldn't allocate queue counter for port 128, err -12

(128 being the pertinent value)


** Also affects: 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 iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1849856

Title:
  ip commands error with mellanox devices in switchdev mode

Status in iproute2 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Kernel: using 5.0.0-23-generic from hwe-edge

  Configuring a mellanox connectx device with configured VF's into
  switchdev (rather than legacy) mode result in the ip cli tool erroring
  when trying to query the interface state:

  $ sudo ip link
  Error: Buffer too small for object.
  Dump terminated

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: iproute2 4.15.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  Date: Fri Oct 25 14:55:36 2019
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: iproute2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1849856/+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 1850502] [NEW] Bluetooth disconnects intermittently on ubuntu 19.10 [RTL8822BE]

[shyamjose]

Public bug reported:

My Bluetooth speaker is disconnecting few minutes after playing youtube
videos on google chrome  [no issues when playing videos in mpv], also I
have noticed that ubuntu detecting my speaker as Bluetooth keyboard
instead of speaker !!

Please find the log below


Oct 29 22:48:56 Asus-VivoBook wpa_supplicant[822]: wlp2s0: 
CTRL-EVENT-BEACON-LOSS 
Oct 29 22:49:29 Asus-VivoBook wpa_supplicant[822]: message repeated 3 times: [ 
wlp2s0: CTRL-EVENT-BEACON-LOSS ]
Oct 29 22:49:37 Asus-VivoBook acpid: input device has been disconnected, fd 18
Oct 29 22:49:37 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (II) 
config/udev: removing device AA:AA:AA:AA:AA:AA
Oct 29 22:49:37 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (**) Option 
"fd" "68"
Oct 29 22:49:37 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (II) event15 - 
AA:AA:AA:AA:AA:AA: device removed
Oct 29 22:49:37 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (II) 
UnloadModule: "libinput"
Oct 29 22:49:37 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (II) 
systemd-logind: releasing fd for 13:79
Oct 29 22:49:37 Asus-VivoBook bluetoothd[819]: Unable to get io data for 
Headset Voice gateway: getpeername: Transport endpoint is not connected (107)
Oct 29 22:49:37 Asus-VivoBook gsd-media-keys[1956]: Unable to get default sink
Oct 29 22:49:46 Asus-VivoBook kernel: [ 2399.077733] input: AA:AA:AA:AA:AA:AA 
as /devices/virtual/input/input19
Oct 29 22:49:46 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (II) 
config/udev: Adding input device AA:AA:AA:AA:AA:AA (/dev/input/event15)
Oct 29 22:49:46 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (**) 
AA:AA:AA:AA:AA:AA: Applying InputClass "libinput keyboard catchall"
Oct 29 22:49:46 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (II) Using 
input driver 'libinput' for 'AA:AA:AA:AA:AA:AA'
Oct 29 22:49:46 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (II) 
systemd-logind: got fd for /dev/input/event15 13:79 fd 69 paused 0
Oct 29 22:49:46 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (**) 
AA:AA:AA:AA:AA:AA: always reports core events
Oct 29 22:49:46 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (**) Option 
"Device" "/dev/input/event15"
Oct 29 22:49:46 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (**) Option 
"_source" "server/udev"
Oct 29 22:49:46 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (II) event15 - 
AA:AA:AA:AA:AA:AA: is tagged by udev as: Keyboard
Oct 29 22:49:46 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (II) event15 - 
AA:AA:AA:AA:AA:AA: device is a keyboard
Oct 29 22:49:46 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (II) event15 - 
AA:AA:AA:AA:AA:AA: device removed
Oct 29 22:49:46 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (**) Option 
"config_info" "udev:/sys/devices/virtual/input/input19/event15"
Oct 29 22:49:46 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (II) XINPUT: 
Adding extended input device "AA:AA:AA:AA:AA:AA" (type: KEYBOARD, id 14)
Oct 29 22:49:46 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (**) Option 
"xkb_model" "pc105"
Oct 29 22:49:46 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (**) Option 
"xkb_layout" "us"
Oct 29 22:49:46 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (WW) Option 
"xkb_variant" requires a string value
Oct 29 22:49:46 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (WW) Option 
"xkb_options" requires a string value
Oct 29 22:49:46 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (II) event15 - 
AA:AA:AA:AA:AA:AA: is tagged by udev as: Keyboard
Oct 29 22:49:46 Asus-VivoBook /usr/lib/gdm3/gdm-x-session[1575]: (II) event15 - 
AA:AA:AA:AA:AA:AA: device is a keyboard

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: bluez 5.50-0ubuntu4
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 29 22:41:48 2019
InstallationDate: Installed on 2019-10-22 (6 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X412UA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=6a724312-c5e6-4ea9-84a3-f755d268a681 ro
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/03/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X412UA.303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X412UA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX412UA.303:bd06/03/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX412UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX412UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: VivoBook
dmi.product.name: VivoBook_ASUSLaptop X412UA

[Touch-packages] [Bug 1850478] Re: package libedataserverui-1.2-1:amd64 3.18.5-1ubuntu1.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attemp

[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 evolution-data-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1850478

Title:
  package libedataserverui-1.2-1:amd64 3.18.5-1ubuntu1.2 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  Install failed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libedataserverui-1.2-1:amd64 3.18.5-1ubuntu1.2
  ProcVersionSignature: Ubuntu 4.4.0-166.195-generic 4.4.194
  Uname: Linux 4.4.0-166-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.19
  AptOrdering:
   linux-modules-4.4.0-164-generic: Remove
   libedataserverui-1.2-1: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Oct 29 06:15:13 2019
  DpkgTerminalLog:
   Removing linux-modules-4.4.0-164-generic (4.4.0-164.192) ...
   dpkg: error processing package libedataserverui-1.2-1:amd64 (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  DuplicateSignature:
   package:libedataserverui-1.2-1:amd64:3.18.5-1ubuntu1.2
   Removing linux-modules-4.4.0-164-generic (4.4.0-164.192) ...
   dpkg: error processing package libedataserverui-1.2-1:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-01-06 (660 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.6
   apt  1.2.32
  SourcePackage: evolution-data-server
  Title: package libedataserverui-1.2-1:amd64 3.18.5-1ubuntu1.2 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1850478/+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 1850478] [NEW] package libedataserverui-1.2-1:amd64 3.18.5-1ubuntu1.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before atte

[Robert Brownell]

Public bug reported:

Install failed

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libedataserverui-1.2-1:amd64 3.18.5-1ubuntu1.2
ProcVersionSignature: Ubuntu 4.4.0-166.195-generic 4.4.194
Uname: Linux 4.4.0-166-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.19
AptOrdering:
 linux-modules-4.4.0-164-generic: Remove
 libedataserverui-1.2-1: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Tue Oct 29 06:15:13 2019
DpkgTerminalLog:
 Removing linux-modules-4.4.0-164-generic (4.4.0-164.192) ...
 dpkg: error processing package libedataserverui-1.2-1:amd64 (--configure):
  package is in a very bad inconsistent state; you should
  reinstall it before attempting configuration
DuplicateSignature:
 package:libedataserverui-1.2-1:amd64:3.18.5-1ubuntu1.2
 Removing linux-modules-4.4.0-164-generic (4.4.0-164.192) ...
 dpkg: error processing package libedataserverui-1.2-1:amd64 (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2018-01-06 (660 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.6
 apt  1.2.32
SourcePackage: evolution-data-server
Title: package libedataserverui-1.2-1:amd64 3.18.5-1ubuntu1.2 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package libedataserverui-1.2-1:amd64 3.18.5-1ubuntu1.2 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  Install failed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libedataserverui-1.2-1:amd64 3.18.5-1ubuntu1.2
  ProcVersionSignature: Ubuntu 4.4.0-166.195-generic 4.4.194
  Uname: Linux 4.4.0-166-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.19
  AptOrdering:
   linux-modules-4.4.0-164-generic: Remove
   libedataserverui-1.2-1: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Oct 29 06:15:13 2019
  DpkgTerminalLog:
   Removing linux-modules-4.4.0-164-generic (4.4.0-164.192) ...
   dpkg: error processing package libedataserverui-1.2-1:amd64 (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  DuplicateSignature:
   package:libedataserverui-1.2-1:amd64:3.18.5-1ubuntu1.2
   Removing linux-modules-4.4.0-164-generic (4.4.0-164.192) ...
   dpkg: error processing package libedataserverui-1.2-1:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-01-06 (660 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.6
   apt  1.2.32
  SourcePackage: evolution-data-server
  Title: package libedataserverui-1.2-1:amd64 3.18.5-1ubuntu1.2 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1850478/+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 1849950] Re: Gnome Shell window shortcuts maximize, windowed and hide (Super + Up / Down / H) don't work if upgrading from Unity

[clel]

I have not changed the config in Unity manually, either. I want to say
that it was just a suspicion that Upgrading from Unity to GNOME caused
this. I cannot say for sure, but your post sounds like that really is
the reason? Just want to make sure this really causes this.

If that is true, I am ok with the solution.

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

Title:
  Gnome Shell window shortcuts maximize, windowed and hide (Super + Up /
  Down / H) don't work if upgrading from Unity

Status in GNOME Shell:
  Fix Released
Status in gsettings-desktop-schemas package in Ubuntu:
  Fix Released

Bug description:
  Happens on Ubuntu 19.10, and did also not work on Ubuntu 19.04 (and
  probably also previous versions), if I recall correctly.

  I am not sure, whether this is an upstream bug of GNOME or just Ubuntu
  related.

  Bug report for GNOME: https://gitlab.gnome.org/GNOME/gnome-
  shell/issues/1829

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1849950/+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 1850258] Re: First breakpoint at AVX instruction with memory operand causes SIGSEGV when tring to continue execution

[Pauli]

A bit more debugging I see that signal comes from kernel (si_code=0x80)
but it claims null pointer reference. I don't understand how it could be
a null pointer  I would need to have better understanding what
happens in gdb and kernel to trigger the SIGSEGV.

I found out also that workaround is to have breakpoint but disable it
after stopping on the problematic instruction. If breakpoint isn't
active then execution continues without issues. Only issues is that I
don't know full set of instructions which actually trigger this issue. I
have had issues with some other memory referencing VEX coded
instructions. But I also have examples of memory reference instructions
which don't trigger the bug.

I attached updated test2.cc which has now signal handling dumping
siginfo.

Reading symbols from ./test2...
(gdb) b main
Breakpoint 1 at 0x650: file test2.cc, line 41.
(gdb) r
Starting program: /home/coren/project/test2 

Breakpoint 1, main () at test2.cc:41
41  asm("\tvmovdqa %1, %0\n" : "=x" (bar) : "xm" (foo));
(gdb) disassemble 
Dump of assembler code for function main():
=> 0x4650 <+0>: vmovdqa 0x19d8(%rip),%xmm0# 
0x6030 
   0x4658 <+8>: vmovd  %xmm0,%eax
   0x465c <+12>:retq   
End of assembler dump.
(gdb) c
Continuing.

Program received signal SIGSEGV, Segmentation fault.
main () at test2.cc:41
41  asm("\tvmovdqa %1, %0\n" : "=x" (bar) : "xm" (foo));
(gdb) 
Continuing.
sig: 11, ctx: 0x7fffd740
si_signo: 11, si_erron: 0, si_code: 128
si_addr: (nil), si_addr_lsb: 0, si_pid: 0, si_uid: 0

Breakpoint 1, main () at test2.cc:41
41  asm("\tvmovdqa %1, %0\n" : "=x" (bar) : "xm" (foo));
(gdb) 
Continuing.

Program received signal SIGSEGV, Segmentation fault.
main () at test2.cc:41
41  asm("\tvmovdqa %1, %0\n" : "=x" (bar) : "xm" (foo));
(gdb) 
Continuing.
sig: 11, ctx: 0x7fffd740
si_signo: 11, si_erron: 0, si_code: 128
si_addr: (nil), si_addr_lsb: 0, si_pid: 0, si_uid: 0

Breakpoint 1, main () at test2.cc:41
41  asm("\tvmovdqa %1, %0\n" : "=x" (bar) : "xm" (foo));
(gdb) dis 1
(gdb) c
Continuing.
[Inferior 1 (process 9091) exited with code 01]


** Attachment added: "test2.cc (A test case with signal handler returning)"
   
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1850258/+attachment/5301182/+files/test2.cc

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

Title:
  First breakpoint at AVX instruction with memory operand causes SIGSEGV
  when tring to continue execution

Status in gdb package in Ubuntu:
  New

Bug description:
  I noticed random looking SIGSEGV to application when trying to
  continue execution after first breakpoint. I now seem to have narrowed
  the issue to SIMD instruction with memory operand as first breakpoint
  location. I haven't managed to figure out why the SIGSEGV is delivered
  to the debugger application.

  It is important have first breakpoint exactly at a problematic
  instructions. If I first break on a different instruction then later
  breakpoints won't reproduce that crash

  I haven't tested if this is a hardware specific issue.

  I managed to write a simple test case which reproduces the crash if
  breakpoint is set. I attached the test.cc which includes compilation
  and testing instructions. test.cc is supposed to generate a simple
  main function like:

  Dump of assembler code for function main():
  => 0x4520 <+0>:   vmovdqa 0x1af8(%rip),%xmm0# 
0x6020 
     0x4528 <+8>:   vmovd  %xmm0,%eax
     0x452c <+12>:  retq

  I set breakpoint with:
  b main

  Then either continue or stepping causes SIGSEGV to the debugged
  application.

  This was happening already with disco. I only now figured out enough
  details to make a simple test case which is worth a bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gdb 8.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Oct 29 09:44:52 2019
  InstallationDate: Installed on 2037-12-25 (-6632 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gdb
  UpgradeStatus: Upgraded to eoan on 2019-10-27 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1850258/+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 1849886] Re: lightdm does not work on eoan on raspberry pi 4

[Kenneth Zadeck]

it is nice to know that i am not the only one wrestling with these alligators.
here is your log as requested.

kenny

** Attachment added: "output of journalctl -b 0"
   
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1849886/+attachment/5301170/+files/log

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

Title:
  lightdm does not work on eoan on raspberry pi 4

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  if you follow the directions on
  https://wiki.ubuntu.com/ARM/RaspberryPi

  sudo apt-get install xubuntu-desktop

  about 20% thru the installation it will ask which window manager you want 
(using dpkg-reconfigure).
  if you select lightdm, you will only get a blank greeter screen after you 
reboot.

  using sudo dpkg-reconfigure gdm3

  resets this to gdm3 and after a reboot, everything is fine.

  this was done on a clean armhf eoan install on a 4gb raspberry pi 4B.

  I have done the install several times.   This bug is repeatable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1849886/+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 1841058] Re: kernel version 4.4.0-1090-aws docker file system issue

[Orlix]

Update on kernel 1096 and the issue still persist
in our container we run as non-root user 
after sed-ing the file persmission are still rw for the user but the nginx 
cannot read the file
after chmod u+rw file with same user the file is readable again... 

E.g.
docker run --rm -ti --entrypoint=bash  -u nginx nginx
nginx@5d5453275231:/$ cd /tmp/
nginx@5d5453275231:/tmp$ echo aaa > test
nginx@5d5453275231:/tmp$ cat test
aaa
nginx@5d5453275231:/tmp$ sed -i 's/a/Q/g' test
nginx@5d5453275231:/tmp$ cat test
cat: test: Permission denied
nginx@5d5453275231:/tmp$ chmod u+rw test
nginx@5d5453275231:/tmp$ cat test
QQQ
nginx@5d5453275231:/tmp$

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

Title:
  kernel version 4.4.0-1090-aws docker file system issue

Status in linux-aws package in Ubuntu:
  New
Status in sed package in Ubuntu:
  New

Bug description:
  When using kernel version 4.4.0-1090-aws 
  if you have running container and you do sed on some files then you cannot 
access them inside the container any more

  we use the nginx image and we can reproduce it everytime

  in the container we have chown and then sed commands on some nginx.conf files 
  after the sed we are getting persmission denied inside the container even 
that we use root.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1841058/+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 1849886] Re: lightdm does not work on eoan on raspberry pi 4

[Sebastien Bacher]

Could you get the 'journalctl -b 0' log from a failed session?

** Package changed: software-properties (Ubuntu) => lightdm (Ubuntu)

** Changed in: lightdm (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  lightdm does not work on eoan on raspberry pi 4

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  if you follow the directions on
  https://wiki.ubuntu.com/ARM/RaspberryPi

  sudo apt-get install xubuntu-desktop

  about 20% thru the installation it will ask which window manager you want 
(using dpkg-reconfigure).
  if you select lightdm, you will only get a blank greeter screen after you 
reboot.

  using sudo dpkg-reconfigure gdm3

  resets this to gdm3 and after a reboot, everything is fine.

  this was done on a clean armhf eoan install on a 4gb raspberry pi 4B.

  I have done the install several times.   This bug is repeatable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1849886/+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 1850444] [NEW] Cannot connect headset to A2DP anymore....

[Rob Frohne]

Public bug reported:

As of October 29, I can no longer connect to my Sony MDR-1000x headphones using 
A2DP.  The gnome sound manager has the setting, but when I select it and use 
the test button, it is only mono.  I tried the gnome extension 
https://extensions.gnome.org/extension/906/sound-output-device-chooser/ and the 
option is always grayed out there. I tried to make A2DP the default using the 
method described here: 
https://medium.com/@overcode/fixing-bluetooth-in-ubuntu-pop-os-18-04-d4b8dbf7ddd6
I tried to install some tools to try and get a better idea what might be going 
on.  In case it was a recent update, here are the last few days of my update 
log:
Start-Date: 2019-10-21  08:19:53
Commandline: aptdaemon role='role-commit-packages' sender=':1.375055'
Install: linux-image-5.3.0-19-generic:amd64 (5.3.0-19.20, automatic), 
linux-modules-extra-5.3.0-19-generic:amd64 (5.3.0-19.20, automatic), 
linux-headers-5.3.0-19-generic:amd64 (5.3.0-19.20, automatic), 
linux-modules-5.3.0-19-generic:amd64 (5.3.0-19.20, automatic), 
linux-headers-5.3.0-19:amd64 (5.3.0-19.20, automatic)
Upgrade: linux-headers-generic:amd64 (5.3.0.18.21, 5.3.0.19.22), 
linux-libc-dev:amd64 (5.3.0-18.19, 5.3.0-19.20), linux-image-generic:amd64 
(5.3.0.18.21, 5.3.0.19.22), linux-signed-generic:amd64 (5.3.0.18.21, 
5.3.0.19.22), linux-generic:amd64 (5.3.0.18.21, 5.3.0.19.22)
End-Date: 2019-10-21  08:21:37

Start-Date: 2019-10-21  11:42:11
Commandline: aptdaemon role='role-commit-packages' sender=':1.1749'
Upgrade: libaspell15:amd64 (0.60.7-3, 0.60.7-3ubuntu0.1), aspell:amd64 
(0.60.7-3, 0.60.7-3ubuntu0.1), libexiv2-14:amd64 (0.25-4ubuntu2, 
0.25-4ubuntu2.1)
Remove: linux-modules-extra-5.0.0-32-generic:amd64 (5.0.0-32.34), 
linux-modules-5.0.0-32-generic:amd64 (5.0.0-32.34), 
linux-image-5.0.0-32-generic:amd64 (5.0.0-32.34)
End-Date: 2019-10-21  11:42:26

Start-Date: 2019-10-22  06:19:40
Commandline: /usr/bin/unattended-upgrade
Upgrade: libopenjp2-7:amd64 (2.3.0-2, 2.3.0-2build0.19.10.1)
End-Date: 2019-10-22  06:19:41

Start-Date: 2019-10-22  19:12:43
Commandline: aptdaemon role='role-commit-packages' sender=':1.375112'
Upgrade: google-chrome-stable:amd64 (77.0.3865.120-1, 78.0.3904.70-1), 
xsltproc:amd64 (1.1.33-0ubuntu1, 1.1.33-0ubuntu1.1), libxslt1.1:amd64 
(1.1.33-0ubuntu1, 1.1.33-0ubuntu1.1), libxslt1.1:i386 (1.1.33-0ubuntu1, 
1.1.33-0ubuntu1.1)
End-Date: 2019-10-22  19:12:59

Start-Date: 2019-10-24  07:00:54
Commandline: aptdaemon role='role-commit-packages' sender=':1.660642'
Upgrade: firefox-locale-en:amd64 (69.0.3+build1-0ubuntu1, 
70.0+build2-0ubuntu0.19.10.1), firefox:amd64 (69.0.3+build1-0ubuntu1, 
70.0+build2-0ubuntu0.19.10.1), linux-firmware:amd64 (1.183, 1.183.1)
End-Date: 2019-10-24  07:01:58

Start-Date: 2019-10-29  06:33:22
Commandline: /usr/bin/unattended-upgrade
Upgrade: libwbclient0:amd64 (2:4.10.7+dfsg-0ubuntu2, 2:4.10.7+dfsg-0ubuntu2.2), 
samba-libs:amd64 (2:4.10.7+dfsg-0ubuntu2, 2:4.10.7+dfsg-0ubuntu2.2), 
libsmbclient:amd64 (2:4.10.7+dfsg-0ubuntu2, 2:4.10.7+dfsg-0ubuntu2.2)
End-Date: 2019-10-29  06:33:25

Start-Date: 2019-10-29  07:22:22
Commandline: /usr/sbin/synaptic
Requested-By: frohro (1000)
Install: bluez-tests:amd64 (5.50-0ubuntu4), bluez-tools:amd64 
(2.0~20170911.0.7cb788c-2build1), bluetooth:amd64 (5.50-0ubuntu4)
End-Date: 2019-10-29  07:22:28

Start-Date: 2019-10-29  07:44:42
Commandline: apt install pulseaudio pulseaudio-utils pavucontrol 
pulseaudio-module-bluetooth
Requested-By: frohro (1000)
Install: pavucontrol:amd64 (3.0-4)
End-Date: 2019-10-29  07:44:48

Nothing I tried solves the issue.  It was working a few days ago.

Thanks,

Rob

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: bluez 5.50-0ubuntu4
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 29 07:52:45 2019
InstallationDate: Installed on 2019-04-19 (193 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: LENOVO 20FES0EX00
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro
SourcePackage: bluez
UpgradeStatus: Upgraded to eoan on 2019-10-18 (11 days ago)
dmi.bios.date: 06/26/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N1GET91W (1.70 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FES0EX00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 31
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1GET91W(1.70):bd06/26/2018:svnLENOVO:pn20FES0EX00:pvrThinkPadYoga260:rvnLENOVO:rn20FES0EX00:rvrSDK0J40700WIN:cvnLENOVO:ct31:cvrNone:
dmi.product.family: ThinkPad Yoga 260
dmi.product.name: 20FES0EX00
dmi.product.sku: 

[Touch-packages] [Bug 1848969] Re: src/date-time.cpp:171:GDateTime* unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)

[Sebastien Bacher]

Setting as rls-ff-notfixing since from a Desktop Team
perspective/workflow it's our of our active set now and we are not going
to consider it as a blocker. It's just a workflow detail though and
doesn't mean the bug shouldn't be/isn't going to be fixed

** Tags removed: rls-ff-incoming
** Tags added: rls-ff-notfixing

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

Title:
  src/date-time.cpp:171:GDateTime*
  unity::indicator::datetime::DateTime::get() const: assertion failed:
  (m_dt)

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Ubuntu 19.10, indicator-datetime
  15.10+19.10.20190819.1-0ubuntu1 crashes right from the start:

  $ /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service 
  (process:17641): Indicator-Datetime-WARNING **: 01:46:35.442: Unrecognized 
TZID: 'Etc/Utc'
  (process:17641): Indicator-Datetime-WARNING **: 01:46:35.442: Unrecognized 
TZID: 'Etc/Utc'
  (process:17641): Indicator-Datetime-WARNING **: 01:46:35.448: Unrecognized 
TZID: 'Etc/Utc'
  (process:17641): libecal-CRITICAL **: 01:46:35.457: 
e_cal_component_datetime_get_value: assertion 'dt != NULL' failed
  (process:17641): libecal-CRITICAL **: 01:46:35.457: 
e_cal_component_datetime_get_value: assertion 'dt != NULL' failed
  (process:17641): libical-glib-CRITICAL **: 01:46:35.457: i_cal_time_as_timet: 
assertion 'I_CAL_IS_TIME (tt)' failed
  (process:17641): libical-glib-CRITICAL **: 01:46:35.457: i_cal_time_as_timet: 
assertion 'I_CAL_IS_TIME (tt)' failed
  [...]
  (process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet: 
assertion 'I_CAL_IS_TIME (tt)' failed
  (process:17641): libecal-CRITICAL **: 01:46:35.458: 
e_cal_component_datetime_get_value: assertion 'dt != NULL' failed
  (process:17641): libecal-CRITICAL **: 01:46:35.458: 
e_cal_component_datetime_get_value: assertion 'dt != NULL' failed
  (process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet: 
assertion 'I_CAL_IS_TIME (tt)' failed
  (process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet: 
assertion 'I_CAL_IS_TIME (tt)' failed
  **
  
Indicator-Datetime:ERROR:/build/indicator-datetime-P60bPZ/indicator-datetime-15.10+19.10.20190819.1/src/date-time.cpp:171:GDateTime*
 unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)
  Bail out! 
Indicator-Datetime:ERROR:/build/indicator-datetime-P60bPZ/indicator-datetime-15.10+19.10.20190819.1/src/date-time.cpp:171:GDateTime*
 unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1848969/+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 1647285] Re: SSL trust not system-wide

[dwmw2]

@kvasko yes, it works here. Are you sure that's the version of
libnssckbi.so that is being used? There are lots; I've replaced them
all...

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

Title:
  SSL trust not system-wide

Status in ca-certificates package in Ubuntu:
  Confirmed
Status in nss package in Ubuntu:
  Confirmed
Status in p11-kit package in Ubuntu:
  Confirmed
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  When I install a corporate CA trust root with update-ca-certificates,
  it doesn't seem to work everywhere. Various things like Firefox,
  Evolution, Chrome, etc. all fail to trust the newly-installed trusted
  CA.

  This ought to work, and does on other distributions. In p11-kit there
  is a module p11-kit-trust.so which can be used as a drop-in
  replacement for NSS's own libnssckbi.so trust root module, but which
  reads from the system's configured trust setup instead of the hard-
  coded version.

  This allows us to install the corporate CAs just once, and then file a
  bug against any package that *doesn't* then trust them.

  See https://fedoraproject.org/wiki/Features/SharedSystemCertificates
  for some of the historical details from when this feature was first
  implemented, but this is all now supported upstream and not at all
  distribution-specific. There shouldn't be any significant work
  required; it's mostly just a case of configuring and building it to
  make use of this functionality. (With 'alternatives' to let you
  substitute p11-kit-trust.so for the original NSS libnssckbi.so, etc.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1647285/+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 1827644] Re: UPower and battery indicator show wrong information on fully charged ASUS Vivobook X510UR laptop

[Yayai]

Been trying for days to 'fix' the battery status, 9.7 hours to full?
think ubuntu is on crack

Device: /org/freedesktop/UPower/devices/line_power_AC
  native-path:  AC
  power supply: yes
  updated:  Tue 29 Oct 2019 09:06:08 PM +08 (4275 seconds ago)
  has history:  no
  has statistics:   no
  line-power
warning-level:   none
online:  yes
icon-name:  'ac-adapter-symbolic'

Device: /org/freedesktop/UPower/devices/battery_BAT0
  native-path:  BAT0
  vendor:   Hewlett-Packard
  model:Primary
  serial:   15305 03/10/2016
  power supply: yes
  updated:  Tue 29 Oct 2019 10:16:20 PM +08 (63 seconds ago)
  has history:  yes
  has statistics:   yes
  battery
present: yes
rechargeable:yes
state:   charging
warning-level:   none
energy:  20.9218 Wh
energy-empty:0 Wh
energy-full: 24.3382 Wh
energy-full-design:  17.8996 Wh
energy-rate: 0.3504 W
voltage: 16.004 V
time to full:9.7 hours
percentage:  100%
capacity:100%
technology:  lithium-ion
icon-name:  'battery-full-charging-symbolic'

Device: /org/freedesktop/UPower/devices/DisplayDevice
  power supply: yes
  updated:  Tue 29 Oct 2019 09:44:19 PM +08 (1984 seconds ago)
  has history:  no
  has statistics:   no
  battery
present: yes
state:   charging
warning-level:   none
energy:  20.9218 Wh
energy-full: 24.3382 Wh
energy-rate: 0.3504 W
time to full:9.7 hours
percentage:  100%
icon-name:  'battery-full-charging-symbolic'

Daemon:
  daemon-version:  0.99.7
  on-battery:  no
  lid-is-closed:   no
  lid-is-present:  yes
  critical-action: HybridSleep

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

Title:
  UPower and battery indicator show wrong information on fully charged
  ASUS Vivobook X510UR laptop

Status in upower package in Ubuntu:
  Confirmed

Bug description:
  When the ASUS Vivobook X510UR laptop is completely charged, the
  correct information is displayed on Windows. However, Ubuntu 18.04.2
  LTS is unable to detect the true battery state. The GNOME battery
  indicator usually shows "Estimating..." or "Not charging", when the
  battery is at 100%.

  If you use the upower version 0.99.7-2ubuntu0.18.04.1 command "upower
  -i /org/freedesktop/UPower/devices/battery_BAT0", this is what you
  get:

native-path:  BAT0
vendor:   ASUSTeK
model:ASUS Battery
power supply: yes
updated:  sex 03 mai 2019 14:33:43 -03 (4 seconds ago)
has history:  yes
has statistics:   yes
battery
  present: yes
  rechargeable:yes
  state:   pending-charge
  warning-level:   none
  energy:  39,191 Wh
  energy-empty:0 Wh
  energy-full: 39,26 Wh
  energy-full-design:  42,082 Wh
  energy-rate: 12,453 W
  voltage: 11,52 V
  percentage:  100%
  capacity:93,294%
  technology:  lithium-ion
  icon-name:  'battery-full-charging-symbolic'
History (charge):
  1556904821100,000 discharging
History (rate):
  155690482112,453  discharging
  15569048183,744   discharging

  The "state" should be "fully-charged", but instead it is "pending-
  charge".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: upower 0.99.7-2ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri May  3 14:34:14 2019
  InstallationDate: Installed on 2018-12-11 (142 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1827644/+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 1647285] Re: SSL trust not system-wide

[Timo Aaltonen]

should this be marked as something to fix in focal for the next LTS?

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

Title:
  SSL trust not system-wide

Status in ca-certificates package in Ubuntu:
  Confirmed
Status in nss package in Ubuntu:
  Confirmed
Status in p11-kit package in Ubuntu:
  Confirmed
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  When I install a corporate CA trust root with update-ca-certificates,
  it doesn't seem to work everywhere. Various things like Firefox,
  Evolution, Chrome, etc. all fail to trust the newly-installed trusted
  CA.

  This ought to work, and does on other distributions. In p11-kit there
  is a module p11-kit-trust.so which can be used as a drop-in
  replacement for NSS's own libnssckbi.so trust root module, but which
  reads from the system's configured trust setup instead of the hard-
  coded version.

  This allows us to install the corporate CAs just once, and then file a
  bug against any package that *doesn't* then trust them.

  See https://fedoraproject.org/wiki/Features/SharedSystemCertificates
  for some of the historical details from when this feature was first
  implemented, but this is all now supported upstream and not at all
  distribution-specific. There shouldn't be any significant work
  required; it's mostly just a case of configuring and building it to
  make use of this functionality. (With 'alternatives' to let you
  substitute p11-kit-trust.so for the original NSS libnssckbi.so, etc.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1647285/+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 1850009] Re: Issue with detecting new state in dhclient-enter-hooks.d/resolved

[Peteris Dzenis]

Hello,

I can confirm this issue: name resolution was not working after
upgrading to Ubuntu 19.10. It was possible to fix it until the next
reboot (or next networking service restart) by restarting systemd-
resolved service. Located the same issue and temporary resolved it by
commenting out `if' condition, forcing systemd-resolved service to
always reload/restart as it was in previous Ubuntu versions.

These are the changes to /etc/dhcp/dhclient-enter-hooks/resolved file:

--- resolved.original2019-10-29 15:43:51.940561949 +0200
+++ resolved2019-10-29 15:44:24.804941675 +0200
@@ -56,9 +56,9 @@

   newstate="$(mktemp)"
   md5sum $statedir/isc-dhcp-v4-$interface.conf 
$statedir/isc-dhcp-v6-$interface.conf &> $newstate
-  if ! cmp $oldstate $newstate; then
+  #if ! cmp $oldstate $newstate; then
   systemctl try-reload-or-restart systemd-resolved.service
-  fi
+  #fi

   rm $oldstate
   }


Best regards,
Peteris

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

Title:
  Issue with detecting new state in dhclient-enter-hooks.d/resolved

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 19.10 I noticed that resolving hostnames stopped
  working.

  Quick release, which package and version info:

  root@caret:~# lsb_release -r
  Release:19.10
  root@caret:~# dpkg -S /etc/dhcp/dhclient-enter-hooks.d/resolved
  systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved
  root@caret:~# apt-cache policy systemd
  systemd:
Installed: 242-7ubuntu3
Candidate: 242-7ubuntu3
Version table:
   *** 242-7ubuntu3 500
  500 http://au.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  
  The file /etc/resolv.conf was pointing to the local instance of 
systemd-resolved however there was no search line, indicating something wasn't 
quite right.

  Restarting the systemd-resolved service did recreate /etc/resolv.conf
  with expected search line.

  After much debugging, I've worked out what was going wrong.

  The dhcp hook file /etc/dhcp/dhclient-enter-hooks.d/resolved has a bug
  in the resolver state change logic.

  This may also impact on tickets 1805183, 1832050, 1832053 and maybe
  others.

  When doing the md5sum of the old and new state, the command is wrong.
  It isn't sending STDOUT (and optionally STDERR) to the temp file but
  rather putting the md5sum command into the background and then
  creating an empty file for both states. Which obviously isn't
  different, so systemd-resolved doesn't restart.

  Quick diff of a working version (I'm not capturing STDERR but one can
  with "2>&1")

  === BEGIN PATCH ===
  *** .brk-resolved-20191027  2019-10-27 11:19:56.210069032 +1030
  --- resolved2019-10-27 11:30:17.156381734 +1030
  ***
  *** 30,36 
  mkdir -p $statedir

  oldstate="$(mktemp)"
  !   md5sum $statedir/isc-dhcp-v4-$interface.conf 
$statedir/isc-dhcp-v6-$interface.conf &> $oldstate
  if [ -n "$new_domain_name_servers" ] ; then
  cat <$statedir/isc-dhcp-v4-$interface.conf
[Resolve]
  --- 30,36 
  mkdir -p $statedir

  oldstate="$(mktemp)"
  !   md5sum $statedir/isc-dhcp-v4-$interface.conf 
$statedir/isc-dhcp-v6-$interface.conf > $oldstate
  if [ -n "$new_domain_name_servers" ] ; then
  cat <$statedir/isc-dhcp-v4-$interface.conf
[Resolve]
  ***
  *** 55,61 
  fi

  newstate="$(mktemp)"
  !   md5sum $statedir/isc-dhcp-v4-$interface.conf 
$statedir/isc-dhcp-v6-$interface.conf &> $newstate
  if ! cmp $oldstate $newstate; then
  systemctl try-reload-or-restart systemd-resolved.service
  fi
  --- 55,61 
  fi

  newstate="$(mktemp)"
  !   md5sum $statedir/isc-dhcp-v4-$interface.conf 
$statedir/isc-dhcp-v6-$interface.conf > $newstate
  if ! cmp $oldstate $newstate; then
  systemctl try-reload-or-restart systemd-resolved.service
  fi
  ===  END  PATCH ===

  Also, the script removes the script removes the $oldstate file but
  doesn't remove the $newstate file.

  Not sure how this made it through QA testing... But breaking DHCP
  client shouldn't happen like this.

  ivan.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: network-manager 1.20.4-2ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  Date: Sun Oct 27 11:48:33 2019
  InstallationDate: 

[Touch-packages] [Bug 1850432] [NEW] acrually i wanted the graphics driver for my intel 3000 graphics driver for 2nd gen core i3 processor

[Ahmmed Sakin Noman]

Public bug reported:

acrually i wanted the graphics driver for my intel 3000 graphics driver
for 2nd gen core i3 processor

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 29 20:09:47 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:0591]
InstallationDate: Installed on 2019-10-29 (0 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
MachineType: Dell Inc. Inspiron 3421
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=UUID=caaedd10-467d-46ef-9bc9-df58fb08f913 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/14/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A13
dmi.board.name: 0WF4PW
dmi.board.vendor: Dell Inc.
dmi.board.version: A13
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd12/14/2015:svnDellInc.:pnInspiron3421:pvrNotSpecified:rvnDellInc.:rn0WF4PW:rvrA13:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 3421
dmi.product.sku: Inspiron 3421
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  acrually i wanted the graphics driver for my intel 3000 graphics
  driver for 2nd gen core i3 processor

Status in xorg package in Ubuntu:
  New

Bug description:
  acrually i wanted the graphics driver for my intel 3000 graphics
  driver for 2nd gen core i3 processor

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 29 20:09:47 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:0591]
  InstallationDate: Installed on 2019-10-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Dell Inc. Inspiron 3421
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=UUID=caaedd10-467d-46ef-9bc9-df58fb08f913 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0WF4PW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A13
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd12/14/2015:svnDellInc.:pnInspiron3421:pvrNotSpecified:rvnDellInc.:rn0WF4PW:rvrA13:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3421
  dmi.product.sku: Inspiron 3421
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  

[Touch-packages] [Bug 1850009] Re: Issue with detecting new state in dhclient-enter-hooks.d/resolved

[Launchpad Bug Tracker]

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

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

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

Title:
  Issue with detecting new state in dhclient-enter-hooks.d/resolved

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 19.10 I noticed that resolving hostnames stopped
  working.

  Quick release, which package and version info:

  root@caret:~# lsb_release -r
  Release:19.10
  root@caret:~# dpkg -S /etc/dhcp/dhclient-enter-hooks.d/resolved
  systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved
  root@caret:~# apt-cache policy systemd
  systemd:
Installed: 242-7ubuntu3
Candidate: 242-7ubuntu3
Version table:
   *** 242-7ubuntu3 500
  500 http://au.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  
  The file /etc/resolv.conf was pointing to the local instance of 
systemd-resolved however there was no search line, indicating something wasn't 
quite right.

  Restarting the systemd-resolved service did recreate /etc/resolv.conf
  with expected search line.

  After much debugging, I've worked out what was going wrong.

  The dhcp hook file /etc/dhcp/dhclient-enter-hooks.d/resolved has a bug
  in the resolver state change logic.

  This may also impact on tickets 1805183, 1832050, 1832053 and maybe
  others.

  When doing the md5sum of the old and new state, the command is wrong.
  It isn't sending STDOUT (and optionally STDERR) to the temp file but
  rather putting the md5sum command into the background and then
  creating an empty file for both states. Which obviously isn't
  different, so systemd-resolved doesn't restart.

  Quick diff of a working version (I'm not capturing STDERR but one can
  with "2>&1")

  === BEGIN PATCH ===
  *** .brk-resolved-20191027  2019-10-27 11:19:56.210069032 +1030
  --- resolved2019-10-27 11:30:17.156381734 +1030
  ***
  *** 30,36 
  mkdir -p $statedir

  oldstate="$(mktemp)"
  !   md5sum $statedir/isc-dhcp-v4-$interface.conf 
$statedir/isc-dhcp-v6-$interface.conf &> $oldstate
  if [ -n "$new_domain_name_servers" ] ; then
  cat <$statedir/isc-dhcp-v4-$interface.conf
[Resolve]
  --- 30,36 
  mkdir -p $statedir

  oldstate="$(mktemp)"
  !   md5sum $statedir/isc-dhcp-v4-$interface.conf 
$statedir/isc-dhcp-v6-$interface.conf > $oldstate
  if [ -n "$new_domain_name_servers" ] ; then
  cat <$statedir/isc-dhcp-v4-$interface.conf
[Resolve]
  ***
  *** 55,61 
  fi

  newstate="$(mktemp)"
  !   md5sum $statedir/isc-dhcp-v4-$interface.conf 
$statedir/isc-dhcp-v6-$interface.conf &> $newstate
  if ! cmp $oldstate $newstate; then
  systemctl try-reload-or-restart systemd-resolved.service
  fi
  --- 55,61 
  fi

  newstate="$(mktemp)"
  !   md5sum $statedir/isc-dhcp-v4-$interface.conf 
$statedir/isc-dhcp-v6-$interface.conf > $newstate
  if ! cmp $oldstate $newstate; then
  systemctl try-reload-or-restart systemd-resolved.service
  fi
  ===  END  PATCH ===

  Also, the script removes the script removes the $oldstate file but
  doesn't remove the $newstate file.

  Not sure how this made it through QA testing... But breaking DHCP
  client shouldn't happen like this.

  ivan.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: network-manager 1.20.4-2ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  Date: Sun Oct 27 11:48:33 2019
  InstallationDate: Installed on 2017-04-21 (918 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  IpRoute:
   default via 172.16.1.14 dev enp0s5 
   150.101.89.32/28 dev enp0s5 scope link 
   169.254.0.0/16 dev enp0s5 scope link metric 1000 
   172.16.1.0/24 dev enp0s5 proto kernel scope link src 172.16.1.120
  IwConfig:
   lono wireless extensions.
   
   enp0s5no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=false
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=vt100
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (0 days ago)
  nmcli-con:
   
  nmcli-dev:
   DEVICE  TYPE  STATE  IP4-CONNECTIVITY  IP6-CONNECTIVITY  DBUS-PATH   
   CONNECTION  

[Touch-packages] [Bug 1850293] Re: libep11 depends on old libssl for disco/eon/focal

[Frank Heimes]

Affects libssl, but needs to be fixed in libep11 (IBM package - hence reverse 
mirrored).
Either with a new version of libep11 that depends on libssl1.1 instead of 
libssl1.0.0 - or the dependency needs to cover both.

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

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

** Summary changed:

- libep11 depends on old libssl for disco/eon/focal
+ libep11 depends on old libssl for disco/eoan/focal

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

Title:
  libep11 depends on old libssl for disco/eoan/focal

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in openssl package in Ubuntu:
  Invalid

Bug description:
  If using the newest version of libep11_2.1.0-8_s390x.deb with
  Disco/Eoan/Focal 
  downloaded from 
  http://public.dhe.ibm.com/security/cryptocards/pciecc3/EP11/2.1.0/

  Following problem occur.:
  libep11 : Depends: libssl1.0.0 but it is not installable 

  rmadison --arch=s390x libssl1.0.0
   libssl1.0.0 | 1.0.2g-1ubuntu4| xenial  | s390x
   libssl1.0.0 | 1.0.2g-1ubuntu4.15 | xenial-security | s390x
   libssl1.0.0 | 1.0.2g-1ubuntu4.15 | xenial-updates  | s390x
   libssl1.0.0 | 1.0.2n-1ubuntu5| bionic  | s390x
   libssl1.0.0 | 1.0.2n-1ubuntu5.3  | bionic-security | s390x
   libssl1.0.0 | 1.0.2n-1ubuntu5.3  | bionic-updates  | s390x

  $ rmadison --arch=s390x libssl1.1
   libssl1.1 | 1.1.0g-2ubuntu4  | bionic  | s390x
   libssl1.1 | 1.1.1-1ubuntu2.1~18.04.4 | bionic-security | s390x
   libssl1.1 | 1.1.1-1ubuntu2.1~18.04.4 | bionic-updates  | s390x
   libssl1.1 | 1.1.1b-1ubuntu2  | disco   | s390x
   libssl1.1 | 1.1.1b-1ubuntu2.4| disco-updates   | s390x
   libssl1.1 | 1.1.1c-1ubuntu4  | eoan| s390x
   libssl1.1 | 1.1.1c-1ubuntu4  | focal   | s390x 

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 19.10
  Release:  19.10
  Codename: eoan

  11:58:56 AM: $ sudo apt install ./libep11_2.1.0-8_s390x.deb
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Note, selecting 'libep11' instead of './libep11_2.1.0-8_s390x.deb'
  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:
   libep11 : Depends: libssl1.0.0 but it is not installable
  E: Unable to correct problems, you have held broken packages.
  ubuntu@s1lp15:~$ sudo apt install ./libep11-dev_2.1.0-8_s390x.deb 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Note, selecting 'libep11-dev' instead of './libep11-dev_2.1.0-8_s390x.deb'
  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:
   libep11-dev : Depends: libep11 (= 2.1.0-8) but it is not installable
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1850293/+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 1850293] [NEW] libep11 depends on old libssl for disco/eon/focal

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

If using the newest version of libep11_2.1.0-8_s390x.deb with
Disco/Eoan/Focal 
downloaded from 
http://public.dhe.ibm.com/security/cryptocards/pciecc3/EP11/2.1.0/

Following problem occur.:
libep11 : Depends: libssl1.0.0 but it is not installable 

rmadison --arch=s390x libssl1.0.0
 libssl1.0.0 | 1.0.2g-1ubuntu4| xenial  | s390x
 libssl1.0.0 | 1.0.2g-1ubuntu4.15 | xenial-security | s390x
 libssl1.0.0 | 1.0.2g-1ubuntu4.15 | xenial-updates  | s390x
 libssl1.0.0 | 1.0.2n-1ubuntu5| bionic  | s390x
 libssl1.0.0 | 1.0.2n-1ubuntu5.3  | bionic-security | s390x
 libssl1.0.0 | 1.0.2n-1ubuntu5.3  | bionic-updates  | s390x

$ rmadison --arch=s390x libssl1.1
 libssl1.1 | 1.1.0g-2ubuntu4  | bionic  | s390x
 libssl1.1 | 1.1.1-1ubuntu2.1~18.04.4 | bionic-security | s390x
 libssl1.1 | 1.1.1-1ubuntu2.1~18.04.4 | bionic-updates  | s390x
 libssl1.1 | 1.1.1b-1ubuntu2  | disco   | s390x
 libssl1.1 | 1.1.1b-1ubuntu2.4| disco-updates   | s390x
 libssl1.1 | 1.1.1c-1ubuntu4  | eoan| s390x
 libssl1.1 | 1.1.1c-1ubuntu4  | focal   | s390x 

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 19.10
Release:19.10
Codename:   eoan

11:58:56 AM: $ sudo apt install ./libep11_2.1.0-8_s390x.deb
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Note, selecting 'libep11' instead of './libep11_2.1.0-8_s390x.deb'
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:
 libep11 : Depends: libssl1.0.0 but it is not installable
E: Unable to correct problems, you have held broken packages.
ubuntu@s1lp15:~$ sudo apt install ./libep11-dev_2.1.0-8_s390x.deb 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Note, selecting 'libep11-dev' instead of './libep11-dev_2.1.0-8_s390x.deb'
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:
 libep11-dev : Depends: libep11 (= 2.1.0-8) but it is not installable
E: Unable to correct problems, you have held broken packages.

** Affects: ubuntu-z-systems
 Importance: Medium
 Assignee: bugproxy (bugproxy)
 Status: Confirmed

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


** Tags: architecture-s39064 bugnameltc-182119 reverse-proxy-bugzilla 
severity-high targetmilestone-inin1910
-- 
libep11 depends on old libssl for disco/eon/focal
https://bugs.launchpad.net/bugs/1850293
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to openssl 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 1850159] Re: gnome-control-center reports Ethernet Connection Failure while Connection success

[Sebastien Bacher]

unsure where the communication is failing, but could you provide a
screenshot showing the issue? or if not at least state that you
can't/don't want and try to explain better what UI is having the
incorrect status?

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

Title:
  gnome-control-center reports Ethernet Connection Failure while
  Connection success

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  gnome-control-center reports Ethernet Connection Failure with TLS
  Authentication

  1) Ubuntu 19.10
  2) 1:3.34.1-1ubuntu2
  3) Show Connected for Wired Connection
  4) Show Disconnected for Wired Connection

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.34.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 28 17:06:43 2019
  InstallationDate: Installed on 2019-08-01 (88 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to eoan on 2019-10-28 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850159/+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 1850159] Re: gnome-control-center reports Ethernet Connection Failure while Connection success

[Mikhail]

Sorry for wrong package name changed to network-manager

** Package changed: gnome-control-center (Ubuntu) => network-manager
(Ubuntu)

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

Title:
  gnome-control-center reports Ethernet Connection Failure while
  Connection success

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  gnome-control-center reports Ethernet Connection Failure with TLS
  Authentication

  1) Ubuntu 19.10
  2) 1:3.34.1-1ubuntu2
  3) Show Connected for Wired Connection
  4) Show Disconnected for Wired Connection

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.34.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 28 17:06:43 2019
  InstallationDate: Installed on 2019-08-01 (88 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to eoan on 2019-10-28 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850159/+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 1850159] [NEW] gnome-control-center reports Ethernet Connection Failure while Connection success

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

gnome-control-center reports Ethernet Connection Failure with TLS
Authentication

1) Ubuntu 19.10
2) 1:3.34.1-1ubuntu2
3) Show Connected for Wired Connection
4) Show Disconnected for Wired Connection

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-control-center 1:3.34.1-1ubuntu2
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 28 17:06:43 2019
InstallationDate: Installed on 2019-08-01 (88 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to eoan on 2019-10-28 (0 days ago)

** Affects: network-manager (Ubuntu)
 Importance: Low
 Status: Incomplete


** Tags: amd64 apport-bug eoan network
-- 
gnome-control-center reports Ethernet Connection Failure while Connection 
success
https://bugs.launchpad.net/bugs/1850159
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 1849886] Re: lightdm does not work on eoan on raspberry pi 4

[Razor_alpha]

The very same happened to me on 19.10 aarch64 version on my Pi 4 4GB,
changing to gdm3 did result in a usable system for me too.

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

Title:
  lightdm does not work on eoan on raspberry pi 4

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  if you follow the directions on
  https://wiki.ubuntu.com/ARM/RaspberryPi

  sudo apt-get install xubuntu-desktop

  about 20% thru the installation it will ask which window manager you want 
(using dpkg-reconfigure).
  if you select lightdm, you will only get a blank greeter screen after you 
reboot.

  using sudo dpkg-reconfigure gdm3

  resets this to gdm3 and after a reboot, everything is fine.

  this was done on a clean armhf eoan install on a 4gb raspberry pi 4B.

  I have done the install several times.   This bug is repeatable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1849886/+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 1849886] Re: lightdm does not work on eoan on raspberry pi 4

[Launchpad Bug Tracker]

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

** Changed in: software-properties (Ubuntu)
   Status: New => Confirmed

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

Title:
  lightdm does not work on eoan on raspberry pi 4

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  if you follow the directions on
  https://wiki.ubuntu.com/ARM/RaspberryPi

  sudo apt-get install xubuntu-desktop

  about 20% thru the installation it will ask which window manager you want 
(using dpkg-reconfigure).
  if you select lightdm, you will only get a blank greeter screen after you 
reboot.

  using sudo dpkg-reconfigure gdm3

  resets this to gdm3 and after a reboot, everything is fine.

  this was done on a clean armhf eoan install on a 4gb raspberry pi 4B.

  I have done the install several times.   This bug is repeatable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1849886/+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 1638395] Re: Unable to locate remote printer when printing

[jolly stark]

the remote printing is basically a kind of printing which contains a
distant printer. it is used for business purposes mainly while we are
traveling it is an alternative term of fax.it make things easy like we
don't need to carry papers while we are traveling remote printer make
this problem easy for us. but when we can not find this remote printer
then it's a big issue to sort out this problem read this article and do
step by step as instructed here.

www.facebook.com

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

Title:
  Unable to locate remote printer when printing

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  My printer (EPSON Stylus Photo RX520) is connected to a  Yakkety station 
called "paris" which is the printing server. 
  Printing is fine from the server.

  When i configure another Yakkety station to print via this server, the 
printer is detected OK via dnssd, the driver is installed OK. But i can't 
print. 
  I get the following message "Unable to locate printer "paris.local"."

  I used to work on xenial but the connection was through ipps. I tried
  to configure the connection as in xenial, to no avail ...

  What i did: 
  add "192.168.1.4 paris.local" in /etc/hosts
  remove printer from cups, reinstalled it and i finally was able to print on 
the remote printer!

  Don't know if this problem is related to cups or avahi ...

  Ubuntu 16.10
  cups 2.2.0-2

  What i expected to happen: printing successful
  What happened: client cannot locate remote printer, add to add a line in 
/etc/hosts to make it work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1638395/+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 1793410] Re: [Acer Swift SF315-52, Realtek ALC256, Mic, Internal] Internal microphone not working

[serg]

the same issue here with
Swift 314-54

just did the support ticket as well

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

Title:
  [Acer Swift SF315-52, Realtek ALC256, Mic, Internal] Internal
  microphone not working

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Recently bought a new Acer Swift 3 laptop and installed Ubuntu 18.04
  on it. Everything works except the internal microphone. I have also
  tested with an external microphone and this didn't work either.

  I have worked my way through all the suggested solutions I could find,
  including trying to reconfigure the pins using hdajacketask. In
  pavucontrol I have options for Internal Microphone and Microphone
  (unplugged) but the internal mic only captures static noise.

  The latest HD-Audio Codec-Specific Models has configurations for
  alc255-acer and alc256 for some other models, but setting options snd-
  hda-intel model=MODEL in /etc/modprobe.d/alsa-base.conf does not solve
  the issue with any of these.

  Some info -

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-
  LP HD Audio (rev 21)

  
  cat /proc/asound/cards:

   0 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xdf1a8000 irq 127

  
  dmesg | grep snd:

  [3.944593] snd_hda_core: loading out-of-tree module taints kernel.
  [3.956337] snd_soc_skl: Unknown symbol snd_hdac_display_power (err 0)
  [3.956422] snd_soc_skl: Unknown symbol snd_hdac_i915_exit (err 0)
  [4.000880] snd_hda_intel :00:1f.3: Probing card using HDA DKMS, 
version 0.201808050301~ubuntu18.04.1
  [4.000895] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
  [4.013061] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC256: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [4.013063] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [4.013065] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [4.013066] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [4.013066] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [4.013068] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x18
  [4.013069] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x12

  
  info on node 12 from cat /proc/asound/card*/codec\#*:

  Node 0x12 [Pin Complex] wcaps 0x40040b: Stereo Amp-In
Control: name="Internal Mic Boost Volume", index=0, device=0
  ControlAmp: chs=3, dir=In, idx=0, ofs=0
Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
Amp-In vals:  [0x02 0x02]
Pincap 0x0020: IN
Pin Default 0x4000: [N/A] Line Out at Ext N/A
  Conn = Unknown, Color = Unknown
  DefAssociation = 0x0, Sequence = 0x0
Pin-ctls: 0x20: IN
Power states:  D0 D1 D2 D3 EPSS
Power: setting=D0, actual=D0

  Let me know if you need any other information.

  James

  ---

  Tags:  bionic
  Uname: Linux 4.15.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  _MarkForUpload: True
  dmi.bios.date: 06/22/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.04
  dmi.board.asset.tag: Default string
  dmi.board.name: Erdinger_KL
  dmi.board.vendor: KBL
  dmi.board.version: V1.04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.04
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.04:bd06/22/2018:svnAcer:pnSwiftSF315-52:pvrV1.04:rvnKBL:rnErdinger_KL:rvrV1.04:cvnAcer:ct10:cvrV1.04:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF315-52
  dmi.product.version: V1.04
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1793410/+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 1824753] Re: When I pass the Qt application to the secondary monitor the characters of the application increase

[Launchpad Bug Tracker]

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

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Confirmed

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

Title:
  When I pass the Qt application to the secondary monitor the characters
  of the application increase

Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in vlc package in Ubuntu:
  Invalid

Bug description:
  Hi. I have recently installed Ubuntu 19.04 RC. Everything works fine except 
the Qt applications. I have two monitors and when I pass the Qt application to 
the secondary monitor the characters of the application increase. They happen 
to the traditionally installed Qt applications and to those installed with 
Flatpak and Snap. I leave you a video in which you can see the problem with the 
VLC application.
  https://youtu.be/tEZJONsinU4
  https://i.imgur.com/R7GubxF.png?fb
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-14 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.2)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: mutter 3.32.0+git20190410-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6
  Tags:  disco
  Uname: Linux 5.0.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1824753/+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 1849950] Re: Gnome Shell window shortcuts maximize, windowed and hide (Super + Up / Down / H) don't work if upgrading from Unity

[Sebastien Bacher]

Unity and GNOME used to share their schemas so any config change done in
Unity would impact GNOME session, that was fixed in 19.10 and Unity now
has its own schemas. We can't tell appart old configs from Unity from
users who changed their GNOME config so we can't really reset those on
upgrade. Closing as we can't really handle better the upgrade but 19.10
fixes the issue for new installs

** Changed in: gsettings-desktop-schemas (Ubuntu)
   Status: New => Fix Released

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

Title:
  Gnome Shell window shortcuts maximize, windowed and hide (Super + Up /
  Down / H) don't work if upgrading from Unity

Status in GNOME Shell:
  Fix Released
Status in gsettings-desktop-schemas package in Ubuntu:
  Fix Released

Bug description:
  Happens on Ubuntu 19.10, and did also not work on Ubuntu 19.04 (and
  probably also previous versions), if I recall correctly.

  I am not sure, whether this is an upstream bug of GNOME or just Ubuntu
  related.

  Bug report for GNOME: https://gitlab.gnome.org/GNOME/gnome-
  shell/issues/1829

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1849950/+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 1850267] Re: autopkgtest 'nm' fails because it can't find dnsmasq

[Dan Streetman]

** Changed in: network-manager (Ubuntu Bionic)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: network-manager (Ubuntu Bionic)
   Status: New => In Progress

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

Title:
  autopkgtest 'nm' fails because it can't find dnsmasq

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  In Progress

Bug description:
  [impact]

  test 'nm' fails

  [test case]

  see test results
  http://autopkgtest.ubuntu.com/packages/network-manager/bionic/amd64

  [regression potential]

  low, test fix only

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850267/+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 1827644] Re: UPower and battery indicator show wrong information on fully charged ASUS Vivobook X510UR laptop

[Launchpad Bug Tracker]

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

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

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

Title:
  UPower and battery indicator show wrong information on fully charged
  ASUS Vivobook X510UR laptop

Status in upower package in Ubuntu:
  Confirmed

Bug description:
  When the ASUS Vivobook X510UR laptop is completely charged, the
  correct information is displayed on Windows. However, Ubuntu 18.04.2
  LTS is unable to detect the true battery state. The GNOME battery
  indicator usually shows "Estimating..." or "Not charging", when the
  battery is at 100%.

  If you use the upower version 0.99.7-2ubuntu0.18.04.1 command "upower
  -i /org/freedesktop/UPower/devices/battery_BAT0", this is what you
  get:

native-path:  BAT0
vendor:   ASUSTeK
model:ASUS Battery
power supply: yes
updated:  sex 03 mai 2019 14:33:43 -03 (4 seconds ago)
has history:  yes
has statistics:   yes
battery
  present: yes
  rechargeable:yes
  state:   pending-charge
  warning-level:   none
  energy:  39,191 Wh
  energy-empty:0 Wh
  energy-full: 39,26 Wh
  energy-full-design:  42,082 Wh
  energy-rate: 12,453 W
  voltage: 11,52 V
  percentage:  100%
  capacity:93,294%
  technology:  lithium-ion
  icon-name:  'battery-full-charging-symbolic'
History (charge):
  1556904821100,000 discharging
History (rate):
  155690482112,453  discharging
  15569048183,744   discharging

  The "state" should be "fully-charged", but instead it is "pending-
  charge".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: upower 0.99.7-2ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri May  3 14:34:14 2019
  InstallationDate: Installed on 2018-12-11 (142 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1827644/+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 1845797] Re: Microphone not detected Lenovo Yoga S940

[Bug Watch Updater]

Launchpad has imported 6 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=203409.

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 2019-04-24T09:50:09+00:00 drsrsprt wrote:

Created attachment 282497
alsa-info.txt

It seems like this device has 5.1 speaker configuration: Front Left,
Front Center, Front Left and LFE in soundbar placed in hinge; Rear Left
and Rear Right on device bottom. Only Front Left and Front Right
speakers are working (tested with 5.1.0-rc6). Remapping pin 0x17 to Dock
Headphone enables Front Center (or LFE, not sure) speaker and also makes
overall speaker volume higher but headphone jack volume lower so there's
a trade in. Randomly messing with pins in hdaanalyzer wont help. I can
provide any additional logs on request.

Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/1845797/comments/0


On 2019-04-24T09:50:57+00:00 drsrsprt wrote:

Created attachment 282499
`pactl list` output

Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/1845797/comments/1


On 2019-04-24T10:03:12+00:00 drsrsprt wrote:

Created attachment 282501
`fwts --all` results.log

Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/1845797/comments/2


On 2019-05-28T21:48:16+00:00 kxra wrote:

There is also some discussion here about this: https://mailman.alsa-
project.org/pipermail/alsa-devel/2018-November/142369.html

I wasn't able to figure out a suitable workaround for the time being,
but hopefully someone more knowledgeable can.

Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/1845797/comments/3


On 2019-09-07T10:50:53+00:00 mesasec wrote:

Same problem here with that configuration (ALC298 + Dolby
configuration), but with diferrent laptop model, Lenovo S940.

Alsa-info.sh log:

http://alsa-project.org/db/?f=701015751be757989bb93d70a9a06f7e89d64e24

Linux lnx 4.19.66-1-MANJARO #1 SMP PREEMPT Fri Aug 9 18:01:53 UTC 2019
x86_64 GNU/Lin

More logs:

00:1f.3 Multimedia audio controller [0401]: Intel Corporation Cannon Point-LP 
High Definition Audio Controller [8086:9dc8] (rev 30)
card 0: PCH [HDA Intel PCH], device 0: ALC298 Analog [ALC298 Analog]
snd_hda_codec_hdmi 69632  1
snd_sof_intel_hda_common73728  1 sof_pci_dev
snd_sof_intel_hda  20480  1 snd_sof_intel_hda_common
snd_sof   118784  4 
snd_sof_intel_hda_common,snd_sof_intel_byt,snd_sof_intel_ipc,sof_pci_dev
snd_hda_codec_realtek   126976  1
snd_hda_codec_generic94208  1 snd_hda_codec_realtek
snd_soc_hdac_hda   24576  2 snd_sof_intel_hda_common,snd_soc_skl
ledtrig_audio  16384  2 snd_hda_codec_generic,snd_hda_codec_realtek
snd_hda_ext_core   36864  4 
snd_sof_intel_hda_common,snd_soc_hdac_hda,snd_soc_skl,snd_sof_intel_hda
snd_soc_acpi_intel_match28672  3 
snd_sof_intel_hda_common,sof_pci_dev,snd_soc_skl
snd_soc_core  290816  4 
snd_sof,snd_sof_intel_hda_common,snd_soc_hdac_hda,snd_soc_skl
snd_hda_intel  49152  8
snd_hda_codec 159744  5 
snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek,snd_soc_hdac_hda
snd_hda_core  102400  10 
snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_ext_core,snd_hda_codec,snd_hda_codec_realtek,snd_sof_intel_hda_common,snd_soc_hdac_hda,snd_soc_skl,snd_sof_intel_hda
snd_hwdep  20480  1 snd_hda_codec
snd_pcm   139264  11 
snd_hda_codec_hdmi,snd_hda_intel,snd_hda_ext_core,snd_hda_codec,snd_sof,snd_sof_intel_hda_common,snd_soc_core,snd_soc_skl,snd_hda_core,snd_pcm_dmaengine
snd   110592  25 
snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_compress,snd_soc_core,snd_pcm

Any ideas to solve this problem? Regards

Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/1845797/comments/4


On 2019-10-20T20:13:27+00:00 ildella wrote:

Same issue on a Lenovo Yoga S940, kernel 5.3.0-18-generic x86_64
Mic not working
Audio works but clearly not properly, volume is very low and feels like 
low-frequencies are not reproduced, as in "no subwoofer". 

alsa-info -> http://alsa-
project.org/db/?f=c74f7b1c3e266514faac4f90ec2f893a3bec1f98

Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/1845797/comments/23


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

** Changed in: linux
   

[Touch-packages] [Bug 1845797] Re: Microphone not detected Lenovo Yoga S940

[Daniel van Vugt]

Yes, looks like the same audio chip. Same bug.

** Also affects: linux via
   https://bugzilla.kernel.org/show_bug.cgi?id=203409
   Importance: Unknown
   Status: Unknown

** Package changed: pulseaudio (Ubuntu) => alsa-driver (Ubuntu)

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

Title:
  Microphone not detected Lenovo Yoga S940

Status in Linux:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 19.10 as well as 19.04 do not detect the microphone in Lenovo
  Yoga S940

  Attached the screen of gnome sound control panel.

  Inxi output:

  System:Host:  Kernel: 5.3.0-13-generic x86_64 bits: 64 Desktop: 
Gnome 3.34.0 Distro: Ubuntu 19.10 (Eoan Ermine) 
  Machine:   Type: Laptop System: LENOVO product: 81Q7 v: Lenovo Yoga 
S940-14IWL serial:  
 Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN serial:  UEFI: LENOVO v: AKCN34WW date: 06/12/2019 
  CPU:   Topology: Quad Core model: Intel Core i7-8565U bits: 64 type: MT 
MCP L2 cache: 8192 KiB 
 Speed: 1161 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 1161 
2: 1195 3: 1848 4: 976 5: 1041 6: 1209 7: 1061 
 8: 2229 
  Audio: Device-1: Intel Cannon Point-LP High Definition Audio driver: 
snd_hda_intel 
 Sound Server: ALSA v: k5.3.0-13-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  daniele2239 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-09-12 (17 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 81Q7
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-13-generic N/A
   linux-backports-modules-5.3.0-13-generic  N/A
   linux-firmware1.182
  Tags:  eoan
  Uname: Linux 5.3.0-13-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-21 (8 days ago)
  UserGroups: adm cdrom dip docker lpadmin microk8s plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/12/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AKCN34WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga S940-14IWL
  dmi.modalias: 
dmi:bvnLENOVO:bvrAKCN34WW:bd06/12/2019:svnLENOVO:pn81Q7:pvrLenovoYogaS940-14IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS940-14IWL:
  dmi.product.family: Yoga S940-14IWL
  dmi.product.name: 81Q7
  dmi.product.sku: LENOVO_MT_81Q7_BU_idea_FM_Yoga S940-14IWL
  dmi.product.version: Lenovo Yoga S940-14IWL
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1845797/+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 1845797] Re: Microphone not detected Lenovo Yoga S940

[Daniele Dellafiore]

Might be related to this kernel bug ->
https://bugzilla.kernel.org/show_bug.cgi?id=203409=1

** Bug watch added: Linux Kernel Bug Tracker #203409
   https://bugzilla.kernel.org/show_bug.cgi?id=203409

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

Title:
  Microphone not detected Lenovo Yoga S940

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 19.10 as well as 19.04 do not detect the microphone in Lenovo
  Yoga S940

  Attached the screen of gnome sound control panel.

  Inxi output:

  System:Host:  Kernel: 5.3.0-13-generic x86_64 bits: 64 Desktop: 
Gnome 3.34.0 Distro: Ubuntu 19.10 (Eoan Ermine) 
  Machine:   Type: Laptop System: LENOVO product: 81Q7 v: Lenovo Yoga 
S940-14IWL serial:  
 Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN serial:  UEFI: LENOVO v: AKCN34WW date: 06/12/2019 
  CPU:   Topology: Quad Core model: Intel Core i7-8565U bits: 64 type: MT 
MCP L2 cache: 8192 KiB 
 Speed: 1161 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 1161 
2: 1195 3: 1848 4: 976 5: 1041 6: 1209 7: 1061 
 8: 2229 
  Audio: Device-1: Intel Cannon Point-LP High Definition Audio driver: 
snd_hda_intel 
 Sound Server: ALSA v: k5.3.0-13-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  daniele2239 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-09-12 (17 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 81Q7
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-13-generic N/A
   linux-backports-modules-5.3.0-13-generic  N/A
   linux-firmware1.182
  Tags:  eoan
  Uname: Linux 5.3.0-13-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-21 (8 days ago)
  UserGroups: adm cdrom dip docker lpadmin microk8s plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/12/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AKCN34WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga S940-14IWL
  dmi.modalias: 
dmi:bvnLENOVO:bvrAKCN34WW:bd06/12/2019:svnLENOVO:pn81Q7:pvrLenovoYogaS940-14IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS940-14IWL:
  dmi.product.family: Yoga S940-14IWL
  dmi.product.name: 81Q7
  dmi.product.sku: LENOVO_MT_81Q7_BU_idea_FM_Yoga S940-14IWL
  dmi.product.version: Lenovo Yoga S940-14IWL
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845797/+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 1850267] [NEW] autopkgtest 'nm' fails because it can't find dnsmasq

[Dan Streetman]

Public bug reported:

[impact]

test 'nm' fails

[test case]

see test results
http://autopkgtest.ubuntu.com/packages/network-manager/bionic/amd64

[regression potential]

low, test fix only

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

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

** Also affects: network-manager (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: network-manager (Ubuntu Bionic)
   Importance: Undecided => Low

** Changed in: network-manager (Ubuntu)
   Status: New => Fix Released

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

Title:
  autopkgtest 'nm' fails because it can't find dnsmasq

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  New

Bug description:
  [impact]

  test 'nm' fails

  [test case]

  see test results
  http://autopkgtest.ubuntu.com/packages/network-manager/bionic/amd64

  [regression potential]

  low, test fix only

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850267/+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 1691678] Re: Scrollbars escape the bottom and right side of the Terminal window by 1px

[Daniel van Vugt]

Still a problem with upstream Adwaita so it would be nice to find a
universal solution.

** Tags added: desktop-lts-wishlist

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

Title:
  Scrollbars escape the bottom and right side of the Terminal window by
  1px

Status in GNOME Terminal:
  Fix Released
Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed
Status in yaru-theme package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu's orange overlay scrollbars escape the bottom of the window
  during resizing.

  To reproduce try gnome-shell on artful using the Ambiance theme. Open
  a Terminal window and resize it vertically, quickly. Notice the bottom
  of the overlay scrollbar overruns the bottom of the window.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.5-0ubuntu3
  Architecture: amd64
  Date: Thu May 18 15:28:33 2017
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
  InstallationDate: Installed on 2017-05-03 (15 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-terminal/+bug/1691678/+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 1693724] Re: Context menus have no animation/fade-in under Gnome Shell

[Daniel van Vugt]

** Changed in: gnome-shell (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: ubuntu-themes (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Context menus have no animation/fade-in under Gnome Shell

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Won't Fix
Status in gnome-shell package in Arch Linux:
  New

Bug description:
  Context menus have no animation/fade-in under Gnome Shell. The
  transitions under Unity7 for context menus look nicer, less abrupt.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1693724/+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 1790098] Re: vlan created on bond fails auto activation on updating parent network bond

[Frank Heimes]

** Changed in: ubuntu-z-systems
   Status: Won't Fix => Fix Committed

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

Title:
  vlan created on bond fails auto activation on updating parent network
  bond

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Fix Committed

Bug description:
  Auto activation of Vlan created over network-bond fails if bond is 
deactivated and reactivated.
   
  Contact Information = Abhiram Kulkarni(abhir...@in.ibm.com), Mandar 
Deshpande(manda...@in.ibm.com) 
   
  ---uname output---
  Linux S36MANDAR 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:23 UTC 2018 
s390x s390x s390x GNU/Linux
   
  Machine Type = s390x 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Created a network bond with static IP address (and no IPv6 address); 
active backup mode; ARP polling; single slave.

  2. Created a VLAN using said network bond with static IPv4 address
  (and no IPv6 address).

  3. Can ping from the appliance to a target on both links (the parent
  bond and the VLAN).

  4. Switched to another slave for the created bond

  5. Can still ping from the appliance to a target via the parent bond;
  however, cannot ping to the target via the VLAN.

  =
  Detailed steps:

  1. Initial setup:
  
  root@S36MANDAR:~# nmcli c s
  NAMEUUID  TYPE  DEVICE  
  enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093  ethernet  enc1a80 
  enc8f00 2423add6-1464-3765-877c-a214dc497492  ethernet  enc8f00 
  enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605  ethernet  --  

  2. Create Netwrok-bond with one slave:
  
  root@S36MANDAR:~# nmcli c add type bond con-name mybond1 ifname mybond1 
ipv4.method disabled ipv6.method ignore
  Connection 'mybond1' (4b918a65-43a6-4ec3-b3c4-388ed52b116d) successfully 
added.

  root@S36MANDAR:~# nmcli con add type ethernet ifname enc1d40 master mybond1
  Connection 'bond-slave-enc1d40' (cfe4b245-3dda-4f45-b7b4-6d40d144a02f) 
successfully added.
  root@S36MANDAR:~# nmcli con up bond-slave-enc1d40
  Connection successfully activated (D-Bus active path: 
/org/freedesktop/NetworkManager/ActiveConnection/18)
  root@S36MANDAR:~# nmcli c s
  NAMEUUID  TYPE  DEVICE  
  bond-slave-enc1d40  cfe4b245-3dda-4f45-b7b4-6d40d144a02f  ethernet  enc1d40 
  enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093  ethernet  enc1a80 
  enc8f00 2423add6-1464-3765-877c-a214dc497492  ethernet  enc8f00 
  mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d  bond  mybond1 
  enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605  ethernet  --  

  3. Create vlan over mybond1:
  ===
  root@S36MANDAR:~# nmcli con add type vlan con-name vlanbond.100 ifname 
vlanbond.100 dev mybond1 id 100  ipv4.method disabled ipv6.method ignore
  Connection 'vlanbond.100' (e054df42-97a0-492b-b2c9-b9571077493e) successfully 
added.
  root@S36MANDAR:~# nmcli c s
  NAMEUUID  TYPE  DEVICE
   
  bond-slave-enc1d40  cfe4b245-3dda-4f45-b7b4-6d40d144a02f  ethernet  enc1d40   
   
  enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093  ethernet  enc1a80   
   
  enc8f00 2423add6-1464-3765-877c-a214dc497492  ethernet  enc8f00   
   
  mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d  bond  mybond1   
   
  vlanbond.100e054df42-97a0-492b-b2c9-b9571077493e  vlan  
vlanbond.100 
  enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605  ethernet  --
   

  4. Reactivate bond : 
  =
  root@S36MANDAR:~# nmcli con up mybond1
  Connection successfully activated (master waiting for slaves) (D-Bus active 
path: /org/freedesktop/NetworkManager/ActiveConnection/30)

  root@S36MANDAR:~# nmcli c s
  NAMEUUID  TYPE  DEVICE  
  enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093  ethernet  enc1a80 
  enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605  ethernet  enc1d40 
  enc8f00 2423add6-1464-3765-877c-a214dc497492  ethernet  enc8f00 
  mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d  bond  mybond1 
  bond-slave-enc1d40  cfe4b245-3dda-4f45-b7b4-6d40d144a02f  ethernet  --  
  encw18104ddeb38e-d5f7-3814-abb7-be50b8da874e  ethernet  --  
  vlanbond.100e054df42-97a0-492b-b2c9-b9571077493e  vlan  --  

  As is seen, vlan(vlanbond.100) did not get activated

  Now, if manually I make vlan connection up, it gets 

[Touch-packages] [Bug 1825946] Re: 'nm' autopkgtest fails due to GI stderr output

[Dan Streetman]

nm test no longer fails due to stderr output as listed in description.
nm test does now fail due to the test thinking dnsmasq is not available,
but that's a separate bug.

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

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

Title:
  'nm' autopkgtest fails due to GI stderr output

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  New
Status in network-manager source package in Bionic:
  Fix Committed

Bug description:
  [impact]

  'nm' testcase contains:
  from gi.repository import NetworkManager, NMClient, GLib  


 

  which generates output to stderr:
  /tmp/autopkgtest.naU0ts/build.riU/src/debian/tests/nm:23: PyGIWarning: 
NetworkManager was imported without specifying a version first. Use 
gi.require_version('NetworkManager', '1.0') before import to ensure that the 
right version gets loaded.

  the gi.require_version call has already been added to cosmic and
  disco.

  [test case]

  see http://autopkgtest.ubuntu.com/packages/network-manager bionic test
  results.

  [other info]

  this only fails intermittently, but the failure is clearly not an
  actual problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1825946/+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 1790098] Re: vlan created on bond fails auto activation on updating parent network bond

[Dan Streetman]

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

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

Title:
  vlan created on bond fails auto activation on updating parent network
  bond

Status in Ubuntu on IBM z Systems:
  Won't Fix
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Fix Committed

Bug description:
  Auto activation of Vlan created over network-bond fails if bond is 
deactivated and reactivated.
   
  Contact Information = Abhiram Kulkarni(abhir...@in.ibm.com), Mandar 
Deshpande(manda...@in.ibm.com) 
   
  ---uname output---
  Linux S36MANDAR 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:23 UTC 2018 
s390x s390x s390x GNU/Linux
   
  Machine Type = s390x 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Created a network bond with static IP address (and no IPv6 address); 
active backup mode; ARP polling; single slave.

  2. Created a VLAN using said network bond with static IPv4 address
  (and no IPv6 address).

  3. Can ping from the appliance to a target on both links (the parent
  bond and the VLAN).

  4. Switched to another slave for the created bond

  5. Can still ping from the appliance to a target via the parent bond;
  however, cannot ping to the target via the VLAN.

  =
  Detailed steps:

  1. Initial setup:
  
  root@S36MANDAR:~# nmcli c s
  NAMEUUID  TYPE  DEVICE  
  enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093  ethernet  enc1a80 
  enc8f00 2423add6-1464-3765-877c-a214dc497492  ethernet  enc8f00 
  enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605  ethernet  --  

  2. Create Netwrok-bond with one slave:
  
  root@S36MANDAR:~# nmcli c add type bond con-name mybond1 ifname mybond1 
ipv4.method disabled ipv6.method ignore
  Connection 'mybond1' (4b918a65-43a6-4ec3-b3c4-388ed52b116d) successfully 
added.

  root@S36MANDAR:~# nmcli con add type ethernet ifname enc1d40 master mybond1
  Connection 'bond-slave-enc1d40' (cfe4b245-3dda-4f45-b7b4-6d40d144a02f) 
successfully added.
  root@S36MANDAR:~# nmcli con up bond-slave-enc1d40
  Connection successfully activated (D-Bus active path: 
/org/freedesktop/NetworkManager/ActiveConnection/18)
  root@S36MANDAR:~# nmcli c s
  NAMEUUID  TYPE  DEVICE  
  bond-slave-enc1d40  cfe4b245-3dda-4f45-b7b4-6d40d144a02f  ethernet  enc1d40 
  enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093  ethernet  enc1a80 
  enc8f00 2423add6-1464-3765-877c-a214dc497492  ethernet  enc8f00 
  mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d  bond  mybond1 
  enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605  ethernet  --  

  3. Create vlan over mybond1:
  ===
  root@S36MANDAR:~# nmcli con add type vlan con-name vlanbond.100 ifname 
vlanbond.100 dev mybond1 id 100  ipv4.method disabled ipv6.method ignore
  Connection 'vlanbond.100' (e054df42-97a0-492b-b2c9-b9571077493e) successfully 
added.
  root@S36MANDAR:~# nmcli c s
  NAMEUUID  TYPE  DEVICE
   
  bond-slave-enc1d40  cfe4b245-3dda-4f45-b7b4-6d40d144a02f  ethernet  enc1d40   
   
  enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093  ethernet  enc1a80   
   
  enc8f00 2423add6-1464-3765-877c-a214dc497492  ethernet  enc8f00   
   
  mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d  bond  mybond1   
   
  vlanbond.100e054df42-97a0-492b-b2c9-b9571077493e  vlan  
vlanbond.100 
  enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605  ethernet  --
   

  4. Reactivate bond : 
  =
  root@S36MANDAR:~# nmcli con up mybond1
  Connection successfully activated (master waiting for slaves) (D-Bus active 
path: /org/freedesktop/NetworkManager/ActiveConnection/30)

  root@S36MANDAR:~# nmcli c s
  NAMEUUID  TYPE  DEVICE  
  enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093  ethernet  enc1a80 
  enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605  ethernet  enc1d40 
  enc8f00 2423add6-1464-3765-877c-a214dc497492  ethernet  enc8f00 
  mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d  bond  mybond1 
  bond-slave-enc1d40  cfe4b245-3dda-4f45-b7b4-6d40d144a02f  ethernet  --  
  encw18104ddeb38e-d5f7-3814-abb7-be50b8da874e  ethernet  --  
  vlanbond.100e054df42-97a0-492b-b2c9-b9571077493e  vlan  --  

  As is seen, vlan(vlanbond.100) did not get activated

  Now, if 

[Touch-packages] [Bug 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN

[Jean]

Hi Till, I've installed network-manager 1.10.6-2ubuntu1.2 from proposed
as suggested in https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1754671/comments/143 and no, the issue is still there: if I
use the split VPN connection I do not get the DNS under systemd-resolve
--status; if I route all traffic through the VPN instead it works.

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

Title:
  1.10.14-0ubuntu2 breaks DNS propagation from VPN

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I have an OpenVPN connection, and I use the update-systemd-resolved to
  correctly fetch the DNS from the VPN. The issue arose updating my
  Ubuntu 18.04: the script is no longer invoked, and even invoking it
  manually (sudo openvpn myfile.ovpn) does not work anymore, even if in
  that case systemd-resolve --status shows the new DNS on the interface
  correctly.

  As suggested in https://bugs.launchpad.net/ubuntu/+source/network-
  manager/+bug/120/comments/99, reverting to 1.10.6-2ubuntu1.1 fixes
  the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829838/+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 1850258] Re: First breakpoint at AVX instruction with memory operand causes SIGSEGV when tring to continue execution

[Pauli]

Actually it seems like it is more restricted towards a few instructions
with memory operand. But if breakpoint is set to them at any point of
execution they crash.

That means also breakpoint before and single stepping to problematic
breakpoint will crash application. But single stepping over problematic
instruction without breakpoint doesn't crash. That was adding to my
earlier confusion why application crashes looked so random.

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

Title:
  First breakpoint at AVX instruction with memory operand causes SIGSEGV
  when tring to continue execution

Status in gdb package in Ubuntu:
  New

Bug description:
  I noticed random looking SIGSEGV to application when trying to
  continue execution after first breakpoint. I now seem to have narrowed
  the issue to SIMD instruction with memory operand as first breakpoint
  location. I haven't managed to figure out why the SIGSEGV is delivered
  to the debugger application.

  It is important have first breakpoint exactly at a problematic
  instructions. If I first break on a different instruction then later
  breakpoints won't reproduce that crash

  I haven't tested if this is a hardware specific issue.

  I managed to write a simple test case which reproduces the crash if
  breakpoint is set. I attached the test.cc which includes compilation
  and testing instructions. test.cc is supposed to generate a simple
  main function like:

  Dump of assembler code for function main():
  => 0x4520 <+0>:   vmovdqa 0x1af8(%rip),%xmm0# 
0x6020 
     0x4528 <+8>:   vmovd  %xmm0,%eax
     0x452c <+12>:  retq

  I set breakpoint with:
  b main

  Then either continue or stepping causes SIGSEGV to the debugged
  application.

  This was happening already with disco. I only now figured out enough
  details to make a simple test case which is worth a bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gdb 8.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Oct 29 09:44:52 2019
  InstallationDate: Installed on 2037-12-25 (-6632 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gdb
  UpgradeStatus: Upgraded to eoan on 2019-10-27 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1850258/+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 1790098] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From abhir...@in.ibm.com 2019-10-29 03:59 EDT---
Tested below scenario:

1)Create a bond network device
2)Create a vlan on top of above bond network device
3)Deactivate the bond
4)VLAN DEVICE ALSO GOES INTO DEACTIVATED state automatically
5)Activate bond
6)With the fix in, VLAN ALSO NOW GETS ACTIVATED AUTOMATICALLY

This defect fix is verified

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

Title:
  vlan created on bond fails auto activation on updating parent network
  bond

Status in Ubuntu on IBM z Systems:
  Won't Fix
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Fix Committed

Bug description:
  Auto activation of Vlan created over network-bond fails if bond is 
deactivated and reactivated.
   
  Contact Information = Abhiram Kulkarni(abhir...@in.ibm.com), Mandar 
Deshpande(manda...@in.ibm.com) 
   
  ---uname output---
  Linux S36MANDAR 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:23 UTC 2018 
s390x s390x s390x GNU/Linux
   
  Machine Type = s390x 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Created a network bond with static IP address (and no IPv6 address); 
active backup mode; ARP polling; single slave.

  2. Created a VLAN using said network bond with static IPv4 address
  (and no IPv6 address).

  3. Can ping from the appliance to a target on both links (the parent
  bond and the VLAN).

  4. Switched to another slave for the created bond

  5. Can still ping from the appliance to a target via the parent bond;
  however, cannot ping to the target via the VLAN.

  =
  Detailed steps:

  1. Initial setup:
  
  root@S36MANDAR:~# nmcli c s
  NAMEUUID  TYPE  DEVICE  
  enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093  ethernet  enc1a80 
  enc8f00 2423add6-1464-3765-877c-a214dc497492  ethernet  enc8f00 
  enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605  ethernet  --  

  2. Create Netwrok-bond with one slave:
  
  root@S36MANDAR:~# nmcli c add type bond con-name mybond1 ifname mybond1 
ipv4.method disabled ipv6.method ignore
  Connection 'mybond1' (4b918a65-43a6-4ec3-b3c4-388ed52b116d) successfully 
added.

  root@S36MANDAR:~# nmcli con add type ethernet ifname enc1d40 master mybond1
  Connection 'bond-slave-enc1d40' (cfe4b245-3dda-4f45-b7b4-6d40d144a02f) 
successfully added.
  root@S36MANDAR:~# nmcli con up bond-slave-enc1d40
  Connection successfully activated (D-Bus active path: 
/org/freedesktop/NetworkManager/ActiveConnection/18)
  root@S36MANDAR:~# nmcli c s
  NAMEUUID  TYPE  DEVICE  
  bond-slave-enc1d40  cfe4b245-3dda-4f45-b7b4-6d40d144a02f  ethernet  enc1d40 
  enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093  ethernet  enc1a80 
  enc8f00 2423add6-1464-3765-877c-a214dc497492  ethernet  enc8f00 
  mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d  bond  mybond1 
  enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605  ethernet  --  

  3. Create vlan over mybond1:
  ===
  root@S36MANDAR:~# nmcli con add type vlan con-name vlanbond.100 ifname 
vlanbond.100 dev mybond1 id 100  ipv4.method disabled ipv6.method ignore
  Connection 'vlanbond.100' (e054df42-97a0-492b-b2c9-b9571077493e) successfully 
added.
  root@S36MANDAR:~# nmcli c s
  NAMEUUID  TYPE  DEVICE
   
  bond-slave-enc1d40  cfe4b245-3dda-4f45-b7b4-6d40d144a02f  ethernet  enc1d40   
   
  enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093  ethernet  enc1a80   
   
  enc8f00 2423add6-1464-3765-877c-a214dc497492  ethernet  enc8f00   
   
  mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d  bond  mybond1   
   
  vlanbond.100e054df42-97a0-492b-b2c9-b9571077493e  vlan  
vlanbond.100 
  enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605  ethernet  --
   

  4. Reactivate bond : 
  =
  root@S36MANDAR:~# nmcli con up mybond1
  Connection successfully activated (master waiting for slaves) (D-Bus active 
path: /org/freedesktop/NetworkManager/ActiveConnection/30)

  root@S36MANDAR:~# nmcli c s
  NAMEUUID  TYPE  DEVICE  
  enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093  ethernet  enc1a80 
  enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605  ethernet  enc1d40 
  enc8f00 2423add6-1464-3765-877c-a214dc497492  ethernet  enc8f00 
  mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d  bond  mybond1 
  bond-slave-enc1d40  cfe4b245-3dda-4f45-b7b4-6d40d144a02f  

[Touch-packages] [Bug 1850258] [NEW] First breakpoint at AVX instruction with memory operand causes SIGSEGV when tring to continue execution

[Pauli]

Public bug reported:

I noticed random looking SIGSEGV to application when trying to continue
execution after first breakpoint. I now seem to have narrowed the issue
to SIMD instruction with memory operand as first breakpoint location. I
haven't managed to figure out why the SIGSEGV is delivered to the
debugger application.

It is important have first breakpoint exactly at a problematic
instructions. If I first break on a different instruction then later
breakpoints won't reproduce that crash

I haven't tested if this is a hardware specific issue.

I managed to write a simple test case which reproduces the crash if
breakpoint is set. I attached the test.cc which includes compilation and
testing instructions. test.cc is supposed to generate a simple main
function like:

Dump of assembler code for function main():
=> 0x4520 <+0>: vmovdqa 0x1af8(%rip),%xmm0# 
0x6020 
   0x4528 <+8>: vmovd  %xmm0,%eax
   0x452c <+12>:retq

I set breakpoint with:
b main

Then either continue or stepping causes SIGSEGV to the debugged
application.

This was happening already with disco. I only now figured out enough
details to make a simple test case which is worth a bug report.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gdb 8.3-0ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Oct 29 09:44:52 2019
InstallationDate: Installed on 2037-12-25 (-6632 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: gdb
UpgradeStatus: Upgraded to eoan on 2019-10-27 (1 days ago)

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


** Tags: amd64 apport-bug eoan

** Attachment added: "A simple test case which crashes if first breakpoint is 
in main"
   https://bugs.launchpad.net/bugs/1850258/+attachment/5301095/+files/test.cc

** Description changed:

  I noticed random looking SIGSEGV to application when trying to continue
  execution after first breakpoint. I now seem to have narrowed the issue
  to SIMD instruction with memory operand as first breakpoint location. I
  haven't managed to figure out why the SIGSEGV is delivered to the
  debugger application.
  
  It is important have first breakpoint exactly at a problematic
  instructions. If I first break on a different instruction then later
  breakpoints won't reproduce that crash
  
  I haven't tested if this is a hardware specific issue.
  
  I managed to write a simple test case which reproduces the crash if
  breakpoint is set. I attached the test.cc which includes compilation and
  testing instructions. test.cc is supposed to generate a simple main
  function like:
  
  Dump of assembler code for function main():
  => 0x4520 <+0>:   vmovdqa 0x1af8(%rip),%xmm0# 
0x6020 
-0x4528 <+8>:   vmovd  %xmm0,%eax
-0x452c <+12>:  retq   
+    0x4528 <+8>:   vmovd  %xmm0,%eax
+    0x452c <+12>:  retq
  
  I set breakpoint with:
  b main
  
  Then either continue or stepping causes SIGSEGV to the debugged
  application.
+ 
+ This was happening already with disco. I only now figured out enough
+ details to make a simple test case which is worth a bug report.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gdb 8.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Oct 29 09:44:52 2019
  InstallationDate: Installed on 2037-12-25 (-6632 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gdb
  UpgradeStatus: Upgraded to eoan on 2019-10-27 (1 days ago)

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

Title:
  First breakpoint at AVX instruction with memory operand causes SIGSEGV
  when tring to continue execution

Status in gdb package in Ubuntu:
  New

Bug description:
  I noticed random looking SIGSEGV to application when trying to
  continue execution after first breakpoint. I now seem to have narrowed
  the issue to SIMD instruction with memory operand as first breakpoint
  location. I haven't managed to figure out why the SIGSEGV is delivered
  to the debugger application.

  It is important have first breakpoint exactly at a problematic
  instructions. If I first break on a different instruction then later
  breakpoints won't reproduce that crash

  I haven't tested if this is a hardware specific issue.

  I managed to write a simple test case which reproduces the crash if
  breakpoint is set. I attached