[Touch-packages] [Bug 1846450] Re: package linux-image-4.15.0-65-generic 4.15.0-65.74~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with return code 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-4.15.0-65-generic 4.15.0-65.74~16.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal
  exited with return code 1

Status in apt package in Ubuntu:
  New

Bug description:
  package linux-image-4.15.0-65-generic 4.15.0-65.74~16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.15.0-65-generic 4.15.0-65.74~16.04.1
  ProcVersionSignature: Ubuntu 4.15.0-64.73~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-64-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.19
  Architecture: amd64
  Date: Thu Oct  3 06:40:23 2019
  ErrorMessage: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with 
return code 1
  InstallationDate: Installed on 2019-08-25 (39 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.6
   apt  1.2.32
  SourcePackage: apt
  Title: package linux-image-4.15.0-65-generic 4.15.0-65.74~16.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1846450/+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 1846450] [NEW] package linux-image-4.15.0-65-generic 4.15.0-65.74~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with return code 1

[redhwan nasser]

Public bug reported:

package linux-image-4.15.0-65-generic 4.15.0-65.74~16.04

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.15.0-65-generic 4.15.0-65.74~16.04.1
ProcVersionSignature: Ubuntu 4.15.0-64.73~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-64-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.19
Architecture: amd64
Date: Thu Oct  3 06:40:23 2019
ErrorMessage: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with 
return code 1
InstallationDate: Installed on 2019-08-25 (39 days ago)
InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.6
 apt  1.2.32
SourcePackage: apt
Title: package linux-image-4.15.0-65-generic 4.15.0-65.74~16.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package linux-image-4.15.0-65-generic 4.15.0-65.74~16.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal
  exited with return code 1

Status in apt package in Ubuntu:
  New

Bug description:
  package linux-image-4.15.0-65-generic 4.15.0-65.74~16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.15.0-65-generic 4.15.0-65.74~16.04.1
  ProcVersionSignature: Ubuntu 4.15.0-64.73~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-64-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.19
  Architecture: amd64
  Date: Thu Oct  3 06:40:23 2019
  ErrorMessage: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with 
return code 1
  InstallationDate: Installed on 2019-08-25 (39 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.6
   apt  1.2.32
  SourcePackage: apt
  Title: package linux-image-4.15.0-65-generic 4.15.0-65.74~16.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1846450/+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 1545945] Re: Selection flickers to dark grey for a split second before settling on light grey

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1846447
   Selection flickers to dark grey each time it changes instead of staying 
light grey

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

Title:
  Selection flickers to dark grey for a split second before settling on
  light grey

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  New
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete
Status in ubuntu-themes package in Ubuntu:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  System Settings: The rounded selection rectangle flickers on mouse
  click.

  Using Unity8 on desktop, when I click on any icon in System Settings a
  rounded selection rectangle appears. However during the click that
  selection rectangle flickers to dark grey for a fraction of a second
  before becoming light grey.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1545945/+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 1846443] [NEW] Strange behavior of GNOME Tweak header when changing button positions (eoan wayland)

[Barabazon]

Public bug reported:

19.10 eoan
Wayland sessions

If the GNOME Tweak Tools window is not maximized to the full screen,
then when you change the buttons from right to left, the title bar
starts to behave strangely, as if it does not have enough space to place
information

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


** Tags: button eoan header tweak wayland

** Attachment added: "tweak header"
   
https://bugs.launchpad.net/bugs/1846443/+attachment/5293873/+files/Peek%202019-10-03%2009-22.mp4

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

Title:
  Strange behavior of GNOME Tweak header when changing button positions
  (eoan wayland)

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  19.10 eoan
  Wayland sessions

  If the GNOME Tweak Tools window is not maximized to the full screen,
  then when you change the buttons from right to left, the title bar
  starts to behave strangely, as if it does not have enough space to
  place information

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1846443/+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 1846148] Re: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019

[Hui Wang]

There is no any internal mic or external mic defined according to the
init verb.

Does those mics work under windows? If yes, please collect the log under
windows.


** Attachment added: "RtHDDump_V226.zip"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+attachment/5293871/+files/RtHDDump_V226.zip

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

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

Status in alsa-driver package in Ubuntu:
  Confirmed

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+subscriptions

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

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

[Daniel van Vugt]

** No longer affects: pulseaudio

-- 
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:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

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

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

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

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

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

[You-Sheng Yang]

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

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

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

Status in alsa-driver package in Ubuntu:
  Confirmed

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+subscriptions

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

[Touch-packages] [Bug 1584314] Re: Togo keyboard layout / compose keys

[Gunnar Hjalmarsson]

Removing the ibus (ubuntu) task, since it does not deal with compose.
It's either GTK or XIM.

** No longer affects: ibus (Ubuntu)

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

Title:
  Togo keyboard layout / compose keys

Status in xkeyboard-config:
  Fix Released
Status in libx11 package in Ubuntu:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Fix Released

Bug description:
  Hi
  My name is Rodrigo with my team we develop the Togo-Africa Keyboard Layout in 
the Linux Distribution.
  We want to include this keyboard in the Ubuntu distribution.

  I've uploaded a keyboard to XKB:
  
https://cgit.freedesktop.org/xkeyboard-config/commit/?id=53452c901fcab08a43705c9aa79a5ec5642cca08

  
  
https://cgit.freedesktop.org/xorg/lib/libX11/commit/?id=3129c757f9da8586ab8b8654a56c8f687cc9ef5c

  
  Here is the Keyboard
  ##

  diff --git a/rules/base.xml.in b/rules/base.xml.in
  index f495c8d..5e91717 100644
  --- a/rules/base.xml.in
  +++ b/rules/base.xml.in
  @@ -5680,6 +5680,16 @@
   
   
     
  +tg
  +<_shortDescription>fr-tg
  +<_description>French (Togo)
  +
  +  fra
  +
  +  
  +
  +
  +  
   ke
   
   <_shortDescription>sw
  diff --git a/symbols/Makefile.am b/symbols/Makefile.am
  index 77ec0ff..3226d41 100644
  --- a/symbols/Makefile.am
  +++ b/symbols/Makefile.am
  @@ -29,7 +29,7 @@ pc ph pk pl pt \
   ro rs ru \
   se si sk sn \
   sy th \
  -terminate \
  +terminate tg \
   tj tm tr tw tz \
   ua us uz vn \
   za \
  diff --git a/symbols/tg b/symbols/tg
  new file mode 100644
  index 000..f7b2cb3
  --- /dev/null
  +++ b/symbols/tg
  @@ -0,0 +1,68 @@
  +default partial alphanumeric_keys
  +xkb_symbols "basic" {
  +
  +include "fr(azerty)"
  +
  +name[Group1]="French (Togo)";
  +
  +// French AZERTY-Keyboard layout including symbols for Togolese local 
languages
  +// Created 2015 by Globalbility Togo (www.globalbility.org)
  +// Authors: Issaka Ouro-Wétchiré, Caroline Riefstahl, Mats Blakstad 
  +//
  +// LAYOUT OVERVIEW
  +//  
  +// | 1 3| 1 = Shift,  3 = AltGr + Shift(AltGr is the right side alt key)
  +// | 2 4| 2 = normal, 4 = AltGr
  +//  
  +//               ___
  +// || 1  | 2  | 3  | 4  | 5  | 6  | 7  | 8  | 9  | 0  | °  | +  | <--   |
  +// | ²  | &  | é ~| " #| ' {| ( [| - || è `| _ \| ç ^| à @| ) ]| = }|   |
  +//  
  +// | |<-  | A  | Z Ʒ| E Ɛ| R Ɗ| T  | Y Ƴ| U Ʊ| I Ɩ| O Ɔ| P  | ¨  | $ €|   , |
  +// |  ->| | a  | z ʒ| e ɛ| r ɗ| t  | y ƴ| u ʊ| i ɩ| o ɔ| p  | ^  ̌| £ ¤| <-' 
|
  +//  ===¬|
  +// |   | Q Ǝ| S  | D Ɖ| F Ƒ| G Ɣ| H Ĥ | J  | K  | L  | M Ŋ| %  | µ  |
|
  +// | MAJ   | q ǝ| s  | d ɖ| f ƒ| g ɣ| h ɦ| j  | k  | l  | m ɲ| ù `| *  ́|
|
  +//  
  +// | ^   | >  | W  | X  | C  | V Ʋ| B Ɓ| N Ŋ| ?  | .  | /  | §  | | |
  +// | |   | <  | w  | x  | c  | v ʋ| b ɓ| n ŋ| , ~| ; ¯| :  | !  | | |
  +//  
  +// |  |  |  |   |   |  | |  |
  +// | Ctrl | Super| Alt  | SpaceNobreakspace | AltGr | Super|Menu | Ctrl |
  +//  ¯¯ ¯¯ ¯¯ ¯¯¯ ¯¯¯ ¯¯ ¯ ¯¯
  +// Togolese local languages use 8 tones markers.
  +// Acute ( ´ ),  Grave ( ` ), Circumflex ( ˆ ), Caron ( ˇ ), Macron ( ¯ 
), Tilde ( ~ ), Tilde + Acute (  ̃́ ), Tilde + Grave (  ̃̀ )
  +// All vowels can have tones except "y" (which is not vowel in Togolese 
local languages)
  +// Nasal consonants ("m" and "n") can have have high tones.
  +
  + // Modifications of the basic French Azerty layout, adding 
symbols for Togolese local languages
  +
  + // Second row
  + key   { [ z,  Z,  ezh,
EZH ] };// U0292 = ʒ (small), U01B7 = Ʒ (capital)
  +override key   { [ e,  E,  U025B,  
U0190   ] };// Replqce Eurosign with U025B = ɛ (small), U0190 = Ɛ 
(capital)
  + key   { [ r,  R,  U0257,  
U018A   ] };// U0257 = ɗ (small), U018A = Ɗ (capital)
  + key   { [ y,  Y,  U01B4,  
U01B3   ] };// U01B4 = ƴ (small), U01B3 = Ƴ (capital)
  + key   { [ u,  U,  U028A,  
U01B1   ] };// U028A = ʊ (small), U01B1 = Ʊ (capital)
  + key   { [ i,  I,  

[Touch-packages] [Bug 366780] Re: Please provide a mechanism whereby Wi-Fi networks can be prioritized

[Joko Yuliyanto]

In windows my pc can connect wirelles but in elmentary my pc do  ot have
wirelles

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

Title:
  Please provide a mechanism whereby Wi-Fi networks can be prioritized

Status in NetworkManager:
  Fix Released
Status in Network Manager Applet:
  Confirmed
Status in Plasma-widget-networkmanagement:
  Won't Fix
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager-applet package in Ubuntu:
  Confirmed
Status in networkmanagement package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: network-manager

  I've got few wifi network profiles. NM connects to 1st available
  network in alphabetical order. But at my home NM connects to slow and
  unstable free network and I want to connect to my own wifi router. I
  suggest to add some priorities to different networks to set the order
  which network to connect to.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/366780/+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 1842439] Re: apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0)

[Daniel van Vugt]

Tracking in:
https://errors.ubuntu.com/problem/815a179408135a894bbb5921adef3757563c75c5


** Summary changed:

- apport-gtk crashed with SIGSEGV
+ apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0)

** Information type changed from Private to Public

** Description changed:

+ https://errors.ubuntu.com/problem/815a179408135a894bbb5921adef3757563c75c5
+ 
+ ---
+ 
  Session suddenly stopped and came back to login screen, all opened
  windows lost.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: apport-gtk 2.20.11-0ubuntu7
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashReports:
-  640:1000:117:7292709:2019-09-03 16:20:13.909392833 +0200:2019-09-03 
16:20:14.909392833 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.crash
-  640:1000:117:48937942:2019-09-03 16:20:11.681426286 +0200:2019-09-03 
16:20:12.681426286 +0200:/var/crash/_usr_bin_gnome-shell.1000.crash
-  640:1000:117:32054:2019-08-27 17:39:07.125607490 +0200:2019-08-28 
12:36:17.087672961 +0200:/var/crash/_usr_bin_dbus-daemon.1000.crash
+  640:1000:117:7292709:2019-09-03 16:20:13.909392833 +0200:2019-09-03 
16:20:14.909392833 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.crash
+  640:1000:117:48937942:2019-09-03 16:20:11.681426286 +0200:2019-09-03 
16:20:12.681426286 +0200:/var/crash/_usr_bin_gnome-shell.1000.crash
+  640:1000:117:32054:2019-08-27 17:39:07.125607490 +0200:2019-08-28 
12:36:17.087672961 +0200:/var/crash/_usr_bin_dbus-daemon.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  3 16:20:13 2019
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2018-06-16 (443 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180611)
  InterpreterPath: /usr/bin/python3.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  ProcEnviron:
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=fr_FR.UTF-8
-  SHELL=/bin/bash
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=fr_FR.UTF-8
+  SHELL=/bin/bash
  Python3Details: /usr/bin/python3.7, Python 3.7.4, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1
  SegvAnalysis:
-  Segfault happened at: 0x7f532548f8c4:mov0x18(%rdi),%rax
-  PC (0x7f532548f8c4) ok
-  source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed 
readable region)!
-  destination "%rax" ok
+  Segfault happened at: 0x7f532548f8c4:mov0x18(%rdi),%rax
+  PC (0x7f532548f8c4) ok
+  source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed 
readable region)!
+  destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: apport
  StacktraceTop:
-  ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
-  ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
-  ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
-  ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
-  ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
+  ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
+  ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
+  ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
+  ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
+  ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: apport-gtk crashed with SIGSEGV
  UpgradeStatus: Upgraded to eoan on 2019-06-10 (84 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

Title:
  apport-gtk crashed with SIGSEGV in
  _gtk_settings_get_screen(settings=0x0)

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/815a179408135a894bbb5921adef3757563c75c5

  ---

  Session suddenly stopped and came back to login screen, all opened
  windows lost.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: apport-gtk 2.20.11-0ubuntu7
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:117:7292709:2019-09-03 16:20:13.909392833 +0200:2019-09-03 
16:20:14.909392833 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.crash
   640:1000:117:48937942:2019-09-03 16:20:11.681426286 +0200:2019-09-03 
16:20:12.681426286 +0200:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:1000:117:32054:2019-08-27 17:39:07.125607490 +0200:2019-08-28 
12:36:17.087672961 +0200:/var/crash/_usr_bin_dbus-daemon.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  3 16:20:13 2019
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2018-06-16 (443 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180611)
  In

[Touch-packages] [Bug 1846353] Re: On xorg balloon tooltips can be graphically glitched

[Daniel van Vugt]

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

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


** This bug has been marked a duplicate of bug 1841718
   [radeon] Rendering of combo boxes and tooltips is broken

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

Title:
  On xorg balloon tooltips can be graphically glitched

Status in xorg package in Ubuntu:
  New

Bug description:
  On xorg balloon tooltips can be graphically glitched I have Ubuntu
  19.10 development branch with an AMD/ATI Radeon HD 5570. On wayland
  this bug doesn't appear.

  Version of xorg: 1:7.7+19ubuntu12

  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 non accordée: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  2 16:10:45 2019
  DistUpgraded: 2019-09-28 11:48:48,742 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.0.12, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Juniper XT [Radeon HD 
5770] [174b:e147]
  InstallationDate: Installed on 2019-08-13 (49 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: wortmann MBR1|1400G
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=cb9f6c77-c09c-4cd5-810c-bc6a5760a04b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (4 days ago)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: TCIBX10H.86A.0039.2010.0722.1419
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH55TC
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE70932-302
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrTCIBX10H.86A.0039.2010.0722.1419:bd07/22/2010:svnwortmann:pnMBR1|1400G:pvr:rvnIntelCorporation:rnDH55TC:rvrAAE70932-302:cvn:ct3:cvr:
  dmi.product.name: MBR1|1400G
  dmi.sys.vendor: wortmann
  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/1846353/+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 1542901] Re: "ubuntu-bug apport-gtk" fails with segmentation fault

[Daniel van Vugt]

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

** This bug has been marked a duplicate of private bug 1842439

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

Title:
  "ubuntu-bug apport-gtk" fails with segmentation fault

Status in apport package in Ubuntu:
  New

Bug description:
  $ ubuntu-bug apport-gtk
  Failed to connect to Mir: Failed to connect to server socket: No such 
file or directory
  Unable to init server: Could not connect: Connection refused

  ** (apport-gtk:21616): WARNING **: Could not open X display
  Failed to connect to Mir: Failed to connect to server socket: Datei oder 
Verzeichnis nicht gefunden
  Unable to init server: Could not connect: Connection refused

  (apport-gtk:21616): Gtk-CRITICAL **: gtk_settings_get_for_screen: 
assertion 'GDK_IS_SCREEN (screen)' failed
  Segmentation fault (core dumped)

  Not a duplicate of #1214783 or #1298782 because error messages are
  different.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1542901/+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 1846440] Re: /usr/share/apport/apport-gtk:11:_gtk_settings_get_screen:gtk_css_value_icon_theme_compute:gtk_css_static_style_compute_value:_gtk_css_lookup_resolve:gtk_css_static_s

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1842439
   apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0)

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

Title:
  /usr/share/apport/apport-
  
gtk:11:_gtk_settings_get_screen:gtk_css_value_icon_theme_compute:gtk_css_static_style_compute_value:_gtk_css_lookup_resolve:gtk_css_static_style_new_compute

Status in apport package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.11-0ubuntu7, the problem page at 
https://errors.ubuntu.com/problem/815a179408135a894bbb5921adef3757563c75c5 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

** Tags added: multimonitor

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

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

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

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

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

Status in mesa package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in xorg-server 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/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 1846440] [NEW] /usr/share/apport/apport-gtk:11:_gtk_settings_get_screen:gtk_css_value_icon_theme_compute:gtk_css_static_style_compute_value:_gtk_css_lookup_resolve:gtk_css_static

[errors.ubuntu.com bug bridge]

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

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.11-0ubuntu7, the problem page at 
https://errors.ubuntu.com/problem/815a179408135a894bbb5921adef3757563c75c5 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: bionic cosmic disco eoan kylin-19.04

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

Title:
  /usr/share/apport/apport-
  
gtk:11:_gtk_settings_get_screen:gtk_css_value_icon_theme_compute:gtk_css_static_style_compute_value:_gtk_css_lookup_resolve:gtk_css_static_style_new_compute

Status in apport package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.11-0ubuntu7, the problem page at 
https://errors.ubuntu.com/problem/815a179408135a894bbb5921adef3757563c75c5 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1846440/+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 1846188] Re: Tooltips in Nautilus 3.34's burger menu are out of place (in Wayland sessions only)

[Daniel van Vugt]

** Also affects: gtk via
   https://gitlab.gnome.org/GNOME/gtk/issues/1427
   Importance: Unknown
   Status: Unknown

-- 
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+:
  Unknown
Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in nautilus package in Ubuntu:
  Invalid

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/gtk/+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 1846201] Re: Rendering is delayed on laptop display (works in external display)

[Daniel van Vugt]

OK, this sounds like a mutter bug... unless that weirdness in your
Xrandr.txt is related:

  eDP-1 connected (normal left inverted right x axis y axis)
  ...
  DP-1 connected primary 2560x1440+0+0 (0x152) normal (normal left inverted 
right x axis y axis) 600mm x 340mm

This means the desktop is arranged primarily to fit your external
monitor (DP-1) but the built-in screen (eDP-1) has no known position. So
it may not update properly. This is too suspicious to ignore so would be
the first thing for someone to look at.

-- 
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:
  New
Status in mutter package in Ubuntu:
  New
Status in xorg-server 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/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 1841718] Re: [radeon] Rendering of combo boxes and tooltips is broken

[Daniel van Vugt]

** Also affects: xserver-xorg-driver-ati via
   https://gitlab.freedesktop.org/xorg/xserver/issues/842
   Importance: Unknown
   Status: Unknown

** No longer affects: mesa (Ubuntu)

** No longer affects: mesa (Ubuntu Eoan)

-- 
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 xserver-xorg-driver-ati:
  Unknown
Status in mutter package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati package in Ubuntu:
  Confirmed
Status in mutter source package in Eoan:
  Invalid
Status in xserver-xorg-video-ati source package in Eoan:
  Confirmed
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 1624320] Re: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries

[Richard Pillay]

Another vote to bump up the priority on this.

Just lost 2 days to this bug, mostly because the behavior is so stupidly
borked that I never suspected that Ubuntu would be the cause. Can you
imagine how stupid it is that the only machines on the network affected
are the Ubuntu Desktops and Ubuntu Servers. Can you imagine how
embarrassing it that even Windows machines follow the standards better
than a Linux machine.

And the absolutely mind-boggling thing is that this is affecting every
release from 16.04 to 19.04 and still it is not considered important
enough to fix.

It is absolutely ridiculous that it would be considered more important
to keep behavior that supports a few edge cases of software that wants
to do their own DNS resolution in spite of the fact that it breaks the
world-wide standards of DNS resolution and ignore DHCP-provided DNS
addresses.

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

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

Status in systemd package in Ubuntu:
  Confirmed

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

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

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

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

[Touch-packages] [Bug 1845319] Re: writing 'add' to /sys/devices/vio/uevent fails with ENODEV

[Bug Watch Updater]

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

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

Title:
  writing 'add' to /sys/devices/vio/uevent fails with ENODEV

Status in systemd:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Eoan:
  Won't Fix
Status in systemd source package in Eoan:
  Invalid

Bug description:
  [impact]

  The systemd-udev-trigger service calls 'udevadm trigger --type=devices
  --action=add', which writes 'add' to all /sys/devices/ uevent nodes,
  to re-generate their uevents sent to udev.  Until systemd commit
  97afc0351a96e0daa83964df33937967c75c644f, any errors during this
  process were simply logged to debug and ignored, but now udevadm will
  log errors and return failure.

  On ppc64el, the /sys/devices/vio device returns ENODEV when writing
  'add' to its uevent, which causes the udevadm command to return
  failure, which causes the systemd-udev-trigger system service to fail.

  The kernel vio driver should be fixed to not return ENODEV.

  [test case]

  On a ppc64el system, with any systemd containing commit
  97afc0351a96e0daa83964df33937967c75c644f, check the status of the
  systemd-udev-trigger service, to see that it's failed.

  Alternately, again on a ppc64el system, run as root:

  # echo add > /sys/devices/vio/uevent
  -bash: echo: write error: No such device

  [regression potential]

  the potential should be low, as this appears to have always behaved
  this way, at least for a while now.

  [other info]

  the systemd commit that changes udevadm to start failing for this
  error isn't included in any Ubuntu release yet, this is found from
  systemd upstream testing.

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

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

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

[Bug Watch Updater]

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

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

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

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

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

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

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

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

[Launchpad Bug Tracker]

This bug was fixed in the package netplan.io - 0.98-0ubuntu1~19.04.1

---
netplan.io (0.98-0ubuntu1~19.04.1) disco; urgency=medium

  * Backport netplan.io 0.98 to 19.04. (LP: #1840832)

 -- Mathieu Trudel-Lapierre   Mon, 26 Aug 2019
16:41:36 -0400

** Changed in: netplan.io (Ubuntu Disco)
   Status: Fix Committed => Fix Released

** Changed in: netplan.io (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  networkd should allow configuring IPV6 MTU

Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Bionic:
  Confirmed
Status in netplan.io source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in cloud-init source package in Disco:
  New
Status in netplan.io source package in Disco:
  Fix Released
Status in systemd source package in Disco:
  New

Bug description:
  = netplan.io =

  [Impact]

   * IPv6 traffic failing to send/receive due to incompatible/low MTU
  setting. Specifically, IPv6 traffic may have higher MTU requirements
  than IPv4 traffic and thus may need to be overridden and/or set to a
  higher value than IPv6 traffic.

  [Test Case]
   * Apply a netplan configuration that specifices ipv6-mtu:

  network:
version: 2
ethernets:
  eth0:
dhcp4: true
dhcp6: true
ipv6-mtu: 6000

   * Check that MTU bytes, is at least IPv6MTUBytes on the interface:

  $ sysctl net.ipv6.conf.eth0.mtu
  net.ipv6.conf.eth0.mtu = 6000

  [Regression Potential]

   * This is a future compatible backport of an additional keyword not
  used by default. It may result in MTU change to a higher value, which
  should not cause loss of connectivity.

  [Other Info]

   * Original bug report below

  = end of netplan.io =

  = systemd =

  [Impact]

   * IPv6 traffic failing to send/receive due to incompatible/low MTU
  setting. Specifically, IPv6 traffic may have higher MTU requirements
  than IPv4 traffic and thus may need to be overridden and/or set to a
  higher value than IPv6 traffic.

  [Test Case]

   * Use IPv6MTUBytes= setting in a .network unit
   * Restart systemd-network
   * Check that there no error messages / warnings about not-recognizing this 
option
   * Check that MTU bytes, is at least IPv6MTUBytes on the interface

  [Regression Potential]

   * This is a future compatible backport of an additional keyword not
  used by default. It may result in MTU change to a higher value, which
  should not cause loss of connectivity.

  [Other Info]

   * Original bug report below

  = end of systemd =

  1) Zesty
  2) systemd-232-19
  3) I need to configure the IPV6 MTU for tunneling by adding an 
IPv6MTUBytes=1480 value in the .network file for an interface with an IPV6 
static address in the [Network] section
  4) networkd does not parse or read the value and does not apply this 
configuration to the interface.

  Upstream has discussed this issue here:

  https://github.com/systemd/systemd/pull/1533

  But it's been closed in favor of only setting via RA.

  However, we know of multiple use-case which are currently supported in
  ifdupdown where we want to retain control over IPV6 MTU values outside
  of PMTU Discovery configurations.

  Some context from those discussions

  >> Client systems that route their ipv6 packets to a 6in4 router also
  >> have to have their ipv6 mtu lowered.  They could lower their link mtu,
  >> so their ipv6 packets are small enough, but that reduces performance
  >> of their ipv4 network.

  Yes.  Anything that creates a PMTUD black hole can result in
  situations where the higher header overhead of IPv6 will cause IPv4 to
  pass but IPv6 traffic to be dropped.

  One example here is egress from an ipsec tunnel wherein the next
  hop MTU is too low for IPv6 datagrams to pass.  Another is VM ->
  whatever -> host bridge -> tunnel ingress.  If the datagram cannot enter
  the tunnel due to size, it is dropped, and an ICMP response uses the
  tunnel address as a source, which may not be routable back to the
  origin.  This one is an issue with IPv4 as well, and is one case where
  manually setting the IPv6 MTU lower than the (also manually set) device
  MTU is of benefit.

  In essence, any of these sort of cases that require an explicit
  setting of the device MTU will likely require a setting of the IPv6 mtu
  as well to account for its larger header overhead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1671951/+subscriptions

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

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

[Launchpad Bug Tracker]

This bug was fixed in the package netplan.io - 0.98-0ubuntu1~18.04.1

---
netplan.io (0.98-0ubuntu1~18.04.1) bionic; urgency=medium

  * Backport netplan.io 0.98 to 18.04. (LP: #1840832)
  * Keep patches specific to 18.04 support:
- disable-networkd-tunnels-ipip-gre.patch: disable tests for unsupported
  tunnel types (ipip and gre) in the 18.04 version of systemd-networkd.
  * Drop debian/patches/glib_changes.patch: No longer necessary, changes were
made upstream to better account for the changes in HashTable.
  * debian/netplan.io.install: add /usr/share/dbus-1

netplan.io (0.98-0ubuntu1) eoan; urgency=medium

  * New upstream release: 0.98 (LP: #1840832)
- Added new "feature flags" to identify new features
- Added support for "use-domains" for DHCP overrides
- Added support for setting IPv6 MTU Bytes (LP: #1671951)
- Added a DBus interface to query and run 'netplan apply' via other apps
- Various build system fixes
- Improved validation for bonding modes
- Added support for "hash:" for hashed 802.1x passwords (LP: #1819831)
- Tolerate devices without a /sys path (LP: #1810043)
- Fix incorrect separator for networkd with ARP IP targets (LP: #1829264)
  * debian/control: Add Build-Depends on libsystemd-dev for DBus feature, and
on dbus-x11 for dbus-launch used in tests.

 -- Mathieu Trudel-Lapierre   Mon, 26 Aug 2019
16:36:03 -0400

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

Title:
  networkd should allow configuring IPV6 MTU

Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Bionic:
  Confirmed
Status in netplan.io source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in cloud-init source package in Disco:
  New
Status in netplan.io source package in Disco:
  Fix Released
Status in systemd source package in Disco:
  New

Bug description:
  = netplan.io =

  [Impact]

   * IPv6 traffic failing to send/receive due to incompatible/low MTU
  setting. Specifically, IPv6 traffic may have higher MTU requirements
  than IPv4 traffic and thus may need to be overridden and/or set to a
  higher value than IPv6 traffic.

  [Test Case]
   * Apply a netplan configuration that specifices ipv6-mtu:

  network:
version: 2
ethernets:
  eth0:
dhcp4: true
dhcp6: true
ipv6-mtu: 6000

   * Check that MTU bytes, is at least IPv6MTUBytes on the interface:

  $ sysctl net.ipv6.conf.eth0.mtu
  net.ipv6.conf.eth0.mtu = 6000

  [Regression Potential]

   * This is a future compatible backport of an additional keyword not
  used by default. It may result in MTU change to a higher value, which
  should not cause loss of connectivity.

  [Other Info]

   * Original bug report below

  = end of netplan.io =

  = systemd =

  [Impact]

   * IPv6 traffic failing to send/receive due to incompatible/low MTU
  setting. Specifically, IPv6 traffic may have higher MTU requirements
  than IPv4 traffic and thus may need to be overridden and/or set to a
  higher value than IPv6 traffic.

  [Test Case]

   * Use IPv6MTUBytes= setting in a .network unit
   * Restart systemd-network
   * Check that there no error messages / warnings about not-recognizing this 
option
   * Check that MTU bytes, is at least IPv6MTUBytes on the interface

  [Regression Potential]

   * This is a future compatible backport of an additional keyword not
  used by default. It may result in MTU change to a higher value, which
  should not cause loss of connectivity.

  [Other Info]

   * Original bug report below

  = end of systemd =

  1) Zesty
  2) systemd-232-19
  3) I need to configure the IPV6 MTU for tunneling by adding an 
IPv6MTUBytes=1480 value in the .network file for an interface with an IPV6 
static address in the [Network] section
  4) networkd does not parse or read the value and does not apply this 
configuration to the interface.

  Upstream has discussed this issue here:

  https://github.com/systemd/systemd/pull/1533

  But it's been closed in favor of only setting via RA.

  However, we know of multiple use-case which are currently supported in
  ifdupdown where we want to retain control over IPV6 MTU values outside
  of PMTU Discovery configurations.

  Some context from those discussions

  >> Client systems that route their ipv6 packets to a 6in4 router also
  >> have to have their ipv6 mtu lowered.  They could lower their link mtu,
  >> so their ipv6 packets are small enough, but that reduces performance
  >> of their ipv4 network.

  Yes.  Anything that creates a PMTUD black hole can result in
  situations where the higher header overhead of IPv6 will cause IPv4 to
  pass but IPv6 traffic to be dropped.

   

[Touch-packages] [Bug 1671951] Update Released

[Brian Murray]

The verification of the Stable Release Update for netplan.io has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  networkd should allow configuring IPV6 MTU

Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Bionic:
  Confirmed
Status in netplan.io source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in cloud-init source package in Disco:
  New
Status in netplan.io source package in Disco:
  Fix Released
Status in systemd source package in Disco:
  New

Bug description:
  = netplan.io =

  [Impact]

   * IPv6 traffic failing to send/receive due to incompatible/low MTU
  setting. Specifically, IPv6 traffic may have higher MTU requirements
  than IPv4 traffic and thus may need to be overridden and/or set to a
  higher value than IPv6 traffic.

  [Test Case]
   * Apply a netplan configuration that specifices ipv6-mtu:

  network:
version: 2
ethernets:
  eth0:
dhcp4: true
dhcp6: true
ipv6-mtu: 6000

   * Check that MTU bytes, is at least IPv6MTUBytes on the interface:

  $ sysctl net.ipv6.conf.eth0.mtu
  net.ipv6.conf.eth0.mtu = 6000

  [Regression Potential]

   * This is a future compatible backport of an additional keyword not
  used by default. It may result in MTU change to a higher value, which
  should not cause loss of connectivity.

  [Other Info]

   * Original bug report below

  = end of netplan.io =

  = systemd =

  [Impact]

   * IPv6 traffic failing to send/receive due to incompatible/low MTU
  setting. Specifically, IPv6 traffic may have higher MTU requirements
  than IPv4 traffic and thus may need to be overridden and/or set to a
  higher value than IPv6 traffic.

  [Test Case]

   * Use IPv6MTUBytes= setting in a .network unit
   * Restart systemd-network
   * Check that there no error messages / warnings about not-recognizing this 
option
   * Check that MTU bytes, is at least IPv6MTUBytes on the interface

  [Regression Potential]

   * This is a future compatible backport of an additional keyword not
  used by default. It may result in MTU change to a higher value, which
  should not cause loss of connectivity.

  [Other Info]

   * Original bug report below

  = end of systemd =

  1) Zesty
  2) systemd-232-19
  3) I need to configure the IPV6 MTU for tunneling by adding an 
IPv6MTUBytes=1480 value in the .network file for an interface with an IPV6 
static address in the [Network] section
  4) networkd does not parse or read the value and does not apply this 
configuration to the interface.

  Upstream has discussed this issue here:

  https://github.com/systemd/systemd/pull/1533

  But it's been closed in favor of only setting via RA.

  However, we know of multiple use-case which are currently supported in
  ifdupdown where we want to retain control over IPV6 MTU values outside
  of PMTU Discovery configurations.

  Some context from those discussions

  >> Client systems that route their ipv6 packets to a 6in4 router also
  >> have to have their ipv6 mtu lowered.  They could lower their link mtu,
  >> so their ipv6 packets are small enough, but that reduces performance
  >> of their ipv4 network.

  Yes.  Anything that creates a PMTUD black hole can result in
  situations where the higher header overhead of IPv6 will cause IPv4 to
  pass but IPv6 traffic to be dropped.

  One example here is egress from an ipsec tunnel wherein the next
  hop MTU is too low for IPv6 datagrams to pass.  Another is VM ->
  whatever -> host bridge -> tunnel ingress.  If the datagram cannot enter
  the tunnel due to size, it is dropped, and an ICMP response uses the
  tunnel address as a source, which may not be routable back to the
  origin.  This one is an issue with IPv4 as well, and is one case where
  manually setting the IPv6 MTU lower than the (also manually set) device
  MTU is of benefit.

  In essence, any of these sort of cases that require an explicit
  setting of the device MTU will likely require a setting of the IPv6 mtu
  as well to account for its larger header overhead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1671951/+subscriptions

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

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

[Brian Murray]

** Also affects: cloud-init (Ubuntu Disco)
   Importance: Undecided
   Status: New

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

** Also affects: netplan.io (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Changed in: netplan.io (Ubuntu Disco)
   Status: New => Fix Committed

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

Title:
  networkd should allow configuring IPV6 MTU

Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Bionic:
  Confirmed
Status in netplan.io source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in cloud-init source package in Disco:
  New
Status in netplan.io source package in Disco:
  Fix Released
Status in systemd source package in Disco:
  New

Bug description:
  = netplan.io =

  [Impact]

   * IPv6 traffic failing to send/receive due to incompatible/low MTU
  setting. Specifically, IPv6 traffic may have higher MTU requirements
  than IPv4 traffic and thus may need to be overridden and/or set to a
  higher value than IPv6 traffic.

  [Test Case]
   * Apply a netplan configuration that specifices ipv6-mtu:

  network:
version: 2
ethernets:
  eth0:
dhcp4: true
dhcp6: true
ipv6-mtu: 6000

   * Check that MTU bytes, is at least IPv6MTUBytes on the interface:

  $ sysctl net.ipv6.conf.eth0.mtu
  net.ipv6.conf.eth0.mtu = 6000

  [Regression Potential]

   * This is a future compatible backport of an additional keyword not
  used by default. It may result in MTU change to a higher value, which
  should not cause loss of connectivity.

  [Other Info]

   * Original bug report below

  = end of netplan.io =

  = systemd =

  [Impact]

   * IPv6 traffic failing to send/receive due to incompatible/low MTU
  setting. Specifically, IPv6 traffic may have higher MTU requirements
  than IPv4 traffic and thus may need to be overridden and/or set to a
  higher value than IPv6 traffic.

  [Test Case]

   * Use IPv6MTUBytes= setting in a .network unit
   * Restart systemd-network
   * Check that there no error messages / warnings about not-recognizing this 
option
   * Check that MTU bytes, is at least IPv6MTUBytes on the interface

  [Regression Potential]

   * This is a future compatible backport of an additional keyword not
  used by default. It may result in MTU change to a higher value, which
  should not cause loss of connectivity.

  [Other Info]

   * Original bug report below

  = end of systemd =

  1) Zesty
  2) systemd-232-19
  3) I need to configure the IPV6 MTU for tunneling by adding an 
IPv6MTUBytes=1480 value in the .network file for an interface with an IPV6 
static address in the [Network] section
  4) networkd does not parse or read the value and does not apply this 
configuration to the interface.

  Upstream has discussed this issue here:

  https://github.com/systemd/systemd/pull/1533

  But it's been closed in favor of only setting via RA.

  However, we know of multiple use-case which are currently supported in
  ifdupdown where we want to retain control over IPV6 MTU values outside
  of PMTU Discovery configurations.

  Some context from those discussions

  >> Client systems that route their ipv6 packets to a 6in4 router also
  >> have to have their ipv6 mtu lowered.  They could lower their link mtu,
  >> so their ipv6 packets are small enough, but that reduces performance
  >> of their ipv4 network.

  Yes.  Anything that creates a PMTUD black hole can result in
  situations where the higher header overhead of IPv6 will cause IPv4 to
  pass but IPv6 traffic to be dropped.

  One example here is egress from an ipsec tunnel wherein the next
  hop MTU is too low for IPv6 datagrams to pass.  Another is VM ->
  whatever -> host bridge -> tunnel ingress.  If the datagram cannot enter
  the tunnel due to size, it is dropped, and an ICMP response uses the
  tunnel address as a source, which may not be routable back to the
  origin.  This one is an issue with IPv4 as well, and is one case where
  manually setting the IPv6 MTU lower than the (also manually set) device
  MTU is of benefit.

  In essence, any of these sort of cases that require an explicit
  setting of the device MTU will likely require a setting of the IPv6 mtu
  as well to account for its larger header overhead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1671951/+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 1845319] Re: writing 'add' to /sys/devices/vio/uevent fails with ENODEV

[Dan Streetman]

systemd upstream PR 13656 merged

** Changed in: systemd (Ubuntu Eoan)
   Status: In Progress => 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/1845319

Title:
  writing 'add' to /sys/devices/vio/uevent fails with ENODEV

Status in systemd:
  Unknown
Status in linux package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Eoan:
  Won't Fix
Status in systemd source package in Eoan:
  Invalid

Bug description:
  [impact]

  The systemd-udev-trigger service calls 'udevadm trigger --type=devices
  --action=add', which writes 'add' to all /sys/devices/ uevent nodes,
  to re-generate their uevents sent to udev.  Until systemd commit
  97afc0351a96e0daa83964df33937967c75c644f, any errors during this
  process were simply logged to debug and ignored, but now udevadm will
  log errors and return failure.

  On ppc64el, the /sys/devices/vio device returns ENODEV when writing
  'add' to its uevent, which causes the udevadm command to return
  failure, which causes the systemd-udev-trigger system service to fail.

  The kernel vio driver should be fixed to not return ENODEV.

  [test case]

  On a ppc64el system, with any systemd containing commit
  97afc0351a96e0daa83964df33937967c75c644f, check the status of the
  systemd-udev-trigger service, to see that it's failed.

  Alternately, again on a ppc64el system, run as root:

  # echo add > /sys/devices/vio/uevent
  -bash: echo: write error: No such device

  [regression potential]

  the potential should be low, as this appears to have always behaved
  this way, at least for a while now.

  [other info]

  the systemd commit that changes udevadm to start failing for this
  error isn't included in any Ubuntu release yet, this is found from
  systemd upstream testing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1845319/+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 1845637] Re: Drop setting fs.protected_regular and fs.protected_fifos from sysctl defaults shipped by systemd

[Balint Reczey]

This is not a bug where logs can be collected.

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

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

Title:
  Drop setting fs.protected_regular and fs.protected_fifos from sysctl
  defaults shipped by systemd

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Those settings are typically set by the kernel in Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845637/+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 1845637] Re: Drop setting fs.protected_regular and fs.protected_fifos from sysctl defaults shipped by systemd

[Balint Reczey]

Those defaults should probably be set by Linux, hence marking linux package as 
affected.
With the systemd packaging dropping the new setting originating from systemd 
upstream Ubuntu's defaults become less secure in this area compared to other 
distros leaving upstream defaults applied, thus I also mark this bug as a 
public security issue.

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

** Information type changed from Public to Public Security

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

Title:
  Drop setting fs.protected_regular and fs.protected_fifos from sysctl
  defaults shipped by systemd

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

Bug description:
  Those settings are typically set by the kernel in Ubuntu.

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

[Ubuntu Kernel Bot]

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

apport-collect 1845637

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

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

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

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

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

Title:
  Drop setting fs.protected_regular and fs.protected_fifos from sysctl
  defaults shipped by systemd

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

Bug description:
  Those settings are typically set by the kernel in Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845637/+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 1846405] [NEW] MSI GS65 8RF key between space and alt-gr in german layout is mapped wrong

[ki za]

Public bug reported:

on a MSI GS65 8RF laptop the key between space and alt-gr is currently
mapped to the same keycode as "#".

Please backport the upstream fix at
https://github.com/systemd/systemd/pull/11508 to fix this.

Without this fix there is no way to type "|", "<" or ">" an this laptop
model when using the german keyboard layout.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: udev 240-6ubuntu5.7
ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
Uname: Linux 5.0.0-29-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CustomUdevRuleFiles: 99-msi-rgb.rules 70-snap.core.rules
Date: Wed Oct  2 22:08:27 2019
InstallationDate: Installed on 2019-09-23 (9 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 1038:1122 SteelSeries ApS 
 Bus 001 Device 003: ID 8087:0aaa Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Micro-Star International Co., Ltd. GS65 Stealth Thin 8RF
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=540feb73-7de0-4295-ba5a-a098cbf5f0b4 ro quiet splash vt.handoff=1
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/21/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E16Q2IMS.112
dmi.board.asset.tag: Default string
dmi.board.name: MS-16Q2
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16Q2IMS.112:bd05/21/2019:svnMicro-StarInternationalCo.,Ltd.:pnGS65StealthThin8RF:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16Q2:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
dmi.product.family: GS
dmi.product.name: GS65 Stealth Thin 8RF
dmi.product.sku: 16Q2.1
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

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


** Tags: amd64 apport-bug disco

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

Title:
  MSI GS65 8RF key between space and alt-gr in german layout is mapped
  wrong

Status in systemd package in Ubuntu:
  New

Bug description:
  on a MSI GS65 8RF laptop the key between space and alt-gr is currently
  mapped to the same keycode as "#".

  Please backport the upstream fix at
  https://github.com/systemd/systemd/pull/11508 to fix this.

  Without this fix there is no way to type "|", "<" or ">" an this
  laptop model when using the german keyboard layout.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: udev 240-6ubuntu5.7
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CustomUdevRuleFiles: 99-msi-rgb.rules 70-snap.core.rules
  Date: Wed Oct  2 22:08:27 2019
  InstallationDate: Installed on 2019-09-23 (9 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 1038:1122 SteelSeries ApS 
   Bus 001 Device 003: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Micro-Star International Co., Ltd. GS65 Stealth Thin 8RF
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=540feb73-7de0-4295-ba5a-a098cbf5f0b4 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/21/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16Q2IMS.112
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16Q2
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16Q2IMS.112:bd05/21/2019:svnMicro-StarInternationalCo.,Ltd.:pnGS65StealthThin8RF:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16Q2:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: GS
  dmi.product.name: GS65 Stealth Thin 8RF
  dmi.product.sku: 16Q2.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

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

[Bryce Harrington]

Hi Nicholas,

The reason for the error you got is because you had a local
configuration setting for ssh in your /etc/ssh/ssh_config:

-Host *
-UseRoaming no

The upgrader was asking whether to keep your changes or revert to the
vanilla config.  Since it timed out without an answer, it defaulted to
keep your configuration changes, which seems sensible in this case.  The
other changes were just deltas in commented-out lines, so would not
affect your installation at all.  I think you can safely ignore the
error.

(It might be nice if the upgrader provided a less confusing UX for
situations such as this, but that's outside the scope of ssh.)

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

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

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 1671951] Re: networkd should allow configuring IPV6 MTU

[Mathieu Trudel-Lapierre]

Verification-done on disco:

ubuntu@ip-172-30-0-243:~$ lsb_release -cs
disco
ubuntu@ip-172-30-0-243:~$ dpkg -l netplan.io systemd | grep ii
ii  netplan.io 0.98-0ubuntu1~19.04.1 amd64YAML network 
configuration abstraction for various backends
ii  systemd240-6ubuntu5.7amd64system and service manager
ubuntu@ip-172-30-0-243:~$ sudo netplan apply
ubuntu@ip-172-30-0-243:~$ ip link
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0:  mtu  qdisc fq_codel state UP 
mode DEFAULT group default qlen 1000
link/ether 06:92:5b:c9:b5:3d brd ff:ff:ff:ff:ff:ff
ubuntu@ip-172-30-0-243:~$ networkctl
IDX LINK TYPE   OPERATIONAL SETUP 
  1 lo   loopback   carrier unmanaged 
  2 eth0 ether  routableconfigured

2 links listed.
ubuntu@ip-172-30-0-243:~$ sysctl net.ipv6.conf.eth0.mtu
net.ipv6.conf.eth0.mtu = 5634
ubuntu@ip-172-30-0-243:~$ cat /etc/netplan/50-cloud-init.yaml 
# This file is generated from information provided by
# the datasource.  Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
version: 2
ethernets:
eth0:
dhcp4: true
match:
macaddress: 06:92:5b:c9:b5:3d
set-name: eth0
ipv6-mtu: 5634
mtu: 
dhcp6: true
dhcp4-overrides:
use-mtu: false
dhcp6-overrides:
use-mtu: false


** Tags added: verification-done-disco

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

Title:
  networkd should allow configuring IPV6 MTU

Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Bionic:
  Confirmed
Status in netplan.io source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  = netplan.io =

  [Impact]

   * IPv6 traffic failing to send/receive due to incompatible/low MTU
  setting. Specifically, IPv6 traffic may have higher MTU requirements
  than IPv4 traffic and thus may need to be overridden and/or set to a
  higher value than IPv6 traffic.

  [Test Case]
   * Apply a netplan configuration that specifices ipv6-mtu:

  network:
version: 2
ethernets:
  eth0:
dhcp4: true
dhcp6: true
ipv6-mtu: 6000

   * Check that MTU bytes, is at least IPv6MTUBytes on the interface:

  $ sysctl net.ipv6.conf.eth0.mtu
  net.ipv6.conf.eth0.mtu = 6000

  [Regression Potential]

   * This is a future compatible backport of an additional keyword not
  used by default. It may result in MTU change to a higher value, which
  should not cause loss of connectivity.

  [Other Info]

   * Original bug report below

  = end of netplan.io =

  = systemd =

  [Impact]

   * IPv6 traffic failing to send/receive due to incompatible/low MTU
  setting. Specifically, IPv6 traffic may have higher MTU requirements
  than IPv4 traffic and thus may need to be overridden and/or set to a
  higher value than IPv6 traffic.

  [Test Case]

   * Use IPv6MTUBytes= setting in a .network unit
   * Restart systemd-network
   * Check that there no error messages / warnings about not-recognizing this 
option
   * Check that MTU bytes, is at least IPv6MTUBytes on the interface

  [Regression Potential]

   * This is a future compatible backport of an additional keyword not
  used by default. It may result in MTU change to a higher value, which
  should not cause loss of connectivity.

  [Other Info]

   * Original bug report below

  = end of systemd =

  1) Zesty
  2) systemd-232-19
  3) I need to configure the IPV6 MTU for tunneling by adding an 
IPv6MTUBytes=1480 value in the .network file for an interface with an IPV6 
static address in the [Network] section
  4) networkd does not parse or read the value and does not apply this 
configuration to the interface.

  Upstream has discussed this issue here:

  https://github.com/systemd/systemd/pull/1533

  But it's been closed in favor of only setting via RA.

  However, we know of multiple use-case which are currently supported in
  ifdupdown where we want to retain control over IPV6 MTU values outside
  of PMTU Discovery configurations.

  Some context from those discussions

  >> Client systems that route their ipv6 packets to a 6in4 router also
  >> have to have their ipv6 mtu lowered.  They could lower their link mtu,
  >> so their ipv6 packets are small enough, but that reduces performance
  >> of

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

[Launchpad Bug Tracker]

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

** Changed in: xserver-xorg-video-ati (Ubuntu)
   Status: New => Confirmed

-- 
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:
  Confirmed
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:
  Confirmed
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 1671951] Re: networkd should allow configuring IPV6 MTU

[Mathieu Trudel-Lapierre]

Verification-done on bionic:

ubuntu@ip-172-30-0-140:/run/systemd/network$ lsb_release -cs
bionic
ubuntu@ip-172-30-0-140:/run/systemd/network$ dpkg -l netplan.io | grep ii
ii  netplan.io 0.98-0ubuntu1~18.04.1 amd64YAML network 
configuration abstraction for various backends
ubuntu@ip-172-30-0-140:/run/systemd/network$ dpkg -l systemd | grep ii
ii  systemd237-3ubuntu10.31 amd64system and service manager
ubuntu@ip-172-30-0-140:/run/systemd/network$ cat 
/etc/netplan/50-cloud-init.yaml 
# This file is generated from information provided by
# the datasource.  Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
version: 2
ethernets:
eth0:
dhcp4: true
match:
macaddress: 06:e0:25:2e:08:ef
set-name: eth0
ipv6-mtu: 5634
mtu: 
dhcp6: true
dhcp4-overrides:
use-mtu: false
dhcp6-overrides:
use-mtu: false
ubuntu@ip-172-30-0-140:/run/systemd/network$ sudo netplan apply
ubuntu@ip-172-30-0-140:/run/systemd/network$ networkctl
IDX LINK TYPE   OPERATIONAL SETUP 
  1 lo   loopback   carrier unmanaged 
  2 eth0 ether  routableconfigured

2 links listed.
ubuntu@ip-172-30-0-140:/run/systemd/network$ sysctl net.ipv6.conf.eth0.mtu
net.ipv6.conf.eth0.mtu = 5634
ubuntu@ip-172-30-0-140:/run/systemd/network$ ip link
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0:  mtu  qdisc fq_codel state UP 
mode DEFAULT group default qlen 1000
link/ether 06:e0:25:2e:08:ef brd ff:ff:ff:ff:ff:ff
ubuntu@ip-172-30-0-140:/run/systemd/network$ 


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

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

Title:
  networkd should allow configuring IPV6 MTU

Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Bionic:
  Confirmed
Status in netplan.io source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  = netplan.io =

  [Impact]

   * IPv6 traffic failing to send/receive due to incompatible/low MTU
  setting. Specifically, IPv6 traffic may have higher MTU requirements
  than IPv4 traffic and thus may need to be overridden and/or set to a
  higher value than IPv6 traffic.

  [Test Case]
   * Apply a netplan configuration that specifices ipv6-mtu:

  network:
version: 2
ethernets:
  eth0:
dhcp4: true
dhcp6: true
ipv6-mtu: 6000

   * Check that MTU bytes, is at least IPv6MTUBytes on the interface:

  $ sysctl net.ipv6.conf.eth0.mtu
  net.ipv6.conf.eth0.mtu = 6000

  [Regression Potential]

   * This is a future compatible backport of an additional keyword not
  used by default. It may result in MTU change to a higher value, which
  should not cause loss of connectivity.

  [Other Info]

   * Original bug report below

  = end of netplan.io =

  = systemd =

  [Impact]

   * IPv6 traffic failing to send/receive due to incompatible/low MTU
  setting. Specifically, IPv6 traffic may have higher MTU requirements
  than IPv4 traffic and thus may need to be overridden and/or set to a
  higher value than IPv6 traffic.

  [Test Case]

   * Use IPv6MTUBytes= setting in a .network unit
   * Restart systemd-network
   * Check that there no error messages / warnings about not-recognizing this 
option
   * Check that MTU bytes, is at least IPv6MTUBytes on the interface

  [Regression Potential]

   * This is a future compatible backport of an additional keyword not
  used by default. It may result in MTU change to a higher value, which
  should not cause loss of connectivity.

  [Other Info]

   * Original bug report below

  = end of systemd =

  1) Zesty
  2) systemd-232-19
  3) I need to configure the IPV6 MTU for tunneling by adding an 
IPv6MTUBytes=1480 value in the .network file for an interface with an IPV6 
static address in the [Network] section
  4) networkd does not parse or read the value and does not apply this 
configuration to the interface.

  Upstream has discussed this issue here:

  https://github.com/systemd/systemd/pull/1533

  But it's been closed in favor of only setting via RA.

  However, we know of multiple use-case which are currently supported in
  ifdupdown where we want to retain control over IPV6 MTU values ou

[Touch-packages] [Bug 1846180] Re: 1910 software-properties larger screen size

[Hans Joachim Desserud]

** Tags added: eoan

-- 
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 1846284] Re: UDEV Symlink Not Created In 19.10

[Greg P]

However, it looks like debian is asking systemd to do this.

Hmmm. I'm talking to a Plex guy in another forum. I'll follow up here,
or he will.

-- 
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 1840817] Re: System won't suspend when closing the lid of my laptop, just shuts down

[Kai-Heng Feng]

If dynamic debug is correctly enabled (comment #6), you should see something 
like:
[   41.607919] ACPI: \_SB_.LID0: ACPI: button: ACPI LID closed

But since there's no such message, it's not a regular ACPI LID device.
Please contact vendor on this issue.

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

Title:
  System won't suspend when closing the lid of my laptop, just shuts
  down

Status in systemd package in Ubuntu:
  New

Bug description:
  1) Using Ubuntu MATE 18.04.3 LTS
  2)systemd: version 237-3ubuntu10.25 /pm-utils: version 1.4.1-17
  3) I expected the laptop to suspend when i closed the lid
  4)It just shut down even though in the logs it reports that it suspended

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.25
  ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18
  Uname: Linux 5.0.0-25-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Aug 20 17:36:30 2019
  InstallationDate: Installed on 2019-08-15 (5 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b52b Chicony Electronics Co., Ltd 
   Bus 001 Device 004: ID 13d3:3423 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X541SC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic 
root=UUID=70ef06f6-6585-41c0-9a60-fd2b8b761810 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [MASKED] /etc/systemd/system/samba-ad-dc.service → 
/lib/systemd/system/samba-ad-dc.service
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X541SC.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X541SC
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX541SC.301:bd09/14/2016:svnASUSTeKCOMPUTERINC.:pnX541SC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541SC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X541SC
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

[Greg P]

Plex for one

-- 
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 1792167] Re: Display size detected incorrectly

[Dark Dragon]

Thanks a lot! I will investigate ways to correct this information:
https://github.com/linuxhw/EDID/issues/4

** Bug watch added: github.com/linuxhw/EDID/issues #4
   https://github.com/linuxhw/EDID/issues/4

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

Title:
  Display size detected incorrectly

Status in mutter package in Ubuntu:
  Invalid
Status in qtbase-opensource-src package in Ubuntu:
  Invalid

Bug description:
  My external monitor is detected as 7" although it is 32". All
  applications which use Qt auto scaling have huge controls!

  It seems like many users have the same problem
  (https://ubuntuforums.org/showthread.php?t=2390362) and thus disable
  Qt auto scaling. I think the solution should be to fix the size
  detection instead.

  It seems not related to the display server, compositor or window
  manager since the problem appeared in Ubuntu 17.04 (Mir, Unity) as
  well es 18.04 (Mutter, Gnome). I tried it with both Wayland and X (on
  Wayland).

  Further, it seems not related to graphics driver, since I personally
  use the open source driver with my internal Intel card, whereas
  someone else uses a proprietary Nvidia driver
  (https://askubuntu.com/q/1066879/206608).

  If it is in the wrong category, please move it / add the corresponding
  packages.

  If you need any further information to tackle the problem, just tell me!
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-09-05 (372 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Package: qtbase-opensource-src
  PackageArchitecture: amd64
  Tags:  bionic
  Uname: Linux 4.18.7-041807-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom davfs2 dip docker lpadmin plugdev sambashare sudo 
vboxusers video voice
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1792167/+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 1846353] Re: On xorg balloon tooltips can be graphically glitched

[Chris Guiver]

Possibly related to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845823, or
https://bugs.launchpad.net/ubuntu/+bug/1845865, maybe even
https://bugs.launchpad.net/ubuntu/eoan/+source/mesa/+bug/1841718

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

Title:
  On xorg balloon tooltips can be graphically glitched

Status in xorg package in Ubuntu:
  New

Bug description:
  On xorg balloon tooltips can be graphically glitched I have Ubuntu
  19.10 development branch with an AMD/ATI Radeon HD 5570. On wayland
  this bug doesn't appear.

  Version of xorg: 1:7.7+19ubuntu12

  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 non accordée: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  2 16:10:45 2019
  DistUpgraded: 2019-09-28 11:48:48,742 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.0.12, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Juniper XT [Radeon HD 
5770] [174b:e147]
  InstallationDate: Installed on 2019-08-13 (49 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: wortmann MBR1|1400G
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=cb9f6c77-c09c-4cd5-810c-bc6a5760a04b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (4 days ago)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: TCIBX10H.86A.0039.2010.0722.1419
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH55TC
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE70932-302
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrTCIBX10H.86A.0039.2010.0722.1419:bd07/22/2010:svnwortmann:pnMBR1|1400G:pvr:rvnIntelCorporation:rnDH55TC:rvrAAE70932-302:cvn:ct3:cvr:
  dmi.product.name: MBR1|1400G
  dmi.sys.vendor: wortmann
  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/1846353/+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 1846353] [NEW] On xorg balloon tooltips can be graphically glitched

[jerareyoshi]

Public bug reported:

On xorg balloon tooltips can be graphically glitched I have Ubuntu 19.10
development branch with an AMD/ATI Radeon HD 5570. On wayland this bug
doesn't appear.

Version of xorg: 1:7.7+19ubuntu12

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 non accordée: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct  2 16:10:45 2019
DistUpgraded: 2019-09-28 11:48:48,742 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: eoan
DistroVariant: ubuntu
DkmsStatus: virtualbox, 6.0.12, 5.3.0-13-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] 
(prog-if 00 [VGA controller])
   Subsystem: PC Partner Limited / Sapphire Technology Juniper XT [Radeon HD 
5770] [174b:e147]
InstallationDate: Installed on 2019-08-13 (49 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: wortmann MBR1|1400G
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=cb9f6c77-c09c-4cd5-810c-bc6a5760a04b ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to eoan on 2019-09-28 (4 days ago)
dmi.bios.date: 07/22/2010
dmi.bios.vendor: Intel Corp.
dmi.bios.version: TCIBX10H.86A.0039.2010.0722.1419
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DH55TC
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE70932-302
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrTCIBX10H.86A.0039.2010.0722.1419:bd07/22/2010:svnwortmann:pnMBR1|1400G:pvr:rvnIntelCorporation:rnDH55TC:rvrAAE70932-302:cvn:ct3:cvr:
dmi.product.name: MBR1|1400G
dmi.sys.vendor: wortmann
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 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/1846353

Title:
  On xorg balloon tooltips can be graphically glitched

Status in xorg package in Ubuntu:
  New

Bug description:
  On xorg balloon tooltips can be graphically glitched I have Ubuntu
  19.10 development branch with an AMD/ATI Radeon HD 5570. On wayland
  this bug doesn't appear.

  Version of xorg: 1:7.7+19ubuntu12

  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 non accordée: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  2 16:10:45 2019
  DistUpgraded: 2019-09-28 11:48:48,742 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.0.12, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Juniper XT [Radeon HD 
5770] [174b:e147]
  InstallationDate: Installed on 2019-08-13 (49 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: wortmann MBR1|1400G
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=cb9f6c77-c09c-4cd5-810c-bc6a5760a04b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (4 days ago)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: TCIBX10H.86A.0039.2010.0722.1419
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH55TC
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE70932-302
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrTCIBX10H.86A.0039.2010.0722.1419:bd07/22/2010:svnwortmann:pnMBR1|1400G:pvr:rvnInt

[Touch-packages] [Bug 1788121] Re: pulseaudio stops playing audio with "Failed to create sink input: sink is suspended"

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

Title:
  pulseaudio stops playing audio with "Failed to create sink input: sink
  is suspended"

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Audio stopped playing, causing all video playback to also wedge unless
  sound output was disabled.

  The only meaningful log message was tens of the following in
  /var/log/syslog:

  [pulseaudio] sink-input.c: Failed to create sink input: sink is
  suspended.

  Sending pulseaudio a SIGHUP had no effect. Killing it caused it to
  restart, however the sound device was no longer present. The sound
  device is built-in laptop audio, so it is still physically present,
  although it's plausible that the problem is at a lower level. rmmoding
  and modprobing snd_hda_intel did not resolve the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmj1391 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue Aug 21 17:35:32 2018
  InstallationDate: Installed on 2018-03-12 (162 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/14/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SSU Ver. F.01
  dmi.board.name: 162B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 04.1C
  dmi.chassis.asset.tag: CNU1311SY3
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SSUVer.F.01:bd04/14/2011:svnHewlett-Packard:pnHPEliteBook2560p:pvrA0001D02:rvnHewlett-Packard:rn162B:rvrKBCVersion04.1C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 2560p
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1788121/+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 1788121] Re: pulseaudio stops playing audio with "Failed to create sink input: sink is suspended"

[John]

Nope, didn't work. Will carry on watching this thread...

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

Title:
  pulseaudio stops playing audio with "Failed to create sink input: sink
  is suspended"

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Audio stopped playing, causing all video playback to also wedge unless
  sound output was disabled.

  The only meaningful log message was tens of the following in
  /var/log/syslog:

  [pulseaudio] sink-input.c: Failed to create sink input: sink is
  suspended.

  Sending pulseaudio a SIGHUP had no effect. Killing it caused it to
  restart, however the sound device was no longer present. The sound
  device is built-in laptop audio, so it is still physically present,
  although it's plausible that the problem is at a lower level. rmmoding
  and modprobing snd_hda_intel did not resolve the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmj1391 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue Aug 21 17:35:32 2018
  InstallationDate: Installed on 2018-03-12 (162 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/14/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SSU Ver. F.01
  dmi.board.name: 162B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 04.1C
  dmi.chassis.asset.tag: CNU1311SY3
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SSUVer.F.01:bd04/14/2011:svnHewlett-Packard:pnHPEliteBook2560p:pvrA0001D02:rvnHewlett-Packard:rn162B:rvrKBCVersion04.1C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 2560p
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1788121/+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 1788121] Re: pulseaudio stops playing audio with "Failed to create sink input: sink is suspended"

[John]

Similar issue, though manifests on my system by a double beep every time
it happens. May be linked to playing music through
GooglePlayMusicDesktopPlayer, and only through the internal soundcard
jack, not with USB headphones.

Trying updating GMPDP

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

Title:
  pulseaudio stops playing audio with "Failed to create sink input: sink
  is suspended"

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Audio stopped playing, causing all video playback to also wedge unless
  sound output was disabled.

  The only meaningful log message was tens of the following in
  /var/log/syslog:

  [pulseaudio] sink-input.c: Failed to create sink input: sink is
  suspended.

  Sending pulseaudio a SIGHUP had no effect. Killing it caused it to
  restart, however the sound device was no longer present. The sound
  device is built-in laptop audio, so it is still physically present,
  although it's plausible that the problem is at a lower level. rmmoding
  and modprobing snd_hda_intel did not resolve the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmj1391 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue Aug 21 17:35:32 2018
  InstallationDate: Installed on 2018-03-12 (162 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/14/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SSU Ver. F.01
  dmi.board.name: 162B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 04.1C
  dmi.chassis.asset.tag: CNU1311SY3
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SSUVer.F.01:bd04/14/2011:svnHewlett-Packard:pnHPEliteBook2560p:pvrA0001D02:rvnHewlett-Packard:rn162B:rvrKBCVersion04.1C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 2560p
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1788121/+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 1840640] Re: sync_file_range fails in nspawn containers on arm, ppc

[Dan Streetman]

** Changed in: systemd (Ubuntu Disco)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: systemd (Ubuntu Bionic)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

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

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

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

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

Title:
  sync_file_range fails in nspawn containers on arm, ppc

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

Bug description:
  ARM has two sync_file_range syscalls, sync_file_range and
  sync_file_range2. The former is apparently not used, and glibc calls
  the latter whenever a userspace program calls sync_file_range. I'm
  guessing systemd-nspawn doesn't know this, because the follow code
  consistently fails in an nspawn container on ARM:

  #define _GNU_SOURCE
  #include 
  #include 
  #include 
  #include 

  void main()
  {
  int f = open("/tmp/syncrange.test",O_CREAT|O_RDWR,0666);
  int r=sync_file_range(f, 0, 0, 0);
  if (r)
  perror("sync_file_range");
  close(f);
  }

  This seems to be causing problems specifically for borg(backup) and
  postgres:

  https://github.com/borgbackup/borg/issues/4710
  
https://www.postgresql.org/message-id/flat/CA%2BhUKG%2BydOUT4zjxb6QmJWy8U9WbC-q%2BJWV7wLsEY9Df%3Dmw0Mw%40mail.gmail.com#ac8f14897647dc7eae3c7e7cbed36d93

  The solution should be to cherrypick
  https://github.com/systemd/systemd/pull/13352, I am currently waiting
  for systemd to rebuild on a slow ARM box. Any chance of an SRU?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd-container 237-3ubuntu10.24
  Uname: Linux 4.14.66+ armv7l
  NonfreeKernelModules: extcon_usb_gpio
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: armhf
  Date: Mon Aug 19 11:10:48 2019
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1840640/+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 1843812] Re: apt info "please use the '-a' switch"

[Julian Andres Klode]

** Changed in: apt (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  apt info "please use the '-a' switch"

Status in apt package in Ubuntu:
  Fix Committed

Bug description:
  When getting info about a package, I see a notice asking me to "Please
  use the '-a' switch", but the apt program does not accept an '-a'
  switch.

  Steps to reproduce:
  $ apt info docker.io
  ...
  N: There is 1 additional record. Please use the '-a' switch to see it
  $ apt -a info docker.io
  $ apt info -a docker.io
  $ apt info docker.io -a

  Expected outcome:
  same output as `apt info docker.io` but with the 1 additional record.

  Seen outcome:
  E: Command line option 'a' [from -a] is not understood in combination with 
the other options.

  Also seen:
  `apt info $pkg` gives the same output as `apt show $pkg` including the Notice 
message, but where `apt info -a $pkg` fails, `apt show -a $pkg` succeeds.

  Workaround:
  Use `apt show -a $pkg` instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: apt 1.8.1
  ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Sep 12 14:16:09 2019
  InstallationDate: Installed on 2018-10-30 (316 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: apt
  UpgradeStatus: Upgraded to disco on 2019-04-18 (147 days ago)
  modified.conffile..etc.logrotate.d.apport: [modified]
  modified.conffile..etc.logrotate.d.apt: [modified]
  mtime.conffile..etc.logrotate.d.apport: 2018-12-13T12:13:33.355709
  mtime.conffile..etc.logrotate.d.apt: 2018-12-13T12:13:41.355709

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1843812/+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 1846053] Re: Use llvm 9 or even llvm-10

[Timo Aaltonen]

19.2.0 uses llvm9

** Changed in: mesa (Ubuntu)
   Status: New => 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/1846053

Title:
  Use llvm 9 or even llvm-10

Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  1. llvm 9 has been released, but mesa in the repo still uses llvm 8.
  2. llvm 9 bitcode libs for OpenCL cause llvm-8-based mesa to fail because 
their file format has changed
  3. There was a bug in llvm-8-based mesa in disco that caused the OpenCL 
compiler to hang on the kernels combining hyperbolic and circular functions. 
There were no hang after I have rebuilt mesa and dri against llvm-10.

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

wow, yes, it does!

-- 
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)

[Daniele Dellafiore]

I mean, the video aligned right fixes the problem

-- 
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 1846334] Re: cupsd assert failure: free(): invalid pointer

[Till Kamppeter]

** Information type changed from Private to Public

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

Title:
  cupsd assert failure: free(): invalid pointer

Status in cups package in Ubuntu:
  New

Bug description:
  Just running in the background, no user action (printing)

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: cups-daemon 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-16.17-generic 5.3.1
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AssertionMessage: free(): invalid pointer
  Date: Tue Oct  1 19:41:35 2019
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2019-02-09 (234 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  Lpstat:
   device for HP_LaserJet_CM1415fn_44A808_: 
implicitclass://HP_LaserJet_CM1415fn_44A808_/
   device for Samsung_C48x_Series_SEC84251900EE44_: 
implicitclass://Samsung_C48x_Series_SEC84251900EE44_/
  MachineType: Dell Inc. Latitude E6530
  Papersize: letter
  PpdFiles:
   HP_LaserJet_CM1415fn_44A808_: LaserJet CM1415fn - IPP Everywhere
   Samsung_C48x_Series_SEC84251900EE44_: C48x Series - IPP Everywhere
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-16-generic 
root=UUID=4cc2c833-0db9-4a3d-84d1-9f00f5785fca ro quiet splash vt.handoff=7
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-16-generic 
root=UUID=4cc2c833-0db9-4a3d-84d1-9f00f5785fca ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: cups
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f923ecb83a5 
"%s\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (str=str@entry=0x7f923ecb652a "free(): invalid pointer") at 
malloc.c:5332
   _int_free (av=, p=, have_lock=0) at 
malloc.c:4173
   ?? () from /lib/x86_64-linux-gnu/libcups.so.2
   ippDelete () from /lib/x86_64-linux-gnu/libcups.so.2
  Title: cupsd assert failure: free(): invalid pointer
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/30/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A22
  dmi.board.name: 07Y85M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA22:bd11/30/2018:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6530
  dmi.product.sku: Latitude E6530
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1846334/+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 1827753] Re: udev package doesn't mark as a configuration file fbdev-blacklist.conf

[Balint Reczey]

@chaitrex, IMO the workaround proposed by @ddstreet in #2 is the simplest 
solution, overriding default configuration by placing a configuration in /etc 
and this also follows the general concept of how systems should be configured.
The big miss here is not having the behavior documented in modprobe.d(5).

Since the file in /lib/modprobe.d can be overridden by placing an identically 
named file in /etc i don't think that making the file shipped in 
/lib/modprobe.d is necessary or desired.
Also we would like to go in the direction of not shipping files in /etc by 
default, so moving the file to /etc would be a step back.

As a side note in similar situation the system administrator can use
dpkg-divert to keep a file from being overwritten by a package upgrade.


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

** Changed in: kmod (Ubuntu)
   Importance: Undecided => Wishlist

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

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

** Changed in: kmod (Ubuntu)
   Status: New => Triaged

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

Title:
  udev package doesn't mark as a configuration file fbdev-blacklist.conf

Status in kmod package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Opinion

Bug description:
  System information
  

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

  $ apt-cache policy udev
  udev:
    Installed: 237-3ubuntu10.21
    Candidate: 237-3ubuntu10.21
    Version table:
   *** 237-3ubuntu10.21 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   237-3ubuntu10.19 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   237-3ubuntu10 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

   Problem
  =

  The `udev` package includes `/lib/modprobe.d/fbdev-blacklist.conf`, a
  configuration file blacklisting several kernel modules. It's not
  listed as a configuration file in the package, though:

  $ cat /var/lib/dpkg/info/udev.conffiles
  /etc/init.d/udev
  /etc/udev/udev.conf

  This means that, if I want to go ahead and use the `sisfb` kernel
  module, for example, I unblacklist it in the two files it's
  blacklisted in. However, any updated version of `udev` that's
  installed will throw away my changes to `/lib/modprobe.d/fbdev-
  blacklist.conf` by simply overwriting the file and again blacklist the
  kernel module, which doesn't work well when the system is being used
  by someone very new to computers.

  I can't avoid that by simply telling APT to leave configuration files
  alone because the `.conf` file here technically isn't a configuration
  file. Also, `chattr +i /lib/modprobe.d/fbdev-blacklist.conf` causes
  APT to require someone with technical knowledge to take extra effort
  to repair things when the end user agrees to an install in the weekly
  GUI reminder of new software.

   Request
  =

  Please mark `/lib/modprobe.d/fbdev-blacklist.conf` as a configuration
  file in `udev`.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: udev 237-3ubuntu10.21
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: XFCE
  CustomUdevRuleFiles: 70-snap.core.rules 70-snap.cnctsun.rules 
70-snap.cncra2yr.rules 70-snap.cncra.rules 60-vboxdrv.rules
  Date: Sat May  4 21:51:42 2019
  InstallationDate: Installed on 2018-12-27 (128 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 020: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/27/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.10.0
  dmi.board.name: 0839Y6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.10.0:bd09/27/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0839Y6:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing l

[Touch-packages] [Bug 1840640] Re: sync_file_range fails in nspawn containers on arm, ppc

[Dan Streetman]

** Tags removed: next-ddstreet
** Tags added: ddstreet disco

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

Title:
  sync_file_range fails in nspawn containers on arm, ppc

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

Bug description:
  ARM has two sync_file_range syscalls, sync_file_range and
  sync_file_range2. The former is apparently not used, and glibc calls
  the latter whenever a userspace program calls sync_file_range. I'm
  guessing systemd-nspawn doesn't know this, because the follow code
  consistently fails in an nspawn container on ARM:

  #define _GNU_SOURCE
  #include 
  #include 
  #include 
  #include 

  void main()
  {
  int f = open("/tmp/syncrange.test",O_CREAT|O_RDWR,0666);
  int r=sync_file_range(f, 0, 0, 0);
  if (r)
  perror("sync_file_range");
  close(f);
  }

  This seems to be causing problems specifically for borg(backup) and
  postgres:

  https://github.com/borgbackup/borg/issues/4710
  
https://www.postgresql.org/message-id/flat/CA%2BhUKG%2BydOUT4zjxb6QmJWy8U9WbC-q%2BJWV7wLsEY9Df%3Dmw0Mw%40mail.gmail.com#ac8f14897647dc7eae3c7e7cbed36d93

  The solution should be to cherrypick
  https://github.com/systemd/systemd/pull/13352, I am currently waiting
  for systemd to rebuild on a slow ARM box. Any chance of an SRU?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd-container 237-3ubuntu10.24
  Uname: Linux 4.14.66+ armv7l
  NonfreeKernelModules: extcon_usb_gpio
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: armhf
  Date: Mon Aug 19 11:10:48 2019
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1839290] Re: systemd doesn't restart a service after crashes

[Dan Streetman]

** Tags removed: next-ddstreet
** Tags added: bionic ddstreet xenial

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

Title:
  systemd doesn't restart a service after crashes

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1783994] Re: systemd spams log with "Failed to dissect: Input/output error" on systems with mmc

[Dan Streetman]

** Tags removed: next-ddstreet
** Tags added: ddstreet

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

Title:
  systemd spams log with "Failed to dissect: Input/output error" on
  systems with mmc

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

Bug description:
  If a device has an mmc installed, systemd-gpt-auto-generator will fail 
because of "special partition" (rpmb, boot) and record a log message: 
  systemd-gpt-auto-generator[207]: Failed to dissect: Input/output error
  This issue was discussed here:  https://github.com/systemd/systemd/issues/5806
  and a fix is proposed for new systemd versions. Please include in bionic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1783994/+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 1832672] Re: systemd-resolve not ignoring comments in /etc/hosts

[Dan Streetman]

** Tags removed: next-ddstreet
** Tags added: bionic ddstreet

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

Title:
  systemd-resolve not ignoring comments in /etc/hosts

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  In Progress

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  $ LANG=C apt-cache policy systemd
  systemd:
Installed: 237-3ubuntu10.22
Candidate: 237-3ubuntu10.22
Version table:
   *** 237-3ubuntu10.22 500
  500 http://ch.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   237-3ubuntu10.19 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   237-3ubuntu10 500
  500 http://ch.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  500 http://mirrors.kernel.org/ubuntu bionic/main amd64 Packages

  
  $ head -1 /etc/hosts
  127.0.2.1 foo # bar

  $ /usr/bin/systemd-resolve -4 bar

  expected
  --
  bar: resolve call failed: 'bar' not found

  What happened instead
  -
  bar: 127.0.2.1


  HOSTS(5)  
  > Text from a "#" character until the end of the line is a comment, and is 
ignored.

  This is fixed in upstream:
  https://github.com/systemd/systemd/issues/10779
  
https://github.com/systemd/systemd/commit/bd0052777981044cf54a1e9d6e3acb1c3d813656

  Please backport to current LTS version.
  I accidentally connected to wrong systems because of this bug.

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

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

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

[Dan Streetman]

** Tags added: bionic disco eoan next-ddstreet systemd

** Tags removed: next-ddstreet
** Tags added: ddstreet

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

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

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

Title:
  Bogus routes after DHCP lease change

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

Bug description:
  Netplan config:

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

  On initial boot, machine got 10.0.15.109 IP address:

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

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

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

  This resulted in IP addresses:

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

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

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

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

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

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

[Touch-packages] [Bug 1843007] Re: namespace: make MountFlags=shared work again

[Dan Streetman]

** Tags removed: next-ddstreet
** Tags added: ddstreet

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

Title:
  namespace: make MountFlags=shared work again

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

Bug description:
  Systemd in Bionic fails to handle MountFlags correctly. Would you mind
  to include
  
https://github.com/systemd/systemd/commit/37ed15d7edaf59a1fc7c9e3552cd93a83f3814ef
  into Bionic? This bug seriously affects Docker > 18.6, see the Docker
  release notes for 18.09.1 (https://docs.docker.com/engine/release-
  notes/#18091).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1843007/+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 1845337] Re: Disco autopkgtest @ armhf fails root-unittests -> test-execute -> exec-dynamicuser-statedir.service

[Dan Streetman]

** Tags removed: next-ddstreet
** Tags added: ddstreet disco

** Tags removed: ddstreet

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

Title:
  Disco autopkgtest @ armhf fails root-unittests -> test-execute ->
  exec-dynamicuser-statedir.service

Status in qemu package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in qemu source package in Disco:
  Confirmed
Status in systemd source package in Disco:
  Confirmed

Bug description:
  Since the recent few weeks systemd autopkgtest @ armhf @ disco fail
  [1].

  The log is very (very) long and partially interwoven due to concurrent 
execution.
  Somewhere in between we see this subcase is the one failing: root-unittests
  Of this test (which again has many subtests) it is: test-execute
  And of this again it is (always):

  I'll attach bad and good case full and stripped logs.

  
  The diff of those comes down to just:
  1. execute a find in a shell
  2. shell exits
  3. exec-dynamicuser-statedir.service: Main process exited, code=exited, 
status=0/SUCCESS
  vs
  3. exec-dynamicuser-statedir.service: Main process exited, code=exited, 
status=1/FAILURE
  4. in the bad case that triggers an assertion
  The find that fails is:

  find / -path /var/tmp -o -path /tmp -o -path /proc -o -path
  /dev/mqueue -o -path /dev/shm -o -path /sys/fs/bpf

  Good and bad case are the same most recent version
  systemd/240-6ubuntu5.7.

  Maybe something is bad in the containers we have for armhf in regard to these 
paths?
  Was there any change we'd know of?

  If there is nothing known, could we force-badtest it to get it out of
  the way of ongoing migrations?

  [1]: http://autopkgtest.ubuntu.com/packages/s/systemd/disco/armhf

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

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

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

[Dan Streetman]

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

** Changed in: systemd (Ubuntu Disco)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: systemd (Ubuntu Bionic)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

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

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

Title:
  Bogus routes after DHCP lease change

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

Bug description:
  Netplan config:

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

  On initial boot, machine got 10.0.15.109 IP address:

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

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

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

  This resulted in IP addresses:

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

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

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

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

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

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

[Touch-packages] [Bug 714545] Re: kerning doesn't work with linux libertine

[Hugh McMaster]

Closing. Fixed.

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

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

Title:
  kerning doesn't work with linux libertine

Status in freetype package in Ubuntu:
  Fix Released

Bug description:
  The kerning of Linux libertine had worked in ubuntu 10.04 (still works on my 
laptop), but doesn't work anymore in ubuntu 10.10 . 
  I have tried all versions of the font (package, otf, ttf), but still it 
doesn't work in open/libre office and in wine (papyrus). The only program I 
have seen that has correct kerning is abiword, but I think it uses the open 
type routines on its own ...

  libfreetype6:
Installiert: 2.4.2-2ubuntu0.1
Kandidat:2.4.2-2ubuntu0.1
Versionstabelle:
   *** 2.4.2-2ubuntu0.1 0
  500 http://archive.ubuntu.com/ubuntu/ maverick-updates/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu/ maverick-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.4.2-2 0
  500 http://archive.ubuntu.com/ubuntu/ maverick/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: libfreetype6 2.4.2-2ubuntu0.1
  ProcVersionSignature: Ubuntu 2.6.35-25.43-generic 2.6.35.10
  Uname: Linux 2.6.35-25-generic x86_64
  NonfreeKernelModules: fglrx
  Architecture: amd64
  Date: Mon Feb  7 13:13:46 2011
  ProcEnviron:
   LANGUAGE=de_DE:de:en_GB:en
   PATH=(custom, user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: freetype

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/714545/+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 1840817] Re: System won't suspend when closing the lid of my laptop, just shuts down

[Nath_SoM R.]

here's the log:

Okt 02 12:41:36 nathsom-X541SC kernel: pci :02:00.0: reg 0x10: [io  
0xd000-0xd0ff]
Okt 02 12:41:36 nathsom-X541SC kernel: pci :02:00.0: reg 0x18: [mem 
0x8240-0x82400fff 64bit]
Okt 02 12:41:36 nathsom-X541SC kernel: pci :02:00.0: reg 0x20: [mem 
0xb210-0xb2103fff 64bit pref]
Okt 02 12:41:36 nathsom-X541SC kernel: pci :02:00.0: supports D1 D2
Okt 02 12:41:36 nathsom-X541SC kernel: pci :02:00.0: PME# supported from D0 
D1 D2 D3hot D3cold
Okt 02 12:41:36 nathsom-X541SC kernel: pci :00:1c.2: PCI bridge to [bus 02]
Okt 02 12:41:36 nathsom-X541SC kernel: pci :00:1c.2:   bridge window [io  
0xd000-0xdfff]
Okt 02 12:41:36 nathsom-X541SC kernel: pci :00:1c.2:   bridge window [mem 
0x8240-0x824f]
Okt 02 12:41:36 nathsom-X541SC kernel: pci :00:1c.2:   bridge window [mem 
0xb210-0xb21f 64bit pref]
Okt 02 12:41:36 nathsom-X541SC kernel: pci :03:00.0: [168c:0036] type 00 
class 0x028000
Okt 02 12:41:36 nathsom-X541SC kernel: pci :03:00.0: reg 0x10: [mem 
0x8230-0x8237 64bit]
Okt 02 12:41:36 nathsom-X541SC kernel: pci :03:00.0: reg 0x30: [mem 
0x8238-0x8238 pref]
Okt 02 12:41:36 nathsom-X541SC kernel: pci :03:00.0: supports D1 D2
Okt 02 12:41:36 nathsom-X541SC kernel: pci :03:00.0: PME# supported from D0 
D1 D2 D3hot D3cold
Okt 02 12:41:36 nathsom-X541SC kernel: pci :00:1c.3: PCI bridge to [bus 03]
Okt 02 12:41:36 nathsom-X541SC kernel: pci :00:1c.3:   bridge window [mem 
0x8230-0x823f]
Okt 02 12:41:36 nathsom-X541SC kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 
4 5 6 7 10 11 12) *0, disabled.
Okt 02 12:41:36 nathsom-X541SC kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 
4 5 6 7 10 12) *0, disabled.
Okt 02 12:41:36 nathsom-X541SC kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 
4 5 6 7 10 12) *0, disabled.
Okt 02 12:41:36 nathsom-X541SC kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 
4 5 6 7 10 12) *0, disabled.
Okt 02 12:41:36 nathsom-X541SC kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 
4 5 6 7 10 12) *0, disabled.
Okt 02 12:41:36 nathsom-X541SC kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 
4 5 6 7 10 12) *0, disabled.
Okt 02 12:41:36 nathsom-X541SC kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 
4 5 6 7 10 12) *0, disabled.
Okt 02 12:41:36 nathsom-X541SC kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 
4 5 6 7 10 12) *0, disabled.
Okt 02 12:41:36 nathsom-X541SC kernel: gpio gpiochip1: (INT33FF:01): detected 
irqchip that is shared with multiple gpiochips: please fix the driver.
Okt 02 12:41:36 nathsom-X541SC kernel: gpio gpiochip2: (INT33FF:02): detected 
irqchip that is shared with multiple gpiochips: please fix the driver.
Okt 02 12:41:36 nathsom-X541SC kernel: gpio gpiochip3: (INT33FF:03): detected 
irqchip that is shared with multiple gpiochips: please fix the driver.
Okt 02 12:41:36 nathsom-X541SC kernel: ACPI: EC: interrupt unblocked
Okt 02 12:41:36 nathsom-X541SC kernel: ACPI: EC: event unblocked
Okt 02 12:41:36 nathsom-X541SC kernel: ACPI: \_SB_.PCI0.SBRG.EC0_: GPE=0x16, 
EC_CMD/EC_SC=0x66, EC_DATA=0x62
Okt 02 12:41:36 nathsom-X541SC kernel: ACPI: \_SB_.PCI0.SBRG.EC0_: Used as boot 
DSDT EC to handle transactions and events
Okt 02 12:41:36 nathsom-X541SC kernel: SCSI subsystem initialized
Okt 02 12:41:36 nathsom-X541SC kernel: libata version 3.00 loaded.
Okt 02 12:41:36 nathsom-X541SC kernel: pci :00:02.0: vgaarb: setting as 
boot VGA device
Okt 02 12:41:36 nathsom-X541SC kernel: pci :00:02.0: vgaarb: VGA device 
added: decodes=io+mem,owns=io+mem,locks=none
Okt 02 12:41:36 nathsom-X541SC kernel: pci :00:02.0: vgaarb: bridge control 
possible
Okt 02 12:41:36 nathsom-X541SC kernel: vgaarb: loaded
Okt 02 12:41:36 nathsom-X541SC kernel: ACPI: bus type USB registered
Okt 02 12:41:36 nathsom-X541SC kernel: usbcore: registered new interface driver 
usbfs
Okt 02 12:41:36 nathsom-X541SC kernel: usbcore: registered new interface driver 
hub
Okt 02 12:41:36 nathsom-X541SC kernel: usbcore: registered new device driver usb
Okt 02 12:41:36 nathsom-X541SC kernel: pps_core: LinuxPPS API ver. 1 registered
Okt 02 12:41:36 nathsom-X541SC kernel: pps_core: Software ver. 5.3.6 - 
Copyright 2005-2007 Rodolfo Giometti 
Okt 02 12:41:36 nathsom-X541SC kernel: PTP clock support registered
Okt 02 12:41:36 nathsom-X541SC kernel: EDAC MC: Ver: 3.0.0
Okt 02 12:41:36 nathsom-X541SC kernel: Registered efivars operations
Okt 02 12:41:36 nathsom-X541SC kernel: PCI: Using ACPI for IRQ routing
Okt 02 12:41:36 nathsom-X541SC kernel: PCI: pci_cache_line_size set to 64 bytes
Okt 02 12:41:36 nathsom-X541SC kernel: e820: reserve RAM buffer [mem 
0x0003f000-0x0003]
Okt 02 12:41:36 nathsom-X541SC kernel: e820: reserve RAM buffer [mem 
0x0009e000-0x0009]
Okt 02 12:41:36 nathsom-X541SC kernel: e820: reserve RAM buffer [mem 
0x1f00-0x1fff]
Okt 02 12:41:36 nathsom-X541SC kernel: e820: reserve RAM buffer [mem 
0x769b9018-0x77ff]
Okt 02 12:41:36 nathsom-X541SC kernel: e820: reserve RAM bu

[Touch-packages] [Bug 1840817] Re: System won't suspend when closing the lid of my laptop, just shuts down

[Nath_SoM R.]

Wait I just realized what you meant, sorry.

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

Title:
  System won't suspend when closing the lid of my laptop, just shuts
  down

Status in systemd package in Ubuntu:
  New

Bug description:
  1) Using Ubuntu MATE 18.04.3 LTS
  2)systemd: version 237-3ubuntu10.25 /pm-utils: version 1.4.1-17
  3) I expected the laptop to suspend when i closed the lid
  4)It just shut down even though in the logs it reports that it suspended

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.25
  ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18
  Uname: Linux 5.0.0-25-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Aug 20 17:36:30 2019
  InstallationDate: Installed on 2019-08-15 (5 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b52b Chicony Electronics Co., Ltd 
   Bus 001 Device 004: ID 13d3:3423 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X541SC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic 
root=UUID=70ef06f6-6585-41c0-9a60-fd2b8b761810 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [MASKED] /etc/systemd/system/samba-ad-dc.service → 
/lib/systemd/system/samba-ad-dc.service
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X541SC.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X541SC
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX541SC.301:bd09/14/2016:svnASUSTeKCOMPUTERINC.:pnX541SC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541SC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X541SC
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1840817/+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 1840817] Re: System won't suspend when closing the lid of my laptop, just shuts down

[Nath_SoM R.]

How do i attach te command?
do I do sudo pm-suspend && journalctl -k -b -1 ?

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

Title:
  System won't suspend when closing the lid of my laptop, just shuts
  down

Status in systemd package in Ubuntu:
  New

Bug description:
  1) Using Ubuntu MATE 18.04.3 LTS
  2)systemd: version 237-3ubuntu10.25 /pm-utils: version 1.4.1-17
  3) I expected the laptop to suspend when i closed the lid
  4)It just shut down even though in the logs it reports that it suspended

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.25
  ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18
  Uname: Linux 5.0.0-25-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Aug 20 17:36:30 2019
  InstallationDate: Installed on 2019-08-15 (5 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b52b Chicony Electronics Co., Ltd 
   Bus 001 Device 004: ID 13d3:3423 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X541SC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic 
root=UUID=70ef06f6-6585-41c0-9a60-fd2b8b761810 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [MASKED] /etc/systemd/system/samba-ad-dc.service → 
/lib/systemd/system/samba-ad-dc.service
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X541SC.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X541SC
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX541SC.301:bd09/14/2016:svnASUSTeKCOMPUTERINC.:pnX541SC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541SC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X541SC
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1840817/+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 1846188] Re: Tooltips in Nautilus 3.34's burger menu are out of place (in Wayland sessions only)

[Sebastien Bacher]

looks like the commit was not backported to the 3.24 gtk serie...

** No longer affects: mutter (Ubuntu)

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

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

-- 
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:
  Fix Committed
Status in nautilus package in Ubuntu:
  Invalid

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 1846188] Re: Tooltips in Nautilus 3.34's burger menu are out of place (in Wayland sessions only)

[Sebastien Bacher]

It looks similar to https://gitlab.gnome.org/GNOME/gtk/issues/1427 which
was flagged as a GTK bug and was supposed to be fixed...

** Bug watch added: gitlab.gnome.org/GNOME/gtk/issues #1427
   https://gitlab.gnome.org/GNOME/gtk/issues/1427

-- 
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:
  Fix Committed
Status in nautilus package in Ubuntu:
  Invalid

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 630359] Re: DejaVu Sans kerning regression with Freetype 2.4

[Hugh McMaster]

Closing. Fixed.

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

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

Title:
  DejaVu Sans kerning regression with Freetype 2.4

Status in freetype package in Ubuntu:
  Fix Released

Bug description:
  With libfreetype 2.3.11-1ubuntu2.2, DejaVu Sans looks great. With
  libfreetype 2.4.2-1 installed (and everything else kept exactly the
  same), the kerning looks really ugly. To me, it's most noticeable
  before lowercase "u". I will attach before and after screenshots.

  I know the focus is on the Ubuntu Font Family for this release (which
  I'm dying to try), but we should make sure DejaVu continues to look
  good as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: libfreetype6 2.4.2-1
  ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
  Uname: Linux 2.6.35-19-generic i686
  NonfreeKernelModules: wl
  Architecture: i386
  Date: Sat Sep  4 10:49:26 2010
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: freetype

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/630359/+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 669571] Re: Ubuntu font's hooked lower-case "l" is autohinted with uneven left/right space

[Hugh McMaster]

Closing. Fixed.

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

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

Title:
  Ubuntu font's hooked lower-case "l" is autohinted with uneven
  left/right space

Status in freetype package in Ubuntu:
  Fix Released

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

  What you see: In the sequences "pla", "ple", "plo", there is equal space left 
and right of the stem of the "l".
  

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

  What you see: The spacing on either side of the stem is sometimes different.
  

  What you should see: There is equal space left and right of the stem
  of the "l".

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

[Sebastien Bacher]

Daniel, could you maybe reopen/provide the info upstream if you are able
to trigger the issue?

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

[Sebastien Bacher]

(also gnome-control-center shouldn't be involved when
disconnecting/reconnecting, it has no service or anything listening to
even, it is just an UI to apply changes, the issue is more likely on the
pulseaudio side (unless g-c-c does the wrong thing when apply configs)

** Changed in: gnome-control-center (Ubuntu)
   Importance: Undecided => Low

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

-- 
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 418325] Re: Freetype stroker overly sensitive and mishandles fonts that don't follow the TrueType spec.

[Hugh McMaster]

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

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

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

Title:
  Freetype stroker overly sensitive and mishandles fonts that don't
  follow the TrueType spec.

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

Bug description:
  From http://code.google.com/p/libass/issues/detail?id=2

  "This is a known problem with FreeType's stroker, which is used for
  creating the bordered glyphs. It probably won't be easy to fix, but
  I'm working on it.

  The FreeType stroker is very sensitive to broken/defective fonts (e.g.
  fonts that do not follow the TrueType specification) and has a few
  design shortcomings (breaks when stroking leads to self-
  intersection)."

  Attached is an example of this bug in action. Pay close attention to
  the border gaps on the glyphs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/freetype/+bug/418325/+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 1840817] Re: System won't suspend when closing the lid of my laptop, just shuts down

[Kai-Heng Feng]

# echo 'file button.c +p' > /sys/kernel/debug/dynamic_debug/control

Close lid to let it shutdown, and attach `journalctl -k -b -1`.

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

Title:
  System won't suspend when closing the lid of my laptop, just shuts
  down

Status in systemd package in Ubuntu:
  New

Bug description:
  1) Using Ubuntu MATE 18.04.3 LTS
  2)systemd: version 237-3ubuntu10.25 /pm-utils: version 1.4.1-17
  3) I expected the laptop to suspend when i closed the lid
  4)It just shut down even though in the logs it reports that it suspended

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.25
  ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18
  Uname: Linux 5.0.0-25-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Aug 20 17:36:30 2019
  InstallationDate: Installed on 2019-08-15 (5 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b52b Chicony Electronics Co., Ltd 
   Bus 001 Device 004: ID 13d3:3423 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X541SC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic 
root=UUID=70ef06f6-6585-41c0-9a60-fd2b8b761810 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [MASKED] /etc/systemd/system/samba-ad-dc.service → 
/lib/systemd/system/samba-ad-dc.service
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X541SC.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X541SC
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX541SC.301:bd09/14/2016:svnASUSTeKCOMPUTERINC.:pnX541SC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541SC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X541SC
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1840817/+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 257135] Re: notify-send(1) can't replace an existing notification

[Colin Hemming]

I would find this incredibly helpful, but would also love to be able to
also dismiss something by ID. That way a "Processing..." notification
could be displayed indefinitely, then removed when the process behind
completed.

As someone seems to have already patched this it would be fantastic to
see it deployed in the official repositories, rather than having to muck
about compiling my own version!

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

Title:
  notify-send(1) can't replace an existing notification

Status in libnotify package in Ubuntu:
  Confirmed
Status in libnotify package in Debian:
  New

Bug description:
  Binary package hint: libnotify-bin

  Ubuntu 8.04, libnotify-bin 0.4.4-3build1.

  notify-send(1) is very useful but it doesn't tell me the notification
  ID that's been created, nor does it let me specify that to replace an
  earlier notification.  See http://www.galago-
  project.org/specs/notification/0.9/x408.html#command-notify, in
  particular the replaces_id parameter and the return value.

  I'd like to be able to use it something like

  id=$(notify-send --show-id foo)
  sleep 60
  notify-send --replace $id bar

  This would be great for long-running shell scripts that are monitoring
  something.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/257135/+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 1801383] Re: the WifiSyslog apport hook (used in firefox/tb) includes SSID informations

[Launchpad Bug Tracker]

This bug was fixed in the package thunderbird - 1:68.1.1+build1-0ubuntu1

---
thunderbird (1:68.1.1+build1-0ubuntu1) eoan; urgency=medium

  * New upstream stable release (68.1.1build1)

  * Build thunderbird against the system-wide version of sqlite3 (LP: #1845929)
- update debian/config/mozconfig.in
- update debian/control{,.in}

 -- Olivier Tilloy   Tue, 01 Oct 2019
14:47:00 +0200

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

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

Title:
  the WifiSyslog apport hook (used in firefox/tb) includes SSID
  informations

Status in apport package in Ubuntu:
  Won't Fix
Status in firefox package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in thunderbird package in Ubuntu:
  Fix Released

Bug description:
  When I apport-bug certain packages such as firefox for example, it
  uploads the WifiSyslog.txt file.

  The WifiSyslog may contain a list of all system connections enumerated
  in /etc/NetworkManager/system-connections, i.e. all SSIDs the user has
  ever connected to that are found in the system-connections. This is a
  serious privacy risk and completely unnecessary information for most
  bug reports.

  Should either remove WifiSyslog as a requirement for packages that
  don't need it (should I report this to
  https://bugs.launchpad.net/ubuntu/+source/firefox/ ?), or redact
  information that may contain usernames and SSIDs from the log file.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.4
  ProcVersionSignature: User Name 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CrashReports: 640:1000:117:62475:2018-11-01 19:17:29.982295751 
-0400:2018-11-01 19:17:30.982295751 
-0400:/var/crash/_usr_bin_gnome-screenshot.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  2 11:24:20 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-09-12 (50 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to bionic on 2018-09-28 (34 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1801383/+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 wonder if the delay is equal to the number of buffers' whose damage
mutter is tracking... What this means is that it could take 3 or 4
frames to update everything. I've seen reports of such issues in mutter
3.34, like bug 1845623.

If you have a separate window animating in the corner of the screen
(glxgears or a video) then does that work around the problem? How about
if you have a maximized window constantly updating underneath?

** Changed in: mutter (Ubuntu)
   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/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 1556439] Proposed package upload rejected

[Chris Halse Rogers]

An upload of pulseaudio to bionic-proposed has been rejected from the
upload queue for the following reason: "The changes file claims to fix
#1663528, but this won't. We don't need to preserve the changelog of
-proposed packages, so drop it from the 1ubuntu7.3 entry".

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

Title:
  pulseaudio crashed with SIGABRT in pa_sink_input_assert_ref() from
  pa_sink_input_finish_move() from pa_sink_move_all_finish() from
  card_set_profile() from pa_card_set_profile

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Committed
Status in pulseaudio source package in Cosmic:
  Fix Released
Status in pulseaudio source package in Disco:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  https://errors.ubuntu.com/problem/a83a007593c81501c4fbb4e9ac0f47e0b3880d17

  This is one of the top pulseaudio crashes in Ubuntu 18.04 according to:
  
https://errors.ubuntu.com/?release=Ubuntu%2018.04&package=pulseaudio&period=year

  [Test Case]

  No manual test case known. Just watch errors.ubuntu.com to check for
  recurrences.

  [Regression Potential]

  Low. The fix is already in PulseAudio 12 so has been used in Ubuntu
  18.10 and later for a year so far.

  [Original Report]

  Changing between Logitech G933 digital and analog and Logitech G930
  digital and analog

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset wl nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar 12 17:20:34 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2016-02-22 (19 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=sv_SE.UTF-8
   LANGUAGE=sv
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_sink_input_finish_move () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so
   pa_sink_move_all_finish () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so
   ?? () from /usr/lib/pulse-8.0/modules/module-alsa-card.so
   pa_card_set_profile () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so
   ?? () from /usr/lib/pulse-8.0/modules/libprotocol-native.so
  Title: pulseaudio crashed with SIGABRT in pa_sink_input_finish_move()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 09/30/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2001
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X99-DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2001:bd09/30/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-DELUXE:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1556439/+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 1834138] Proposed package upload rejected

[Chris Halse Rogers]

An upload of pulseaudio to bionic-proposed has been rejected from the
upload queue for the following reason: "The changes file claims to fix
#1663528, but this won't. We don't need to preserve the changelog of
-proposed packages, so drop it from the 1ubuntu7.3 entry".

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

Title:
  PA: Don't restore the streams to sinks/sources with only unavailable
  ports

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Incomplete
Status in pulseaudio source package in Disco:
  Fix Committed
Status in pulseaudio source package in Eoan:
  Fix Released

Bug description:
  SRU Document:

  [Impact]

  The Lenovo P520 machine has dual analogue codecs, so there are two
  sinks and two sources in the PA, one has the front headphone and front
  microphone, the other has the rear lineout, linein and rear
  microphone, and the rear microphone always shows up in the gnome-
  sound-setting, When we plug a microphone to front audio jack, there
  are two input devices: rear mic and front mic in the gnome-sound-
  setting, and suppose users select the the front mic to record sound
  via audio app like arecord, the front mic will be bond the arecord,
  after the front mic is unplugged, there is only one rear mic left in
  the gnome-sound-setting, but the binding will not be changed, the
  arecrod still bind to front mic, under this situation if users record
  sound via arecord, they will find they can't record any sound from any
  other input devices even they are listed in the gnome-sound-setting.
  This problem also happens to output devices too.

  [Test Case]

  After applying this patch, I did the same test: unplug the front mic,
  then use the arecord to record sound, the app can record sound from
  rear mic now. After I plug the front mic back, the arecord still
  record from front mic. Also did the similar test for output devices,
  it worked as expected too.

  [Regression Potential]

  Low, Just make a simple check when creating new streams
  (sink_input/source_output), If the restored device (sink/source) has
  ports and all ports are unavialble, it will not restore the binding,
  otherwise it will work as before.

  For the Bionic, This SRU also includes the fix of LP: #1556439, this
  fix is safe and is very low possible to introduce any regression too,
  because it just adds a sink-input/source-output state checking, if the
  sink-input/source-output is unlinking or unlinked, it is useless to
  move it to a new sink/source, furthermore it will trigger an assertion
  that make the pulseaudio crash, adding this check can fix this problem
  (LP: #1556439).

  [Other Info]

  No more info here

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1834138/+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 1663528] Proposed package upload rejected

[Chris Halse Rogers]

An upload of pulseaudio to bionic-proposed has been rejected from the
upload queue for the following reason: "The changes file claims to fix
#1663528, but this won't. We don't need to preserve the changelog of
-proposed packages, so drop it from the 1ubuntu7.3 entry".

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

Title:
  pulseaudio assert failure: pulseaudio: mixer.c:929:
  snd_mixer_elem_get_callback_private: Assertion `mixer' failed.

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Won't Fix
Status in pulseaudio source package in Cosmic:
  Fix Released
Status in pulseaudio source package in Disco:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  https://errors.ubuntu.com/problem/a8bcc8185d5b1da4614bcdcf99daf57011bf9250
  https://errors.ubuntu.com/problem/5e10f78db7c4d1d3ab1cd6cd5d0b7cda2299eaad
  https://errors.ubuntu.com/problem/0f07e226e7db1d0fb140736a956760871e695669

  This is one of the top pulseaudio crashes in Ubuntu 18.04 according to:
  
https://errors.ubuntu.com/?release=Ubuntu%2018.04&package=pulseaudio&period=year

  [Test Case]

  No manual test case known. Just watch errors.ubuntu.com to check for
  recurrences.

  [Regression Potential]

  Low. The fix is already in PulseAudio 12 so has been used in Ubuntu
  18.10 and later for a year so far.

  [Other Info]

  SRU sponsorship tracked in bug 1556439.

  [Original Report]

  Sidenote: Imediatly got that crash after the apt-xapian-index one (
  lp:1663524 ); does not know if it can exist a possible relationship
  between them.

  Got an other crash, and that time 'sound' is fully lost (pulseaudio
  not reloaded). Wonder if lp:1662860 can be concerned.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6
  Uname: Linux 4.9.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AssertionMessage: pulseaudio: mixer.c:929: 
snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem4084 F pulseaudio
   /dev/snd/controlC0:  oem4084 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Feb 10 09:55:45 2017
  ExecutablePath: /usr/bin/pulseaudio
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   __assert_fail_base (fmt=, 
assertion=assertion@entry=0x7f92818e7188 "mixer", 
file=file@entry=0x7f92818e7419 "mixer.c", line=line@entry=929, 
function=function@entry=0x7f92818e76a0 "snd_mixer_elem_get_callback_private") 
at assert.c:92
   __GI___assert_fail (assertion=0x7f92818e7188 "mixer", file=0x7f92818e7419 
"mixer.c", line=929, function=0x7f92818e76a0 
"snd_mixer_elem_get_callback_private") at assert.c:101
   snd_mixer_elem_get_callback_private () from 
/usr/lib/x86_64-linux-gnu/libasound.so.2
   ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so
   ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so
  Title: pulseaudio assert failure: pulseaudio: mixer.c:929: 
snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom colord dip lpadmin nvidia-persistenced plugdev 
sambashare sudo users
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

Ubuntu on Wayland has same behavior, but worst.

Video attached shows open a new tab with CTRL+T and the new tab not being 
rendered until I create a new. 
Then I remove both, I create a new one, not rendered, and got rendered only 
when the mouse is moved. 
https://photos.app.goo.gl/6Nc6oABXs1xX1ks26

This worked fine in 19.04 and works fine now with external display.

I'll send another video showing how windows animation for align right/left do 
not work, windows just step from one state to the next with no animation. 
Minimize/maximize are perfect.

-- 
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 1845319] Re: writing 'add' to /sys/devices/vio/uevent fails with ENODEV

[Dan Streetman]

As this is a trivial issue that nobody will care about, as long as udevadm 
ignores the error code, I'm marking wontfix for the kernel.  I'll still try to 
get it fixed in the upstream kernel, but I think there's no need to SRU it, and 
systemd is going to fix udevadm to ignore ENODEV during triggering.
https://github.com/systemd/systemd/pull/13656

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

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

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

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

** No longer affects: linux (Ubuntu Bionic)

** No longer affects: linux (Ubuntu Disco)

** No longer affects: systemd (Ubuntu Bionic)

** No longer affects: systemd (Ubuntu Disco)

** Changed in: systemd (Ubuntu Eoan)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

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

** Also affects: systemd via
   https://github.com/systemd/systemd/issues/13652
   Importance: Unknown
   Status: Unknown

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

Title:
  writing 'add' to /sys/devices/vio/uevent fails with ENODEV

Status in systemd:
  Unknown
Status in linux package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  In Progress
Status in linux source package in Eoan:
  Won't Fix
Status in systemd source package in Eoan:
  In Progress

Bug description:
  [impact]

  The systemd-udev-trigger service calls 'udevadm trigger --type=devices
  --action=add', which writes 'add' to all /sys/devices/ uevent nodes,
  to re-generate their uevents sent to udev.  Until systemd commit
  97afc0351a96e0daa83964df33937967c75c644f, any errors during this
  process were simply logged to debug and ignored, but now udevadm will
  log errors and return failure.

  On ppc64el, the /sys/devices/vio device returns ENODEV when writing
  'add' to its uevent, which causes the udevadm command to return
  failure, which causes the systemd-udev-trigger system service to fail.

  The kernel vio driver should be fixed to not return ENODEV.

  [test case]

  On a ppc64el system, with any systemd containing commit
  97afc0351a96e0daa83964df33937967c75c644f, check the status of the
  systemd-udev-trigger service, to see that it's failed.

  Alternately, again on a ppc64el system, run as root:

  # echo add > /sys/devices/vio/uevent
  -bash: echo: write error: No such device

  [regression potential]

  the potential should be low, as this appears to have always behaved
  this way, at least for a while now.

  [other info]

  the systemd commit that changes udevadm to start failing for this
  error isn't included in any Ubuntu release yet, this is found from
  systemd upstream testing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1845319/+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 1845319] Re: writing 'add' to /sys/devices/vio/uevent fails with ENODEV

[Dan Streetman]

Just keeping this open in systemd for my tracking until it's added
upstream

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

Title:
  writing 'add' to /sys/devices/vio/uevent fails with ENODEV

Status in systemd:
  Unknown
Status in linux package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  In Progress
Status in linux source package in Eoan:
  Won't Fix
Status in systemd source package in Eoan:
  In Progress

Bug description:
  [impact]

  The systemd-udev-trigger service calls 'udevadm trigger --type=devices
  --action=add', which writes 'add' to all /sys/devices/ uevent nodes,
  to re-generate their uevents sent to udev.  Until systemd commit
  97afc0351a96e0daa83964df33937967c75c644f, any errors during this
  process were simply logged to debug and ignored, but now udevadm will
  log errors and return failure.

  On ppc64el, the /sys/devices/vio device returns ENODEV when writing
  'add' to its uevent, which causes the udevadm command to return
  failure, which causes the systemd-udev-trigger system service to fail.

  The kernel vio driver should be fixed to not return ENODEV.

  [test case]

  On a ppc64el system, with any systemd containing commit
  97afc0351a96e0daa83964df33937967c75c644f, check the status of the
  systemd-udev-trigger service, to see that it's failed.

  Alternately, again on a ppc64el system, run as root:

  # echo add > /sys/devices/vio/uevent
  -bash: echo: write error: No such device

  [regression potential]

  the potential should be low, as this appears to have always behaved
  this way, at least for a while now.

  [other info]

  the systemd commit that changes udevadm to start failing for this
  error isn't included in any Ubuntu release yet, this is found from
  systemd upstream testing.

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

[Chris Halse Rogers]

Hello Timo, or anyone else affected,

Accepted mesa into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/19.0.8-0ubuntu0~18.04.3 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: mesa (Ubuntu Bionic)
   Status: New => Fix Committed

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

-- 
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:
  Fix Committed

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 1833193] Re: systemd-networkd fails to apply static IPv4 when the static IP is the same as previously configured by DHCP

[Dan Streetman]

> I just tested it on Eoan, using systemd 242-6, and the valid__lft and
preferred_lft did indeed change to 'forever'.

well that's interesting...I tested with the latest upstream systemd code
and i *was* able to reproduce the problem...maybe something reverted the
fix since 242.  Unless, of course, I messed up my test :-)  I'll
backport the fix for that and see if it fixes bionic, then retest the
latest upstream to make sure it hasn't reverted.

> 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..

yes, I agree, and it is an entertaining discussion on what systemd
should prevent users from doing ;)

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