[Touch-packages] [Bug 1846148] Re: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019

[Hui Wang]

please install this dkms " sudo dpkg -i oem-audio-xxx.deb" and reboot

please check if there is internal mic now (through gnome-control-center
sound), and if we can record sound through internal mic.

if it doesn't work, please upload the alsa-info.txt after applying this
deb.


** Attachment added: "oem-audio-hda-daily-dkms_0.1_all.deb"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+attachment/5298073/+files/oem-audio-hda-daily-dkms_0.1_all.deb

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

Title:
  Realtek ALC256M with DTS Audio Processing internal microphone doesn't
  work on Redmi Book 14 2019

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sound works okay but the internal mic doesn't work.
  When I plug in headset, the mic on headset also doens't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lilian 1689 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  1 12:27:10 2019
  InstallationDate: Installed on 2019-09-21 (9 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2019
  dmi.bios.vendor: TIMI
  dmi.bios.version: RMRCM400P0100
  dmi.board.name: TM1901
  dmi.board.vendor: TIMI
  dmi.chassis.type: 10
  dmi.chassis.vendor: TIMI
  dmi.modalias: 
dmi:bvnTIMI:bvrRMRCM400P0100:bd08/19/2019:svnTIMI:pnRedmiBook14:pvr:rvnTIMI:rnTM1901:rvr:cvnTIMI:ct10:cvr:
  dmi.product.family: Mi Laptop
  dmi.product.name: RedmiBook 14
  dmi.product.sku: TM1901-24822
  dmi.sys.vendor: TIMI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+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 1848627] [NEW] bash root autocomplete disabled on upgrade

[NBR]

Public bug reported:

In 19.04 I could type apt upd or apt fu and autocomplete would
work. It doesn't work in 19.10 as root (though it does as my normal
user). I fixed the issue by uncommenting the last lines of /root/.bashrc
but I don't understand why you'd break root user autocomplete by
default.

This is in an upgrade scenario from 19.04, I don't know if it's
similarly broken in a clean install.

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


** Tags: bash

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

Title:
  bash root autocomplete disabled on upgrade

Status in bash package in Ubuntu:
  New

Bug description:
  In 19.04 I could type apt upd or apt fu and autocomplete
  would work. It doesn't work in 19.10 as root (though it does as my
  normal user). I fixed the issue by uncommenting the last lines of
  /root/.bashrc but I don't understand why you'd break root user
  autocomplete by default.

  This is in an upgrade scenario from 19.04, I don't know if it's
  similarly broken in a clean install.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1848627/+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 1848626] [NEW] When seeking in VLC playing most videos, sound is choppy for 9s after seek.

[NBR]

Public bug reported:

System was working fine in Ubuntu 19.04. After update to 19.10 and
reboot, videos have audio problems after seeking. The majority of videos
I tested had trouble, but the severity of the problem varies even in the
problem videos. The sound cuts in and out inconsistently, as if some
software is having trouble filling the audio buffer in time.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  x  1708 F pulseaudio
 /dev/snd/controlC0:  x  1708 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 17 21:07:33 2019
InstallationDate: Installed on 2018-12-09 (313 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic successful
Symptom_Card: Family 17h (Models 00h-0fh) HD Audio Controller - HD-Audio Generic
Symptom_Jack: Black SPDIF Out, Rear
Symptom_PulsePlaybackTest: PulseAudio playback test failed
Symptom_Type: None of the above
Title: [To Be Filled By O.E.M., Realtek ALC1220, Black SPDIF Out, Rear] 
Playback problem
UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago)
dmi.bios.date: 04/01/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P3.20
dmi.board.name: B450 Gaming-ITX/ac
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.20:bd04/01/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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


** Tags: amd64 apport-bug eoan vlc wayland-session

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

Title:
  When seeking in VLC playing most videos, sound is choppy for 9s after
  seek.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  System was working fine in Ubuntu 19.04. After update to 19.10 and
  reboot, videos have audio problems after seeking. The majority of
  videos I tested had trouble, but the severity of the problem varies
  even in the problem videos. The sound cuts in and out inconsistently,
  as if some software is having trouble filling the audio buffer in
  time.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  x  1708 F pulseaudio
   /dev/snd/controlC0:  x  1708 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 21:07:33 2019
  InstallationDate: Installed on 2018-12-09 (313 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic successful
  Symptom_Card: Family 17h (Models 00h-0fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_Jack: Black SPDIF Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: None of the above
  Title: [To Be Filled By O.E.M., Realtek ALC1220, Black SPDIF Out, Rear] 
Playback problem
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago)
  dmi.bios.date: 04/01/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.20
  dmi.board.name: B450 Gaming-ITX/ac
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.20:bd04/01/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To 

[Touch-packages] [Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)

[Jim Hobbs]

I found this thread via Google, trying to fix the Bluetooth pairing of
my Bose QC35 (version 1) running Ubuntu 16.0.4.6 on a ThinkPad X230.
Whilst trying out a few things I managed to solve my problem by
temporarily disabling my VPN. Might have been a random coincidence but I
wanted to leave this here in case it helped others. Worth a try anyway
:)

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

Title:
  pulseaudio crashes when connecting to bluetooth headphones (due to
  ubuntu changes?)

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Released
Status in pulseaudio source package in Yakkety:
  Fix Released

Bug description:
  Impact:

  A patch we carry for Ubuntu touch introduced a change that originally
  was required to make sure PulseAudio did not crash. This patch was
  ported to PulseAudio 8 in Xenial, but the patch author's bluetooth
  hardware that was to hand at the time worked so was assumed to be ok.
  However, the opposite is now happening, i.e PulseAudio is crashing
  with a subset of Bluetooth hardware.

  Regression potential:

  Very low to none. As can be read in this report, much debugging and
  testing has been done to find the problem, and the eventual fix.
  Moreover the change is the removal of a patch hunk that removed a line
  of code originally present in PulseAudio.

  Test case:

  NOTE that this test case applies to bluetooth hardware that is
  identified as not working in this bug report.

  1. Install, or upgrade to Xenial or yakkety.
  2. Pair your bluetooth device in the bluetooth settings in the relevant 
settings application for your desktop environment.
  3. Once paired, you will notice that sound stops working, as pulseaudio has 
thrown an assertion error.
  4. You do not have to remove your audio device from the paired device list, 
but it may be easier to do so for the next part of the testing.
  5. Update to the version of PulseAudio in xenial-proposed which is 
1:8.0-0ubuntu3.1, or in yakkety-proposed, which is 1:9.0-2ubuntu2.1.
  6. Re-pair your device. Audio should continue to work, and you should be able 
to switch to your bluetooth device and use it.

  
  Original bug report:

  When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04
  pulseaudio crashes, this does *NOT* happen with a Jambox which leads
  me to believe it's an intermittent problem with some hardware. This
  did not happen on Ubuntu 15.10 (which was an upgrade of 15.04).

  Ubuntu Release:

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Pulseaudio Version:

  pulseaudio:
    Installed: 1:8.0-0ubuntu3
    Candidate: 1:8.0-0ubuntu3
    Version table:
   *** 1:8.0-0ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  Device info:

  [bluetooth]# info 44:5E:F3:B4:07:29
  Device 44:5E:F3:B4:07:29
   Name: BlueBuds X
   Alias: BlueBuds X
   Class: 0x240404
   Icon: audio-card
   Paired: yes
   Trusted: yes
   Blocked: no
   Connected: no
   LegacyPairing: no
   UUID: Headset   (1108--1000-8000-00805f9b34fb)
   UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
   UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
   UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
   UUID: Handsfree (111e--1000-8000-00805f9b34fb)
   UUID: Unknown   (80ff--1000-8000-00805f9b34fb)

  I have also attached a debug dump of Pulseaudio when attempting to
  connect to the headphones.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324/+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 1848623] Re: package systemd 237-3ubuntu10.31 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1

[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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1848623

Title:
  package systemd 237-3ubuntu10.31 failed to install/upgrade: installed
  systemd package post-installation script subprocess returned error
  exit status 1

Status in systemd package in Ubuntu:
  New

Bug description:
  This error appeared during release upgrade from 17.10.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.31
  ProcVersionSignature: Ubuntu 4.13.0-46.51-generic 4.13.16
  Uname: Linux 4.13.0-46-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.9
  Architecture: amd64
  Date: Fri Oct 18 06:15:02 2019
  ErrorMessage: installed systemd package post-installation script subprocess 
returned error exit status 1
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: DigitalOcean Droplet
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-46-generic 
root=UUID=a1c86501-45f5-4b0f-a356-9421fe46b341 ro console=tty1 console=ttyS0
  Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.3
   apt  1.6.12
  SourcePackage: systemd
  Title: package systemd 237-3ubuntu10.31 failed to install/upgrade: installed 
systemd package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to bionic on 2019-10-18 (0 days ago)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: DigitalOcean
  dmi.bios.version: 20171212
  dmi.chassis.type: 1
  dmi.chassis.vendor: Bochs
  dmi.modalias: 
dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr:
  dmi.product.family: DigitalOcean_Droplet
  dmi.product.name: Droplet
  dmi.product.version: 20171212
  dmi.sys.vendor: DigitalOcean

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1848623/+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 1848623] [NEW] package systemd 237-3ubuntu10.31 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1

[Ayman Ahmed]

Public bug reported:

This error appeared during release upgrade from 17.10.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu10.31
ProcVersionSignature: Ubuntu 4.13.0-46.51-generic 4.13.16
Uname: Linux 4.13.0-46-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.9
Architecture: amd64
Date: Fri Oct 18 06:15:02 2019
ErrorMessage: installed systemd package post-installation script subprocess 
returned error exit status 1
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: DigitalOcean Droplet
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-46-generic 
root=UUID=a1c86501-45f5-4b0f-a356-9421fe46b341 ro console=tty1 console=ttyS0
Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.3
 apt  1.6.12
SourcePackage: systemd
Title: package systemd 237-3ubuntu10.31 failed to install/upgrade: installed 
systemd package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to bionic on 2019-10-18 (0 days ago)
dmi.bios.date: 12/12/2017
dmi.bios.vendor: DigitalOcean
dmi.bios.version: 20171212
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias: 
dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr:
dmi.product.family: DigitalOcean_Droplet
dmi.product.name: Droplet
dmi.product.version: 20171212
dmi.sys.vendor: DigitalOcean

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


** Tags: amd64 apport-package bionic need-duplicate-check third-party-packages 
uec-images

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

Title:
  package systemd 237-3ubuntu10.31 failed to install/upgrade: installed
  systemd package post-installation script subprocess returned error
  exit status 1

Status in systemd package in Ubuntu:
  New

Bug description:
  This error appeared during release upgrade from 17.10.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.31
  ProcVersionSignature: Ubuntu 4.13.0-46.51-generic 4.13.16
  Uname: Linux 4.13.0-46-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.9
  Architecture: amd64
  Date: Fri Oct 18 06:15:02 2019
  ErrorMessage: installed systemd package post-installation script subprocess 
returned error exit status 1
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: DigitalOcean Droplet
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-46-generic 
root=UUID=a1c86501-45f5-4b0f-a356-9421fe46b341 ro console=tty1 console=ttyS0
  Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.3
   apt  1.6.12
  SourcePackage: systemd
  Title: package systemd 237-3ubuntu10.31 failed to install/upgrade: installed 
systemd package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to bionic on 2019-10-18 (0 days ago)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: DigitalOcean
  dmi.bios.version: 20171212
  dmi.chassis.type: 1
  dmi.chassis.vendor: Bochs
  dmi.modalias: 
dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr:
  dmi.product.family: DigitalOcean_Droplet
  dmi.product.name: Droplet
  dmi.product.version: 20171212
  dmi.sys.vendor: DigitalOcean

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1848623/+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 1848534] Re: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts

[Daniel van Vugt]

Please run this command:

  lspci -k > lspcik.txt

and then send us the file 'lspcik.txt'.

Please also attach the log files /var/log/Xorg*.log

** Summary changed:

- System shows graphic artifacts for a moment, then text cursor for about 
minute and then starts
+ [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then 
text cursor for about minute and then starts

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

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

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

Title:
  [Microsoft Hyper-V guest] System shows graphic artifacts for a moment,
  then text cursor for about minute and then starts

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  AFter upgrade system shows graphic artefacts for a moment and then
  text cursor for about minute (it looks like hanged) and then starts.

  In 19.04 startup required 1 or 2 seconds.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 17:42:27 2019
  InstallationDate: Installed on 2019-07-04 (104 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago)
  VarLogDistupgradeLspcitxt:
   
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1848534/+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 1181106] Re: Failed to change profile to A2DP

[Daniel van Vugt]

** Tags added: bionic

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

Title:
  Failed to change profile to A2DP

Status in Bluez Utilities:
  New
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio package in Debian:
  Fix Released

Bug description:
  I upgraded to 13.04 recently and my A2DP profile, which had been
  working great under 12.10 is suddenly gone.  Neither my blueman applet
  nor the built-in bluetooth manager applet can connect my external
  bluetooth speaker to the A2DP profile.  They can connect to the
  bluetooth device itself just fine.

  Steps I'm using:

  * using blueman, I can connect to the external bluetooth speaker and view the 
device in the devices listing
  * I can connect the device to the Audio sink and I get a message saying it is 
now connected and will "show in the PulseAudio mixer"
  * After connecting the external speaker to the audio sink, I can also see the 
device in the "Play sound through" listing in the Sound system control panel, 
but the icon has a circle with a line through it.
  * but if I right-click the device and choose "Audio Profile" from the context 
menu and try to select "High Fidelity Playback (A2DP)" as the new profile, I 
get an error message stating "failed to change profile to a2dp"

  I've already added "Enable=Socket" in /etc/bluetooth/audio.conf,
  without that I can't pair my headset. Now I can pair it, but I can't
  activate the A2DP profile.

  When I try to activate it, I see this message in my syslog :
  pulseaudio[2603]: [pulseaudio] module-bluetooth-device.c: Profile has no 
transport

  I tried the kernel 3.9.0 because of a sound problem with my soundcard,
  this kernel fixed my soundcard problem, but A2DP still doesn't work

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1181106/+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 1848616] [NEW] LightDM crashes and logs me out when resuming from suspend

[Douglas Silva]

Public bug reported:

I close the laptop lid and let it suspend. On resume, the whole desktop
is frozen for a while. Nothing works during this time, no CAPS LOCK
indicator LED, neither TTY switching. Then the screen goes dark and I
see the LightDM login screen. I was logged out.

This is a regression, since it wasn't reproducible on Ubuntu 19.04.

How reproducible?
100% of the time.

I am not totally sure it was LightDM's fault. It is my best guess based
on the behavior I witnessed.

See logs.

Potentially relevant specs:
- Intel HD Graphics 400 (Braswell)

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: lightdm 1.30.0-0ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Oct 17 21:52:19 2019
InstallationDate: Installed on 2019-10-17 (0 days ago)
InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug eoan

** Attachment added: "Journalctl output from right after the problem"
   
https://bugs.launchpad.net/bugs/1848616/+attachment/5298012/+files/journalctl.txt

** Description changed:

  I close the laptop lid and let it suspend. On resume, the whole desktop
  is frozen for a while. Nothing works during this time, no CAPS LOCK
  indicator LED, neither TTY switching. Then the screen goes dark and I
  see the LightDM login screen. I was logged out.
  
  This is a regression, since it wasn't reproducible on Ubuntu 19.04.
+ 
+ How reproducible?
+ 100% of the time.
  
  I am not totally sure it was LightDM's fault. It is my best guess based
  on the behavior I witnessed.
  
  See logs.
  
  Potentially relevant specs:
  - Intel HD Graphics 400 (Braswell)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: lightdm 1.30.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Oct 17 21:52:19 2019
  InstallationDate: Installed on 2019-10-17 (0 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  LightDM crashes and logs me out when resuming from suspend

Status in lightdm package in Ubuntu:
  New

Bug description:
  I close the laptop lid and let it suspend. On resume, the whole
  desktop is frozen for a while. Nothing works during this time, no CAPS
  LOCK indicator LED, neither TTY switching. Then the screen goes dark
  and I see the LightDM login screen. I was logged out.

  This is a regression, since it wasn't reproducible on Ubuntu 19.04.

  How reproducible?
  100% of the time.

  I am not totally sure it was LightDM's fault. It is my best guess
  based on the behavior I witnessed.

  See logs.

  Potentially relevant specs:
  - Intel HD Graphics 400 (Braswell)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: lightdm 1.30.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Oct 17 21:52:19 2019
  InstallationDate: Installed on 2019-10-17 (0 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1848616/+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 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

[Mathew Hodson]

** No longer affects: cairo (Ubuntu)

** Project changed: cairo => ubuntu-translations

** No longer affects: ubuntu-translations

** Tags removed: verification-needed

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

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

Status in OEM Priority Project:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubiquity source package in Bionic:
  Fix Released

Bug description:
  * Impact
  The Ubuntu installer crashes on some machines (seems more often on hiDPI 
machines (QHD/UHD etc)).

  * Test case
  Try installing Ubuntu on an hidpi machine, it should complete installation 
instead of crashing.

  * Regression potential
  The fix in ubiquity touches the code handle uid drop/privilege, that can have 
unexpected side effects so we need proper/complete testing of the installer

  --

  Update: Actually the crash occurs on slow-ish systems due to a race
  condition. It's not strictly only hi-DPI machines - that's just the
  most common place it is experienced.

  ---

  https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
  https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
  https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
  https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
  https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524

  ---

  WORKAROUND:

  1. Boot into the live session.
  2. Settings > Devices > Displays > Scale = 100%
  3. Click Apply.
  4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".

  ---

  Crashed in a VM in the middle of installation. The host is Bionic up
  to date.

  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 135, in run
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 505, in copy_all
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + 
copy_progress)
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: 
self.command(command, *args, **kw))
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
  Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
  Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for 
int() with base 10: ''

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  Date: Fri Feb 23 12:52:28 2018
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  InterpreterPath: /usr/bin/python3.6
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  Signal: 5
  SourcePackage: ubiquity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: ubiquity crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1751252/+subscriptions

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

[Touch-packages] [Bug 1427264] Re: using ecryptfs, creating frameworks fail to bind mount issues

[Mathew Hodson]

This was fixed in package schroot 1.6.10-3 available in Ubuntu Artful
and later.

** No longer affects: click (Ubuntu)

** Also affects: schroot (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: schroot (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Changed in: schroot (Ubuntu Trusty)
   Status: New => Won't Fix

** Changed in: schroot (Ubuntu Vivid)
   Status: New => Won't Fix

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

** Tags removed: verification-needed

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

Title:
  using ecryptfs, creating frameworks fail to bind mount issues

Status in schroot package in Ubuntu:
  Fix Released
Status in schroot source package in Trusty:
  Won't Fix
Status in schroot source package in Vivid:
  Won't Fix
Status in schroot package in Debian:
  Fix Released

Bug description:
  Using vivid creating framework fails for ecryptfs users, the issue is
  similar to bug #769595

  The userdir is mounted in a way which makes unmounts fail

  "E: 10mount: umount: /var/lib/schroot/mount/click-ubuntu-sdk-14.10
  -armhf-ec6aaf62-31e0-47e9-b2f8-73f0b038fb4d/home/user: target is busy
  E: 10mount: (In some cases useful info about processes that E:
  10mount: use the device is found by lsof(8) or fuser(1).) "

  changing the fstab line to be "/home/user /home/user  none
  rw,bind0   0" workarounds the issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/schroot/+bug/1427264/+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 1848200] Re: gdb not stopping on breakpoint in a 32-bit program

[Chistian Gagneraud]

We have this problem, here at work. This affect all developpers that
keep their system up do date (18.04). We currently hold to the previous
version.

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

Title:
  gdb not stopping on breakpoint in a 32-bit program

Status in gdb package in Ubuntu:
  Confirmed

Bug description:
  After upgrading gdb from 8.1-0ubuntu3 to 8.1-0ubuntu3.1, gdb does not
  stop on breakpoint when running a 32-bit application (on 64-bit
  Ubuntu). This can be reproduced with a simple “hello world” program:

  $ cat hello.c 
  #include 
  int main()
  {
 // printf() displays the string inside quotation
 printf("Hello, World!");
 return 0;
  }
  $ gcc -ggdb -m32 hello.c
  $ gdb a.out
  (gdb) b hello.c:5
  Breakpoint 1 at 0x536: file hello.c, line 5.
  (gdb) run
  Starting program: /home/user/sandbox/a.out 
  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.

  --- (and not stopping nor outputting the text…) ---

  It works well with a 64-bit build (leaving out the gcc’s -m32 option).

  This problem has been already discussed on:
  https://stackoverflow.com/questions/58225562/how-to-fix-hang-in-gdb-
  in-ld-linux-so-2-when-running-a-32-bit-executable-on-a-64

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdb 8.1-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
  Uname: Linux 4.15.0-65-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Oct 15 14:37:37 2019
  InstallationDate: Installed on 2015-12-08 (1407 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  SourcePackage: gdb
  UpgradeStatus: Upgraded to bionic on 2019-06-10 (127 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1848200/+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 1835738] Re: SRU: Update Python interpreter to 3.6.9 and 3.7.5

[Mathew Hodson]

** No longer affects: python3.6 (Ubuntu)

** No longer affects: python3.6 (Ubuntu Disco)

** No longer affects: python3.6 (Ubuntu Eoan)

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

Title:
  SRU: Update Python interpreter to 3.6.9 and 3.7.5

Status in python3-defaults package in Ubuntu:
  New
Status in python3-stdlib-extensions package in Ubuntu:
  Fix Committed
Status in python3.7 package in Ubuntu:
  Fix Committed
Status in python3-defaults source package in Bionic:
  New
Status in python3-stdlib-extensions source package in Bionic:
  New
Status in python3.6 source package in Bionic:
  New
Status in python3.7 source package in Bionic:
  New
Status in python3-defaults source package in Disco:
  New
Status in python3-stdlib-extensions source package in Disco:
  New
Status in python3.7 source package in Disco:
  New
Status in python3-defaults source package in Eoan:
  New
Status in python3-stdlib-extensions source package in Eoan:
  Fix Committed
Status in python3.7 source package in Eoan:
  Fix Committed

Bug description:
  Update Python interpreter to 3.6.9 and 3.7.5.  As done with earlier
  subminor upstream releases (LP: #1822993).

  SRU: update Python 3.7 to the 3.7.5 release, update Python 3.6 to the
  3.6.9 release.

  python3-stdlib-extensions also updates the modules to the 3.6.9
  release for Python 3.6.

  Acceptance Criteria: The package builds, and the test suite doesn't
  show regressions. The test suite passes in the autopkg tests. The new
  packages don't cause regressions in a test rebuild of the main
  component.

  TODO: update after test rebuild
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-cosmic.html
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-gcc8-cosmic.html

  The test rebuilds are finished, and don't show any regressions for the
  main component.

  Regression Potential: Python 3.7 isn't used by default, so we don't have many 
default users.
  Regression Potential: Python 3.6 could see some regressions, although we are 
trying to minimize the risk by doing the test rebuild.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1835738/+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 1848587] [NEW] lxc 3.0.4-0ubuntu1 ADT test failure with linux 5.4.0-1.2

[Seth Forshee]

Public bug reported:

Testing failed on:
amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/amd64/l/lxc/20191016_150939_0f81d@/log.gz
arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/arm64/l/lxc/20191016_152027_0f81d@/log.gz
ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/ppc64el/l/lxc/20191016_150251_0f81d@/log.gz
s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/s390x/l/lxc/20191016_150201_0f81d@/log.gz

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


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

Title:
  lxc 3.0.4-0ubuntu1 ADT test failure with linux 5.4.0-1.2

Status in lxc package in Ubuntu:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/amd64/l/lxc/20191016_150939_0f81d@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/arm64/l/lxc/20191016_152027_0f81d@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/ppc64el/l/lxc/20191016_150251_0f81d@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/s390x/l/lxc/20191016_150201_0f81d@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1848587/+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 1668771] Re: [SRU] systemd-resolved negative caching for extended period of time

[Dan Streetman]

** Tags added: ddstreet eoan systemd

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

Title:
  [SRU] systemd-resolved negative caching for extended period of time

Status in systemd:
  New
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Disco:
  Fix Released
Status in systemd source package in Eoan:
  In Progress

Bug description:
  [Impact]

   * If a DNS lookup returns SERVFAIL, systemd-resolved seems to cache
  the result for very long (infinity?). I have to restart systemd-
  resolved to have the negative caching purged.

  * After SERVFAIL DNS server issue has been resolved, chromium/firefox
  still returns DNS error despite host can correctly resolve the name.

  [Test Case]

  * If a lookup returns SERVFAIL systemd-resolved will cache the result for 30s 
(See 201d995),
  however, there are several use cases on which this condition is not 
acceptable (See #5552 comments)
  and the only workaround would be to disable cache entirely or flush it , 
which isn't optimal.

  * Configure /etc/systemd/resolved.conf as follows:

  Cache=yes (default)

  * Restart systemd-resolved (systemctl restart systemd-
  resolved.service)

  * Run a host/getent command against a entry that will return SERVFAIL
  and check the journalctl output to see that the reply gets served from
  cache.

  root@systemd-disco:/home/ubuntu# host www.no-record.cl
  Host www.montemar.cl not found: 2(SERVFAIL)
  root@systemd-disco:/home/ubuntu# journalctl -u systemd-resolved -n
  -- Logs begin at Fri 2019-07-12 18:09:42 UTC, end at Tue 2019-07-23 15:10:17 
UTC. --
  Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Transaction 6222 for 
 on scope dns on ens3/* now complete with 
  Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Sending response packet 
with id 61042 on interface 1/AF_INET.
  Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Freeing transaction 
6222.
  Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Got DNS stub UDP query 
packet for id 53580
  Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Looking up RR for  
www.no-record.cl IN A.
  Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: RCODE SERVFAIL cache 
hit for  www.no-record.cl IN A
  Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Transaction 58570 for < 
www.no-record.cl IN A> on scope dns on ens3/* now complete with  scope dns on ens3/.
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Using feature level UDP 
for transaction 22382.
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending query packet 
with id 22382.
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Processing incoming 
packet on transaction 22382 (rcode=SERVFAIL).
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Server returned error: 
SERVFAIL
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Not caching negative 
entry for: www.metaklass.org IN A, cache mode set to no-negative
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Transaction 22382 for 
 on scope dns on ens3/ now complete with from network 
(unsigned).
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending response packet 
with id 31060 on interface 1/AF_INET.

  The following patch https://github.com/systemd/systemd/pull/13047
  implements the required changes.

  [Other Info]

  Note that systemd in Eoan is being upgraded to upstream 242, so I am
  not adding this to Eoan now, as I don't want to disturb the merge. If
  needed after the merge, I'll add to Eoan.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1668771/+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 1835581] Re: networkd-dhcp4 does not set prefsrc for dhcp-provided classless or static routes

[Dan Streetman]

** Tags added: ddstreet eoan

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

Title:
  networkd-dhcp4 does not set prefsrc for dhcp-provided classless or
  static routes

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Cosmic:
  Won't Fix
Status in systemd source package in Disco:
  Fix Released
Status in systemd source package in Eoan:
  In Progress

Bug description:
  [impact]

  the systemd networkd dhcp4 client sets the prefsrc for the default
  route added when a dhcp server provides only the gateway; but if the
  dhcp server provides classless route(s), those are configured instead,
  and the prefsrc is not set for those.

  Normally this is ok, but if the dhcp client system has other
  address(es) configured on the interface using dhcp, then the src for
  packets sent through a classless/static route might not be the same as
  the address provided by the dhcp server.

  If the gateway/router provided in the dhcp classless/static route(s)
  only allows traffic from the address provided to the dhcp client, then
  traffic from the dhcp client may be dropped by the gateway/router.

  [test case]

  set up a dhcp server system (e.g. ubuntu with dnsmasq installed and
  configured) and a dhcp client system.  For example on the dhcp server,
  use this dnsmasq config:

  interface=ens8
  bind-interfaces
  domain=test,10.10.0.0/24
  dhcp-option=42,10.10.0.1
  dhcp-range=test,10.10.0.10,10.10.0.100,1h

  On the dhcp client system, use networkd config such as:

  $ cat /etc/systemd/network/80-ens8.network
  [Match]
  Name=ens8

  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6
  Address=10.10.0.5/24

  Reboot the client, or restart networkd, and it should result in:

  $ ip -4 a show ens8
  3: ens8:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000
  inet 10.10.0.5/24 brd 10.10.0.255 scope global ens8
     valid_lft forever preferred_lft forever
  inet 10.10.0.75/24 brd 10.10.0.255 scope global secondary dynamic ens8
     valid_lft 3580sec preferred_lft 3580sec

  $ ip r
  default via 10.10.0.1 dev ens8 proto dhcp src 10.10.0.75 metric 1024
  10.10.0.0/24 dev ens8 proto kernel scope link src 10.10.0.5
  10.10.0.1 dev ens8 proto dhcp scope link src 10.10.0.75 metric 1024

  Note that, because networkd completes the static ip configuration
  before the dhcp reply is returned and processed, the static address is
  used for the subnet-local routing.  But for global routing through the
  gateway, the dhcp-provided address is used:

  $ ip r get 1.1.1.1
  1.1.1.1 via 10.10.0.1 dev ens8 src 10.10.0.75 uid 1000

  Now on the server, add a classless route:

  dhcp-option=121,0.0.0.0/0,10.10.0.1

  and restart dnsmasq on the server.  Then on the client, reboot.  It
  should now have:

  $ ip -4 a show ens8
  3: ens8:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000
  inet 10.10.0.5/24 brd 10.10.0.255 scope global ens8
     valid_lft forever preferred_lft forever
  inet 10.10.0.75/24 brd 10.10.0.255 scope global secondary dynamic ens8
     valid_lft 3585sec preferred_lft 3585sec

  $ ip r
  default via 10.10.0.1 dev ens8 proto dhcp metric 1024
  10.10.0.0/24 dev ens8 proto kernel scope link src 10.10.0.5

  Now, the global route will use the static address, not the dhcp-
  provided address:

  $ ip r get 1.1.1.1
  1.1.1.1 via 10.10.0.1 dev ens8 src 10.10.0.5 uid 1000

  If the router, 10.10.0.1, only will forward traffic sent from the dhcp
  address it provided, 10.10.0.75, then this configuration will result
  in the client being unable to reach anything through the router,
  because all its packets will have a source address of 10.10.0.5, which
  the router would drop/reject.

  [regression potential]

  this only affects dhcp routes provided by a dhcp server using the
  'static' or 'classless' route dhcp options.  Since this behavior is
  currently the default when a system doesn't add static address(es) to
  interfaces that also get dhcp addresses, this is likely not a change
  in behavior for the vast majority of systems.  And any systems that do
  add static address(es) would usually be able to route through a
  gateway from either the dhcp-provided, or static, address.  So the
  regression potential for this change should be low.

  [other info]

  Note that systemd in Eoan is being upgraded to upstream 242, so I am
  not adding this to Eoan now, as I don't want to disturb the merge.  If
  needed after the merge, I'll add to Eoan.

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

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

[Touch-packages] [Bug 1831787] Re: Bogus routes after DHCP lease change

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~ddstreet/ubuntu/+source/systemd/+git/systemd/+merge/374312

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

Title:
  Bogus routes after DHCP lease change

Status in netplan:
  Invalid
Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Disco:
  In Progress
Status in systemd source package in Eoan:
  In Progress

Bug description:
  Netplan config:

  network:
version: 2
renderer: networkd
ethernets:
  eno4:
dhcp4: no
  eno1np0:
dhcp4: no
addresses: 
  - 172.16.0.2/24
bridges:
  br0:
dhcp4: yes
interfaces:
  - eno4

  On initial boot, machine got 10.0.15.109 IP address:

  May 03 13:09:41 ceph2 systemd-networkd[29349]: br0: Configured
  May 03 13:09:41 ceph2 systemd-networkd[29349]: br0: DHCPv4 address 
10.0.15.109/23 via 10.0.15.253

  At one point, DHCP server reserver this IP address and client
  eventually picked up new IP address:

  May 03 15:01:12 ceph2 systemd-networkd[1137]: br0: DHCPv4 address
  10.0.15.128/23 via 10.0.15.253

  This resulted in IP addresses:

  # ip -o a
  1: loinet 127.0.0.1/8 scope host lo\   valid_lft forever 
preferred_lft forever
  1: loinet6 ::1/128 scope host \   valid_lft forever preferred_lft 
forever
  2: eno1np0inet 172.16.0.2/24 brd 172.16.0.255 scope global eno1np0\   
valid_lft forever preferred_lft forever
  2: eno1np0inet6 fe80::b226:28ff:fe53:56be/64 scope link \   valid_lft 
forever preferred_lft forever
  6: br0inet 10.0.15.128/23 brd 10.0.15.255 scope global dynamic br0\   
valid_lft 503sec preferred_lft 503sec
  6: br0inet6 fe80::b8d7:5eff:fe6b:62a/64 scope link \   valid_lft 
forever preferred_lft forever

  So far, everything is fine. But, the routes on the machine are bogus:

  # ip r
  default via 10.0.15.253 dev br0 proto dhcp src 10.0.15.109 metric 100 
  default via 10.0.15.253 dev br0 proto dhcp src 10.0.15.128 metric 100 
  10.0.14.0/23 dev br0 proto kernel scope link src 10.0.15.128 
  10.0.15.253 dev br0 proto dhcp scope link src 10.0.15.109 metric 100 
  10.0.15.253 dev br0 proto dhcp scope link src 10.0.15.128 metric 100 
  172.16.0.0/24 dev eno1np0 proto kernel scope link src 172.16.0.2 

  routes with src 10.0.15.109 should have been removed when lease was
  renewed. I'm not sure if this is a bug in netplan or systemd. This is
  18.04, systemd 37-3ubuntu10.21, netplan 0.40.1~18.04.4.

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1831787/+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 1835581] Re: networkd-dhcp4 does not set prefsrc for dhcp-provided classless or static routes

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~ddstreet/ubuntu/+source/systemd/+git/systemd/+merge/374312

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

Title:
  networkd-dhcp4 does not set prefsrc for dhcp-provided classless or
  static routes

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Cosmic:
  Won't Fix
Status in systemd source package in Disco:
  Fix Released
Status in systemd source package in Eoan:
  In Progress

Bug description:
  [impact]

  the systemd networkd dhcp4 client sets the prefsrc for the default
  route added when a dhcp server provides only the gateway; but if the
  dhcp server provides classless route(s), those are configured instead,
  and the prefsrc is not set for those.

  Normally this is ok, but if the dhcp client system has other
  address(es) configured on the interface using dhcp, then the src for
  packets sent through a classless/static route might not be the same as
  the address provided by the dhcp server.

  If the gateway/router provided in the dhcp classless/static route(s)
  only allows traffic from the address provided to the dhcp client, then
  traffic from the dhcp client may be dropped by the gateway/router.

  [test case]

  set up a dhcp server system (e.g. ubuntu with dnsmasq installed and
  configured) and a dhcp client system.  For example on the dhcp server,
  use this dnsmasq config:

  interface=ens8
  bind-interfaces
  domain=test,10.10.0.0/24
  dhcp-option=42,10.10.0.1
  dhcp-range=test,10.10.0.10,10.10.0.100,1h

  On the dhcp client system, use networkd config such as:

  $ cat /etc/systemd/network/80-ens8.network
  [Match]
  Name=ens8

  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6
  Address=10.10.0.5/24

  Reboot the client, or restart networkd, and it should result in:

  $ ip -4 a show ens8
  3: ens8:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000
  inet 10.10.0.5/24 brd 10.10.0.255 scope global ens8
     valid_lft forever preferred_lft forever
  inet 10.10.0.75/24 brd 10.10.0.255 scope global secondary dynamic ens8
     valid_lft 3580sec preferred_lft 3580sec

  $ ip r
  default via 10.10.0.1 dev ens8 proto dhcp src 10.10.0.75 metric 1024
  10.10.0.0/24 dev ens8 proto kernel scope link src 10.10.0.5
  10.10.0.1 dev ens8 proto dhcp scope link src 10.10.0.75 metric 1024

  Note that, because networkd completes the static ip configuration
  before the dhcp reply is returned and processed, the static address is
  used for the subnet-local routing.  But for global routing through the
  gateway, the dhcp-provided address is used:

  $ ip r get 1.1.1.1
  1.1.1.1 via 10.10.0.1 dev ens8 src 10.10.0.75 uid 1000

  Now on the server, add a classless route:

  dhcp-option=121,0.0.0.0/0,10.10.0.1

  and restart dnsmasq on the server.  Then on the client, reboot.  It
  should now have:

  $ ip -4 a show ens8
  3: ens8:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000
  inet 10.10.0.5/24 brd 10.10.0.255 scope global ens8
     valid_lft forever preferred_lft forever
  inet 10.10.0.75/24 brd 10.10.0.255 scope global secondary dynamic ens8
     valid_lft 3585sec preferred_lft 3585sec

  $ ip r
  default via 10.10.0.1 dev ens8 proto dhcp metric 1024
  10.10.0.0/24 dev ens8 proto kernel scope link src 10.10.0.5

  Now, the global route will use the static address, not the dhcp-
  provided address:

  $ ip r get 1.1.1.1
  1.1.1.1 via 10.10.0.1 dev ens8 src 10.10.0.5 uid 1000

  If the router, 10.10.0.1, only will forward traffic sent from the dhcp
  address it provided, 10.10.0.75, then this configuration will result
  in the client being unable to reach anything through the router,
  because all its packets will have a source address of 10.10.0.5, which
  the router would drop/reject.

  [regression potential]

  this only affects dhcp routes provided by a dhcp server using the
  'static' or 'classless' route dhcp options.  Since this behavior is
  currently the default when a system doesn't add static address(es) to
  interfaces that also get dhcp addresses, this is likely not a change
  in behavior for the vast majority of systems.  And any systems that do
  add static address(es) would usually be able to route through a
  gateway from either the dhcp-provided, or static, address.  So the
  regression potential for this change should be low.

  [other info]

  Note that systemd in Eoan is being upgraded to upstream 242, so I am
  not adding this to Eoan now, as I don't want to disturb the merge.  If
  needed after the merge, I'll add to Eoan.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

[Touch-packages] [Bug 1668771] Re: [SRU] systemd-resolved negative caching for extended period of time

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~ddstreet/ubuntu/+source/systemd/+git/systemd/+merge/374312

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

Title:
  [SRU] systemd-resolved negative caching for extended period of time

Status in systemd:
  New
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Disco:
  Fix Released
Status in systemd source package in Eoan:
  In Progress

Bug description:
  [Impact]

   * If a DNS lookup returns SERVFAIL, systemd-resolved seems to cache
  the result for very long (infinity?). I have to restart systemd-
  resolved to have the negative caching purged.

  * After SERVFAIL DNS server issue has been resolved, chromium/firefox
  still returns DNS error despite host can correctly resolve the name.

  [Test Case]

  * If a lookup returns SERVFAIL systemd-resolved will cache the result for 30s 
(See 201d995),
  however, there are several use cases on which this condition is not 
acceptable (See #5552 comments)
  and the only workaround would be to disable cache entirely or flush it , 
which isn't optimal.

  * Configure /etc/systemd/resolved.conf as follows:

  Cache=yes (default)

  * Restart systemd-resolved (systemctl restart systemd-
  resolved.service)

  * Run a host/getent command against a entry that will return SERVFAIL
  and check the journalctl output to see that the reply gets served from
  cache.

  root@systemd-disco:/home/ubuntu# host www.no-record.cl
  Host www.montemar.cl not found: 2(SERVFAIL)
  root@systemd-disco:/home/ubuntu# journalctl -u systemd-resolved -n
  -- Logs begin at Fri 2019-07-12 18:09:42 UTC, end at Tue 2019-07-23 15:10:17 
UTC. --
  Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Transaction 6222 for 
 on scope dns on ens3/* now complete with 
  Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Sending response packet 
with id 61042 on interface 1/AF_INET.
  Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Freeing transaction 
6222.
  Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Got DNS stub UDP query 
packet for id 53580
  Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Looking up RR for  
www.no-record.cl IN A.
  Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: RCODE SERVFAIL cache 
hit for  www.no-record.cl IN A
  Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Transaction 58570 for < 
www.no-record.cl IN A> on scope dns on ens3/* now complete with  scope dns on ens3/.
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Using feature level UDP 
for transaction 22382.
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending query packet 
with id 22382.
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Processing incoming 
packet on transaction 22382 (rcode=SERVFAIL).
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Server returned error: 
SERVFAIL
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Not caching negative 
entry for: www.metaklass.org IN A, cache mode set to no-negative
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Transaction 22382 for 
 on scope dns on ens3/ now complete with from network 
(unsigned).
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending response packet 
with id 31060 on interface 1/AF_INET.

  The following patch https://github.com/systemd/systemd/pull/13047
  implements the required changes.

  [Other Info]

  Note that systemd in Eoan is being upgraded to upstream 242, so I am
  not adding this to Eoan now, as I don't want to disturb the merge. If
  needed after the merge, I'll add to Eoan.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1668771/+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 1848571] Re: APT does not honour [trusted=yes] when added to sources.list

[Julian Andres Klode]

It does honour it, it should be downgradting from errors 2 warnings. If
it does not we do need the program output

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

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

Title:
  APT does not honour [trusted=yes] when added to sources.list

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  When adding the PPA for NordVPN the GPG key did not save properly. In
  order to resolve this, I added [trusted=yes] to
  sources.list.d/nordvpn.list and sources.list.d/nordvpn.list.save. APT,
  when running apt update, did not honour this and instead checked the
  GPG key.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: apt 1.8.1
  ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 15:19:05 2019
  InstallationDate: Installed on 2019-07-21 (87 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1848571/+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 1835581] Re: networkd-dhcp4 does not set prefsrc for dhcp-provided classless or static routes

[Dan Streetman]

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

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

Title:
  networkd-dhcp4 does not set prefsrc for dhcp-provided classless or
  static routes

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Cosmic:
  Won't Fix
Status in systemd source package in Disco:
  Fix Released
Status in systemd source package in Eoan:
  In Progress

Bug description:
  [impact]

  the systemd networkd dhcp4 client sets the prefsrc for the default
  route added when a dhcp server provides only the gateway; but if the
  dhcp server provides classless route(s), those are configured instead,
  and the prefsrc is not set for those.

  Normally this is ok, but if the dhcp client system has other
  address(es) configured on the interface using dhcp, then the src for
  packets sent through a classless/static route might not be the same as
  the address provided by the dhcp server.

  If the gateway/router provided in the dhcp classless/static route(s)
  only allows traffic from the address provided to the dhcp client, then
  traffic from the dhcp client may be dropped by the gateway/router.

  [test case]

  set up a dhcp server system (e.g. ubuntu with dnsmasq installed and
  configured) and a dhcp client system.  For example on the dhcp server,
  use this dnsmasq config:

  interface=ens8
  bind-interfaces
  domain=test,10.10.0.0/24
  dhcp-option=42,10.10.0.1
  dhcp-range=test,10.10.0.10,10.10.0.100,1h

  On the dhcp client system, use networkd config such as:

  $ cat /etc/systemd/network/80-ens8.network
  [Match]
  Name=ens8

  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6
  Address=10.10.0.5/24

  Reboot the client, or restart networkd, and it should result in:

  $ ip -4 a show ens8
  3: ens8:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000
  inet 10.10.0.5/24 brd 10.10.0.255 scope global ens8
     valid_lft forever preferred_lft forever
  inet 10.10.0.75/24 brd 10.10.0.255 scope global secondary dynamic ens8
     valid_lft 3580sec preferred_lft 3580sec

  $ ip r
  default via 10.10.0.1 dev ens8 proto dhcp src 10.10.0.75 metric 1024
  10.10.0.0/24 dev ens8 proto kernel scope link src 10.10.0.5
  10.10.0.1 dev ens8 proto dhcp scope link src 10.10.0.75 metric 1024

  Note that, because networkd completes the static ip configuration
  before the dhcp reply is returned and processed, the static address is
  used for the subnet-local routing.  But for global routing through the
  gateway, the dhcp-provided address is used:

  $ ip r get 1.1.1.1
  1.1.1.1 via 10.10.0.1 dev ens8 src 10.10.0.75 uid 1000

  Now on the server, add a classless route:

  dhcp-option=121,0.0.0.0/0,10.10.0.1

  and restart dnsmasq on the server.  Then on the client, reboot.  It
  should now have:

  $ ip -4 a show ens8
  3: ens8:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000
  inet 10.10.0.5/24 brd 10.10.0.255 scope global ens8
     valid_lft forever preferred_lft forever
  inet 10.10.0.75/24 brd 10.10.0.255 scope global secondary dynamic ens8
     valid_lft 3585sec preferred_lft 3585sec

  $ ip r
  default via 10.10.0.1 dev ens8 proto dhcp metric 1024
  10.10.0.0/24 dev ens8 proto kernel scope link src 10.10.0.5

  Now, the global route will use the static address, not the dhcp-
  provided address:

  $ ip r get 1.1.1.1
  1.1.1.1 via 10.10.0.1 dev ens8 src 10.10.0.5 uid 1000

  If the router, 10.10.0.1, only will forward traffic sent from the dhcp
  address it provided, 10.10.0.75, then this configuration will result
  in the client being unable to reach anything through the router,
  because all its packets will have a source address of 10.10.0.5, which
  the router would drop/reject.

  [regression potential]

  this only affects dhcp routes provided by a dhcp server using the
  'static' or 'classless' route dhcp options.  Since this behavior is
  currently the default when a system doesn't add static address(es) to
  interfaces that also get dhcp addresses, this is likely not a change
  in behavior for the vast majority of systems.  And any systems that do
  add static address(es) would usually be able to route through a
  gateway from either the dhcp-provided, or static, address.  So the
  regression potential for this change should be low.

  [other info]

  Note that systemd in Eoan is being upgraded to upstream 242, so I am
  not adding this to Eoan now, as I don't want to disturb the merge.  If
  needed after the merge, I'll add to Eoan.

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

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

[Touch-packages] [Bug 1831787] Re: Bogus routes after DHCP lease change

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~ddstreet/ubuntu/+source/systemd/+git/systemd/+merge/370152

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

Title:
  Bogus routes after DHCP lease change

Status in netplan:
  Invalid
Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Disco:
  In Progress
Status in systemd source package in Eoan:
  In Progress

Bug description:
  Netplan config:

  network:
version: 2
renderer: networkd
ethernets:
  eno4:
dhcp4: no
  eno1np0:
dhcp4: no
addresses: 
  - 172.16.0.2/24
bridges:
  br0:
dhcp4: yes
interfaces:
  - eno4

  On initial boot, machine got 10.0.15.109 IP address:

  May 03 13:09:41 ceph2 systemd-networkd[29349]: br0: Configured
  May 03 13:09:41 ceph2 systemd-networkd[29349]: br0: DHCPv4 address 
10.0.15.109/23 via 10.0.15.253

  At one point, DHCP server reserver this IP address and client
  eventually picked up new IP address:

  May 03 15:01:12 ceph2 systemd-networkd[1137]: br0: DHCPv4 address
  10.0.15.128/23 via 10.0.15.253

  This resulted in IP addresses:

  # ip -o a
  1: loinet 127.0.0.1/8 scope host lo\   valid_lft forever 
preferred_lft forever
  1: loinet6 ::1/128 scope host \   valid_lft forever preferred_lft 
forever
  2: eno1np0inet 172.16.0.2/24 brd 172.16.0.255 scope global eno1np0\   
valid_lft forever preferred_lft forever
  2: eno1np0inet6 fe80::b226:28ff:fe53:56be/64 scope link \   valid_lft 
forever preferred_lft forever
  6: br0inet 10.0.15.128/23 brd 10.0.15.255 scope global dynamic br0\   
valid_lft 503sec preferred_lft 503sec
  6: br0inet6 fe80::b8d7:5eff:fe6b:62a/64 scope link \   valid_lft 
forever preferred_lft forever

  So far, everything is fine. But, the routes on the machine are bogus:

  # ip r
  default via 10.0.15.253 dev br0 proto dhcp src 10.0.15.109 metric 100 
  default via 10.0.15.253 dev br0 proto dhcp src 10.0.15.128 metric 100 
  10.0.14.0/23 dev br0 proto kernel scope link src 10.0.15.128 
  10.0.15.253 dev br0 proto dhcp scope link src 10.0.15.109 metric 100 
  10.0.15.253 dev br0 proto dhcp scope link src 10.0.15.128 metric 100 
  172.16.0.0/24 dev eno1np0 proto kernel scope link src 172.16.0.2 

  routes with src 10.0.15.109 should have been removed when lease was
  renewed. I'm not sure if this is a bug in netplan or systemd. This is
  18.04, systemd 37-3ubuntu10.21, netplan 0.40.1~18.04.4.

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1831787/+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 1848570] Re: Skip individual bad sources

[Julian Andres Klode]

It does just that

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

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

Title:
  Skip individual bad sources

Status in apt package in Ubuntu:
  Invalid

Bug description:
  Yesterday I was unable to update *any* packages on my system, just
  because *one* source sent a malformed package list. apt-get update
  gave:

  E: Encountered a section with no Package: header
  E: Problem with MergeList 
/var/lib/apt/lists/adoptopenjdk.jfrog.io_adoptopenjdk_deb_dists_disco_main_binary-amd64_Packages
  E: The package lists or status file could not be parsed or opened.

  When this happens, apt should degrade gracefully by skipping just that
  one package list, and continuing to process all the others, so that
  unaffected packages can still be updated. Otherwise, we don't have the
  resilient, fault-tolerant system that people expect when they choose
  Ubuntu or Debian.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: apt 1.8.3
  ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Oct 17 12:14:44 2019
  InstallationDate: Installed on 2019-06-18 (120 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: apt
  UpgradeStatus: Upgraded to disco on 2019-06-26 (112 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1848570/+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 1668771] Re: [SRU] systemd-resolved negative caching for extended period of time

[Dan Streetman]

this did not make it into Eoan.

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

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

Title:
  [SRU] systemd-resolved negative caching for extended period of time

Status in systemd:
  New
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Disco:
  Fix Released
Status in systemd source package in Eoan:
  In Progress

Bug description:
  [Impact]

   * If a DNS lookup returns SERVFAIL, systemd-resolved seems to cache
  the result for very long (infinity?). I have to restart systemd-
  resolved to have the negative caching purged.

  * After SERVFAIL DNS server issue has been resolved, chromium/firefox
  still returns DNS error despite host can correctly resolve the name.

  [Test Case]

  * If a lookup returns SERVFAIL systemd-resolved will cache the result for 30s 
(See 201d995),
  however, there are several use cases on which this condition is not 
acceptable (See #5552 comments)
  and the only workaround would be to disable cache entirely or flush it , 
which isn't optimal.

  * Configure /etc/systemd/resolved.conf as follows:

  Cache=yes (default)

  * Restart systemd-resolved (systemctl restart systemd-
  resolved.service)

  * Run a host/getent command against a entry that will return SERVFAIL
  and check the journalctl output to see that the reply gets served from
  cache.

  root@systemd-disco:/home/ubuntu# host www.no-record.cl
  Host www.montemar.cl not found: 2(SERVFAIL)
  root@systemd-disco:/home/ubuntu# journalctl -u systemd-resolved -n
  -- Logs begin at Fri 2019-07-12 18:09:42 UTC, end at Tue 2019-07-23 15:10:17 
UTC. --
  Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Transaction 6222 for 
 on scope dns on ens3/* now complete with 
  Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Sending response packet 
with id 61042 on interface 1/AF_INET.
  Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Freeing transaction 
6222.
  Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Got DNS stub UDP query 
packet for id 53580
  Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Looking up RR for  
www.no-record.cl IN A.
  Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: RCODE SERVFAIL cache 
hit for  www.no-record.cl IN A
  Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Transaction 58570 for < 
www.no-record.cl IN A> on scope dns on ens3/* now complete with  scope dns on ens3/.
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Using feature level UDP 
for transaction 22382.
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending query packet 
with id 22382.
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Processing incoming 
packet on transaction 22382 (rcode=SERVFAIL).
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Server returned error: 
SERVFAIL
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Not caching negative 
entry for: www.metaklass.org IN A, cache mode set to no-negative
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Transaction 22382 for 
 on scope dns on ens3/ now complete with from network 
(unsigned).
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending response packet 
with id 31060 on interface 1/AF_INET.

  The following patch https://github.com/systemd/systemd/pull/13047
  implements the required changes.

  [Other Info]

  Note that systemd in Eoan is being upgraded to upstream 242, so I am
  not adding this to Eoan now, as I don't want to disturb the merge. If
  needed after the merge, I'll add to Eoan.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1668771/+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 1848570] [NEW] Skip individual bad sources

[seahen]

Public bug reported:

Yesterday I was unable to update *any* packages on my system, just
because *one* source sent a malformed package list. apt-get update gave:

E: Encountered a section with no Package: header
E: Problem with MergeList 
/var/lib/apt/lists/adoptopenjdk.jfrog.io_adoptopenjdk_deb_dists_disco_main_binary-amd64_Packages
E: The package lists or status file could not be parsed or opened.

When this happens, apt should degrade gracefully by skipping just that
one package list, and continuing to process all the others, so that
unaffected packages can still be updated. Otherwise, we don't have the
resilient, fault-tolerant system that people expect when they choose
Ubuntu or Debian.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: apt 1.8.3
ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
Uname: Linux 5.0.0-31-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Oct 17 12:14:44 2019
InstallationDate: Installed on 2019-06-18 (120 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: apt
UpgradeStatus: Upgraded to disco on 2019-06-26 (112 days ago)

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


** Tags: amd64 apport-bug disco

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

Title:
  Skip individual bad sources

Status in apt package in Ubuntu:
  New

Bug description:
  Yesterday I was unable to update *any* packages on my system, just
  because *one* source sent a malformed package list. apt-get update
  gave:

  E: Encountered a section with no Package: header
  E: Problem with MergeList 
/var/lib/apt/lists/adoptopenjdk.jfrog.io_adoptopenjdk_deb_dists_disco_main_binary-amd64_Packages
  E: The package lists or status file could not be parsed or opened.

  When this happens, apt should degrade gracefully by skipping just that
  one package list, and continuing to process all the others, so that
  unaffected packages can still be updated. Otherwise, we don't have the
  resilient, fault-tolerant system that people expect when they choose
  Ubuntu or Debian.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: apt 1.8.3
  ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Oct 17 12:14:44 2019
  InstallationDate: Installed on 2019-06-18 (120 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: apt
  UpgradeStatus: Upgraded to disco on 2019-06-26 (112 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1848570/+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 1848571] [NEW] APT does not honour [trusted=yes] when added to sources.list

[Connor McDermid]

Public bug reported:

When adding the PPA for NordVPN the GPG key did not save properly. In
order to resolve this, I added [trusted=yes] to
sources.list.d/nordvpn.list and sources.list.d/nordvpn.list.save. APT,
when running apt update, did not honour this and instead checked the GPG
key.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: apt 1.8.1
ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
Uname: Linux 5.0.0-31-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 17 15:19:05 2019
InstallationDate: Installed on 2019-07-21 (87 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug disco

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

Title:
  APT does not honour [trusted=yes] when added to sources.list

Status in apt package in Ubuntu:
  New

Bug description:
  When adding the PPA for NordVPN the GPG key did not save properly. In
  order to resolve this, I added [trusted=yes] to
  sources.list.d/nordvpn.list and sources.list.d/nordvpn.list.save. APT,
  when running apt update, did not honour this and instead checked the
  GPG key.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: apt 1.8.1
  ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 15:19:05 2019
  InstallationDate: Installed on 2019-07-21 (87 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1848571/+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 1848558] Re: (intermittent) need to authenticate 3 times before accepted

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1848558

** Tags added: iso-testing

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

Title:
  (intermittent) need to authenticate 3 times before accepted

Status in apport package in Ubuntu:
  New

Bug description:
  When at the terminal, trying to file an issue with ubuntu-bug, I was
  prompted for authentication. Only after the third try was the password
  accepted.

  1. I entered the password correctly and the authentication window closed and 
reopened very quickly (no error message that I had entered the password 
incorrectly).
  2. Then I entered a bogus password and the authentication window closed and 
reopened very quickly (this time with the expected “Your authentication attempt 
was unsuccessful. Please try again”).
  3. Then I entered the correct password again and it was accepted.

  This happens more often than not, however sometimes I'm not prompted
  for authentication at all with ubuntu-bug. When I am prompted for
  authentication, all three tries can be the correct password (no need
  to have a bogus password entered as one of the tries) and only the
  third one is accepted.

  The expected behavior is:
  1. Consistency: ubuntu-bug should either always prompt the user for a 
password or always not
  2. Only one entry needed: If ubuntu-bug is going to prompt the user for a 
password using apport, then the first correct entry should be accepted.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: apport 2.20.11-0ubuntu8
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Oct 17 11:44:30 2019
  InstallationDate: Installed on 2019-10-17 (0 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1848558/+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 1831787] Re: Bogus routes after DHCP lease change

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~ddstreet/ubuntu/+source/systemd/+git/systemd/+merge/374303

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

Title:
  Bogus routes after DHCP lease change

Status in netplan:
  Invalid
Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Disco:
  In Progress
Status in systemd source package in Eoan:
  In Progress

Bug description:
  Netplan config:

  network:
version: 2
renderer: networkd
ethernets:
  eno4:
dhcp4: no
  eno1np0:
dhcp4: no
addresses: 
  - 172.16.0.2/24
bridges:
  br0:
dhcp4: yes
interfaces:
  - eno4

  On initial boot, machine got 10.0.15.109 IP address:

  May 03 13:09:41 ceph2 systemd-networkd[29349]: br0: Configured
  May 03 13:09:41 ceph2 systemd-networkd[29349]: br0: DHCPv4 address 
10.0.15.109/23 via 10.0.15.253

  At one point, DHCP server reserver this IP address and client
  eventually picked up new IP address:

  May 03 15:01:12 ceph2 systemd-networkd[1137]: br0: DHCPv4 address
  10.0.15.128/23 via 10.0.15.253

  This resulted in IP addresses:

  # ip -o a
  1: loinet 127.0.0.1/8 scope host lo\   valid_lft forever 
preferred_lft forever
  1: loinet6 ::1/128 scope host \   valid_lft forever preferred_lft 
forever
  2: eno1np0inet 172.16.0.2/24 brd 172.16.0.255 scope global eno1np0\   
valid_lft forever preferred_lft forever
  2: eno1np0inet6 fe80::b226:28ff:fe53:56be/64 scope link \   valid_lft 
forever preferred_lft forever
  6: br0inet 10.0.15.128/23 brd 10.0.15.255 scope global dynamic br0\   
valid_lft 503sec preferred_lft 503sec
  6: br0inet6 fe80::b8d7:5eff:fe6b:62a/64 scope link \   valid_lft 
forever preferred_lft forever

  So far, everything is fine. But, the routes on the machine are bogus:

  # ip r
  default via 10.0.15.253 dev br0 proto dhcp src 10.0.15.109 metric 100 
  default via 10.0.15.253 dev br0 proto dhcp src 10.0.15.128 metric 100 
  10.0.14.0/23 dev br0 proto kernel scope link src 10.0.15.128 
  10.0.15.253 dev br0 proto dhcp scope link src 10.0.15.109 metric 100 
  10.0.15.253 dev br0 proto dhcp scope link src 10.0.15.128 metric 100 
  172.16.0.0/24 dev eno1np0 proto kernel scope link src 172.16.0.2 

  routes with src 10.0.15.109 should have been removed when lease was
  renewed. I'm not sure if this is a bug in netplan or systemd. This is
  18.04, systemd 37-3ubuntu10.21, netplan 0.40.1~18.04.4.

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1831787/+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 1847896] Re: Unable to shutdown or restart from log-in screen

[Balint Reczey]

I've pushed the fix to schedule it for the next upload:
https://code.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/+git/systemd/+ref/ubuntu-eoan

I'm waiting a few days to see if there are other fixes showing up to
include in the same upload.

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

Title:
  Unable to shutdown or restart from log-in screen

Status in gnome-shell package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  When selecting the shutdown icon from the log-in screen you are
  prompted with a dialog that allows you to either cancel, restart or
  shutdown.

  It has been noted that the restart and shutdown options no longer
  work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Oct 13 09:08:23 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-05-17 (148 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847896/+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 1848558] [NEW] (intermittent) need to authenticate 3 times before accepted

[Heather Ellsworth]

Public bug reported:

When at the terminal, trying to file an issue with ubuntu-bug, I was
prompted for authentication. Only after the third try was the password
accepted.

1. I entered the password correctly and the authentication window closed and 
reopened very quickly (no error message that I had entered the password 
incorrectly).
2. Then I entered a bogus password and the authentication window closed and 
reopened very quickly (this time with the expected “Your authentication attempt 
was unsuccessful. Please try again”).
3. Then I entered the correct password again and it was accepted.

This happens more often than not, however sometimes I'm not prompted for
authentication at all with ubuntu-bug. When I am prompted for
authentication, all three tries can be the correct password (no need to
have a bogus password entered as one of the tries) and only the third
one is accepted.

The expected behavior is:
1. Consistency: ubuntu-bug should either always prompt the user for a password 
or always not
2. Only one entry needed: If ubuntu-bug is going to prompt the user for a 
password using apport, then the first correct entry should be accepted.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: apport 2.20.11-0ubuntu8
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Oct 17 11:44:30 2019
InstallationDate: Installed on 2019-10-17 (0 days ago)
InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug eoan

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

Title:
  (intermittent) need to authenticate 3 times before accepted

Status in apport package in Ubuntu:
  New

Bug description:
  When at the terminal, trying to file an issue with ubuntu-bug, I was
  prompted for authentication. Only after the third try was the password
  accepted.

  1. I entered the password correctly and the authentication window closed and 
reopened very quickly (no error message that I had entered the password 
incorrectly).
  2. Then I entered a bogus password and the authentication window closed and 
reopened very quickly (this time with the expected “Your authentication attempt 
was unsuccessful. Please try again”).
  3. Then I entered the correct password again and it was accepted.

  This happens more often than not, however sometimes I'm not prompted
  for authentication at all with ubuntu-bug. When I am prompted for
  authentication, all three tries can be the correct password (no need
  to have a bogus password entered as one of the tries) and only the
  third one is accepted.

  The expected behavior is:
  1. Consistency: ubuntu-bug should either always prompt the user for a 
password or always not
  2. Only one entry needed: If ubuntu-bug is going to prompt the user for a 
password using apport, then the first correct entry should be accepted.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: apport 2.20.11-0ubuntu8
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Oct 17 11:44:30 2019
  InstallationDate: Installed on 2019-10-17 (0 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1848558/+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 1847666] Re: Ubuntu doesn't cannot be suspended via the suspend icon after you log out.

[Lyubomir Parvanov]

Yes, it seems like a duplicate. And yes, i think it worked in 19.04.

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

Title:
  Ubuntu doesn't cannot be suspended via the suspend icon after you log
  out.

Status in systemd package in Ubuntu:
  New

Bug description:
  Pressing the suspend button in the top right menu when you are logged
  out doesn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-13-generic 5.3.0-13.14
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1766 F pulseaudio
lyubomir  18081 F pulseaudio
  Date: Thu Oct 10 23:15:08 2019
  HibernationDevice: RESUME=UUID=6f86efb8-0e86-4159-9412-28658da56f90
  InstallationDate: Installed on 2019-07-23 (78 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b5f7 Chicony Electronics Co., Ltd HD WebCam
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID :0538   USB OPTICAL MOUSE
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire A515-51G
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-13-generic N/A
   linux-backports-modules-5.3.0-13-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-09-27 (12 days ago)
  dmi.bios.date: 01/03/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.02
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Charmander_KL
  dmi.board.vendor: KBL
  dmi.board.version: V2.02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.02:bd01/03/2019:svnAcer:pnAspireA515-51G:pvrV2.02:rvnKBL:rnCharmander_KL:rvrV2.02:cvnAcer:ct10:cvrV2.02:
  dmi.product.family: Aspire 5
  dmi.product.name: Aspire A515-51G
  dmi.product.sku: 
  dmi.product.version: V2.02
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1847666/+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 1845314] Re: udisks2 fails to install in a container with systemd 243

[Dan Streetman]

@panfaust I believe this should be fixed now upstream by
https://github.com/systemd/systemd/pull/13656

can you verify that is correct?  And we shouldn't need anything in Eoan
since it's going to be based on 242, which doesn't have commit
97afc0351a96e0daa83964df33937967c75c644f that introduces this problem.

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

Title:
  udisks2 fails to install in a container with systemd 243

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

Bug description:
  santa_ | rbalint: hey while systemd 243 was available in eoan I still
  got one of "my" issues (udisks2 fails to install in a container)

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1845314/+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 1847666] Re: Ubuntu doesn't cannot be suspended via the suspend icon after you log out.

[Dan Streetman]

maybe this is a dup of bug 1847896?

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

Title:
  Ubuntu doesn't cannot be suspended via the suspend icon after you log
  out.

Status in systemd package in Ubuntu:
  New

Bug description:
  Pressing the suspend button in the top right menu when you are logged
  out doesn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-13-generic 5.3.0-13.14
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1766 F pulseaudio
lyubomir  18081 F pulseaudio
  Date: Thu Oct 10 23:15:08 2019
  HibernationDevice: RESUME=UUID=6f86efb8-0e86-4159-9412-28658da56f90
  InstallationDate: Installed on 2019-07-23 (78 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b5f7 Chicony Electronics Co., Ltd HD WebCam
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID :0538   USB OPTICAL MOUSE
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire A515-51G
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-13-generic N/A
   linux-backports-modules-5.3.0-13-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-09-27 (12 days ago)
  dmi.bios.date: 01/03/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.02
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Charmander_KL
  dmi.board.vendor: KBL
  dmi.board.version: V2.02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.02:bd01/03/2019:svnAcer:pnAspireA515-51G:pvrV2.02:rvnKBL:rnCharmander_KL:rvrV2.02:cvnAcer:ct10:cvrV2.02:
  dmi.product.family: Aspire 5
  dmi.product.name: Aspire A515-51G
  dmi.product.sku: 
  dmi.product.version: V2.02
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1847666/+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 1848534] Re: System shows graphic artifacts for a moment, then text cursor for about minute and then starts

[Brian Murray]

** Package changed: ubuntu-release-upgrader (Ubuntu) => xorg (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/1848534

Title:
  System shows graphic artifacts for a moment, then text cursor for
  about minute and then starts

Status in xorg package in Ubuntu:
  New

Bug description:
  AFter upgrade system shows graphic artefacts for a moment and then
  text cursor for about minute (it looks like hanged) and then starts.

  In 19.04 startup required 1 or 2 seconds.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 17:42:27 2019
  InstallationDate: Installed on 2019-07-04 (104 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago)
  VarLogDistupgradeLspcitxt:
   
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1848534/+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 1848534] [NEW] System shows graphic artifacts for a moment, then text cursor for about minute and then starts

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

AFter upgrade system shows graphic artefacts for a moment and then text
cursor for about minute (it looks like hanged) and then starts.

In 19.04 startup required 1 or 2 seconds.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: ubuntu-release-upgrader-core 1:19.10.15
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 17 17:42:27 2019
InstallationDate: Installed on 2019-07-04 (104 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago)
VarLogDistupgradeLspcitxt:
 
VarLogDistupgradeXorgFixuplog:
 INFO:root:/usr/bin/do-release-upgrade running
 INFO:root:No xorg.conf, exiting

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


** Tags: amd64 apport-bug dist-upgrade eoan
-- 
System shows graphic artifacts for a moment, then text cursor for about minute 
and then starts
https://bugs.launchpad.net/bugs/1848534
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg 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 1759836] Re: systemd-udevd consumes 100% of CPU due to hid2hci udev rule from bluez

[Dan Streetman]

thank you!  marking as verified for bionic :)

** 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 bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1759836

Title:
  systemd-udevd consumes 100% of CPU due to hid2hci udev rule from bluez

Status in linux:
  Confirmed
Status in The Ubuntu Power Consumption Project:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in bluez source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Invalid
Status in bluez source package in Disco:
  Fix Released
Status in linux source package in Disco:
  Invalid
Status in systemd source package in Disco:
  Invalid
Status in bluez source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Invalid
Status in systemd source package in Eoan:
  Invalid
Status in bluez package in Debian:
  New

Bug description:
  [impact]

  on specific Dell systems, with a specific usb bluetooth device built-
  in, the udev rule 'hid2hci' provided by the 'bluez' package causes an
  endless loop of uevents resulting from 'bind' or 'unbind' kernel
  uevents.  These new events were added to the kernel after the
  'hid2hci' udev rule was written.

  [test case]

  the specific Dell system is required to be able to reproduce this, or
  at least the specific usb bluetooth hardware included in that system.

  Reproducing this is reportedly easy, for example comment 75 indicates
  it happens on every boot.

  When this happens, any process monitor (e.g. ps, top, etc) will show
  the 'udevd' process using 100% of a cpu, and 'udevadm monitor' should
  show repeated 'bind' and 'unbind' events as mentioned in comment 39.

  [regression potential]

  as this alters what kernel uevents the 'hid2hci' udev rule processes,
  regressions would involve the affected usb bluetooth device failing to
  be set up, or otherwise not processing the uevents correctly.

  [other info]

  this is not fixed yet upstream, as of my last check, but has been
  submitted upstream as mentioned in comment 95.

  
  original description:

  --

  
  The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not 
noticing any difference in my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 29 08:52:54 2018
  InstallationDate: Installed on 2018-03-05 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  MachineType: Dell Inc. Inspiron N5010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 08R0GW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel/+bug/1759836/+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 1847896] Re: Unable to shutdown or restart from log-in screen

[Balint Reczey]

** Changed in: systemd (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  Unable to shutdown or restart from log-in screen

Status in gnome-shell package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  When selecting the shutdown icon from the log-in screen you are
  prompted with a dialog that allows you to either cancel, restart or
  shutdown.

  It has been noted that the restart and shutdown options no longer
  work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Oct 13 09:08:23 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-05-17 (148 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847896/+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 1759836] Re: systemd-udevd consumes 100% of CPU due to hid2hci udev rule from bluez

[David Killingsworth]

Dan,

I can confirm that after enabling proposed for bionic and then issuing
the command which installs bluez/5.48-0ubuntu3.2

$ sudo apt-get install bluez/bionic-proposed

The issue has been fixed for me.

I have a Dell Latitude E5400.

Thanks,
David

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

Title:
  systemd-udevd consumes 100% of CPU due to hid2hci udev rule from bluez

Status in linux:
  Confirmed
Status in The Ubuntu Power Consumption Project:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in bluez source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Invalid
Status in bluez source package in Disco:
  Fix Released
Status in linux source package in Disco:
  Invalid
Status in systemd source package in Disco:
  Invalid
Status in bluez source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Invalid
Status in systemd source package in Eoan:
  Invalid
Status in bluez package in Debian:
  New

Bug description:
  [impact]

  on specific Dell systems, with a specific usb bluetooth device built-
  in, the udev rule 'hid2hci' provided by the 'bluez' package causes an
  endless loop of uevents resulting from 'bind' or 'unbind' kernel
  uevents.  These new events were added to the kernel after the
  'hid2hci' udev rule was written.

  [test case]

  the specific Dell system is required to be able to reproduce this, or
  at least the specific usb bluetooth hardware included in that system.

  Reproducing this is reportedly easy, for example comment 75 indicates
  it happens on every boot.

  When this happens, any process monitor (e.g. ps, top, etc) will show
  the 'udevd' process using 100% of a cpu, and 'udevadm monitor' should
  show repeated 'bind' and 'unbind' events as mentioned in comment 39.

  [regression potential]

  as this alters what kernel uevents the 'hid2hci' udev rule processes,
  regressions would involve the affected usb bluetooth device failing to
  be set up, or otherwise not processing the uevents correctly.

  [other info]

  this is not fixed yet upstream, as of my last check, but has been
  submitted upstream as mentioned in comment 95.

  
  original description:

  --

  
  The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not 
noticing any difference in my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 29 08:52:54 2018
  InstallationDate: Installed on 2018-03-05 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  MachineType: Dell Inc. Inspiron N5010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 08R0GW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel/+bug/1759836/+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 1839290] Re: systemd doesn't restart a service after crashes

[Vladimir Kononov]

Mathew, I've just checked the ubuntu-disco branch of systemd — it looks
like fix was backported in systemd=240-6ubuntu5 with a bunch of other
fixes, see debian/patches/Change-job-mode-of-manager-triggered-restarts-
to-JOB_REPL.patch. So disco was fixed before this bug was actually
filed.

Xenial and Bionic are still affected — any chance of a bugfix landing
there?

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

Title:
  systemd doesn't restart a service after crashes

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  New
Status in systemd source package in Bionic:
  New
Status in systemd source package in Disco:
  Fix Released

Bug description:
  Affected versions of OS and systemd:
  $ cat /etc/issue
  Ubuntu 16.04.6 LTS \n \l
  $ systemd --version
  systemd 229
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

  Affected packages:
  systemd 229-4ubuntu21.22 and previous versions.

  Expected behaviour you didn't see:
  Scheduling restart of failed service.
  A process crashed by sigabrt and didn't restart.

  Description:
  The bug was reported to a systemd upstream repository: 
https://github.com/systemd/systemd/issues/11456
  The bug was fixed and accepted to the master branch: 
https://github.com/systemd/systemd/pull/11467/files

  Action:
  Include this patch to Ubuntu 16.04 and other version of Ubuntu which are 
supported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1839290/+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 1848522] [NEW] Backport packages for 18.04.4 HWE stack

[Timo Aaltonen]

Public bug reported:

PLACEHOLDER

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

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

** Affects: llvm-toolchain-9 (Ubuntu)
 Importance: Undecided
 Status: Invalid

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

** Affects: xorg-server-hwe-18.04 (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: libclc (Ubuntu Bionic)
 Importance: Undecided
 Assignee: Timo Aaltonen (tjaalton)
 Status: New

** Affects: libdrm (Ubuntu Bionic)
 Importance: Undecided
 Assignee: Timo Aaltonen (tjaalton)
 Status: New

** Affects: llvm-toolchain-9 (Ubuntu Bionic)
 Importance: Undecided
 Assignee: Timo Aaltonen (tjaalton)
 Status: New

** Affects: mesa (Ubuntu Bionic)
 Importance: Undecided
 Assignee: Timo Aaltonen (tjaalton)
 Status: New

** Affects: xorg-server-hwe-18.04 (Ubuntu Bionic)
 Importance: Undecided
 Assignee: Timo Aaltonen (tjaalton)
 Status: New

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

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

** Also affects: llvm-toolchain-9 (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

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

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

** Also affects: llvm-toolchain-9 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

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

** Changed in: llvm-toolchain-9 (Ubuntu)
   Status: New => Invalid

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

** Changed in: xorg-server-hwe-18.04 (Ubuntu)
   Status: New => Invalid

** Changed in: libclc (Ubuntu Bionic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: libdrm (Ubuntu Bionic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: mesa (Ubuntu Bionic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: xorg-server-hwe-18.04 (Ubuntu Bionic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: llvm-toolchain-9 (Ubuntu Bionic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  Backport packages for 18.04.4 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-9 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  New
Status in libdrm source package in Bionic:
  New
Status in llvm-toolchain-9 source package in Bionic:
  New
Status in mesa source package in Bionic:
  New
Status in xorg-server-hwe-18.04 source package in Bionic:
  New

Bug description:
  PLACEHOLDER

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1848522/+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 1181106] Re: Failed to change profile to A2DP

[Falk Pauser]

Not working in 18.04 for me.

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

Title:
  Failed to change profile to A2DP

Status in Bluez Utilities:
  New
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio package in Debian:
  Fix Released

Bug description:
  I upgraded to 13.04 recently and my A2DP profile, which had been
  working great under 12.10 is suddenly gone.  Neither my blueman applet
  nor the built-in bluetooth manager applet can connect my external
  bluetooth speaker to the A2DP profile.  They can connect to the
  bluetooth device itself just fine.

  Steps I'm using:

  * using blueman, I can connect to the external bluetooth speaker and view the 
device in the devices listing
  * I can connect the device to the Audio sink and I get a message saying it is 
now connected and will "show in the PulseAudio mixer"
  * After connecting the external speaker to the audio sink, I can also see the 
device in the "Play sound through" listing in the Sound system control panel, 
but the icon has a circle with a line through it.
  * but if I right-click the device and choose "Audio Profile" from the context 
menu and try to select "High Fidelity Playback (A2DP)" as the new profile, I 
get an error message stating "failed to change profile to a2dp"

  I've already added "Enable=Socket" in /etc/bluetooth/audio.conf,
  without that I can't pair my headset. Now I can pair it, but I can't
  activate the A2DP profile.

  When I try to activate it, I see this message in my syslog :
  pulseaudio[2603]: [pulseaudio] module-bluetooth-device.c: Profile has no 
transport

  I tried the kernel 3.9.0 because of a sound problem with my soundcard,
  this kernel fixed my soundcard problem, but A2DP still doesn't work

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1181106/+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 1846787] Re: systemd-logind leaves leftover sessions and scope files

[Robie Basak]

This looks good, thanks!

I think it would be appropriate for a second developer to review the
patches for any backport-related issues. As you say the patches are non-
trivial. I asked Dimitri to take a look, as he's familiar with the code
base and will probably be far quicker at reviewing them than I can.

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

Title:
  systemd-logind leaves leftover sessions and scope files

Status in dbus package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  In Progress
Status in systemd source package in Xenial:
  In Progress

Bug description:
  [Impact]
  Scope file leakage can cause SSH delays and reduce performance in systemd

  [Description]
  The current systemd-logind version present in Xenial can leave abandoned SSH
  sessions and scope files in cases where the host sees a lot of concurrent SSH
  connections. These leftover sessions can slow down systemd performance
  greatly, and can have an impact on sshd handling a great number of concurrent
  connections.

  To fix this issue, patches are needed in both dbus and systemd. These improve 
the
  performance of the communication between dbus and systemd, so that they can
  handle a better volume of events (e.g. SSH logins). All of those patches are
  already present from Bionic onwards, so we only need those fixes for Xenial.

  == Systemd ==
  Upstream patches:
  - core: use an AF_UNIX/SOCK_DGRAM socket for cgroup agent notification 
(d8fdc62037b5)

  $ git describe --contains d8fdc62037b5
  v230~71^2~2

  $ rmadison systemd
   systemd | 229-4ubuntu4 | xenial  | source, ...
   systemd | 229-4ubuntu21.21 | xenial-security | source, ...
   systemd | 229-4ubuntu21.22 | xenial-updates  | source, ... <
   systemd | 237-3ubuntu10| bionic  | source, ...
   systemd | 237-3ubuntu10.29 | bionic-security | source, ...
   systemd | 237-3ubuntu10.29 | bionic-updates  | source, ...
   systemd | 237-3ubuntu10.31 | bionic-proposed | source, ...

  == DBus ==
  Upstream patches:
  - Only read one message at a time if there are fds pending (892f084eeda0)
  - bus: Fix timeout restarts  (529600397bca)
  - DBusMainLoop: ensure all required timeouts are restarted (446b0d9ac75a)

  $ git describe --contains 892f084eeda0 529600397bca 446b0d9ac75a
  dbus-1.11.10~44
  dbus-1.11.10~45
  dbus-1.11.16~2

  $ rmadison dbus
   dbus | 1.10.6-1ubuntu3| xenial   | source, ...
   dbus | 1.10.6-1ubuntu3.4  | xenial-security  | source, ...
   dbus | 1.10.6-1ubuntu3.4  | xenial-updates   | source, ... <
   dbus | 1.12.2-1ubuntu1| bionic   | source, ...
   dbus | 1.12.2-1ubuntu1.1  | bionic-security  | source, ...
   dbus | 1.12.2-1ubuntu1.1  | bionic-updates   | source, ...

  [Test Case]
  1) Simulate a lot of concurrent SSH connections with e.g. a for loop:
  multipass@xenial-logind:~$ for i in {1..1000}; do sleep 0.1; ssh localhost 
sleep 1 & done

  2) Check for leaked sessions in /run/systemd/system/:
  multipass@xenial-logind:~$ ls -ld /run/systemd/system/session-*.scope*
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-103.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-104.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-105.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-106.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-110.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-111.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-112.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-113.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-114.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-115.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-116.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-117.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-118.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-119.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-120.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-121.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-122.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-123.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-126.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-131.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-134.scope.d
  ...

  [Regression Potential]
  As the 

[Touch-packages] [Bug 1774757] Re: package libgraphite2-3 1.3.11-2 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libgraphite2-3/changelog.Debian.gz', which is different from ot

[Mattia Rizzolo]

I can't quite imagine what could have happened here, but I'm totally
unable to reproduce it.  Also, you are the only one that reported this,
so I'm totally at a loss.  I'll be marking this bug as incompleted, and
see if anybody can post new details, otherwise it'll expire.

I also believe just retrying didn't trigger this issue anymore, right?
so…

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

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

Title:
  package libgraphite2-3 1.3.11-2 failed to install/upgrade: trying to
  overwrite shared '/usr/share/doc/libgraphite2-3/changelog.Debian.gz',
  which is different from other instances of package libgraphite2-3:i386

Status in graphite2 package in Ubuntu:
  Incomplete

Bug description:
  everytime i turn on my pc it shows the error

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libgraphite2-3 1.3.11-2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Sat Jun  2 09:52:02 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  DuplicateSignature:
   package:libgraphite2-3:1.3.11-2
   Unpacking libgraphite2-3:i386 (1.3.11-2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-WRx3Ga/12-libgraphite2-3_1.3.11-2_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libgraphite2-3/changelog.Debian.gz', which is different from 
other instances of package libgraphite2-3:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libgraphite2-3/changelog.Debian.gz', which is different from 
other instances of package libgraphite2-3:i386
  InstallationDate: Installed on 2018-05-24 (8 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: graphite2
  Title: package libgraphite2-3 1.3.11-2 failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libgraphite2-3/changelog.Debian.gz', which is 
different from other instances of package libgraphite2-3:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/graphite2/+bug/1774757/+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 983220] Re: subpixel rendering doesn't respect screen rotation

[Hugh McMaster]

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

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

Title:
  subpixel rendering doesn't respect screen rotation

Status in freetype package in Ubuntu:
  Invalid
Status in wayland package in Ubuntu:
  New

Bug description:
  1) Open gnome-terminal
  2) xrandr --output default --rotate inverted
  2) Open another gnome-terminal

  In both the original and the new terminal, text has red and blue
  "shadows" caused by subpixel rendering that doesn't match up to the
  inverted pixel layout resulting from the screen being flipped 180
  degrees.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libfreetype6 2.4.8-1ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.0.1-0ubuntu3
  Architecture: amd64
  Date: Mon Apr 16 11:34:06 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(2029.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: freetype
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/983220/+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 985647] Re: Some Traditional Chinese words looks very strange during the installation process

[Hugh McMaster]

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

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

Title:
  Some Traditional Chinese words looks very strange during the
  installation process

Status in freetype package in Ubuntu:
  Fix Released

Bug description:
  ISO version: precise-desktop-amd64.iso
  Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120418.2)
  Installation language: Traditional Chinese

  Description:
  Select Traditional Chinese as the installation language, some words looks 
very strange during the installation process. Please refer to the attached 
picture for more info.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/985647/+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 1779497] Re: package libfreetype6:i386 2.8.1-2ubuntu2 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo.

[Hugh McMaster]

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

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

Title:
  package libfreetype6:i386 2.8.1-2ubuntu2 failed to install/upgrade: O
  pacote está num mau estado de inconsistência; deve  reinstala-lo antes
  de tentar configura-lo.

Status in freetype package in Ubuntu:
  Invalid

Bug description:
  dpkg: erro ao processar o pacote libsane1:i386 (--configure):
   problemas de dependência - deixando desconfigurado
  Erros foram encontrados durante o processamento de:
   libfreetype6:i386
   libwine:i386
   libfontconfig1:i386
   wine32:i386
   libgd3:i386
   libgphoto2-6:i386
   libsane1:i386
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libfreetype6:i386 2.8.1-2ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Jun 26 14:30:18 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
   libpng16-16 1.6.34-1
   zlib1g 1:1.2.11.dfsg-0ubuntu2
  DpkgTerminalLog:
   dpkg: erro ao processar o pacote libfreetype6:i386 (--configure):
O pacote está num mau estado de inconsistência; deve
reinstala-lo antes de tentar configura-lo.
  ErrorMessage: O pacote está num mau estado de inconsistência; deve  
reinstala-lo antes de tentar configura-lo.
  InstallationDate: Installed on 2018-05-16 (45 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: i386
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: freetype
  Title: package libfreetype6:i386 2.8.1-2ubuntu2 failed to install/upgrade: O 
pacote está num mau estado de inconsistência; deve  reinstala-lo antes de 
tentar configura-lo.
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1779497/+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 1847666] Re: Ubuntu doesn't cannot be suspended via the suspend icon after you log out.

[Dan Streetman]

did it work before you upgraded to 19.10?

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

Title:
  Ubuntu doesn't cannot be suspended via the suspend icon after you log
  out.

Status in systemd package in Ubuntu:
  New

Bug description:
  Pressing the suspend button in the top right menu when you are logged
  out doesn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-13-generic 5.3.0-13.14
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1766 F pulseaudio
lyubomir  18081 F pulseaudio
  Date: Thu Oct 10 23:15:08 2019
  HibernationDevice: RESUME=UUID=6f86efb8-0e86-4159-9412-28658da56f90
  InstallationDate: Installed on 2019-07-23 (78 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b5f7 Chicony Electronics Co., Ltd HD WebCam
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID :0538   USB OPTICAL MOUSE
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire A515-51G
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-13-generic N/A
   linux-backports-modules-5.3.0-13-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-09-27 (12 days ago)
  dmi.bios.date: 01/03/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.02
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Charmander_KL
  dmi.board.vendor: KBL
  dmi.board.version: V2.02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.02:bd01/03/2019:svnAcer:pnAspireA515-51G:pvrV2.02:rvnKBL:rnCharmander_KL:rvrV2.02:cvnAcer:ct10:cvrV2.02:
  dmi.product.family: Aspire 5
  dmi.product.name: Aspire A515-51G
  dmi.product.sku: 
  dmi.product.version: V2.02
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1847666/+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 608712] Re: In Ubuntu font, autohinted distance to diaeresis varies between letters

[Hugh McMaster]

** Changed in: freetype (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  In Ubuntu font, autohinted distance to diaeresis varies between
  letters

Status in freetype package in Ubuntu:
  Fix Released

Bug description:
  1. Load the attached HTML file in an app that uses the Ubuntu font's
  manual hinting.
  

  2. Load the same file in an app that uses the autohinter.

  What you see:

  1. At any size, the distance from any letter to its diaeresis is the
  same number of pixels.
  

  2. The distance from a letter to its diaeresis varies.
  

  What you should see:
  2. At any size, the distance from any letter to its diaeresis is the same 
number of pixels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/608712/+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 655619] Re: Auto-hinter muddles tildes/macrons in Ubuntu font <19px (ñĀÃāãŌÕōõ)

[Hugh McMaster]

No longer affected.

** Changed in: freetype (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Auto-hinter muddles tildes/macrons in Ubuntu font <19px (ñĀÃāãŌÕōõ)

Status in FreeType:
  Unknown
Status in freetype package in Ubuntu:
  Fix Released

Bug description:
  1. Copy and paste this line into the address field of a Web browser:
  data:text/html;charset=UTF-8,  
ñĀÃāãŌÕōõ

  2. Reduce the font-size until the tildes ˜ become indistinguishable
  from the macrons ¯.

  Rendered in 13pt Regular

  Sample Glyphs:

  õ

  Description:

  At size 18 and less õ looks o that doesn't have tilde but simple line
  on it. I don't know if it's a bug but there may be different similar
  letters in other languages. Õ is estonian font.

  UA String:

  Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.10) Gecko/20100915
  Ubuntu/10.04 (lucid) Firefox/3.6.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/freetype/+bug/655619/+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 1759836] Re: systemd-udevd consumes 100% of CPU due to hid2hci udev rule from bluez

[Dan Streetman]

nobody who has been affected by this bug is able to test on Bionic?

@stan are you able to test using Bionic by any chance?

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

Title:
  systemd-udevd consumes 100% of CPU due to hid2hci udev rule from bluez

Status in linux:
  Confirmed
Status in The Ubuntu Power Consumption Project:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in bluez source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Invalid
Status in bluez source package in Disco:
  Fix Released
Status in linux source package in Disco:
  Invalid
Status in systemd source package in Disco:
  Invalid
Status in bluez source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Invalid
Status in systemd source package in Eoan:
  Invalid
Status in bluez package in Debian:
  New

Bug description:
  [impact]

  on specific Dell systems, with a specific usb bluetooth device built-
  in, the udev rule 'hid2hci' provided by the 'bluez' package causes an
  endless loop of uevents resulting from 'bind' or 'unbind' kernel
  uevents.  These new events were added to the kernel after the
  'hid2hci' udev rule was written.

  [test case]

  the specific Dell system is required to be able to reproduce this, or
  at least the specific usb bluetooth hardware included in that system.

  Reproducing this is reportedly easy, for example comment 75 indicates
  it happens on every boot.

  When this happens, any process monitor (e.g. ps, top, etc) will show
  the 'udevd' process using 100% of a cpu, and 'udevadm monitor' should
  show repeated 'bind' and 'unbind' events as mentioned in comment 39.

  [regression potential]

  as this alters what kernel uevents the 'hid2hci' udev rule processes,
  regressions would involve the affected usb bluetooth device failing to
  be set up, or otherwise not processing the uevents correctly.

  [other info]

  this is not fixed yet upstream, as of my last check, but has been
  submitted upstream as mentioned in comment 95.

  
  original description:

  --

  
  The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not 
noticing any difference in my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 29 08:52:54 2018
  InstallationDate: Installed on 2018-03-05 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  MachineType: Dell Inc. Inspiron N5010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 08R0GW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel/+bug/1759836/+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 1848477] [NEW] Issue Screen Lenovo Miix320 (Intel GPU)

[Christian Diez Barceló]

Public bug reported:

La pantalla crashea al establecer la resolución en 1280x800 en el dispositivo 
Lenovo Miix 320 ICR.
Por defecto, se establece en una resolución de 800x1280, es decir, vertical. 
Sin embargo, para que antes llegue a mostrar algo en pantalla es necesario 
tener que entrar al modo supsensión nada más en el encendido. (Antes de iniciar 
sesión)
A partir del grub, tampoco muestra el logo de la diestro en cuestión 
(Independientemente de si es Ubuntu, Lubuntu, etc)
Una solución temporal, es poner la orientación en horizontal. Sin embargo, esto 
no cambia el lado de la tasa de refresco, con lo cual, es como si se 
actualizase "De lado".
Ésto da lugar a varios Gliches en la pantalla, bastante molestos a la hora de 
hacer desplazamientos horizontales.

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

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

Title:
  Issue Screen Lenovo Miix320 (Intel GPU)

Status in mesa package in Ubuntu:
  New

Bug description:
  La pantalla crashea al establecer la resolución en 1280x800 en el dispositivo 
Lenovo Miix 320 ICR.
  Por defecto, se establece en una resolución de 800x1280, es decir, vertical. 
  Sin embargo, para que antes llegue a mostrar algo en pantalla es necesario 
tener que entrar al modo supsensión nada más en el encendido. (Antes de iniciar 
sesión)
  A partir del grub, tampoco muestra el logo de la diestro en cuestión 
(Independientemente de si es Ubuntu, Lubuntu, etc)
  Una solución temporal, es poner la orientación en horizontal. Sin embargo, 
esto no cambia el lado de la tasa de refresco, con lo cual, es como si se 
actualizase "De lado".
  Ésto da lugar a varios Gliches en la pantalla, bastante molestos a la hora de 
hacer desplazamientos horizontales.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1848477/+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 1848476] [NEW] [ZenBook UX534FT_UX534FT, Realtek ALC294, Black Headphone Out, Left] No sound at all

[Daniela Rato]

Public bug reported:

Ubuntu 18.04.3 LTS
The sound works until I plug the headphones and then it never works again, even 
without them.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
Uname: Linux 5.3.6-050306-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  daniela2692 F pulseaudio
 /dev/snd/pcmC0D0c:   daniela2692 F...m pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 17 11:03:37 2019
InstallationDate: Installed on 2019-09-18 (28 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
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_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm1426 F pulseaudio
  daniela2692 F pulseaudio
Symptom_Jack: Black Headphone Out, Left
Symptom_Type: No sound at all
Title: [ZenBook UX534FT_UX534FT, Realtek ALC294, Black Headphone Out, Left] No 
sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/10/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX534FT.204
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX534FT
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.:bvrUX534FT.204:bd06/10/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX534FT_UX534FT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX534FT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ZenBook
dmi.product.name: ZenBook UX534FT_UX534FT
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug bionic

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

Title:
  [ZenBook UX534FT_UX534FT, Realtek ALC294, Black Headphone Out, Left]
  No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04.3 LTS
  The sound works until I plug the headphones and then it never works again, 
even without them.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 5.3.6-050306-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  daniela2692 F pulseaudio
   /dev/snd/pcmC0D0c:   daniela2692 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 11:03:37 2019
  InstallationDate: Installed on 2019-09-18 (28 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  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_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1426 F pulseaudio
daniela2692 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [ZenBook UX534FT_UX534FT, Realtek ALC294, Black Headphone Out, Left] 
No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX534FT.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX534FT
  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.:bvrUX534FT.204:bd06/10/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX534FT_UX534FT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX534FT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX534FT_UX534FT
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1848476/+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 1847967] Re: oem kernel packages treated differently from generic kernel ones

[You-Sheng Yang]

So before the merge proposal[1] is accepted, you can take following
steps to file a bug with all the information for kernel packages:

1. find out the source package name for the binary kernel package. It
should be "linux-signed-oem[-osp1]" for signed kernel packages, and
"linux-oem[-osp1]" for unsigned ones.

  $ apt show ${pkg} | grep ^Source:

2. create symlinks for apport:

  $ sudo ln -s source_linux.py /usr/share/apport/package-
hooks/source_${srcpkg}.py

3. appport-bug ${pkg}

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

Title:
  oem kernel packages treated differently from generic kernel ones

Status in OEM Priority Project:
  New
Status in apport package in Ubuntu:
  In Progress

Bug description:
  When `apport-bug linux` was executed on systems with linux-oem, linux-
  oem-osp1 kernels, many details are not included as generic linux
  kernel does. Alsa info, dmesg, lspci, lsusb, DMI, etc. are missing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1847967/+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 1715749] Re: Intermittent black screen on HP EliteBook 840 G1

[Ariane Dupont]

I have exactly the same problem too with the same computer. I also have
ubuntu on a dual boot with Windows.

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

Title:
  Intermittent black screen on HP EliteBook 840 G1

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Once every couple hours, the internal laptop display goes black for a
  few seconds.

  This was reproducible:
  + With the laptop connected to a port replicator and the external display 
connected into the port replicator DP port via DP-DVI adapter. The external 
display remains on during this time.
  + With the laptop not connected into a port replicator but connected to an 
external display. The external display remains on during this time.
  + With the laptop not connected to either a port replicator or an external 
display.

  The hard disk was originally installed with Ubuntu MATE 14.10 in a HP
  EliteBook 6930p, upgraded to 15.04, 15.10 and eventually 16.04 and
  finally moved to the EliteBook 840 G1. The problem started immediately
  after the drive move.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Sep  8 00:53:24 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-12-09 (1002 days ago)
  InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:198f]
  InstallationDate: Installed on 2014-12-09 (1158 days ago)
  InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023)
  MachineType: Hewlett-Packard HP EliteBook 840 G1
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-112-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-112-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/23/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.37
  dmi.board.name: 198F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.59
  dmi.chassis.asset.tag: CNU407CM0V
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.37:bd05/23/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 840 G1
  dmi.product.version: A3009DD10203
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1715749/+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 1654448] Re: Dell XPS 13 9350/9360 headphone audio hiss

[Daniel van Vugt]

** Changed in: linux (Ubuntu)
   Status: Won't Fix => In Progress

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

Title:
  Dell XPS 13 9350/9360 headphone audio hiss

Status in Dell Sputnik:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  
  When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears. 
  20.00, 20.00 cause a louder hiss and 
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1654448/+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 1654448] Re: Dell XPS 13 9350/9360 headphone audio hiss

[Kai-Heng Feng]

The fix is now in upstream. Please refer to the patch for justification:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=1099f48457d06b816359fb43ac32a4a07e33219b

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

Title:
  Dell XPS 13 9350/9360 headphone audio hiss

Status in Dell Sputnik:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Won't Fix
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  
  When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears. 
  20.00, 20.00 cause a louder hiss and 
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1654448/+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 1848200] Re: gdb not stopping on breakpoint in a 32-bit program

[Launchpad Bug Tracker]

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

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

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

Title:
  gdb not stopping on breakpoint in a 32-bit program

Status in gdb package in Ubuntu:
  Confirmed

Bug description:
  After upgrading gdb from 8.1-0ubuntu3 to 8.1-0ubuntu3.1, gdb does not
  stop on breakpoint when running a 32-bit application (on 64-bit
  Ubuntu). This can be reproduced with a simple “hello world” program:

  $ cat hello.c 
  #include 
  int main()
  {
 // printf() displays the string inside quotation
 printf("Hello, World!");
 return 0;
  }
  $ gcc -ggdb -m32 hello.c
  $ gdb a.out
  (gdb) b hello.c:5
  Breakpoint 1 at 0x536: file hello.c, line 5.
  (gdb) run
  Starting program: /home/user/sandbox/a.out 
  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.

  --- (and not stopping nor outputting the text…) ---

  It works well with a 64-bit build (leaving out the gcc’s -m32 option).

  This problem has been already discussed on:
  https://stackoverflow.com/questions/58225562/how-to-fix-hang-in-gdb-
  in-ld-linux-so-2-when-running-a-32-bit-executable-on-a-64

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdb 8.1-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
  Uname: Linux 4.15.0-65-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Oct 15 14:37:37 2019
  InstallationDate: Installed on 2015-12-08 (1407 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  SourcePackage: gdb
  UpgradeStatus: Upgraded to bionic on 2019-06-10 (127 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1848200/+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 1847980] Re: Lightdm is just a black screen when booting kernel 5.3 on an i5-6500, but kernels 5.0/5.2 work

[Kai-Heng Feng]

Would it be possible for you to do a kernel bisection?

First, find the last good -rc kernel and the first bad -rc kernel from
http://kernel.ubuntu.com/~kernel-ppa/mainline/

Then,
$ sudo apt build-dep linux
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
$ cd linux
$ git bisect start
$ git bisect good $(the good version you found)
$ git bisect bad $(the bad version found)
$ make localmodconfig
$ make -j`nproc` deb-pkg
Install the newly built kernel, then reboot with it.
If the issue still happens,
$ git bisect bad
Otherwise,
$ git bisect good
Repeat to "make -j`nproc` deb-pkg" until you find the commit that causes the 
regression.

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

Title:
  Lightdm is just a black screen when booting kernel 5.3 on an i5-6500,
  but kernels 5.0/5.2 work

Status in lightdm package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Xorg freeze at boot on Intel Corporation HD Graphics 530 with 
linux-image-5.3.0-17 after upgraded to the development release Ubuntu Eoan 
Ermine (development branch).
  If i boot with linux-image-5.0.0-31-generic the Xorg works well.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Oct 14 11:15:23 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:8054]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 047d:2048 Kensington Orbit Trackball with Scroll Ring
   Bus 001 Device 002: ID 04d9:a0cd Holtek Semiconductor, Inc. USB Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP EliteDesk 800 G2 SFF
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=714cc192-0d1c-4899-b891-16e6e504c662 ro 
resume=UUID=316a3e2d-ef98-4c31-8ba1-52e1cd0e8c05
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2019
  dmi.bios.vendor: HP
  dmi.bios.version: N01 Ver. 02.42
  dmi.board.name: 8054
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 05.36
  dmi.chassis.asset.tag: CZC64082W1
  dmi.chassis.type: 4
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN01Ver.02.42:bd08/19/2019:svnHP:pnHPEliteDesk800G2SFF:pvr:rvnHP:rn8054:rvrKBCVersion05.36:cvnHP:ct4:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP EliteDesk 800 G2 SFF
  dmi.product.sku: X3J10ET#ABZ
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:8054]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 047d:2048 Kensington Orbit Trackball with Scroll Ring
   Bus 001 Device 002: ID 04d9:a0cd Holtek Semiconductor, Inc. USB Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP EliteDesk 800 G2 SFF
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-17-generic 
root=UUID=714cc192-0d1c-4899-b891-16e6e504c662 ro 

[Touch-packages] [Bug 1843381] Re: Dell system takes a long time to connect network with external dock

[Che Cheng]

@ddstreet

Tested on bionic/disco/eoan. All of them do not rename the second usbnet
with MAC passthrough function, it keeps ifname eth0.

Thank you so much.

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

Title:
  Dell system takes a long time to connect network with external dock

Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Disco:
  In Progress
Status in systemd source package in Eoan:
  Invalid

Bug description:
  This is a bug reopen from
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1837700
  The original one caused systemd regressed.
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1842651

  This issue needs an alternative solution.
  

  Dell has a feature called MAC addrss passthrough[1] that would force usb 
ethernet adapters to be assigned with a predefined MAC address stored in BIOS 
or so. This feature has been landed to mainline kernel in driver r8152[2]. So 
whenever a r8152 managed device is plugged into Dell devices with MAC addrss 
passthrough enabled, this driver will set NIC MAC to a predefined one.

  And some Dell devices have already one built-in r8152 NIC port. On
  these devices, when a second r8152 NIC is plugged in, a Debian
  originated udev rules file 73-usb-net-by-mac.rules[3] will invoke udev
  built-in command `net_id` to give a persistent name, and that will be
  based on MAC address. However, since the system has already
  initialized the built-in r8152 NIC with that name, renaming the second
  interface with this name will always fail.

  While Debian still carries a patch called "Revert-udev-network-device-
  renaming-immediately-give.patch"[4] that tries to keep support of
  already deprecated "75-persistent-net-generator.rules" based interface
  renaming mechanism, this patch also propagated into Ubuntu[5]. This
  patch will retry renaming with a 90 seconds timeout when the error
  code is -EEXIST, so the uevent processing will always be blocked in
  the last ifrename step in the victim system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: udev 237-3ubuntu10.24 [modified: lib/udev/rules.d/50-firmware.rules 
lib/udev/rules.d/50-udev-default.rules 
lib/udev/rules.d/73-special-net-names.rules 
lib/udev/rules.d/73-usb-net-by-mac.rules]
  ProcVersionSignature: Ubuntu 4.15.0-1043.48-oem 4.15.18
  Uname: Linux 4.15.0-1043-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.core.rules 95-oem-hotkey-osd.rules
  Date: Wed Jul 24 15:30:59 2019
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-jorah+X90
  InstallationDate: Installed on 2019-07-03 (20 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Latitude 7424 Rugged Extreme
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1043-oem.efi.signed 
root=UUID=5da90c85-3500-49a2-b989-71a604f9eec4 ro mem_sleep_default=deep quiet 
splash systemd.log_level=debug udev.log-priority=debug log_buf_len=8M 
vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/27/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0Y7FK3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X03
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd05/27/2019:svnDellInc.:pnLatitude7424RuggedExtreme:pvr:rvnDellInc.:rn0Y7FK3:rvrX03:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7424 Rugged Extreme
  dmi.sys.vendor: Dell Inc.

  [1]: 
https://www.dell.com/support/article/tw/zh/twdhs1/sln301147/what-is-mac-address-pass-through?lang=en
  [2]: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/usb/r8152.c
  [3]: 
https://salsa.debian.org/systemd-team/systemd/blob/master/debian/extra/rules/73-usb-net-by-mac.rules
  [4]: 
https://salsa.debian.org/systemd-team/systemd/blob/master/debian/patches/debian/Revert-udev-network-device-renaming-immediately-give.patch
  [5]: 
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/tree/debian/patches/debian/Revert-udev-network-device-renaming-immediately-give.patch?h=ubuntu-bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1843381/+subscriptions

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

[Touch-packages] [Bug 1847967] Re: oem kernel packages treated differently from generic kernel ones

[You-Sheng Yang]

Maybe the best solution is to install such links in every kernel related
source packages built kernel image packages themselves. :X

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

Title:
  oem kernel packages treated differently from generic kernel ones

Status in OEM Priority Project:
  New
Status in apport package in Ubuntu:
  In Progress

Bug description:
  When `apport-bug linux` was executed on systems with linux-oem, linux-
  oem-osp1 kernels, many details are not included as generic linux
  kernel does. Alsa info, dmesg, lspci, lsusb, DMI, etc. are missing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1847967/+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 1847967] Re: oem kernel packages treated differently from generic kernel ones

[You-Sheng Yang]

--- debian/apport.links 2018-05-09 23:42:20 +
+++ debian/apport.links 2019-10-17 06:20:03 +
@@ -1,4 +1,10 @@
+/usr/share/apport/package-hooks/source_linux.py 
/usr/share/apport/package-hooks/source_linux-meta-oem-osp1.py
+/usr/share/apport/package-hooks/source_linux.py 
/usr/share/apport/package-hooks/source_linux-meta-oem.py
 /usr/share/apport/package-hooks/source_linux.py 
/usr/share/apport/package-hooks/source_linux-meta.py
+/usr/share/apport/package-hooks/source_linux.py 
/usr/share/apport/package-hooks/source_linux-oem-osp1.py
+/usr/share/apport/package-hooks/source_linux.py 
/usr/share/apport/package-hooks/source_linux-oem.py
+/usr/share/apport/package-hooks/source_linux.py 
/usr/share/apport/package-hooks/source_linux-signed-oem-osp1.py
+/usr/share/apport/package-hooks/source_linux.py 
/usr/share/apport/package-hooks/source_linux-signed-oem.py
 /usr/share/apport/package-hooks/source_linux.py 
/usr/share/apport/package-hooks/source_linux-signed.py
 /usr/bin/apport-bug /usr/bin/ubuntu-bug
 /usr/share/man/man1/apport-bug.1.gz /usr/share/man/man1/ubuntu-bug.1.gz

** Branch linked: lp:~vicamo/ubuntu/eoan/apport/bug-1847967

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

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

Title:
  oem kernel packages treated differently from generic kernel ones

Status in OEM Priority Project:
  New
Status in apport package in Ubuntu:
  In Progress

Bug description:
  When `apport-bug linux` was executed on systems with linux-oem, linux-
  oem-osp1 kernels, many details are not included as generic linux
  kernel does. Alsa info, dmesg, lspci, lsusb, DMI, etc. are missing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1847967/+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 1831252] Re: panic=-1 is completely ignored by the initrd causing unexpected behaviour

[Mathew Hodson]

** Changed in: initramfs-tools (Ubuntu Disco)
   Importance: Undecided => Medium

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

Title:
  panic=-1 is completely ignored by the initrd causing unexpected
  behaviour

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Bionic:
  Fix Committed
Status in initramfs-tools source package in Disco:
  Fix Committed
Status in initramfs-tools source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  in Ubuntu Core we default to using panic=-1 on the kernel command line 
(documented at [1]) to speed up the auto-rollback mechanism of the kernel. on a 
kernel level this works just fine and the system reboots immediately ...

  when in the initramfs during boot and a panic occurs, no reboot
  happens at all, the initrd spawns a shell regardless of the panic=
  value ...

  
  [Test case]

  Before booting change root=$foo to root=x$foo - this will make it
  panic. Then test that

  1) "panic=-1" causes an immediate reboot
  2) "panic=5" waits 5 seconds
  3) no "panic" drops you to a shell

  [Regression potential]
  This adds some very specific checks for -1 in places that use ${panic}, as 
such the regression potential is somewhat limited. If there were a regression, 
it could be a syntax error (causing boot to fail) or a sleep not working 
correctly (causing sleep to, well, not sleep) - but that's unrealistic.

  
  [Other info]
  this is caused by a filter in  /usr/share/initramfs-tools/init

  panic=*)
  panic="${x#panic=}"
  case ${panic} in
  *[![:digit:].]*)
  panic=
  ;;
  esac
  ;;

  this function only lets positive values through, else panic= simply
  gets unset

  the panic() function itself is also not capable of handling negative
  values, it has a sleep call that interprets negative values as
  commandline options instead of simply ignoring a negative sleep time
  [2] (line 11).

  the filter in the init script should allow the -1 value (to comply
  with the kernel documentation and behaviour) and the panic() function
  should properly skip the sleep call when a negative value for panic=
  is set.

  [1] 
https://github.com/torvalds/linux/blob/v4.17/Documentation/admin-guide/kernel-parameters.txt#L2931
  [2] https://paste.ubuntu.com/p/mswD8Cd869/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1831252/+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 1846140] Re: Realtek RTL8723BU doesn't work well in ubuntu

[Kai-Heng Feng]

It's in linux-next but not in mainline yet.

https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
next.git/commit/?id=a9bb0b51577835d26054d080c59935be8b7e44f4

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

Title:
  Realtek RTL8723BU doesn't work well in ubuntu

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  I have one laptop with Realtek RTL8723BU wifi card. It runs, but
  signal is weak (it only works if the router is less than a meter
  away), and even if it gets signal it's slow and it gets interrupted
  frequently. In windows it works normally, and with a much stronger
  signal. I tested it on Ubuntu 18.04.3 and 19.04.

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