[Touch-packages] [Bug 1823125] Re: tomcat9 fails to install in 18.04

[Balint Reczey]

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

** Also affects: tomcat9 (Ubuntu Disco)
   Importance: High
   Status: Fix Released

** Also affects: tomcat9 (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

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

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

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

** Changed in: systemd (Ubuntu Disco)
   Status: Incomplete => Fix Released

** Changed in: systemd (Ubuntu Cosmic)
   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/1823125

Title:
  tomcat9 fails to install in 18.04

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

Bug description:
  # apt install tomcat9
  ...
  Setting up tomcat9 (9.0.16-3~18.04) ...
  [/usr/lib/sysusers.d/tomcat9.conf:7] Trailing garbage.

  Creating config file /etc/tomcat9/tomcat-users.xml with new version
  chown: invalid group: ‘root:tomcat’
  dpkg: error processing package tomcat9 (--configure):
   installed tomcat9 package post-installation script subprocess returned error 
exit status 1
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  Processing triggers for ureadahead (0.100.0-20) ...
  Processing triggers for systemd (237-3ubuntu10.15) ...
  Processing triggers for ca-certificates (20180409) ...
  Updating certificates in /etc/ssl/certs...
  0 added, 0 removed; done.
  Running hooks in /etc/ca-certificates/update.d...

  done.
  done.
  Processing triggers for rsyslog (8.32.0-1ubuntu4) ...
  Errors were encountered while processing:
   tomcat9
  E: Sub-process /usr/bin/dpkg returned an error code (1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823125/+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 1823134] [NEW] Cannot change display brightness

[Daniel Martinek]

Public bug reported:

ubuntu 18.10
xorg version

xorg:
  Instalovaná verze: 1:7.7+19ubuntu8
  Kandidát:  1:7.7+19ubuntu8
  Tabulka verzí:
 *** 1:7.7+19ubuntu8 500
500 http://cz.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
100 /var/lib/dpkg/status

display brightness slider does nothing. Should change brightness

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
Uname: Linux 4.18.0-17-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
CompositorRunning: None
Date: Thu Apr  4 09:37:32 2019
DistUpgraded: Fresh install
DistroCodename: cosmic
DistroVariant: ubuntu
DkmsStatus: als, master, 4.18.0-17-generic, x86_64: installed (WARNING! Diff 
between built and installed module!)
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company GP107GLM [Quadro P1000 Mobile] [103c:842f]
MachineType: HP HP ZBook 17 G5
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=cs_CZ.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic 
root=UUID=d3c1a21c-bf79-43cc-9eb9-83748dbaf57d ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/15/2019
dmi.bios.vendor: HP
dmi.bios.version: Q70 Ver. 01.06.03
dmi.board.name: 842D
dmi.board.vendor: HP
dmi.board.version: KBC Version 15.35.00
dmi.chassis.asset.tag: 5CD8501DGX
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrQ70Ver.01.06.03:bd02/15/2019:svnHP:pnHPZBook17G5:pvr:rvnHP:rn842D:rvrKBCVersion15.35.00:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN HP ZBook 17
dmi.product.name: HP ZBook 17 G5
dmi.product.sku: 4QH25EA#BCM
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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


** Tags: amd64 apport-bug cosmic ubuntu

** Attachment added: "otput from lshw command"
   https://bugs.launchpad.net/bugs/1823134/+attachment/5252678/+files/lshw

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

Title:
  Cannot change display brightness

Status in xorg package in Ubuntu:
  New

Bug description:
  ubuntu 18.10
  xorg version

  xorg:
Instalovaná verze: 1:7.7+19ubuntu8
Kandidát:  1:7.7+19ubuntu8
Tabulka verzí:
   *** 1:7.7+19ubuntu8 500
  500 http://cz.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status

  display brightness slider does nothing. Should change brightness

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CompositorRunning: None
  Date: Thu Apr  4 09:37:32 2019
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus: als, master, 4.18.0-17-generic, x86_64: installed (WARNING! Diff 
between built and installed module!)
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company GP107GLM [Quadro P1000 Mobile] 
[103c:842f]
  MachineType: HP HP ZBook 17 G5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic 
root=UUID=d3c1a21c-bf79-43cc-9eb9-83748dbaf57d ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q70 Ver. 01.06.03
  dmi.board.name: 842D
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 15.35.00
  dmi.chassis.asset.tag: 5CD8501DGX
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ70Ver.01.06.03:bd02/15/2019:svnHP:pnHPZBook17G5:pvr:rvnHP:rn842D:rvrKBCVersion15.35.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook 17
  dmi.product.name: HP ZBook 17 G5
  dmi.product.sku: 

[Touch-packages] [Bug 1821863] Re: Need to add Intel CML related pci-id's

[Launchpad Bug Tracker]

This bug was fixed in the package xorg-server - 2:1.20.4-1ubuntu3

---
xorg-server (2:1.20.4-1ubuntu3) disco; urgency=medium

  * sync-i965-pciids.diff: Sync with mesa, add support for CML. (LP:
#1821863)
  * dix-ensure-work-queues-are-cleared-on-reset.diff: Fix a race
condition that might crash the server.
  * reset-transforms-in-closescreen.diff: Fix a crash when resuming a
scale transformation after closing the screen. (LP: #1820850)

 -- Timo Aaltonen   Wed, 03 Apr 2019 12:03:57 +0300

** Changed in: xorg-server (Ubuntu Disco)
   Status: New => Fix Released

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

Title:
  Need to add Intel CML related pci-id's

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Fix Committed
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in libdrm source package in Bionic:
  New
Status in linux source package in Bionic:
  Invalid
Status in linux-oem source package in Bionic:
  New
Status in mesa source package in Bionic:
  New
Status in xorg-server source package in Bionic:
  New
Status in libdrm source package in Disco:
  Fix Released
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem source package in Disco:
  Fix Committed
Status in mesa source package in Disco:
  Fix Released
Status in xorg-server source package in Disco:
  Fix Released

Bug description:
  [Impact]

  Please make it happen in the coming oem-kernel as there will be a
  flood of Intel Comet Lake (CML) platforms that would need it. Thank
  you.

  The same is needed for the rest of the stack.

  CML is basically another iteration of Skylake/Kabylake/Coffee Lake,
  and doesn't need other changes than pci-id's and support for the PCH
  (similar to Cannon point, already supported by the kernel).

  [Test case]

  Test that i915 graphics works on CML.

  [Regression potential]

  None really, these only add a bunch of new pci-id's across the stack.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1821863/+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 1823150] [NEW] Bluetooth cannot be turned on (Bluetooth: hci0: Reading Intel version information failed (-110))

[Emiliano]

Public bug reported:

I cannot turn on Bluetooth in the settings, and `hcitool dev` doesn't
show devices. Bluetooth used to work before upgrading from 18.04 to
18.10.

lsb_release -rd:
Description:Ubuntu 18.10
Release:18.10

apt-cache policy bluez
bluez:
  Installed: 5.50-0ubuntu1
  Candidate: 5.50-0ubuntu1
  Version table:
 *** 5.50-0ubuntu1 500
500 http://nl.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: bluez 5.50-0ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
Uname: Linux 4.18.0-17-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr  4 12:08:46 2019
InstallationDate: Installed on 2018-10-26 (159 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
InterestingModules: bnep btusb bluetooth
MachineType: HP HP EliteBook 820 G3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic 
root=UUID=c4bb9536-586b-43ea-a9cf-379bad764d8a ro quiet splash
SourcePackage: bluez
UpgradeStatus: Upgraded to cosmic on 2019-03-15 (19 days ago)
dmi.bios.date: 01/30/2018
dmi.bios.vendor: HP
dmi.bios.version: N75 Ver. 01.24
dmi.board.name: 807C
dmi.board.vendor: HP
dmi.board.version: KBC Version 85.77
dmi.chassis.asset.tag: 5CG73148FW
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.24:bd01/30/2018:svnHP:pnHPEliteBook820G3:pvr:rvnHP:rn807C:rvrKBCVersion85.77:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN HP EliteBook
dmi.product.name: HP EliteBook 820 G3
dmi.product.sku: 2SF33EP#ABH
dmi.sys.vendor: HP
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
DOWN 
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:3 acl:0 sco:0 commands:1 errors:0

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


** Tags: amd64 apport-bug cosmic

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

Title:
  Bluetooth cannot be turned on (Bluetooth: hci0: Reading Intel version
  information failed (-110))

Status in bluez package in Ubuntu:
  New

Bug description:
  I cannot turn on Bluetooth in the settings, and `hcitool dev` doesn't
  show devices. Bluetooth used to work before upgrading from 18.04 to
  18.10.

  lsb_release -rd:
  Description:  Ubuntu 18.10
  Release:  18.10

  apt-cache policy bluez
  bluez:
Installed: 5.50-0ubuntu1
Candidate: 5.50-0ubuntu1
Version table:
   *** 5.50-0ubuntu1 500
  500 http://nl.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: bluez 5.50-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  4 12:08:46 2019
  InstallationDate: Installed on 2018-10-26 (159 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: bnep btusb bluetooth
  MachineType: HP HP EliteBook 820 G3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic 
root=UUID=c4bb9536-586b-43ea-a9cf-379bad764d8a ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: Upgraded to cosmic on 2019-03-15 (19 days ago)
  dmi.bios.date: 01/30/2018
  dmi.bios.vendor: HP
  dmi.bios.version: N75 Ver. 01.24
  dmi.board.name: 807C
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 85.77
  dmi.chassis.asset.tag: 5CG73148FW
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.24:bd01/30/2018:svnHP:pnHPEliteBook820G3:pvr:rvnHP:rn807C:rvrKBCVersion85.77:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 820 G3
  dmi.product.sku: 2SF33EP#ABH
  dmi.sys.vendor: HP
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
DOWN 
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:3 acl:0 sco:0 commands:1 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1823150/+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 1768379] Re: python3-minimal should predepend on versioned version of python3-minimal

[Mathew Hodson]

** No longer affects: ubuntu-release-upgrader (Ubuntu)

** No longer affects: ubuntu-release-upgrader (Ubuntu Artful)

** No longer affects: ubuntu-release-upgrader (Ubuntu Bionic)

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

Title:
  python3-minimal should predepend on versioned version of
  python3-minimal

Status in python3-defaults package in Ubuntu:
  Fix Released
Status in python3-defaults source package in Artful:
  Fix Released
Status in python3-defaults source package in Bionic:
  Fix Released
Status in python3-defaults package in Debian:
  Fix Released

Bug description:
  [Impact]
  Release upgrades from Ubuntu 16.04 LTS to either Ubuntu 17.10 or Ubuntu 18.04 
LTS can fail if python3-minimial is unpacked before python3.x-minimal so a 
system won't have a usable python3 symlink. Then upgrades will fail because 
py3clean, used in prerm scripts of python3 packages, will fail with "not found".

  [Test Case]
  1) on a Ubuntu 16.04 LTS system with python3-apt installed download debs for 
Ubuntu 17.10 or 18.04 LTS of python3-minimal and python3-apt
  2) dpkg --unpack python3-minimal...
  3) dpkg --unpack python3-apt...

  Observe the following Traceback:

  Preparing to unpack .../python3-apt_1.4.0_beta3build2_amd64.deb ...
  /var/lib/dpkg/info/python3-apt.prerm: 6: 
/var/lib/dpkg/info/python3-apt.prerm: py3clean: not found
  dpkg: warning: subprocess old pre-removal script returned error exit status 
127
  dpkg: trying script from the new package instead ...
  /var/lib/dpkg/tmp.ci/prerm: 6: /var/lib/dpkg/tmp.ci/prerm: py3clean: not found
  dpkg: error processing archive 
/home/jak/Downloads/python3-apt_1.4.0_beta3build2_amd64.deb (--unpack):
   subprocess new pre-removal script returned error exit status 127
  /var/lib/dpkg/info/python3-apt.postinst: 6: 
/var/lib/dpkg/info/python3-apt.postinst: py3compile: not found
  dpkg: error while cleaning up:
   subprocess installed post-installation script returned error exit status 127

  With the deb python3-minimal from -proposed you won't be able to
  unpack python3-minimal without first installing python3.6-minimal.
  While that may qualify as verification it'd still be good to test
  unpacking python3-apt. To do that you'll need to install
  python3.6-minimal from the target release by editing you
  /etc/apt/sources.list to the new release, running 'apt-get update',
  and then 'apt-get install python3.6-minimal'. After that's all done
  you can try steps 2 and 3 from the test case again and you should not
  receive a Traceback.

  [Regression Potential]
  Its possible this could cause or reveal different upgrade failures so some 
extensive (desktop, cloud, server) upgrade testing should be done.

  
  [A Portion of the Original Description (it was a huge blob of failure)]
  do-release-upgrade -d  on my 16.04 LTS unity laptop lead to an install 
failure:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1768379/+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 984390] Re: $PATH is taken from login.defs not /etc/environment

[Michael Vogt]

** Description changed:

+ TEST CASE:
+ 
  $PATH isn't sourced from /etc/environment, instead the version in
  /etc/login.defs is used.  (The example below comes from a precise install.)
  
  | james@panlong:~$ echo $PATH
  | /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
  | james@panlong:~$ sudo su - buildd
  | buildd@panlong:~$ echo $PATH
  | /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
  | buildd@panlong:~$ cat /etc/environment
  | 
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games"
  | buildd@panlong:~$ grep PATH /etc/login.defs
  | # Three items must be defined:  MAIL_DIR, ENV_SUPATH, and ENV_PATH.
  | # *REQUIRED*  The default PATH settings, for superuser and normal users.
  | ENV_SUPATH  
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  | ENV_PATH
PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
  | #CRACKLIB_DICTPATH
  | buildd@panlong:~$ sudo sed -i -e "s#^ENV_PATH.*#ENV_PATH
PATH=/wtf:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games#" 
/etc/login.defs
  | buildd@panlong:~$ logout
  | james@panlong:~$ sudo su - buildd
  | buildd@panlong:~$ echo $PATH
  | /wtf:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
  | buildd@panlong:~$
  
  REGRESSION POTENTIAL:
  - medium: it changes (incorrect) existing behaviour so https://xkcd.com/1172/ 
may apply

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

Title:
  $PATH is taken from login.defs not /etc/environment

Status in shadow package in Ubuntu:
  Fix Released
Status in shadow source package in Precise:
  Won't Fix
Status in shadow source package in Xenial:
  Fix Committed
Status in shadow source package in Bionic:
  Fix Committed

Bug description:
  TEST CASE:

  $PATH isn't sourced from /etc/environment, instead the version in
  /etc/login.defs is used.  (The example below comes from a precise install.)

  | james@panlong:~$ echo $PATH
  | /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
  | james@panlong:~$ sudo su - buildd
  | buildd@panlong:~$ echo $PATH
  | /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
  | buildd@panlong:~$ cat /etc/environment
  | 
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games"
  | buildd@panlong:~$ grep PATH /etc/login.defs
  | # Three items must be defined:  MAIL_DIR, ENV_SUPATH, and ENV_PATH.
  | # *REQUIRED*  The default PATH settings, for superuser and normal users.
  | ENV_SUPATH  
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  | ENV_PATH
PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
  | #CRACKLIB_DICTPATH
  | buildd@panlong:~$ sudo sed -i -e "s#^ENV_PATH.*#ENV_PATH
PATH=/wtf:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games#" 
/etc/login.defs
  | buildd@panlong:~$ logout
  | james@panlong:~$ sudo su - buildd
  | buildd@panlong:~$ echo $PATH
  | /wtf:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
  | buildd@panlong:~$

  REGRESSION POTENTIAL:
  - medium: it changes (incorrect) existing behaviour so https://xkcd.com/1172/ 
may apply

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/984390/+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 1822565] Re: Wireless network immediately disconnects after updating to 19.04

[arturo]

This seems to be fixed with latest update

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

Title:
  Wireless network immediately disconnects after updating to 19.04

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  When trying to connect through wifi it keeps disconnecting and trying
  to connect again. The output from dmesg shows repeatedly:

  [  237.763532] wlp3s0: RX AssocResp from 78:81:02:8f:b7:b4 (capab=0x411 
status=0 aid=3)
  [  237.770669] wlp3s0: associated
  [  237.949148] wlp3s0: deauthenticating from 78:81:02:8f:b7:b4 by local 
choice (Reason: 1=UNSPECIFIED)
  [  238.080024] wlp3s0: authenticate with 78:81:02:8f:b7:b6
  [  238.084439] wlp3s0: send auth to 78:81:02:8f:b7:b6 (try 1/3)
  [  238.089443] wlp3s0: authenticated
  [  238.092096] wlp3s0: associate with 78:81:02:8f:b7:b6 (try 1/3)
  [  238.093446] wlp3s0: RX AssocResp from 78:81:02:8f:b7:b6 (capab=0x11 
status=0 aid=1)
  [  238.095034] wlp3s0: associated
  [  238.120780] wlp3s0: deauthenticating from 78:81:02:8f:b7:b6 by local 
choice (Reason: 1=UNSPECIFIED)
  [  238.271261] wlp3s0: authenticate with 78:81:02:8f:b7:b4
  [  238.274585] wlp3s0: send auth to 78:81:02:8f:b7:b4 (try 1/3)
  [  238.280295] wlp3s0: authenticated
  [  238.284119] wlp3s0: associate with 78:81:02:8f:b7:b4 (try 1/3)
  [  238.288600] wlp3s0: RX AssocResp from 78:81:02:8f:b7:b4 (capab=0x411 
status=0 aid=3)
  [  238.290668] wlp3s0: associated
  [  238.472343] wlp3s0: deauthenticating from 78:81:02:8f:b7:b4 by local 
choice (Reason: 1=UNSPECIFIED)
  [  238.612923] wlp3s0: authenticate with 78:81:02:8f:b7:b6
  [  238.615663] wlp3s0: send auth to 78:81:02:8f:b7:b6 (try 1/3)
  [  238.617052] wlp3s0: authenticated
  [  238.620101] wlp3s0: associate with 78:81:02:8f:b7:b6 (try 1/3)
  [  238.621631] wlp3s0: RX AssocResp from 78:81:02:8f:b7:b6 (capab=0x11 
status=0 aid=1)
  [  238.623148] wlp3s0: associated
  [  238.649560] wlp3s0: deauthenticating from 78:81:02:8f:b7:b6 by local 
choice (Reason: 1=UNSPECIFIED)


  Looking for similar errors some posts suggest to disable the
  wpa_supplicant service as it might be clashing with NetworkManager
  starting it on it's own but disabling it doesn't seem to have any
  effect.

  This seems to happen only when connecting to a particular router, a
  vodafone EasyBox (which worked fine before updating to ubuntu 19.04)
  connecting to some other router seems to not have this problem

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: network-manager 1.15.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  1 11:30:05 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-12-10 (111 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IpRoute:
   default via 192.168.42.129 dev enp0s20u9 proto dhcp metric 100 
   169.254.0.0/16 dev enp0s20u9 scope link metric 1000 
   192.168.42.0/24 dev enp0s20u9 proto kernel scope link src 192.168.42.112 
metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to disco on 2019-03-31 (0 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.15.2   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1822565/+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 1099184] Re: Avahi reports IPv6/IPv4 and "dnssd" CUPS backend only tries IPv6, no IPv4 fallback

[Trent Lloyd]

This is a bug in CUPS, CUPS needs to remember the address family of the
advertised service (and preferably the interface ID). Avahi does know
this interface and does provide it in the API responses to CUPS, but
it's currently not using it.

For more detailed information please refer to here:
https://github.com/lathiat/avahi/issues/125

** Bug watch added: github.com/lathiat/avahi/issues #125
   https://github.com/lathiat/avahi/issues/125

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

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

Title:
  Avahi reports IPv6/IPv4 and "dnssd" CUPS backend only tries IPv6, no
  IPv4 fallback

Status in avahi package in Ubuntu:
  Invalid

Bug description:
  lsb_release -rd
  Description: Ubuntu 12.04.1 LTS
  Release: 12.04
  -
  avahi-daemon 0.6.30-5ubuntu2
  cups 1.5.3-0ubuntu6
  

  Avahi for default publishes services also in IPv6 as in 
/etc/avahi/avahi-daemon.conf there is
  use-ipv6=yes

  At the same time services are listening on IPv4 addresses only.

  Cups is able to discover published printers via dnssd protocol but its
  ipp backend prints only on the IPv6 resolved address which does not
  answer and it does not try the IPv4 address.

  
  Excerpt from "avahi-browse -a -t -r" to show the IPv6 and IPv4 addresses

  + wlan0 IPv6 Hewlett-Packard HP LaserJet 1100 @ hjemme Internet Printer local
  + wlan0 IPv4 Hewlett-Packard HP LaserJet 1100 @ hjemme Internet Printer local
  + wlan0 IPv6 MobilIgor5a [00:26:82:9d:b9:6d] Workstation local
  + wlan0 IPv6 hjemme [00:40:f4:ff:55:32] Workstation local

  []

  = wlan0 IPv6 Hewlett-Packard HP LaserJet 1100 @ hjemme Internet Printer local
 hostname = [hjemme.local]
 address = [fe80::240:f4ff:feff:5532]
 port = [631]
 txt = ["printer-type=0x900E" "printer-state=3" "Scan=F" "Sort=F" "Bind=F" 
"Punch=F" "Collate=F" "Copies=F" "Staple=F" "Duplex=F" "Color=T" "Fax=F" 
"Binary=F" "Transparent=F" "TLS=1.2" 
"UUID=1577ef95-eecb-3eae-6d02-aa29003eb546" "URF=DM3" 
"pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg,image/png,image/urf"
 "product=(HP LaserJet 1100xi Printer)" "priority=0" "note=hjemme" 
"adminurl=http://hjemme.local:631/printers/Hewlett-Packard-HP-LaserJet-1100; 
"ty=HP LaserJet 1100, hpcups 3.12.2" 
"rp=printers/Hewlett-Packard-HP-LaserJet-1100" "qtotal=1" "txtvers=1"]
  = wlan0 IPv6 hjemme Remote Disk Management local
 hostname = [hjemme.local]
 address = [fe80::240:f4ff:feff:5532]
 port = [22]
 txt = []
  = wlan0 IPv6 hjemme [00:40:f4:ff:55:32] Workstation local
 hostname = [hjemme.local]
 address = [fe80::240:f4ff:feff:5532]
 port = [9]
 txt = []
  = wlan0 IPv4 Hewlett-Packard HP LaserJet 1100 @ hjemme Internet Printer local
 hostname = [hjemme.local]
 address = [192.168.1.2]
 port = [631]
 txt = ["printer-type=0x900E" "printer-state=3" "Scan=F" "Sort=F" "Bind=F" 
"Punch=F" "Collate=F" "Copies=F" "Staple=F" "Duplex=F" "Color=T" "Fax=F" 
"Binary=F" "Transparent=F" "TLS=1.2" 
"UUID=1577ef95-eecb-3eae-6d02-aa29003eb546" "URF=DM3" 
"pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg,image/png,image/urf"
 "product=(HP LaserJet 1100xi Printer)" "priority=0" "note=hjemme" 
"adminurl=http://hjemme.local:631/printers/Hewlett-Packard-HP-LaserJet-1100; 
"ty=HP LaserJet 1100, hpcups 3.12.2" 
"rp=printers/Hewlett-Packard-HP-LaserJet-1100" "qtotal=1" "txtvers=1"]

  
  Excerpt from /var/log/cups/error_log to show that only IPv6 address is tried

  I [13/Jan/2013:18:02:55 +0100] [Job 61] Started backend 
/usr/lib/cups/backend/dnssd (PID 7179)
  D [13/Jan/2013:18:02:55 +0100] [Job 61] Resolving "Hewlett-Packard HP 
LaserJet 1100 @ hjemme._ipp._tcp.local"...
  D [13/Jan/2013:18:02:55 +0100] [Job 61] STATE: +connecting-to-device
  D [13/Jan/2013:18:02:55 +0100] [Job 61] Resolving "Hewlett-Packard HP 
LaserJet 1100 @ hjemme", regtype="_ipp._tcp", domain="local."...
  D [13/Jan/2013:18:02:55 +0100] [Job 61] PPD uses qualifier 'Gray.Plain.'
  D [13/Jan/2013:18:02:55 +0100] [Job 61] Calling 
FindDeviceById(LaserJet_1100xi_Printer)
  D [13/Jan/2013:18:02:55 +0100] [Job 61] Failed to send: 
org.freedesktop.ColorManager.Failed:device id 'LaserJet_1100xi_Printer' does 
not exists
  D [13/Jan/2013:18:02:55 +0100] [Job 61] Failed to get profile filename!
  I [13/Jan/2013:18:02:55 +0100] [Job 61] no profiles specified in PPD
  D [13/Jan/2013:18:02:55 +0100] [Job 61] Set job-printer-state-message to "no 
profiles specified in PPD", current level=INFO
  D [13/Jan/2013:18:02:55 +0100] [Job 61] Ghostscript command line: /usr/bin/gs 
-dQUIET -dPARANOIDSAFER -dNOPAUSE -dBATCH -dNOINTERPOLATE -sDEVICE=cups 
-sstdout=%stderr -sOutputFile=%stdout -sMediaType=Plain 

[Touch-packages] [Bug 1822184] Re: clear_console locks up video when X is running and you log out from a plain text console

[Launchpad Bug Tracker]

This bug was fixed in the package bash - 5.0-3ubuntu1

---
bash (5.0-3ubuntu1) disco; urgency=medium

  * Merge with Debian; remaining changes:
- skel.bashrc:
  - Run lesspipe.
  - Enable ls aliases.
  - Set options in ll alias to -alF.
  - Define an alert alias.
  - Enabled colored grep aliases.
- etc.bash.bashrc:
  - Add sudo hint.

bash (5.0-3) unstable; urgency=medium

  * Apply upstream patch 003.
  * Fix clear_console locking up video when X is running and logging out
from a plain text console. Closes: #810660. LP: #1822184.

 -- Matthias Klose   Thu, 04 Apr 2019 05:11:47 +0200

** Changed in: bash (Ubuntu)
   Status: Opinion => Fix Released

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

Title:
  clear_console locks up video when X is running and you log out from a
  plain text console

Status in X.Org X server:
  New
Status in bash package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Confirmed
Status in xorg package in Debian:
  New
Status in xorg-server package in Debian:
  Confirmed

Bug description:
  References:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810660
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866898

  
  If X is running and you switch to a plain text console (ie ctrl-alt-f3), log 
in as a regular user, and then log out, the display switches back to the 
graphical login screen and locks up.  The system is still functioning (can ssh 
in, etc) but the video output is frozen.

  The underlying cause is:
  https://gitlab.freedesktop.org/xorg/xserver/issues/492

  However, the problem can at least be worked around by making
  clear_console switch to tty 6 and back instead of switching to 1 and
  back.  This patch corrects the problem:

  
  --- bash-4.4.18.orig/debian/clear_console.c 2019-03-28 12:09:02.415907787 
-0400
  +++ bash-4.4.18/debian/clear_console.c  2019-03-28 12:08:11.984366858 -0400
  @@ -205,7 +205,7 @@
   #if defined(__linux__)
 num = vtstat.v_active;
   #endif
  -  tmp_num = (num == 1 ? 2 : 1);
  +  tmp_num = (num == 6 ? 5 : 6);
   
 /* switch vt to clear the scrollback buffer */
 if (ioctl(fd, VT_ACTIVATE, tmp_num))

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1822184/+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 1821863] Re: Need to add Intel CML related pci-id's

[Launchpad Bug Tracker]

This bug was fixed in the package mesa - 19.0.1-1ubuntu2

---
mesa (19.0.1-1ubuntu2) disco; urgency=medium

  * i965-comet-lake.diff: Add support for CML. (LP: #1821863)

 -- Timo Aaltonen   Wed, 03 Apr 2019 10:58:06 +0300

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

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

Title:
  Need to add Intel CML related pci-id's

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Fix Committed
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  New
Status in libdrm source package in Bionic:
  New
Status in linux source package in Bionic:
  Invalid
Status in linux-oem source package in Bionic:
  New
Status in mesa source package in Bionic:
  New
Status in xorg-server source package in Bionic:
  New
Status in libdrm source package in Disco:
  Fix Released
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem source package in Disco:
  Fix Committed
Status in mesa source package in Disco:
  Fix Released
Status in xorg-server source package in Disco:
  New

Bug description:
  [Impact]

  Please make it happen in the coming oem-kernel as there will be a
  flood of Intel Comet Lake (CML) platforms that would need it. Thank
  you.

  The same is needed for the rest of the stack.

  CML is basically another iteration of Skylake/Kabylake/Coffee Lake,
  and doesn't need other changes than pci-id's and support for the PCH
  (similar to Cannon point, already supported by the kernel).

  [Test case]

  Test that i915 graphics works on CML.

  [Regression potential]

  None really, these only add a bunch of new pci-id's across the stack.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1821863/+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 1823134] Re: Cannot change display brightness [HP ZBook 17 G5]

[Daniel van Vugt]

** Summary changed:

- Cannot change display brightness
+ Cannot change display brightness [HP ZBook 17 G5]

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

** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- Cannot change display brightness [HP ZBook 17 G5]
+ Cannot change display brightness [HP ZBook 17 G5 with Nvidia Quadro P1000 
Mobile]

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

Title:
  Cannot change display brightness [HP ZBook 17 G5 with Nvidia Quadro
  P1000 Mobile]

Status in gnome-shell package in Ubuntu:
  New
Status in upower package in Ubuntu:
  New

Bug description:
  ubuntu 18.10
  xorg version

  xorg:
Instalovaná verze: 1:7.7+19ubuntu8
Kandidát:  1:7.7+19ubuntu8
Tabulka verzí:
   *** 1:7.7+19ubuntu8 500
  500 http://cz.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status

  display brightness slider does nothing. Should change brightness

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CompositorRunning: None
  Date: Thu Apr  4 09:37:32 2019
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus: als, master, 4.18.0-17-generic, x86_64: installed (WARNING! Diff 
between built and installed module!)
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company GP107GLM [Quadro P1000 Mobile] 
[103c:842f]
  MachineType: HP HP ZBook 17 G5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic 
root=UUID=d3c1a21c-bf79-43cc-9eb9-83748dbaf57d ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q70 Ver. 01.06.03
  dmi.board.name: 842D
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 15.35.00
  dmi.chassis.asset.tag: 5CD8501DGX
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ70Ver.01.06.03:bd02/15/2019:svnHP:pnHPZBook17G5:pvr:rvnHP:rn842D:rvrKBCVersion15.35.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook 17
  dmi.product.name: HP ZBook 17 G5
  dmi.product.sku: 4QH25EA#BCM
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1823134/+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 1813587] Re: libunistring and libidn ftbfs on 18.04 LTS

[Launchpad Bug Tracker]

This bug was fixed in the package libunistring - 0.9.10-1ubuntu1.18.10.1

---
libunistring (0.9.10-1ubuntu1.18.10.1) cosmic; urgency=medium

  * Cherry-pick pthread fix from upstream and disco release.
(LP: #1813587)

 -- Gianfranco Costamagna   Wed, 27 Mar 2019
12:21:30 +0100

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

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

Title:
  libunistring and libidn ftbfs on 18.04 LTS

Status in libidn package in Ubuntu:
  Fix Released
Status in libunistring package in Ubuntu:
  Fix Released
Status in libidn source package in Bionic:
  Fix Committed
Status in libunistring source package in Bionic:
  Fix Released
Status in libidn source package in Cosmic:
  Fix Committed
Status in libunistring source package in Cosmic:
  Fix Released
Status in libunistring package in Debian:
  New

Bug description:
  Impact
  --
  libunistring doesn't build from source which means someone would need to fix 
that problem before fixing any bugs in the libunistring package for Ubuntu 
18.04 LTS.

  Test Case
  -
  Does libunistring build successfully?

  Regression Potential
  
  We are simply backporting the workaround we applied in Ubuntu 19.04.

  Original Bug Report
  ---
  according to
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html

  libunistring ftbfs.

  FAIL: test-thread_create
  

  glthread_create failed
  FAIL test-thread_create (exit status: 1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1813587/+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 1813587] Re: libunistring and libidn ftbfs on 18.04 LTS

[Launchpad Bug Tracker]

This bug was fixed in the package libunistring - 0.9.9-0ubuntu2

---
libunistring (0.9.9-0ubuntu2) bionic; urgency=medium

  * Cherry-pick pthread fix from upstream and disco release.
(LP: #1813587)

 -- Gianfranco Costamagna   Thu, 21 Mar 2019
10:30:01 +0100

** Changed in: libunistring (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 libidn in Ubuntu.
https://bugs.launchpad.net/bugs/1813587

Title:
  libunistring and libidn ftbfs on 18.04 LTS

Status in libidn package in Ubuntu:
  Fix Released
Status in libunistring package in Ubuntu:
  Fix Released
Status in libidn source package in Bionic:
  Fix Committed
Status in libunistring source package in Bionic:
  Fix Released
Status in libidn source package in Cosmic:
  Fix Committed
Status in libunistring source package in Cosmic:
  Fix Released
Status in libunistring package in Debian:
  New

Bug description:
  Impact
  --
  libunistring doesn't build from source which means someone would need to fix 
that problem before fixing any bugs in the libunistring package for Ubuntu 
18.04 LTS.

  Test Case
  -
  Does libunistring build successfully?

  Regression Potential
  
  We are simply backporting the workaround we applied in Ubuntu 19.04.

  Original Bug Report
  ---
  according to
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html

  libunistring ftbfs.

  FAIL: test-thread_create
  

  glthread_create failed
  FAIL test-thread_create (exit status: 1)

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

[Łukasz Zemczak]

The verification of the Stable Release Update for libunistring has
completed successfully and the package has now been 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 libidn in Ubuntu.
https://bugs.launchpad.net/bugs/1813587

Title:
  libunistring and libidn ftbfs on 18.04 LTS

Status in libidn package in Ubuntu:
  Fix Released
Status in libunistring package in Ubuntu:
  Fix Released
Status in libidn source package in Bionic:
  Fix Committed
Status in libunistring source package in Bionic:
  Fix Released
Status in libidn source package in Cosmic:
  Fix Committed
Status in libunistring source package in Cosmic:
  Fix Released
Status in libunistring package in Debian:
  New

Bug description:
  Impact
  --
  libunistring doesn't build from source which means someone would need to fix 
that problem before fixing any bugs in the libunistring package for Ubuntu 
18.04 LTS.

  Test Case
  -
  Does libunistring build successfully?

  Regression Potential
  
  We are simply backporting the workaround we applied in Ubuntu 19.04.

  Original Bug Report
  ---
  according to
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html

  libunistring ftbfs.

  FAIL: test-thread_create
  

  glthread_create failed
  FAIL test-thread_create (exit status: 1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1813587/+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 1823139] [NEW] package unattended-upgrades (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 1

[MUHAMMAD FAHEEM]

Public bug reported:

during startup i get this error.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: unattended-upgrades (not installed)
ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-47-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
AptOrdering:
 unattended-upgrades: Purge
 rsyslog: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Tue Apr  2 17:52:13 2019
ErrorMessage: subprocess installed post-removal script returned error exit 
status 1
InstallationDate: Installed on 2018-08-09 (238 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.5
 apt  1.2.31
SourcePackage: unattended-upgrades
Title: package unattended-upgrades (not installed) failed to install/upgrade: 
subprocess installed post-removal script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: unattended-upgrades (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 unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1823139

Title:
  package unattended-upgrades (not installed) failed to install/upgrade:
  subprocess installed post-removal script returned error exit status 1

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  during startup i get this error.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  AptOrdering:
   unattended-upgrades: Purge
   rsyslog: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Apr  2 17:52:13 2019
  ErrorMessage: subprocess installed post-removal script returned error exit 
status 1
  InstallationDate: Installed on 2018-08-09 (238 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.31
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades (not installed) failed to install/upgrade: 
subprocess installed post-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1823139/+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 1823139] Re: package unattended-upgrades (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package unattended-upgrades (not installed) failed to install/upgrade:
  subprocess installed post-removal script returned error exit status 1

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  during startup i get this error.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  AptOrdering:
   unattended-upgrades: Purge
   rsyslog: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Apr  2 17:52:13 2019
  ErrorMessage: subprocess installed post-removal script returned error exit 
status 1
  InstallationDate: Installed on 2018-08-09 (238 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.31
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades (not installed) failed to install/upgrade: 
subprocess installed post-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1823139/+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 1813587] Re: libunistring and libidn ftbfs on 18.04 LTS

[Gianfranco Costamagna]

its a build fix... 
anyway, its a library, so not that easy to test, but I picked up 
gnome-characters, one of its reverse-dependencies that uses a lot of unicode, 
and it still works

gnome-characters
Gtk-Message: 09:13:35.039: Failed to load module "canberra-gtk-module"
Gtk-Message: 09:13:35.039: Failed to load module "canberra-gtk-module"
Gjs-Message: 09:13:35.042: JS LOG: Characters Application started
Gjs-Message: 09:13:38.057: JS LOG: Characters Application exiting
dpkg -l |grep unistr
ii  libunistring2:amd640.9.10-1ubuntu1.18.10.1   amd64
Unicode string library for C

ii  libidn11:amd64 1.33-2.2ubuntu1.1 amd64
GNU Libidn library, implementation of IETF IDN specifications
ii  libidn2-0:amd642.0.5-1   amd64
Internationalized domain names (IDNA2008/TR46) library


to test libidn I installed and started successfully vlc.

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

Title:
  libunistring and libidn ftbfs on 18.04 LTS

Status in libidn package in Ubuntu:
  Fix Released
Status in libunistring package in Ubuntu:
  Fix Released
Status in libidn source package in Bionic:
  Fix Committed
Status in libunistring source package in Bionic:
  Fix Released
Status in libidn source package in Cosmic:
  Fix Committed
Status in libunistring source package in Cosmic:
  Fix Released
Status in libunistring package in Debian:
  New

Bug description:
  Impact
  --
  libunistring doesn't build from source which means someone would need to fix 
that problem before fixing any bugs in the libunistring package for Ubuntu 
18.04 LTS.

  Test Case
  -
  Does libunistring build successfully?

  Regression Potential
  
  We are simply backporting the workaround we applied in Ubuntu 19.04.

  Original Bug Report
  ---
  according to
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html

  libunistring ftbfs.

  FAIL: test-thread_create
  

  glthread_create failed
  FAIL test-thread_create (exit status: 1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1813587/+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 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)

[Bug Watch Updater]

Launchpad has imported 1 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=110187.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2019-03-19T06:49:42+00:00 Timo Aaltonen wrote:

This bug is filed to monitor the progress on getting this patchset
upstream:

https://patchwork.freedesktop.org/series/55415/

one use case for it is to be able to set up a 3x4k horizontal monitor
configuration for X.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1714178/comments/61


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

** Changed in: dri
   Importance: Unknown => Medium

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

Title:
  Triple 4K monitor display failed (modesetting driver limited to
  8192x8192)

Status in DRI:
  Confirmed
Status in X.Org X server:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Confirmed
Status in mesa source package in Bionic:
  Fix Released
Status in xorg-server source package in Bionic:
  Confirmed

Bug description:
  Title: Triple monitor display failed with Dell Dock (HiDPI)
  (modesetting)

  Summary: Triple monitor display failed with Dell Dock (HiDPI)
  (modesetting)

  Steps:
  1. a laptop with Built-in 4K LCD
  2. Cold boot system with Dell Dock connected
  3. Connect a 4K monitor to Dock
  4. Connect 2nd 4K monitor to Dock
  5. Go to [All Settings]=>[Displays] to have the following configuration.
  Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors)
  Mirror displays: disable

  Expected results: Triple monitor display should works without issues
  Actual results: Triple monitor display failed with Dell Dock

  Additional information:
  1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04
  2. Laptop: Dell Precision 5520
  3. Dell Business Thunderbolt Dock - TB16
  https://goo.gl/vFDjpi

  WORKAROUND (UBUNTU 18.04+):
  Log in to "Ubuntu on Wayland" instead of "Ubuntu".

  ---
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:07bf]
     Subsystem: Dell Device [1028:07bf]
  InstallationDate: Installed on 2017-08-29 (2 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Precision 5520
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed 
root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.11.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.3
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 

[Touch-packages] [Bug 1754628] Re: vaapi not working [libva error: dlopen of /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so failed: /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so: undefined

[Daniel van Vugt]

** Summary changed:

- vaapi not working
+ vaapi not working [libva error: dlopen of 
/usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so failed: 
/usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so: undefined symbol: 
amdgpu_cs_syncobj_import_sync_file]

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

Title:
  vaapi not working [libva error: dlopen of /usr/lib/x86_64-linux-
  gnu/dri/radeonsi_drv_video.so failed: /usr/lib/x86_64-linux-
  gnu/dri/radeonsi_drv_video.so: undefined symbol:
  amdgpu_cs_syncobj_import_sync_file]

Status in mesa package in Ubuntu:
  New

Bug description:
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=18.04
  DISTRIB_CODENAME=bionic
  DISTRIB_DESCRIPTION="Ubuntu Bionic Beaver (development branch)"

  04:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Ellesmere [Radeon RX 470/480] [1002:67df] (rev e7)
Subsystem: Sapphire Technology Limited Ellesmere [Radeon RX 
470/480/570/580] (Nitro+ Radeon RX 580 4GB) [1da2:e366]

  The graphics run by the amdgpu (not -pro) and is unable to address va-
  api acceleration.

  eric@athena:~$ vainfo
  libva info: VA-API version 1.1.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
  libva error: dlopen of /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so 
failed: /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so: undefined symbol: 
amdgpu_cs_syncobj_import_sync_file
  libva info: va_openDriver() returns -1
  vaInitialize failed with error code -1 (unknown libva error),exit

  While open GL software like the unigine heaven benchmark runs very
  well.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,gnomecompat,grid,imgpng,mousepoll,move,place,regex,resize,session,unitymtgrabhandles,wall,wobbly,animation,expo,ezoom,fade,scale,unityshell,workarounds]
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Mar  9 12:16:28 2018
  DistUpgraded: 2018-03-09 11:15:52,669 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: amdgpu, 17.50-511655, 4.13.0-36-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] 
[1002:67df] (rev e7) (prog-if 00 [VGA controller])
 Subsystem: Sapphire Technology Limited Ellesmere [Radeon RX 
470/480/570/580] (Nitro+ Radeon RX 580 4GB) [1da2:e366]
  InstallationDate: Installed on 2018-01-04 (63 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=9782f23b-461f-4cf0-b7d4-9b4e2739964c ro iommu=soft quiet splash 
vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-03-09 (0 days ago)
  dmi.bios.date: 10/07/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2g
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970A-UD3P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2g:bd10/07/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu Jan 11 18:02:23 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: amdgpu

To manage notifications about this bug go to:

[Touch-packages] [Bug 1822565] Re: Wireless network immediately disconnects after updating to 19.04

[Sebastien Bacher]

Great, thanks for the status update. Closing but feel free to reopen if
you get the issue again

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

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

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

Title:
  Wireless network immediately disconnects after updating to 19.04

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  When trying to connect through wifi it keeps disconnecting and trying
  to connect again. The output from dmesg shows repeatedly:

  [  237.763532] wlp3s0: RX AssocResp from 78:81:02:8f:b7:b4 (capab=0x411 
status=0 aid=3)
  [  237.770669] wlp3s0: associated
  [  237.949148] wlp3s0: deauthenticating from 78:81:02:8f:b7:b4 by local 
choice (Reason: 1=UNSPECIFIED)
  [  238.080024] wlp3s0: authenticate with 78:81:02:8f:b7:b6
  [  238.084439] wlp3s0: send auth to 78:81:02:8f:b7:b6 (try 1/3)
  [  238.089443] wlp3s0: authenticated
  [  238.092096] wlp3s0: associate with 78:81:02:8f:b7:b6 (try 1/3)
  [  238.093446] wlp3s0: RX AssocResp from 78:81:02:8f:b7:b6 (capab=0x11 
status=0 aid=1)
  [  238.095034] wlp3s0: associated
  [  238.120780] wlp3s0: deauthenticating from 78:81:02:8f:b7:b6 by local 
choice (Reason: 1=UNSPECIFIED)
  [  238.271261] wlp3s0: authenticate with 78:81:02:8f:b7:b4
  [  238.274585] wlp3s0: send auth to 78:81:02:8f:b7:b4 (try 1/3)
  [  238.280295] wlp3s0: authenticated
  [  238.284119] wlp3s0: associate with 78:81:02:8f:b7:b4 (try 1/3)
  [  238.288600] wlp3s0: RX AssocResp from 78:81:02:8f:b7:b4 (capab=0x411 
status=0 aid=3)
  [  238.290668] wlp3s0: associated
  [  238.472343] wlp3s0: deauthenticating from 78:81:02:8f:b7:b4 by local 
choice (Reason: 1=UNSPECIFIED)
  [  238.612923] wlp3s0: authenticate with 78:81:02:8f:b7:b6
  [  238.615663] wlp3s0: send auth to 78:81:02:8f:b7:b6 (try 1/3)
  [  238.617052] wlp3s0: authenticated
  [  238.620101] wlp3s0: associate with 78:81:02:8f:b7:b6 (try 1/3)
  [  238.621631] wlp3s0: RX AssocResp from 78:81:02:8f:b7:b6 (capab=0x11 
status=0 aid=1)
  [  238.623148] wlp3s0: associated
  [  238.649560] wlp3s0: deauthenticating from 78:81:02:8f:b7:b6 by local 
choice (Reason: 1=UNSPECIFIED)


  Looking for similar errors some posts suggest to disable the
  wpa_supplicant service as it might be clashing with NetworkManager
  starting it on it's own but disabling it doesn't seem to have any
  effect.

  This seems to happen only when connecting to a particular router, a
  vodafone EasyBox (which worked fine before updating to ubuntu 19.04)
  connecting to some other router seems to not have this problem

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: network-manager 1.15.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  1 11:30:05 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-12-10 (111 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IpRoute:
   default via 192.168.42.129 dev enp0s20u9 proto dhcp metric 100 
   169.254.0.0/16 dev enp0s20u9 scope link metric 1000 
   192.168.42.0/24 dev enp0s20u9 proto kernel scope link src 192.168.42.112 
metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to disco on 2019-03-31 (0 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.15.2   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1822565/+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 1806012] Re: set-cpufreq: 'powersave' governor configuration sanity on ubuntu server

[Trent Lloyd]

On the previously mentioned HP server today I was able to get closer to
reproducing the situation by testing with bionic (4.15.0-47-generic)
instead of xenial (4.4)

On bionic, unlike xenial, even with the BIOS set to "BIOS controlled
dynamic" mode, the intel_pstate driver is loaded instead of pcc-cpufreq

Found this kernel commit:
https://github.com/torvalds/linux/commit/bfa54a3a00e2f7ff051a50f3957e4fca3d73f6e7

Pull power management fix from Rafael Wysocki:
 "Fix a relatively old initialization issue in intel_pstate causing the
  pcc-cpufreq driver to be used instead of it on some HP Proliant
  systems.

  This turned into a functional regression during the 4.17 cycle,
  because pcc-cpufreq is a scalability disaster and that was amplified
  by the idle loop rework done at that time (Rafael Wysocki).

This suggests there has definitely been some related change in this area
that sound very much similar to this which is worth further research.

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

Title:
  set-cpufreq: 'powersave' governor configuration sanity on ubuntu
  server

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Xenial:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  In Progress
Status in systemd source package in Disco:
  In Progress

Bug description:
  Whilst debugging 'slow instance performance' on a Ubuntu Bionic based
  cloud, I observed that the default cpu governor configuration was set
  to 'powersave'; toggling this to 'performance' (while in not anyway a
  particularly green thing todo) resulted in the instance slowness
  disappearing and the cloud performance being as expected (based on a
  prior version of the deploy on Ubuntu Xenial).

  AFAICT Xenial does the same thing albeit in a slight different way,
  but we definitely did not see the same performance laggy-ness under a
  Xenial based cloud.

  Raising against systemd (as this package sets the governor to
  'powersave') - I feel that the switch to 'performance' although
  appropriate then obscures what might be a performance/behavioural
  difference in the underlying kernel when a machine is under load.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.9
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Fri Nov 30 10:05:46 2018
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R630
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic 
root=UUID=a361a524-47eb-46c3-8a04-e5eaa65188c9 ro hugepages=103117 iommu=pt 
intel_iommu=on
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.3.4
  dmi.board.name: 02C2CP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA03:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R630
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1806012/+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 1822984] Re: revert tls security level back to 1

[Launchpad Bug Tracker]

This bug was fixed in the package openssl - 1.1.1b-1ubuntu2

---
openssl (1.1.1b-1ubuntu2) disco; urgency=medium

  * debian/rules: Ship openssl.cnf in libssl1.1-udeb, as required to use
OpenSSL by other udebs, e.g. wget-udeb. LP: #1822898

  * Drop debian/patches/UBUNTU-lower-tls-security-level-for-compat.patch
to revert TLS_SECURITY_LEVEL back to 1. LP: #1822984

 -- Dimitri John Ledkov   Wed, 03 Apr 2019 11:50:23
+0100

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

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

Title:
  revert tls security level back to 1

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Cosmic:
  In Progress
Status in openssl source package in Disco:
  Fix Released

Bug description:
  [Impact]
  * increase minimum default tls security level from 0 to 1, as is the default 
upstream

  [Test Case]

  * generate 80bits TLS certificate and attempt to use it

  * with prior openssl it should work, but with this update it should
  fail

  [Regression Potential]

  * This increases the minimum required certificate/keys sizes and
  algorithms, back to what Bionic GA openssl 1.1.0 shipped as. It also
  now will match upstream default. It is still lower than Debian's
  default that raises it to 2 by default.

  * Cosmic GA shipped with TLS_SECURITY_LEVEL 0, meaning pretty much any
  weak keys were accepted. With this change keys lower than 112 will be
  rejected, which are considered to be too weak to be useful by most CAs
  out there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1822984/+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 1822898] Re: wget https://geoip.ubuntu.com/lookup fails in mini.iso d-i

[Launchpad Bug Tracker]

This bug was fixed in the package openssl - 1.1.1b-1ubuntu2

---
openssl (1.1.1b-1ubuntu2) disco; urgency=medium

  * debian/rules: Ship openssl.cnf in libssl1.1-udeb, as required to use
OpenSSL by other udebs, e.g. wget-udeb. LP: #1822898

  * Drop debian/patches/UBUNTU-lower-tls-security-level-for-compat.patch
to revert TLS_SECURITY_LEVEL back to 1. LP: #1822984

 -- Dimitri John Ledkov   Wed, 03 Apr 2019 11:50:23
+0100

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

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

Title:
  wget https://geoip.ubuntu.com/lookup fails in mini.iso d-i

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Cosmic:
  In Progress
Status in openssl source package in Disco:
  Fix Released
Status in openssl package in Debian:
  New

Bug description:
  [Impact]
   * fetch-url cannot use https protocol (no https preseeds)

  [Test case]
   * in d-i, mini.iso, tty try
 wget https://geoip.ubuntu.com/lookup

   it should succeed.

  [Solution]
  The required openssl.cnf configuration file is missing, needs to simply 
exists, even if it is empty.

  [Regression Potential]
  well, if one cannot download over https / init ssl library in d-i, it's hard 
to get openssl busted more than that. No code changes on the .deb side of things

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1822898/+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 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)

[Timo Aaltonen]

** Bug watch added: freedesktop.org Bugzilla #110187
   https://bugs.freedesktop.org/show_bug.cgi?id=110187

** Also affects: dri via
   https://bugs.freedesktop.org/show_bug.cgi?id=110187
   Importance: Unknown
   Status: Unknown

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

Title:
  Triple 4K monitor display failed (modesetting driver limited to
  8192x8192)

Status in DRI:
  Unknown
Status in X.Org X server:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Confirmed
Status in mesa source package in Bionic:
  Fix Released
Status in xorg-server source package in Bionic:
  Confirmed

Bug description:
  Title: Triple monitor display failed with Dell Dock (HiDPI)
  (modesetting)

  Summary: Triple monitor display failed with Dell Dock (HiDPI)
  (modesetting)

  Steps:
  1. a laptop with Built-in 4K LCD
  2. Cold boot system with Dell Dock connected
  3. Connect a 4K monitor to Dock
  4. Connect 2nd 4K monitor to Dock
  5. Go to [All Settings]=>[Displays] to have the following configuration.
  Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors)
  Mirror displays: disable

  Expected results: Triple monitor display should works without issues
  Actual results: Triple monitor display failed with Dell Dock

  Additional information:
  1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04
  2. Laptop: Dell Precision 5520
  3. Dell Business Thunderbolt Dock - TB16
  https://goo.gl/vFDjpi

  WORKAROUND (UBUNTU 18.04+):
  Log in to "Ubuntu on Wayland" instead of "Ubuntu".

  ---
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:07bf]
     Subsystem: Dell Device [1028:07bf]
  InstallationDate: Installed on 2017-08-29 (2 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Precision 5520
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed 
root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.11.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.3
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/dri/+bug/1714178/+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 1823125] Re: tomcat9 fails to install in 18.04

[Balint Reczey]

The issue seems to be in systemd-sysusers, but to be released to bionic
tomcat9 needs to either depend on a fixed systemd or create the user by
other means.

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

Title:
  tomcat9 fails to install in 18.04

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

Bug description:
  # apt install tomcat9
  ...
  Setting up tomcat9 (9.0.16-3~18.04) ...
  [/usr/lib/sysusers.d/tomcat9.conf:7] Trailing garbage.

  Creating config file /etc/tomcat9/tomcat-users.xml with new version
  chown: invalid group: ‘root:tomcat’
  dpkg: error processing package tomcat9 (--configure):
   installed tomcat9 package post-installation script subprocess returned error 
exit status 1
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  Processing triggers for ureadahead (0.100.0-20) ...
  Processing triggers for systemd (237-3ubuntu10.15) ...
  Processing triggers for ca-certificates (20180409) ...
  Updating certificates in /etc/ssl/certs...
  0 added, 0 removed; done.
  Running hooks in /etc/ca-certificates/update.d...

  done.
  done.
  Processing triggers for rsyslog (8.32.0-1ubuntu4) ...
  Errors were encountered while processing:
   tomcat9
  E: Sub-process /usr/bin/dpkg returned an error code (1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823125/+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 1822426] Re: 19.04 Built in Intel HDA sound is disabled upon resume

[Cristian Măgherușan-Stanciu]

I also noticed this, my laptop's integrated Intel audio device is also
missing from pulseaudio(both as input and output), but I can see other
HDMI or USB sound devices I may have attached and I can switch to them
and they work as expected.

Interestingly the device works when playing a WAV file using aplay, but
only if I run aplay as root. As a normal user I can just see it in
alsamixer and I can play with the volume and mute controls there.

Here's the error I get when using aplay as my ordinary user:
$  aplay test.wav 
ALSA lib pcm_dmix.c:1071:(snd_pcm_dmix_open) unable to create IPC semaphore
aplay: main:828: audio open error: Permission denied

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

Title:
  19.04 Built in Intel HDA sound is disabled upon resume

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

Bug description:
  With 19.04, Intel Corporation 8 Series/C220 Series Chipset High
  Definition Audio Controller intermittently is not enabled when
  resuming from sleep. The HDMI sound device is enabled but that is not
  hooked up on my system.  New with 19.04, when sound works after
  resume, an icon labeled "Built in Audio Stereo" appears during the
  resume process.

  Unsure if this is related, but sound seems to sleep when not in use.
  Launching sound enabled apps produces a quiet "tick, thud" sound as
  sound system turns on.

  When sound is not working, killall pusleaudio "fixes" the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  darin  4814 F pulseaudio
   /dev/snd/controlC1:  darin  4814 F pulseaudio
   /dev/snd/controlC0:  darin  4814 F pulseaudio
  CurrentDesktop: KDE
  Date: Sat Mar 30 10:20:24 2019
  InstallationDate: Installed on 2018-01-13 (441 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180112)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-03-27 (3 days ago)
  dmi.bios.date: 08/18/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-PRO
  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.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822426/+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 1823139] Re: package unattended-upgrades (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 1

[Balint Reczey]

https://answers.launchpad.net/ubuntu/+source/apt/+question/284708

Removing unattended-upgrades (0.90ubuntu0.10) ...
Purging configuration files for unattended-upgrades (0.90ubuntu0.10) ...
insserv: warning: script 'S99runmbbservice' missing LSB tags and overrides
insserv: warning: script 'runmbbservice' missing LSB tags and overrides
insserv: There is a loop between service plymouth and procps if started
insserv:  loop involving service procps at depth 2
insserv:  loop involving service udev at depth 1
insserv: There is a loop between service runmbbservice and hwclock if started
insserv:  loop involving service hwclock at depth 1
insserv:  loop involving service checkroot at depth 3
insserv:  loop involving service mountdevsubfs at depth 1
insserv: There is a loop at service runmbbservice if started
insserv: There is a loop at service plymouth if started
insserv:  loop involving service networking at depth 4
insserv: Starting runmbbservice depends on plymouth and therefore on system 
facility `$all' which ...
insserv: There is a loop between service runmbbservice and dns-clean if started
insserv:  loop involving service dns-clean at depth 1
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header
dpkg: error processing package unattended-upgrades (--purge):
 subprocess installed post-removal script returned error exit status 1

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Invalid

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

Title:
  package unattended-upgrades (not installed) failed to install/upgrade:
  subprocess installed post-removal script returned error exit status 1

Status in unattended-upgrades package in Ubuntu:
  Invalid

Bug description:
  during startup i get this error.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  AptOrdering:
   unattended-upgrades: Purge
   rsyslog: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Apr  2 17:52:13 2019
  ErrorMessage: subprocess installed post-removal script returned error exit 
status 1
  InstallationDate: Installed on 2018-08-09 (238 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.31
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades (not installed) failed to install/upgrade: 
subprocess installed post-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1823139/+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 1823077] Re: Cannot upgrade libxkbcommon0 without removing half the operating system

[Sebastien Bacher]

Thank you for your bug report. How do you try to upgrade? Can you copy
the log of the command?

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

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

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

Title:
  Cannot upgrade libxkbcommon0 without removing half the operating
  system

Status in libxkbcommon package in Ubuntu:
  Incomplete

Bug description:
  Attempting to upgrade the libxkbcommon0:i386 0.8.0-1ubuntu0.1 to
  0.8.2-1~ubuntu18.04.1 will cause a large amount of packages central to
  the OS to be removed - basically more than a thousand packages.  Never
  seen anything like this.  Dependencies need to be fixed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libxkbcommon0 0.8.0-1ubuntu0.1
  ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Wed Apr  3 16:22:28 2019
  Dependencies:
   gcc-8-base 8.3.0-5ubuntu1~18.04
   libc6 2.27-3ubuntu1
   libgcc1 1:8.3.0-5ubuntu1~18.04
   xkb-data 2.23.1-1ubuntu1.18.04.1
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 4.18.0-17-generic, x86_64: installedError! Could not 
locate dkms.conf file.
   File:  does not exist.
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Device [1558:1323]
  InstallationDate: Installed on 2019-01-15 (78 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: System76 Galago Pro
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-17-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash i915.enable_guc=-1 vt.handoff=1
  SourcePackage: libxkbcommon
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/05/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.03
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Galago Pro
  dmi.board.vendor: System76
  dmi.board.version: galp3-c
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: galp3-c
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.03:bd12/05/2018:svnSystem76:pnGalagoPro:pvrgalp3-c:rvnSystem76:rnGalagoPro:rvrgalp3-c:cvnSystem76:ct10:cvrgalp3-c:
  dmi.product.family: Not Applicable
  dmi.product.name: Galago Pro
  dmi.product.sku: Not Applicable
  dmi.product.version: galp3-c
  dmi.sys.vendor: System76
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.3-1ubuntu1~18.04~ppa1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.3-1ubuntu1~18.04~ppa1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1823077/+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 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 - failure to load i915 kernel module

[Derk Willem te Bokkel]

so why the peculiar behaviour that lightdm works when the partition
installed native grub boots the system

BUT not when a grub installed by another partition is used then lightdm
consistently crashes and the machine locks up..

BUT if i915 is added to /etc/modules in the offending partition it all
seems to work properly .. except plymouth does not show up..

if grub is restored by the offending partition via booting via rescue or
working through a chroot  WITHOUT i915 added to /etc/modules i.e. as
installed originally .. the system seems to work but some times only
vesa is used after an initial lightdm crash ..

Then there is partition sda1 which consistently works from any grub
installed by other partitions and NEVER had i915 added to /etc/modules
..

please explain...what might cause this

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

Title:
  lightdm login screen briefly appears and then blanks out on Intel(R)
  Core(TM)2 Duo CPU T5870 - failure to load i915 kernel module

Status in lightdm package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: 

[Touch-packages] [Bug 1822730] Re: Disco server install fails to boot using encrypted partitions

[Dimitri John Ledkov]

sigh, looks like initramfs-tools-core now depends on busybox-initramfs,
instead of using busybox nor busybox static.

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

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

Title:
  Disco server install fails to boot using encrypted partitions

Status in busybox package in Ubuntu:
  Fix Committed

Bug description:
  Performing a fresh Disco (daily build from 2019-03-31) server install
  with / mounted from LVM over dm-crypt (over mdadm), the boot fails
  just after asking the encrypted partition passphrase with the
  following error:

  /scripts/local-top/cryptroot: line 1: fold: not found

  Building a custom busybox package with "fold" binary enabled for
  busybox-initramfs and busybox-static configs fixes the issue.

  Diff from debian/ directory:

  diff --git a/config/pkg/initramfs b/config/pkg/initramfs
  index 2ef98e5..5725daf 100644
  --- a/config/pkg/initramfs
  +++ b/config/pkg/initramfs
  @@ -228,7 +228,7 @@ CONFIG_EXPR=y
   CONFIG_EXPR_MATH_SUPPORT_64=y
   # CONFIG_FACTOR is not set
   CONFIG_FALSE=y
  -# CONFIG_FOLD is not set
  +CONFIG_FOLD=y
   # CONFIG_FSYNC is not set
   # CONFIG_HEAD is not set
   # CONFIG_FEATURE_FANCY_HEAD is not set
  diff --git a/config/pkg/udeb b/config/pkg/udeb
  index 7538ae5..f9a6d4c 100644
  --- a/config/pkg/udeb
  +++ b/config/pkg/udeb
  @@ -228,7 +228,7 @@ CONFIG_EXPR=y
   CONFIG_EXPR_MATH_SUPPORT_64=y
   # CONFIG_FACTOR is not set
   CONFIG_FALSE=y
  -# CONFIG_FOLD is not set
  +CONFIG_FOLD=y
   # CONFIG_FSYNC is not set
   CONFIG_HEAD=y
   CONFIG_FEATURE_FANCY_HEAD=y

  It might be enough to add "fold" to the initramfs variant only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1822730/+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 1822730] Re: Disco server install fails to boot using encrypted partitions

[Dimitri John Ledkov]

Also, cryptsetup uses Depends: busybox-static | busybox
and both of those variants have FOLD enabled.

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

Title:
  Disco server install fails to boot using encrypted partitions

Status in busybox package in Ubuntu:
  Fix Committed

Bug description:
  Performing a fresh Disco (daily build from 2019-03-31) server install
  with / mounted from LVM over dm-crypt (over mdadm), the boot fails
  just after asking the encrypted partition passphrase with the
  following error:

  /scripts/local-top/cryptroot: line 1: fold: not found

  Building a custom busybox package with "fold" binary enabled for
  busybox-initramfs and busybox-static configs fixes the issue.

  Diff from debian/ directory:

  diff --git a/config/pkg/initramfs b/config/pkg/initramfs
  index 2ef98e5..5725daf 100644
  --- a/config/pkg/initramfs
  +++ b/config/pkg/initramfs
  @@ -228,7 +228,7 @@ CONFIG_EXPR=y
   CONFIG_EXPR_MATH_SUPPORT_64=y
   # CONFIG_FACTOR is not set
   CONFIG_FALSE=y
  -# CONFIG_FOLD is not set
  +CONFIG_FOLD=y
   # CONFIG_FSYNC is not set
   # CONFIG_HEAD is not set
   # CONFIG_FEATURE_FANCY_HEAD is not set
  diff --git a/config/pkg/udeb b/config/pkg/udeb
  index 7538ae5..f9a6d4c 100644
  --- a/config/pkg/udeb
  +++ b/config/pkg/udeb
  @@ -228,7 +228,7 @@ CONFIG_EXPR=y
   CONFIG_EXPR_MATH_SUPPORT_64=y
   # CONFIG_FACTOR is not set
   CONFIG_FALSE=y
  -# CONFIG_FOLD is not set
  +CONFIG_FOLD=y
   # CONFIG_FSYNC is not set
   CONFIG_HEAD=y
   CONFIG_FEATURE_FANCY_HEAD=y

  It might be enough to add "fold" to the initramfs variant only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1822730/+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 1822730] Re: Disco server install fails to boot using encrypted partitions

[Dimitri John Ledkov]

Normally one should have plymouth installed, and fold code path
shouldn't be used.

Do you not have plymouth installed, and/or does it not work in you
environment?

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

Title:
  Disco server install fails to boot using encrypted partitions

Status in busybox package in Ubuntu:
  Fix Committed

Bug description:
  Performing a fresh Disco (daily build from 2019-03-31) server install
  with / mounted from LVM over dm-crypt (over mdadm), the boot fails
  just after asking the encrypted partition passphrase with the
  following error:

  /scripts/local-top/cryptroot: line 1: fold: not found

  Building a custom busybox package with "fold" binary enabled for
  busybox-initramfs and busybox-static configs fixes the issue.

  Diff from debian/ directory:

  diff --git a/config/pkg/initramfs b/config/pkg/initramfs
  index 2ef98e5..5725daf 100644
  --- a/config/pkg/initramfs
  +++ b/config/pkg/initramfs
  @@ -228,7 +228,7 @@ CONFIG_EXPR=y
   CONFIG_EXPR_MATH_SUPPORT_64=y
   # CONFIG_FACTOR is not set
   CONFIG_FALSE=y
  -# CONFIG_FOLD is not set
  +CONFIG_FOLD=y
   # CONFIG_FSYNC is not set
   # CONFIG_HEAD is not set
   # CONFIG_FEATURE_FANCY_HEAD is not set
  diff --git a/config/pkg/udeb b/config/pkg/udeb
  index 7538ae5..f9a6d4c 100644
  --- a/config/pkg/udeb
  +++ b/config/pkg/udeb
  @@ -228,7 +228,7 @@ CONFIG_EXPR=y
   CONFIG_EXPR_MATH_SUPPORT_64=y
   # CONFIG_FACTOR is not set
   CONFIG_FALSE=y
  -# CONFIG_FOLD is not set
  +CONFIG_FOLD=y
   # CONFIG_FSYNC is not set
   CONFIG_HEAD=y
   CONFIG_FEATURE_FANCY_HEAD=y

  It might be enough to add "fold" to the initramfs variant only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1822730/+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 1823125] Re: tomcat9 fails to install in 18.04

[Balint Reczey]

Fixed it in tomcat9 only, by not setting shell in sysusers.d/tomcat9.conf .
The slightly ugly part is that systemd sets the default shell to 
/sbin/nologin , not /usr/sbin/nologin that exists on Ubuntu.
The effect is the same, user can't log in it is just a little ugly and with 
mergedusr the problem goes away thus I have not filed a bug for it.

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

Title:
  tomcat9 fails to install in 18.04

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

Bug description:
  # apt install tomcat9
  ...
  Setting up tomcat9 (9.0.16-3~18.04) ...
  [/usr/lib/sysusers.d/tomcat9.conf:7] Trailing garbage.

  Creating config file /etc/tomcat9/tomcat-users.xml with new version
  chown: invalid group: ‘root:tomcat’
  dpkg: error processing package tomcat9 (--configure):
   installed tomcat9 package post-installation script subprocess returned error 
exit status 1
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  Processing triggers for ureadahead (0.100.0-20) ...
  Processing triggers for systemd (237-3ubuntu10.15) ...
  Processing triggers for ca-certificates (20180409) ...
  Updating certificates in /etc/ssl/certs...
  0 added, 0 removed; done.
  Running hooks in /etc/ca-certificates/update.d...

  done.
  done.
  Processing triggers for rsyslog (8.32.0-1ubuntu4) ...
  Errors were encountered while processing:
   tomcat9
  E: Sub-process /usr/bin/dpkg returned an error code (1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823125/+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 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS

[Dimitri John Ledkov]

** Description changed:

  [Impact]
  
   * OpenSSL 1.1.1 is an LTS release upstream, which will continue to
  receive security support for much longer than 1.1.0 series will.
  
   * OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to be
  rapidly adopted due to increased set of supported hashes & algoes, as
  well as improved handshake [re-]negotiation.
  
   * OpenSSL 1.1.1 comes with improved hw-acceleration capabilities.
  
   * OpenSSL 1.1.1 is ABI/API compatible with 1.1.0, however some software
  is sensitive to the negotiation handshake and may either need
  patches/improvements or clamp-down to maximum v1.2.
  
  [Test Case]
  
   * Rebuild all reverse dependencies
  
   * Execute autopkg tests for all of them
  
   * Clamp down to TLS v1.2 software that does not support TLS v1.3 (e.g.
  mongodb)
  
   * Backport TLS v1.3 support patches, where applicable
+ 
+ [Test cases for the python updates]
+ 
+ python3.7 is a preview in bionic as a non-supported/non-default
+ version of python3. Passing it's own autopkgtests is sufficient
+ validation for python3.7. It includes a point release update, with
+ OpenSSL 1.1.1 compat and features.
+ 
+ python3.6 not only has OpenSSL 1.1.1 compat and features patches, but
+ also includes a point release update to 3.6.8. It has been part of the
+ full-archive rebuild and regression analysis. Autopkgtests were
+ triggered for python3.6 and python3-defaults with regressions already
+ fixed in the individual packages as appropriate.
+ 
+ python2.7 has the update from .15~rc1 to .15 final, with OpenSSL 1.1.1
+ compat only. It has been part of the full-archive rebuild and
+ regression analysis. Autopkgtests were triggered for python2.7 and
+ python-defaults with regressions already fixed in the individual
+ packages as appropriate.
  
  [Regression Potential]
  
   * Connectivity interop is the biggest issues which will be unavoidable
  with introducing TLS v1.3. However, tests on cosmic demonstrate that
  curl/nginx/google-chrome/mozilla-firefox connect and negotiate TLS v1.3
  without issues.
  
   * Mitigation of discovered connectivity issues will be possible by
  clamping down to TLS v1.2 in either server-side or client-side software
  or by backporting relevant support fixes
  
   * Notable changes are listed here
  https://wiki.openssl.org/index.php/TLS1.3
  
   * Most common connectivity issues so far:
     - client verifies SNI in TLSv1.3 mode, yet client doesn't set hostname. 
Solution is client change to set hostname, or to clamp down the client to 
TLSv1.2.
  
     - session negotiation is different in TLSv1.3, existing client code
  may fail to create/negotiate/resume session. Clients need to learn how
  to use session callback.
  
   * This update bundles python 3.6 and 3.7 point releases
  
  [Other Info]
  
   * Previous FFe for OpenSSL in 18.10 is at
     https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1793092
  
   * TLS v1.3 support in NSS is expected to make it to 18.04 via security
  updates
  
   * TLS v1.3 support in GnuTLS is expected to be available in 19.04
  
   * Test OpenSSL is being prepared in
     https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3473
+ 
+ [Autopkgtest Regressions]
+ 
+ dovecot/armhf - flakey
+ 
+ libnet-ssleay-perl - awaiting sru accept into proposed of
+ libnet-ssleay-perl and libio-socket-ssl-perl due to fixes and
+ versioned breaks.
+ 
+ linux* - rebuild testcases passes (for some edge flavours the build
+ fails in non-ssl portions of the build), ubuntu-regression-suite
+ testcase fails for a few variants but should have been skipped (in
+ progress to be fixed in
+ https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823056)
+ 
+ openvswitch/i386 - extremely flakey, errors out or fails mostly

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

Title:
  [SRU] OpenSSL 1.1.1 to 18.04 LTS

Status in openssl package in Ubuntu:
  In Progress
Status in libio-socket-ssl-perl source package in Bionic:
  New
Status in libnet-ssleay-perl source package in Bionic:
  New
Status in nova source package in Bionic:
  New
Status in openssl source package in Bionic:
  Fix Committed
Status in python-cryptography source package in Bionic:
  New
Status in python2.7 source package in Bionic:
  New
Status in python3.6 source package in Bionic:
  New
Status in python3.7 source package in Bionic:
  New
Status in r-cran-openssl source package in Bionic:
  Fix Committed
Status in ruby-openssl source package in Bionic:
  Fix Committed
Status in ruby2.5 source package in Bionic:
  New

Bug description:
  [Impact]

   * OpenSSL 1.1.1 is an LTS release upstream, which will continue to
  receive security support for much longer than 1.1.0 series will.

   * OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to
  be rapidly adopted due to increased set of supported hashes & 

[Touch-packages] [Bug 1693819] Re: dhclient DHCPv6 does not work with interface alias

[Dan Streetman]

** Changed in: isc-dhcp (Ubuntu)
 Assignee: Dan Streetman (ddstreet) => (unassigned)

** Changed in: isc-dhcp (Ubuntu Zesty)
 Assignee: Dan Streetman (ddstreet) => (unassigned)

** Changed in: isc-dhcp (Ubuntu Artful)
   Status: In Progress => Confirmed

** Changed in: isc-dhcp (Ubuntu Artful)
 Assignee: Dan Streetman (ddstreet) => (unassigned)

** Changed in: isc-dhcp (Ubuntu Yakkety)
 Assignee: Dan Streetman (ddstreet) => (unassigned)

** Changed in: isc-dhcp (Ubuntu Xenial)
 Assignee: Dan Streetman (ddstreet) => (unassigned)

** Changed in: isc-dhcp (Ubuntu Trusty)
 Assignee: Dan Streetman (ddstreet) => (unassigned)

** Changed in: isc-dhcp (Ubuntu)
   Status: In Progress => Confirmed

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

** Changed in: isc-dhcp (Ubuntu Trusty)
   Status: Confirmed => Won't Fix

** Changed in: isc-dhcp (Ubuntu Xenial)
   Status: Confirmed => Won't Fix

** Changed in: isc-dhcp (Ubuntu Yakkety)
   Status: Confirmed => Won't Fix

** Changed in: isc-dhcp (Ubuntu Zesty)
   Status: Confirmed => Won't Fix

** Changed in: isc-dhcp (Ubuntu Artful)
   Status: Confirmed => Won't Fix

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

Title:
  dhclient DHCPv6 does not work with interface alias

Status in isc-dhcp package in Ubuntu:
  Won't Fix
Status in isc-dhcp source package in Trusty:
  Won't Fix
Status in isc-dhcp source package in Xenial:
  Won't Fix
Status in isc-dhcp source package in Yakkety:
  Won't Fix
Status in isc-dhcp source package in Zesty:
  Won't Fix
Status in isc-dhcp source package in Artful:
  Won't Fix
Status in isc-dhcp package in Debian:
  New

Bug description:
  [Impact]

  The isc-dhcp-client dhclient program does not work with interface
  alias names, e.g. eth0:1.  It fails immediately.

  [Test Case]

  On trusty through artful, find an interface that is connected to a
  network that has a DHCPv6 server on it.  First verify it can get a
  DHCPv6 address, e.g.:

  $ sudo dhclient -6 -v ens7

  that should successfully set up a DHCPv6 address on the interface.
  Then release the interface:

  $ sudo dhclient -6 -v -r ens7

  Now, try again but use the interface alias, e.g.:

  $ sudo dhclient -6 -v ens7:1

  It should succeed, but it will fail with:

  no link-local IPv6 address for ens7:1

  [Regression Potential]

  Changing how isc-dhcp handles (enumerates/lists/compares) interface
  names may lead to isc-dhcp using the wrong interface or failing to
  find the correct interface to use.  However, if the only change is to
  strip the alias part from the interface during comparison, the
  possibility of error should be small, since all interface aliases
  point back to the same physical interface.

  [Other Info]

  This bug exists in the upstream isc-dhcp; the ISC has no public bug
  tracker, and only accepts bug reports via private email, which has
  been sent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1693819/+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 1818282] Re: systemd-networkd - RoutingPolicyRule does not apply correctly

[Bug Watch Updater]

** Changed in: systemd (Debian)
   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/1818282

Title:
  systemd-networkd - RoutingPolicyRule does not apply correctly

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

Bug description:
  [Impact]

  When attaching multiple IPs on secondary interface the routing policy rules 
do not
  apply for all IPs.
  The rules that are applied after restarting networkd are random.

  The issue has been reported and addressed upstream.

  [Test Case]

  Attach multiple IPs to secondary interface, config file:

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

  [Network]
  Address=172.31.28.195/20
  Address=172.31.24.151/20
  Address=172.31.24.152/20
  Address=172.31.24.153/20

  [Route]
  Destination=0.0.0.0/0
  Gateway=172.31.16.1
  Table=1000

  [Route]
  Destination=172.31.24.153
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [Route]
  Destination=172.31.28.195
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [Route]
  Destination=172.31.24.151
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [Route]
  Destination=172.31.24.152
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [RoutingPolicyRule]
  From=172.31.24.153
  Table=1000

  [RoutingPolicyRule]
  From=172.31.28.195
  Table=1000

  [RoutingPolicyRule]
  From=172.31.24.152
  Table=1000

  [RoutingPolicyRule]
  From=172.31.24.151
  Table=1000

  $ ip rule show
  0:from all lookup local
  0:from 172.31.24.151 lookup 1000
  32766:from all lookup main
  32767:from all lookup default

  - restart networkd

  $ sudo systemctl restart systemd-networkd

  $ ip rule show
  0:from all lookup local
  0:from 172.31.24.151 lookup 1000
  0:from 172.31.24.153 lookup 1000
  0:from 172.31.28.195 lookup 1000
  32766:from all lookup main
  32767:from all lookup default

  - restart again

  $ sudo systemctl restart systemd-networkd

  $ ip rule show
  0:from all lookup local
  0:from 172.31.24.151 lookup 1000
  0:from 172.31.24.152 lookup 1000
  32766:from all lookup main
  32767:from all lookup default

  The behaviour is random

  [Regression Potential]

  May impact the systemd-networkd service functionality.

  [Other]

  Affects Disco Bionic and Cosmic.

  Upstream bug : https://github.com/systemd/systemd/issues/11280
  Upstream fix : https://github.com/systemd/systemd/pull/11795/commits

  $ lsb_release -rd
  Description:  Ubuntu Disco Dingo (development branch)
  Release:  19.04

  Systemd version :
  systemd:
    Installed: 240-6ubuntu1
    Candidate: 240-6ubuntu1
    Version table:
   *** 240-6ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818282/+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 105101] Re: the "lock screen" thing is slow to appear after opening the lid

[Pier]

Affects Mint 18.3 Sylvia release on Ubuntu xenial too.

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

Title:
  the "lock screen" thing is slow to appear after opening the lid

Status in GNOME Screensaver:
  Invalid
Status in pam package in Ubuntu:
  Incomplete
Status in gnome-screensaver package in Debian:
  Confirmed

Bug description:
  Binary package hint: gnome-screensaver

  This is on Ubuntu Feisty, up to date, running on a Dell Latitude D620
  laptop (Intel video). I have the computer set up to lock the screen
  when I close the lid. (This mostly works.)

  When I open the lid, though, there's almost always a delay before the
  "unlock" window appears. I can open the lid, type the password, and
  still have to wait three-four seconds, sometimes more, before the
  "enter password" window appears. It receives the already-typed
  password and then goes away in a second or so. Note that the screen
  turns on pretty much instantly (the back-light is usually on by the
  time the screen is up). Also, the laptop is NOT in stand-by or
  anything, it's running normally.

  The password-entry box should appear instantly (by the time the back-
  light turns on) and disappear the moment enter is pressed. After all,
  it's an extremely resource-light application. (It's OK if the desktop
  takes a bit to redraw after; that's a potentially slow operation. But
  just showing the password box on a black screen should be very quick.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-screensaver/+bug/105101/+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 1823070] Re: unattended-upgrades should tell the user (via motd) when security updates are held back

[Francis Ginther]

** Tags added: id-5ca50c3568756c4a351b6f5f

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

Title:
  unattended-upgrades should tell the user (via motd) when security
  updates are held back

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  Currently we have the following pieces as part of the default UX on
  Ubuntu 18.04 and later:

   1) unattended-upgrades automatically installs security updates daily by 
default
   2) the motd reports the number of available updates, including security 
updates.

  A user who knows about 1) also knows that a non-zero number of pending
  security updates listed in 2) is nothing to worry about.

  However, unattended-upgrades will also cleverly detect when a security
  update cannot safely be installed non-interactively due to conffile
  changes on the system.

  In this case, unattended-upgrades should also inform the user via the
  motd that these updates are not being installed.  Otherwise, there's
  nothing to tell the user that the non-zero count of available security
  updates in motd is a *problem*.

  Suggested wording:

   N security updates will not be automatically installed due to local changes.
   See /var/log/foo for details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1823070/+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 1823171] [NEW] systemd-resolve hides DS records in explicit queries

[Nicos Gollan]

Public bug reported:

When querying for DS resource records on a DNSSEC signed domain using
dig, the DS records are not shown when the system is using systemd-
resolve.

Run: dig +short DS ripe.net

Expected: something like
40991 8 2 D8D3C88263D58930A8B5FE16427130AB84CA73A4988385B2F4B121A7 2E5299A6

Actual result: no output.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu10.15
ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
Uname: Linux 4.15.0-46-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: KDE
Date: Thu Apr  4 14:14:06 2019
MachineType: MSI MS-7A70
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=/dev/mapper/system-slash ro
SourcePackage: systemd
SystemdDelta:
 [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
 
 2 overridden configuration files found.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/03/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: A.80
dmi.board.asset.tag: Default string
dmi.board.name: B250M PRO-VDH (MS-7A70)
dmi.board.vendor: MSI
dmi.board.version: 2.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 2.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.80:bd07/03/2018:svnMSI:pnMS-7A70:pvr2.0:rvnMSI:rnB250MPRO-VDH(MS-7A70):rvr2.0:cvnMSI:ct3:cvr2.0:
dmi.product.family: Default string
dmi.product.name: MS-7A70
dmi.product.version: 2.0
dmi.sys.vendor: MSI

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


** Tags: amd64 apport-bug bionic

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

Title:
  systemd-resolve hides DS records in explicit queries

Status in systemd package in Ubuntu:
  New

Bug description:
  When querying for DS resource records on a DNSSEC signed domain using
  dig, the DS records are not shown when the system is using systemd-
  resolve.

  Run: dig +short DS ripe.net

  Expected: something like
  40991 8 2 D8D3C88263D58930A8B5FE16427130AB84CA73A4988385B2F4B121A7 2E5299A6

  Actual result: no output.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.15
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Apr  4 14:14:06 2019
  MachineType: MSI MS-7A70
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=/dev/mapper/system-slash ro
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/03/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.80
  dmi.board.asset.tag: Default string
  dmi.board.name: B250M PRO-VDH (MS-7A70)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.80:bd07/03/2018:svnMSI:pnMS-7A70:pvr2.0:rvnMSI:rnB250MPRO-VDH(MS-7A70):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A70
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823171/+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 1823125] Re: tomcat9 fails to install in 18.04

[Balint Reczey]

** Changed in: systemd (Ubuntu Bionic)
   Status: New => Won't Fix

** Changed in: tomcat9 (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/1823125

Title:
  tomcat9 fails to install in 18.04

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

Bug description:
  # apt install tomcat9
  ...
  Setting up tomcat9 (9.0.16-3~18.04) ...
  [/usr/lib/sysusers.d/tomcat9.conf:7] Trailing garbage.

  Creating config file /etc/tomcat9/tomcat-users.xml with new version
  chown: invalid group: ‘root:tomcat’
  dpkg: error processing package tomcat9 (--configure):
   installed tomcat9 package post-installation script subprocess returned error 
exit status 1
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  Processing triggers for ureadahead (0.100.0-20) ...
  Processing triggers for systemd (237-3ubuntu10.15) ...
  Processing triggers for ca-certificates (20180409) ...
  Updating certificates in /etc/ssl/certs...
  0 added, 0 removed; done.
  Running hooks in /etc/ca-certificates/update.d...

  done.
  done.
  Processing triggers for rsyslog (8.32.0-1ubuntu4) ...
  Errors were encountered while processing:
   tomcat9
  E: Sub-process /usr/bin/dpkg returned an error code (1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823125/+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 1754628] Re: vaapi not working [libva error: dlopen of /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so failed: /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so: undefined

[Timo Aaltonen]

can't mix amdgpu and distro, I'm sure there's a vaapi driver for amdpgu
too, or if this error is from it, complain to AMD

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

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

Title:
  vaapi not working [libva error: dlopen of /usr/lib/x86_64-linux-
  gnu/dri/radeonsi_drv_video.so failed: /usr/lib/x86_64-linux-
  gnu/dri/radeonsi_drv_video.so: undefined symbol:
  amdgpu_cs_syncobj_import_sync_file]

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=18.04
  DISTRIB_CODENAME=bionic
  DISTRIB_DESCRIPTION="Ubuntu Bionic Beaver (development branch)"

  04:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Ellesmere [Radeon RX 470/480] [1002:67df] (rev e7)
Subsystem: Sapphire Technology Limited Ellesmere [Radeon RX 
470/480/570/580] (Nitro+ Radeon RX 580 4GB) [1da2:e366]

  The graphics run by the amdgpu (not -pro) and is unable to address va-
  api acceleration.

  eric@athena:~$ vainfo
  libva info: VA-API version 1.1.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
  libva error: dlopen of /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so 
failed: /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so: undefined symbol: 
amdgpu_cs_syncobj_import_sync_file
  libva info: va_openDriver() returns -1
  vaInitialize failed with error code -1 (unknown libva error),exit

  While open GL software like the unigine heaven benchmark runs very
  well.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,gnomecompat,grid,imgpng,mousepoll,move,place,regex,resize,session,unitymtgrabhandles,wall,wobbly,animation,expo,ezoom,fade,scale,unityshell,workarounds]
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Mar  9 12:16:28 2018
  DistUpgraded: 2018-03-09 11:15:52,669 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: amdgpu, 17.50-511655, 4.13.0-36-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] 
[1002:67df] (rev e7) (prog-if 00 [VGA controller])
 Subsystem: Sapphire Technology Limited Ellesmere [Radeon RX 
470/480/570/580] (Nitro+ Radeon RX 580 4GB) [1da2:e366]
  InstallationDate: Installed on 2018-01-04 (63 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=9782f23b-461f-4cf0-b7d4-9b4e2739964c ro iommu=soft quiet splash 
vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-03-09 (0 days ago)
  dmi.bios.date: 10/07/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2g
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970A-UD3P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2g:bd10/07/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu Jan 11 18:02:23 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: amdgpu

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

-- 
Mailing list: 

[Touch-packages] [Bug 1013597] Re: No default route for stateful DHCPv6

[Dan Streetman]

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

** Changed in: ifupdown (Ubuntu Precise)
 Assignee: Dan Streetman (ddstreet) => (unassigned)

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

Title:
  No default route for stateful DHCPv6

Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifupdown source package in Precise:
  Triaged

Bug description:
  The default route cannot be provided via DHCPv6, it must be obtained
  from router advertisements. However, when using the dhcp method for
  inet6 in /etc/network/interfaces (e.g. "iface eth0 inet6 dhcp"), ifup
  will set net.ipv6.conf..accept_ra=0, resulting in no default
  route for IPv6. Instead, it should explicitly set accept_ra=1.

  A workaround is to set it in a post-up script. However, Linux
  apparently only sends router solicitations when the interface is
  brought up, so if unsolicited RA:s are infrequent the host will be
  without a default route until the next RA.

  Another problem is that when bringing the interface down on dual-stack
  hosts, there will be a long timeout. This is because bringing down
  IPv4 also brings the interface link down, and afterwards dhclient
  cannot release the DHCPv6 lease due to the link being down ("RTNETLINK
  answers: Cannot assign requested address"). The workaround is to bring
  the link back up before bringing IPv6 down.

  So the workarounds (which obviously should not be needed) for a dual-
  stack dhcp client look like this:

  iface eth0 inet dhcp
  iface eth0 inet6 dhcp
  up sysctl net.ipv6.conf.$IFACE.accept_ra=1
  pre-down ip link set dev $IFACE up

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1013597/+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 1821491] Re: DNS lookup fails for local hosts

[Steve Roberts]

Okay thanks for the attention, full output below:

$ systemd-resolve --status
Global
  DNS Domain: phs
  DNSSEC NTA: 10.in-addr.arpa
  16.172.in-addr.arpa
  168.192.in-addr.arpa
  17.172.in-addr.arpa
  18.172.in-addr.arpa
  19.172.in-addr.arpa
  20.172.in-addr.arpa
  21.172.in-addr.arpa
  22.172.in-addr.arpa
  23.172.in-addr.arpa
  24.172.in-addr.arpa
  25.172.in-addr.arpa
  26.172.in-addr.arpa
  27.172.in-addr.arpa
  28.172.in-addr.arpa
  29.172.in-addr.arpa
  30.172.in-addr.arpa
  31.172.in-addr.arpa
  corp
  d.f.ip6.arpa
  home
  internal
  intranet
  lan
  local
  private
  test

Link 2 (wlp2s0)
  Current Scopes: DNS
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no
 DNS Servers: 192.168.2.1
  DNS Domain: ~.
  phs


$ nslookup phspi05
Server: 127.0.0.53
Address:127.0.0.53#53

** server can't find phspi05: SERVFAIL

if I specify the dns in nslookup
$ nslookup phspi05 192.168.2.1
Server: 192.168.2.1
Address:192.168.2.1#53

Non-authoritative answer:
Name:   phspi05
Address: 192.168.2.35
** server can't find phspi05: NXDOMAIN

and the contents of resolv.conf

$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.

nameserver 127.0.0.53
search phs

If I manually edit resolv.conf to the local dns, nslookup, ping etc.
work as expected (until the next reboot of course)

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

Title:
  DNS lookup fails for local hosts

Status in resolvconf package in Ubuntu:
  Incomplete

Bug description:
  Mint 19 (Ubuntu Bionic) 
  Laptop so Using NetworkManager, and connecting wirelessly to LAN
  Upgraded from Mint 18.3 so using resolvconf...

  Versions:
  network-manager: 1.10.6-2ubuntu1.1
  resolvconf: 1.79ubuntu10.18.04.3 or 1.79ubuntu10.18.04.2
  systemd: 237-3ubuntu10.15

  dns is specified in NetworkMananager as 192.168.2.1
  the dns is a router, and has static ips assigned to certain hosts on my lan...

  $cat resolv.conf
  nameserver 127.0.0.53
  search phs
  options edns0

  $ nslookup phspi05
  Server:   127.0.0.53
  Address:  127.0.0.53#53

  ** server can't find phspi05: SERVFAIL

  If I explicity specify the dns:

  $ nslookup phspi05 192.168.2.1
  Server:   192.168.2.1
  Address:  192.168.2.1#53

  Non-authoritative answer:
  Name: phspi05
  Address: 192.168.2.35

  I get the correct ip address...

  Same with dig...

  I would expect that the nameserver set in network-manager would be
  used

  From tail of $ systemd-resolve --status

  Link 2 (wlp2s0)
Current Scopes: DNS
 LLMNR setting: yes
  MulticastDNS setting: no
DNSSEC setting: no
  DNSSEC supported: no
   DNS Servers: 192.168.2.1
DNS Domain: phs

  So the dns address had been picked up from NetworkManager, but
  apparently is not being used...

  Thought it might be related to this bug:
  https://bugs.launchpad.net/ubuntu/bionic/+source/resolvconf/+bug/1817903

  So installed the proposed fix, but no change. I also tried removing
  package resolvconf, again no change...

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

[bugproxy]

--- Comment From heinz-werner_se...@de.ibm.com 2019-04-04 09:01 EDT---
Basic testing is done on the image and it looks good.

Will be doing more testing and get back if any issues.

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

Title:
  Automatic ipv4 not assigned to bond interface is manual ipv6 is
  assigned to it

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

Bug description:
  ---Problem Description---
  Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get 
automatic ipv4 assigned from dhcp server.
   
  ---uname output---
  Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 
2018 s390x s390x s390x GNU/Linux
   
  Machine Type = s390x 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   When user configures ipv4 as automatic and ipv6 as manual for bond interface 
automatic ipv4 is not getting assigned.
  Looks like dhcp client request for ipv4 is not done to dhcp server after 
maunal ipv6 is assigned quickly to bond interface

  This issue will not happen in below cases:
  1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan 
interface.
  2)with ipv4 automatic and ipv6 automatic configuration for bond interface
  3)with ipv4 automatic and ipv6 disabled configuration for bond interface

  Configuration:
  Bond interface, ipv4 automatic mode and ipv6 automatic mode

  root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond 
  [connection]
  id=test_bond
  uuid=63e54542-5135-47ac-a954-b861c3937be2
  type=bond
  interface-name=test_bond
  permissions=
  timestamp=1537944121

  [ethernet]
  mac-address-blacklist=

  [bond]
  downdelay=0
  fail_over_mac=none
  miimon=100
  mode=active-backup
  num_grat_arp=0
  primary_reselect=always
  updelay=0

  [ipv4]
  dns-search=
  method=auto

  [ipv6]
  addr-gen-mode=stable-privacy
  dns-search=
  method=auto

  From /var/log/syslog, we can see ip got assigned:

  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 
255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e)
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on 
test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e)
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 
10.2.3.1
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1

  root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond
  28: test_bond:  mtu 1500 qdisc 
noqueue state UP group default qlen 1000
  link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff
  inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute 
test_bond
 valid_lft 353sec preferred_lft 353sec
  inet6 fe80::ff:feb3:b522/64 scope link 
 valid_lft forever preferred_lft forever

  
  
+++
  Bond interface, ipv4 automatic mode and ipv6 manual mode

  root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond 
  [connection]
  id=test_bond
  uuid=3efb153a-a6e4-48fb-aa04-f0b8cb549bab
  type=bond
  interface-name=test_bond
  permissions=
  timestamp=1537943300

  [ethernet]
  mac-address-blacklist=

  [bond]
  downdelay=0
  fail_over_mac=none
  miimon=100
  mode=active-backup
  num_grat_arp=0
  primary_reselect=always
  updelay=0

  [ipv4]
  dns-search=
  method=auto

  [ipv6]
  addr-gen-mode=stable-privacy
  address1=fe81::32a5:bc5f:287f:8db8/64
  dns-search=
  method=manual

  No automatic ip assigned to ipv4 and no requests to dhcp server seen in 
/var/log/syslog
  root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond
  29: test_bond:  mtu 1500 qdisc 
noqueue state UP group default qlen 1000
  link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff
  inet6 fe81::32a5:bc5f:287f:8db8/64 scope link noprefixroute 
 valid_lft forever preferred_lft forever

  
  ==> Correct LP-Package need to be assigned...!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1794478/+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 1821091] Re: [FFe] Qt 5.12.2 update

[Rik Mills]

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  [FFe] Qt 5.12.2 update

Status in qtbase-opensource-src package in Ubuntu:
  Fix Committed

Bug description:
  Dear Release Team,

  I would like to update Qt in disco from 5.11.3 to 5.12.2.

  The reasons are the following:

  1) The 5.11 branch is EOL and no longer receiving any fixes. The 5.12
  branch is LTS and will be supported for three years.

  2) New versions of Plasma are going to require Qt 5.12, and the
  Kubuntu team would like to be able to package them in their backports
  PPA for disco.

  3) In Qt 5.12, the memory usage of the QML Engine is reduced by up to
  30 %.

  4) Finally we will be able to sync all packages from Debian. I have
  managed to drop the delta in qtbase, qtmultimedia and qtwebkit.

  Why we haven’t packaged it early: we did not want to package 5.12.1
  because it had some known bugs. And 5.12.2 was released upstream later
  than it was originally planned.

  Changelog: https://wiki.qt.io/New_Features_in_Qt_5.12

  The packages are being prepared in https://launchpad.net/~ci-train-
  ppa-service/+archive/ubuntu/3680/+packages, but these will be replaced
  with syncs from Debian when qtbase and qtdeclarative get accepted from
  Debian’s NEW queue.

  This transition will require syncs of all Qt packages, and no-change
  rebuilds of packages that build-depend on qtbase5-private-dev or
  qtdeclarative5-private-dev.

  All Qt modules are in universe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1821091/+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 1822587] Re: wifi service stops occasionally.

[Sebastien Bacher]

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

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

Title:
  wifi service stops occasionally.

Status in network-manager package in Ubuntu:
  New

Bug description:
  wifi service stops occasionally: ('?' in the top right icon). an old
  bug that disappeared a few updates back, back now after yesterday's
  update.  'service network-manager restart' gets it working again.
  annoying as i thought it gone.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: network-manager 1.12.4-1ubuntu1.2
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  1 14:50:50 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-07-30 (975 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.8.1 dev wlp3s0f0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp3s0f0 scope link metric 1000 
   192.168.8.0/24 dev wlp3s0f0 proto kernel scope link src 192.168.8.100 metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to cosmic on 2018-12-06 (116 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTIONCON-UUID  CON-PATH   

   wlp3s0f0   wifi  connected 
/org/freedesktop/NetworkManager/Devices/3  HUAWEI-B315-D7CD  
01a82e09-44b7-4509-af07-4bf05f76759a  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   1C:AF:05:F7:CE:56  btdisconnected  
/org/freedesktop/NetworkManager/Devices/4  ---- 
   -- 
   enp2s0f1   ethernet  unavailable   
/org/freedesktop/NetworkManager/Devices/2  ---- 
   -- 
   lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/1  ---- 
   --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN 
   running  1.12.4   connected  started  full  enabled enabled  
enabled  enabled  disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1822587/+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 1642514] Re: sched: Match-all classifier is missing in xenial

[Stefan Bader]

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

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

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

** Changed in: iproute2 (Ubuntu Xenial)
 Assignee: (unassigned) => Stefan Bader (smb)

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

Title:
  sched: Match-all classifier is missing in xenial

Status in iproute2 package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in iproute2 source package in Xenial:
  In Progress
Status in linux source package in Xenial:
  Fix Released

Bug description:
  This is implemented in linux v4.8 by the following upstream patch:
  bf3994d2ed31 ("net/sched: introduce Match-all classifier")

  
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=bf3994d2ed31

  The backport is straightforward. It's useful in combination with
  clsact qdisc (see bug #1642510).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1642514/+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 1823110] Re: Screen not resized when rotating 90*

[Brian Murray]

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

** Tags added: regression-release

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

Title:
  Screen not resized when rotating 90*

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running 19.04 beta on a Microsoft Surface Pro 3.
  Screen resolution 2160x1440 works in normal landscape mode (Docked mode) 
however if I rotate the device 90* clockwise or counter-clockwise, the screen 
resolution doesn't change to 1440x2160. The screen actually rotates however it 
hasn't flipped the dimensions to fit.
  This was previously working on Ubuntu 18.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1823110/+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 1492560] Re: package libopenal-data 1:1.14-4ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurati

[Bret Curtis]

Trusty is now end-of-life, later releases of openal-soft don't have this
issue.

** Changed in: openal-soft (Ubuntu)
   Status: New => Invalid

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

Title:
  package libopenal-data 1:1.14-4ubuntu1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in openal-soft package in Ubuntu:
  Invalid

Bug description:
  firefox crashes frequently

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libopenal-data 1:1.14-4ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25
  Uname: Linux 3.13.0-63-generic i686
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: i386
  Date: Sat Sep  5 12:23:11 2015
  Dependencies:
   
  DuplicateSignature: package:libopenal-data:1:1.14-4ubuntu1:package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2015-03-24 (164 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.4
   apt  1.0.1ubuntu2.10
  SourcePackage: openal-soft
  Title: package libopenal-data 1:1.14-4ubuntu1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.openal.alsoft.conf: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openal-soft/+bug/1492560/+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 1819969] Re: gdb-multiarch does not include RISC-V architecture

[Brian Murray]

** Tags removed: rls-dd-incoming

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

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

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

Title:
  gdb-multiarch does not include RISC-V architecture

Status in gdb package in Ubuntu:
  Triaged

Bug description:
  This issue was recently fixed in Debian, but seems to have not been
  pulled into Ubuntu: https://salsa.debian.org/gdb-
  team/gdb/commit/e59e4e54af0fbe9086c40ab80a1000d5c50c7175

  Description:  Ubuntu Disco Dingo (development branch)
  Release:  19.04

  gdb-multiarch:
Installed: 8.2.90-0ubuntu1
Candidate: 8.2.90-0ubuntu1
Version table:
   *** 8.2.90-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/universe amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1819969/+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 1822730] Re: Disco server install fails to boot using encrypted partitions

[Launchpad Bug Tracker]

This bug was fixed in the package busybox - 1:1.27.2-2ubuntu7

---
busybox (1:1.27.2-2ubuntu7) disco; urgency=medium

  * Enable fold in busybox-initramfs, as it appears that
initrmafs-tools-core now uses that variant of busybox, instead of
busybox-static or busybox. Also, potentially cryptsetup dependencies
on busybox-static|busybox are now meaningless. LP: #1822730

 -- Dimitri John Ledkov   Thu, 04 Apr 2019 12:50:59
+0100

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

Title:
  Disco server install fails to boot using encrypted partitions

Status in busybox package in Ubuntu:
  Fix Released

Bug description:
  Performing a fresh Disco (daily build from 2019-03-31) server install
  with / mounted from LVM over dm-crypt (over mdadm), the boot fails
  just after asking the encrypted partition passphrase with the
  following error:

  /scripts/local-top/cryptroot: line 1: fold: not found

  Building a custom busybox package with "fold" binary enabled for
  busybox-initramfs and busybox-static configs fixes the issue.

  Diff from debian/ directory:

  diff --git a/config/pkg/initramfs b/config/pkg/initramfs
  index 2ef98e5..5725daf 100644
  --- a/config/pkg/initramfs
  +++ b/config/pkg/initramfs
  @@ -228,7 +228,7 @@ CONFIG_EXPR=y
   CONFIG_EXPR_MATH_SUPPORT_64=y
   # CONFIG_FACTOR is not set
   CONFIG_FALSE=y
  -# CONFIG_FOLD is not set
  +CONFIG_FOLD=y
   # CONFIG_FSYNC is not set
   # CONFIG_HEAD is not set
   # CONFIG_FEATURE_FANCY_HEAD is not set
  diff --git a/config/pkg/udeb b/config/pkg/udeb
  index 7538ae5..f9a6d4c 100644
  --- a/config/pkg/udeb
  +++ b/config/pkg/udeb
  @@ -228,7 +228,7 @@ CONFIG_EXPR=y
   CONFIG_EXPR_MATH_SUPPORT_64=y
   # CONFIG_FACTOR is not set
   CONFIG_FALSE=y
  -# CONFIG_FOLD is not set
  +CONFIG_FOLD=y
   # CONFIG_FSYNC is not set
   CONFIG_HEAD=y
   CONFIG_FEATURE_FANCY_HEAD=y

  It might be enough to add "fold" to the initramfs variant only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1822730/+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 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (using "foreign grub")

[Derk Willem te Bokkel]

** Summary changed:

- lightdm login screen briefly appears and then blanks out on Intel(R) 
Core(TM)2 Duo CPU T5870 - failure to load i915 kernel module
+ lightdm login screen briefly appears and then blanks out on Intel(R) 
Core(TM)2 Duo CPU T5870 (using "foreign grub")

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

Title:
  lightdm login screen briefly appears and then blanks out on Intel(R)
  Core(TM)2 Duo CPU T5870 (using "foreign grub")

Status in lightdm package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  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/lightdm/+bug/1821609/+subscriptions

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

[Touch-packages] [Bug 1822730] Re: Disco server install fails to boot using encrypted partitions

[Arthur Loiret]

Thanks!

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

Title:
  Disco server install fails to boot using encrypted partitions

Status in busybox package in Ubuntu:
  Fix Released

Bug description:
  Performing a fresh Disco (daily build from 2019-03-31) server install
  with / mounted from LVM over dm-crypt (over mdadm), the boot fails
  just after asking the encrypted partition passphrase with the
  following error:

  /scripts/local-top/cryptroot: line 1: fold: not found

  Building a custom busybox package with "fold" binary enabled for
  busybox-initramfs and busybox-static configs fixes the issue.

  Diff from debian/ directory:

  diff --git a/config/pkg/initramfs b/config/pkg/initramfs
  index 2ef98e5..5725daf 100644
  --- a/config/pkg/initramfs
  +++ b/config/pkg/initramfs
  @@ -228,7 +228,7 @@ CONFIG_EXPR=y
   CONFIG_EXPR_MATH_SUPPORT_64=y
   # CONFIG_FACTOR is not set
   CONFIG_FALSE=y
  -# CONFIG_FOLD is not set
  +CONFIG_FOLD=y
   # CONFIG_FSYNC is not set
   # CONFIG_HEAD is not set
   # CONFIG_FEATURE_FANCY_HEAD is not set
  diff --git a/config/pkg/udeb b/config/pkg/udeb
  index 7538ae5..f9a6d4c 100644
  --- a/config/pkg/udeb
  +++ b/config/pkg/udeb
  @@ -228,7 +228,7 @@ CONFIG_EXPR=y
   CONFIG_EXPR_MATH_SUPPORT_64=y
   # CONFIG_FACTOR is not set
   CONFIG_FALSE=y
  -# CONFIG_FOLD is not set
  +CONFIG_FOLD=y
   # CONFIG_FSYNC is not set
   CONFIG_HEAD=y
   CONFIG_FEATURE_FANCY_HEAD=y

  It might be enough to add "fold" to the initramfs variant only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1822730/+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 1823076] Re: Intel NUC (8I3BEH1) wakes up immediately after suspend if Bluetooth is still enabled

[b]

I believe this issue was due to "legacy suspend" rather than "modern
suspend" selected in UEFI. After a couple suspends I am no longer seeing
the problem, but will reopen if it happens again.

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Intel NUC (8I3BEH1) wakes up immediately after suspend if Bluetooth is
  still enabled

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  After replacing my USB mouse with a BT mouse, I noticed my machine
  would no longer suspend without immediately waking up. i.e. I suspend
  and see the light go into the slow fade in and out for one cycle and
  then goes solid and the display wakes up again. If I disable BT (via
  blueman applet) suspend works fine.

  I've fixed this by shutting down the BT service before suspend, and
  starting it back up on wake, as indicated here:
  https://askubuntu.com/questions/797590/ubuntu-wakes-up-immediately-
  after-suspend

  Perhaps this script should be included in blueZ as suspend issues seem
  very hard to debug and the immediate wake after suspend could be
  caused many any number of things.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1 [modified: 
lib/systemd/system/bluetooth.service]
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Apr  3 13:16:14 2019
  InstallationDate: Installed on 2019-02-09 (53 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Intel(R) Client Systems NUC8i3BEH
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/15/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0051.2018.1015.1513
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-304
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0051.2018.1015.1513:bd10/15/2018:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i3BEH
  dmi.product.version: J72753-303
  dmi.sys.vendor: Intel(R) Client Systems
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:BB:60:50:92:5D  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:1912660 acl:106009 sco:0 events:337 errors:0
TX bytes:12331 acl:74 sco:0 commands:204 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1823076/+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 1823110] [NEW] Screen not resized when rotating 90*

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Running 19.04 beta on a Microsoft Surface Pro 3.
Screen resolution 2160x1440 works in normal landscape mode (Docked mode) 
however if I rotate the device 90* clockwise or counter-clockwise, the screen 
resolution doesn't change to 1440x2160. The screen actually rotates however it 
hasn't flipped the dimensions to fit.
This was previously working on Ubuntu 18.10.

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


** Tags: bot-comment disco
-- 
Screen not resized when rotating 90*
https://bugs.launchpad.net/bugs/1823110
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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

[Touch-packages] [Bug 1816753] Re: do-release-upgrade on WSL failed horribly due to grub and others

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 239-7ubuntu10.11

---
systemd (239-7ubuntu10.11) cosmic; urgency=medium

  * virt: detect WSL environment as a container (LP: #1816753)

 -- Balint Reczey   Mon, 25 Mar 2019 11:30:22 +0100

** Changed in: systemd (Ubuntu Cosmic)
   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/1816753

Title:
  do-release-upgrade on WSL failed horribly due to grub and others

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

Bug description:
  [Impact]

   * Package maintainer scripts and services use systemd-detect-virt and 
systemd's virtualization detection to determine the environment they are ran in 
and based on that skip not applicable operations, such as installing grub info 
to the MBR or to the EFI partition in a container. The WSL environment is 
similar to containers in that boot loader and initramfs preparations are not 
useful, but without this change only ad-hoc tests could be implemented in each 
separate package to avoid obsolete actions or failing in trying not applicable 
operations.
   * The fix detects WSL as a container type, called wsl in systemd and as a 
result make packages behave like they would in classic Linuxcontainers.

  [Test Case]

   * Install the fixed systemd package in WSL and observe that it is detected 
as a container:
   $ systemd-detect-virt --container
   wsl
   $

   * Install the fixed systemd package in LXC and observe that it is still 
detected correctly:
   $ systemd-detect-virt --container
   lxc
   $

   * Install the fixed systemd package in a VM or on a bare metal systemd and 
observe that it is still detected correctly:
   $ systemd-detect-virt --container
   none
   $ echo $?
   1

   * Observe the man page of sytemd-detect-virt mentioning wsl.

  [Regression Potential]

   * The changes is virtualization detection could break the detection logic 
but the test cases here cover most of the relevant code paths and the detection 
logic is also exercised in autopkgtests thus causing a regression is unlikely.
   * The changes to the man pages could break the formatting, but a simple 
observation mitigates that risk, too.

  [Original Bug Text]

  Upon reading an Ubuntu page that said it was possible to upgrade my
  Ubuntu-under-Windows 10 install (WSL) from 16.04 LTS just by running
  do-release-upgrade, I excitedly went to my terminal and ran the
  command.

  First it refused to run because system was not fully updated. Fine, I ran:
  sudo apt update
  sudo apt dist-upgrade

  This process completed without any errors. I then ran do-release-
  upgrade again. This time it started okay and got through most of the
  process.

  But then at some point it decided to run grub even though I am running
  Ubuntu under WSL, so presumably grub should not be used. It did
  apparently detect that it wasn't needed, because it asked me if I was
  sure I didn't want to install it on the boot device. I answered yes.
  Then the install proceeded to LXD but soon after came an error related
  to grub.

  After that it went downhill fast with at least 2 other errors.

  Additionally, when the system attempted to roll back the upgrade I got
  an error from a kernel package.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: friendly-recovery 0.2.38ubuntu1
  ProcVersionSignature: Microsoft 4.4.0-17763.253-Microsoft 4.4.35
  Uname: Linux 4.4.0-17763-Microsoft x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Tue Feb 19 23:50:44 2019
  Dmesg: [0.017808]  Microsoft 4.4.0-17763.253-Microsoft 4.4.35
  ErrorMessage: installed friendly-recovery package post-installation script 
subprocess returned error exit status 1
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.8
  SourcePackage: grub2
  Title: package friendly-recovery 0.2.38ubuntu1 failed to install/upgrade: 
installed friendly-recovery package post-installation script subprocess 
returned error exit status 1
  UpgradeStatus: Upgraded to bionic on 2019-02-20 (0 days ago)

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

[Łukasz Zemczak]

The verification of the Stable Release Update for systemd has completed
successfully and the package has now been 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/1816753

Title:
  do-release-upgrade on WSL failed horribly due to grub and others

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

Bug description:
  [Impact]

   * Package maintainer scripts and services use systemd-detect-virt and 
systemd's virtualization detection to determine the environment they are ran in 
and based on that skip not applicable operations, such as installing grub info 
to the MBR or to the EFI partition in a container. The WSL environment is 
similar to containers in that boot loader and initramfs preparations are not 
useful, but without this change only ad-hoc tests could be implemented in each 
separate package to avoid obsolete actions or failing in trying not applicable 
operations.
   * The fix detects WSL as a container type, called wsl in systemd and as a 
result make packages behave like they would in classic Linuxcontainers.

  [Test Case]

   * Install the fixed systemd package in WSL and observe that it is detected 
as a container:
   $ systemd-detect-virt --container
   wsl
   $

   * Install the fixed systemd package in LXC and observe that it is still 
detected correctly:
   $ systemd-detect-virt --container
   lxc
   $

   * Install the fixed systemd package in a VM or on a bare metal systemd and 
observe that it is still detected correctly:
   $ systemd-detect-virt --container
   none
   $ echo $?
   1

   * Observe the man page of sytemd-detect-virt mentioning wsl.

  [Regression Potential]

   * The changes is virtualization detection could break the detection logic 
but the test cases here cover most of the relevant code paths and the detection 
logic is also exercised in autopkgtests thus causing a regression is unlikely.
   * The changes to the man pages could break the formatting, but a simple 
observation mitigates that risk, too.

  [Original Bug Text]

  Upon reading an Ubuntu page that said it was possible to upgrade my
  Ubuntu-under-Windows 10 install (WSL) from 16.04 LTS just by running
  do-release-upgrade, I excitedly went to my terminal and ran the
  command.

  First it refused to run because system was not fully updated. Fine, I ran:
  sudo apt update
  sudo apt dist-upgrade

  This process completed without any errors. I then ran do-release-
  upgrade again. This time it started okay and got through most of the
  process.

  But then at some point it decided to run grub even though I am running
  Ubuntu under WSL, so presumably grub should not be used. It did
  apparently detect that it wasn't needed, because it asked me if I was
  sure I didn't want to install it on the boot device. I answered yes.
  Then the install proceeded to LXD but soon after came an error related
  to grub.

  After that it went downhill fast with at least 2 other errors.

  Additionally, when the system attempted to roll back the upgrade I got
  an error from a kernel package.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: friendly-recovery 0.2.38ubuntu1
  ProcVersionSignature: Microsoft 4.4.0-17763.253-Microsoft 4.4.35
  Uname: Linux 4.4.0-17763-Microsoft x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Tue Feb 19 23:50:44 2019
  Dmesg: [0.017808]  Microsoft 4.4.0-17763.253-Microsoft 4.4.35
  ErrorMessage: installed friendly-recovery package post-installation script 
subprocess returned error exit status 1
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.8
  SourcePackage: grub2
  Title: package friendly-recovery 0.2.38ubuntu1 failed to install/upgrade: 
installed friendly-recovery package post-installation script subprocess 
returned error exit status 1
  UpgradeStatus: Upgraded to bionic on 2019-02-20 (0 days ago)

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

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

[Touch-packages] [Bug 1778936] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for systemd has completed
successfully and the package has now been 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/1778936

Title:
  please re-add Support-system-image-read-only-etc.patch

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * core18 systems fail to update hostname
   * this happens due to /etc/hostname actually being a symlink to a file under 
/etc/writable/, adjust hostnamed to take that into account when trying to 
update /etc/hostname

  [Test Case]

   * run a core18 system, check that dhcp acquire hostname is correctly
  updated in /etc/writable/hostname

  [Regression Potential]

   * This is cherrypick of code that has gone missing since xenial.
   * There is no change of behaviour for the classic systems.
   * Currently, core18 systems simply fail to update hostname/machine-info 
files, thus the worst case is that they will still fail to do so.

  [Other Info]
   
   * original bug report

  The 16.04 version of systemd had a patch to support the read-only etc.
  For core18 we will also need this change because core18 is still not
  on a fully writable etc.

  I will attach a debdiff against the current bionic version of systemd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1778936/+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 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (using "foreign grub")

[Derk Willem te Bokkel]

here we have a normal journalctl boot log .. notice the size .. more
entries .. about 1 minute start to finish source the partition that
always works lightdm starts normally plymouth appears on screen etc.

this one was booted by grub installed by zlink4 - on sda6 ..

** Attachment added: "zlink1 / sda1 .. booted from foreign grub .. installed by 
 zl04/sda6"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1821609/+attachment/5252838/+files/zl01-current-04-04fg-zl04boot.log

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

Title:
  lightdm login screen briefly appears and then blanks out on Intel(R)
  Core(TM)2 Duo CPU T5870 (using "foreign grub")

Status in lightdm package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:

[Touch-packages] [Bug 1816753] Re: do-release-upgrade on WSL failed horribly due to grub and others

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 229-4ubuntu21.19

---
systemd (229-4ubuntu21.19) xenial; urgency=medium

  [ Michael Vogt ]
  * d/p/fix-race-daemon-reload-11121.patch:
- backport systemd upstream PR#8803 and PR#11121 to fix race
  when doing systemctl and systemctl daemon-reload at the
  same time LP: #1819728

  [ Balint Reczey ]
  * d/p/virt-detect-WSL-environment-as-a-container.patch:
- virt: detect WSL environment as a container (LP: #1816753)

 -- Michael Vogt   Mon, 25 Mar 2019 16:04:56
+0100

** Changed in: systemd (Ubuntu Xenial)
   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/1816753

Title:
  do-release-upgrade on WSL failed horribly due to grub and others

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

Bug description:
  [Impact]

   * Package maintainer scripts and services use systemd-detect-virt and 
systemd's virtualization detection to determine the environment they are ran in 
and based on that skip not applicable operations, such as installing grub info 
to the MBR or to the EFI partition in a container. The WSL environment is 
similar to containers in that boot loader and initramfs preparations are not 
useful, but without this change only ad-hoc tests could be implemented in each 
separate package to avoid obsolete actions or failing in trying not applicable 
operations.
   * The fix detects WSL as a container type, called wsl in systemd and as a 
result make packages behave like they would in classic Linuxcontainers.

  [Test Case]

   * Install the fixed systemd package in WSL and observe that it is detected 
as a container:
   $ systemd-detect-virt --container
   wsl
   $

   * Install the fixed systemd package in LXC and observe that it is still 
detected correctly:
   $ systemd-detect-virt --container
   lxc
   $

   * Install the fixed systemd package in a VM or on a bare metal systemd and 
observe that it is still detected correctly:
   $ systemd-detect-virt --container
   none
   $ echo $?
   1

   * Observe the man page of sytemd-detect-virt mentioning wsl.

  [Regression Potential]

   * The changes is virtualization detection could break the detection logic 
but the test cases here cover most of the relevant code paths and the detection 
logic is also exercised in autopkgtests thus causing a regression is unlikely.
   * The changes to the man pages could break the formatting, but a simple 
observation mitigates that risk, too.

  [Original Bug Text]

  Upon reading an Ubuntu page that said it was possible to upgrade my
  Ubuntu-under-Windows 10 install (WSL) from 16.04 LTS just by running
  do-release-upgrade, I excitedly went to my terminal and ran the
  command.

  First it refused to run because system was not fully updated. Fine, I ran:
  sudo apt update
  sudo apt dist-upgrade

  This process completed without any errors. I then ran do-release-
  upgrade again. This time it started okay and got through most of the
  process.

  But then at some point it decided to run grub even though I am running
  Ubuntu under WSL, so presumably grub should not be used. It did
  apparently detect that it wasn't needed, because it asked me if I was
  sure I didn't want to install it on the boot device. I answered yes.
  Then the install proceeded to LXD but soon after came an error related
  to grub.

  After that it went downhill fast with at least 2 other errors.

  Additionally, when the system attempted to roll back the upgrade I got
  an error from a kernel package.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: friendly-recovery 0.2.38ubuntu1
  ProcVersionSignature: Microsoft 4.4.0-17763.253-Microsoft 4.4.35
  Uname: Linux 4.4.0-17763-Microsoft x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Tue Feb 19 23:50:44 2019
  Dmesg: [0.017808]  Microsoft 4.4.0-17763.253-Microsoft 4.4.35
  ErrorMessage: installed friendly-recovery package post-installation script 
subprocess returned error exit status 1
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.8
  SourcePackage: grub2
  Title: package friendly-recovery 0.2.38ubuntu1 failed to install/upgrade: 
installed friendly-recovery package post-installation script subprocess 
returned error exit status 1
  UpgradeStatus: Upgraded to bionic on 2019-02-20 (0 days ago)

To manage notifications about this bug go to:

[Touch-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (using "foreign grub")

[Derk Willem te Bokkel]

here is the journalctl boot log for sda6 /zlink4 booted by it's own
install of grub (self grub)

(it was reinstalled for this purpose  .. to show it works .. however
plymouth does not show on the screen at all on boot but does on shutdown
)

now one change is addition of a vt.handoff=1 to the end of the grub entry 
(originally a $vt_handoff)   i'll shortly revert this and regenerate this log 
again.. 

size is about same as zlink1 version also about 1 minute long

note every problem boot has a much shorter journalctl boot log..why?

some stuff is not getting done .. only because the source of the grub-
install has changed and the controlling partition grub.cfg used instead
..   ??

these are generic auto-generated by update-grub .. so why the different
behaviours





** Attachment added: "zlink4 / sda6 boot log -- self grub boot"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1821609/+attachment/5252840/+files/zl04-apr-4-sgrub-currentboot.log

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

Title:
  lightdm login screen briefly appears and then blanks out on Intel(R)
  Core(TM)2 Duo CPU T5870 (using "foreign grub")

Status in lightdm package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 

[Touch-packages] [Bug 1778936] Re: please re-add Support-system-image-read-only-etc.patch

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 237-3ubuntu10.17

---
systemd (237-3ubuntu10.17) bionic; urgency=medium

  [ Michael Vogt ]
  * d/p/Support-system-image-read-only-etc.patch:
- re-add support for /etc/writable for core18 (LP: #1778936)
  * d/p/fix-race-daemon-reload-8803.patch:
- backport systemd upstream PR#8803 and PR#11121 to fix race
  when doing systemctl and systemctl daemon-reload at the
  same time LP: #1819728

  [ Balint Reczey ]
   * d/p/virt-detect-WSL-environment-as-a-container.patch:
 - virt: detect WSL environment as a container (LP: #1816753)

 -- Michael Vogt   Mon, 18 Mar 2019 08:40:44
+0100

** Changed in: systemd (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/1778936

Title:
  please re-add Support-system-image-read-only-etc.patch

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

Bug description:
  [Impact]

   * core18 systems fail to update hostname
   * this happens due to /etc/hostname actually being a symlink to a file under 
/etc/writable/, adjust hostnamed to take that into account when trying to 
update /etc/hostname

  [Test Case]

   * run a core18 system, check that dhcp acquire hostname is correctly
  updated in /etc/writable/hostname

  [Regression Potential]

   * This is cherrypick of code that has gone missing since xenial.
   * There is no change of behaviour for the classic systems.
   * Currently, core18 systems simply fail to update hostname/machine-info 
files, thus the worst case is that they will still fail to do so.

  [Other Info]
   
   * original bug report

  The 16.04 version of systemd had a patch to support the read-only etc.
  For core18 we will also need this change because core18 is still not
  on a fully writable etc.

  I will attach a debdiff against the current bionic version of systemd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1778936/+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 1823202] Re: HOME points to something not owned by user in sudo

[Seth Arnold]

This appears to be the missing context:

╭─rkm@Khadas ~  
╰─➤  sudo -s
[oh-my-zsh] Insecure completion-dependent directories detected:
drwxr-xr-x  11 rkm rkm  4096 Mar 30 19:19 /home/rkm/.oh-my-zsh
drwxr-xr-x 266 rkm rkm 12288 Mar 30 19:19 /home/rkm/.oh-my-zsh/plugins
drwxr-xr-x   2 rkm rkm  4096 Mar 30 19:19 /home/rkm/.oh-my-zsh/plugins/git

[oh-my-zsh] For safety, we will not load completions from these directories 
until
[oh-my-zsh] you fix their permissions and ownership and restart zsh.
[oh-my-zsh] See the above list for directories with group or other writability.

[oh-my-zsh] To fix your permissions you can do so by disabling
[oh-my-zsh] the write permission of "group" and "others" and making sure that 
the
[oh-my-zsh] owner of these directories is either root or your current user.
[oh-my-zsh] The following command may help:
[oh-my-zsh] compaudit | xargs chmod g-w,o-w

[oh-my-zsh] If the above didn't help or you want to skip the verification of
[oh-my-zsh] insecure directories you can set the variable ZSH_DISABLE_COMPFIX to
[oh-my-zsh] "true" before oh-my-zsh is sourced in your zshrc file.

from http://dpaste.com/1NQ618Y

** Information type changed from Private Security to Public

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

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

Title:
  HOME points to something not owned by user in sudo

Status in sudo package in Ubuntu:
  New
Status in zsh package in Ubuntu:
  New

Bug description:
   You shouldn't use interactive shell, or any program with
  executable configuration, while your HOME points to something not
  owned by your user. That's the big issue and it's with sudo, not zsh,
  not omz, not any other shell or application you launch.  You
  can go shout "you are doing security wrong" at Ubuntu. Good luck.

  ╭─rkm@Khadas ~  
  ╰─➤  id rkm && getent passwd rkm
  uid=1001(rkm) gid=1001(rkm) 
groups=1001(rkm),0(root),4(adm),5(tty),6(disk),20(dialout),21(fax),24(cdrom),25(floppy),26(tape),27(sudo),29(audio),30(dip),44(video),46(plugdev),50(staff),60(games),100(users),101(systemd-journal),104(input),108(netdev),112(bluetooth),113(lpadmin),121(pulse-access)
  rkm:x:1001:1001:Ryan McKee:/home/rkm:/usr/bin/zsh

  ╭─rkm@Khadas ~  
  ╰─➤  sudo /usr/bin/env  1 
↵
  LC_MESSAGES=en_US.UTF-8
  LANG=en_US.UTF-8
  LANGUAGE=en_US.UTF-8
  TERM=xterm-256color
  XAUTHORITY=/home/rkm/.Xauthority
  COLORTERM=truecolor
  DISPLAY=:0.0
  PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin
  HOME=/home/rkm
  LC_CTYPE=en_US.UTF-8
  
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.wim=01;31:*.swm=01;31:*.dwm=01;31:*.esd=01;31:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:
  MAIL=/var/mail/root
  LOGNAME=root
  USER=root
  USERNAME=root
  SHELL=/bin/bash
  SUDO_COMMAND=/usr/bin/env

  
  SUDO_USER=rkm
  SUDO_UID=1001
  SUDO_GID=1001
  ╭─rkm@Khadas ~  
  ╰─➤  

   CyberManifest: sudo is a package. Also, once filed, add
  zsh to the bug since it could be a bug in zsh's package as well.

   Not necessarily zsh itself, but the packaging.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: sudo 1.8.21p2-3ubuntu1
  Uname: Linux 4.9.40 aarch64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: arm64
  CurrentDesktop: XFCE
  Date: Thu Apr  4 11:07:42 2019
  SourcePackage: sudo
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   /etc/sudoers: parsed OK
   

[Touch-packages] [Bug 1821491] Re: DNS lookup fails for local hosts

[Steve Langasek]

Ok, so you have no other DNS servers configured.  So 192.168.2.1 is the
DNS server that's being used, but systemd-resolved doesn't like
something about either the request or the response and is not forwarding
it.

I note that you also say that this only fails for *local* hosts; i.e. if
I pay more attention, I see that the name that is being resolved has no
domain name at all.  So it looks to me like systemd-resolved is unhappy
with this in particular and this is why it's not giving you results.

Reassigning to systemd.

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

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

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

Title:
  DNS lookup fails for local hosts

Status in systemd package in Ubuntu:
  New

Bug description:
  Mint 19 (Ubuntu Bionic) 
  Laptop so Using NetworkManager, and connecting wirelessly to LAN
  Upgraded from Mint 18.3 so using resolvconf...

  Versions:
  network-manager: 1.10.6-2ubuntu1.1
  resolvconf: 1.79ubuntu10.18.04.3 or 1.79ubuntu10.18.04.2
  systemd: 237-3ubuntu10.15

  dns is specified in NetworkMananager as 192.168.2.1
  the dns is a router, and has static ips assigned to certain hosts on my lan...

  $cat resolv.conf
  nameserver 127.0.0.53
  search phs
  options edns0

  $ nslookup phspi05
  Server:   127.0.0.53
  Address:  127.0.0.53#53

  ** server can't find phspi05: SERVFAIL

  If I explicity specify the dns:

  $ nslookup phspi05 192.168.2.1
  Server:   192.168.2.1
  Address:  192.168.2.1#53

  Non-authoritative answer:
  Name: phspi05
  Address: 192.168.2.35

  I get the correct ip address...

  Same with dig...

  I would expect that the nameserver set in network-manager would be
  used

  From tail of $ systemd-resolve --status

  Link 2 (wlp2s0)
Current Scopes: DNS
 LLMNR setting: yes
  MulticastDNS setting: no
DNSSEC setting: no
  DNSSEC supported: no
   DNS Servers: 192.168.2.1
DNS Domain: phs

  So the dns address had been picked up from NetworkManager, but
  apparently is not being used...

  Thought it might be related to this bug:
  https://bugs.launchpad.net/ubuntu/bionic/+source/resolvconf/+bug/1817903

  So installed the proposed fix, but no change. I also tried removing
  package resolvconf, again no change...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821491/+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 1823076] Re: Intel NUC (8I3BEH1) wakes up immediately after suspend if Bluetooth is still enabled

[b]

Scratch that; the first couple suspend operations did work, and then
they stopped again. I'll do more testing and report back. I did rule out
mouse movement by using the hardware power switch on the mouse.

** Changed in: bluez (Ubuntu)
   Status: Invalid => Incomplete

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

Title:
  Intel NUC (8I3BEH1) wakes up immediately after suspend if Bluetooth is
  still enabled

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  After replacing my USB mouse with a BT mouse, I noticed my machine
  would no longer suspend without immediately waking up. i.e. I suspend
  and see the light go into the slow fade in and out for one cycle and
  then goes solid and the display wakes up again. If I disable BT (via
  blueman applet) suspend works fine.

  I've fixed this by shutting down the BT service before suspend, and
  starting it back up on wake, as indicated here:
  https://askubuntu.com/questions/797590/ubuntu-wakes-up-immediately-
  after-suspend

  Perhaps this script should be included in blueZ as suspend issues seem
  very hard to debug and the immediate wake after suspend could be
  caused many any number of things.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1 [modified: 
lib/systemd/system/bluetooth.service]
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Apr  3 13:16:14 2019
  InstallationDate: Installed on 2019-02-09 (53 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Intel(R) Client Systems NUC8i3BEH
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/15/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0051.2018.1015.1513
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-304
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0051.2018.1015.1513:bd10/15/2018:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i3BEH
  dmi.product.version: J72753-303
  dmi.sys.vendor: Intel(R) Client Systems
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:BB:60:50:92:5D  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:1912660 acl:106009 sco:0 events:337 errors:0
TX bytes:12331 acl:74 sco:0 commands:204 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1823076/+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 1822184] Re: clear_console locks up video when X is running and you log out from a plain text console

[Quesar]

Thanks!  This also affects 18.04 and will need to be fixed there too
please.

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

Title:
  clear_console locks up video when X is running and you log out from a
  plain text console

Status in X.Org X server:
  New
Status in bash package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Confirmed
Status in xorg package in Debian:
  New
Status in xorg-server package in Debian:
  Confirmed

Bug description:
  References:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810660
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866898

  
  If X is running and you switch to a plain text console (ie ctrl-alt-f3), log 
in as a regular user, and then log out, the display switches back to the 
graphical login screen and locks up.  The system is still functioning (can ssh 
in, etc) but the video output is frozen.

  The underlying cause is:
  https://gitlab.freedesktop.org/xorg/xserver/issues/492

  However, the problem can at least be worked around by making
  clear_console switch to tty 6 and back instead of switching to 1 and
  back.  This patch corrects the problem:

  
  --- bash-4.4.18.orig/debian/clear_console.c 2019-03-28 12:09:02.415907787 
-0400
  +++ bash-4.4.18/debian/clear_console.c  2019-03-28 12:08:11.984366858 -0400
  @@ -205,7 +205,7 @@
   #if defined(__linux__)
 num = vtstat.v_active;
   #endif
  -  tmp_num = (num == 1 ? 2 : 1);
  +  tmp_num = (num == 6 ? 5 : 6);
   
 /* switch vt to clear the scrollback buffer */
 if (ioctl(fd, VT_ACTIVATE, tmp_num))

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1822184/+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 1819728] Re: Please backport "fix race between daemon-reload and other commands #8803" to 16.04 (for UC16) and 18.04 (for UC18)

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 237-3ubuntu10.17

---
systemd (237-3ubuntu10.17) bionic; urgency=medium

  [ Michael Vogt ]
  * d/p/Support-system-image-read-only-etc.patch:
- re-add support for /etc/writable for core18 (LP: #1778936)
  * d/p/fix-race-daemon-reload-8803.patch:
- backport systemd upstream PR#8803 and PR#11121 to fix race
  when doing systemctl and systemctl daemon-reload at the
  same time LP: #1819728

  [ Balint Reczey ]
   * d/p/virt-detect-WSL-environment-as-a-container.patch:
 - virt: detect WSL environment as a container (LP: #1816753)

 -- Michael Vogt   Mon, 18 Mar 2019 08:40:44
+0100

** Changed in: systemd (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/1819728

Title:
  Please backport "fix race between daemon-reload and other commands
  #8803" to 16.04 (for UC16) and 18.04 (for UC18)

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

Bug description:
  [Impact]
  On Ubuntu Core we recently hit the a race in daemon-reload and systemctl 
twice. This race is fixed in systemd upstream: "fix race between daemon-reload 
and other commands #8803" and a subsequent fix in "PR#11121".

  Note that this is a general problem in systemd with daemon-reload and
  systemctl commands, we just happen to hit it more often on Ubuntu Core
  but the test-case below explodes just fine on a normal Ubuntu release
  like 16.04 or 18.04 (not on 18.10+ as its fixed there).

  [TEST CASE]
  To reproduce its enough to run:

  for i in $(seq 50); do
    systemctl daemon-reload &
    systemctl start ssh &
  done

  This will result in "systemctl start ssh" hanging in ppoll. With the
  patch applied the hangs go away.

  [REGRESSION POTENTIAL]
  Medium/High, this change is already in the systemd upstream and in use disco 
and later but the backport required some manual resolving of conflicts the code 
because changed between 229,237 and the fixed code in 240. Its also
  not fully clear if the fix relies on the new systemd "coldplug" functionality 
that was added in more recent git revisions.

  The upstream fix is https://github.com/systemd/systemd/pull/8803 and
  https://github.com/systemd/systemd/pull/11121

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1819728/+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 1816753] Re: do-release-upgrade on WSL failed horribly due to grub and others

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 237-3ubuntu10.17

---
systemd (237-3ubuntu10.17) bionic; urgency=medium

  [ Michael Vogt ]
  * d/p/Support-system-image-read-only-etc.patch:
- re-add support for /etc/writable for core18 (LP: #1778936)
  * d/p/fix-race-daemon-reload-8803.patch:
- backport systemd upstream PR#8803 and PR#11121 to fix race
  when doing systemctl and systemctl daemon-reload at the
  same time LP: #1819728

  [ Balint Reczey ]
   * d/p/virt-detect-WSL-environment-as-a-container.patch:
 - virt: detect WSL environment as a container (LP: #1816753)

 -- Michael Vogt   Mon, 18 Mar 2019 08:40:44
+0100

** Changed in: systemd (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/1816753

Title:
  do-release-upgrade on WSL failed horribly due to grub and others

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

Bug description:
  [Impact]

   * Package maintainer scripts and services use systemd-detect-virt and 
systemd's virtualization detection to determine the environment they are ran in 
and based on that skip not applicable operations, such as installing grub info 
to the MBR or to the EFI partition in a container. The WSL environment is 
similar to containers in that boot loader and initramfs preparations are not 
useful, but without this change only ad-hoc tests could be implemented in each 
separate package to avoid obsolete actions or failing in trying not applicable 
operations.
   * The fix detects WSL as a container type, called wsl in systemd and as a 
result make packages behave like they would in classic Linuxcontainers.

  [Test Case]

   * Install the fixed systemd package in WSL and observe that it is detected 
as a container:
   $ systemd-detect-virt --container
   wsl
   $

   * Install the fixed systemd package in LXC and observe that it is still 
detected correctly:
   $ systemd-detect-virt --container
   lxc
   $

   * Install the fixed systemd package in a VM or on a bare metal systemd and 
observe that it is still detected correctly:
   $ systemd-detect-virt --container
   none
   $ echo $?
   1

   * Observe the man page of sytemd-detect-virt mentioning wsl.

  [Regression Potential]

   * The changes is virtualization detection could break the detection logic 
but the test cases here cover most of the relevant code paths and the detection 
logic is also exercised in autopkgtests thus causing a regression is unlikely.
   * The changes to the man pages could break the formatting, but a simple 
observation mitigates that risk, too.

  [Original Bug Text]

  Upon reading an Ubuntu page that said it was possible to upgrade my
  Ubuntu-under-Windows 10 install (WSL) from 16.04 LTS just by running
  do-release-upgrade, I excitedly went to my terminal and ran the
  command.

  First it refused to run because system was not fully updated. Fine, I ran:
  sudo apt update
  sudo apt dist-upgrade

  This process completed without any errors. I then ran do-release-
  upgrade again. This time it started okay and got through most of the
  process.

  But then at some point it decided to run grub even though I am running
  Ubuntu under WSL, so presumably grub should not be used. It did
  apparently detect that it wasn't needed, because it asked me if I was
  sure I didn't want to install it on the boot device. I answered yes.
  Then the install proceeded to LXD but soon after came an error related
  to grub.

  After that it went downhill fast with at least 2 other errors.

  Additionally, when the system attempted to roll back the upgrade I got
  an error from a kernel package.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: friendly-recovery 0.2.38ubuntu1
  ProcVersionSignature: Microsoft 4.4.0-17763.253-Microsoft 4.4.35
  Uname: Linux 4.4.0-17763-Microsoft x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Tue Feb 19 23:50:44 2019
  Dmesg: [0.017808]  Microsoft 4.4.0-17763.253-Microsoft 4.4.35
  ErrorMessage: installed friendly-recovery package post-installation script 
subprocess returned error exit status 1
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.8
  SourcePackage: grub2
  Title: package friendly-recovery 0.2.38ubuntu1 failed to install/upgrade: 
installed friendly-recovery package post-installation script subprocess 
returned error exit status 1
  UpgradeStatus: Upgraded to 

[Touch-packages] [Bug 1823070] Re: unattended-upgrades should tell the user (via motd) when security updates are held back

[Balint Reczey]

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Confirmed

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

Title:
  unattended-upgrades should tell the user (via motd) when security
  updates are held back

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  Currently we have the following pieces as part of the default UX on
  Ubuntu 18.04 and later:

   1) unattended-upgrades automatically installs security updates daily by 
default
   2) the motd reports the number of available updates, including security 
updates.

  A user who knows about 1) also knows that a non-zero number of pending
  security updates listed in 2) is nothing to worry about.

  However, unattended-upgrades will also cleverly detect when a security
  update cannot safely be installed non-interactively due to conffile
  changes on the system.

  In this case, unattended-upgrades should also inform the user via the
  motd that these updates are not being installed.  Otherwise, there's
  nothing to tell the user that the non-zero count of available security
  updates in motd is a *problem*.

  Suggested wording:

   N security updates will not be automatically installed due to local changes.
   See /var/log/foo for details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1823070/+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 1819728] Re: Please backport "fix race between daemon-reload and other commands #8803" to 16.04 (for UC16) and 18.04 (for UC18)

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 229-4ubuntu21.19

---
systemd (229-4ubuntu21.19) xenial; urgency=medium

  [ Michael Vogt ]
  * d/p/fix-race-daemon-reload-11121.patch:
- backport systemd upstream PR#8803 and PR#11121 to fix race
  when doing systemctl and systemctl daemon-reload at the
  same time LP: #1819728

  [ Balint Reczey ]
  * d/p/virt-detect-WSL-environment-as-a-container.patch:
- virt: detect WSL environment as a container (LP: #1816753)

 -- Michael Vogt   Mon, 25 Mar 2019 16:04:56
+0100

** Changed in: systemd (Ubuntu Xenial)
   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/1819728

Title:
  Please backport "fix race between daemon-reload and other commands
  #8803" to 16.04 (for UC16) and 18.04 (for UC18)

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

Bug description:
  [Impact]
  On Ubuntu Core we recently hit the a race in daemon-reload and systemctl 
twice. This race is fixed in systemd upstream: "fix race between daemon-reload 
and other commands #8803" and a subsequent fix in "PR#11121".

  Note that this is a general problem in systemd with daemon-reload and
  systemctl commands, we just happen to hit it more often on Ubuntu Core
  but the test-case below explodes just fine on a normal Ubuntu release
  like 16.04 or 18.04 (not on 18.10+ as its fixed there).

  [TEST CASE]
  To reproduce its enough to run:

  for i in $(seq 50); do
    systemctl daemon-reload &
    systemctl start ssh &
  done

  This will result in "systemctl start ssh" hanging in ppoll. With the
  patch applied the hangs go away.

  [REGRESSION POTENTIAL]
  Medium/High, this change is already in the systemd upstream and in use disco 
and later but the backport required some manual resolving of conflicts the code 
because changed between 229,237 and the fixed code in 240. Its also
  not fully clear if the fix relies on the new systemd "coldplug" functionality 
that was added in more recent git revisions.

  The upstream fix is https://github.com/systemd/systemd/pull/8803 and
  https://github.com/systemd/systemd/pull/11121

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

[Łukasz Zemczak]

The verification of the Stable Release Update for systemd has completed
successfully and the package has now been 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/1819728

Title:
  Please backport "fix race between daemon-reload and other commands
  #8803" to 16.04 (for UC16) and 18.04 (for UC18)

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

Bug description:
  [Impact]
  On Ubuntu Core we recently hit the a race in daemon-reload and systemctl 
twice. This race is fixed in systemd upstream: "fix race between daemon-reload 
and other commands #8803" and a subsequent fix in "PR#11121".

  Note that this is a general problem in systemd with daemon-reload and
  systemctl commands, we just happen to hit it more often on Ubuntu Core
  but the test-case below explodes just fine on a normal Ubuntu release
  like 16.04 or 18.04 (not on 18.10+ as its fixed there).

  [TEST CASE]
  To reproduce its enough to run:

  for i in $(seq 50); do
    systemctl daemon-reload &
    systemctl start ssh &
  done

  This will result in "systemctl start ssh" hanging in ppoll. With the
  patch applied the hangs go away.

  [REGRESSION POTENTIAL]
  Medium/High, this change is already in the systemd upstream and in use disco 
and later but the backport required some manual resolving of conflicts the code 
because changed between 229,237 and the fixed code in 240. Its also
  not fully clear if the fix relies on the new systemd "coldplug" functionality 
that was added in more recent git revisions.

  The upstream fix is https://github.com/systemd/systemd/pull/8803 and
  https://github.com/systemd/systemd/pull/11121

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1819728/+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 1823202] Re: HOME points to something not owned by user in sudo

[Seth Arnold]

You should use sudo -i to get a clean root login without your local user
configuration seeping into the shell.

Thanks

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

Title:
  HOME points to something not owned by user in sudo

Status in sudo package in Ubuntu:
  New
Status in zsh package in Ubuntu:
  New

Bug description:
   You shouldn't use interactive shell, or any program with
  executable configuration, while your HOME points to something not
  owned by your user. That's the big issue and it's with sudo, not zsh,
  not omz, not any other shell or application you launch.  You
  can go shout "you are doing security wrong" at Ubuntu. Good luck.

  ╭─rkm@Khadas ~  
  ╰─➤  id rkm && getent passwd rkm
  uid=1001(rkm) gid=1001(rkm) 
groups=1001(rkm),0(root),4(adm),5(tty),6(disk),20(dialout),21(fax),24(cdrom),25(floppy),26(tape),27(sudo),29(audio),30(dip),44(video),46(plugdev),50(staff),60(games),100(users),101(systemd-journal),104(input),108(netdev),112(bluetooth),113(lpadmin),121(pulse-access)
  rkm:x:1001:1001:Ryan McKee:/home/rkm:/usr/bin/zsh

  ╭─rkm@Khadas ~  
  ╰─➤  sudo /usr/bin/env  1 
↵
  LC_MESSAGES=en_US.UTF-8
  LANG=en_US.UTF-8
  LANGUAGE=en_US.UTF-8
  TERM=xterm-256color
  XAUTHORITY=/home/rkm/.Xauthority
  COLORTERM=truecolor
  DISPLAY=:0.0
  PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin
  HOME=/home/rkm
  LC_CTYPE=en_US.UTF-8
  
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.wim=01;31:*.swm=01;31:*.dwm=01;31:*.esd=01;31:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:
  MAIL=/var/mail/root
  LOGNAME=root
  USER=root
  USERNAME=root
  SHELL=/bin/bash
  SUDO_COMMAND=/usr/bin/env

  
  SUDO_USER=rkm
  SUDO_UID=1001
  SUDO_GID=1001
  ╭─rkm@Khadas ~  
  ╰─➤  

   CyberManifest: sudo is a package. Also, once filed, add
  zsh to the bug since it could be a bug in zsh's package as well.

   Not necessarily zsh itself, but the packaging.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: sudo 1.8.21p2-3ubuntu1
  Uname: Linux 4.9.40 aarch64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: arm64
  CurrentDesktop: XFCE
  Date: Thu Apr  4 11:07:42 2019
  SourcePackage: sudo
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   /etc/sudoers: parsed OK
   /etc/sudoers.d/README: parsed OK

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1823202/+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 1823110] Re: Screen not resized when rotating 90*

[Brian Murray]

This may be a duplicate of bug 1822513.

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

Title:
  Screen not resized when rotating 90*

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running 19.04 beta on a Microsoft Surface Pro 3.
  Screen resolution 2160x1440 works in normal landscape mode (Docked mode) 
however if I rotate the device 90* clockwise or counter-clockwise, the screen 
resolution doesn't change to 1440x2160. The screen actually rotates however it 
hasn't flipped the dimensions to fit.
  This was previously working on Ubuntu 18.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1823110/+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 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability

[Till Kamppeter]

The patch got merged upstream.

See

https://gitlab.gnome.org/GNOME/gtk/merge_requests/434

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

Title:
  after upgrade to bionic, printing fails without explanation / logs /
  debuggability

Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in gtk+3.0 source package in Bionic:
  In Progress
Status in gtk+3.0 source package in Cosmic:
  In Progress

Bug description:
  [Impact]

  The problem occurs when the printer's driver package is updated and
  with this the PPD is replaced and one of the default settings of the
  queue is not available any more in the new PPD file. Then the setting
  is prefixed with "Custom." and with this the jobs fail.

  See comment #15 for more info.

  [Test Case]

  - Create a print queue with a PPD.
  - evince an arbitrary PDF file
  - Click the print icon
  - In the print dialog choose the newly created queue and choose some uncommon 
paper size (not custom). Click "Print".
  - Check /var/log/cups/error_log, the page size gets correctly received.
  - Close evince.
  - Stop CUPS, edit the PPD file removing the paper size you have selected for 
your job in the PageSize, PageRegion, PaperDimension, and ImageableArea lines.
  - Start CUPS.
  - Open the same PDF file again with evince, click Print and then select 
"Print" in the print dialog without changing anything.
  - The job fails, in /var/log/cups/error_log you see that the page size is 
prefixed with "Custom.".

  With the fixed package installed the job will print.

  [Regression Potential]

  The change applies only to saved settings of the print dialog not
  matching with any of the settings available in the PPD file. In rare
  cases the fix could fail by mis-understanding the setting and this way
  not being effective. For options which do not support setting custom
  values (the vast majority) the patch should always prevent a job
  failure though.

  [Other Info]

  Complete info about the bug and the fix in comment #15,

  Original bug description:

  I am unable to print to my network-attached printer after upgrade to
  bionic.  ps shows:

  lp   26047  0.0  0.0  91668  5756 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  lp   26050  0.1  0.0  0 0 ?Z15:06   0:00  |   \_ [gs] 

  lp   26048  0.0  0.0  79908  3836 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  root 26049  0.0  0.0  84388  6192 ?S15:06   0:00  \_ 
ipp://HP645106EA160E.local:631/ipp/print 473 vorlon USCIS Form I-9 1 
print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 
number-up=1 MediaType=Stationery noCollate print-scaling=auto 
PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble 
job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4

  Note the un-reaped gs process.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 12 15:07:49 2018
  InstallationDate: Installed on 2010-09-24 (2757 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  Papersize: letter
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: Upgraded to bionic on 2018-03-21 (21 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  

[Touch-packages] [Bug 1821491] Re: DNS lookup fails for local hosts

[Steve Roberts]

Yes, that sounds correct, your reply made me check, if I do:

nslookup phspi05.phs

I also get the same result...

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

Title:
  DNS lookup fails for local hosts

Status in systemd package in Ubuntu:
  New

Bug description:
  Mint 19 (Ubuntu Bionic) 
  Laptop so Using NetworkManager, and connecting wirelessly to LAN
  Upgraded from Mint 18.3 so using resolvconf...

  Versions:
  network-manager: 1.10.6-2ubuntu1.1
  resolvconf: 1.79ubuntu10.18.04.3 or 1.79ubuntu10.18.04.2
  systemd: 237-3ubuntu10.15

  dns is specified in NetworkMananager as 192.168.2.1
  the dns is a router, and has static ips assigned to certain hosts on my lan...

  $cat resolv.conf
  nameserver 127.0.0.53
  search phs
  options edns0

  $ nslookup phspi05
  Server:   127.0.0.53
  Address:  127.0.0.53#53

  ** server can't find phspi05: SERVFAIL

  If I explicity specify the dns:

  $ nslookup phspi05 192.168.2.1
  Server:   192.168.2.1
  Address:  192.168.2.1#53

  Non-authoritative answer:
  Name: phspi05
  Address: 192.168.2.35

  I get the correct ip address...

  Same with dig...

  I would expect that the nameserver set in network-manager would be
  used

  From tail of $ systemd-resolve --status

  Link 2 (wlp2s0)
Current Scopes: DNS
 LLMNR setting: yes
  MulticastDNS setting: no
DNSSEC setting: no
  DNSSEC supported: no
   DNS Servers: 192.168.2.1
DNS Domain: phs

  So the dns address had been picked up from NetworkManager, but
  apparently is not being used...

  Thought it might be related to this bug:
  https://bugs.launchpad.net/ubuntu/bionic/+source/resolvconf/+bug/1817903

  So installed the proposed fix, but no change. I also tried removing
  package resolvconf, again no change...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821491/+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 1809247] Re: SetReportCrashes to true dbus call failed

[Launchpad Bug Tracker]

This bug was fixed in the package apport - 2.20.10-0ubuntu25

---
apport (2.20.10-0ubuntu25) disco; urgency=medium

  * test/test_report.py: update test_add_proc_info for function raising a
ValueError.

 -- Brian Murray   Thu, 04 Apr 2019 10:18:25 -0700

** Changed in: apport (Ubuntu Disco)
   Status: In Progress => 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/1809247

Title:
  SetReportCrashes to true dbus call failed

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Disco:
  Fix Released

Bug description:
  The following copied from screenshot 2018-12-20 11-50-53
  Saving crash reporting state failed, Can't set auto auto or never 
  reporting mode.

  Command '['/usr/bin/gdbus','call','-y','-d',
  'com.ubuntu.WhoopsiePreferences','-o','/com/ubuntu/
  WhoopsiePreferences','-m',
  'com.ubuntu.WhoopsiePreferences.SetReportCrashes', 'true']'
  returned non-zero exit status 1.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-headers-4.15.0-43 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic i686
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  Date: Thu Dec 20 11:22:53 2018
  Dependencies:
   
  DuplicateSignature:
   package:linux-headers-4.15.0-43:4.15.0-43.46
   Unpacking linux-modules-extra-4.15.0-43-generic (4.15.0-43.46) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-OeaFpG/04-linux-modules-extra-4.15.0-43-generic_4.15.0-43.46_i386.deb
 (--unpack):
unable to open 
'/lib/modules/4.15.0-43-generic/kernel/drivers/infiniband/hw/cxgb4/iw_cxgb4.ko.dpkg-new':
 Operation not permitted
  ErrorMessage: unable to create new file 
'/var/lib/dpkg/info/linux-headers-4.15.0-43.list-new': Operation not permitted
  InstallationDate: Installed on 2017-12-03 (382 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: linux
  Title: package linux-headers-4.15.0-43 4.15.0-43.46 failed to 
install/upgrade: unable to create new file 
'/var/lib/dpkg/info/linux-headers-4.15.0-43.list-new': Operation not permitted
  UpgradeStatus: Upgraded to bionic on 2018-09-18 (92 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1809247/+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 1820132] Re: /usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport/whoopsie-upload-all@162:collect_info:process_report:add_gdb_info:gdb_command

[Launchpad Bug Tracker]

This bug was fixed in the package apport - 2.20.10-0ubuntu25

---
apport (2.20.10-0ubuntu25) disco; urgency=medium

  * test/test_report.py: update test_add_proc_info for function raising a
ValueError.

 -- Brian Murray   Thu, 04 Apr 2019 10:18:25 -0700

** Changed in: apport (Ubuntu Disco)
   Status: In Progress => 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/1820132

Title:
  /usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport
  /whoopsie-upload-
  all@162:collect_info:process_report:add_gdb_info:gdb_command

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Bionic:
  Triaged
Status in apport source package in Disco:
  Fix Released

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.10-0ubuntu23, the problem page at 
https://errors.ubuntu.com/problem/4a48673e60f08b7d2b9067d1b47766a57f7e693e 
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/1820132/+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 1396160] Re: /usr/share/apport/recoverable_problem:PermissionError:/usr/share/apport/recoverable_problem@75:main:add_proc_info

[Launchpad Bug Tracker]

This bug was fixed in the package apport - 2.20.10-0ubuntu25

---
apport (2.20.10-0ubuntu25) disco; urgency=medium

  * test/test_report.py: update test_add_proc_info for function raising a
ValueError.

 -- Brian Murray   Thu, 04 Apr 2019 10:18:25 -0700

** Changed in: apport (Ubuntu Disco)
   Status: In Progress => 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/1396160

Title:
  
/usr/share/apport/recoverable_problem:PermissionError:/usr/share/apport/recoverable_problem@75:main:add_proc_info

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Bionic:
  Triaged
Status in apport source package in Disco:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding apport.  This problem was most recently seen with version
  2.14.7-0ubuntu10, the problem page at
  https://errors.ubuntu.com/problem/9a1df90760a88c9b4e5e7e3b4ef450f6b5669c7c
  contains more details.

  More Buckets:
  https://errors.ubuntu.com/problem/2a97a88118a1d8746cff239205a4cd9eb3d0357d
  https://errors.ubuntu.com/problem/72c621876cfe04b51b37f8f3ef08c3da0460b462

  
  Other reference:
  bug 1394919

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

Re: [Touch-packages] [Bug 1821491] Re: DNS lookup fails for local hosts

[Steve Langasek]

On Thu, Apr 04, 2019 at 07:27:00PM -, Steve Roberts wrote:
> Yes, that sounds correct, your reply made me check, if I do:

> nslookup phspi05.phs

> I also get the same result...

By "same result", you mean the successful result or the failure result?

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

Title:
  DNS lookup fails for local hosts

Status in systemd package in Ubuntu:
  New

Bug description:
  Mint 19 (Ubuntu Bionic) 
  Laptop so Using NetworkManager, and connecting wirelessly to LAN
  Upgraded from Mint 18.3 so using resolvconf...

  Versions:
  network-manager: 1.10.6-2ubuntu1.1
  resolvconf: 1.79ubuntu10.18.04.3 or 1.79ubuntu10.18.04.2
  systemd: 237-3ubuntu10.15

  dns is specified in NetworkMananager as 192.168.2.1
  the dns is a router, and has static ips assigned to certain hosts on my lan...

  $cat resolv.conf
  nameserver 127.0.0.53
  search phs
  options edns0

  $ nslookup phspi05
  Server:   127.0.0.53
  Address:  127.0.0.53#53

  ** server can't find phspi05: SERVFAIL

  If I explicity specify the dns:

  $ nslookup phspi05 192.168.2.1
  Server:   192.168.2.1
  Address:  192.168.2.1#53

  Non-authoritative answer:
  Name: phspi05
  Address: 192.168.2.35

  I get the correct ip address...

  Same with dig...

  I would expect that the nameserver set in network-manager would be
  used

  From tail of $ systemd-resolve --status

  Link 2 (wlp2s0)
Current Scopes: DNS
 LLMNR setting: yes
  MulticastDNS setting: no
DNSSEC setting: no
  DNSSEC supported: no
   DNS Servers: 192.168.2.1
DNS Domain: phs

  So the dns address had been picked up from NetworkManager, but
  apparently is not being used...

  Thought it might be related to this bug:
  https://bugs.launchpad.net/ubuntu/bionic/+source/resolvconf/+bug/1817903

  So installed the proposed fix, but no change. I also tried removing
  package resolvconf, again no change...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821491/+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 1812014] Re: keyboard not responding after suspend after some time

[Krzysztof]

Hi, recently I had changed the gpu driver to the latest one from nvidia
nvidia-driver-418(opensource) and I since then, I started experiencing
performance problems similar to those mentioned earlier: "'upower' using
100% CPU and another shows 'kworker/6:0-events' using 100%.". The
prolems starts after suspending my system and bringing it back to life
like previously, but this time keyboard is working fine.

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

Title:
  keyboard not responding after suspend after some time

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete
Status in upower package in Ubuntu:
  Incomplete

Bug description:
  I work on Lenovo laptop y-700. When I resume system after suspend, keyboards 
stop working, and sometimes there are performance problems visible when playing 
videos. It happens not immediately but after a few minutes or even a few hours 
of working. Restart or shutdown does not finish correctly and I need to hold 
the power button for a few seconds.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  GsettingsChanges:
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-08-06 (165 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.30.1-2ubuntu1.18.10.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

Re: [Touch-packages] [Bug 1823202] Re: HOME points to something not owned by user in sudo

[Ryan K. McKee]

So does this mean sudo -s doesn't work? If not, why the implementation? Why
does an "-s" switch exist if it provides no functionality?

On Thu, Apr 4, 2019, 11:55 AM Seth Arnold <1823...@bugs.launchpad.net>
wrote:

> You should use sudo -i to get a clean root login without your local user
> configuration seeping into the shell.
>
> Thanks
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1823202
>
> Title:
>   HOME points to something not owned by user in sudo
>
> Status in sudo package in Ubuntu:
>   New
> Status in zsh package in Ubuntu:
>   New
>
> Bug description:
>You shouldn't use interactive shell, or any program with
>   executable configuration, while your HOME points to something not
>   owned by your user. That's the big issue and it's with sudo, not zsh,
>   not omz, not any other shell or application you launch.  You
>   can go shout "you are doing security wrong" at Ubuntu. Good luck.
>
>   ╭─rkm@Khadas ~
>   ╰─➤  id rkm && getent passwd rkm
>   uid=1001(rkm) gid=1001(rkm)
> groups=1001(rkm),0(root),4(adm),5(tty),6(disk),20(dialout),21(fax),24(cdrom),25(floppy),26(tape),27(sudo),29(audio),30(dip),44(video),46(plugdev),50(staff),60(games),100(users),101(systemd-journal),104(input),108(netdev),112(bluetooth),113(lpadmin),121(pulse-access)
>   rkm:x:1001:1001:Ryan McKee:/home/rkm:/usr/bin/zsh
>
>   ╭─rkm@Khadas ~
>   ╰─➤  sudo /usr/bin/env
> 1 ↵
>   LC_MESSAGES=en_US.UTF-8
>   LANG=en_US.UTF-8
>   LANGUAGE=en_US.UTF-8
>   TERM=xterm-256color
>   XAUTHORITY=/home/rkm/.Xauthority
>   COLORTERM=truecolor
>   DISPLAY=:0.0
>
> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin
>   HOME=/home/rkm
>   LC_CTYPE=en_US.UTF-8
>
> LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.wim=01;31:*.swm=01;31:*.dwm=01;31:*.esd=01;31:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:
>   MAIL=/var/mail/root
>   LOGNAME=root
>   USER=root
>   USERNAME=root
>   SHELL=/bin/bash
>   SUDO_COMMAND=/usr/bin/env
>
>
>   SUDO_USER=rkm
>   SUDO_UID=1001
>   SUDO_GID=1001
>   ╭─rkm@Khadas ~
>   ╰─➤
>
>CyberManifest: sudo is a package. Also, once filed, add
>   zsh to the bug since it could be a bug in zsh's package as well.
>
>Not necessarily zsh itself, but the packaging.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: sudo 1.8.21p2-3ubuntu1
>   Uname: Linux 4.9.40 aarch64
>   ApportVersion: 2.20.9-0ubuntu7.6
>   Architecture: arm64
>   CurrentDesktop: XFCE
>   Date: Thu Apr  4 11:07:42 2019
>   SourcePackage: sudo
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   VisudoCheck:
>/etc/sudoers: parsed OK
>/etc/sudoers.d/README: parsed OK
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1823202/+subscriptions
>

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

Title:
  HOME points to something not owned by user in sudo

Status in sudo package in Ubuntu:
  New
Status in zsh package in Ubuntu:
  New

Bug description:
   You shouldn't use interactive shell, or any program with
  executable configuration, while your HOME points to something not
  owned by your user. That's the big issue and it's with sudo, not zsh,
  not omz, not any other shell or application you launch.  You
  can go shout "you are doing security wrong" at Ubuntu. Good luck.

  ╭─rkm@Khadas ~  
  ╰─➤  id rkm && getent passwd rkm
  uid=1001(rkm) gid=1001(rkm) 

[Touch-packages] [Bug 1823217] [NEW] Portrait display cuts off below primary monitor

[Douglas Hitchcock]

Public bug reported:

Using beta of Disco Dingo, so gnome-shell 3.32.0-1ubuntu1.

Two monitors, place one Portrait right.  Any part of that screen that
extends below the primary monitor is cut off.  The mouse cursor will go
in there, but any window you drag in there disappears.  If you take a
screen shot, the screenshot tool thinks that area does not exist.
Screenshots attached.

I've used this same monitor layout for years, this issue did not exist
in Cosmic.  I was able to reproduce it in a clean install in Virtualbox,
so it's not limited to my hardware or any extensions/apps I'm using.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
Uname: Linux 5.0.0-8-generic x86_64
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr  4 14:02:45 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 6.0.4, 5.0.0-7-generic, x86_64: installed
 virtualbox, 6.0.4, 5.0.0-8-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Crystal Well Integrated Graphics Controller [8086:0d26] (rev 
08) (prog-if 00 [VGA controller])
   Subsystem: CLEVO/KAPOK Computer Crystal Well Integrated Graphics Controller 
[1558:7410]
InstallationDate: Installed on 2019-03-26 (8 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190325)
MachineType: System76, Inc. Galago UltraPro
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic 
root=UUID=6429a565-4509-46ef-9be8-1558a2b094e4 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/09/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: Galago UltraPro
dmi.board.vendor: System76, Inc.
dmi.board.version: galu1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: System76, Inc,
dmi.chassis.version: galu1
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/09/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnSystem76,Inc.:rnGalagoUltraPro:rvrgalu1:cvnSystem76,Inc,:ct9:cvrgalu1:
dmi.product.family: Not Applicable
dmi.product.name: Galago UltraPro
dmi.product.sku: Not Applicable
dmi.product.version: galu1
dmi.sys.vendor: System76, Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.1-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
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 disco ubuntu

** Attachment added: "Picture of screen, since screenshot doesn't capture the 
blackness"
   
https://bugs.launchpad.net/bugs/1823217/+attachment/5252896/+files/IMG_20190404_121441.jpg

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

Title:
  Portrait display cuts off below primary monitor

Status in xorg package in Ubuntu:
  New

Bug description:
  Using beta of Disco Dingo, so gnome-shell 3.32.0-1ubuntu1.

  Two monitors, place one Portrait right.  Any part of that screen that
  extends below the primary monitor is cut off.  The mouse cursor will
  go in there, but any window you drag in there disappears.  If you take
  a screen shot, the screenshot tool thinks that area does not exist.
  Screenshots attached.

  I've used this same monitor layout for years, this issue did not exist
  in Cosmic.  I was able to reproduce it in a clean install in
  Virtualbox, so it's not limited to my hardware or any extensions/apps
  I'm using.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  4 14:02:45 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.0.4, 5.0.0-7-generic, x86_64: installed
   virtualbox, 6.0.4, 5.0.0-8-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Crystal Well Integrated Graphics 

[Touch-packages] [Bug 1812014] Re: keyboard not responding after suspend after some time

[Daniel van Vugt]

Please keep this bug about the keyboard only.

Performance issues should be logged as separate bugs, although it sounds
like bug 1808108 is one of the issues.

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

Title:
  keyboard not responding after suspend after some time

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete
Status in upower package in Ubuntu:
  Incomplete

Bug description:
  I work on Lenovo laptop y-700. When I resume system after suspend, keyboards 
stop working, and sometimes there are performance problems visible when playing 
videos. It happens not immediately but after a few minutes or even a few hours 
of working. Restart or shutdown does not finish correctly and I need to hold 
the power button for a few seconds.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  GsettingsChanges:
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-08-06 (165 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.30.1-2ubuntu1.18.10.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812014/+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 1822426] Re: 19.04 Built in Intel HDA sound is disabled upon resume

[Daniel van Vugt]

Cristian,

And if your issue is just timidity then that is bug 1793640.

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

Title:
  19.04 Built in Intel HDA sound is disabled upon resume

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

Bug description:
  With 19.04, Intel Corporation 8 Series/C220 Series Chipset High
  Definition Audio Controller intermittently is not enabled when
  resuming from sleep. The HDMI sound device is enabled but that is not
  hooked up on my system.  New with 19.04, when sound works after
  resume, an icon labeled "Built in Audio Stereo" appears during the
  resume process.

  Unsure if this is related, but sound seems to sleep when not in use.
  Launching sound enabled apps produces a quiet "tick, thud" sound as
  sound system turns on.

  When sound is not working, killall pusleaudio "fixes" the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  darin  4814 F pulseaudio
   /dev/snd/controlC1:  darin  4814 F pulseaudio
   /dev/snd/controlC0:  darin  4814 F pulseaudio
  CurrentDesktop: KDE
  Date: Sat Mar 30 10:20:24 2019
  InstallationDate: Installed on 2018-01-13 (441 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180112)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-03-27 (3 days ago)
  dmi.bios.date: 08/18/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-PRO
  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.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822426/+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 1822426] Re: 19.04 Built in Intel HDA sound is disabled upon resume

[Daniel van Vugt]

Cristian,

Please log that issue as a new bug by running:

  ubuntu-bug 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/1822426

Title:
  19.04 Built in Intel HDA sound is disabled upon resume

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

Bug description:
  With 19.04, Intel Corporation 8 Series/C220 Series Chipset High
  Definition Audio Controller intermittently is not enabled when
  resuming from sleep. The HDMI sound device is enabled but that is not
  hooked up on my system.  New with 19.04, when sound works after
  resume, an icon labeled "Built in Audio Stereo" appears during the
  resume process.

  Unsure if this is related, but sound seems to sleep when not in use.
  Launching sound enabled apps produces a quiet "tick, thud" sound as
  sound system turns on.

  When sound is not working, killall pusleaudio "fixes" the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  darin  4814 F pulseaudio
   /dev/snd/controlC1:  darin  4814 F pulseaudio
   /dev/snd/controlC0:  darin  4814 F pulseaudio
  CurrentDesktop: KDE
  Date: Sat Mar 30 10:20:24 2019
  InstallationDate: Installed on 2018-01-13 (441 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180112)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-03-27 (3 days ago)
  dmi.bios.date: 08/18/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-PRO
  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.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Touch-packages] [Bug 1659534] Re: userdel doesn't supports extrausers

[Sergio Cazzolato]

Validation done on xenial and bionic

This log is part of the test I did to check --extrausers can be used to
add and del users.

https://paste.ubuntu.com/p/Jn2kDcNcnv/


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

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

Title:
  userdel doesn't supports extrausers

Status in Snappy:
  In Progress
Status in shadow package in Ubuntu:
  Fix Released
Status in shadow source package in Xenial:
  Fix Committed
Status in shadow source package in Bionic:
  Fix Committed

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

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

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

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

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

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

[Touch-packages] [Bug 1823202] Re: HOME points to something not owned by user in sudo

[Ryan K. McKee]

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

[17:16:23]  CyberManifest: there are two other bugs that are
the same as yours, both can be found in
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/760140

[17:16:46]  I personally believe that the decision of adding
this patch is wrong, please refer Bug #1373495. / I'm expecting the
documented behavior. Please refer Bug #889936

** This bug has been marked a duplicate of bug 1373495
   sudo shouldn't preserve caller's HOME environment variable by default

** This bug is no longer a duplicate of bug 1373495
   sudo shouldn't preserve caller's HOME environment variable by default

** This bug has been marked a duplicate of bug 889936
   sudo(8) incorrectly says HOME is reset if env_reset is set

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

Title:
  HOME points to something not owned by user in sudo

Status in sudo package in Ubuntu:
  New
Status in zsh package in Ubuntu:
  New

Bug description:
   You shouldn't use interactive shell, or any program with
  executable configuration, while your HOME points to something not
  owned by your user. That's the big issue and it's with sudo, not zsh,
  not omz, not any other shell or application you launch.  You
  can go shout "you are doing security wrong" at Ubuntu. Good luck.

  ╭─rkm@Khadas ~  
  ╰─➤  id rkm && getent passwd rkm
  uid=1001(rkm) gid=1001(rkm) 
groups=1001(rkm),0(root),4(adm),5(tty),6(disk),20(dialout),21(fax),24(cdrom),25(floppy),26(tape),27(sudo),29(audio),30(dip),44(video),46(plugdev),50(staff),60(games),100(users),101(systemd-journal),104(input),108(netdev),112(bluetooth),113(lpadmin),121(pulse-access)
  rkm:x:1001:1001:Ryan McKee:/home/rkm:/usr/bin/zsh

  ╭─rkm@Khadas ~  
  ╰─➤  sudo /usr/bin/env  1 
↵
  LC_MESSAGES=en_US.UTF-8
  LANG=en_US.UTF-8
  LANGUAGE=en_US.UTF-8
  TERM=xterm-256color
  XAUTHORITY=/home/rkm/.Xauthority
  COLORTERM=truecolor
  DISPLAY=:0.0
  PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin
  HOME=/home/rkm
  LC_CTYPE=en_US.UTF-8
  
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.wim=01;31:*.swm=01;31:*.dwm=01;31:*.esd=01;31:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:
  MAIL=/var/mail/root
  LOGNAME=root
  USER=root
  USERNAME=root
  SHELL=/bin/bash
  SUDO_COMMAND=/usr/bin/env

  
  SUDO_USER=rkm
  SUDO_UID=1001
  SUDO_GID=1001
  ╭─rkm@Khadas ~  
  ╰─➤  

   CyberManifest: sudo is a package. Also, once filed, add
  zsh to the bug since it could be a bug in zsh's package as well.

   Not necessarily zsh itself, but the packaging.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: sudo 1.8.21p2-3ubuntu1
  Uname: Linux 4.9.40 aarch64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: arm64
  CurrentDesktop: XFCE
  Date: Thu Apr  4 11:07:42 2019
  SourcePackage: sudo
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   /etc/sudoers: parsed OK
   /etc/sudoers.d/README: parsed OK

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1823202/+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 1823261] Re: PCI/internal sound card not detected

[Daniel van Vugt]

It appears the kernel has stopped reporting any sound devices:

!!Loaded ALSA modules
!!---


!!Sound Servers on this system
!!

Pulseaudio:
  Installed - Yes (/usr/bin/pulseaudio)
  Running - Yes


!!Soundcards recognised by ALSA
!!-

--- no soundcards ---

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

** Tags added: regression-update

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

Title:
  PCI/internal sound card not detected

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It was ok previously but it stopped some days back. my tracking results no 
sound card found.
  may be a driver problem or something.
  no hardware changes have been made since i started using the device.
  lspci -v says there is intel corp. broadwell-U audio controller is there.
  please help or advise.
  i am using ubuntu 14.04 lts.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-52.86+bdw1-generic 3.13.11-ckt18
  Uname: Linux 3.13.0-52-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Fri Apr  5 02:13:22 2019
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  InstallationDate: Installed on 2019-03-19 (16 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  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: 10/16/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0RG2FR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd10/16/2015:svnDellInc.:pnInspiron3543:pvrA07:rvnDellInc.:rn0RG2FR:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3543
  dmi.product.version: A07
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823261/+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 1821491] Re: DNS lookup fails for local hosts

[Dan Streetman]

> $ nslookup phspi05 192.168.2.1
> Server:   192.168.2.1
> Address:  192.168.2.1#53
>
> Non-authoritative answer:
> Name: phspi05
> Address: 192.168.2.35
> ** server can't find phspi05: NXDOMAIN

your upstream ns is returning an address, but NXDOMAIN as well; I'm
pretty sure resolved sees that as query failure, and ignores the address
that the server returned.  What dns server are you using on your router,
and how is it set up with your custom host 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/1821491

Title:
  DNS lookup fails for local hosts

Status in systemd package in Ubuntu:
  New

Bug description:
  Mint 19 (Ubuntu Bionic) 
  Laptop so Using NetworkManager, and connecting wirelessly to LAN
  Upgraded from Mint 18.3 so using resolvconf...

  Versions:
  network-manager: 1.10.6-2ubuntu1.1
  resolvconf: 1.79ubuntu10.18.04.3 or 1.79ubuntu10.18.04.2
  systemd: 237-3ubuntu10.15

  dns is specified in NetworkMananager as 192.168.2.1
  the dns is a router, and has static ips assigned to certain hosts on my lan...

  $cat resolv.conf
  nameserver 127.0.0.53
  search phs
  options edns0

  $ nslookup phspi05
  Server:   127.0.0.53
  Address:  127.0.0.53#53

  ** server can't find phspi05: SERVFAIL

  If I explicity specify the dns:

  $ nslookup phspi05 192.168.2.1
  Server:   192.168.2.1
  Address:  192.168.2.1#53

  Non-authoritative answer:
  Name: phspi05
  Address: 192.168.2.35

  I get the correct ip address...

  Same with dig...

  I would expect that the nameserver set in network-manager would be
  used

  From tail of $ systemd-resolve --status

  Link 2 (wlp2s0)
Current Scopes: DNS
 LLMNR setting: yes
  MulticastDNS setting: no
DNSSEC setting: no
  DNSSEC supported: no
   DNS Servers: 192.168.2.1
DNS Domain: phs

  So the dns address had been picked up from NetworkManager, but
  apparently is not being used...

  Thought it might be related to this bug:
  https://bugs.launchpad.net/ubuntu/bionic/+source/resolvconf/+bug/1817903

  So installed the proposed fix, but no change. I also tried removing
  package resolvconf, again no change...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821491/+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 1823202] Re: HOME points to something not owned by user in sudo

[Ryan K. McKee]

[16:51:24]  that patch that they added in ... 1.7.4p4-5ubuntu6 
breaks the default sudo compared to upstream (both sudo and debian)
[16:52:36]  you can reference to 
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/760140

Basically I resolved my sudo -s issue by 
creating a new file: /etc/sudoers.d/01_env_keep
with the following contents:

Defaults env_keep -= "HOME"

and then chmod 440 /etc/sudoers.d/01_env_keep

and then confirming with sudo sudo -V

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

Title:
  HOME points to something not owned by user in sudo

Status in sudo package in Ubuntu:
  New
Status in zsh package in Ubuntu:
  New

Bug description:
   You shouldn't use interactive shell, or any program with
  executable configuration, while your HOME points to something not
  owned by your user. That's the big issue and it's with sudo, not zsh,
  not omz, not any other shell or application you launch.  You
  can go shout "you are doing security wrong" at Ubuntu. Good luck.

  ╭─rkm@Khadas ~  
  ╰─➤  id rkm && getent passwd rkm
  uid=1001(rkm) gid=1001(rkm) 
groups=1001(rkm),0(root),4(adm),5(tty),6(disk),20(dialout),21(fax),24(cdrom),25(floppy),26(tape),27(sudo),29(audio),30(dip),44(video),46(plugdev),50(staff),60(games),100(users),101(systemd-journal),104(input),108(netdev),112(bluetooth),113(lpadmin),121(pulse-access)
  rkm:x:1001:1001:Ryan McKee:/home/rkm:/usr/bin/zsh

  ╭─rkm@Khadas ~  
  ╰─➤  sudo /usr/bin/env  1 
↵
  LC_MESSAGES=en_US.UTF-8
  LANG=en_US.UTF-8
  LANGUAGE=en_US.UTF-8
  TERM=xterm-256color
  XAUTHORITY=/home/rkm/.Xauthority
  COLORTERM=truecolor
  DISPLAY=:0.0
  PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin
  HOME=/home/rkm
  LC_CTYPE=en_US.UTF-8
  
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.wim=01;31:*.swm=01;31:*.dwm=01;31:*.esd=01;31:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:
  MAIL=/var/mail/root
  LOGNAME=root
  USER=root
  USERNAME=root
  SHELL=/bin/bash
  SUDO_COMMAND=/usr/bin/env

  
  SUDO_USER=rkm
  SUDO_UID=1001
  SUDO_GID=1001
  ╭─rkm@Khadas ~  
  ╰─➤  

   CyberManifest: sudo is a package. Also, once filed, add
  zsh to the bug since it could be a bug in zsh's package as well.

   Not necessarily zsh itself, but the packaging.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: sudo 1.8.21p2-3ubuntu1
  Uname: Linux 4.9.40 aarch64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: arm64
  CurrentDesktop: XFCE
  Date: Thu Apr  4 11:07:42 2019
  SourcePackage: sudo
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   /etc/sudoers: parsed OK
   /etc/sudoers.d/README: parsed OK

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1823202/+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 1820132] Re: /usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport/whoopsie-upload-all@162:collect_info:process_report:add_gdb_info:gdb_command

[Brian Murray]

Here's the better changelog entry:

apport (2.20.10-0ubuntu24) disco; urgency=medium

   


   
  * debian/control: apport-gtk should depend on whoopsie-preferences as that

   
is needed to store preferences for reporting crashes. (LP: #1809247)

   
  * apport/report.py, apport/ui.py: raise ValueError if the pid is not  

   
accessible, display an error message for that or an invalid pid. (LP: 
#1396160)   

 
  * switch from pyflakes to pyflakes3, drop some python2 code   

   
  * apport/report.py: Have add_gdb_info return a FileNotFoundError if gdb or

   
the crashing executable are not found and modify whoopsie-upload-all to 

   
upload crashes in that situation. (LP: #1820132)

   
  * debian/control, apport/hookutils.py: pkexec does not work in non-graphical  

   
environments yet (LP #1821415) and its providing package should only be 

   
a suggests because gathering of information as root isn't entirely  

   
necessary for a bug report.

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

Title:
  /usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport
  /whoopsie-upload-
  all@162:collect_info:process_report:add_gdb_info:gdb_command

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Bionic:
  Triaged
Status in apport source package in Disco:
  Fix Released

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.10-0ubuntu23, the problem page at 
https://errors.ubuntu.com/problem/4a48673e60f08b7d2b9067d1b47766a57f7e693e 
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/1820132/+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 1823217] Re: Portrait display cuts off below primary monitor

[Daniel van Vugt]

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

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 1822513, 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 1822513
   [regression] gnome-shell aspect ratio doesn't rotate with the rest of the 
screen

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

Title:
  Portrait display cuts off below primary monitor

Status in xorg package in Ubuntu:
  New

Bug description:
  Using beta of Disco Dingo, so gnome-shell 3.32.0-1ubuntu1.

  Two monitors, place one Portrait right.  Any part of that screen that
  extends below the primary monitor is cut off.  The mouse cursor will
  go in there, but any window you drag in there disappears.  If you take
  a screen shot, the screenshot tool thinks that area does not exist.
  Screenshots attached.

  I've used this same monitor layout for years, this issue did not exist
  in Cosmic.  I was able to reproduce it in a clean install in
  Virtualbox, so it's not limited to my hardware or any extensions/apps
  I'm using.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  4 14:02:45 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.0.4, 5.0.0-7-generic, x86_64: installed
   virtualbox, 6.0.4, 5.0.0-8-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Crystal Well Integrated Graphics Controller [8086:0d26] 
(rev 08) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Crystal Well Integrated Graphics 
Controller [1558:7410]
  InstallationDate: Installed on 2019-03-26 (8 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190325)
  MachineType: System76, Inc. Galago UltraPro
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic 
root=UUID=6429a565-4509-46ef-9be8-1558a2b094e4 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Galago UltraPro
  dmi.board.vendor: System76, Inc.
  dmi.board.version: galu1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: System76, Inc,
  dmi.chassis.version: galu1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/09/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnSystem76,Inc.:rnGalagoUltraPro:rvrgalu1:cvnSystem76,Inc,:ct9:cvrgalu1:
  dmi.product.family: Not Applicable
  dmi.product.name: Galago UltraPro
  dmi.product.sku: Not Applicable
  dmi.product.version: galu1
  dmi.sys.vendor: System76, Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  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/1823217/+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 1823269] Re: vm ubuntu Canon printer will not print

[Raymond Schutte]

** Attachment added: "troubleshoot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1823269/+attachment/5252961/+files/troubleshoot.txt

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

Title:
  vm ubuntu Canon printer will not print

Status in cups package in Ubuntu:
  New

Bug description:
  Printer stays in processing mode and does not print

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: cups 2.2.10-4
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log'
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  4 16:52:17 2019
  InstallationDate: Installed on 2017-07-06 (637 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lpstat:
   device for iR-ADV-C5535-5540-III-UFR-II: socket://192.168.5.8
   device for iR-ADV-C5535-5540-III-UFR-II-2: socket://192.168.5.9
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/iR-ADV-C5535-5540-III-UFR-II.ppd', 
'/etc/cups/ppd/iR-ADV-C5535-5540-III-UFR-II-2.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/iR-ADV-C5535-5540-III-UFR-II.ppd: Permission denied
   grep: /etc/cups/ppd/iR-ADV-C5535-5540-III-UFR-II-2.ppd: Permission denied
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic 
root=UUID=0da1d663-4b5f-454a-aecf-80ce65eb22d3 ro cgroup_enable=memory 
swapaccount=1 splash
  SourcePackage: cups
  UpgradeStatus: Upgraded to disco on 2019-04-04 (0 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1823269/+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 1823269] [NEW] vm ubuntu Canon printer will not print

[Raymond Schutte]

Public bug reported:

Printer stays in processing mode and does not print

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: cups 2.2.10-4
ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
Uname: Linux 5.0.0-8-generic x86_64
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log'
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr  4 16:52:17 2019
InstallationDate: Installed on 2017-07-06 (637 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
Lpstat:
 device for iR-ADV-C5535-5540-III-UFR-II: socket://192.168.5.8
 device for iR-ADV-C5535-5540-III-UFR-II-2: socket://192.168.5.9
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
Papersize: letter
PpdFiles:
 Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/iR-ADV-C5535-5540-III-UFR-II.ppd', 
'/etc/cups/ppd/iR-ADV-C5535-5540-III-UFR-II-2.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/iR-ADV-C5535-5540-III-UFR-II.ppd: Permission denied
 grep: /etc/cups/ppd/iR-ADV-C5535-5540-III-UFR-II-2.ppd: Permission denied
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic 
root=UUID=0da1d663-4b5f-454a-aecf-80ce65eb22d3 ro cgroup_enable=memory 
swapaccount=1 splash
SourcePackage: cups
UpgradeStatus: Upgraded to disco on 2019-04-04 (0 days ago)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

** Affects: cups (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 cups in Ubuntu.
https://bugs.launchpad.net/bugs/1823269

Title:
  vm ubuntu Canon printer will not print

Status in cups package in Ubuntu:
  New

Bug description:
  Printer stays in processing mode and does not print

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: cups 2.2.10-4
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log'
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  4 16:52:17 2019
  InstallationDate: Installed on 2017-07-06 (637 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lpstat:
   device for iR-ADV-C5535-5540-III-UFR-II: socket://192.168.5.8
   device for iR-ADV-C5535-5540-III-UFR-II-2: socket://192.168.5.9
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/iR-ADV-C5535-5540-III-UFR-II.ppd', 
'/etc/cups/ppd/iR-ADV-C5535-5540-III-UFR-II-2.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/iR-ADV-C5535-5540-III-UFR-II.ppd: Permission denied
   grep: /etc/cups/ppd/iR-ADV-C5535-5540-III-UFR-II-2.ppd: Permission denied
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic 
root=UUID=0da1d663-4b5f-454a-aecf-80ce65eb22d3 ro cgroup_enable=memory 
swapaccount=1 splash
  SourcePackage: cups
  UpgradeStatus: Upgraded to disco on 2019-04-04 (0 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Touch-packages] [Bug 1396160] Re: /usr/share/apport/recoverable_problem:PermissionError:/usr/share/apport/recoverable_problem@75:main:add_proc_info

[Brian Murray]

Here's the better changelog entry:

apport (2.20.10-0ubuntu24) disco; urgency=medium

   


   
  * debian/control: apport-gtk should depend on whoopsie-preferences as that

   
is needed to store preferences for reporting crashes. (LP: #1809247)

   
  * apport/report.py, apport/ui.py: raise ValueError if the pid is not  

   
accessible, display an error message for that or an invalid pid. (LP: 
#1396160)   

 
  * switch from pyflakes to pyflakes3, drop some python2 code   

   
  * apport/report.py: Have add_gdb_info return a FileNotFoundError if gdb or

   
the crashing executable are not found and modify whoopsie-upload-all to 

   
upload crashes in that situation. (LP: #1820132)

   
  * debian/control, apport/hookutils.py: pkexec does not work in non-graphical  

   
environments yet (LP #1821415) and its providing package should only be 

   
a suggests because gathering of information as root isn't entirely  

   
necessary for a bug report.

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

Title:
  
/usr/share/apport/recoverable_problem:PermissionError:/usr/share/apport/recoverable_problem@75:main:add_proc_info

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Bionic:
  Triaged
Status in apport source package in Disco:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding apport.  This problem was most recently seen with version
  2.14.7-0ubuntu10, the problem page at
  https://errors.ubuntu.com/problem/9a1df90760a88c9b4e5e7e3b4ef450f6b5669c7c
  contains more details.

  More Buckets:
  https://errors.ubuntu.com/problem/2a97a88118a1d8746cff239205a4cd9eb3d0357d
  https://errors.ubuntu.com/problem/72c621876cfe04b51b37f8f3ef08c3da0460b462

  
  Other reference:
  bug 1394919

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1396160/+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 1823150] Re: Bluetooth cannot be turned on (Bluetooth: hci0: Reading Intel version information failed (-110))

[Daniel van Vugt]

[   13.020023] Bluetooth: hci0: command 0xfc05 tx timeout
[   13.020027] Bluetooth: hci0: Reading Intel version information failed (-110)

Yeah we assume this isn't a hardware error if it works in 18.04.

Does it work in a live session of 19.04 if you boot that from USB?
http://cdimages.ubuntu.com/daily-live/current/

I guess this bug is either in the kernel or in the firmware for the
Intel 8260 chip. That is package 'linux-firmware'.

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

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

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

Title:
  Bluetooth cannot be turned on (Bluetooth: hci0: Reading Intel version
  information failed (-110))

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  I cannot turn on Bluetooth in the settings, and `hcitool dev` doesn't
  show devices. Bluetooth used to work before upgrading from 18.04 to
  18.10.

  lsb_release -rd:
  Description:  Ubuntu 18.10
  Release:  18.10

  apt-cache policy bluez
  bluez:
Installed: 5.50-0ubuntu1
Candidate: 5.50-0ubuntu1
Version table:
   *** 5.50-0ubuntu1 500
  500 http://nl.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: bluez 5.50-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  4 12:08:46 2019
  InstallationDate: Installed on 2018-10-26 (159 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: bnep btusb bluetooth
  MachineType: HP HP EliteBook 820 G3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic 
root=UUID=c4bb9536-586b-43ea-a9cf-379bad764d8a ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: Upgraded to cosmic on 2019-03-15 (19 days ago)
  dmi.bios.date: 01/30/2018
  dmi.bios.vendor: HP
  dmi.bios.version: N75 Ver. 01.24
  dmi.board.name: 807C
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 85.77
  dmi.chassis.asset.tag: 5CG73148FW
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.24:bd01/30/2018:svnHP:pnHPEliteBook820G3:pvr:rvnHP:rn807C:rvrKBCVersion85.77:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 820 G3
  dmi.product.sku: 2SF33EP#ABH
  dmi.sys.vendor: HP
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
DOWN 
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:3 acl:0 sco:0 commands:1 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823150/+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 1640544] Re: "indicator-power" says "estimating" when plugged to power.

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Changed in: indicator-power (Ubuntu)
   Status: New => Won't Fix

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

Title:
  "indicator-power" says "estimating" when plugged to power.

Status in indicator-power package in Ubuntu:
  Won't Fix

Bug description:
  There seem to be a couple of bug reports from 4 - 5 years ago,
  complaining the same thing. Looks like the bug is back in 16.10.

  ---

  >1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  16.10 (yakkety)

  >2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  Installed: 12.10.6+16.10.20160708-0ubuntu1
  Candidate: 12.10.6+16.10.20160708-0ubuntu1

  >3) What you expected to happen

  The indicator should say the remaining time to be fully charged, and
  display an icon of either a charging battery, or a "power plug" (In
  case the battery is fully charged, and the machine is running on
  direct power.).

  >4) What happened instead

  The indicator just says "estimating". It doesn't display whether it is
  being charged, or running on direct power.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1640544/+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 1822184] Re: clear_console locks up video when X is running and you log out from a plain text console

[Bug Watch Updater]

** Changed in: xorg-server (Debian)
   Status: Confirmed => Fix Released

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

Title:
  clear_console locks up video when X is running and you log out from a
  plain text console

Status in X.Org X server:
  New
Status in bash package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Confirmed
Status in xorg package in Debian:
  New
Status in xorg-server package in Debian:
  Fix Released

Bug description:
  References:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810660
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866898

  
  If X is running and you switch to a plain text console (ie ctrl-alt-f3), log 
in as a regular user, and then log out, the display switches back to the 
graphical login screen and locks up.  The system is still functioning (can ssh 
in, etc) but the video output is frozen.

  The underlying cause is:
  https://gitlab.freedesktop.org/xorg/xserver/issues/492

  However, the problem can at least be worked around by making
  clear_console switch to tty 6 and back instead of switching to 1 and
  back.  This patch corrects the problem:

  
  --- bash-4.4.18.orig/debian/clear_console.c 2019-03-28 12:09:02.415907787 
-0400
  +++ bash-4.4.18/debian/clear_console.c  2019-03-28 12:08:11.984366858 -0400
  @@ -205,7 +205,7 @@
   #if defined(__linux__)
 num = vtstat.v_active;
   #endif
  -  tmp_num = (num == 1 ? 2 : 1);
  +  tmp_num = (num == 6 ? 5 : 6);
   
 /* switch vt to clear the scrollback buffer */
 if (ioctl(fd, VT_ACTIVATE, tmp_num))

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1822184/+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 1823284] [NEW] Please enable USDT probe generation

[Chris Halse Rogers]

Public bug reported:

The userspace LTTng library can also generate USDT (Userspace Staticly
Defined Tracepoints) probes for ust tracepoints. These allow tracing
lttng tracepoints with ftrace or eBPF tracers.,

Enabling this should be as simple as adding --with-sdt to the configure
options and adding systemtap-sdt-dev to Build-Depends:

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: liblttng-ust0 2.10.3-1
ProcVersionSignature: Ubuntu 4.20.0+bcachefs.git20190325.ffe09df1-1.0-generic 
4.20.0
Uname: Linux 4.20.0+bcachefs.git20190325.ffe09df1-1-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu25
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr  5 16:00:22 2019
SourcePackage: ust
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ust (Ubuntu)
 Importance: Wishlist
 Status: New


** Tags: amd64 apport-bug disco

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

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

Title:
  Please enable USDT probe generation

Status in ust package in Ubuntu:
  New

Bug description:
  The userspace LTTng library can also generate USDT (Userspace Staticly
  Defined Tracepoints) probes for ust tracepoints. These allow tracing
  lttng tracepoints with ftrace or eBPF tracers.,

  Enabling this should be as simple as adding --with-sdt to the
  configure options and adding systemtap-sdt-dev to Build-Depends:

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: liblttng-ust0 2.10.3-1
  ProcVersionSignature: Ubuntu 4.20.0+bcachefs.git20190325.ffe09df1-1.0-generic 
4.20.0
  Uname: Linux 4.20.0+bcachefs.git20190325.ffe09df1-1-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu25
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  5 16:00:22 2019
  SourcePackage: ust
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ust/+bug/1823284/+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 1823110] Re: Screen not resized when rotating 90*

[Daniel van Vugt]

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

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 1822513, 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 1822513
   [regression] gnome-shell aspect ratio doesn't rotate with the rest of the 
screen

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

Title:
  Screen not resized when rotating 90*

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running 19.04 beta on a Microsoft Surface Pro 3.
  Screen resolution 2160x1440 works in normal landscape mode (Docked mode) 
however if I rotate the device 90* clockwise or counter-clockwise, the screen 
resolution doesn't change to 1440x2160. The screen actually rotates however it 
hasn't flipped the dimensions to fit.
  This was previously working on Ubuntu 18.10.

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