[Touch-packages] [Bug 1846290] [NEW] Ubuntu 19.10 incorrectly selects audio output source

[Bickhaus]

Public bug reported:

I have two monitors hooked up to an AMD RX570 via displayport.  In the
sound settings they appear as "Ellesmere HDMI Audio [Radeon RX
470/480/560/570/580/590]" and Ubuntu 19.10 selected one of them as the
output device by default.  My speakers are connected to a green mini-
jack line out jack on the motherboard.  Switching to line out gives me
sound, and I have no other issues.

Originally, I had upgraded to the beta from the command line in 19.04.
I had not experienced this issue in 19.04, but upon first booting into
19.10, I had to switch output device back to line out.  A fresh install
of the beta iso gave the same result (one of my monitors connected to my
video card was selected by default).  Note that my monitors are Dell
U2415s but they do have line out jacks.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
Uname: Linux 5.3.0-13-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  bick   1719 F pulseaudio
 /dev/snd/controlC0:  bick   1719 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct  2 00:19:28 2019
InstallationDate: Installed on 2019-10-02 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
PackageArchitecture: all
ProcEnviron:
 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:HDMI failed
Symptom_Card: Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590] - HDA ATI 
HDMI
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  bick   1719 F pulseaudio
 /dev/snd/controlC0:  bick   1719 F pulseaudio
Symptom_Jack: Digital Out, HDMI
Symptom_Type: No sound at all
Title: [System Product Name, ATI R6xx HDMI, Digital Out, HDMI] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/12/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1820
dmi.board.asset.tag: Default string
dmi.board.name: PRIME B450-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1820:bd09/12/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug eoan 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/1846290

Title:
  Ubuntu 19.10 incorrectly selects audio output source

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I have two monitors hooked up to an AMD RX570 via displayport.  In the
  sound settings they appear as "Ellesmere HDMI Audio [Radeon RX
  470/480/560/570/580/590]" and Ubuntu 19.10 selected one of them as the
  output device by default.  My speakers are connected to a green mini-
  jack line out jack on the motherboard.  Switching to line out gives me
  sound, and I have no other issues.

  Originally, I had upgraded to the beta from the command line in 19.04.
  I had not experienced this issue in 19.04, but upon first booting into
  19.10, I had to switch output device back to line out.  A fresh
  install of the beta iso gave the same result (one of my monitors
  connected to my video card was selected by default).  Note that my
  monitors are Dell U2415s but they do have line out jacks.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bick   1719 F pulseaudio
   /dev/snd/controlC0:  bick   1719 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  2 00:19:28 2019
  InstallationDate: Installed on 2019-10-02 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  PackageArchitecture: all
  ProcEnviron:
   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:HDMI failed
  Symptom_Card: Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590] - HDA 
ATI HDMI
  Symp

[Touch-packages] [Bug 1293950] Re: [enhancement] Add support for deep color

[Daniel van Vugt]

Continued in bug 1844775.

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

Title:
  [enhancement] Add support for deep color

Status in Mir:
  Triaged
Status in mir package in Ubuntu:
  Triaged

Bug description:
  It would be nice to eventually add support for deep color. That is
  30-bit or higher color depths. I suspect doing so would require work
  both in the server and clients (new pixel formats).

  http://en.wikipedia.org/wiki/Color_depth#Deep_color_.2830.2F36.2F48-bit.29

  See also related bug 1212753, which I suspect could be solved by
  adding high colour support.

  See also bug 1469673 which is about high colour.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1293950/+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 1844775] Re: HDR support for Ubuntu 20.04

[Daniel van Vugt]

Note that "HDR" and deep colour (any colour depth higher than 8-bit) are
two different things.

It sounds like some of the above links refer to deep colour support and
others refer to HDR. We should clarify which this bug is about (or that
it really is about both disparate issues).

For regular desktop usage I think deep colour support is more important
(and should come first), as first mentioned in bug 1293950.

** Changed in: mutter (Ubuntu)
   Importance: Undecided => Medium

** Changed in: mutter (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  HDR support for Ubuntu 20.04

Status in ffmpeg package in Ubuntu:
  Fix Released
Status in intel-media-driver package in Ubuntu:
  Fix Released
Status in libva package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Triaged
Status in weston package in Ubuntu:
  Confirmed

Bug description:
  This is a tracker bug for getting HDR support integrated in Ubuntu.

  Kernel
  i915:
  - 5.3 (Ice Lake)
  - plus at least https://patchwork.freedesktop.org/series/65656/
  - gen4+ needs https://patchwork.freedesktop.org/series/63373/
  - so anything beyond initial Ice Lake support will not be in 5.4

  Mesa
  - needs current git master plus
  https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1942

  Mutter:
  https://gitlab.gnome.org/GNOME/mutter/merge_requests/804

  Weston:
  
https://gitlab.freedesktop.org/ajax/weston/commit/591c95ddeb67324778cbbb5d0102bdd1a1721d99

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1844775/+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 1846284] Re: UDEV Symlink Not Created In 19.10

[Jean-Baptiste Lallement]

Thanks for your report.

This is a change in sysdtemd

systemd (242-6ubuntu1) eoan; urgency=medium

[...]
  * Drop /sbin/udevadm compat symlink (Closes: #852580)


Do you have a list of applications this change broke? A bug task should be 
added for each one.

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

** Package changed: udev (Ubuntu) => systemd (Ubuntu)

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

Title:
  UDEV Symlink Not Created In 19.10

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Upon upgrade from 19.04 to 19.10, the symlink for udev is broken.

  /sbin/udevadm should link to /bin/udev

  It doesn't.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  Date: Tue Oct  1 19:53:28 2019
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to eoan on 2019-09-29 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz:
   Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  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/systemd/+bug/1846284/+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 1846284] [NEW] UDEV Symlink Not Created In 19.10

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Upon upgrade from 19.04 to 19.10, the symlink for udev is broken.

/sbin/udevadm should link to /bin/udev

It doesn't.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: ubuntu-release-upgrader-core 1:19.10.12
ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
Uname: Linux 5.3.0-13-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CrashDB: ubuntu
Date: Tue Oct  1 19:53:28 2019
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: Upgraded to eoan on 2019-09-29 (2 days ago)
VarLogDistupgradeAptclonesystemstate.tar.gz:
 Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
 Error executing command as another user: Not authorized
 
 This incident has been reported.
VarLogDistupgradeXorgFixuplog:
 INFO:root:/usr/bin/do-release-upgrade running
 INFO:root:No xorg.conf, exiting

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


** Tags: amd64 apport-bug dist-upgrade eoan uec-images
-- 
UDEV Symlink Not Created In 19.10
https://bugs.launchpad.net/bugs/1846284
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd 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 1844132] Re: FFe: Mesa 19.2.0

[Launchpad Bug Tracker]

This bug was fixed in the package mesa - 19.2.0-1ubuntu1

---
mesa (19.2.0-1ubuntu1) eoan; urgency=medium

  * Merge from Debian.

 -- Timo Aaltonen   Tue, 01 Oct 2019 16:16:29 +0300

** Changed in: mesa (Ubuntu Eoan)
   Status: Confirmed => Fix Released

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

Title:
  FFe: Mesa 19.2.0

Status in libclc package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in libclc source package in Eoan:
  Fix Released
Status in mesa source package in Eoan:
  Fix Released

Bug description:
  It would be great to get 19.2.0 in eoan, though it's release cycle has
  slipped. It's working fine on a typical desktop use here on i915 (Kaby
  Lake). It would also migrate to llvm-9.

  It is currently at rc3, and final version is expected to arrive next
  week (week 39).

  New features:

  Full support for Intel Ice Lake
  Support for AMD Navi

  GL_ARB_post_depth_coverage on radeonsi (Navi)
  GL_ARB_seamless_cubemap_per_texture on etnaviv (if GPU supports 
SEAMLESS_CUBE_MAP)
  GL_EXT_shader_image_load_store on radeonsi (with LLVM >= 10)
  GL_EXT_shader_samples_identical on iris and radeonsi (if using NIR)
  GL_EXT_texture_shadow_lod on i965, iris
  EGL_EXT_platform_device
  VK_AMD_buffer_marker on radv
  VK_EXT_index_type_uint8 on radv
  VK_EXT_post_depth_coverage on radv
  VK_EXT_queue_family_foreign on radv
  VK_EXT_sample_locations on radv
  VK_EXT_shader_demote_to_helper_invocation on Intel.
  VK_KHR_depth_stencil_resolve on radv
  VK_KHR_imageless_framebuffer on radv
  VK_KHR_shader_atomic_int64 on radv
  VK_KHR_uniform_buffer_standard_layout on radv

  (note: iris is the new DRI driver for newer Intel, not enabled by
  default yet)

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

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

[Touch-packages] [Bug 1845046] Re: [WH-1000XM3, playback] Hearing input and output audio until disconnecting and reconnecting

[Daniel van Vugt]

Ignore the above "Fix Released". That's just a Launchpad issue where it
can't tell the reason for an upstream bug being closed. In fact that
user just gave up and closed their own bug.

I've confirmed the problem exists in both 18.04 and 19.10 today.

** Tags added: disco eoan

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

Title:
  [WH-1000XM3, playback] Hearing input and output audio until
  disconnecting and reconnecting

Status in PulseAudio:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

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

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

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

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

[Touch-packages] [Bug 1845046] Re: [WH-1000XM3, playback] Hearing input and output audio until disconnecting and reconnecting

[Launchpad Bug Tracker]

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

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

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

Title:
  [WH-1000XM3, playback] Hearing input and output audio until
  disconnecting and reconnecting

Status in PulseAudio:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

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

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

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

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

[Touch-packages] [Bug 1845046] Re: [WH-1000XM3, playback] Hearing input and output audio until disconnecting and reconnecting

[Launchpad Bug Tracker]

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

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Confirmed

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

Title:
  [WH-1000XM3, playback] Hearing input and output audio until
  disconnecting and reconnecting

Status in PulseAudio:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

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

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

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

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

[Touch-packages] [Bug 1845046] Re: [WH-1000XM3, playback] Hearing input and output audio until disconnecting and reconnecting

[Bug Watch Updater]

** Changed in: pulseaudio
   Status: Unknown => Fix Released

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

Title:
  [WH-1000XM3, playback] Hearing input and output audio until
  disconnecting and reconnecting

Status in PulseAudio:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

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

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

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

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

[Touch-packages] [Bug 1846232] Re: vmtests: test_ip_output failing in vlan tests on eoan

[Ryan Harper]

This looks to be related to networkd:

https://github.com/systemd/systemd/pull/12574/commits

Which is automatically added 4 bytes to base interface MTU, even though
we're explicitly setting mtu to 1500 on base interface and vlan.


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

** Changed in: curtin
   Status: New => Invalid

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

Title:
  vmtests: test_ip_output failing in vlan tests on eoan

Status in curtin:
  Invalid
Status in systemd package in Ubuntu:
  New

Bug description:
  From https://jenkins.ubuntu.com/server/job/curtin-vmtest-devel-
  amd64/916/console:

  ==
  FAIL: test_ip_output (vmtests.test_network_vlan.EoanTestNetworkVlan)
  --
  Traceback (most recent call last):
File 
"/var/lib/jenkins/servers/server/workspace/curtin-vmtest-devel-amd64/curtin-916/tests/vmtests/test_network.py",
 line 311, in test_ip_output
  routes)
File 
"/var/lib/jenkins/servers/server/workspace/curtin-vmtest-devel-amd64/curtin-916/tests/vmtests/test_network.py",
 line 337, in check_interface
  int(ipcfg[key]))
  AssertionError: 1500 != 1504
   >> begin captured stdout << -
  parsed ip_a dict:
  interface0:
  broadcast: 10.245.175.255
  group: default
  inet4:
  -   address: 10.245.168.16
  prefixlen: '21'
  scope: global
  valid_lft: forever
  inet6:
  -   address: fec0::d6be:d9ff:fea8:4913
  prefixlen: '64'
  scope: site
  valid_lft: 86256sec
  -   address: fe80::d6be:d9ff:fea8:4913
  prefixlen: '64'
  scope: link
  valid_lft: forever
  interface: interface0
  loopback: false
  lower_up: false
  mac_address: d4:be:d9:a8:49:13
  mtu: '1500'
  multicast: false
  qdisc: fq_codel
  qlen: '1000'
  running: false
  state: UP
  up: false
  interface1:
  broadcast: 10.245.188.255
  group: default
  inet4:
  -   address: 10.245.188.2
  prefixlen: '24'
  scope: global
  valid_lft: forever
  inet6:
  -   address: fec0::d6be:d9ff:fea8:4915
  prefixlen: '64'
  scope: site
  valid_lft: 86256sec
  -   address: fe80::d6be:d9ff:fea8:4915
  prefixlen: '64'
  scope: link
  valid_lft: forever
  interface: interface1
  loopback: false
  lower_up: false
  mac_address: d4:be:d9:a8:49:15
  mtu: '1504'
  multicast: false
  qdisc: fq_codel
  qlen: '1000'
  running: false
  state: UP
  up: false
  interface1.2667:
  broadcast: 10.245.184.255
  group: default
  inet4:
  -   address: 10.245.184.2
  prefixlen: '24'
  scope: global
  valid_lft: forever
  inet6:
  -   address: fe80::d6be:d9ff:fea8:4915
  prefixlen: '64'
  scope: link
  valid_lft: forever
  interface: interface1.2667
  loopback: false
  lower_up: false
  mac_address: d4:be:d9:a8:49:15
  mtu: '1500'
  multicast: false
  qdisc: noqueue
  qlen: '1000'
  running: false
  state: UP
  up: false
  vlan_link: interface1
  interface1.2668:
  broadcast: 10.245.185.255
  group: default
  inet4:
  -   address: 10.245.185.1
  prefixlen: '24'
  scope: global
  valid_lft: forever
  inet6:
  -   address: fe80::d6be:d9ff:fea8:4915
  prefixlen: '64'
  scope: link
  valid_lft: forever
  interface: interface1.2668
  loopback: false
  lower_up: false
  mac_address: d4:be:d9:a8:49:15
  mtu: '1500'
  multicast: false
  qdisc: noqueue
  qlen: '1000'
  running: false
  state: UP
  up: false
  vlan_link: interface1
  interface1.2669:
  broadcast: 10.245.186.255
  group: default
  inet4:
  -   address: 10.245.186.1
  prefixlen: '24'
  scope: global
  valid_lft: forever
  inet6:
  -   address: fe80::d6be:d9ff:fea8:4915
  prefixlen: '64'
  scope: link
  valid_lft: forever
  interface: interface1.2669
  loopback: false
  lower_up: false
  mac_address: d4:be:d9:a8:49:15
  mtu: '1500'
  multicast: false
  qdisc: noqueue
  qlen: '1000'
  running: false
  state: UP
  up: false
  vlan_link: interface1
  interface1.2670:
  broadcast: 10.245.187.255
  group: default
  inet4:
  -   address: 10.245.187.2
  prefixlen: '24'
  scope: global
  valid_lft: forever
  inet6:
  -   address: fe80::d6be:d9ff:fea8:4915
  prefixlen: '64'
   

[Touch-packages] [Bug 1846232] Re: vmtests: test_ip_output failing in vlan tests on eoan

[Ryan Harper]

This can be reproduced in an LXD Eoan container:

lxc launch ubuntu-daily:eoan e1
lxc exec e1
cat > /etc/netplan/50-cloud-init.yaml << EOF
network:
version: 2
ethernets:
eth0:
dhcp4: false
mtu: 1500
vlans:
eth0.2667:
id: 2667
addresses: [10.22.33.2/24]
link: eth0
mtu: 1500
EOF
reboot
lxc exec e1 bash
cloud-init status --wait
ip link show eth0

And this is not an issue in Disco 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/1846232

Title:
  vmtests: test_ip_output failing in vlan tests on eoan

Status in curtin:
  Invalid
Status in systemd package in Ubuntu:
  New

Bug description:
  From https://jenkins.ubuntu.com/server/job/curtin-vmtest-devel-
  amd64/916/console:

  ==
  FAIL: test_ip_output (vmtests.test_network_vlan.EoanTestNetworkVlan)
  --
  Traceback (most recent call last):
File 
"/var/lib/jenkins/servers/server/workspace/curtin-vmtest-devel-amd64/curtin-916/tests/vmtests/test_network.py",
 line 311, in test_ip_output
  routes)
File 
"/var/lib/jenkins/servers/server/workspace/curtin-vmtest-devel-amd64/curtin-916/tests/vmtests/test_network.py",
 line 337, in check_interface
  int(ipcfg[key]))
  AssertionError: 1500 != 1504
   >> begin captured stdout << -
  parsed ip_a dict:
  interface0:
  broadcast: 10.245.175.255
  group: default
  inet4:
  -   address: 10.245.168.16
  prefixlen: '21'
  scope: global
  valid_lft: forever
  inet6:
  -   address: fec0::d6be:d9ff:fea8:4913
  prefixlen: '64'
  scope: site
  valid_lft: 86256sec
  -   address: fe80::d6be:d9ff:fea8:4913
  prefixlen: '64'
  scope: link
  valid_lft: forever
  interface: interface0
  loopback: false
  lower_up: false
  mac_address: d4:be:d9:a8:49:13
  mtu: '1500'
  multicast: false
  qdisc: fq_codel
  qlen: '1000'
  running: false
  state: UP
  up: false
  interface1:
  broadcast: 10.245.188.255
  group: default
  inet4:
  -   address: 10.245.188.2
  prefixlen: '24'
  scope: global
  valid_lft: forever
  inet6:
  -   address: fec0::d6be:d9ff:fea8:4915
  prefixlen: '64'
  scope: site
  valid_lft: 86256sec
  -   address: fe80::d6be:d9ff:fea8:4915
  prefixlen: '64'
  scope: link
  valid_lft: forever
  interface: interface1
  loopback: false
  lower_up: false
  mac_address: d4:be:d9:a8:49:15
  mtu: '1504'
  multicast: false
  qdisc: fq_codel
  qlen: '1000'
  running: false
  state: UP
  up: false
  interface1.2667:
  broadcast: 10.245.184.255
  group: default
  inet4:
  -   address: 10.245.184.2
  prefixlen: '24'
  scope: global
  valid_lft: forever
  inet6:
  -   address: fe80::d6be:d9ff:fea8:4915
  prefixlen: '64'
  scope: link
  valid_lft: forever
  interface: interface1.2667
  loopback: false
  lower_up: false
  mac_address: d4:be:d9:a8:49:15
  mtu: '1500'
  multicast: false
  qdisc: noqueue
  qlen: '1000'
  running: false
  state: UP
  up: false
  vlan_link: interface1
  interface1.2668:
  broadcast: 10.245.185.255
  group: default
  inet4:
  -   address: 10.245.185.1
  prefixlen: '24'
  scope: global
  valid_lft: forever
  inet6:
  -   address: fe80::d6be:d9ff:fea8:4915
  prefixlen: '64'
  scope: link
  valid_lft: forever
  interface: interface1.2668
  loopback: false
  lower_up: false
  mac_address: d4:be:d9:a8:49:15
  mtu: '1500'
  multicast: false
  qdisc: noqueue
  qlen: '1000'
  running: false
  state: UP
  up: false
  vlan_link: interface1
  interface1.2669:
  broadcast: 10.245.186.255
  group: default
  inet4:
  -   address: 10.245.186.1
  prefixlen: '24'
  scope: global
  valid_lft: forever
  inet6:
  -   address: fe80::d6be:d9ff:fea8:4915
  prefixlen: '64'
  scope: link
  valid_lft: forever
  interface: interface1.2669
  loopback: false
  lower_up: false
  mac_address: d4:be:d9:a8:49:15
  mtu: '1500'
  multicast: false
  qdisc: noqueue
  qlen: '1000'
  running: false
  state: UP
  up: false
  vlan_link: interface1
  interface1.2670:
  broadcast: 10.245.187.255
  group: default
  inet4:
  -   address: 10.245.187.2
  prefixlen: '24'
  scope: gl

[Touch-packages] [Bug 1846232] Re: vmtests: test_ip_output failing in vlan tests on eoan

[Ryan Harper]

@Dan/Chad  I suggest we skip-by this bug number on the eoan vlan test
case;

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

Title:
  vmtests: test_ip_output failing in vlan tests on eoan

Status in curtin:
  Invalid
Status in systemd package in Ubuntu:
  New

Bug description:
  From https://jenkins.ubuntu.com/server/job/curtin-vmtest-devel-
  amd64/916/console:

  ==
  FAIL: test_ip_output (vmtests.test_network_vlan.EoanTestNetworkVlan)
  --
  Traceback (most recent call last):
File 
"/var/lib/jenkins/servers/server/workspace/curtin-vmtest-devel-amd64/curtin-916/tests/vmtests/test_network.py",
 line 311, in test_ip_output
  routes)
File 
"/var/lib/jenkins/servers/server/workspace/curtin-vmtest-devel-amd64/curtin-916/tests/vmtests/test_network.py",
 line 337, in check_interface
  int(ipcfg[key]))
  AssertionError: 1500 != 1504
   >> begin captured stdout << -
  parsed ip_a dict:
  interface0:
  broadcast: 10.245.175.255
  group: default
  inet4:
  -   address: 10.245.168.16
  prefixlen: '21'
  scope: global
  valid_lft: forever
  inet6:
  -   address: fec0::d6be:d9ff:fea8:4913
  prefixlen: '64'
  scope: site
  valid_lft: 86256sec
  -   address: fe80::d6be:d9ff:fea8:4913
  prefixlen: '64'
  scope: link
  valid_lft: forever
  interface: interface0
  loopback: false
  lower_up: false
  mac_address: d4:be:d9:a8:49:13
  mtu: '1500'
  multicast: false
  qdisc: fq_codel
  qlen: '1000'
  running: false
  state: UP
  up: false
  interface1:
  broadcast: 10.245.188.255
  group: default
  inet4:
  -   address: 10.245.188.2
  prefixlen: '24'
  scope: global
  valid_lft: forever
  inet6:
  -   address: fec0::d6be:d9ff:fea8:4915
  prefixlen: '64'
  scope: site
  valid_lft: 86256sec
  -   address: fe80::d6be:d9ff:fea8:4915
  prefixlen: '64'
  scope: link
  valid_lft: forever
  interface: interface1
  loopback: false
  lower_up: false
  mac_address: d4:be:d9:a8:49:15
  mtu: '1504'
  multicast: false
  qdisc: fq_codel
  qlen: '1000'
  running: false
  state: UP
  up: false
  interface1.2667:
  broadcast: 10.245.184.255
  group: default
  inet4:
  -   address: 10.245.184.2
  prefixlen: '24'
  scope: global
  valid_lft: forever
  inet6:
  -   address: fe80::d6be:d9ff:fea8:4915
  prefixlen: '64'
  scope: link
  valid_lft: forever
  interface: interface1.2667
  loopback: false
  lower_up: false
  mac_address: d4:be:d9:a8:49:15
  mtu: '1500'
  multicast: false
  qdisc: noqueue
  qlen: '1000'
  running: false
  state: UP
  up: false
  vlan_link: interface1
  interface1.2668:
  broadcast: 10.245.185.255
  group: default
  inet4:
  -   address: 10.245.185.1
  prefixlen: '24'
  scope: global
  valid_lft: forever
  inet6:
  -   address: fe80::d6be:d9ff:fea8:4915
  prefixlen: '64'
  scope: link
  valid_lft: forever
  interface: interface1.2668
  loopback: false
  lower_up: false
  mac_address: d4:be:d9:a8:49:15
  mtu: '1500'
  multicast: false
  qdisc: noqueue
  qlen: '1000'
  running: false
  state: UP
  up: false
  vlan_link: interface1
  interface1.2669:
  broadcast: 10.245.186.255
  group: default
  inet4:
  -   address: 10.245.186.1
  prefixlen: '24'
  scope: global
  valid_lft: forever
  inet6:
  -   address: fe80::d6be:d9ff:fea8:4915
  prefixlen: '64'
  scope: link
  valid_lft: forever
  interface: interface1.2669
  loopback: false
  lower_up: false
  mac_address: d4:be:d9:a8:49:15
  mtu: '1500'
  multicast: false
  qdisc: noqueue
  qlen: '1000'
  running: false
  state: UP
  up: false
  vlan_link: interface1
  interface1.2670:
  broadcast: 10.245.187.255
  group: default
  inet4:
  -   address: 10.245.187.2
  prefixlen: '24'
  scope: global
  valid_lft: forever
  inet6:
  -   address: fe80::d6be:d9ff:fea8:4915
  prefixlen: '64'
  scope: link
  valid_lft: forever
  interface: interface1.2670
  loopback: false
  lower_up: false
  mac_address: d4:be:d9:a8:49:15
  mtu: '1500'
  multicast: false
  qdisc: noqueue
  qlen: '1000'
  running: false
  state: UP
  up: fa

[Touch-packages] [Bug 1846201] Re: Rendering is delayed on laptop display (works in external display)

[Daniel van Vugt]

Possibly also related - Xrandr.txt strangely doesn't list any viewport
dimensions for the laptop display eDP-1.


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

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

Title:
   Rendering is delayed on laptop display (works in external display)

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

Bug description:
  This is a very wierd behavior I get on the Lenovo Yoga S940 after upgrading 
to 19.10.
  This makes the laptop almost unusable with its own display.
  This happens only on the laptop display, not on the external display.

  
  The render of portions of the screen does not happen after some events 
(listed below) resulting in all or part of the screen not being re-rendered. 
The UX is that nothing happened, but it has. 
  This happens after:

  * key-stroke while typing sometimes
  * alt-tab
  * shift-right to align window to the right
  * ctrl-pgup/down to switch tab in multi tabs apps. 

  
  Please note that:
  * screenshots can't see the problem
  * also screenrecorder always seem ok, despite rendering being broken.


  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  1 13:13:40 2019
  DistUpgraded: 2019-09-21 10:16:26,647 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:3801]
  InstallationDate: Installed on 2019-09-12 (18 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 81Q7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-09-21 (10 days ago)
  dmi.bios.date: 06/12/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AKCN34WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga S940-14IWL
  dmi.modalias: 
dmi:bvnLENOVO:bvrAKCN34WW:bd06/12/2019:svnLENOVO:pn81Q7:pvrLenovoYogaS940-14IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS940-14IWL:
  dmi.product.family: Yoga S940-14IWL
  dmi.product.name: 81Q7
  dmi.product.sku: LENOVO_MT_81Q7_BU_idea_FM_Yoga S940-14IWL
  dmi.product.version: Lenovo Yoga S940-14IWL
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1846201/+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 1846201] Re: Rendering is delayed on laptop display (works in external display)

[Daniel van Vugt]

Also, does the bug occur if you log into 'Ubuntu on Wayland' ?

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

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

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

Title:
   Rendering is delayed on laptop display (works in external display)

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

Bug description:
  This is a very wierd behavior I get on the Lenovo Yoga S940 after upgrading 
to 19.10.
  This makes the laptop almost unusable with its own display.
  This happens only on the laptop display, not on the external display.

  
  The render of portions of the screen does not happen after some events 
(listed below) resulting in all or part of the screen not being re-rendered. 
The UX is that nothing happened, but it has. 
  This happens after:

  * key-stroke while typing sometimes
  * alt-tab
  * shift-right to align window to the right
  * ctrl-pgup/down to switch tab in multi tabs apps. 

  
  Please note that:
  * screenshots can't see the problem
  * also screenrecorder always seem ok, despite rendering being broken.


  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  1 13:13:40 2019
  DistUpgraded: 2019-09-21 10:16:26,647 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:3801]
  InstallationDate: Installed on 2019-09-12 (18 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 81Q7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-09-21 (10 days ago)
  dmi.bios.date: 06/12/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AKCN34WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga S940-14IWL
  dmi.modalias: 
dmi:bvnLENOVO:bvrAKCN34WW:bd06/12/2019:svnLENOVO:pn81Q7:pvrLenovoYogaS940-14IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS940-14IWL:
  dmi.product.family: Yoga S940-14IWL
  dmi.product.name: 81Q7
  dmi.product.sku: LENOVO_MT_81Q7_BU_idea_FM_Yoga S940-14IWL
  dmi.product.version: Lenovo Yoga S940-14IWL
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1846201/+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 1846201] Re: Rendering is delayed on laptop display (works in external display)

[Daniel van Vugt]

I've never seen this problem before. The only unusual thing I can see is
that you have a shiny new Whiskey Lake GPU, which means it's a newish
graphics driver path.

Can you please make a video of the problem on a phone or camera?

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

** Also 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 xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1846201

Title:
   Rendering is delayed on laptop display (works in external display)

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

Bug description:
  This is a very wierd behavior I get on the Lenovo Yoga S940 after upgrading 
to 19.10.
  This makes the laptop almost unusable with its own display.
  This happens only on the laptop display, not on the external display.

  
  The render of portions of the screen does not happen after some events 
(listed below) resulting in all or part of the screen not being re-rendered. 
The UX is that nothing happened, but it has. 
  This happens after:

  * key-stroke while typing sometimes
  * alt-tab
  * shift-right to align window to the right
  * ctrl-pgup/down to switch tab in multi tabs apps. 

  
  Please note that:
  * screenshots can't see the problem
  * also screenrecorder always seem ok, despite rendering being broken.


  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  1 13:13:40 2019
  DistUpgraded: 2019-09-21 10:16:26,647 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:3801]
  InstallationDate: Installed on 2019-09-12 (18 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 81Q7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-09-21 (10 days ago)
  dmi.bios.date: 06/12/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AKCN34WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga S940-14IWL
  dmi.modalias: 
dmi:bvnLENOVO:bvrAKCN34WW:bd06/12/2019:svnLENOVO:pn81Q7:pvrLenovoYogaS940-14IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS940-14IWL:
  dmi.product.family: Yoga S940-14IWL
  dmi.product.name: 81Q7
  dmi.product.sku: LENOVO_MT_81Q7_BU_idea_FM_Yoga S940-14IWL
  dmi.product.version: Lenovo Yoga S940-14IWL
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1846201/+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 1846252] Re: gnome-shell segfault

[Daniel van Vugt]

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

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

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

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

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

** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

** Tags added: nvidia

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

Title:
  gnome-shell segfault

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Description:Ubuntu 18.04.3 LTS
  Release:18.04

  gnome-shell:
Installed: 3.28.4-0ubuntu18.04.1

  At totally random times the screen will lock up, right in the middle
  use.  Everything is still there, and the mouse moves fine, just
  nothing responds.

  Switching to a txt terminal I can see that gnome-shell has segfaulted.

dmesg -T | tail -50

  Once or twice I was able to get back by doing

gnome-shell --replace &

  in that txt terminal.  It complains about wrong session type, but
  alt-F2 goes back to the desktop and all was well.  Except, weirdly,
  all terminal sessions were gone.  Chromium, Slack etc were all still
  running fine, just terminal was gone.  That's happened twice.

  Several times though the "gnome-shell --replace" bit doesn't work.
  The desktop is till there, but clearly not working correctly.  Mouse
  clicks only work on the active window/app, but won't select any other.
  Ctrl-tab works to switch active windows, then mouse will work in THAT
  window.  Good enough to cleanly shut apps down, then reboot.

  Heh, have to reboot from a terminal - can't click the upper-right ...

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  430.50  Thu Sep  5 22:36:31 
CDT 2019
   GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  1 14:04:34 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 430.50, 4.15.0-64-generic, x86_64: installed
   nvidia, 430.50, 5.0.0-27-generic, x86_64: installed
   nvidia, 430.50, 5.0.0-29-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Once a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Subsystem: Lenovo Device [17aa:3132]
   NVIDIA Corporation GK208B [GeForce GT 730] [10de:1287] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. GK208B 
[GeForce GT 730] [1642:3f86]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1050:0407 Yubico.com 
   Bus 001 Device 002: ID 1b1c:1b15 Corsair 
   Bus 001 Device 004: ID 046d:c069 Logitech, Inc. M-U0007 [Corded Mouse M500]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 10SKS0C100
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.0.0-29-generic 
root=ZFS=/ROOT/ubuntu ro net.ifnames=0 biosdevname=0 root=ZFS=rpool/ROOT/ubuntu 
quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/10/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: M1UKT39A
  dmi.board.name: 3132
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN 3305206851

[Touch-packages] [Bug 1846188] Re: 1910 Tips in Nautilus 3.34 are out of place

[Daniel van Vugt]

Confirmed. But the good news is that I can't find any other app or menu
that's affected.

So this could be Nautilus-specific, or it could just be that hardly
anything else uses tooltips within their bubble menus.

** Tags added: eoan

** Summary changed:

- 1910 Tips in Nautilus 3.34 are out of place
+ Tooltips in Nautilus 3.34 are out of place (in Wayland sessions only)

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Confirmed

** Tags added: wayland wayland-session

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

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

** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

** Summary changed:

- Tooltips in Nautilus 3.34 are out of place (in Wayland sessions only)
+ Tooltips in Nautilus 3.34's burger menu are out of place (in Wayland sessions 
only)

** Changed in: gtk+3.0 (Ubuntu)
   Importance: Undecided => Low

** Changed in: mutter (Ubuntu)
   Importance: Undecided => Low

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

** Changed in: nautilus (Ubuntu)
   Importance: Undecided => Low

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

** No longer affects: gnome-shell (Ubuntu)

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

Title:
  Tooltips in Nautilus 3.34's burger menu are out of place (in Wayland
  sessions only)

Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu Eoan Ermine (development branch)
  Release:  19.10

  
  In Nautilus, tooltips appear far to the left in the app menu.

  (Kazam and Peek were unable to record Nautilus)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1846188/+subscriptions

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

[Touch-packages] [Bug 1845046] Re: [WH-1000XM3, playback] Hearing input and output audio until disconnecting and reconnecting

[Daniel van Vugt]

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

** Changed in: gnome-control-center (Ubuntu)
   Status: Incomplete => New

** Bug watch added: PulseAudio #716
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/716

** Also affects: pulseaudio via
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/716
   Importance: Unknown
   Status: Unknown

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

Title:
  [WH-1000XM3, playback] Hearing input and output audio until
  disconnecting and reconnecting

Status in PulseAudio:
  Unknown
Status in gnome-control-center package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

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

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

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

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

[Touch-packages] [Bug 1845046] Re: [WH-1000XM3, playback] Hearing input and output audio until disconnecting and reconnecting

[Nicholas Owens]

Whenever I first connect its set to Headset Head Unit but then I switch
to High Fidelity Playback and have to disconnect and reconnect in the
Bluetooth settings for it to change.

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

Title:
  [WH-1000XM3, playback] Hearing input and output audio until
  disconnecting and reconnecting

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1845046/+subscriptions

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

[Touch-packages] [Bug 1845741] Re: package libpam-runtime 1.1.8-3.6ubuntu2 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de le

[Steve Langasek]

> ErrorMessage: le paquet est dans un état vraiment incohérent; vous
devriez le réinstaller avant de tenter de le configurer.

Unfortunately your report does not include enough information for us to
debug this problem.  If you have a /var/log/apt/term.log, please attach
it to this bug report.

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

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

Title:
  package libpam-runtime 1.1.8-3.6ubuntu2 failed to install/upgrade: le
  paquet est dans un état vraiment incohérent; vous devriez  le
  réinstaller avant de tenter de le configurer.

Status in pam package in Ubuntu:
  Incomplete

Bug description:
  je ne peux telecharger aucune application toujours il me notifie qu'il
  au probléme

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libpam-runtime 1.1.8-3.6ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  AptOrdering:
   libpam-runtime:amd64: Configure
   cups-browsed:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Sep 28 00:43:19 2019
  DpkgTerminalLog:
   dpkg: erreur de traitement du paquet libpam-runtime (--configure) :
le paquet est dans un état vraiment incohérent; vous devriez
le réinstaller avant de tenter de le configurer.
  ErrorMessage: le paquet est dans un état vraiment incohérent; vous devriez  
le réinstaller avant de tenter de le configurer.
  InstallationDate: Installed on 2018-05-12 (503 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] Aucun fichier ou dossier de ce type: "/root/Error: command 
['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 
'python'] failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.3ubuntu0.1
  SourcePackage: pam
  Title: package libpam-runtime 1.1.8-3.6ubuntu2 failed to install/upgrade: le 
paquet est dans un état vraiment incohérent; vous devriez  le réinstaller avant 
de tenter de le configurer.
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1845741/+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 1845741] Re: package libpam-runtime 1.1.8-3.6ubuntu2 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de le

[Seth Arnold]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package libpam-runtime 1.1.8-3.6ubuntu2 failed to install/upgrade: le
  paquet est dans un état vraiment incohérent; vous devriez  le
  réinstaller avant de tenter de le configurer.

Status in pam package in Ubuntu:
  New

Bug description:
  je ne peux telecharger aucune application toujours il me notifie qu'il
  au probléme

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libpam-runtime 1.1.8-3.6ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  AptOrdering:
   libpam-runtime:amd64: Configure
   cups-browsed:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Sep 28 00:43:19 2019
  DpkgTerminalLog:
   dpkg: erreur de traitement du paquet libpam-runtime (--configure) :
le paquet est dans un état vraiment incohérent; vous devriez
le réinstaller avant de tenter de le configurer.
  ErrorMessage: le paquet est dans un état vraiment incohérent; vous devriez  
le réinstaller avant de tenter de le configurer.
  InstallationDate: Installed on 2018-05-12 (503 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] Aucun fichier ou dossier de ce type: "/root/Error: command 
['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 
'python'] failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.3ubuntu0.1
  SourcePackage: pam
  Title: package libpam-runtime 1.1.8-3.6ubuntu2 failed to install/upgrade: le 
paquet est dans un état vraiment incohérent; vous devriez  le réinstaller avant 
de tenter de le configurer.
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1845741/+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 1808710] Re: !xcb_xlib_threads_sequence_lost error with GTK2 applications

[Peter S]

I have the same problem with eboard 1.1.3 on Debian Buster. The program
build is quite old (2016), hence it seems that the problem is with some
high-level library.

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

Title:
  !xcb_xlib_threads_sequence_lost error with GTK2 applications

Status in gtk+2.0 package in Ubuntu:
  Confirmed

Bug description:
  GTK2 applications randomly crash or freeze with error like:

  [xcb] Unknown sequence number while processing queue
  [xcb] Most likely this is a multi-threaded client and XInitThreads has not 
been called
  [xcb] Aborting, sorry about that.
  : ../../src/xcb_io.c:263: poll_for_event: Assertion 
`!xcb_xlib_threads_sequence_lost' failed.

  where  is the name of the executable, e.g. audacious,
  soffice.bin, etc.

  RELATED BUGS
  LibreOffice: 
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1801161
  PCManFM: https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1782984
  Audacious: https://redmine.audacious-media-player.org/issues/798
  FreeCAD: https://bugs.launchpad.net/ubuntu/+source/freecad/+bug/1754084
  ClawsMail: 
https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4203

  OTHER APPLICATIONS
  SpaceFM, Pidgin, GPicView and GIMP appear to have similar problems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710/+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 1818243] Re: systemd-logind takes 25s to stop when rebooting

[Brian Murray]

** Changed in: systemd (Ubuntu Cosmic)
   Status: Confirmed => Won't Fix

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

Title:
  systemd-logind takes 25s to stop when rebooting

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Cosmic:
  Won't Fix

Bug description:
  During reboot:

  Mar 01 14:15:52 P8lpar5 systemd[1]: Stopping Login Service...
  [...]
  Mar 01 14:16:17 P8lpar5 systemd-logind[2756]: Failed to abandon session 
scope, ignoring: Connection timed out
  Mar 01 14:16:17 P8lpar5 systemd-logind[2756]: Session 5 logged out. Waiting 
for processes to exit.
  Mar 01 14:16:17 P8lpar5 dbus-daemon[2855]: [system] Failed to activate 
service 'org.freedesktop.systemd1': timed out (service_start_timeout=
  25000ms)
  Mar 01 14:16:17 P8lpar5 systemd[1]: Stopped Login Service.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818243/+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 1832651] Re: jackdbus fails to start: cannot allocate memory

[John Sweeney]

This bug also affects me with jackdbus. I too need a workaround

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

Title:
  jackdbus fails to start: cannot allocate memory

Status in systemd:
  Fix Released
Status in jackd2 package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in jackd2 source package in Eoan:
  Invalid
Status in systemd source package in Eoan:
  Fix Released

Bug description:
  The `.log/jack/jackdbus.log` shows the following after trying to
  start/restart jack using "Ubuntu Studio Controls" (also tried using
  `jack_control start`):

  ERROR: Cannot lock down 82280346 byte memory area (Cannot allocate
  memory)

  This is a fresh install of Ubuntu Studio 19.04, installed via USB. The
  first thing I did after installing was check to see if jack was
  running, but unfortunately it's not working. The error would seem to
  indicate that I'm not in the `audio` group, however checking `groups`
  shows that I am in the audio group.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: jackd2 1.9.12~dfsg-2build1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-lowlatency 5.0.6
  Uname: Linux 5.0.0-13-lowlatency x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Jun 12 18:13:25 2019
  InstallationDate: Installed on 2019-06-12 (0 days ago)
  InstallationMedia: Ubuntu-Studio 19.04 "Disco Dingo" - Release amd64 
(20190416)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: jackd2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1832651/+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 1845950] Re: Bug reporting doesn't work upon a crash

[Dean Henrichsmeyer]

Here it is.

** Attachment added: "crashdb.conf"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1845950/+attachment/5293314/+files/crashdb.conf

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

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

Title:
  Bug reporting doesn't work upon a crash

Status in apport package in Ubuntu:
  New

Bug description:
  On eoan, after an initial startup / login, if an application crashes
  and I click "report", I get a prompt saying the crash is reported and
  to check the web page open in the browser to see if I have any
  additional information.. except it never opens a page. The dialog just
  disappears, the crash log stays in /var/crash and nothing happens.

  The only way to actually file it is to run ubuntu-bug  which does
  work as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: apport 2.20.11-0ubuntu7
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportLog:
   ERROR: apport (pid 3941) Mon Sep 30 07:28:14 2019: called for pid 3409, 
signal 6, core limit 0, dump mode 1
   ERROR: apport (pid 3941) Mon Sep 30 07:28:14 2019: executable: 
/usr/lib/tracker/tracker-miner-fs (command line 
"/usr/lib/tracker/tracker-miner-fs")
   ERROR: apport (pid 3941) Mon Sep 30 07:28:14 2019: debug: session gdbus 
call: (true,)
   
   ERROR: apport (pid 3941) Mon Sep 30 07:28:15 2019: wrote report 
/var/crash/_usr_lib_tracker_tracker-miner-fs.1000.crash
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:117:2696160:2019-09-26 13:17:54.338476419 -0500:2019-09-26 
13:17:55.338476419 -0500:/var/crash/_opt_google_chrome_chrome.1000.crash
   640:1000:117:2499555:2019-09-30 07:28:32.538634538 -0500:2019-09-30 
07:28:33.538634538 -0500:/var/crash/_usr_lib_tracker_tracker-miner-fs.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 30 07:34:38 2019
  InstallationDate: Installed on 2018-07-24 (432 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180724)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to eoan on 2019-07-19 (72 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1845950/+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 1846252] [NEW] gnome-shell segfault

[Halfwalker]

Public bug reported:

Description:Ubuntu 18.04.3 LTS
Release:18.04

gnome-shell:
  Installed: 3.28.4-0ubuntu18.04.1

At totally random times the screen will lock up, right in the middle
use.  Everything is still there, and the mouse moves fine, just nothing
responds.

Switching to a txt terminal I can see that gnome-shell has segfaulted.

  dmesg -T | tail -50

Once or twice I was able to get back by doing

  gnome-shell --replace &

in that txt terminal.  It complains about wrong session type, but alt-F2
goes back to the desktop and all was well.  Except, weirdly, all
terminal sessions were gone.  Chromium, Slack etc were all still running
fine, just terminal was gone.  That's happened twice.

Several times though the "gnome-shell --replace" bit doesn't work.  The
desktop is till there, but clearly not working correctly.  Mouse clicks
only work on the active window/app, but won't select any other.  Ctrl-
tab works to switch active windows, then mouse will work in THAT window.
Good enough to cleanly shut apps down, then reboot.

Heh, have to reboot from a terminal - can't click the upper-right ...

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-29-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  430.50  Thu Sep  5 22:36:31 
CDT 2019
 GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct  1 14:04:34 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 430.50, 4.15.0-64-generic, x86_64: installed
 nvidia, 430.50, 5.0.0-27-generic, x86_64: installed
 nvidia, 430.50, 5.0.0-29-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GpuHangFrequency: Once a week
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Subsystem: Lenovo Device [17aa:3132]
 NVIDIA Corporation GK208B [GeForce GT 730] [10de:1287] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. GK208B 
[GeForce GT 730] [1642:3f86]
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 1050:0407 Yubico.com 
 Bus 001 Device 002: ID 1b1c:1b15 Corsair 
 Bus 001 Device 004: ID 046d:c069 Logitech, Inc. M-U0007 [Corded Mouse M500]
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 10SKS0C100
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.0.0-29-generic 
root=ZFS=/ROOT/ubuntu ro net.ifnames=0 biosdevname=0 root=ZFS=rpool/ROOT/ubuntu 
quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/10/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: M1UKT39A
dmi.board.name: 3132
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN 3305206851929
dmi.chassis.asset.tag: MJ099889
dmi.chassis.type: 3
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrM1UKT39A:bd05/10/2019:svnLENOVO:pn10SKS0C100:pvrThinkCentreM920s:rvnLENOVO:rn3132:rvrSDK0J40697WIN3305206851929:cvnLENOVO:ct3:cvrNone:
dmi.product.family: ThinkCentre M920s
dmi.product.name: 10SKS0C100
dmi.product.sku: LENOVO_MT_10SK_BU_Think_FM_ThinkCentre M920s
dmi.product.version: ThinkCentre M920s
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


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

Title:
  gnome-shell segfault

Status in xorg 

[Touch-packages] [Bug 1846201] Re: Rendering is delayed on laptop display (works in external display)

[Daniele Dellafiore]

I've made a picture as screenrecord/screenshot can't cath the problem. 
As you can see the render is still on "General" despite "Extensions" being the 
current selection. 
You can see at the top part of the rendering is restarted and is now stuck in 
the middle. 

** Attachment added: "IMG_20191001_155337.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1846201/+attachment/5293261/+files/IMG_20191001_155337.jpg

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

Title:
   Rendering is delayed on laptop display (works in external display)

Status in xorg package in Ubuntu:
  New

Bug description:
  This is a very wierd behavior I get on the Lenovo Yoga S940 after upgrading 
to 19.10.
  This makes the laptop almost unusable with its own display.
  This happens only on the laptop display, not on the external display.

  
  The render of portions of the screen does not happen after some events 
(listed below) resulting in all or part of the screen not being re-rendered. 
The UX is that nothing happened, but it has. 
  This happens after:

  * key-stroke while typing sometimes
  * alt-tab
  * shift-right to align window to the right
  * ctrl-pgup/down to switch tab in multi tabs apps. 

  
  Please note that:
  * screenshots can't see the problem
  * also screenrecorder always seem ok, despite rendering being broken.


  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  1 13:13:40 2019
  DistUpgraded: 2019-09-21 10:16:26,647 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:3801]
  InstallationDate: Installed on 2019-09-12 (18 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 81Q7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-09-21 (10 days ago)
  dmi.bios.date: 06/12/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AKCN34WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga S940-14IWL
  dmi.modalias: 
dmi:bvnLENOVO:bvrAKCN34WW:bd06/12/2019:svnLENOVO:pn81Q7:pvrLenovoYogaS940-14IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS940-14IWL:
  dmi.product.family: Yoga S940-14IWL
  dmi.product.name: 81Q7
  dmi.product.sku: LENOVO_MT_81Q7_BU_idea_FM_Yoga S940-14IWL
  dmi.product.version: Lenovo Yoga S940-14IWL
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  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

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

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

[Touch-packages] [Bug 1845494] Re: gdb 8.1-0ubuntu3.1 freezes before call main function while debugging 32bit application

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

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

Status in gdb package in Ubuntu:
  Confirmed

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

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

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

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

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

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

[Touch-packages] [Bug 1846243] [NEW] package openssh-client 1:7.6p1-4ubuntu0.3 failed to install/upgrade: end of file on stdin at conffile prompt

[Nicholas Oddson]

Public bug reported:

bug to install

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: openssh-client 1:7.6p1-4ubuntu0.3
ProcVersionSignature: Ubuntu 4.4.0-1095.106-aws 4.4.189
Uname: Linux 4.4.0-1095-aws x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
Date: Tue Oct  1 17:20:44 2019
Ec2AMI: ami-0e3d43d99dd9cda2c
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: ca-central-1a
Ec2InstanceType: t2.nano
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
ErrorMessage: end of file on stdin at conffile prompt
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:
 ssh-askpass   N/A
 libpam-sshN/A
 keychain  N/A
 ssh-askpass-gnome N/A
SSHClientVersion: OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n  7 Dec 2017
SourcePackage: openssh
Title: package openssh-client 1:7.6p1-4ubuntu0.3 failed to install/upgrade: end 
of file on stdin at conffile prompt
UpgradeStatus: Upgraded to bionic on 2019-10-01 (0 days ago)
modified.conffile..etc.ssh.ssh_config: [modified]
mtime.conffile..etc.ssh.ssh_config: 2019-04-30T10:51:02.029086

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


** Tags: amd64 apport-package bionic ec2-images

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

Title:
  package openssh-client 1:7.6p1-4ubuntu0.3 failed to install/upgrade:
  end of file on stdin at conffile prompt

Status in openssh package in Ubuntu:
  New

Bug description:
  bug to install

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: openssh-client 1:7.6p1-4ubuntu0.3
  ProcVersionSignature: Ubuntu 4.4.0-1095.106-aws 4.4.189
  Uname: Linux 4.4.0-1095-aws x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  Date: Tue Oct  1 17:20:44 2019
  Ec2AMI: ami-0e3d43d99dd9cda2c
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ca-central-1a
  Ec2InstanceType: t2.nano
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ErrorMessage: end of file on stdin at conffile prompt
  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:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome N/A
  SSHClientVersion: OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n  7 Dec 2017
  SourcePackage: openssh
  Title: package openssh-client 1:7.6p1-4ubuntu0.3 failed to install/upgrade: 
end of file on stdin at conffile prompt
  UpgradeStatus: Upgraded to bionic on 2019-10-01 (0 days ago)
  modified.conffile..etc.ssh.ssh_config: [modified]
  mtime.conffile..etc.ssh.ssh_config: 2019-04-30T10:51:02.029086

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1846243/+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 1846208] Re: [MIR] abootimg (dependency of initramfs-tools-ubuntu-core)

[Dimitri John Ledkov]

Cute, but things in the image build PPA should be MIRed.

This is in use in bionic and up from the sideload PPA.

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

Title:
  [MIR] abootimg (dependency of initramfs-tools-ubuntu-core)

Status in abootimg package in Ubuntu:
  Incomplete

Bug description:
  needs a MIR (or removal of the dependency): abootimg (dependency of
  initramfs-tools-ubuntu-core)

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

[Julian Andres Klode]

** Description changed:

- 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 ...
+ [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/

-- 
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:
  New
Status in initramfs-tools source package in Bionic:
  New
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   : h

[Touch-packages] [Bug 1844119] Re: readelf crash on 32bit, leading to abi-monitor testsuite regression

[Launchpad Bug Tracker]

This bug was fixed in the package binutils - 2.32.90.20190929-0ubuntu2

---
binutils (2.32.90.20190929-0ubuntu2) eoan; urgency=medium

  * Snapshot, taken from the 2.33 branch (20190929).
- Fix PR25031, nm reports wrong address on 32bit. LP: #1845190.
- Fix PR25018, readelf crash on 32bits. LP: #1844119.
- [GOLD] Fix spurious "plugin needed to handle lto object" warnings.
- GCC 10 related warning fixes.
- i386: Adjust for new output format from readelf.
  * Include the test logs in the binutils-dev package.

 -- Matthias Klose   Sun, 29 Sep 2019 07:37:06 +0200

** Changed in: binutils (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  readelf crash on 32bit, leading to abi-monitor testsuite regression

Status in binutils:
  Fix Released
Status in binutils package in Ubuntu:
  Fix Released
Status in glibc package in Ubuntu:
  Invalid

Bug description:
  readelf --debug-dump=info libjsoncpp.so.1.8.1
  to reproduce
  dpkg -l |grep binut
  ii  binutils2.32.51.20190905-0ubuntu1   i386 GNU 
assembler, linker and binary utilities
  ii  binutils-common:i3862.32.51.20190905-0ubuntu1   i386 Common 
files for the GNU assembler, linker and binary utilities
  ii  binutils-i686-linux-gnu 2.32.51.20190905-0ubuntu1   i386 GNU 
binary utilities, for i686-linux-gnu target
  ii  libbinutils:i3862.32.51.20190905-0ubuntu1   i386 GNU 
binary utilities (private shared library)

To manage notifications about this bug go to:
https://bugs.launchpad.net/binutils/+bug/1844119/+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 1845190] Re: binutils nm wrong output format breaks i386 nm work

[Launchpad Bug Tracker]

This bug was fixed in the package binutils - 2.32.90.20190929-0ubuntu2

---
binutils (2.32.90.20190929-0ubuntu2) eoan; urgency=medium

  * Snapshot, taken from the 2.33 branch (20190929).
- Fix PR25031, nm reports wrong address on 32bit. LP: #1845190.
- Fix PR25018, readelf crash on 32bits. LP: #1844119.
- [GOLD] Fix spurious "plugin needed to handle lto object" warnings.
- GCC 10 related warning fixes.
- i386: Adjust for new output format from readelf.
  * Include the test logs in the binutils-dev package.

 -- Matthias Klose   Sun, 29 Sep 2019 07:37:06 +0200

** Changed in: binutils (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  binutils nm wrong output format breaks i386 nm work

Status in binutils:
  Fix Released
Status in binutils package in Ubuntu:
  Fix Released

Bug description:
  discovered with diffoscope autopkgregression, looks like a real bug, based on
  https://salsa.debian.org/reproducible-builds/diffoscope/issues/69

To manage notifications about this bug go to:
https://bugs.launchpad.net/binutils/+bug/1845190/+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 1846208] Re: [MIR] abootimg (dependency of initramfs-tools-ubuntu-core)

[Steve Langasek]

Dimitri uploaded the version of initramfs-tools-ubuntu-core that's stuck
in -proposed; reassigning.

** Changed in: abootimg (Ubuntu)
 Assignee: Snappy Developers (snappy-dev) => Dimitri John Ledkov (xnox)

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

Title:
  [MIR] abootimg (dependency of initramfs-tools-ubuntu-core)

Status in abootimg package in Ubuntu:
  Incomplete

Bug description:
  needs a MIR (or removal of the dependency): abootimg (dependency of
  initramfs-tools-ubuntu-core)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/abootimg/+bug/1846208/+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 214786] Re: Apple USB ISO keyboard has incorrectly swapped keys

[Daniel]

I'm currently having this issue on a portuguese (european) apple
keyboard. The wireless kind used in iMac.

I have two keys swapped. The key < > prints ` and ~

Was working fine previously, not sure what changed.

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

Title:
  Apple USB ISO keyboard has incorrectly swapped keys

Status in Mactel Support:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading kernel to version 2.6.24-12.22 two keys are now
  swapped on my Apple USB aluminium keyboard with danish layout. Now the
  keys "<" and "½" are swapped and no longer matches the actual print on
  the keycaps.

  The error is isolated to the following commit:
  http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-
  hardy.git;a=commitdiff;h=efb3031b446d441dca5b10619503ac0bba7f9748

  This commit introduced a key swapping for all "ISO" type Apple
  keyboards. In my case this swapping is incorrect, and generally it
  seems like a very bad idea to perform hard coded locale specific key
  mapping in kernel space as this is also done several places in user
  space.

  The included patch reverts the behavior to the default that matches
  the keycap printing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mactel-support/+bug/214786/+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 1846201] Re: Rendering is delayed on laptop display (works in external display)

[Daniele Dellafiore]

** Attachment added: "Attached output of gsettings list-recursively"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1846201/+attachment/5293166/+files/gsettings

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

Title:
   Rendering is delayed on laptop display (works in external display)

Status in xorg package in Ubuntu:
  New

Bug description:
  This is a very wierd behavior I get on the Lenovo Yoga S940 after upgrading 
to 19.10.
  This makes the laptop almost unusable with its own display.
  This happens only on the laptop display, not on the external display.

  
  The render of portions of the screen does not happen after some events 
(listed below) resulting in all or part of the screen not being re-rendered. 
The UX is that nothing happened, but it has. 
  This happens after:

  * key-stroke while typing sometimes
  * alt-tab
  * shift-right to align window to the right
  * ctrl-pgup/down to switch tab in multi tabs apps. 

  
  Please note that:
  * screenshots can't see the problem
  * also screenrecorder always seem ok, despite rendering being broken.


  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  1 13:13:40 2019
  DistUpgraded: 2019-09-21 10:16:26,647 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:3801]
  InstallationDate: Installed on 2019-09-12 (18 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 81Q7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-09-21 (10 days ago)
  dmi.bios.date: 06/12/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AKCN34WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga S940-14IWL
  dmi.modalias: 
dmi:bvnLENOVO:bvrAKCN34WW:bd06/12/2019:svnLENOVO:pn81Q7:pvrLenovoYogaS940-14IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS940-14IWL:
  dmi.product.family: Yoga S940-14IWL
  dmi.product.name: 81Q7
  dmi.product.sku: LENOVO_MT_81Q7_BU_idea_FM_Yoga S940-14IWL
  dmi.product.version: Lenovo Yoga S940-14IWL
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1846201/+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 1846201] Re: Rendering is delayed on laptop display (works in external display)

[Daniele Dellafiore]

Update. 
Today I experienced this: after suspending the laptop, now I do not experience 
broken rendering anymore. 
This happened once before. Everytime I reboot, it comes back. 

I'll try to identify a pattern here.

Also this is in the "Tweaks" application, gnome-shell does not have a
theme associated (see screenshot)

** Attachment added: "Screenshot from 2019-10-01 15-47-58.png"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1846201/+attachment/5293165/+files/Screenshot%20from%202019-10-01%2015-47-58.png

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

Title:
   Rendering is delayed on laptop display (works in external display)

Status in xorg package in Ubuntu:
  New

Bug description:
  This is a very wierd behavior I get on the Lenovo Yoga S940 after upgrading 
to 19.10.
  This makes the laptop almost unusable with its own display.
  This happens only on the laptop display, not on the external display.

  
  The render of portions of the screen does not happen after some events 
(listed below) resulting in all or part of the screen not being re-rendered. 
The UX is that nothing happened, but it has. 
  This happens after:

  * key-stroke while typing sometimes
  * alt-tab
  * shift-right to align window to the right
  * ctrl-pgup/down to switch tab in multi tabs apps. 

  
  Please note that:
  * screenshots can't see the problem
  * also screenrecorder always seem ok, despite rendering being broken.


  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  1 13:13:40 2019
  DistUpgraded: 2019-09-21 10:16:26,647 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:3801]
  InstallationDate: Installed on 2019-09-12 (18 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 81Q7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-09-21 (10 days ago)
  dmi.bios.date: 06/12/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AKCN34WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga S940-14IWL
  dmi.modalias: 
dmi:bvnLENOVO:bvrAKCN34WW:bd06/12/2019:svnLENOVO:pn81Q7:pvrLenovoYogaS940-14IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS940-14IWL:
  dmi.product.family: Yoga S940-14IWL
  dmi.product.name: 81Q7
  dmi.product.sku: LENOVO_MT_81Q7_BU_idea_FM_Yoga S940-14IWL
  dmi.product.version: Lenovo Yoga S940-14IWL
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1846201/+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 1841718] Re: [radeon] Rendering of combo boxes and tooltips is broken

[Sebastien Bacher]

** Changed in: xserver-xorg-video-ati (Ubuntu Eoan)
   Importance: Undecided => High

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

Title:
  [radeon] Rendering of combo boxes and tooltips is broken

Status in Mutter:
  New
Status in mesa package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati package in Ubuntu:
  New
Status in mesa source package in Eoan:
  Invalid
Status in mutter source package in Eoan:
  Invalid
Status in xserver-xorg-video-ati source package in Eoan:
  New
Status in xserver-xorg-video-ati package in Fedora:
  Fix Released

Bug description:
  Combo boxes are broken (cf screenshot) Tested in gnome-control-center
  and gtk3-demo.

  Tooltips are also garbage.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.33.91-1ubuntu1
  ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8
  Uname: Linux 5.2.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 28 07:08:33 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2014-07-15 (1869 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2018-03-24 (521 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1841718/+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 1846201] Re: Rendering is delayed on laptop display (works in external display)

[Daniele Dellafiore]

Update. 
Today I experienced this: after suspending the laptop, now I do not experience 
broken rendering anymore. 
This happened once before. Everytime I reboot, it comes back. 

I'll try to identify a pattern here.

** Description changed:

- This is a very wierd behavior I get on the Lenovo Yoga S940 after
- upgrading to 19.10.
+ This is a very wierd behavior I get on the Lenovo Yoga S940 after upgrading 
to 19.10.
+ This makes the laptop almost unusable with its own display.
+ This happens only on the laptop display, not on the external display.
  
- Basically the rendering on the laptop display is... messy, I'll try to
- describe how as
  
- * screenshots always take it ok
+ The render of portions of the screen does not happen after some events 
(listed below) resulting in all or part of the screen not being re-rendered. 
The UX is that nothing happened, but it has. 
+ This happens after:
+ 
+ * key-stroke while typing sometimes
+ * alt-tab
+ * shift-right to align window to the right
+ * ctrl-pgup/down to switch tab in multi tabs apps. 
+ 
+ 
+ Please note that:
+ * screenshots can't see the problem
  * also screenrecorder always seem ok, despite rendering being broken.
  
- What heppen is:
- 
- When I alt-tab or switch tabs or align window right, the rendering does not 
happen completely, so the screen displays part of the old status and part of 
the new.
- If I then alt-tab again for example, or move the mouse cursor over the 
portions that has not rendered properly, the renders happens.
- 
- This happens only on the laptop display, not on the external display.
- 
- This makes the laptop almost unusable with its own display.
- 
- I will need to go back to 19.04, if there's something I can do to help
- debug this I'd rather do.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  1 13:13:40 2019
  DistUpgraded: 2019-09-21 10:16:26,647 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
-  Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
-Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:3801]
+  Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
+    Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:3801]
  InstallationDate: Installed on 2019-09-12 (18 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 81Q7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-09-21 (10 days ago)
  dmi.bios.date: 06/12/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AKCN34WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga S940-14IWL
  dmi.modalias: 
dmi:bvnLENOVO:bvrAKCN34WW:bd06/12/2019:svnLENOVO:pn81Q7:pvrLenovoYogaS940-14IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS940-14IWL:
  dmi.product.family: Yoga S940-14IWL
  dmi.product.name: 81Q7
  dmi.product.sku: LENOVO_MT_81Q7_BU_idea_FM_Yoga S940-14IWL
  dmi.product.version: Lenovo Yoga S940-14IWL
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  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

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

Title:
   Rendering is delayed on laptop display (works in external display)

Status in xorg package in Ubuntu:
  New

Bug description:
  This is a very wierd behavior I get on the Lenovo Yoga S940 after upgrading 
to 19.10.
  This makes the laptop almost unusable with its own display.
  This happens only on the laptop display, not on the external display.

  
  The render of portions of the screen does not happen after 

[Touch-packages] [Bug 1781428] Re: please enable snap mediation support

[Ken VanDine]

** Changed in: pulseaudio (Ubuntu Xenial)
 Assignee: (unassigned) => James Henstridge (jamesh)

** Changed in: pulseaudio (Ubuntu Bionic)
 Assignee: (unassigned) => James Henstridge (jamesh)

** Changed in: pulseaudio (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: pulseaudio (Ubuntu Bionic)
   Importance: Undecided => Medium

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

Title:
  please enable snap mediation support

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Triaged
Status in pulseaudio source package in Bionic:
  Triaged

Bug description:
  [Impact]
  Ubuntu 16.10 added rudimentary snap support to disable audio recording if the 
connecting process was a snap. By Ubuntu 18.04, something changed in the build 
resulting in 'Enable Snappy support: no' with audio recording no longer being 
mediated by pulseaudio (access to the pulseaudio socket continued to be 
mediated by snapd's apparmor policy). This resulted in any application with the 
pulseaudio interface connected to be able to also record. Ubuntu 16.04 never 
had mediation patches and always allowed recording when the pulseaudio 
interface was connected.

  To correct this situation but not regress existing behavior, Ubuntu
  19.04's pulseaudio was updated patch to allow playback to all
  connected clients (snaps or not), record by classic snaps (see bug
  1787324) and record by strict mode snaps if either the pulseaudio or
  new-in-snapd-2.41 audio-record interfaces were connected. With this
  change, snapd is in a position to migrate snaps to the new audio-
  playback and audio-record interfaces and properly mediate audio
  recording (see https://forum.snapcraft.io/t/upcoming-pulseaudio-
  interface-deprecation/13418).

  The patch to pulseaudio consists of adding a module, enabling it in
  default.pa and then when it is enabled, pulseaudio when faced with a
  record operation will, when the connecting process is a snap (ie, its
  security label (ie, apparmor label) starts with 'snap.'), query snapd
  via its control socket to ask if the snap is classic and if not,
  whether the pulseaudio or audio-record interfaces are connected.
  Adjusting pulseaudio in the manner does not require coordination with
  any release of snapd. It does need a newer version of snapd-glib,
  which was recently updated to 1.49 in the last SRU.

  [Test Case]

  IMPORTANT: if updating pulseaudio while the session is running, either
  need to reboot for the test or kill pulseaudio so it can restart with
  the new snap policy

  For unconfined applications:
  $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes"
  yes

  $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes"  # ctrl-c to stop 
recording
  ^Cyes

  $ paplay /tmp/out.wav && echo "yes"
  yes

  For confined, non-snap applications:
  $ sudo apt-get install evince

  $ aa-exec -p /usr/bin/evince -- paplay
  /usr/share/sounds/alsa/Noise.wav && echo yes

  $ rm -f /tmp/out.wav ; aa-exec -p /usr/bin/evince -- parecord /tmp/out.wav && 
echo "yes"  # ctrl-c to stop recording
  ^Cyes

  $ aa-exec -p /usr/bin/evince -- paplay /tmp/out.wav && echo "yes"
  yes

  For classic snaps:
  $ sudo snap install test-snapd-classic-confinement --classic

  $ snap run --shell test-snapd-classic-confinement

  $ cat /proc/self/attr/current   # verify we are classic confined
  snap.test-snapd-classic-confinement.test-snapd-classic-confinement (complain)

  $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes"
  yes

  $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes"  # ctrl-c to stop 
recording
  ^Cyes

  $ paplay /tmp/out.wav && echo "yes"
  yes

  For strict snaps with pulseaudio:
  $ sudo snap install --dangerous ./test-snapd-pulseaudio_1_amd64.snap

  $ snap connections test-snapd-pulseaudio
  Interface   Plug  Slot Notes
  pulseaudio  test-snapd-pulseaudio:pulseaudio  :pulseaudio  -

  $ test-snapd-pulseaudio.play --help  # ensure SNAP dirs are created
  ...

  $ sudo cp /usr/share/sounds/alsa/Noise.wav /var/snap/test-snapd-
  pulseaudio/common/

  $ test-snapd-pulseaudio.play /var/snap/test-snapd-pulseaudio/common/Noise.wav 
&& echo yes
  xcb_connection_has_error() returned true
  yes

  (note, the xcb_connection_has_error() message is due to the x11
  interface not being connecting which is unrelated to mediation. x11 is
  left out to ensure that just audio-playback/audio-record are tested)

  $ test-snapd-pulseaudio.record /tmp/out.wav && echo yes # should pass
  ...
  ^Cyes

  $ test-snapd-pulseaudio.play /tmp/out.wav && echo yes
  ...
  yes

  For strict snaps with audio-playback/audio-record:
  $ sudo snap refresh core --candidate # make sure have 2.41. 'install' on 16.04
  $ sudo snap install --dangerous ./test-snapd-audio-record_1_amd64.snap

  $ 

[Touch-packages] [Bug 1841718] Re: [radeon] Rendering of combo boxes and tooltips is broken

[Timo Aaltonen]

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

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

** Changed in: xserver-xorg-video-ati (Ubuntu Eoan)
 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/1841718

Title:
  [radeon] Rendering of combo boxes and tooltips is broken

Status in Mutter:
  New
Status in mesa package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati package in Ubuntu:
  New
Status in mesa source package in Eoan:
  Invalid
Status in mutter source package in Eoan:
  Invalid
Status in xserver-xorg-video-ati source package in Eoan:
  New
Status in xserver-xorg-video-ati package in Fedora:
  Fix Released

Bug description:
  Combo boxes are broken (cf screenshot) Tested in gnome-control-center
  and gtk3-demo.

  Tooltips are also garbage.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.33.91-1ubuntu1
  ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8
  Uname: Linux 5.2.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 28 07:08:33 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2014-07-15 (1869 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2018-03-24 (521 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1841718/+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 1845317] Re: Add new pci-id's for CML-S, ICL

[Timo Aaltonen]

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

Title:
  Add new pci-id's for CML-S, ICL

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in libdrm source package in Bionic:
  New
Status in linux source package in Bionic:
  Won't Fix
Status in linux-oem-osp1 source package in Bionic:
  New
Status in mesa source package in Bionic:
  New

Bug description:
  [Impact]
  Comet Lake (CML) is basically same gen9 GPU as Sky Lake (SKL) (as is KBL, 
CFL, WHL). There are new CML-S desktop cpu's on the way, and they add three new 
pci-id's that need to be added across the stack in order to use the GPU 
properly.

  There's also one ICL pci-id which was added recently (not in 5.3).

  [Test case]
  The proper way to test is to have an actual machine and boot it up with the 
updated stack, but since these are just pci-id's with no regression potential 
on older hw, it should be fine to just accept them.

  [Regression potential]
  None, just adds new pci-id's to allow the new GPUs to load the proper drivers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1845317/+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 1846208] [NEW] [MIR] abootimg (dependency of initramfs-tools-ubuntu-core)

[Matthias Klose]

Public bug reported:

needs a MIR (or removal of the dependency): abootimg (dependency of
initramfs-tools-ubuntu-core)

** Affects: abootimg (Ubuntu)
 Importance: High
 Assignee: Snappy Developers (snappy-dev)
 Status: Incomplete


** Tags: eoan rls-ee-incoming

** Changed in: abootimg (Ubuntu)
   Importance: Undecided => High

** Changed in: abootimg (Ubuntu)
 Assignee: (unassigned) => Snappy Developers (snappy-dev)

** Tags added: rls-ee-incoming

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

Title:
  [MIR] abootimg (dependency of initramfs-tools-ubuntu-core)

Status in abootimg package in Ubuntu:
  Incomplete

Bug description:
  needs a MIR (or removal of the dependency): abootimg (dependency of
  initramfs-tools-ubuntu-core)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/abootimg/+bug/1846208/+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 1779121] Re: mobile broadband is slow to start in wake from suspend (or system startup)

[budkin]

have you found a workaround for this? I'm having the same issue with
T450s and EM7345

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

Title:
  mobile broadband is slow to start in wake from suspend (or system
  startup)

Status in network-manager package in Ubuntu:
  New

Bug description:
  On a ThinkPad 470s it takes ~ 40 seconds to gain connectivity on wake
  or startup.

  The log seems to incidate that there is first a 10 second delay in the
  kernel recognising the USB device and assigning a serial port to it,
  and then it takes ModemManager 20 seconds to open the device, and a
  further 13 seconds to go from unlocking the SIM ("locked" state) to
  getting an ip address.

  Apparently it starts in 10 seconds in Windows (see
  https://forums.lenovo.com/t5/ThinkPad-X-Series-Laptops/SierraWireless-
  EM7455-in-X1c5-is-Lenovo-going-to-fix-its-poor/td-p/3716748) so the
  40+ seconds it's not a hardware property.

  The log goes like this:

  Jun 28 15:06:35 myhostname NetworkManager[1302]:   [1530187595.7935] 
manager: sleep: wake requested (sleeping: yes  enabled: yes)
  Jun 28 15:06:35 myhostname NetworkManager[1302]:   [1530187595.7936] 
device (enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping', 
sys-iface-state: 'managed')
  Jun 28 15:06:35 myhostname NetworkManager[1302]:   [1530187595.8780] 
device (enp0s31f6): state change: unmanaged -> unavailable (reason 'managed', 
sys-iface-state: 'managed')
  Jun 28 15:06:36 myhostname kernel: [127229.483041] usb 1-6: config 1 
interface 0 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64
  Jun 28 15:06:36 myhostname kernel: [127229.483051] usb 1-6: config 1 
interface 0 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64
  Jun 28 15:06:36 myhostname kernel: [127229.483720] usb 1-6: New USB device 
found, idVendor=1199, idProduct=9078
  Jun 28 15:06:36 myhostname kernel: [127229.483728] usb 1-6: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3
  Jun 28 15:06:36 myhostname kernel: [127229.483734] usb 1-6: Product: Sierra 
Wireless EM7455 Qualcomm
  Jun 28 15:06:36 myhostname kernel: [127229.483741] usb 1-6: Manufacturer: 
Sierra Wireless, Incorporated
  Jun 28 15:06:36 myhostname kernel: [127229.483747] usb 1-6: SerialNumber: 
LF80875274011022
  Jun 28 15:06:36 myhostname kernel: [127229.502644] usb 1-6: USB disconnect, 
device number 14

  Jun 28 15:06:36 myhostname NetworkManager[1302]:   [1530187596.0722] 
device (wlp58s0): state change: unmanaged -> unavailable (reason 'managed', 
sys-iface-state: 'managed')
  Jun 28 15:06:36 myhostname NetworkManager[1302]:   [1530187596.0744] 
manager: NetworkManager state is now CONNECTED_LOCAL
  Jun 28 15:06:36 myhostname upowerd[1509]: unhandled action 'bind' on 
/sys/devices/pci:00/:00:14.0/usb1/1-6
  Jun 28 15:06:36 myhostname upowerd[1509]: unhandled action 'unbind' on 
/sys/devices/pci:00/:00:14.0/usb1/1-6
  Jun 28 15:06:36 myhostname upowerd[1509]: unhandled action 'bind' on 
/sys/devices/pci:00/:00:14.0/usb2/2-3/2-3:1.0
  Jun 28 15:06:36 myhostname upowerd[1509]: unhandled action 'bind' on 
/sys/devices/pci:00/:00:14.0/usb2/2-3

  Jun 28 15:06:38 myhostname ModemManager[1312]:   Couldn't check support 
for device at '/sys/devices/pci:00/:00:1c.2/:3a:00.0': not 
supported by any plu
  gin
  Jun 28 15:06:38 myhostname ModemManager[1312]:   Couldn't check support 
for device at '/sys/devices/pci:00/:00:1f.6': not supported by any 
plugin

  Jun 28 15:06:45 myhostname kernel: [127238.486536] usb 1-6: new high-speed 
USB device number 15 using xhci_hcd
  Jun 28 15:06:45 myhostname kernel: [127238.642917] usb 1-6: config 1 has an 
invalid interface number: 12 but max is 4
  Jun 28 15:06:45 myhostname kernel: [127238.642920] usb 1-6: config 1 has an 
invalid interface number: 13 but max is 4
  Jun 28 15:06:45 myhostname kernel: [127238.642921] usb 1-6: config 1 has an 
invalid interface number: 13 but max is 4
  Jun 28 15:06:45 myhostname kernel: [127238.642923] usb 1-6: config 1 has no 
interface number 1
  Jun 28 15:06:45 myhostname kernel: [127238.642925] usb 1-6: config 1 has no 
interface number 4
  Jun 28 15:06:45 myhostname kernel: [127238.643533] usb 1-6: New USB device 
found, idVendor=1199, idProduct=9079
  Jun 28 15:06:45 myhostname kernel: [127238.643535] usb 1-6: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3
  Jun 28 15:06:45 myhostname kernel: [127238.643537] usb 1-6: Product: Sierra 
Wireless EM7455 Qualcomm Snapdragon X7 LTE-A
  Jun 28 15:06:45 myhostname kernel: [127238.643539] usb 1-6: Manufacturer: 
Sierra Wireless, Incorporated
  Jun 28 15:06:45 myhostname kernel: [127238.646888] qcserial 1-6:1.0: Qualcomm 
USB modem converter detected
  Jun 28 15:06:45 myhostname kernel: [127238.647053] usb 1-6: Qualcomm USB 
modem converter now attached to ttyUSB0
  Jun 28 1

[Touch-packages] [Bug 1796501] Re: systemd-resolved tries to mitigate DVE-2018-0001 even if DNSSEC=yes

[Francis Ginther]

** Tags added: id-5d92536b4bcd9c68caddc01c

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

Title:
  systemd-resolved tries to mitigate DVE-2018-0001 even if DNSSEC=yes

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

Bug description:
  I ask systemd-resolved through dig to resolve the SOA of test.asdf. (doesn't 
exist) but it returns SERVFAIL instead of NXDOMAIN. It seems to do the 
following steps:
  1. Ask upstream for SOA of test.asdf. with EDNS0, DO-bit and 4k size.
  2. Ask upstream for SOA of test.asdf. with EDNS0 and DO-bit.
  3. Ask upstream for SOA of test.asdf. with EDNS0.
  4. Ask upstream for SOA of test.asdf. without EDNS0.
  5. Repeat 1-4 for DS of test.asdf.
  6. Repeat 1-5 for asdf.
  7. Ask upstream for SOA of . with EDNS0, DO-bit and 4k size.
  8. Ask upstream for DNSKEY of . with EDNS0, DO-bit and 4k size.

  The upstream returns an unfragmented NXDOMAIN response for steps 1-6,
  an unfragmented NOERROR response for step 7 and a fragmented NOERROR
  response for step 8 which is the correct behaviour. DNSSEC records are
  included in the response if the DO-bit in the request was set.

  systemd-resolved should take the response from step 1 and start with
  validation instead of starting useless retries with reduced feture
  set. Step 3 and 4 are completely useless and probably lead to the
  SERVFAIL because I have configured it with DNSSEC=yes to prevent
  downgrade attacks.

  This regression seems to be caused by the patch resolved-Mitigate-
  DVE-2018-0001-by-retrying-NXDOMAIN-with.patch. The downgrade logic
  should only be executed if it is configured as DNSSEC=allow-downgrade
  or DNSSEC=no. See also
  https://github.com/systemd/systemd/pull/8608#issuecomment-396927885.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1796501/+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 1846201] [NEW] Rendering is delayed on laptop display (works in external display)

[Daniele Dellafiore]

Public bug reported:

This is a very wierd behavior I get on the Lenovo Yoga S940 after
upgrading to 19.10.

Basically the rendering on the laptop display is... messy, I'll try to
describe how as

* screenshots always take it ok
* also screenrecorder always seem ok, despite rendering being broken.

What heppen is:

When I alt-tab or switch tabs or align window right, the rendering does not 
happen completely, so the screen displays part of the old status and part of 
the new.
If I then alt-tab again for example, or move the mouse cursor over the portions 
that has not rendered properly, the renders happens.

This happens only on the laptop display, not on the external display.

This makes the laptop almost unusable with its own display.

I will need to go back to 19.04, if there's something I can do to help
debug this I'd rather do.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
Uname: Linux 5.3.0-13-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct  1 13:13:40 2019
DistUpgraded: 2019-09-21 10:16:26,647 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: eoan
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:3801]
InstallationDate: Installed on 2019-09-12 (18 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 81Q7
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to eoan on 2019-09-21 (10 days ago)
dmi.bios.date: 06/12/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: AKCN34WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Yoga S940-14IWL
dmi.modalias: 
dmi:bvnLENOVO:bvrAKCN34WW:bd06/12/2019:svnLENOVO:pn81Q7:pvrLenovoYogaS940-14IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS940-14IWL:
dmi.product.family: Yoga S940-14IWL
dmi.product.name: 81Q7
dmi.product.sku: LENOVO_MT_81Q7_BU_idea_FM_Yoga S940-14IWL
dmi.product.version: Lenovo Yoga S940-14IWL
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
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

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


** Tags: amd64 apport-bug corruption eoan 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/1846201

Title:
   Rendering is delayed on laptop display (works in external display)

Status in xorg package in Ubuntu:
  New

Bug description:
  This is a very wierd behavior I get on the Lenovo Yoga S940 after
  upgrading to 19.10.

  Basically the rendering on the laptop display is... messy, I'll try to
  describe how as

  * screenshots always take it ok
  * also screenrecorder always seem ok, despite rendering being broken.

  What heppen is:

  When I alt-tab or switch tabs or align window right, the rendering does not 
happen completely, so the screen displays part of the old status and part of 
the new.
  If I then alt-tab again for example, or move the mouse cursor over the 
portions that has not rendered properly, the renders happens.

  This happens only on the laptop display, not on the external display.

  This makes the laptop almost unusable with its own display.

  I will need to go back to 19.04, if there's something I can do to help
  debug this I'd rather do.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  1 13:13:40 2019
  DistUpgraded: 2019-09-21 10:16:26,647 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodena

[Touch-packages] [Bug 1846185] [NEW] rc.local error compatablity

[Abhilash anand kulkarni]

Public bug reported:

#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.

. /var/www/html/env/bin/activate
nohup python3 /var/www/html/SOCO/soco_invex/manage.py runserver 0.0.0.0:8000 &

exit 0

This is my rc.local file i am trying to run my python3 code but when i
check status of rc.local

rc-local.service - /etc/rc.local Compatibility
   Loaded: loaded (/lib/systemd/system/rc-local.service; static; vendor preset: 
enable
  Drop-In: /lib/systemd/system/rc-local.service.d
   └─debian.conf
   Active: failed (Result: exit-code) since Tue 2019-10-01 09:32:46 UTC; 30min 
ago

Oct 01 09:32:46 ip-172-31-17-137 systemd[1]: Starting /etc/rc.local 
Compatibility...
Oct 01 09:32:46 ip-172-31-17-137 systemd[1]: rc-local.service: Control process 
exited,
Oct 01 09:32:46 ip-172-31-17-137 systemd[1]: Failed to start /etc/rc.local 
Compatibili
Oct 01 09:32:46 ip-172-31-17-137 systemd[1]: rc-local.service: Unit entered 
failed sta
Oct 01 09:32:46 ip-172-31-17-137 systemd[1]: rc-local.service: Failed with 
result 'exi


I am getting this error i tried restarting and changing the mode of the 
rc.local still i am getting this error please help me out with this
the same i did in another server i am able to run the code but not in this 
server
the server is deployed in aws

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

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

Title:
  rc.local error compatablity

Status in sysvinit package in Ubuntu:
  New

Bug description:
  #!/bin/sh -e
  #
  # rc.local
  #
  # This script is executed at the end of each multiuser runlevel.
  # Make sure that the script will "exit 0" on success or any other
  # value on error.
  #
  # In order to enable or disable this script just change the execution
  # bits.
  #
  # By default this script does nothing.

  . /var/www/html/env/bin/activate
  nohup python3 /var/www/html/SOCO/soco_invex/manage.py runserver 0.0.0.0:8000 &

  exit 0

  This is my rc.local file i am trying to run my python3 code but when i
  check status of rc.local

  rc-local.service - /etc/rc.local Compatibility
 Loaded: loaded (/lib/systemd/system/rc-local.service; static; vendor 
preset: enable
Drop-In: /lib/systemd/system/rc-local.service.d
 └─debian.conf
 Active: failed (Result: exit-code) since Tue 2019-10-01 09:32:46 UTC; 
30min ago

  Oct 01 09:32:46 ip-172-31-17-137 systemd[1]: Starting /etc/rc.local 
Compatibility...
  Oct 01 09:32:46 ip-172-31-17-137 systemd[1]: rc-local.service: Control 
process exited,
  Oct 01 09:32:46 ip-172-31-17-137 systemd[1]: Failed to start /etc/rc.local 
Compatibili
  Oct 01 09:32:46 ip-172-31-17-137 systemd[1]: rc-local.service: Unit entered 
failed sta
  Oct 01 09:32:46 ip-172-31-17-137 systemd[1]: rc-local.service: Failed with 
result 'exi

  
  I am getting this error i tried restarting and changing the mode of the 
rc.local still i am getting this error please help me out with this
  the same i did in another server i am able to run the code but not in this 
server
  the server is deployed in aws

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1846185/+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 1846180] Re: 1910 software-properties larger screen size

[Barabazon]

** Description changed:

+ Description:  Ubuntu Eoan Ermine (development branch)
+ Release:  19.10
+ 
  Screen size 1366x768, Russian language.
  
  Update settings go beyond the edge of the screen. The window cannot be
  reduced.

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

Title:
  1910 software-properties larger screen size

Status in software-properties package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu Eoan Ermine (development branch)
  Release:  19.10

  Screen size 1366x768, Russian language.

  Update settings go beyond the edge of the screen. The window cannot be
  reduced.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1846180/+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 1846180] [NEW] 1910 software-properties larger screen size

[Barabazon]

Public bug reported:

Screen size 1366x768, Russian language.

Update settings go beyond the edge of the screen. The window cannot be
reduced.

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: properties settings update

** Attachment added: "software properties"
   
https://bugs.launchpad.net/bugs/1846180/+attachment/5293041/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202019-09-28%2023-41-03.png

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

Title:
  1910 software-properties larger screen size

Status in software-properties package in Ubuntu:
  New

Bug description:
  Screen size 1366x768, Russian language.

  Update settings go beyond the edge of the screen. The window cannot be
  reduced.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1846180/+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 1784454] Re: kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image

[Frank Heimes]

Since it was me who initially raised that bug, I feel like I should
comment on this.

My test case was and is to install Ubuntu on z/VM using (at least one) 
zFCP/SCSI devices for disk storage.
That should be a proper end-2-end test since it includes the entire zFCP/SCSI 
stack (even incl. multipath) and with that covers the initially reported 
problem mentioned in the bug description.

Please notice that all this happened to me on 16.04(.5) only with GA
kernel 4.4 (hence the '4.4' still in the headline and even 16.04's HWE
kernel 4.15 worked for me in the past - see comment above), but now it
looks like we talk about 18.04 too, but I never saw that problem on
18.04.

Nevertheless, I (re-)tested today on 18.04(.3) - so it's more a
regression test than anything else.

I used 18.04.3 default (means proposed disabled) as well as with proposed 
enabled.
W/o proposed I see systemd 237-3ubuntu10.29 with propose I see 237-3ubuntu10.31.
Means I wasn't able to use 237-3ubuntu10.30 - like mentioned in comment #30.
But both tests worked fine for me and I didn't saw any anomalies (details see 
attachment).


** Attachment added: "verification bionic.txt"
   
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1784454/+attachment/5293039/+files/verification%20bionic.txt

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

Title:
  kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Bionic:
  Incomplete

Bug description:
  Booting d-i based on kernel 4.4 (from ./boot folder) from the 16.04.5 RC 
image on a z/VM guest
  leads to a kernel panic:

  /lib/debian-installer/start-udev: line 15: can't create 
/sys/module/scsi_mod/par
  ameters/scan: Permission denied 
  ¬0.845071| Kernel panic - not syncing: Attempted to kill initÜ 
exitcode=0x00
  000100 
  ¬0.845071|  
  ¬0.845075| CPU: 0 PID: 1 Comm: /init Not tainted 4.4.0-131-generic 
#157-Ubun
  tu 
  ¬0.845077|7d107c20 7d107cb0 0002 
000
  0  
 7d107d50 7d107cc8 7d107cc8 00114732  
 008b 009a304c 009f11d0 000b  
 7d107d10 7d107cb0    
 040001cdf800 00114732 7d107cb0 7d107d10  
  ¬0.845089| Call Trace: 
  ¬0.845093| (¬<0011461a>| show_trace+0xfa/0x150) 
  ¬0.845095|  ¬<001146e2>| show_stack+0x72/0xf8 
  ¬0.845099|  ¬<00555752>| dump_stack+0x82/0xb8 
  ¬0.845101|  ¬<00286390>| panic+0x108/0x250 
  ¬0.845104|  ¬<00166228>| do_exit+0xac0/0xba0 
  ¬0.845106|  ¬<001663c8>| do_group_exit+0x50/0xe0 
  ¬0.845108|  ¬<00166488>| __wake_up_parent+0x0/0x28 
  ¬0.845111|  ¬<007eadda>| system_call+0xee/0x28c 
  ¬0.845113|  ¬<03ff8953983a>| 0x3ff8953983a 
  00: HCPGIR450W CP entered; disabled wait PSW 00020001 8000  
0010F8CA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1784454/+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 1843381] Re: Dell system takes a long time to connect network with external dock

[Che Cheng]

There is 73-special-net-names.rules which 73-usb-net-by-mac.rules was
split from, and it'll execute prior to 73-usb-net-by-mac.rules.

We can keep the fixed internal MAC passthrough interface using MAC
address as interface name, and let removable dongles using pathname by
adding following line to 73-special-net-names.rules.

ACTION=="add", SUBSYSTEM=="net", SUBSYSTEMS=="usb", NAME=="",
ATTRS{idVendor}=="0bda", ATTRS{idProduct}=="8153",
ATTRS{removable}=="removable", IMPORT{builtin}="net_id",
NAME="$env{ID_NET_NAME_PATH}"

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

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

[Touch-packages] [Bug 1843479] Re: gzip in Ubuntu Eoan results in Exec format error on WSL1

[Sebastien Bacher]

Thanks Hayden, closing

** Changed in: gzip (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  gzip in Ubuntu Eoan results in Exec format error on WSL1

Status in gzip package in Ubuntu:
  Invalid

Bug description:
  Summary:

  Running gzip on WSL1 results in the following error:

  $ gzip
  -bash: /bin/gzip: cannot execute binary file: Exec format error

  What I expect to happen:

  gzip executes correctly on WSL1.

  What happens instead:

  gzip fails with an Exec format error.

  Notes:

  I suspect a change in how gzip is being built for Eoan is causing
  issues with ELF parsing on the WSL1 translation layer. For example:

  On Disco with gzip 1.9-3:

  $ file /bin/gzip
  /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), 
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 
3.2.0, BuildID[sha1]=efa859c26eaf8e035efe9a139361e2a60cd17b3e, stripped

  On Eoan with gzip 1.10-0ubuntu3:

  $ file /bin/gzip
  /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), 
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, 
BuildID[sha1]=bc0f5994544c2a469d04c914bf4bf44b4ded6040, for GNU/Linux 3.2.0, 
stripped

  Eoan ships with gzip 1.10, while Disco ships with gzip 1.9, but I do
  not believe this is an issue in 1.10 because this error does not occur
  when building gzip from GNU project source on Ubuntu Eoan.

  Justifications:

  WSL1 will need to be patched in future Windows builds for this change
  in ELF. However that patch will likely not be backported to older
  builds of Windows, including Windows Enterprise/Server 2019.

  To ensure Eoan can run on current and older builds of Windows Ubuntu
  should consider looking at how it's building gzip and see if it can be
  made to 'play nice' until WSL1 can be updated.

  This was originally reported here:
  https://github.com/microsoft/WSL/issues/4461

  Details:

  Description:Ubuntu Eoan Ermine (development branch)
  Release:19.10

  gzip:
Installed: 1.10-0ubuntu3
Candidate: 1.10-0ubuntu3
Version table:
   *** 1.10-0ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gzip/+bug/1843479/+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 1833193] Re: systemd-networkd fails to apply static IPv4 when the static IP is the same as previously configured by DHCP

[Lars Erik Pedersen]

Yes that's the same issue. And it seems to be fixed in some version as
well? I just tested it on Eoan, using systemd 242-6, and the valid__lft
and preferred_lft did indeed change to 'forever'. Don't know which
version it was fixed in though. Do you think it kan be backported to
Bionic?

The discussion in the GitHub issue was rather interesting as well. I
kind of "agree" that this is a strange thing to do, but I don't think
that should be any of systemd's business..

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

Title:
  systemd-networkd fails to apply static IPv4 when the static IP is the
  same as previously configured by DHCP

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

Bug description:
  In bionic, running systemd 237-3ubuntu10.22 and netplan.io
  0.97-0ubuntu1~18.04.1, systemd-networkd fails to configure an
  interface with a static IPv4 address if the statically confiugred
  address is the same as the interface already has gotten from DHCP.

  This will cause the interface to loose its IP address when the DHCP
  lease exires, even though you've told netplan to configure it as
  static.

  I expect systemd-networkd to actually configure an IP address as
  static, regardless of what address the interface has before from DHCP.

  # lsb_release  -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  # apt-cache policy systemd
  systemd:
Installed: 237-3ubuntu10.22

  # apt-cache policy netplan.io
  netplan.io:
Installed: 0.97-0ubuntu1~18.04.1

  A paste of systemd-networkd's debug log when I run "netplan apply" and
  the interface already has the static IP configured from DHCP.

  It seems like upon a restart, systemd-networkd will allways add
  whatever IP config it had before the service stopped, and then apply
  changes (if any). Since my new config has the same IP as it already
  had, it does nothing even though the new config has static
  configuration.

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

[Roque]

** Description changed:

  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 very stronger signal. I tested it
+ windows it works normally, and with a much stronger signal. I tested it
  on Ubuntu 18.04.3 and 19.04.

-- 
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 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/network-manager/+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

[Touch-packages] [Bug 1846140] Re: Realtek RTL8723BU doesn't work well in ubuntu

[Roque]

I think it's related to that package, although it could also be related
to the kernel.

** Package changed: ubuntu => network-manager (Ubuntu)

** Description changed:

  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 whit a very stronger signal. I tested it
+ windows it works normally, and with a very stronger signal. I tested it
  on Ubuntu 18.04.3 and 19.04.

-- 
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 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 very 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/network-manager/+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

[Touch-packages] [Bug 1830146] Re: Checkbox detect an extra webcam "video1"

[Betty Lin]

Verified the bug pass with latptop - 201903-26914

checkbox-ng: 1.5.0rc3
checkbox-support: 0.42.0rc2
com.canonical.ce:oem: 1.0
certification-client: 0.38.0rc2
plainbox-provider-checkbox: 0.49.0rc4
plainbox-provider-resource-generic: 0.41.0rc2
plainbox-provider-sru: 1.14.0rc1
plainbox-provider-tpm2: 1.11.0rc2


** Tags added: cqa-verified

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

Title:
  Checkbox detect an extra webcam "video1"

Status in Checkbox Support Library:
  Fix Committed
Status in systemd package in Ubuntu:
  New

Bug description:
  Summary: System only have 1 webcam (video0) but checkbox detect an
  extra webcam "video1"

  
  -

  system-product-name: Latitude 5501
  GPU: 00:02.0 VGA compatible controller: Intel Corporation Device 3e9b (rev 02)
  CPU: Intel(R) Core(TM) i7-9850H CPU @ 2.60GHz (12x)
  bios-version: 1.0.0
  system-manufacturer: Dell Inc.
  Image: somerville-bionic-amd64-iso-hybrid-20180608-47

To manage notifications about this bug go to:
https://bugs.launchpad.net/checkbox-support/+bug/1830146/+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] [NEW] Realtek RTL8723BU doesn't work well in ubuntu

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

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 whit a very stronger signal. I tested it
on Ubuntu 18.04.3 and 19.04.

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


** Tags: bot-comment
-- 
Realtek RTL8723BU doesn't work well in ubuntu
https://bugs.launchpad.net/bugs/1846140
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to network-manager in Ubuntu.

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