[Touch-packages] [Bug 1788620] [NEW] package keyboard-configuration 1.178ubuntu2.6 failed to install/upgrade: installed keyboard-configuration package post-installation script subprocess returned erro

[Ashwin V George]

Public bug reported:

My latest update for Ubuntu failed. I did not really focus on the error
reported though, Apologies for the same.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: keyboard-configuration 1.178ubuntu2.6
ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
Uname: Linux 4.15.0-30-generic x86_64
NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_30_32_generic_42 wl
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Thu Aug 23 19:22:37 2018
ErrorMessage: installed keyboard-configuration package post-installation script 
subprocess returned error exit status 5
InstallationDate: Installed on 2018-07-08 (46 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3ubuntu0.1
SourcePackage: console-setup
Title: package keyboard-configuration 1.178ubuntu2.6 failed to install/upgrade: 
installed keyboard-configuration package post-installation script subprocess 
returned error exit status 5
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: console-setup (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package keyboard-configuration 1.178ubuntu2.6 failed to
  install/upgrade: installed keyboard-configuration package post-
  installation script subprocess returned error exit status 5

Status in console-setup package in Ubuntu:
  New

Bug description:
  My latest update for Ubuntu failed. I did not really focus on the
  error reported though, Apologies for the same.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: keyboard-configuration 1.178ubuntu2.6
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_30_32_generic_42 wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Thu Aug 23 19:22:37 2018
  ErrorMessage: installed keyboard-configuration package post-installation 
script subprocess returned error exit status 5
  InstallationDate: Installed on 2018-07-08 (46 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: console-setup
  Title: package keyboard-configuration 1.178ubuntu2.6 failed to 
install/upgrade: installed keyboard-configuration package post-installation 
script subprocess returned error exit status 5
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1788620/+subscriptions

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

[Touch-packages] [Bug 1788597] Re: ubiquity broken with console-setup 1.178ubuntu2.5

[Jonathan Riddell]

** Patch added: "fix to .config file"
   
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1788597/+attachment/5179744/+files/console-setup_1.178ubuntu2.6.dsc.diff

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

Title:
  ubiquity broken with console-setup 1.178ubuntu2.5

Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  Since this version of console-setup in bionic ubiquity now skips the
  Keyboard and Wireless pages.

  http://launchpadlibrarian.net/382474004/console-
  setup_1.178ubuntu2.4_1.178ubuntu2.5.diff.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1788597/+subscriptions

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

[Touch-packages] [Bug 1574862] Re: CUPS attached printer always paused

[gf]

Hello James,
Thank you for submitting this bug and reporting a problem with cups.  You made 
this bug report some time ago and Ubuntu has been updated since then. 
 
Could you confirm that this is no longer a problem and that we can close the 
ticket? 
If it is still a problem, are you still interested in finding a solution to 
this bug? 
If you are, could you let us know, and in the current version, run the 
following (only once): 
apport-collect BUGNUMBER
and upload the updated logs and and any other logs that are relevant for this 
particular issue.  

Thank you again for helping make Ubuntu better. 
G
[Ubuntu Bug Squad volunteer triager]

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

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

Title:
  CUPS attached printer always paused

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  CUPS network printing has not worked for several weeks now.  I can
  print to the printer from the system it is physically attached to by
  USB; the printer shows as Idle-ready to print.  But from another
  computer on the same LAN the printer shows as paused and all of the
  print jobs as held.

  jcobban@jcobban-laptop:~$ /usr/lib/cups/backend/snmp
  jcobban@jcobban-laptop:~$ lpinfo -v
  network https
  network ipp
  network ipps
  network http
  network ipp14
  network beh
  network socket
  network lpd
  network smb
  direct hp
  direct hpfax
  network 
dnssd://HP%20Deskjet%20F4500%20series%20%40%20jcobban-server._ipp._tcp.local/cups?uuid=d67423d3-4c38-341a-5cef-03a958e31b7e
  jcobban@jcobban-laptop:~$ sudo 'usr/lib/cups/backend/dnssd
  > '
  [sudo] password for jcobban: 
  sudo: usr/lib/cups/backend/dnssd
  : command not found
  jcobban@jcobban-laptop:~$ sudo /usr/lib/cups/backend/dnssd
  DEBUG: Querying 
"HP\032Deskjet\032F4500\032series\032\064\032jcobban-server._ipp._tcp.local"...
  DEBUG: Querying 
"HP\032Deskjet\032F4500\032series\032\064\032jcobban-server._ipps._tcp.local"...
  DEBUG: Querying 
"HP\032Deskjet\032F4500\032series\032\064\032jcobban-server._printer._tcp.local"...
  DEBUG: sent=0, count=3
  DEBUG2: query_callback(browser=0x558f5b5aadf0, interfaceIndex=2, protocol=1, 
event=0, 
fullName="HP\032Deskjet\032F4500\032series\032\064\032jcobban-server._ipp._tcp.local",
 rrclass=1, rrtype=16, rdata=0x558f5b5ac6f0, rdlen=474, flags=5, 
context=0x558f5b5a8bd0)
  DEBUG2: query_callback: "txtvers=1".
  DEBUG2: query_callback: "qtotal=1".
  DEBUG2: query_callback: "rp=printers/HP-Deskjet-F4500-series".
  DEBUG2: query_callback: "ty=HP Deskjet f4500 Series, hpcups 3.15.7".
  DEBUG2: query_callback: 
"adminurl=https://jcobban-server.local:631/printers/HP-Deskjet-F4500-series;.
  DEBUG2: query_callback: "note=jcobban-server".
  DEBUG2: query_callback: "priority=0".
  DEBUG2: query_callback: "product=(HP Deskjet f4500 All-in-one Printer 
Series)".
  DEBUG2: query_callback: 
"pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg,image/png,image/pwg-raster,image/urf".
  DEBUG2: query_callback: "URF=DM3".
  DEBUG2: query_callback: "UUID=d67423d3-4c38-341a-5cef-03a958e31b7e".
  DEBUG2: query_callback: "TLS=1.2".
  DEBUG2: query_callback: "Color=T".
  DEBUG2: query_callback: "printer-state=3".
  DEBUG2: query_callback: "printer-type=0x900E".
  DEBUG2: query_callback(browser=0x558f5b5aadf0, interfaceIndex=2, protocol=0, 
event=0, 
fullName="HP\032Deskjet\032F4500\032series\032\064\032jcobban-server._ipp._tcp.local",
 rrclass=1, rrtype=16, rdata=0x558f5b5ac940, rdlen=474, flags=5, 
context=0x558f5b5a8bd0)
  DEBUG2: query_callback: "txtvers=1".
  DEBUG2: query_callback: "qtotal=1".
  DEBUG2: query_callback: "rp=printers/HP-Deskjet-F4500-series".
  DEBUG2: query_callback: "ty=HP Deskjet f4500 Series, hpcups 3.15.7".
  DEBUG2: query_callback: 
"adminurl=https://jcobban-server.local:631/printers/HP-Deskjet-F4500-series;.
  DEBUG2: query_callback: "note=jcobban-server".
  DEBUG2: query_callback: "priority=0".
  DEBUG2: query_callback: "product=(HP Deskjet f4500 All-in-one Printer 
Series)".
  DEBUG2: query_callback: 
"pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg,image/png,image/pwg-raster,image/urf".
  DEBUG2: query_callback: "URF=DM3".
  DEBUG2: query_callback: "UUID=d67423d3-4c38-341a-5cef-03a958e31b7e".
  DEBUG2: query_callback: "TLS=1.2".
  DEBUG2: query_callback: "Color=T".
  DEBUG2: query_callback: "printer-state=3".
  DEBUG2: query_callback: "printer-type=0x900E".
  DEBUG2: query_callback(browser=0x558f5b5aadf0, interfaceIndex=-1, 
protocol=-1, event=2, 
fullName="HP\032Deskjet\032F4500\032series\032\064\032jcobban-server._ipp._tcp.local",
 rrclass=1, rrtype=16, rdata=(nil), rdlen=0, flags=0, context=0x558f5b5a8bd0)
  DEBUG2: query_callback(browser=0x558f5b5aae90, 

[Touch-packages] [Bug 1537056] Re: apt-add-repository always returns "user or team does not exist." for ppa repos

[nPatel]

Just upgraded Ubuntu 16.04 LTS to 18.04.1 LTS. PPA that i added in
previous version, can't add it in newer and result is same as mentioned
by others "user or team does not exist."

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

Title:
  apt-add-repository always returns "user or team does not exist." for
  ppa repos

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  I have just installed a fresh Ubuntu 15.10 to my machine and run into
  trouble with adding ppa repositories using apt-add-repository:

  for e.g. running 
  apt-add-repository ppa:git-core/ppa
  Cannot add PPA: 'ppa:~git-core/ubuntu/ppa'.
  ERROR: '~git-core' user or team does not exist.

  After debugging a lot of code, I found the trouble, the used proxy-
  server needs authentification but the apt-add-repository does not
  throw a correct error message fro this case:

  The PPAException raised here seems to be interpreted as not available,
  which is rather hard to debug.

  def _get_https_content_py3(lp_url):
  print("RETRIEVING URL: %s"%lp_url)
  try:
  request = urllib.request.Request(str(lp_url), headers={"Accept":" 
application/json"})
  lp_page = urllib.request.urlopen(request, cafile=LAUNCHPAD_PPA_CERT)
  json_data = lp_page.read().decode("utf-8", "strict")
  print("RV: %s"%str(json_data))
  except (URLError, HTTPException) as e:
  # HTTPException doesn't have a reason but might have a string
  # representation
  print(e)
  reason = hasattr(e, "reason") and e.reason or e
  raise PPAException("Error reading %s: %s" % (lp_url, reason), e)

  The last print(e) gives me the hint what went wrong:
  

  For the future it would be great to get a correct error message.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1537056/+subscriptions

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

[Touch-packages] [Bug 1582251] Re: CUPS does not find network Samsung SCX-4729FD printer

[gf]

Hello again John!
On this totally different bug report, we begin the conversation again. :)

Thank you for submitting this bug and reporting a problem with cups.  You made 
this bug report some time ago and Ubuntu has been updated since then. 
 
Could you confirm that this is no longer a problem and that we can close the 
ticket? 
If it is still a problem, are you still interested in finding a solution to 
this bug? 
If you are, could you let us know, and in the current version, run the 
following (only once): 
apport-collect BUGNUMBER
and upload the updated logs and and any other logs that are relevant for this 
particular issue.  

Thank you again for helping make Ubuntu better. 
G
[Ubuntu Bug Squad volunteer triager]

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

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

Title:
  CUPS does not find network Samsung SCX-4729FD printer

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  CUPS does not find network Samsung SCX-4729FD printer i.e. one
  connected to router's ethernet socket. This error is intermittent. It
  occurs because I have to keep deleting and adding networked Samsung
  SCX-4729FD printer, due to desktop being informed that printer is not
  connected when attempting to print.

  printer-driver-splix (version 2.0.0+svn315-2fakesync1) package is
  installed.

  Add button (in Printers dialog) does not find (using Find Network
  hotspot) Samsung SCX-4729FD printer printer: it used to do so.

  Similarly, localhost:631/printers (in Firefox) does not find Samsung
  SCX-4729FD printer.

  Printer has static ip address (on my network) of 192.168.1.20

  Ping of printer shows connection is OK:
  john@Desktop:~$ ping 192.168.1.20
  PING 192.168.1.20 (192.168.1.20) 56(84) bytes of data.
  64 bytes from 192.168.1.20: icmp_seq=1 ttl=64 time=0.516 ms


  Firewall has port 631 open.

  Using Ubuntu 64 bit desktop fully up to date.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.7
  ProcVersionSignature: Ubuntu 3.13.0-86.130-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-86-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: Unity
  Date: Mon May 16 14:53:17 2016
  InstallationDate: Installed on 2014-04-25 (752 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lpstat: device for Deskjet-2540-series: 
usb://HP/Deskjet%202540%20series?serial=CN51A5721J0604=1
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Papersize: a4
  PpdFiles: Deskjet-2540-series: HP Deskjet 2540 Series, hpcups 3.14.3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-86-generic 
root=UUID=0d248ee7-6e51-4cfd-aa7e-f1963792d493 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/25/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FH
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61M-S2PV
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  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.:bvrFH:bd02/25/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-S2PV:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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.

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

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

[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

[Launchpad Bug Tracker]

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

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

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1788643] [NEW] zombies pile up, system becomes unresponsive

[Ivan Popivanov]

Public bug reported:

Description:Ubuntu 16.04.5 LTS
Release:16.04

systemd:
  Installed: 229-4ubuntu21.4
  Candidate: 229-4ubuntu21.4
  Version table:
 *** 229-4ubuntu21.4 500
500 http://azure.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 229-4ubuntu21.1 500
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
 229-4ubuntu4 500
500 http://azure.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

This problem is in Azure. We are seeing these problems on different
systems. Worker nodes (Ubuntu 16.04) in a hadoop cluster start piling up
zombies and become unresponsive. The syslog and the kernel logs don't
provide much information.

The only error we could correlate with what we are seeing was in the
audit logs. See at the end of this message, the "Connection timed out"
and the "Cannot create session: Already running in a session" messages.

Our first suspect was memory pressure on the machines. We added logging
and settings to reboot on out of memory, but all these turned to be red
herrings.

Aug 18 19:11:08 wn2-d3ncsp su[112600]: Successful su for root by root
Aug 18 19:11:08 wn2-d3ncsp su[112600]: + ??? root:root
Aug 18 19:11:08 wn2-d3ncsp su[112600]: pam_unix(su:session): session opened for 
user root by (uid=0)
Aug 18 19:11:08 wn2-d3ncsp systemd-logind[1486]: New session c8 of user root.
Aug 18 19:11:26 wn2-d3ncsp sshd[112690]: Did not receive identification string 
from 10.84.93.35
Aug 18 19:11:34 wn2-d3ncsp su[112600]: pam_systemd(su:session): Failed to 
create session: Connection timed out
Aug 18 19:11:34 wn2-d3ncsp su[112600]: pam_unix(su:session): session closed for 
user root
Aug 18 19:11:34 wn2-d3ncsp systemd-logind[1486]: Removed session c8.

 
Aug 18 19:12:03 wn2-d3ncsp sudo: ehiadmin : TTY=pts/1 ; PWD=/home/ehiadmin ; 
USER=root ; COMMAND=/bin/su -
Aug 18 19:12:03 wn2-d3ncsp sudo: pam_unix(sudo:session): session opened for 
user root by ehiadmin(uid=0)
Aug 18 19:12:03 wn2-d3ncsp su[113085]: Successful su for root by root
Aug 18 19:12:03 wn2-d3ncsp su[113085]: + /dev/pts/1 root:root
Aug 18 19:12:03 wn2-d3ncsp su[113085]: pam_unix(su:session): session opened for 
user root by ehiadmin(uid=0)
Aug 18 19:12:03 wn2-d3ncsp su[113085]: pam_systemd(su:session): Cannot create 
session: Already running in a session
Aug 18 19:12:42 wn2-d3ncsp sshd[113274]: Did not receive identification string 
from 10.84.93.42
Aug 18 19:13:37 wn2-d3ncsp su[113085]: pam_unix(su:session): session closed for 
user root
Aug 18 19:13:37 wn2-d3ncsp sudo: pam_unix(sudo:session): session closed for 
user root
Aug 18 19:13:37 wn2-d3ncsp sshd[112285]: pam_unix(sshd:session): session closed 
for user ehiadmin
Aug 18 19:13:37 wn2-d3ncsp systemd-logind[1486]: Removed session 1291.

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

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

Title:
  zombies pile up, system becomes unresponsive

Status in systemd package in Ubuntu:
  New

Bug description:
  Description:Ubuntu 16.04.5 LTS
  Release:16.04

  systemd:
Installed: 229-4ubuntu21.4
Candidate: 229-4ubuntu21.4
Version table:
   *** 229-4ubuntu21.4 500
  500 http://azure.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   229-4ubuntu21.1 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   229-4ubuntu4 500
  500 http://azure.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  This problem is in Azure. We are seeing these problems on different
  systems. Worker nodes (Ubuntu 16.04) in a hadoop cluster start piling
  up zombies and become unresponsive. The syslog and the kernel logs
  don't provide much information.

  The only error we could correlate with what we are seeing was in the
  audit logs. See at the end of this message, the "Connection timed out"
  and the "Cannot create session: Already running in a session"
  messages.

  Our first suspect was memory pressure on the machines. We added
  logging and settings to reboot on out of memory, but all these turned
  to be red herrings.

  Aug 18 19:11:08 wn2-d3ncsp su[112600]: Successful su for root by root
  Aug 18 19:11:08 wn2-d3ncsp su[112600]: + ??? root:root
  Aug 18 19:11:08 wn2-d3ncsp su[112600]: pam_unix(su:session): session opened 
for user root by (uid=0)
  Aug 18 19:11:08 wn2-d3ncsp systemd-logind[1486]: New session c8 of user root.
  Aug 18 19:11:26 wn2-d3ncsp sshd[112690]: Did not receive identification 
string from 10.84.93.35
  Aug 18 19:11:34 wn2-d3ncsp su[112600]: pam_systemd(su:session): Failed to 
create session: Connection timed out
  Aug 18 19:11:34 wn2-d3ncsp su[112600]: pam_unix(su:session): session closed 
for user root
  Aug 18 19:11:34 wn2-d3ncsp 

[Touch-packages] [Bug 1788560] Re: volledige upgrate loopt vast op systemd-shim

[Daniel Manrique]

Moving to the appropriate project

** Project changed: canonical-identity-provider => systemd-shim (Ubuntu)

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

Title:
  volledige upgrate loopt vast op systemd-shim

Status in systemd-shim package in Ubuntu:
  New

Bug description:
  installed systemd-shim package post-removal script subprocess returned
  error exit status 2

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

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

[Touch-packages] [Bug 1788560] [NEW] volledige upgrate loopt vast op systemd-shim

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

installed systemd-shim package post-removal script subprocess returned
error exit status 2

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

-- 
volledige upgrate loopt vast op systemd-shim
https://bugs.launchpad.net/bugs/1788560
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd-shim 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 1788608] Re: wget doesn't support compression, it needs zlib1g-dev

[Bug Watch Updater]

** Changed in: wget (Debian)
   Status: Unknown => New

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

Title:
  wget doesn't support compression, it needs zlib1g-dev

Status in wget package in Ubuntu:
  New
Status in wget package in Debian:
  New

Bug description:
  wget can use zlib1g for a few features, notably --compression support.
  The Debian package doesn't explicitly build-depend on zlib1g-dev, it
  gets it via libgnutls28-dev; since the Ubuntu package drops the
  latter, compression support is lost too.

  Please consider adding zlib1g-dev. (I've also asked the Debian
  maintainer to do so, see the linked bug; however the libgnutls28-dev
  removal in Ubuntu should take this into account IMO.)

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

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

[Touch-packages] [Bug 1788486] Re: apt behaviour with strict dependencies

[Eric Desrochers]

** Also affects: landscape-client (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: landscape-client (Ubuntu)
   Status: New => Won't Fix

** Changed in: landscape-client (Ubuntu Xenial)
   Status: New => Won't Fix

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

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

Title:
  apt behaviour with strict dependencies

Status in apt package in Ubuntu:
  Won't Fix
Status in landscape-client package in Ubuntu:
  Won't Fix
Status in apt source package in Xenial:
  Won't Fix
Status in landscape-client source package in Xenial:
  Won't Fix
Status in apt source package in Bionic:
  Won't Fix
Status in landscape-client source package in Bionic:
  Won't Fix

Bug description:
  [Impact]

  We notice that situation while investigating a security update using
  Landscape, but it also applies to 'apt' outside the Landscape context.

  'apt' should be smarter to detect/install packages with strict
  dependencies such as systemd[1] when a version is specified for
  upgrade (Ex: $ apt-get install systemd=229-4ubuntu-21.1).

  It should automatically install the dependencies (if any) from that
  same version as well instead of failing trying to install the highest
  version available (if any) while installing the specified version for
  the one mentionned :

  
  $ apt-get install systemd=229-4ubuntu-21.1
  
  "systemd : Depends: libsystemd0 (= 229-4ubuntu21.1) but 229-4ubuntu21.4 is to 
be installed"
  =

  To face that problem :
  - Package with lower version should be found in -security ( Ex: 
systemd/229-4ubuntu21.1 )
  - Package with higher version should be found in -updates ( Ex: 
systemd/229-4ubuntu21.4 )
  - Package should have strict dependencies ( Ex: libsystemd0 (= 
${binary:Version}) )
  - The upgrade should only specify version for the package, without it's 
dependencies. (Ex: $ apt-get install systemd=229-4ubuntu-21.1" #systemd without 
libsystemd0 depends)

  Using systemd is a good reproducer, I'm sure finding other package
  with the same situation is easy.

  It has been easily reproduced with systemd on Xenial and Bionic so
  far.

  [1] debian/control
  Depends: ${shlibs:Depends},
  ${misc:Depends},
  libsystemd0 (= ${binary:Version}),
  ...

  [Workaround]
  If package + dependencies are specified, the upgrade work just fine :

  Ex: $ apt-get install systemd=229-4ubuntu-21.1
  libsystemd0=229-4ubuntu-21.1

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

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

[Touch-packages] [Bug 1780227] Re: locking sockets broken due to missing AppArmor socket mediation patches

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.15.0-33.36

---
linux (4.15.0-33.36) bionic; urgency=medium

  * linux: 4.15.0-33.36 -proposed tracker (LP: #1787149)

  * RTNL assertion failure on ipvlan (LP: #1776927)
- ipvlan: drop ipv6 dependency
- ipvlan: use per device spinlock to protect addrs list updates
- SAUCE: fix warning from "ipvlan: drop ipv6 dependency"

  * ubuntu_bpf_jit test failed on Bionic s390x systems (LP: #1753941)
- test_bpf: flag tests that cannot be jited on s390

  * HDMI/DP audio can't work on the laptop of Dell Latitude 5495 (LP: #1782689)
- drm/nouveau: fix nouveau_dsm_get_client_id()'s return type
- drm/radeon: fix radeon_atpx_get_client_id()'s return type
- drm/amdgpu: fix amdgpu_atpx_get_client_id()'s return type
- platform/x86: apple-gmux: fix gmux_get_client_id()'s return type
- ALSA: hda: use PCI_BASE_CLASS_DISPLAY to replace PCI_CLASS_DISPLAY_VGA
- vga_switcheroo: set audio client id according to bound GPU id

  * locking sockets broken due to missing AppArmor socket mediation patches
(LP: #1780227)
- UBUNTU SAUCE: apparmor: fix apparmor mediating locking non-fs, unix 
sockets

  * Update2 for ocxl driver (LP: #1781436)
- ocxl: Fix page fault handler in case of fault on dying process

  * netns: unable to follow an interface that moves to another netns
(LP: #1774225)
- net: core: Expose number of link up/down transitions
- dev: always advertise the new nsid when the netns iface changes
- dev: advertise the new ifindex when the netns iface changes

  * [Bionic] Disk IO hangs when using BFQ as io scheduler (LP: #1780066)
- block, bfq: fix occurrences of request finish method's old name
- block, bfq: remove batches of confusing ifdefs
- block, bfq: add requeue-request hook

  * HP ProBook 455 G5 needs mute-led-gpio fixup (LP: #1781763)
- ALSA: hda: add mute led support for HP ProBook 455 G5

  * [Bionic] bug fixes to improve stability of the ThunderX2 i2c driver
(LP: #1781476)
- i2c: xlp9xx: Fix issue seen when updating receive length
- i2c: xlp9xx: Make sure the transfer size is not more than
  I2C_SMBUS_BLOCK_SIZE

  * x86/kvm: fix LAPIC timer drift when guest uses periodic mode (LP: #1778486)
- x86/kvm: fix LAPIC timer drift when guest uses periodic mode

  * Please include ax88179_178a and r8152 modules in d-i udeb (LP: #1771823)
- [Config:] d-i: Add ax88179_178a and r8152 to nic-modules

  * Nvidia fails after switching its mode (LP: #1778658)
- PCI: Restore config space on runtime resume despite being unbound

  * Kernel error "task zfs:pid blocked for more than 120 seconds" (LP: #1781364)
- SAUCE: (noup) zfs to 0.7.5-1ubuntu16.3

  * CVE-2018-12232
- PATCH 1/1] socket: close race condition between sock_close() and
  sockfs_setattr()

  * CVE-2018-10323
- xfs: set format back to extents if xfs_bmap_extents_to_btree

  * change front mic location for more lenovo m7/8/9xx machines (LP: #1781316)
- ALSA: hda/realtek - Fix the problem of two front mics on more machines
- ALSA: hda/realtek - two more lenovo models need fixup of MIC_LOCATION

  * Cephfs + fscache: unable to handle kernel NULL pointer dereference at
 IP: jbd2__journal_start+0x22/0x1f0 (LP: #1783246)
- ceph: track read contexts in ceph_file_info

  * Touchpad of ThinkPad P52 failed to work with message "lost sync at byte"
(LP: #1779802)
- Input: elantech - fix V4 report decoding for module with middle key
- Input: elantech - enable middle button of touchpads on ThinkPad P52

  * xhci_hcd :00:14.0: Root hub is not suspended (LP: #1779823)
- usb: xhci: dbc: Fix lockdep warning
- usb: xhci: dbc: Don't decrement runtime PM counter if DBC is not started

  * CVE-2018-13406
- video: uvesafb: Fix integer overflow in allocation

  * CVE-2018-10840
- ext4: correctly handle a zero-length xattr with a non-zero e_value_offs

  * CVE-2018-11412
- ext4: do not allow external inodes for inline data

  * CVE-2018-10881
- ext4: clear i_data in ext4_inode_info when removing inline data

  * CVE-2018-12233
- jfs: Fix inconsistency between memory allocation and ea_buf->max_size

  * CVE-2018-12904
- kvm: nVMX: Enforce cpl=0 for VMX instructions

  * Error parsing PCC subspaces from PCCT (LP: #1528684)
- mailbox: PCC: erroneous error message when parsing ACPI PCCT

  * CVE-2018-13094
- xfs: don't call xfs_da_shrink_inode with NULL bp

  * other users' coredumps can be read via setgid directory and killpriv bypass
(LP: #1779923) // CVE-2018-13405
- Fix up non-directory creation in SGID directories

  * Invoking obsolete 'firmware_install' target breaks snap build (LP: #1782166)
- snapcraft.yaml: stop invoking the obsolete (and non-existing)
  'firmware_install' target

  * snapcraft.yaml: missing ubuntu-retpoline-extract-one script breaks the build
(LP: #1782116)
- snapcraft.yaml: copy 

[Touch-packages] [Bug 1788486] Re: apt behaviour with strict dependencies

[Eric Desrochers]

In the attempt to workaround that behaviour at least for Landscape USN.

Would it be doable to force the package upgrade in Landscape by pocket
instead of package version ?

Fetching the package list from the USN file, then instead of ordering a
specific version, just mentioning where to go to find the package.

Ex:

apt-get install -t xenial-security systemd

instead of

apt-get install systemd=

- Eric

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

Title:
  apt behaviour with strict dependencies

Status in apt package in Ubuntu:
  Confirmed
Status in apt source package in Xenial:
  Confirmed
Status in apt source package in Bionic:
  Confirmed

Bug description:
  [Impact]

  We notice that situation while investigating a security update using
  Landscape, but it also applies to 'apt' outside the Landscape context.

  'apt' should be smarter to detect/install packages with strict
  dependencies such as systemd[1] when a version is specified for
  upgrade (Ex: $ apt-get install systemd=229-4ubuntu-21.1).

  It should automatically install the dependencies (if any) from that
  same version as well instead of failing trying to install the highest
  version available (if any) while installing the specified version for
  the one mentionned :

  
  $ apt-get install systemd=229-4ubuntu-21.1
  
  "systemd : Depends: libsystemd0 (= 229-4ubuntu21.1) but 229-4ubuntu21.4 is to 
be installed"
  =

  To face that problem :
  - Package with lower version should be found in -security ( Ex: 
systemd/229-4ubuntu21.1 )
  - Package with higher version should be found in -updates ( Ex: 
systemd/229-4ubuntu21.4 )
  - Package should have strict dependencies ( Ex: libsystemd0 (= 
${binary:Version}) )
  - The upgrade should only specify version for the package, without it's 
dependencies. (Ex: $ apt-get install systemd=229-4ubuntu-21.1" #systemd without 
libsystemd0 depends)

  Using systemd is a good reproducer, I'm sure finding other package
  with the same situation is easy.

  It has been easily reproduced with systemd on Xenial and Bionic so
  far.

  [1] debian/control
  Depends: ${shlibs:Depends},
  ${misc:Depends},
  libsystemd0 (= ${binary:Version}),
  ...

  [Workaround]
  If package + dependencies are specified, the upgrade work just fine :

  Ex: $ apt-get install systemd=229-4ubuntu-21.1
  libsystemd0=229-4ubuntu-21.1

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

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

[Touch-packages] [Bug 1788486] Re: apt behaviour with strict dependencies

[Eric Desrochers]

# apt-get install --dry-run -t xenial-security systemd
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following additional packages will be installed:
  libpam-systemd libsystemd0
Suggested packages:
  systemd-ui systemd-container
The following packages will be upgraded:
  libpam-systemd libsystemd0 systemd
3 upgraded, 0 newly installed, 0 to remove and 221 not upgraded.
Inst libpam-systemd [229-4ubuntu7] (229-4ubuntu21.1 
Ubuntu:16.04/xenial-security [amd64]) []
Inst libsystemd0 [229-4ubuntu7] (229-4ubuntu21.1 Ubuntu:16.04/xenial-security 
[amd64]) [systemd:amd64 ]
Conf libsystemd0 (229-4ubuntu21.1 Ubuntu:16.04/xenial-security [amd64]) 
[systemd:amd64 ]
Inst systemd [229-4ubuntu7] (229-4ubuntu21.1 Ubuntu:16.04/xenial-security 
[amd64])
Conf systemd (229-4ubuntu21.1 Ubuntu:16.04/xenial-security [amd64])
Conf libpam-systemd (229-4ubuntu21.1 Ubuntu:16.04/xenial-security [amd64])

# apt-get install --dry-run systemd=229-4ubuntu21.1
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 systemd : Depends: libsystemd0 (= 229-4ubuntu21.1) but 229-4ubuntu21.4 is to 
be installed
   Recommends: libpam-systemd but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

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

Title:
  apt behaviour with strict dependencies

Status in apt package in Ubuntu:
  Confirmed
Status in apt source package in Xenial:
  Confirmed
Status in apt source package in Bionic:
  Confirmed

Bug description:
  [Impact]

  We notice that situation while investigating a security update using
  Landscape, but it also applies to 'apt' outside the Landscape context.

  'apt' should be smarter to detect/install packages with strict
  dependencies such as systemd[1] when a version is specified for
  upgrade (Ex: $ apt-get install systemd=229-4ubuntu-21.1).

  It should automatically install the dependencies (if any) from that
  same version as well instead of failing trying to install the highest
  version available (if any) while installing the specified version for
  the one mentionned :

  
  $ apt-get install systemd=229-4ubuntu-21.1
  
  "systemd : Depends: libsystemd0 (= 229-4ubuntu21.1) but 229-4ubuntu21.4 is to 
be installed"
  =

  To face that problem :
  - Package with lower version should be found in -security ( Ex: 
systemd/229-4ubuntu21.1 )
  - Package with higher version should be found in -updates ( Ex: 
systemd/229-4ubuntu21.4 )
  - Package should have strict dependencies ( Ex: libsystemd0 (= 
${binary:Version}) )
  - The upgrade should only specify version for the package, without it's 
dependencies. (Ex: $ apt-get install systemd=229-4ubuntu-21.1" #systemd without 
libsystemd0 depends)

  Using systemd is a good reproducer, I'm sure finding other package
  with the same situation is easy.

  It has been easily reproduced with systemd on Xenial and Bionic so
  far.

  [1] debian/control
  Depends: ${shlibs:Depends},
  ${misc:Depends},
  libsystemd0 (= ${binary:Version}),
  ...

  [Workaround]
  If package + dependencies are specified, the upgrade work just fine :

  Ex: $ apt-get install systemd=229-4ubuntu-21.1
  libsystemd0=229-4ubuntu-21.1

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

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

[Touch-packages] [Bug 1651818] Re: busybox-initramfs needs different compile options to work with cryptroot-unlock

[Matthias Klose]

** Description changed:

+ SRU for bionic:
+ 
+ Acceptance criteria: An encrypted partition can be decrypted using
+ cryptroot-unlock.
+ 
+ Regression potential: It's not the default method, so unused by the
+ majority of people. Besides that the patched script runs fine in cosmic.
+ 
  The cryptroot-unlock script in the cryptsetup package does not work in 
initramfs.
  It fails because "ps -e" is not available in busybox for initramfs.
  When building the package with
  
  CONFIG_DESKTOP=y
  CONFIG_EXTRA_COMPAT=y
  
  the needed commands (ps, grep) with parameter are there and it works.
  Tetsted on Ubuntu GNOME 16.10.

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

Title:
  busybox-initramfs needs different compile options to work with
  cryptroot-unlock

Status in busybox package in Ubuntu:
  Won't Fix
Status in cryptsetup package in Ubuntu:
  Fix Released
Status in cryptsetup source package in Bionic:
  Confirmed

Bug description:
  SRU for bionic:

  Acceptance criteria: An encrypted partition can be decrypted using
  cryptroot-unlock.

  Regression potential: It's not the default method, so unused by the
  majority of people. Besides that the patched script runs fine in
  cosmic.

  The cryptroot-unlock script in the cryptsetup package does not work in 
initramfs.
  It fails because "ps -e" is not available in busybox for initramfs.
  When building the package with

  CONFIG_DESKTOP=y
  CONFIG_EXTRA_COMPAT=y

  the needed commands (ps, grep) with parameter are there and it works.
  Tetsted on Ubuntu GNOME 16.10.

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

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

[Touch-packages] [Bug 1784023] Re: Update profiles for usrmerge

[Andreas Hasenack]

** Merge proposal unlinked:
   
https://code.launchpad.net/~ahasenack/ubuntu/+source/strongswan/+git/strongswan/+merge/353642

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

Title:
  Update profiles for usrmerge

Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor-profiles-extra package in Ubuntu:
  New
Status in dhcpcanon package in Ubuntu:
  New
Status in ejabberd package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  In Progress
Status in fwknop package in Ubuntu:
  New
Status in i2p package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in kopanocore package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm-remote-session-freerdp2 package in Ubuntu:
  Fix Released
Status in lightdm-remote-session-x2go package in Ubuntu:
  Fix Released
Status in man-db package in Ubuntu:
  Fix Released
Status in strongswan package in Ubuntu:
  Fix Released
Status in surf package in Ubuntu:
  New
Status in telepathy-mission-control-5 package in Ubuntu:
  Fix Released
Status in strongswan package in Debian:
  New

Bug description:
  this is about / and /usr merge.

  /bin & /sbin merge is out of scope. Anything that was in /sbin/  will
  remain in /{,usr/}sbin/.

  = src:apparmor =
  usr.bin.chromium-browser appears to be out of date w.r.t. apparmor-profiles 
upstream git tree

  /usr/share/apparmor/extra-profiles/usr.sbin.useradd needs update
  upstream https://gitlab.com/apparmor/apparmor/merge_requests/152/diffs

  = other packages =

  Slightly more complete list: https://paste.ubuntu.com/p/4zDJ8mTc5Z/

  $ sudo grep '[[:space:]]/bin' -r .
  ./usr.bin.man:  /bin/bzip2 rmCx -> _filter,
  ./usr.bin.man:  /bin/gzip rmCx -> _filter,
  ./usr.bin.man:  /bin/bzip2 rm,
  ./usr.bin.man:  /bin/gzip rm,
  ./usr.sbin.libvirtd:  /bin/* PUx,
  ./abstractions/lightdm:  /bin/ rmix,
  ./abstractions/lightdm:  /bin/fusermount Px,
  ./abstractions/lightdm:  /bin/** rmix,
  ./abstractions/libvirt-qemu:  /bin/uname rmix,
  ./abstractions/libvirt-qemu:  /bin/grep rmix,
  ./usr.bin.chromium-browser:  /bin/ps Uxr,
  ./usr.bin.chromium-browser:/bin/dash ixr,
  ./usr.bin.chromium-browser:/bin/grep ixr,
  ./usr.bin.chromium-browser:/bin/readlink ixr,
  ./usr.bin.chromium-browser:/bin/sed ixr,
  ./usr.bin.chromium-browser:/bin/which ixr,
  ./usr.bin.chromium-browser:/bin/mkdir ixr,
  ./usr.bin.chromium-browser:/bin/mv ixr,
  ./usr.bin.chromium-browser:/bin/touch ixr,
  ./usr.bin.chromium-browser:/bin/dash ixr,
  ./usr.bin.firefox:  /bin/which ixr,
  ./usr.bin.firefox:  /bin/ps Uxr,
  ./usr.bin.firefox:  /bin/uname Uxr,
  ./usr.bin.firefox:/bin/dash ixr,
  ./sbin.dhclient:  /bin/bash mr,

  $ sudo grep '[[:space:]]/sbin' -r .
  ./usr.lib.telepathy:deny /sbin/ldconfig x,
  ./usr.sbin.libvirtd:  /sbin/* PUx,
  ./abstractions/lightdm:  /sbin/ r,
  ./abstractions/lightdm:  /sbin/** rmixk,
  ./usr.bin.firefox:  /sbin/killall5 ixr,
  ./sbin.dhclient:  /sbin/dhclient mr,
  ./sbin.dhclient:  # daemon to run arbitrary code via /sbin/dhclient-script, 
it would need to be
  ./sbin.dhclient:  /sbin/dhclient-script   Uxr,

  $ sudo grep '[[:space:]]/lib' -r .
  ./snap.core.4917.usr.lib.snapd.snap-confine:/lib/udev/snappy-app-dev ixr, 
# drop
  ./usr.lib.snapd.snap-confine.real:/lib/udev/snappy-app-dev ixr, # drop
  ./abstractions/lightdm:  /lib/ r,
  ./abstractions/lightdm:  /lib/** rmixk,
  ./abstractions/lightdm:  /lib32/ r,
  ./abstractions/lightdm:  /lib32/** rmixk,
  ./abstractions/lightdm:  /lib64/ r,
  ./abstractions/lightdm:  /lib64/** rmixk,
  ./usr.bin.chromium-browser:/lib/libgcc_s.so* mr,
  ./usr.bin.chromium-browser:/lib/@{multiarch}/libgcc_s.so* mr,
  ./usr.bin.chromium-browser:/lib{,32,64}/libm-*.so* mr,
  ./usr.bin.chromium-browser:/lib/@{multiarch}/libm-*.so* mr,
  ./usr.bin.chromium-browser:/lib{,32,64}/libpthread-*.so* mr,
  ./usr.bin.chromium-browser:/lib/@{multiarch}/libpthread-*.so* mr,
  ./usr.bin.chromium-browser:/lib{,32,64}/libc-*.so* mr,
  ./usr.bin.chromium-browser:/lib/@{multiarch}/libc-*.so* mr,
  ./usr.bin.chromium-browser:/lib{,32,64}/libld-*.so* mr,
  ./usr.bin.chromium-browser:/lib/@{multiarch}/libld-*.so* mr,
  ./usr.bin.chromium-browser:/lib{,32,64}/ld-*.so* mr,
  ./usr.bin.chromium-browser:/lib/@{multiarch}/ld-*.so* mr,
  ./usr.bin.chromium-browser:/lib/tls/*/{cmov,nosegneg}/libm-*.so* mr,
  ./usr.bin.chromium-browser:/lib/tls/*/{cmov,nosegneg}/libpthread-*.so* mr,
  ./usr.bin.chromium-browser:/lib/tls/*/{cmov,nosegneg}/libc-*.so* mr,

  above list might be incomplete

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

-- 
Mailing list: 

[Touch-packages] [Bug 1752411] Re: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck

[fermulator]

We should also consider:

```
# CLEAN
fermulator@fermmy:~$ host -t soa local.
Host local. not found: 3(NXDOMAIN)
fermulator@fermmy:~$ echo $?
1

# BROKEN (host hangs)
fermulator@fermmy:~$ LC_ALL=C /usr/bin/timeout 1 host -t soa local. 2>&1
fermulator@fermmy:~$ echo $?
124

# timeout
fermulator@fermmy:~$ timeout 1 sleep 2
fermulator@fermmy:~$ echo $?
124

# no timeout
fermulator@fermmy:~$ timeout 5 sleep 1
fermulator@fermmy:~$ echo $?
0
```

Isn't the existing logic broken? (perhaps insufficient
comments/documentation in this method for me to conclude either way ...
the intention maybe is unclear)

```
  if [ $? -eq 0 ] ; then
if echo "$OUT" | egrep -vq 'has no|not found'; then
  return 0
fi
  else
# Checking the dns servers failed. Assuming no .local unicast dns, but
# remove the nameserver cache so we recheck the next time we're triggered
rm -f ${NS_CACHE}
  fi

```

later it's used only here
```
if dns_has_local ; then
  # .local from dns server, disabling avahi
  disable_avahi
else
  # no .local from dns server, enabling avahi
  enable_avahi
fi
```

When host call fails (even with timeout), it returns "1" claiming 
"dns_has_local()=true".
{{{
fermulator@fermmy:~$ OUT="Host local. not found: 3(NXDOMAIN)"
fermulator@fermmy:~$ if echo "$OUT" | egrep -vq 'has no|not found'; then echo 
"RETURN 0"; else echo "RETURN 1"; fi
RETURN 1
}}}

At least the additional wrapping of timeout (workaround) doesn't make it
any worse I suppose ...

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

Title:
  bind9-host, avahi-daemon-check-dns.sh hang forever causes network
  connections to get stuck

Status in avahi package in Ubuntu:
  In Progress
Status in bind9 package in Ubuntu:
  Confirmed
Status in openconnect package in Ubuntu:
  Invalid
Status in strongswan package in Ubuntu:
  Invalid
Status in avahi source package in Bionic:
  Triaged
Status in bind9 source package in Bionic:
  Confirmed
Status in avahi source package in Cosmic:
  In Progress
Status in bind9 source package in Cosmic:
  Confirmed
Status in avahi package in Debian:
  New

Bug description:
  [Impact]

   * Network connections for some users fail (in some cases a direct
  interface, in others when connecting a VPN) because the 'host' command
  to check for .local in DNS called by /usr/lib/avahi/avahi-daemon-
  check-dns.sh never times out like it should - leaving the script
  hanging indefinitely blocking interface up and start-up. This appears
  to be a bug in host caused in some circumstances however we implement
  a workaround to call it under 'timeout' as the issue with 'host' has
  not easily been identified, and in any case acts as a fall-back.

  [Test Case]

   * Multiple people have been unable to create a reproducer on a
  generic machine (e.g. it does not occur in a VM), I have a specific
  machine I can reproduce it on (a Skull Canyon NUC with Intel I219-LM)
  by simply "ifdown br0; ifup br0" and there are clearly 10s of other
  users affected in varying circumstances that all involve the same
  symptoms but no clear test case exists. Best I can suggest is that I
  test the patch on my system to ensure it works as expected, and the
  change is only 1 line which is fairly easily auditible and
  understandable.

  [Regression Potential]

   * The change is a single line change to the shell script to call host with 
"timeout". When tested on working and non-working system this appears to 
function as expected. I believe the regression potential for this is 
subsequently low.
   * In attempt to anticipate possible issues, I checked that the timeout 
command is in the same path (/usr/bin) as the host command that is already 
called without a path, and the coreutils package (which contains timeout) is an 
Essential package. I also checked that timeout is not a built-in in bash, for 
those that have changed /bin/sh to bash (just in case).

  [Other Info]
   
   * N/A

  [Original Bug Description]

  On 18.04 Openconnect connects successfully to any of multiple VPN
  concentrators but network traffic does not flow across the VPN tunnel
  connection. When testing on 16.04 this works flawlessly. This also
  worked on this system when it was on 17.10.

  I have tried reducing the mtu of the tun0 network device but this has
  not resulted in me being able to successfully ping the IP address.

  Example showing ping attempt to the IP of DNS server:

  ~$ 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 172.29.88.11
  nameserver 127.0.0.53

  liam@liam-lat:~$ netstat -nr
  Kernel IP routing table
  Destination Gateway 

[Touch-packages] [Bug 1752411] Re: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck

[ Christian Ehrhardt ]

Hi fermulator,
I was wondering vice versa if 5 seconds would be too short actually.
Yes the good cases will return in sub-second, but it is the bad cases we want 
to fix here.
Having a bit more time to recover if it can doesn't seem too bad to me.

On the question of host -W for waiting.
While it isn't fully clarified, we have to consider that in this case there is 
a real hang inside host or one of its syscalls due to the odd states the 
devices are in.
That said it could be that the call just blocks forever and a "host internal" 
timeout would never trigger leaving the system in just the bad state it is now.

Instead the external timeout wrapper should be immune to that, and
therefore is better for this case.

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

Title:
  bind9-host, avahi-daemon-check-dns.sh hang forever causes network
  connections to get stuck

Status in avahi package in Ubuntu:
  In Progress
Status in bind9 package in Ubuntu:
  Confirmed
Status in openconnect package in Ubuntu:
  Invalid
Status in strongswan package in Ubuntu:
  Invalid
Status in avahi source package in Bionic:
  Triaged
Status in bind9 source package in Bionic:
  Confirmed
Status in avahi source package in Cosmic:
  In Progress
Status in bind9 source package in Cosmic:
  Confirmed
Status in avahi package in Debian:
  New

Bug description:
  [Impact]

   * Network connections for some users fail (in some cases a direct
  interface, in others when connecting a VPN) because the 'host' command
  to check for .local in DNS called by /usr/lib/avahi/avahi-daemon-
  check-dns.sh never times out like it should - leaving the script
  hanging indefinitely blocking interface up and start-up. This appears
  to be a bug in host caused in some circumstances however we implement
  a workaround to call it under 'timeout' as the issue with 'host' has
  not easily been identified, and in any case acts as a fall-back.

  [Test Case]

   * Multiple people have been unable to create a reproducer on a
  generic machine (e.g. it does not occur in a VM), I have a specific
  machine I can reproduce it on (a Skull Canyon NUC with Intel I219-LM)
  by simply "ifdown br0; ifup br0" and there are clearly 10s of other
  users affected in varying circumstances that all involve the same
  symptoms but no clear test case exists. Best I can suggest is that I
  test the patch on my system to ensure it works as expected, and the
  change is only 1 line which is fairly easily auditible and
  understandable.

  [Regression Potential]

   * The change is a single line change to the shell script to call host with 
"timeout". When tested on working and non-working system this appears to 
function as expected. I believe the regression potential for this is 
subsequently low.
   * In attempt to anticipate possible issues, I checked that the timeout 
command is in the same path (/usr/bin) as the host command that is already 
called without a path, and the coreutils package (which contains timeout) is an 
Essential package. I also checked that timeout is not a built-in in bash, for 
those that have changed /bin/sh to bash (just in case).

  [Other Info]
   
   * N/A

  [Original Bug Description]

  On 18.04 Openconnect connects successfully to any of multiple VPN
  concentrators but network traffic does not flow across the VPN tunnel
  connection. When testing on 16.04 this works flawlessly. This also
  worked on this system when it was on 17.10.

  I have tried reducing the mtu of the tun0 network device but this has
  not resulted in me being able to successfully ping the IP address.

  Example showing ping attempt to the IP of DNS server:

  ~$ 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 172.29.88.11
  nameserver 127.0.0.53

  liam@liam-lat:~$ netstat -nr
  Kernel IP routing table
  Destination Gateway Genmask Flags   MSS Window  irtt Iface
  0.0.0.0 192.168.1.1 0.0.0.0 UG0 0  0 
wlp2s0
  105.27.198.106  192.168.1.1 255.255.255.255 UGH   0 0  0 
wlp2s0
  169.254.0.0 0.0.0.0 255.255.0.0 U 0 0  0 
docker0
  172.17.0.0  0.0.0.0 255.255.0.0 U 0 0  0 
docker0
  172.29.0.0  0.0.0.0 255.255.0.0 U 0 0  0 tun0
  172.29.88.110.0.0.0 255.255.255.255 UH0 0  0 tun0
  192.168.1.0 0.0.0.0 255.255.255.0   U 0 0  0 
wlp2s0
  liam@liam-lat:~$ ping 172.29.88.11
  PING 172.29.88.11 (172.29.88.11) 56(84) bytes of data.
  ^C
  --- 172.29.88.11 ping statistics ---
 

[Touch-packages] [Bug 1583997] Re: cannot print correctly on HP Deskjet 840C

[gf]

Hello Reinach,
Thank you for submitting this bug and reporting a problem with cups.  You made 
this bug report some time ago and Ubuntu has been updated since then. 
 
Could you confirm that this is no longer a problem and that we can close the 
ticket? 
If it is still a problem, are you still interested in finding a solution to 
this bug? 
If you are, could you let us know, and in the current version, run the 
following (only once): 
apport-collect BUGNUMBER
and upload the updated logs and and any other logs that are relevant for this 
particular issue.  

Thank you again for helping make Ubuntu better. 
G
[Ubuntu Bug Squad volunteer triager]

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

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

Title:
  cannot print correctly on HP Deskjet 840C

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  I have some problems printing with HP Deskjet 840C. At times I can
  print correctly while at times I have problems mainly with pdf files.
  Sometimes they will not be printed at all (the status says "waiting"
  or "cancelled"). Sometimes some pages get printed and the others fail.

  I recently installed HP Tools and while initially I could print fine,
  now it doesn't print at all or it prints ALL pages while I choose a
  range of pages. I installed and reinstalled the printer and the HP
  Tools to no avail.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.7
  ProcVersionSignature: Ubuntu 3.13.0-87.132-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-87-generic i686
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: i386
  CurrentDesktop: Unity
  Date: Fri May 20 12:45:42 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-01-02 (868 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  Lpstat: device for HP_DeskJet_840C: hp:/usb/DeskJet_840C?serial=HU0292N111LW
  MachineType: TOSHIBA Satellite A300
  Papersize: a4
  PpdFiles: HP_DeskJet_840C: HP DeskJet 840C - CUPS+Gutenprint v5.2.10-pre2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-87-generic 
root=UUID=0554b137-c865-40cf-a427-1501c7ec954f ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to trusty on 2014-06-24 (695 days ago)
  dmi.bios.date: 04/14/2008
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: V2.70
  dmi.board.name: Satellite A300
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrV2.70:bd04/14/2008:svnTOSHIBA:pnSatelliteA300:pvrPSAJ4E-01U00NGE:rvnTOSHIBA:rnSatelliteA300:rvrNotApplicable:cvnTOSHIBA:ct1:cvrN/A:
  dmi.product.name: Satellite A300
  dmi.product.version: PSAJ4E-01U00NGE
  dmi.sys.vendor: TOSHIBA

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

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

[Touch-packages] [Bug 1788597] Re: ubiquity broken with console-setup 1.178ubuntu2.5

[Jean-Baptiste Lallement]

** Changed in: console-setup (Ubuntu)
   Importance: Undecided => Critical

** Tags added: rls-cc-incoming

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

Title:
  ubiquity broken with console-setup 1.178ubuntu2.5

Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  Since this version of console-setup in bionic ubiquity now skips the
  Keyboard and Wireless pages.

  http://launchpadlibrarian.net/382474004/console-
  setup_1.178ubuntu2.4_1.178ubuntu2.5.diff.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1788597/+subscriptions

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

[Touch-packages] [Bug 1788486] Re: apt behaviour with strict dependencies

[Julian Andres Klode]

FWIW, the real approach would be to follow unattended-upgrades and write
a GPLed script that uses python-apt and adjusts the candidates. Then
(copy and? - no real idea how landscape works) invoke that on the
system.

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

Title:
  apt behaviour with strict dependencies

Status in apt package in Ubuntu:
  Won't Fix
Status in landscape-client package in Ubuntu:
  Won't Fix
Status in apt source package in Xenial:
  Won't Fix
Status in landscape-client source package in Xenial:
  Won't Fix
Status in apt source package in Bionic:
  Won't Fix
Status in landscape-client source package in Bionic:
  Won't Fix

Bug description:
  [Impact]

  We notice that situation while investigating a security update using
  Landscape, but it also applies to 'apt' outside the Landscape context.

  'apt' should be smarter to detect/install packages with strict
  dependencies such as systemd[1] when a version is specified for
  upgrade (Ex: $ apt-get install systemd=229-4ubuntu-21.1).

  It should automatically install the dependencies (if any) from that
  same version as well instead of failing trying to install the highest
  version available (if any) while installing the specified version for
  the one mentionned :

  
  $ apt-get install systemd=229-4ubuntu-21.1
  
  "systemd : Depends: libsystemd0 (= 229-4ubuntu21.1) but 229-4ubuntu21.4 is to 
be installed"
  =

  To face that problem :
  - Package with lower version should be found in -security ( Ex: 
systemd/229-4ubuntu21.1 )
  - Package with higher version should be found in -updates ( Ex: 
systemd/229-4ubuntu21.4 )
  - Package should have strict dependencies ( Ex: libsystemd0 (= 
${binary:Version}) )
  - The upgrade should only specify version for the package, without it's 
dependencies. (Ex: $ apt-get install systemd=229-4ubuntu-21.1" #systemd without 
libsystemd0 depends)

  Using systemd is a good reproducer, I'm sure finding other package
  with the same situation is easy.

  It has been easily reproduced with systemd on Xenial and Bionic so
  far.

  [1] debian/control
  Depends: ${shlibs:Depends},
  ${misc:Depends},
  libsystemd0 (= ${binary:Version}),
  ...

  [Workaround]
  If package + dependencies are specified, the upgrade work just fine :

  Ex: $ apt-get install systemd=229-4ubuntu-21.1
  libsystemd0=229-4ubuntu-21.1

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

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

[Touch-packages] [Bug 1774651] Re: Ubuntu 18.04: click: install updates before shutdown, enter disk password

[Amr Ibrahim]

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

** This bug has been marked a duplicate of bug 1775226
   [SRU] Gnome Software offers installation of updates on shutdown 
independently from update-manager and unattended-upgrades

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

Title:
  Ubuntu 18.04: click: install updates before shutdown, enter disk
  password

Status in packagekit package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04 with disk-encryption, when (security) updates are
  available but not installed, then the shutdown- menu gives the option
  to "install updates before shutdown" selecting this option takes you
  to the disk-encrytion password screen before installing updates and
  shutdown.

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

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

[Touch-packages] [Bug 1771598] Re: package sudo 1.8.21p2-3ubuntu1 failed to install/upgrade: installed sudo package pre-removal script subprocess returned error exit status 1

[Balint Reczey]

You were trying to remove sudo and it warns about not existing root
password in DpkgTerminalLog.txt:

Removing sudo (1.8.21p2-3ubuntu1) ...
You have asked that the sudo package be removed,
but no root password has been set.
Without sudo, you may not be able to gain administrative privileges.

If you would prefer to access the root account with su(1)
or by logging in directly,
you must set a root password with "sudo passwd".

If you have arranged other means to access the root account,
and you are sure this is what you want,
you may bypass this check by setting an environment variable 
(export SUDO_FORCE_REMOVE=yes).

Refusing to remove sudo.
dpkg: error processing package sudo (--remove):
 installed sudo package pre-removal script subprocess returned error exit 
status 1

It is not clear what you did to your system and what does not work,
please try seeking for help on Ubuntu user forums or mailing lists.


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

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

Title:
  package sudo 1.8.21p2-3ubuntu1 failed to install/upgrade: installed
  sudo package pre-removal script subprocess returned error exit status
  1

Status in sudo package in Ubuntu:
  Invalid

Bug description:
  Hi, I tried editing the sudoers that is located on my Ubuntu setup on
  Virtual Box, it didn't allow me to update sudoers due to permission
  issues. I changed the permission of sudoers to 777 and was able to add
  my user name into it, however after that I was not able to run few
  commands hence I got instruction from google to purge and re-install
  it however it started throwing error afterwards however I noticed that
  I was able to remove my username entries from it before re-installing.
  Please suggest if I would need to re-install ubuntu on my virtual box
  or the current setup would work as before ?

  Thanks,
  Mahesh Bhatia

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: sudo 1.8.21p2-3ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  AptOrdering:
   ubuntu-minimal:amd64: Purge
   sudo:amd64: Purge
   NULL: ConfigurePending
   NULL: PurgePending
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed May 16 16:17:51 2018
  ErrorMessage: installed sudo package pre-removal script subprocess returned 
error exit status 1
  InstallationDate: Installed on 2018-05-15 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: sudo
  Title: package sudo 1.8.21p2-3ubuntu1 failed to install/upgrade: installed 
sudo package pre-removal script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   /etc/sudoers: parsed OK
   /etc/sudoers.d/README: parsed OK
  mtime.conffile..etc.sudoers: 2018-05-16T16:12:29.233258

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

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

[Touch-packages] [Bug 1788602] Re: package base-files 10.1ubuntu2.2 failed to install/upgrade: fim de ficheiro em stdin na prompt do ficheiro de configuração

[Steve Langasek]

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

This appears to be the same as bug #1788192: you are both being shown
conffile prompts about unmodified conffiles.  This should never happen.
You should be able to handle this problem by manually running 'sudo apt
upgrade' from a shell, but it's still very unclear why these prompts are
being shown at all.

** This bug has been marked a duplicate of bug 1788192
   package base-files 10.1ubuntu2.2 failed to install/upgrade: end of file on 
stdin at conffile prompt

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

Title:
  package base-files 10.1ubuntu2.2 failed to install/upgrade: fim de
  ficheiro em stdin na prompt do ficheiro de configuração

Status in base-files package in Ubuntu:
  New

Bug description:
  Ubuntu Community would like the help of you to solve this problem

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: base-files 10.1ubuntu2.2
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  AptOrdering:
   base-files:amd64: Install
   base-files:amd64: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Aug 23 08:53:13 2018
  Dependencies:
   
  ErrorMessage: fim de ficheiro em stdin na prompt do ficheiro de configuração
  Python3Details: /usr/bin/python3.6, Python 3.6.5, unpackaged
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: base-files
  Title: package base-files 10.1ubuntu2.2 failed to install/upgrade: fim de 
ficheiro em stdin na prompt do ficheiro de configuração
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.update-motd.d.50-motd-news: 2018-04-09T08:10:28

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1788602/+subscriptions

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

[Touch-packages] [Bug 1784023] Re: Update profiles for usrmerge

[Andreas Hasenack]

** Merge proposal unlinked:
   
https://code.launchpad.net/~ahasenack/ubuntu/+source/strongswan/+git/strongswan/+merge/353642

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

Title:
  Update profiles for usrmerge

Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor-profiles-extra package in Ubuntu:
  New
Status in dhcpcanon package in Ubuntu:
  New
Status in ejabberd package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  In Progress
Status in fwknop package in Ubuntu:
  New
Status in i2p package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in kopanocore package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm-remote-session-freerdp2 package in Ubuntu:
  Fix Released
Status in lightdm-remote-session-x2go package in Ubuntu:
  Fix Released
Status in man-db package in Ubuntu:
  Fix Released
Status in strongswan package in Ubuntu:
  Fix Released
Status in surf package in Ubuntu:
  New
Status in telepathy-mission-control-5 package in Ubuntu:
  Fix Released
Status in strongswan package in Debian:
  New

Bug description:
  this is about / and /usr merge.

  /bin & /sbin merge is out of scope. Anything that was in /sbin/  will
  remain in /{,usr/}sbin/.

  = src:apparmor =
  usr.bin.chromium-browser appears to be out of date w.r.t. apparmor-profiles 
upstream git tree

  /usr/share/apparmor/extra-profiles/usr.sbin.useradd needs update
  upstream https://gitlab.com/apparmor/apparmor/merge_requests/152/diffs

  = other packages =

  Slightly more complete list: https://paste.ubuntu.com/p/4zDJ8mTc5Z/

  $ sudo grep '[[:space:]]/bin' -r .
  ./usr.bin.man:  /bin/bzip2 rmCx -> _filter,
  ./usr.bin.man:  /bin/gzip rmCx -> _filter,
  ./usr.bin.man:  /bin/bzip2 rm,
  ./usr.bin.man:  /bin/gzip rm,
  ./usr.sbin.libvirtd:  /bin/* PUx,
  ./abstractions/lightdm:  /bin/ rmix,
  ./abstractions/lightdm:  /bin/fusermount Px,
  ./abstractions/lightdm:  /bin/** rmix,
  ./abstractions/libvirt-qemu:  /bin/uname rmix,
  ./abstractions/libvirt-qemu:  /bin/grep rmix,
  ./usr.bin.chromium-browser:  /bin/ps Uxr,
  ./usr.bin.chromium-browser:/bin/dash ixr,
  ./usr.bin.chromium-browser:/bin/grep ixr,
  ./usr.bin.chromium-browser:/bin/readlink ixr,
  ./usr.bin.chromium-browser:/bin/sed ixr,
  ./usr.bin.chromium-browser:/bin/which ixr,
  ./usr.bin.chromium-browser:/bin/mkdir ixr,
  ./usr.bin.chromium-browser:/bin/mv ixr,
  ./usr.bin.chromium-browser:/bin/touch ixr,
  ./usr.bin.chromium-browser:/bin/dash ixr,
  ./usr.bin.firefox:  /bin/which ixr,
  ./usr.bin.firefox:  /bin/ps Uxr,
  ./usr.bin.firefox:  /bin/uname Uxr,
  ./usr.bin.firefox:/bin/dash ixr,
  ./sbin.dhclient:  /bin/bash mr,

  $ sudo grep '[[:space:]]/sbin' -r .
  ./usr.lib.telepathy:deny /sbin/ldconfig x,
  ./usr.sbin.libvirtd:  /sbin/* PUx,
  ./abstractions/lightdm:  /sbin/ r,
  ./abstractions/lightdm:  /sbin/** rmixk,
  ./usr.bin.firefox:  /sbin/killall5 ixr,
  ./sbin.dhclient:  /sbin/dhclient mr,
  ./sbin.dhclient:  # daemon to run arbitrary code via /sbin/dhclient-script, 
it would need to be
  ./sbin.dhclient:  /sbin/dhclient-script   Uxr,

  $ sudo grep '[[:space:]]/lib' -r .
  ./snap.core.4917.usr.lib.snapd.snap-confine:/lib/udev/snappy-app-dev ixr, 
# drop
  ./usr.lib.snapd.snap-confine.real:/lib/udev/snappy-app-dev ixr, # drop
  ./abstractions/lightdm:  /lib/ r,
  ./abstractions/lightdm:  /lib/** rmixk,
  ./abstractions/lightdm:  /lib32/ r,
  ./abstractions/lightdm:  /lib32/** rmixk,
  ./abstractions/lightdm:  /lib64/ r,
  ./abstractions/lightdm:  /lib64/** rmixk,
  ./usr.bin.chromium-browser:/lib/libgcc_s.so* mr,
  ./usr.bin.chromium-browser:/lib/@{multiarch}/libgcc_s.so* mr,
  ./usr.bin.chromium-browser:/lib{,32,64}/libm-*.so* mr,
  ./usr.bin.chromium-browser:/lib/@{multiarch}/libm-*.so* mr,
  ./usr.bin.chromium-browser:/lib{,32,64}/libpthread-*.so* mr,
  ./usr.bin.chromium-browser:/lib/@{multiarch}/libpthread-*.so* mr,
  ./usr.bin.chromium-browser:/lib{,32,64}/libc-*.so* mr,
  ./usr.bin.chromium-browser:/lib/@{multiarch}/libc-*.so* mr,
  ./usr.bin.chromium-browser:/lib{,32,64}/libld-*.so* mr,
  ./usr.bin.chromium-browser:/lib/@{multiarch}/libld-*.so* mr,
  ./usr.bin.chromium-browser:/lib{,32,64}/ld-*.so* mr,
  ./usr.bin.chromium-browser:/lib/@{multiarch}/ld-*.so* mr,
  ./usr.bin.chromium-browser:/lib/tls/*/{cmov,nosegneg}/libm-*.so* mr,
  ./usr.bin.chromium-browser:/lib/tls/*/{cmov,nosegneg}/libpthread-*.so* mr,
  ./usr.bin.chromium-browser:/lib/tls/*/{cmov,nosegneg}/libc-*.so* mr,

  above list might be incomplete

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

-- 
Mailing list: 

[Touch-packages] [Bug 1788658] [NEW] Videos (Totem)

[Ed Lewis]

Public bug reported:

works, but with lots of stutter

same problem with all three computers running current and fully updated
Ubuntu

VLC is fine but I like Videos

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 23 12:33:55 2018
DistUpgraded: 2018-05-02 18:26:01,704 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
DistroCodename: bionic
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0535]
InstallationDate: Installed on 2017-11-24 (271 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: Dell Inc. Latitude E6530
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=92f668d2-1882-408b-a814-61e23a9171ae ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to bionic on 2018-05-02 (112 days ago)
dmi.bios.date: 04/24/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A02
dmi.board.name: 0JC5MT
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd04/24/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn0JC5MT:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6530
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-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

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  Videos (Totem)

Status in xorg package in Ubuntu:
  New

Bug description:
  works, but with lots of stutter

  same problem with all three computers running current and fully
  updated Ubuntu

  VLC is fine but I like Videos

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 23 12:33:55 2018
  DistUpgraded: 2018-05-02 18:26:01,704 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0535]
  InstallationDate: Installed on 2017-11-24 (271 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Dell Inc. Latitude E6530
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=92f668d2-1882-408b-a814-61e23a9171ae ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (112 days ago)
  dmi.bios.date: 04/24/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0JC5MT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd04/24/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn0JC5MT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6530
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  

[Touch-packages] [Bug 1788659] [NEW] network manager assigns ethernet default route metric of 20100

[Josh Hill]

Public bug reported:

After upgrading from 16.04 to 18.04, when I boot with an ethernet cable
connected, Ubuntu prefers to use the wifi interface over the ethernet
interface. Wifi is assigned the normal metric of 600 for both of its
routing table entries. However ethernet is assigned a metric of 20100.

I edited the connection details via nmcli to manually set the ethernet
metric to 100. After a reboot, the link route (for the LAN subnet)
correctly has a metric of 100. But the default route for eth0 is still
20100.

nm-applet shows the wifi icon, correctly indicating that the default
route is over wifi rather than ethernet. The only fix is to manually set
the route after every reboot, or turn off wifi. This is a regression
from 16.04.

network-manager 1.10.6-2ubuntu1

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

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

Title:
  network manager assigns ethernet default route metric of 20100

Status in network-manager package in Ubuntu:
  New

Bug description:
  After upgrading from 16.04 to 18.04, when I boot with an ethernet
  cable connected, Ubuntu prefers to use the wifi interface over the
  ethernet interface. Wifi is assigned the normal metric of 600 for both
  of its routing table entries. However ethernet is assigned a metric of
  20100.

  I edited the connection details via nmcli to manually set the ethernet
  metric to 100. After a reboot, the link route (for the LAN subnet)
  correctly has a metric of 100. But the default route for eth0 is still
  20100.

  nm-applet shows the wifi icon, correctly indicating that the default
  route is over wifi rather than ethernet. The only fix is to manually
  set the route after every reboot, or turn off wifi. This is a
  regression from 16.04.

  network-manager 1.10.6-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1788659/+subscriptions

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

[Touch-packages] [Bug 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable

[Colan Schwartz]

Ah, thanks!  I must have been reading too fast. ;)

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

Title:
  Alt+left/right arrows switch between tty consoles (Gnome Shell
  vanishes), cannot disable

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I'm used to using alt+left/right arrow to navigate back and forward in
  web browsers and elsewhere (nautilus)...  But on this fresh install of
  Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty
  consoles (the ctrl+alt+f1 ones).  But it's not listed as one of the
  shortcuts in the "keyboard" menu, so I don't know how to disable it...

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

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

[Touch-packages] [Bug 1697160] Re: add function to be able to copy text from error summary dialog

[spm2011]

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

** This bug has been marked a duplicate of bug 1273752
   Can't Copy Crash Report Details to Clipboard

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

Title:
  add function to be able to copy text from error summary dialog

Status in apport package in Ubuntu:
  New

Bug description:
  It'd be nice to have a function to be able to copy text from the error
  summary dialog.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: apport-gtk 2.20.4-0ubuntu4.1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Sat Jun 10 12:55:31 2017
  InstallationDate: Installed on 2015-12-12 (545 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to zesty on 2017-05-01 (39 days ago)

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

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

[Touch-packages] [Bug 1770686] Re: Hide livepatch widgets in flavors without an online account panel in gnome-control-center

[Łukasz Zemczak]

Hello Andrea, or anyone else affected,

Accepted software-properties into bionic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/software-properties/0.96.24.32.5 in a few hours, and then in the
-proposed repository.

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

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

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

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

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

Title:
  Hide livepatch widgets in flavors without an online account panel in
  gnome-control-center

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Bionic:
  Fix Committed

Bug description:
  
  [Impact]
  Some distributions ship software-properties-gtk but not gnome-control-center. 
Considering that Livepatch strictly depends on the online account panel in 
gnome-control-center we should not show the option to enable Livepatch if those 
distributions, otherwise enabling Livepatch will fail and it will seem buggy.

  [Test Case]
  1. Start xubuntu (Bionic)
  2. Open software-properties-gtk
  3. Go to "Updates" tab
  4. Make sure no Livepatch UI is displayed

  [Regression Potential] 
  Please make sure the Livepatch UI is correctly displayed in vanilla Bionic.

  [Original Bug Report]

  Unfortunately Livepatch strictly depends on the online account panel
  in gnome-control-center. We should hide the checkbutton in flavors
  (e.g. Xubuntu) that do not ship gnome-control-center and/or the online
  account panel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1770686/+subscriptions

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

[Touch-packages] [Bug 1651818] Re: busybox-initramfs needs different compile options to work with cryptroot-unlock

[Łukasz Zemczak]

Hello Linuxrider, or anyone else affected,

Accepted cryptsetup into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/cryptsetup/2:2.0.2-1ubuntu1.1 in a
few hours, and then in the -proposed repository.

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

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

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

** Changed in: cryptsetup (Ubuntu Bionic)
   Status: Confirmed => Fix Committed

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

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

Title:
  busybox-initramfs needs different compile options to work with
  cryptroot-unlock

Status in busybox package in Ubuntu:
  Won't Fix
Status in cryptsetup package in Ubuntu:
  Fix Released
Status in cryptsetup source package in Bionic:
  Fix Committed

Bug description:
  SRU for bionic:

  Acceptance criteria: An encrypted partition can be decrypted using
  cryptroot-unlock.

  Regression potential: It's not the default method, so unused by the
  majority of people. Besides that the patched script runs fine in
  cosmic.

  The cryptroot-unlock script in the cryptsetup package does not work in 
initramfs.
  It fails because "ps -e" is not available in busybox for initramfs.
  When building the package with

  CONFIG_DESKTOP=y
  CONFIG_EXTRA_COMPAT=y

  the needed commands (ps, grep) with parameter are there and it works.
  Tetsted on Ubuntu GNOME 16.10.

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

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

[Touch-packages] [Bug 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable

[Janne Snabb]

$ apt-file search kbd_mode
kbd: /bin/kbd_mode
kbd: /usr/share/man/man1/kbd_mode.1.gz
[..]

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

Title:
  Alt+left/right arrows switch between tty consoles (Gnome Shell
  vanishes), cannot disable

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I'm used to using alt+left/right arrow to navigate back and forward in
  web browsers and elsewhere (nautilus)...  But on this fresh install of
  Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty
  consoles (the ctrl+alt+f1 ones).  But it's not listed as one of the
  shortcuts in the "keyboard" menu, so I don't know how to disable it...

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

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

[Touch-packages] [Bug 1769301] Re: resetting /proc/thread-self/attr/fscreate results in 'Invalid Argument'

[Igor Klyuchnikov]

Got the same problem. It looks like the problem is in the kernel 4.15
with Canonical patches. Vanilla 4.15, built from source, has no problem
with useradd. Ubuntu 16.04 LTS kernel 4.13 generic, built from source,
is also  ok. I've spent plenty of time trying to make it work.

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

Title:
  resetting /proc/thread-self/attr/fscreate results in 'Invalid
  Argument'

Status in libselinux package in Ubuntu:
  New

Bug description:
  root@ubuntu:~# useradd -g 100 tst003
  useradd: failure while writing changes to /etc/passwd

  root@ubuntu:~# sestatus 
  SELinux status: enabled
  SELinuxfs mount:/sys/fs/selinux
  SELinux root directory: /etc/selinux
  Loaded policy name: default
  Current mode:   permissive
  Mode from config file:  permissive
  Policy MLS status:  enabled
  Policy deny_unknown status: allowed
  Memory protection checking: requested (insecure)
  Max kernel policy version:  31

  
  The problem does not occur when SELinux is complete disabled.

  Please note that a very similar problem occurs using groupadd:

  root@ubuntu:~# groupadd tstgrp001
  groupadd: failure while writing changes to /etc/group

  
  = journal = 
  (Please note that there is *no* AVC!)

  May 05 05:11:44 ubuntu useradd[756]: new user: name=tst003, UID=1004, 
GID=100, home=/home/tst003, shell=/bin/sh
  May 05 05:11:44 ubuntu audit[756]: ADD_USER pid=756 uid=0 auid=1002 ses=1 
subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=adding user 
id=1004 exe="/usr/sbin/useradd" hostname=ubuntu addr=? terminal=pts/0 
res=success'
  May 05 05:11:44 ubuntu useradd[756]: failure while writing changes to 
/etc/passwd
  May 05 05:11:44 ubuntu audit[756]: ADD_USER pid=756 uid=0 auid=1002 ses=1 
subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=adding user 
acct="tst003" exe="/usr/sbin/useradd" hostname=ubuntu addr=? terminal=pts/0 
res=failed'
  May 05 05:11:44 ubuntu useradd[756]: failed adding user 'tst003', data deleted

  = ltrace =

  [pid 1074] SYS_write(12, "root:x:"..., 1360) = 1360
  [pid 1074] <... fflush resumed> )= 0
  [pid 1074] fileno(0x5595b21c6200)= 12
  [pid 1074] fsync(12, 0x5595b21c62e0, 0, 0x7ff933d5c154 
  [pid 1074] SYS_fsync(12) = 0
  [pid 1074] <... fsync resumed> ) = 0
  [pid 1074] fclose(0x5595b21c6200 
  [pid 1074] SYS_close(12) = 0
  [pid 1074] <... fclose resumed> )= 0
  [pid 1074] utime(0x7ffee34207e0, 0x7ffee34206b0, 0x5595b21af010, 1 

  [pid 1074] SYS_utime("/etc/passwd-", 0x7ffee34206b0) = 0
  [pid 1074] <... utime resumed> ) = 0
  [pid 1074] fclose(0x5595b21af2a0 
  [pid 1074] SYS_close(5)  = 0
  [pid 1074] <... fclose resumed> )= 0
  [pid 1074] setfscreatecon(0, 0x5595b21af118, 1, 2 
  [pid 1074] SYS_openat(0xff9c, 0x5595b21cebc0, 0x80002, 0) = 5
  [pid 1074] SYS_write(5, nil, 0)  = -22
  [pid 1074] SYS_close(5)  = 0
  [pid 1074] <... setfscreatecon resumed> )= 0x
  [pid 1074] free(0x5595b21b9dc0)  = 
  [pid 1074] free(0x5595b21b8a00)  = 
  [pid 1074] strlen("x")   = 1
  [pid 1074] memset(0x5595b21b7560, '\0', 1)   = 0x5595b21b7560
  [pid 1074] free(0x5595b21b7560)  = 
  [pid 1074] free(0x5595b21b94e0)  = 
  [pid 1074] free(0x5595b21b9000)  = 
  [pid 1074] free(0x5595b21b8fc0)  = 

  = strace =

  write(12, "root:x:"..., 1360) = 1360
  fsync(12)   = 0
  close(12)   = 0
  utime("/etc/passwd-", {actime=1525497034 /* 2018-05-05T05:10:34+ */, 
modtime=1525496803 /* 2018-05-05T05:06:43+ */}) = 0
  close(5)= 0
  openat(AT_FDCWD, "/proc/thread-self/attr/fscreate", O_RDWR|O_CLOEXEC) = 5
  write(5, NULL, 0)   = -1 EINVAL (Invalid argument)
  close(5)= 0

  = Version Information =
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  root@ubuntu:~# dpkg -l | grep passwd | grep -v base-pa
  ii  passwd1:4.5-1ubuntu1
amd64change and administer password and group data

  root@ubuntu:~# dpkg -l | grep selinux
  ii  libselinux1:amd64 2.7-2build2   
amd64SELinux runtime shared libraries
  ii  python3-selinux   2.7-2build2   
amd64Python3 bindings to SELinux shared libraries
  ii  selinux-basics0.5.6   

[Touch-packages] [Bug 1784023] Re: Update profiles for usrmerge

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~ahasenack/ubuntu/+source/strongswan/+git/strongswan/+merge/353642

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

Title:
  Update profiles for usrmerge

Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor-profiles-extra package in Ubuntu:
  New
Status in dhcpcanon package in Ubuntu:
  New
Status in ejabberd package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  In Progress
Status in fwknop package in Ubuntu:
  New
Status in i2p package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in kopanocore package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm-remote-session-freerdp2 package in Ubuntu:
  Fix Released
Status in lightdm-remote-session-x2go package in Ubuntu:
  Fix Released
Status in man-db package in Ubuntu:
  Fix Released
Status in strongswan package in Ubuntu:
  Fix Released
Status in surf package in Ubuntu:
  New
Status in telepathy-mission-control-5 package in Ubuntu:
  Fix Released
Status in strongswan package in Debian:
  New

Bug description:
  this is about / and /usr merge.

  /bin & /sbin merge is out of scope. Anything that was in /sbin/  will
  remain in /{,usr/}sbin/.

  = src:apparmor =
  usr.bin.chromium-browser appears to be out of date w.r.t. apparmor-profiles 
upstream git tree

  /usr/share/apparmor/extra-profiles/usr.sbin.useradd needs update
  upstream https://gitlab.com/apparmor/apparmor/merge_requests/152/diffs

  = other packages =

  Slightly more complete list: https://paste.ubuntu.com/p/4zDJ8mTc5Z/

  $ sudo grep '[[:space:]]/bin' -r .
  ./usr.bin.man:  /bin/bzip2 rmCx -> _filter,
  ./usr.bin.man:  /bin/gzip rmCx -> _filter,
  ./usr.bin.man:  /bin/bzip2 rm,
  ./usr.bin.man:  /bin/gzip rm,
  ./usr.sbin.libvirtd:  /bin/* PUx,
  ./abstractions/lightdm:  /bin/ rmix,
  ./abstractions/lightdm:  /bin/fusermount Px,
  ./abstractions/lightdm:  /bin/** rmix,
  ./abstractions/libvirt-qemu:  /bin/uname rmix,
  ./abstractions/libvirt-qemu:  /bin/grep rmix,
  ./usr.bin.chromium-browser:  /bin/ps Uxr,
  ./usr.bin.chromium-browser:/bin/dash ixr,
  ./usr.bin.chromium-browser:/bin/grep ixr,
  ./usr.bin.chromium-browser:/bin/readlink ixr,
  ./usr.bin.chromium-browser:/bin/sed ixr,
  ./usr.bin.chromium-browser:/bin/which ixr,
  ./usr.bin.chromium-browser:/bin/mkdir ixr,
  ./usr.bin.chromium-browser:/bin/mv ixr,
  ./usr.bin.chromium-browser:/bin/touch ixr,
  ./usr.bin.chromium-browser:/bin/dash ixr,
  ./usr.bin.firefox:  /bin/which ixr,
  ./usr.bin.firefox:  /bin/ps Uxr,
  ./usr.bin.firefox:  /bin/uname Uxr,
  ./usr.bin.firefox:/bin/dash ixr,
  ./sbin.dhclient:  /bin/bash mr,

  $ sudo grep '[[:space:]]/sbin' -r .
  ./usr.lib.telepathy:deny /sbin/ldconfig x,
  ./usr.sbin.libvirtd:  /sbin/* PUx,
  ./abstractions/lightdm:  /sbin/ r,
  ./abstractions/lightdm:  /sbin/** rmixk,
  ./usr.bin.firefox:  /sbin/killall5 ixr,
  ./sbin.dhclient:  /sbin/dhclient mr,
  ./sbin.dhclient:  # daemon to run arbitrary code via /sbin/dhclient-script, 
it would need to be
  ./sbin.dhclient:  /sbin/dhclient-script   Uxr,

  $ sudo grep '[[:space:]]/lib' -r .
  ./snap.core.4917.usr.lib.snapd.snap-confine:/lib/udev/snappy-app-dev ixr, 
# drop
  ./usr.lib.snapd.snap-confine.real:/lib/udev/snappy-app-dev ixr, # drop
  ./abstractions/lightdm:  /lib/ r,
  ./abstractions/lightdm:  /lib/** rmixk,
  ./abstractions/lightdm:  /lib32/ r,
  ./abstractions/lightdm:  /lib32/** rmixk,
  ./abstractions/lightdm:  /lib64/ r,
  ./abstractions/lightdm:  /lib64/** rmixk,
  ./usr.bin.chromium-browser:/lib/libgcc_s.so* mr,
  ./usr.bin.chromium-browser:/lib/@{multiarch}/libgcc_s.so* mr,
  ./usr.bin.chromium-browser:/lib{,32,64}/libm-*.so* mr,
  ./usr.bin.chromium-browser:/lib/@{multiarch}/libm-*.so* mr,
  ./usr.bin.chromium-browser:/lib{,32,64}/libpthread-*.so* mr,
  ./usr.bin.chromium-browser:/lib/@{multiarch}/libpthread-*.so* mr,
  ./usr.bin.chromium-browser:/lib{,32,64}/libc-*.so* mr,
  ./usr.bin.chromium-browser:/lib/@{multiarch}/libc-*.so* mr,
  ./usr.bin.chromium-browser:/lib{,32,64}/libld-*.so* mr,
  ./usr.bin.chromium-browser:/lib/@{multiarch}/libld-*.so* mr,
  ./usr.bin.chromium-browser:/lib{,32,64}/ld-*.so* mr,
  ./usr.bin.chromium-browser:/lib/@{multiarch}/ld-*.so* mr,
  ./usr.bin.chromium-browser:/lib/tls/*/{cmov,nosegneg}/libm-*.so* mr,
  ./usr.bin.chromium-browser:/lib/tls/*/{cmov,nosegneg}/libpthread-*.so* mr,
  ./usr.bin.chromium-browser:/lib/tls/*/{cmov,nosegneg}/libc-*.so* mr,

  above list might be incomplete

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

-- 
Mailing list: 

[Touch-packages] [Bug 1134036] Re: Failure when using ssh with a locale that is not configured on the server

[Łukasz Zemczak]

Can we get a Test Case and Regression Potential in the description
following SRU guidelines? Thank you!

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

Title:
  Failure when using ssh with a locale that is not configured on the
  server

Status in base-files package in Ubuntu:
  Fix Released
Status in maas package in Ubuntu:
  Invalid
Status in base-files source package in Bionic:
  New
Status in maas source package in Bionic:
  New

Bug description:
  If LC_ALL is not set (which seems to be the default on a few server
  installations I've done now), mid way through installing, you get this
  backtrace and then the installation just hangs.  You can ctrl-c out of
  it but the package is left half configured.

  Traceback (most recent call last):
    File "/usr/bin/django-admin", line 5, in 
  management.execute_from_command_line()
    File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 443, in execute_from_command_line
  utility.execute()
    File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 382, in execute
  self.fetch_command(subcommand).run_from_argv(self.argv)
    File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", 
line 196, in run_from_argv
  self.execute(*args, **options.__dict__)
    File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", 
line 232, in execute
  output = self.handle(*args, **options)
    File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", 
line 371, in handle
  return self.handle_noargs(**options)
    File 
"/usr/lib/python2.7/dist-packages/south/management/commands/syncdb.py", line 
90, in handle_noargs
  syncdb.Command().execute(**options)
    File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", 
line 232, in execute
  output = self.handle(*args, **options)
    File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", 
line 371, in handle
  return self.handle_noargs(**options)
    File 
"/usr/lib/python2.7/dist-packages/django/core/management/commands/syncdb.py", 
line 57, in handle_noargs
  cursor = connection.cursor()
    File "/usr/lib/python2.7/dist-packages/django/db/backends/__init__.py", 
line 308, in cursor
  cursor = util.CursorWrapper(self._cursor(), self)
    File 
"/usr/lib/python2.7/dist-packages/django/db/backends/postgresql_psycopg2/base.py",
 line 177, in _cursor
  self.connection = Database.connect(**conn_params)
    File "/usr/lib/python2.7/dist-packages/psycopg2/__init__.py", line 179, in 
connect
  connection_factory=connection_factory, async=async)
  psycopg2.OperationalError: FATAL:  password authentication failed for user 
"maas"
  FATAL:  password authentication failed for user "maas"

  
  Related bugs:
   * bug 969462: [postgres] fails to start after install if invalid locale is 
set

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1134036/+subscriptions

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

[Touch-packages] [Bug 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable

[Colan Schwartz]

Folks that are able to run `kdb_mode`:  Please let the rest of us know
what package it's from.  It's not available on my system by default, and
I can't seem to find the package that it ships with.

Also, what does this command do?  I can't find a man page anywhere.
Thanks!

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

Title:
  Alt+left/right arrows switch between tty consoles (Gnome Shell
  vanishes), cannot disable

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I'm used to using alt+left/right arrow to navigate back and forward in
  web browsers and elsewhere (nautilus)...  But on this fresh install of
  Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty
  consoles (the ctrl+alt+f1 ones).  But it's not listed as one of the
  shortcuts in the "keyboard" menu, so I don't know how to disable it...

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

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

[Touch-packages] [Bug 1788597] Re: ubiquity broken with console-setup 1.178ubuntu2.5

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  ubiquity broken with console-setup 1.178ubuntu2.5

Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  Since this version of console-setup in bionic ubiquity now skips the
  Keyboard and Wireless pages.

  http://launchpadlibrarian.net/382474004/console-
  setup_1.178ubuntu2.4_1.178ubuntu2.5.diff.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1788597/+subscriptions

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

[Touch-packages] [Bug 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable

[Juan Leni]

Colan, notice that it is kbd not kdb

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

Title:
  Alt+left/right arrows switch between tty consoles (Gnome Shell
  vanishes), cannot disable

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I'm used to using alt+left/right arrow to navigate back and forward in
  web browsers and elsewhere (nautilus)...  But on this fresh install of
  Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty
  consoles (the ctrl+alt+f1 ones).  But it's not listed as one of the
  shortcuts in the "keyboard" menu, so I don't know how to disable it...

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

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

[Touch-packages] [Bug 1780606] Re: NetworkManager not able to manage WWAN devices in 18.04 server

[Launchpad Bug Tracker]

This bug was fixed in the package network-manager - 1.10.8-1ubuntu4

---
network-manager (1.10.8-1ubuntu4) cosmic; urgency=medium

  * debian/10-globally-managed-devices.conf: adjust exception for wwan to
specify cdma and gsm, since those are the actual types handled by NM/MM.
(LP: #1780606)

 -- Mathieu Trudel-Lapierre   Tue, 10 Jul 2018
08:17:11 -0400

** Changed in: network-manager (Ubuntu)
   Status: Triaged => 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/1780606

Title:
  NetworkManager not able to manage WWAN devices in 18.04 server

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  Installed a 18.04 server image, and installed NetworkManager.

  NetworkManager comes with a "/usr/lib/NetworkManager/conf.d/10
  -globally-managed-devices.conf" file where it speciefies that all
  devices are by default unmanaged except for types "wifi" and "wwan".

  Now, the problem is that the filter should apply to "gsm" or "cdma"
  types, not "wwan".

  E.g.:
[keyfile]
unmanaged-devices=*,except:type:wifi,except:type:gsm,except:type:cdma

  Before the change:
  $ nmcli d
  DEVICETYPE  STATE  CONNECTION 
  wlan0 wifi   connected  Bumbu
  eth0  ethernet  unmanaged  -- 
  cdc-wdm0  gsm   unmanaged  -- 
  loloopback  unmanaged  -- 

  After the change:
  $ nmcli d
  DEVICETYPE  STATE  CONNECTION 
  wlan0 wifi   connected  Bumbu
  cdc-wdm0  gsm   connected  cell   
  eth0  ethernet  unmanaged  -- 
  loloopback  unmanaged  --

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1780606/+subscriptions

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

[Touch-packages] [Bug 1751271] Re: sudo apt remove xclip sudo apt sudo E: Sub-process /usr/bin/dpkg returned an error code (1)

[Balint Reczey]

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

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

Title:
   sudo apt remove xclip sudo apt sudo E: Sub-process /usr/bin/dpkg
  returned an error code (1)

Status in sudo package in Ubuntu:
  Invalid

Bug description:
  При удалении пакетов мною была допущена ошибка в тексте команды. Вот
  полное описание процесса:

  beginner@beginner-desktop:~$ sudo apt remove xclip sudo apt
  Чтение списков пакетов… Готово
  Построение дерева зависимостей   
  Чтение информации о состоянии… Готово
  Следующие пакеты устанавливались автоматически и больше не требуются:
extlinux gdebi-core gnome-icon-theme libgksu2-0 linux-headers-4.10.0-28
linux-headers-4.10.0-28-generic linux-image-4.10.0-28-generic
linux-image-extra-4.10.0-28-generic sudo-ldap unetbootin-translations
  Для их удаления используйте «sudo apt autoremove».
  Будут установлены следующие дополнительные пакеты:
sudo-ldap
  Пакеты, которые будут УДАЛЕНЫ:
apt apt-utils gdebi gksu sudo ubuntu-minimal unattended-upgrades unetbootin
xclip
  НОВЫЕ пакеты, которые будут установлены:
sudo-ldap
  ВНИМАНИЕ: Эти существенно важные пакеты будут удалены.
  НЕ ДЕЛАЙТЕ этого, если вы НЕ представляете себе все возможные последствия!
apt
  обновлено 0, установлено 1 новых пакетов, для удаления отмечено 9 пакетов, и 
0 пакетов не обновлено.
  Необходимо скачать 420 kБ архивов.
  После данной операции, объём занятого дискового пространства уменьшится на 6 
050 kB.
  То, что вы хотите сделать, может иметь нежелательные последствия.
  Чтобы продолжить, введите фразу: «Да, делать, как я скажу!»
   ?] Да, делать, как я скажу!
  Пол:1 http://ru.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
sudo-ldap amd64 1.8.16-0ubuntu1.5 [420 kB]
  Получено 420 kБ за 20с (20,8 kБ/c)
  (Чтение базы данных … на данный момент установлено 307670 файлов и каталогов.)
  Удаляется unattended-upgrades (0.90ubuntu0.9) …
  Удаляется ubuntu-minimal (1.361.1) …
  Удаляется apt-utils (1.2.25) …
  Удаляется apt (1.2.25) …
  Удаляется gdebi (0.9.5.7ubuntu1) …
  Удаляется unetbootin (608-1) …
  Удаляется gksu (2.0.2-9ubuntu1) …
  Удаляется sudo (1.8.16-0ubuntu1.5) …
  You have asked that the sudo package be removed,
  but no root password has been set.
  Without sudo, you may not be able to gain administrative privileges.

  If you would prefer to access the root account with su(1)
  or by logging in directly,
  you must set a root password with "sudo passwd".

  If you have arranged other means to access the root account,
  and you are sure this is what you want,
  you may bypass this check by setting an environment variable 
  (export SUDO_FORCE_REMOVE=yes).

  Refusing to remove sudo.
  dpkg: ошибка при обработке пакета sudo (--remove):
   подпроцесс установлен сценарий pre-removal возвратил код ошибки 1
  Удаляется xclip (0.12+svn84-4) …
  Обрабатываются триггеры для man-db (2.7.5-1) …
  Обрабатываются триггеры для libc-bin (2.23-0ubuntu10) …
  Обрабатываются триггеры для gnome-menus (3.13.3-6ubuntu3.1) …
  Обрабатываются триггеры для desktop-file-utils (0.22-1ubuntu5.1) …
  Обрабатываются триггеры для bamfdaemon (0.5.3~bzr0+16.04.20160824-0ubuntu1) …
  Rebuilding /usr/share/applications/bamf-2.index...
  Обрабатываются триггеры для mime-support (3.59ubuntu1) …
  При обработке следующих пакетов произошли ошибки:
   sudo
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sudo 1.8.16-0ubuntu1.5
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  Architecture: amd64
  Date: Fri Feb 23 11:53:32 2018
  ErrorMessage: подпроцесс установлен сценарий pre-removal возвратил код ошибки 
1
  InstallationDate: Installed on 2018-01-29 (24 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: sudo
  Title: package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: подпроцесс 
установлен сценарий pre-removal возвратил код ошибки 1
  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/1751271/+subscriptions

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

[Touch-packages] [Bug 1787508] Re: (non-syslog) log file entries are missing the newline when loglinelen is set to a non-positive number (sudo version 1.8.14 - 1.8.16)

[Balint Reczey]

Fixed in latest Ubuntu releases, let release managers decide if it can go into 
Xenial.
Thanks for the offer BTW! :-)

** Also affects: sudo (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

Title:
  (non-syslog) log file entries are missing the newline when loglinelen
  is set to a non-positive number (sudo version 1.8.14 - 1.8.16)

Status in sudo package in Ubuntu:
  Fix Released
Status in sudo source package in Xenial:
  New

Bug description:
  This is basically a request to have an upstream patch applied to the
  current Ubuntu Xenial package.

  Changes made in sudo 1.8.14 introduced this bug. It was fixed upstream in 
1.8.17
  https://www.sudo.ws/devel.html#1.8.17b1
  https://bugzilla.sudo.ws/show_bug.cgi?id=742

  Ubuntu release:   Ubuntu 16.04.5 LTS
  Package version:  sudo/xenial-updates,now 1.8.16-0ubuntu1.5 amd64

  I am willing to help fix this (literally a one-liner in the patch), I
  just don't know the proper channels.

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

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

[Touch-packages] [Bug 1767801] Re: Wrong group name "admin" instead of "adm" in default sudoers file of sudo 1.8.21p2-3ubuntu1

[Balint Reczey]

The group is there for backward compatibility, it will be removed rather
than being changed to adm.

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

Title:
  Wrong group name "admin" instead of "adm" in default sudoers file of
  sudo 1.8.21p2-3ubuntu1

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  This is just to inform you, that the file /etc/sudoers, that comes
  with sudo 1.8.21p2-3ubuntu1 during a fresh install of Xubuntu 18.04,
  contains

  # Members of the admin group may gain root privileges
  %adminALL=(ALL) ALL

  but the admin group is now named "adm" instead of "admin".
  This is easy to correct, but it might confuse people, that are not familiar 
with the sudoers file. So, I suggest to change this line to

  %adm ...

  
  Additional information:
  lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  
  apt-cache policy sudo
  sudo:
Installiert:   1.8.21p2-3ubuntu1
Installationskandidat: 1.8.21p2-3ubuntu1
Versionstabelle:
   *** 1.8.21p2-3ubuntu1 500
  500 http://at.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1788620] Re: package keyboard-configuration 1.178ubuntu2.6 failed to install/upgrade: installed keyboard-configuration package post-installation script subprocess returned error

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

** Changed in: console-setup (Ubuntu)
   Importance: Undecided => Low

** Changed in: console-setup (Ubuntu)
   Status: New => Invalid

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

Title:
  package keyboard-configuration 1.178ubuntu2.6 failed to
  install/upgrade: installed keyboard-configuration package post-
  installation script subprocess returned error exit status 5

Status in console-setup package in Ubuntu:
  Invalid

Bug description:
  My latest update for Ubuntu failed. I did not really focus on the
  error reported though, Apologies for the same.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: keyboard-configuration 1.178ubuntu2.6
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_30_32_generic_42 wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Thu Aug 23 19:22:37 2018
  ErrorMessage: installed keyboard-configuration package post-installation 
script subprocess returned error exit status 5
  InstallationDate: Installed on 2018-07-08 (46 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: console-setup
  Title: package keyboard-configuration 1.178ubuntu2.6 failed to 
install/upgrade: installed keyboard-configuration package post-installation 
script subprocess returned error exit status 5
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1788620/+subscriptions

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

[Touch-packages] [Bug 1788620] Re: package keyboard-configuration 1.178ubuntu2.6 failed to install/upgrade: installed keyboard-configuration package post-installation script subprocess returned error

[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 console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1788620

Title:
  package keyboard-configuration 1.178ubuntu2.6 failed to
  install/upgrade: installed keyboard-configuration package post-
  installation script subprocess returned error exit status 5

Status in console-setup package in Ubuntu:
  New

Bug description:
  My latest update for Ubuntu failed. I did not really focus on the
  error reported though, Apologies for the same.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: keyboard-configuration 1.178ubuntu2.6
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_30_32_generic_42 wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Thu Aug 23 19:22:37 2018
  ErrorMessage: installed keyboard-configuration package post-installation 
script subprocess returned error exit status 5
  InstallationDate: Installed on 2018-07-08 (46 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: console-setup
  Title: package keyboard-configuration 1.178ubuntu2.6 failed to 
install/upgrade: installed keyboard-configuration package post-installation 
script subprocess returned error exit status 5
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1788620/+subscriptions

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

[Touch-packages] [Bug 1752411] Re: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck

[fermulator]

PS: I've been running with a hacked /usr/lib/avahi/avahi-daemon-check-dns.sh 
for a few days with this code:
```
  OUT=`LC_ALL=C /usr/bin/timeout 2 host -t soa local. 2>&1`
```
, works like a charm

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

Title:
  bind9-host, avahi-daemon-check-dns.sh hang forever causes network
  connections to get stuck

Status in avahi package in Ubuntu:
  In Progress
Status in bind9 package in Ubuntu:
  Confirmed
Status in openconnect package in Ubuntu:
  Invalid
Status in strongswan package in Ubuntu:
  Invalid
Status in avahi source package in Bionic:
  Triaged
Status in bind9 source package in Bionic:
  Confirmed
Status in avahi source package in Cosmic:
  In Progress
Status in bind9 source package in Cosmic:
  Confirmed
Status in avahi package in Debian:
  New

Bug description:
  [Impact]

   * Network connections for some users fail (in some cases a direct
  interface, in others when connecting a VPN) because the 'host' command
  to check for .local in DNS called by /usr/lib/avahi/avahi-daemon-
  check-dns.sh never times out like it should - leaving the script
  hanging indefinitely blocking interface up and start-up. This appears
  to be a bug in host caused in some circumstances however we implement
  a workaround to call it under 'timeout' as the issue with 'host' has
  not easily been identified, and in any case acts as a fall-back.

  [Test Case]

   * Multiple people have been unable to create a reproducer on a
  generic machine (e.g. it does not occur in a VM), I have a specific
  machine I can reproduce it on (a Skull Canyon NUC with Intel I219-LM)
  by simply "ifdown br0; ifup br0" and there are clearly 10s of other
  users affected in varying circumstances that all involve the same
  symptoms but no clear test case exists. Best I can suggest is that I
  test the patch on my system to ensure it works as expected, and the
  change is only 1 line which is fairly easily auditible and
  understandable.

  [Regression Potential]

   * The change is a single line change to the shell script to call host with 
"timeout". When tested on working and non-working system this appears to 
function as expected. I believe the regression potential for this is 
subsequently low.
   * In attempt to anticipate possible issues, I checked that the timeout 
command is in the same path (/usr/bin) as the host command that is already 
called without a path, and the coreutils package (which contains timeout) is an 
Essential package. I also checked that timeout is not a built-in in bash, for 
those that have changed /bin/sh to bash (just in case).

  [Other Info]
   
   * N/A

  [Original Bug Description]

  On 18.04 Openconnect connects successfully to any of multiple VPN
  concentrators but network traffic does not flow across the VPN tunnel
  connection. When testing on 16.04 this works flawlessly. This also
  worked on this system when it was on 17.10.

  I have tried reducing the mtu of the tun0 network device but this has
  not resulted in me being able to successfully ping the IP address.

  Example showing ping attempt to the IP of DNS server:

  ~$ 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 172.29.88.11
  nameserver 127.0.0.53

  liam@liam-lat:~$ netstat -nr
  Kernel IP routing table
  Destination Gateway Genmask Flags   MSS Window  irtt Iface
  0.0.0.0 192.168.1.1 0.0.0.0 UG0 0  0 
wlp2s0
  105.27.198.106  192.168.1.1 255.255.255.255 UGH   0 0  0 
wlp2s0
  169.254.0.0 0.0.0.0 255.255.0.0 U 0 0  0 
docker0
  172.17.0.0  0.0.0.0 255.255.0.0 U 0 0  0 
docker0
  172.29.0.0  0.0.0.0 255.255.0.0 U 0 0  0 tun0
  172.29.88.110.0.0.0 255.255.255.255 UH0 0  0 tun0
  192.168.1.0 0.0.0.0 255.255.255.0   U 0 0  0 
wlp2s0
  liam@liam-lat:~$ ping 172.29.88.11
  PING 172.29.88.11 (172.29.88.11) 56(84) bytes of data.
  ^C
  --- 172.29.88.11 ping statistics ---
  4 packets transmitted, 0 received, 100% packet loss, time 3054ms

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: openconnect 7.08-3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 28 22:11:33 2018
  InstallationDate: Installed on 2017-06-15 (258 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  

[Touch-packages] [Bug 1752411] Re: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck

[fermulator]

Are we sure timeout of 5 seconds is appropriate? (it FEELS too long)
My intuition says that if a DNS query takes longer than 1 second it took too 
long ...

However (consider also the "wait" (-W) parameter for the host command itself)
```

   -W wait
   Timeout: Wait for up to wait seconds for a reply. If wait is less
   than one, the wait interval is set to one second.

   By default, host will wait for 5 seconds for UDP responses and 10
   seconds for TCP connections. These defaults can be overridden by
   the timeout option in /etc/resolv.conf.

   See also the -w option.
```

None-the-less, this is a _workaround_ for the issue -- (will the ticket
remain open to fix the underlying issue, or a subsequent issue be
submitted?)

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

Title:
  bind9-host, avahi-daemon-check-dns.sh hang forever causes network
  connections to get stuck

Status in avahi package in Ubuntu:
  In Progress
Status in bind9 package in Ubuntu:
  Confirmed
Status in openconnect package in Ubuntu:
  Invalid
Status in strongswan package in Ubuntu:
  Invalid
Status in avahi source package in Bionic:
  Triaged
Status in bind9 source package in Bionic:
  Confirmed
Status in avahi source package in Cosmic:
  In Progress
Status in bind9 source package in Cosmic:
  Confirmed
Status in avahi package in Debian:
  New

Bug description:
  [Impact]

   * Network connections for some users fail (in some cases a direct
  interface, in others when connecting a VPN) because the 'host' command
  to check for .local in DNS called by /usr/lib/avahi/avahi-daemon-
  check-dns.sh never times out like it should - leaving the script
  hanging indefinitely blocking interface up and start-up. This appears
  to be a bug in host caused in some circumstances however we implement
  a workaround to call it under 'timeout' as the issue with 'host' has
  not easily been identified, and in any case acts as a fall-back.

  [Test Case]

   * Multiple people have been unable to create a reproducer on a
  generic machine (e.g. it does not occur in a VM), I have a specific
  machine I can reproduce it on (a Skull Canyon NUC with Intel I219-LM)
  by simply "ifdown br0; ifup br0" and there are clearly 10s of other
  users affected in varying circumstances that all involve the same
  symptoms but no clear test case exists. Best I can suggest is that I
  test the patch on my system to ensure it works as expected, and the
  change is only 1 line which is fairly easily auditible and
  understandable.

  [Regression Potential]

   * The change is a single line change to the shell script to call host with 
"timeout". When tested on working and non-working system this appears to 
function as expected. I believe the regression potential for this is 
subsequently low.
   * In attempt to anticipate possible issues, I checked that the timeout 
command is in the same path (/usr/bin) as the host command that is already 
called without a path, and the coreutils package (which contains timeout) is an 
Essential package. I also checked that timeout is not a built-in in bash, for 
those that have changed /bin/sh to bash (just in case).

  [Other Info]
   
   * N/A

  [Original Bug Description]

  On 18.04 Openconnect connects successfully to any of multiple VPN
  concentrators but network traffic does not flow across the VPN tunnel
  connection. When testing on 16.04 this works flawlessly. This also
  worked on this system when it was on 17.10.

  I have tried reducing the mtu of the tun0 network device but this has
  not resulted in me being able to successfully ping the IP address.

  Example showing ping attempt to the IP of DNS server:

  ~$ 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 172.29.88.11
  nameserver 127.0.0.53

  liam@liam-lat:~$ netstat -nr
  Kernel IP routing table
  Destination Gateway Genmask Flags   MSS Window  irtt Iface
  0.0.0.0 192.168.1.1 0.0.0.0 UG0 0  0 
wlp2s0
  105.27.198.106  192.168.1.1 255.255.255.255 UGH   0 0  0 
wlp2s0
  169.254.0.0 0.0.0.0 255.255.0.0 U 0 0  0 
docker0
  172.17.0.0  0.0.0.0 255.255.0.0 U 0 0  0 
docker0
  172.29.0.0  0.0.0.0 255.255.0.0 U 0 0  0 tun0
  172.29.88.110.0.0.0 255.255.255.255 UH0 0  0 tun0
  192.168.1.0 0.0.0.0 255.255.255.0   U 0 0  0 
wlp2s0
  liam@liam-lat:~$ ping 172.29.88.11
  PING 172.29.88.11 

[Touch-packages] [Bug 1784023] Re: Update profiles for usrmerge

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~ahasenack/ubuntu/+source/strongswan/+git/strongswan/+merge/353642

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

Title:
  Update profiles for usrmerge

Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor-profiles-extra package in Ubuntu:
  New
Status in dhcpcanon package in Ubuntu:
  New
Status in ejabberd package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  In Progress
Status in fwknop package in Ubuntu:
  New
Status in i2p package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in kopanocore package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm-remote-session-freerdp2 package in Ubuntu:
  Fix Released
Status in lightdm-remote-session-x2go package in Ubuntu:
  Fix Released
Status in man-db package in Ubuntu:
  Fix Released
Status in strongswan package in Ubuntu:
  Fix Released
Status in surf package in Ubuntu:
  New
Status in telepathy-mission-control-5 package in Ubuntu:
  Fix Released
Status in strongswan package in Debian:
  New

Bug description:
  this is about / and /usr merge.

  /bin & /sbin merge is out of scope. Anything that was in /sbin/  will
  remain in /{,usr/}sbin/.

  = src:apparmor =
  usr.bin.chromium-browser appears to be out of date w.r.t. apparmor-profiles 
upstream git tree

  /usr/share/apparmor/extra-profiles/usr.sbin.useradd needs update
  upstream https://gitlab.com/apparmor/apparmor/merge_requests/152/diffs

  = other packages =

  Slightly more complete list: https://paste.ubuntu.com/p/4zDJ8mTc5Z/

  $ sudo grep '[[:space:]]/bin' -r .
  ./usr.bin.man:  /bin/bzip2 rmCx -> _filter,
  ./usr.bin.man:  /bin/gzip rmCx -> _filter,
  ./usr.bin.man:  /bin/bzip2 rm,
  ./usr.bin.man:  /bin/gzip rm,
  ./usr.sbin.libvirtd:  /bin/* PUx,
  ./abstractions/lightdm:  /bin/ rmix,
  ./abstractions/lightdm:  /bin/fusermount Px,
  ./abstractions/lightdm:  /bin/** rmix,
  ./abstractions/libvirt-qemu:  /bin/uname rmix,
  ./abstractions/libvirt-qemu:  /bin/grep rmix,
  ./usr.bin.chromium-browser:  /bin/ps Uxr,
  ./usr.bin.chromium-browser:/bin/dash ixr,
  ./usr.bin.chromium-browser:/bin/grep ixr,
  ./usr.bin.chromium-browser:/bin/readlink ixr,
  ./usr.bin.chromium-browser:/bin/sed ixr,
  ./usr.bin.chromium-browser:/bin/which ixr,
  ./usr.bin.chromium-browser:/bin/mkdir ixr,
  ./usr.bin.chromium-browser:/bin/mv ixr,
  ./usr.bin.chromium-browser:/bin/touch ixr,
  ./usr.bin.chromium-browser:/bin/dash ixr,
  ./usr.bin.firefox:  /bin/which ixr,
  ./usr.bin.firefox:  /bin/ps Uxr,
  ./usr.bin.firefox:  /bin/uname Uxr,
  ./usr.bin.firefox:/bin/dash ixr,
  ./sbin.dhclient:  /bin/bash mr,

  $ sudo grep '[[:space:]]/sbin' -r .
  ./usr.lib.telepathy:deny /sbin/ldconfig x,
  ./usr.sbin.libvirtd:  /sbin/* PUx,
  ./abstractions/lightdm:  /sbin/ r,
  ./abstractions/lightdm:  /sbin/** rmixk,
  ./usr.bin.firefox:  /sbin/killall5 ixr,
  ./sbin.dhclient:  /sbin/dhclient mr,
  ./sbin.dhclient:  # daemon to run arbitrary code via /sbin/dhclient-script, 
it would need to be
  ./sbin.dhclient:  /sbin/dhclient-script   Uxr,

  $ sudo grep '[[:space:]]/lib' -r .
  ./snap.core.4917.usr.lib.snapd.snap-confine:/lib/udev/snappy-app-dev ixr, 
# drop
  ./usr.lib.snapd.snap-confine.real:/lib/udev/snappy-app-dev ixr, # drop
  ./abstractions/lightdm:  /lib/ r,
  ./abstractions/lightdm:  /lib/** rmixk,
  ./abstractions/lightdm:  /lib32/ r,
  ./abstractions/lightdm:  /lib32/** rmixk,
  ./abstractions/lightdm:  /lib64/ r,
  ./abstractions/lightdm:  /lib64/** rmixk,
  ./usr.bin.chromium-browser:/lib/libgcc_s.so* mr,
  ./usr.bin.chromium-browser:/lib/@{multiarch}/libgcc_s.so* mr,
  ./usr.bin.chromium-browser:/lib{,32,64}/libm-*.so* mr,
  ./usr.bin.chromium-browser:/lib/@{multiarch}/libm-*.so* mr,
  ./usr.bin.chromium-browser:/lib{,32,64}/libpthread-*.so* mr,
  ./usr.bin.chromium-browser:/lib/@{multiarch}/libpthread-*.so* mr,
  ./usr.bin.chromium-browser:/lib{,32,64}/libc-*.so* mr,
  ./usr.bin.chromium-browser:/lib/@{multiarch}/libc-*.so* mr,
  ./usr.bin.chromium-browser:/lib{,32,64}/libld-*.so* mr,
  ./usr.bin.chromium-browser:/lib/@{multiarch}/libld-*.so* mr,
  ./usr.bin.chromium-browser:/lib{,32,64}/ld-*.so* mr,
  ./usr.bin.chromium-browser:/lib/@{multiarch}/ld-*.so* mr,
  ./usr.bin.chromium-browser:/lib/tls/*/{cmov,nosegneg}/libm-*.so* mr,
  ./usr.bin.chromium-browser:/lib/tls/*/{cmov,nosegneg}/libpthread-*.so* mr,
  ./usr.bin.chromium-browser:/lib/tls/*/{cmov,nosegneg}/libc-*.so* mr,

  above list might be incomplete

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

-- 
Mailing list: 

[Touch-packages] [Bug 1272859] Re: unity-greeter crashed with signal 5 in atspi_dbus_connection_setup_with_g_main()

[Bug Watch Updater]

** Changed in: at-spi
   Status: New => Expired

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

Title:
  unity-greeter crashed with signal 5 in
  atspi_dbus_connection_setup_with_g_main()

Status in at-spi:
  Expired
Status in at-spi2-core package in Ubuntu:
  Triaged
Status in unity-greeter package in Ubuntu:
  Triaged

Bug description:
  This happened when I logged into Ubuntu14.04 Alpha1 after upgrading
  from 13.10, it caused some of the display to blank for a time but
  seemed to recover after a few seconds.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity-greeter 14.04.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  ApportVersion: 2.13.1-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Sun Jan 26 08:18:36 2014
  ExecutablePath: /usr/sbin/unity-greeter
  InstallationDate: Installed on 2013-09-27 (120 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  ProcCmdline: /usr/sbin/unity-greeter
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: unity-greeter
  StacktraceTop:
   atspi_dbus_connection_setup_with_g_main () from 
/usr/lib/x86_64-linux-gnu/libatspi.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: unity-greeter crashed with signal 5 in 
atspi_dbus_connection_setup_with_g_main()
  UpgradeStatus: Upgraded to trusty on 2013-12-17 (39 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/at-spi/+bug/1272859/+subscriptions

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

[Touch-packages] [Bug 1580216] Re: Color manager breaks Zebra ZPL

[gf]

Hello Nick,
Thank you for submitting this bug and reporting a problem with cups.  You made 
this bug report some time ago and Ubuntu has been updated since then. 
 
Could you confirm that this is no longer a problem and that we can close the 
ticket? 
If it is still a problem, are you still interested in finding a solution to 
this bug? 
If you are, could you let us know, and in the current version, run the 
following (only once): 
apport-collect BUGNUMBER
and upload the updated logs and and any other logs that are relevant for this 
particular issue.  

Thank you again for helping make Ubuntu better. 
G
[Ubuntu Bug Squad volunteer triager]

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

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

Title:
  Color manager breaks Zebra ZPL

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 14.04.3 LTS
  CUPS 1.7.2-0ubuntu1.7
  On new install, I setup a Zebra printer (USB). I guess I'm used to the old 
CUPS web UI because I didn't even notice the Color Manager option. So I didn't 
uncheck it. If you leave Color Manager enabled it will cause some print jobs to 
not print but show the job completed normally.

  #EDIT: Issue remains with color manager disabled

  D [10/May/2016:09:26:18 -0500] [Job 56] Failed to send: 
org.freedesktop.ColorManager.Device.NothingMatched:nothing matched expression 
'Gray.Thermal.203dpi,Gray.Thermal.*,Gray.*.203dpi,Gray.*.*,*'
  D [10/May/2016:09:26:18 -0500] [Job 56] Failed to get profile filename for 
cups-TestTouch
  D [10/May/2016:09:26:18 -0500] cupsd is not idle any more, canceling shutdown.
  I [10/May/2016:09:26:18 -0500] [Job 56] no profiles specified in PPD

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

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

[Touch-packages] [Bug 1572489] Re: Canon MF4330d needs usb-no-reattach-default=true

[gf]

Hello Fernando,
Thank you for submitting this bug and reporting a problem with cups.  You made 
this bug report some time ago and Ubuntu has been updated since then. 
 
Could you confirm that this is no longer a problem and that we can close the 
ticket? 
If it is still a problem, are you still interested in finding a solution to 
this bug? 
If you are, could you let us know, and in the current version, run the 
following (only once): 
apport-collect BUGNUMBER
and upload the updated logs and and any other logs that are relevant for this 
particular issue.  

Thank you again for helping make Ubuntu better. 
G
[Ubuntu Bug Squad volunteer triager]

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

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

Title:
  Canon MF4330d needs usb-no-reattach-default=true

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Following the instructions on
  , I'd like to
  report that my Canon MF4330d (USB) needs usb-no-reattach-default=true
  to print the 2nd job; otherwise it only prints the first one after
  each power cycle.

  $ lsusb
  Bus 003 Device 007: ID 04a9:26ee Canon, Inc.

  $ lsb_release -rd
  Description:Ubuntu 15.10
  Release:15.10

  $ apt-cache policy cups
  cups:
Installed: 2.1.0-4ubuntu3
Candidate: 2.1.0-4ubuntu3
Version table:
   *** 2.1.0-4ubuntu3 0
  500 http://nl.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: cups 2.1.0-4ubuntu3
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CupsErrorLog:
   W [20/Apr/2016:11:48:49 +0200] Notifier for subscription 62 (dbus://) went 
away, retrying!
   W [20/Apr/2016:11:48:49 +0200] Notifier for subscription 65 (dbus://) went 
away, retrying!
   W [20/Apr/2016:11:48:49 +0200] Notifier for subscription 68 (dbus://) went 
away, retrying!
  Date: Wed Apr 20 11:58:45 2016
  Lpstat: device for Canon: 
usb://Canon/MF4320-4350%20(UFRII%20LT)?serial=SJ3008471311L=1
  MachineType: Gigabyte Technology Co., Ltd. Z68AP-D3
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Canon.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Canon.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-35-generic 
root=UUID=d901b113-8377-400e-9d0b-8a3bb6e3caac ro quiet splash nomdmonddf 
nomdmonisw vt.handoff=7
  SourcePackage: cups
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/21/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F8
  dmi.board.name: Z68AP-D3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF8:bd03/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnZ68AP-D3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnZ68AP-D3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: Z68AP-D3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1788486] Re: apt behaviour with strict dependencies

[Simon Poirier]

That workaround wouldn't work in Landscape for many configurations; we
can't assume pocket names as many use custom mirrors or repository
snapshots in which the pocket may not match.

It seems to me there is no simple way to resolve this automatically in
Landscape, but as that upgrade situation is both infrequent, noisy, and
is easy to resolve manually, the real workaround for landscape is to
install those versions manually when that case happens.

Other than that, managing sources lists to limit them to -security after
deployment is the only other simple way to ensure that situation does
not happen with landscape.

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

Title:
  apt behaviour with strict dependencies

Status in apt package in Ubuntu:
  Won't Fix
Status in apt source package in Xenial:
  Won't Fix
Status in apt source package in Bionic:
  Won't Fix

Bug description:
  [Impact]

  We notice that situation while investigating a security update using
  Landscape, but it also applies to 'apt' outside the Landscape context.

  'apt' should be smarter to detect/install packages with strict
  dependencies such as systemd[1] when a version is specified for
  upgrade (Ex: $ apt-get install systemd=229-4ubuntu-21.1).

  It should automatically install the dependencies (if any) from that
  same version as well instead of failing trying to install the highest
  version available (if any) while installing the specified version for
  the one mentionned :

  
  $ apt-get install systemd=229-4ubuntu-21.1
  
  "systemd : Depends: libsystemd0 (= 229-4ubuntu21.1) but 229-4ubuntu21.4 is to 
be installed"
  =

  To face that problem :
  - Package with lower version should be found in -security ( Ex: 
systemd/229-4ubuntu21.1 )
  - Package with higher version should be found in -updates ( Ex: 
systemd/229-4ubuntu21.4 )
  - Package should have strict dependencies ( Ex: libsystemd0 (= 
${binary:Version}) )
  - The upgrade should only specify version for the package, without it's 
dependencies. (Ex: $ apt-get install systemd=229-4ubuntu-21.1" #systemd without 
libsystemd0 depends)

  Using systemd is a good reproducer, I'm sure finding other package
  with the same situation is easy.

  It has been easily reproduced with systemd on Xenial and Bionic so
  far.

  [1] debian/control
  Depends: ${shlibs:Depends},
  ${misc:Depends},
  libsystemd0 (= ${binary:Version}),
  ...

  [Workaround]
  If package + dependencies are specified, the upgrade work just fine :

  Ex: $ apt-get install systemd=229-4ubuntu-21.1
  libsystemd0=229-4ubuntu-21.1

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

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

[Touch-packages] [Bug 1788486] Re: apt behaviour with strict dependencies

[Eric Desrochers]

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

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

** Changed in: apt (Ubuntu Bionic)
   Status: Confirmed => Won't Fix

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

Title:
  apt behaviour with strict dependencies

Status in apt package in Ubuntu:
  Won't Fix
Status in apt source package in Xenial:
  Won't Fix
Status in apt source package in Bionic:
  Won't Fix

Bug description:
  [Impact]

  We notice that situation while investigating a security update using
  Landscape, but it also applies to 'apt' outside the Landscape context.

  'apt' should be smarter to detect/install packages with strict
  dependencies such as systemd[1] when a version is specified for
  upgrade (Ex: $ apt-get install systemd=229-4ubuntu-21.1).

  It should automatically install the dependencies (if any) from that
  same version as well instead of failing trying to install the highest
  version available (if any) while installing the specified version for
  the one mentionned :

  
  $ apt-get install systemd=229-4ubuntu-21.1
  
  "systemd : Depends: libsystemd0 (= 229-4ubuntu21.1) but 229-4ubuntu21.4 is to 
be installed"
  =

  To face that problem :
  - Package with lower version should be found in -security ( Ex: 
systemd/229-4ubuntu21.1 )
  - Package with higher version should be found in -updates ( Ex: 
systemd/229-4ubuntu21.4 )
  - Package should have strict dependencies ( Ex: libsystemd0 (= 
${binary:Version}) )
  - The upgrade should only specify version for the package, without it's 
dependencies. (Ex: $ apt-get install systemd=229-4ubuntu-21.1" #systemd without 
libsystemd0 depends)

  Using systemd is a good reproducer, I'm sure finding other package
  with the same situation is easy.

  It has been easily reproduced with systemd on Xenial and Bionic so
  far.

  [1] debian/control
  Depends: ${shlibs:Depends},
  ${misc:Depends},
  libsystemd0 (= ${binary:Version}),
  ...

  [Workaround]
  If package + dependencies are specified, the upgrade work just fine :

  Ex: $ apt-get install systemd=229-4ubuntu-21.1
  libsystemd0=229-4ubuntu-21.1

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

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

[Touch-packages] [Bug 1788598] Re: Xorg crash

[Daniel van Vugt]

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

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

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

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

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

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

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

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

Title:
  Xorg crash

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  The bug was already in the previous edition of Ubuntu (17.10) using awesome 
window manager.
  After upgrading to Ubuntu 18.04 and switched to xmonad the problem still 
occurs.

  It seems currently that the crash occurs randomly.
  Sometimes not at all for a day, sometimes after only a few minutes three 
times in a row.

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

  $ apt-cache policy xorg
  xorg:
Installed: 1:7.7+19ubuntu7.1
Candidate: 1:7.7+19ubuntu7.1
Version table:
   *** 1:7.7+19ubuntu7.1 500
  500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:7.7+19ubuntu7 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: openafs
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompositorRunning: None
  Date: Thu Aug 23 13:11:40 2018
  DistUpgraded: 2018-07-06 15:34:21,080 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   openafs, 1.8.0pre5, 4.15.0-30-generic, x86_64: installed
   openafs, 1.8.0pre5, 4.15.0-32-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 (ThinkPad X1 Carbon 5th Gen) [17aa:224f]
  InstallationDate: Installed on 2017-10-10 (316 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 20HR002RGE
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-32-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to bionic on 2018-07-06 (47 days ago)
  dmi.bios.date: 05/17/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET35W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HR002RGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET35W(1.20):bd05/17/2017:svnLENOVO:pn20HR002RGE:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HR002RGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 5th
  dmi.product.name: 20HR002RGE
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-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

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

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

[Touch-packages] [Bug 1651818] Re: busybox-initramfs needs different compile options to work with cryptroot-unlock

[Trent Nelson]

Tested working! 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/1651818

Title:
  busybox-initramfs needs different compile options to work with
  cryptroot-unlock

Status in busybox package in Ubuntu:
  Won't Fix
Status in cryptsetup package in Ubuntu:
  Fix Released
Status in cryptsetup source package in Bionic:
  Fix Committed

Bug description:
  SRU for bionic:

  Acceptance criteria: An encrypted partition can be decrypted using
  cryptroot-unlock.

  Regression potential: It's not the default method, so unused by the
  majority of people. Besides that the patched script runs fine in
  cosmic.

  The cryptroot-unlock script in the cryptsetup package does not work in 
initramfs.
  It fails because "ps -e" is not available in busybox for initramfs.
  When building the package with

  CONFIG_DESKTOP=y
  CONFIG_EXTRA_COMPAT=y

  the needed commands (ps, grep) with parameter are there and it works.
  Tetsted on Ubuntu GNOME 16.10.

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

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

[Touch-packages] [Bug 1787548] Re: PAM fscrypt adds root(0) group to all users called by su

[Launchpad Bug Tracker]

This bug was fixed in the package fscrypt - 0.2.2-0ubuntu2.1

---
fscrypt (0.2.2-0ubuntu2.1) bionic-security; urgency=medium

  * SECURITY UPDATE: Privilege escalation via improperly restored
supplementary groups in libpam-fscrypt (LP: #1787548)
- CVE-2018-6558.patch: Save the euid, egid, and supplementary groups when
  entering the PAM module, drop privileges to perform actions on behalf of
  the user, and then properly restore the saved values before exiting the
  PAM module. Based on patch from upstream.
- CVE-2018-6558
  * 0001-security-drop-and-regain-privileges-in-all-threads.patch: Drop and
regain privileges in all threads of the current process
  * 0001-Ensure-keyring-privilege-changes-are-reversible.patch: Ensure keyring
privilege changes are reversible to prevent failures when, for example,
"su " is executed as an unprivileged user

 -- Tyler Hicks   Wed, 22 Aug 2018 18:57:26 +

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

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

Title:
  PAM fscrypt adds root(0) group to all users called by su

Status in Shadow:
  Invalid
Status in fscrypt package in Ubuntu:
  Fix Released
Status in shadow package in Ubuntu:
  Invalid

Bug description:
  related packages: /bin/su (from login , shadow)

  OS: ubuntu 18.04.1, updated

  Bug: a normal user (not in 'root' group), when the PAM module fscrypt
  is active, all calls of su give the user additional group root(0).

  Results: this is a permission escalation, such user can now delete
  files owned by root group (where permisions are g+w)

  Steps to reproduce: 
  0/ login uses pam unix authentication module (default on ubuntu, no action 
needed)
  0.1/ create a new user: 
  # useradd developer

  1/ verify:
  #id developer 
  // on my system, shows
  // uid=1004(developer) gid=1004(developer) groups=1004(developer) 
  \su - developer -c id
  sudo -u developer id

  2/ enable pam-fscrypt
  # apt install libpam-fscrypt
  # pam-auth-update --enable fscrypt

  3/ verify again (bug shows)
  // repeate step 1/ 
  // the su command will show the bug (sudo won't, interestingly)
  \su - developer -c id
  // uid=1004(developer) gid=1004(developer) groups=1004(developer),0(root)

  4/ workaround and return to original state:
  pam-auth-update --disable fscrypt
  apt remove  libpam-fscrypt

  Thank you,

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

-- 
Mailing list: https://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 1783693] Re:failed to install winepackage sudo 1.8.21p2-3ubuntu1 failed to install/upgrade: instalado sudo paquete pre-removal guión el subproceso devolvióun error con estado

[Seth Arnold]

On Thu, Aug 23, 2018 at 06:43:32PM -, Balint Reczey wrote:
> The problem occurs when sudo:i386 is replacing sudo:amd64.
> 
> As the error message suggests please export SUDO_FORCE_REMOVE=yes to
> make the operation succeed as a workaround, like this:
> 
> sudo env SUDO_FORCE_REMOVE=yes apt install sudo:i386

I should point out that while this *is* the way to replace sudo:amd64 with
sudo:i386, one should *really* stop and wonder *why* this operation is
being undertaken at all. Probably something is broken and should be fixed.

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

Title:
  failed to install winepackage sudo 1.8.21p2-3ubuntu1 failed to
  install/upgrade: instalado sudo paquete pre-removal guión el
  subproceso devolvió un error con estado de salida 1

Status in sudo package in Ubuntu:
  Invalid

Bug description:
  no direct access after installing wine

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: sudo 1.8.21p2-3ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Thu Jul 26 00:28:22 2018
  ErrorMessage: instalado sudo paquete pre-removal guión el subproceso devolvió 
un error con estado de salida 1
  InstallationDate: Installed on 2018-07-21 (4 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: sudo
  Title: package sudo 1.8.21p2-3ubuntu1 failed to install/upgrade: instalado 
sudo paquete pre-removal guión el subproceso devolvió un error con estado de 
salida 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   /etc/sudoers análisis OK
   /etc/sudoers.d/README análisis OK

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

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

[Touch-packages] [Bug 1788658] Re: Videos (Totem)

[Daniel van Vugt]

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

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


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

** This bug has been marked a duplicate of bug 1698270
   Totem pauses and stutters during video playback even when CPU usage is low

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

Title:
  Videos (Totem)

Status in totem package in Ubuntu:
  New

Bug description:
  works, but with lots of stutter

  same problem with all three computers running current and fully
  updated Ubuntu

  VLC is fine but I like Videos

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 23 12:33:55 2018
  DistUpgraded: 2018-05-02 18:26:01,704 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0535]
  InstallationDate: Installed on 2017-11-24 (271 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Dell Inc. Latitude E6530
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=92f668d2-1882-408b-a814-61e23a9171ae ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (112 days ago)
  dmi.bios.date: 04/24/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0JC5MT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd04/24/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn0JC5MT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6530
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-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

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

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

[Touch-packages] [Bug 1788739] [NEW] When starting Evolution /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset information is printed to syslog

[chris pollock]

Public bug reported:

This started the same day I did the upgrade from 16.04LTS to 18.04LTS.
Package/system information below:

lsb_release -crid
Distributor ID: Ubuntu
Description:Ubuntu 18.04.1 LTS
Release:18.04
Codename:   bionic

apt-cache policy gdm3
gdm3:
  Installed: 3.28.2-0ubuntu1.4
  Candidate: 3.28.2-0ubuntu1.4

apt-cache policy evolution
evolution:
  Installed: 3.28.1-2
  Candidate: 3.28.1-2

The output written to syslog is:

Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
EDID vendor "ACR", prod id 22
Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Using hsync ranges from config file
Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Using vrefresh ranges from config file
Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Printing DDC gathered Modelines:
Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Modeline "1680x1050"x0.0  119.00  1680 1728 1760 1840  1050 1053 1059 1080 
-hsync -vsync (64.7 kHz eP)
Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync 
(37.9 kHz e)
Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Modeline "800x600"x0.0   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync 
(35.2 kHz e)
Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync 
(37.5 kHz e)
Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Modeline "640x480"x0.0   31.50  640 664 704 832  480 489 492 520 -hsync -vsync 
(37.9 kHz e)
Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Modeline "640x480"x0.0   30.24  640 704 768 864  480 483 486 525 -hsync -vsync 
(35.0 kHz e)
Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync 
(31.5 kHz e)
Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync 
(31.5 kHz e)
Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Modeline "1280x1024"x0.0  135.00  1280 1296 1440 1688  1024 1025 1028 1066 
+hsync +vsync (80.0 kHz e)
Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Modeline "1024x768"x0.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync 
+vsync (60.0 kHz e)
Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Modeline "1024x768"x0.0   75.00  1024 1048 1184 1328  768 771 777 806 -hsync 
-vsync (56.5 kHz e)
Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync 
-vsync (48.4 kHz e)
Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Modeline "832x624"x0.0   57.28  832 864 928 1152  624 625 628 667 -hsync -vsync 
(49.7 kHz e)
Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Modeline "800x600"x0.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync 
(46.9 kHz e)
Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Modeline "800x600"x0.0   50.00  800 856 976 1040  600 637 643 666 +hsync +vsync 
(48.1 kHz e)
Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Modeline "1152x864"x0.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync 
+vsync (67.5 kHz e)
Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Modeline "1280x1024"x0.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 
+hsync +vsync (64.0 kHz e)
Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Modeline "1680x1050"x0.0  146.25  1680 1784 1960 2240  1050 1053 1059 1089 
-hsync +vsync (65.3 kHz e)
Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Modeline "1440x900"x0.0  136.75  1440 1536 1688 1936  900 903 909 942 -hsync 
+vsync (70.6 kHz e)
Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Modeline "1440x900"x0.0  106.50  1440 1520 1672 1904  900 903 909 934 -hsync 
+vsync (55.9 kHz e)
Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Modeline "1600x1200"x0.0  162.00  1600 1664 1856 2160  1200 1201 1204 1250 
+hsync +vsync (75.0 kHz e)
Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Modeline "1280x960"x0.0  108.00  1280 1376 1488 1800  960 961 964 1000 +hsync 
+vsync (60.0 kHz e)
Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Modeline "1280x720"x60.0   74.48  1280 1336 1472 1664  720 721 724 746 -hsync 
+vsync (44.8 kHz e)

This can easily be duplicated 

[Touch-packages] [Bug 1629632] Re: Sap driver initialization failed, sap-server: Operation not permitted

[nda888]

The issue still exits on Debian 9

Please help, thanks so much

** Attachment added: "Screenshot at 2018-08-24 11-17-00.png"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1629632/+attachment/5180073/+files/Screenshot%20at%202018-08-24%2011-17-00.png

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

Title:
  Sap driver initialization failed, sap-server: Operation not permitted

Status in bluez package in Ubuntu:
  Fix Released
Status in bluez package in Debian:
  New

Bug description:
  Hi,

  here are are messages from the bluetooth daemon:

  $ journalctl -b | grep bluetoothd
  Oct 01 17:24:35 xeelee bluetoothd[1104]: Bluetooth daemon 5.41
  Oct 01 17:24:35 xeelee bluetoothd[1104]: Starting SDP server
  Oct 01 17:24:36 xeelee bluetoothd[1104]: Bluetooth management interface 1.13 
initialized
  Oct 01 17:24:36 xeelee bluetoothd[1104]: Failed to obtain handles for 
"Service Changed" characteristic
  Oct 01 17:24:36 xeelee bluetoothd[1104]: Sap driver initialization failed.
  Oct 01 17:24:36 xeelee bluetoothd[1104]: sap-server: Operation not permitted 
(1)

  There are at least 2 errors concerning:
   - handles
   - Sap driver/server

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: bluez 5.41-0ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-19.21-lowlatency 4.8.0-rc8
  Uname: Linux 4.8.0-19-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Oct  2 09:59:43 2016
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-19-lowlatency 
root=UUID=347d095b-3b19-412b-841e-acfd162e2c53 ro quiet splash nomdmonddf 
nomdmonisw vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to yakkety on 2016-03-31 (184 days ago)
  dmi.bios.date: 03/25/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: HM77-HT
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd03/25/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM77-HT:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.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: To Be Filled By O.E.M.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: DC:85:DE:57:27:6F  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING PSCAN ISCAN 
RX bytes:1974 acl:0 sco:0 events:132 errors:0
TX bytes:6033 acl:0 sco:0 commands:132 errors:0

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

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

[Touch-packages] [Bug 1783693] Re: failed to install winepackage sudo 1.8.21p2-3ubuntu1 failed to install/upgrade: instalado sudo paquete pre-removal guión el subproceso devolvió un error con estado d

[Balint Reczey]

The problem occurs when sudo:i386 is replacing sudo:amd64.

As the error message suggests please export SUDO_FORCE_REMOVE=yes to
make the operation succeed as a workaround, like this:

sudo env SUDO_FORCE_REMOVE=yes apt install sudo:i386


The original error message can be observed in DpkgTerminalLog.txt:

Desinstalando sudo (1.8.21p2-3ubuntu1) ...
You have asked that the sudo package be removed,
but no root password has been set.
Without sudo, you may not be able to gain administrative privileges.

If you would prefer to access the root account with su(1)
or by logging in directly,
you must set a root password with "sudo passwd".

If you have arranged other means to access the root account,
and you are sure this is what you want,
you may bypass this check by setting an environment variable 
(export SUDO_FORCE_REMOVE=yes).

Refusing to remove sudo.
dpkg: error al procesar el paquete sudo (--remove):
 instalado sudo paquete pre-removal guión el subproceso devolvió un error con 
estado de salida 1

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

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

Title:
  failed to install winepackage sudo 1.8.21p2-3ubuntu1 failed to
  install/upgrade: instalado sudo paquete pre-removal guión el
  subproceso devolvió un error con estado de salida 1

Status in sudo package in Ubuntu:
  Invalid

Bug description:
  no direct access after installing wine

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: sudo 1.8.21p2-3ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Thu Jul 26 00:28:22 2018
  ErrorMessage: instalado sudo paquete pre-removal guión el subproceso devolvió 
un error con estado de salida 1
  InstallationDate: Installed on 2018-07-21 (4 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: sudo
  Title: package sudo 1.8.21p2-3ubuntu1 failed to install/upgrade: instalado 
sudo paquete pre-removal guión el subproceso devolvió un error con estado de 
salida 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   /etc/sudoers análisis OK
   /etc/sudoers.d/README análisis OK

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

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

[Touch-packages] [Bug 1787548] Re: PAM fscrypt adds root(0) group to all users called by su

[Tyler Hicks]

I've uploaded an fscrypt security update to the Ubuntu Security PPA.
Ubuntu Security will release it once they've reviewed and approved the
changes.

** Information type changed from Private Security to Public Security

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

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

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

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

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

Title:
  PAM fscrypt adds root(0) group to all users called by su

Status in Shadow:
  Invalid
Status in fscrypt package in Ubuntu:
  Confirmed
Status in shadow package in Ubuntu:
  Invalid

Bug description:
  related packages: /bin/su (from login , shadow)

  OS: ubuntu 18.04.1, updated

  Bug: a normal user (not in 'root' group), when the PAM module fscrypt
  is active, all calls of su give the user additional group root(0).

  Results: this is a permission escalation, such user can now delete
  files owned by root group (where permisions are g+w)

  Steps to reproduce: 
  0/ login uses pam unix authentication module (default on ubuntu, no action 
needed)
  0.1/ create a new user: 
  # useradd developer

  1/ verify:
  #id developer 
  // on my system, shows
  // uid=1004(developer) gid=1004(developer) groups=1004(developer) 
  \su - developer -c id
  sudo -u developer id

  2/ enable pam-fscrypt
  # apt install libpam-fscrypt
  # pam-auth-update --enable fscrypt

  3/ verify again (bug shows)
  // repeate step 1/ 
  // the su command will show the bug (sudo won't, interestingly)
  \su - developer -c id
  // uid=1004(developer) gid=1004(developer) groups=1004(developer),0(root)

  4/ workaround and return to original state:
  pam-auth-update --disable fscrypt
  apt remove  libpam-fscrypt

  Thank you,

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

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

[Touch-packages] [Bug 1788597] Re: ubiquity broken with console-setup 1.178ubuntu2.5

[Adam Conrad]

*sigh*... That exit really wanted to be a return.

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

Title:
  ubiquity broken with console-setup 1.178ubuntu2.5

Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  Since this version of console-setup in bionic ubiquity now skips the
  Keyboard and Wireless pages.

  http://launchpadlibrarian.net/382474004/console-
  setup_1.178ubuntu2.4_1.178ubuntu2.5.diff.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1788597/+subscriptions

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

[Touch-packages] [Bug 1780227] Re: locking sockets broken due to missing AppArmor socket mediation patches

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.4.0-134.160

---
linux (4.4.0-134.160) xenial; urgency=medium

  * linux: 4.4.0-134.160 -proposed tracker (LP: #1787177)

  * locking sockets broken due to missing AppArmor socket mediation patches
(LP: #1780227)
- UBUNTU SAUCE: apparmor: fix apparmor mediating locking non-fs, unix 
sockets

  * Backport namespaced fscaps to xenial 4.4 (LP: #1778286)
- Introduce v3 namespaced file capabilities
- commoncap: move assignment of fs_ns to avoid null pointer dereference
- capabilities: fix buffer overread on very short xattr
- commoncap: Handle memory allocation failure.

  * Xenial update to 4.4.140 stable release (LP: #1784409)
- usb: cdc_acm: Add quirk for Uniden UBC125 scanner
- USB: serial: cp210x: add CESINEL device ids
- USB: serial: cp210x: add Silicon Labs IDs for Windows Update
- n_tty: Fix stall at n_tty_receive_char_special().
- staging: android: ion: Return an ERR_PTR in ion_map_kernel
- n_tty: Access echo_* variables carefully.
- x86/boot: Fix early command-line parsing when matching at end
- ath10k: fix rfc1042 header retrieval in QCA4019 with eth decap mode
- i2c: rcar: fix resume by always initializing registers before transfer
- ipv4: Fix error return value in fib_convert_metrics()
- kprobes/x86: Do not modify singlestep buffer while resuming
- nvme-pci: initialize queue memory before interrupts
- netfilter: nf_tables: use WARN_ON_ONCE instead of BUG_ON in nft_do_chain()
- ARM: dts: imx6q: Use correct SDMA script for SPI5 core
- ubi: fastmap: Correctly handle interrupted erasures in EBA
- mm: hugetlb: yield when prepping struct pages
- tracing: Fix missing return symbol in function_graph output
- scsi: sg: mitigate read/write abuse
- s390: Correct register corruption in critical section cleanup
- drbd: fix access after free
- cifs: Fix infinite loop when using hard mount option
- jbd2: don't mark block as modified if the handle is out of credits
- ext4: make sure bitmaps and the inode table don't overlap with bg
  descriptors
- ext4: always check block group bounds in ext4_init_block_bitmap()
- ext4: only look at the bg_flags field if it is valid
- ext4: verify the depth of extent tree in ext4_find_extent()
- ext4: include the illegal physical block in the bad map ext4_error msg
- ext4: clear i_data in ext4_inode_info when removing inline data
- ext4: add more inode number paranoia checks
- ext4: add more mount time checks of the superblock
- ext4: check superblock mapped prior to committing
- HID: i2c-hid: Fix "incomplete report" noise
- HID: hiddev: fix potential Spectre v1
- HID: debug: check length before copy_to_user()
- x86/mce: Detect local MCEs properly
- x86/mce: Fix incorrect "Machine check from unknown source" message
- media: cx25840: Use subdev host data for PLL override
- mm, page_alloc: do not break __GFP_THISNODE by zonelist reset
- dm bufio: avoid sleeping while holding the dm_bufio lock
- dm bufio: drop the lock when doing GFP_NOIO allocation
- mtd: rawnand: mxc: set spare area size register explicitly
- dm bufio: don't take the lock in dm_bufio_shrink_count
- mtd: cfi_cmdset_0002: Change definition naming to retry write operation
- mtd: cfi_cmdset_0002: Change erase functions to retry for error
- mtd: cfi_cmdset_0002: Change erase functions to check chip good only
- netfilter: nf_log: don't hold nf_log_mutex during user access
- staging: comedi: quatech_daqp_cs: fix no-op loop daqp_ao_insn_write()
- Linux 4.4.140

  * Xenial update to 4.4.139 stable release (LP: #1784382)
- xfrm6: avoid potential infinite loop in _decode_session6()
- netfilter: ebtables: handle string from userspace with care
- ipvs: fix buffer overflow with sync daemon and service
- atm: zatm: fix memcmp casting
- net: qmi_wwan: Add Netgear Aircard 779S
- net/sonic: Use dma_mapping_error()
- Revert "Btrfs: fix scrub to repair raid6 corruption"
- tcp: do not overshoot window_clamp in tcp_rcv_space_adjust()
- Btrfs: make raid6 rebuild retry more
- usb: musb: fix remote wakeup racing with suspend
- bonding: re-evaluate force_primary when the primary slave name changes
- tcp: verify the checksum of the first data segment in a new connection
- ext4: update mtime in ext4_punch_hole even if no blocks are released
- ext4: fix fencepost error in check for inode count overflow during resize
- driver core: Don't ignore class_dir_create_and_add() failure.
- btrfs: scrub: Don't use inode pages for device replace
- ALSA: hda - Handle kzalloc() failure in snd_hda_attach_pcm_stream()
- ALSA: hda: add dock and led support for HP EliteBook 830 G5
- ALSA: hda: add dock and led support for HP ProBook 640 G4
- cpufreq: Fix new policy initialization during limits updates via 

[Touch-packages] [Bug 1788683] [NEW] Totem freeze while reading a .mp4 video

[J-Paul BERARD]

Public bug reported:

When I try to read a .mp4 video, Totem start without movie and quickly freeze, 
or doesn't open the file with an alert dialog-box "Internal data stream error"
The files can be red by VLC or QuickTime on a Mac without problem

Ubuntu 18.04
libgstreamer1.0-0:amd64  1.14.1-1~ubuntu18.04.1

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libgstreamer1.0-0 1.14.1-1~ubuntu18.04.1
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
Uname: Linux 4.15.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 23 20:49:09 2018
InstallationDate: Installed on 2018-04-27 (118 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: gstreamer1.0
UpgradeStatus: No upgrade log present (probably fresh install)
XorgLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: 
'/var/log/Xorg.0.log'

** Affects: gstreamer1.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic wayland-session

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

Title:
  Totem freeze while reading a .mp4 video

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  When I try to read a .mp4 video, Totem start without movie and quickly 
freeze, or doesn't open the file with an alert dialog-box "Internal data stream 
error"
  The files can be red by VLC or QuickTime on a Mac without problem

  Ubuntu 18.04
  libgstreamer1.0-0:amd64  1.14.1-1~ubuntu18.04.1

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgstreamer1.0-0 1.14.1-1~ubuntu18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 23 20:49:09 2018
  InstallationDate: Installed on 2018-04-27 (118 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: 
'/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1788683/+subscriptions

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

[Touch-packages] [Bug 1752411] Re: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck

[Trent Lloyd]

I agree with the sentiment that 5 seconds feels too long, however as a
workaround I decided I would just copy the existing timeout. I certainly
would not want to make it longer since this is in the critical boot
path.

I would generally agree that in general a DNS request should fail faster
however there are some cases where it won't, e.g. spanning tree bring up
on ports can take 2 seconds.

My hope is to correctly fix host after getting this in, since the impact
is very high for affected users.

This check may actually be able to go away, I believe both systemd-
resolved and libnss-mdns (latest version that I think is not in bionic)
implement the .local label checking to do this at runtime instead of
this old hack. So for cosmic+ we can probably get rid of this logic,
which always sucked anyway. As we only needed to really disable nss-mdns
and not avahi entirely (since apps should normally resolve the IPs using
avahi's API anyway, the impact to actual avahi usage is low).

Since the impact is high but only on a smaller subset of users, I think
we should go with matching the current timeout for now and worry about
further improvements later.

I've verified the cosmic upload is working as expected on a non-affected
system.

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

Title:
  bind9-host, avahi-daemon-check-dns.sh hang forever causes network
  connections to get stuck

Status in avahi package in Ubuntu:
  In Progress
Status in bind9 package in Ubuntu:
  Confirmed
Status in openconnect package in Ubuntu:
  Invalid
Status in strongswan package in Ubuntu:
  Invalid
Status in avahi source package in Bionic:
  Triaged
Status in bind9 source package in Bionic:
  Confirmed
Status in avahi source package in Cosmic:
  In Progress
Status in bind9 source package in Cosmic:
  Confirmed
Status in avahi package in Debian:
  New

Bug description:
  [Impact]

   * Network connections for some users fail (in some cases a direct
  interface, in others when connecting a VPN) because the 'host' command
  to check for .local in DNS called by /usr/lib/avahi/avahi-daemon-
  check-dns.sh never times out like it should - leaving the script
  hanging indefinitely blocking interface up and start-up. This appears
  to be a bug in host caused in some circumstances however we implement
  a workaround to call it under 'timeout' as the issue with 'host' has
  not easily been identified, and in any case acts as a fall-back.

  [Test Case]

   * Multiple people have been unable to create a reproducer on a
  generic machine (e.g. it does not occur in a VM), I have a specific
  machine I can reproduce it on (a Skull Canyon NUC with Intel I219-LM)
  by simply "ifdown br0; ifup br0" and there are clearly 10s of other
  users affected in varying circumstances that all involve the same
  symptoms but no clear test case exists. Best I can suggest is that I
  test the patch on my system to ensure it works as expected, and the
  change is only 1 line which is fairly easily auditible and
  understandable.

  [Regression Potential]

   * The change is a single line change to the shell script to call host with 
"timeout". When tested on working and non-working system this appears to 
function as expected. I believe the regression potential for this is 
subsequently low.
   * In attempt to anticipate possible issues, I checked that the timeout 
command is in the same path (/usr/bin) as the host command that is already 
called without a path, and the coreutils package (which contains timeout) is an 
Essential package. I also checked that timeout is not a built-in in bash, for 
those that have changed /bin/sh to bash (just in case).

  [Other Info]
   
   * N/A

  [Original Bug Description]

  On 18.04 Openconnect connects successfully to any of multiple VPN
  concentrators but network traffic does not flow across the VPN tunnel
  connection. When testing on 16.04 this works flawlessly. This also
  worked on this system when it was on 17.10.

  I have tried reducing the mtu of the tun0 network device but this has
  not resulted in me being able to successfully ping the IP address.

  Example showing ping attempt to the IP of DNS server:

  ~$ 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 172.29.88.11
  nameserver 127.0.0.53

  liam@liam-lat:~$ netstat -nr
  Kernel IP routing table
  Destination Gateway Genmask Flags   MSS Window  irtt Iface
  0.0.0.0 192.168.1.1 0.0.0.0 UG0 0  0 
wlp2s0
  105.27.198.106  192.168.1.1 255.255.255.255 UGH   0 0  0 
wlp2s0
  169.254.0.0 0.0.0.0

[Touch-packages] [Bug 1752411] Re: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck

[ Christian Ehrhardt ]

Thanks Trent for the extra verification.
Tests also look good so far, but currently since a lot got uploaded due to 
feature freeze some tests take a while.
We should have that in cosmic soon and then can pick the same for Bionic.

Thanks also for your thoughts on a better long term solution.

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

Title:
  bind9-host, avahi-daemon-check-dns.sh hang forever causes network
  connections to get stuck

Status in avahi package in Ubuntu:
  In Progress
Status in bind9 package in Ubuntu:
  Confirmed
Status in openconnect package in Ubuntu:
  Invalid
Status in strongswan package in Ubuntu:
  Invalid
Status in avahi source package in Bionic:
  Triaged
Status in bind9 source package in Bionic:
  Confirmed
Status in avahi source package in Cosmic:
  In Progress
Status in bind9 source package in Cosmic:
  Confirmed
Status in avahi package in Debian:
  New

Bug description:
  [Impact]

   * Network connections for some users fail (in some cases a direct
  interface, in others when connecting a VPN) because the 'host' command
  to check for .local in DNS called by /usr/lib/avahi/avahi-daemon-
  check-dns.sh never times out like it should - leaving the script
  hanging indefinitely blocking interface up and start-up. This appears
  to be a bug in host caused in some circumstances however we implement
  a workaround to call it under 'timeout' as the issue with 'host' has
  not easily been identified, and in any case acts as a fall-back.

  [Test Case]

   * Multiple people have been unable to create a reproducer on a
  generic machine (e.g. it does not occur in a VM), I have a specific
  machine I can reproduce it on (a Skull Canyon NUC with Intel I219-LM)
  by simply "ifdown br0; ifup br0" and there are clearly 10s of other
  users affected in varying circumstances that all involve the same
  symptoms but no clear test case exists. Best I can suggest is that I
  test the patch on my system to ensure it works as expected, and the
  change is only 1 line which is fairly easily auditible and
  understandable.

  [Regression Potential]

   * The change is a single line change to the shell script to call host with 
"timeout". When tested on working and non-working system this appears to 
function as expected. I believe the regression potential for this is 
subsequently low.
   * In attempt to anticipate possible issues, I checked that the timeout 
command is in the same path (/usr/bin) as the host command that is already 
called without a path, and the coreutils package (which contains timeout) is an 
Essential package. I also checked that timeout is not a built-in in bash, for 
those that have changed /bin/sh to bash (just in case).

  [Other Info]
   
   * N/A

  [Original Bug Description]

  On 18.04 Openconnect connects successfully to any of multiple VPN
  concentrators but network traffic does not flow across the VPN tunnel
  connection. When testing on 16.04 this works flawlessly. This also
  worked on this system when it was on 17.10.

  I have tried reducing the mtu of the tun0 network device but this has
  not resulted in me being able to successfully ping the IP address.

  Example showing ping attempt to the IP of DNS server:

  ~$ 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 172.29.88.11
  nameserver 127.0.0.53

  liam@liam-lat:~$ netstat -nr
  Kernel IP routing table
  Destination Gateway Genmask Flags   MSS Window  irtt Iface
  0.0.0.0 192.168.1.1 0.0.0.0 UG0 0  0 
wlp2s0
  105.27.198.106  192.168.1.1 255.255.255.255 UGH   0 0  0 
wlp2s0
  169.254.0.0 0.0.0.0 255.255.0.0 U 0 0  0 
docker0
  172.17.0.0  0.0.0.0 255.255.0.0 U 0 0  0 
docker0
  172.29.0.0  0.0.0.0 255.255.0.0 U 0 0  0 tun0
  172.29.88.110.0.0.0 255.255.255.255 UH0 0  0 tun0
  192.168.1.0 0.0.0.0 255.255.255.0   U 0 0  0 
wlp2s0
  liam@liam-lat:~$ ping 172.29.88.11
  PING 172.29.88.11 (172.29.88.11) 56(84) bytes of data.
  ^C
  --- 172.29.88.11 ping statistics ---
  4 packets transmitted, 0 received, 100% packet loss, time 3054ms

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: openconnect 7.08-3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 28 22:11:33 2018
  InstallationDate: Installed on 2017-06-15 (258 days ago)
  

[Touch-packages] [Bug 1788597] Re: ubiquity broken with console-setup 1.178ubuntu2.5

[Adam Conrad]

** Also affects: console-setup (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: console-setup (Ubuntu)
 Assignee: (unassigned) => Adam Conrad (adconrad)

** Changed in: console-setup (Ubuntu Bionic)
 Assignee: (unassigned) => Adam Conrad (adconrad)

** Changed in: console-setup (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: console-setup (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: console-setup (Ubuntu)
   Status: In Progress => Fix Committed

** Description changed:

- Since this version of console-setup in bionic ubiquity now skips the
- Keyboard and Wireless pages.
+ [ SRU Justification ]
+ Due to my brain being in the wrong language, a function was exiting the 
script instead of returning.  Derp.
+ 
+ [ Regression Potential ]
+ N'much.
+ 
+ [ Test Case ]
+ Build a new ubiquity and see if we can haz keyboard again.
+ 
+ [ Original Bug ]
+ Since this version of console-setup in bionic ubiquity now skips the Keyboard 
and Wireless pages.
  
  http://launchpadlibrarian.net/382474004/console-
  setup_1.178ubuntu2.4_1.178ubuntu2.5.diff.gz

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

Title:
  ubiquity broken with console-setup 1.178ubuntu2.5

Status in console-setup package in Ubuntu:
  Fix Committed
Status in console-setup source package in Bionic:
  In Progress

Bug description:
  [ SRU Justification ]
  Due to my brain being in the wrong language, a function was exiting the 
script instead of returning.  Derp.

  [ Regression Potential ]
  N'much.

  [ Test Case ]
  Build a new ubiquity and see if we can haz keyboard again.

  [ Original Bug ]
  Since this version of console-setup in bionic ubiquity now skips the Keyboard 
and Wireless pages.

  http://launchpadlibrarian.net/382474004/console-
  setup_1.178ubuntu2.4_1.178ubuntu2.5.diff.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1788597/+subscriptions

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

[Touch-packages] [Bug 1134036] Re: Failure when using ssh with a locale that is not configured on the server

[Michael Hudson-Doyle]

Ah sorry, now done.

** Description changed:

- If LC_ALL is not set (which seems to be the default on a few server
- installations I've done now), mid way through installing, you get this
- backtrace and then the installation just hangs.  You can ctrl-c out of
- it but the package is left half configured.
+ [impact]
+ The setup:
+ 
+ 1) The user has LC_ALL set to a locale on their machine (or some other LC_* 
variable but it's usually LC_ALL).
+ 2) This locale does not exist on an Ubuntu server.
+ 3) The user sshes into the server.
+ 
+ ssh (at least with the settings that are default on Debian and Ubuntu
+ and Fedora) send the value of LC_ALL to the remote server, where the
+ default settings on Ubuntu allow this to be set in the environment of
+ the process it launches.
+ 
+ Because we are now in a situation where LC_ALL is set to a value that is
+ not valid for the system, various undesirable things happen, including
+ ugly messages from cloud-init and perl complaining every time a perl
+ process starts and the bug that the original description below
+ describes.
+ 
+ [test case]
+ Configure the setup as described above. Ssh into the server and run "perl < 
/dev/null" and check for warnings.
+ 
+ [regression potential]
+ This adds a step to the startup of every login shell, which obviously is not 
entirely trivial. However, the new executable being invoked is very simple and 
even if it fails, the startup of the shell should not be inhibited.
+ 
+ 
+ [original description]
+ 
+ 
+ If LC_ALL is not set (which seems to be the default on a few server 
installations I've done now), mid way through installing, you get this 
backtrace and then the installation just hangs.  You can ctrl-c out of it but 
the package is left half configured.
  
  Traceback (most recent call last):
    File "/usr/bin/django-admin", line 5, in 
  management.execute_from_command_line()
    File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 443, in execute_from_command_line
  utility.execute()
    File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 382, in execute
  self.fetch_command(subcommand).run_from_argv(self.argv)
    File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", 
line 196, in run_from_argv
  self.execute(*args, **options.__dict__)
    File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", 
line 232, in execute
  output = self.handle(*args, **options)
    File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", 
line 371, in handle
  return self.handle_noargs(**options)
    File 
"/usr/lib/python2.7/dist-packages/south/management/commands/syncdb.py", line 
90, in handle_noargs
  syncdb.Command().execute(**options)
    File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", 
line 232, in execute
  output = self.handle(*args, **options)
    File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", 
line 371, in handle
  return self.handle_noargs(**options)
    File 
"/usr/lib/python2.7/dist-packages/django/core/management/commands/syncdb.py", 
line 57, in handle_noargs
  cursor = connection.cursor()
    File "/usr/lib/python2.7/dist-packages/django/db/backends/__init__.py", 
line 308, in cursor
  cursor = util.CursorWrapper(self._cursor(), self)
    File 
"/usr/lib/python2.7/dist-packages/django/db/backends/postgresql_psycopg2/base.py",
 line 177, in _cursor
  self.connection = Database.connect(**conn_params)
    File "/usr/lib/python2.7/dist-packages/psycopg2/__init__.py", line 179, in 
connect
  connection_factory=connection_factory, async=async)
  psycopg2.OperationalError: FATAL:  password authentication failed for user 
"maas"
  FATAL:  password authentication failed for user "maas"
  
- 
  Related bugs:
-  * bug 969462: [postgres] fails to start after install if invalid locale is 
set
+  * bug 969462: [postgres] fails to start after install if invalid locale is 
set

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

Title:
  Failure when using ssh with a locale that is not configured on the
  server

Status in base-files package in Ubuntu:
  Fix Released
Status in maas package in Ubuntu:
  Invalid
Status in base-files source package in Bionic:
  New
Status in maas source package in Bionic:
  New

Bug description:
  [impact]
  The setup:

  1) The user has LC_ALL set to a locale on their machine (or some other LC_* 
variable but it's usually LC_ALL).
  2) This locale does not exist on an Ubuntu server.
  3) The user sshes into the server.

  ssh (at least with the settings that are default on Debian and Ubuntu
  and Fedora) send the value of LC_ALL to the remote server, where the
  default settings on Ubuntu allow this to be set in the environment of
  the process it launches.

  Because we 

[Touch-packages] [Bug 1772405] Re: freeipa dns install does not correctly configure reverse zones due to systemd-resolved

[Launchpad Bug Tracker]

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

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

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

Title:
  freeipa dns install does not correctly configure reverse zones due to
  systemd-resolved

Status in freeipa package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 18.04, ipa-dns-intall (or ipa-server-install when asking to
  configure BIND) does not create reverse DNS zones for my domain. Note
  that I already fixed (or more correctly, circumvented) other bugs
  involving BIND, such as
  https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1769440.

  The problem seems due to the presence of systemd-resolved. When ipa-
  dns-install valuates whether to create a reverse DNS zone, it tries to
  use the local DNS for resolving the IP address of the server. When you
  want to install BIND alongside IPA, this normally fails, and the
  installer knows he needs to configure an appropriate reverse zone. But
  when systemd-resolved is active, it takes the role of local DNS and
  answers this query: therefore, the installer thinks a reverse DNS zone
  is already present.

  To fix this problem I had to perform the following steps before calling 
ipa-dns-install (or ipa-server-install):
  1) stop systemd-resolved with "systemctl stop systemd-resolved".
  2) disable systemd-resolved with "systemctl disable systemd-resolved".
  3) delete the file "/etc/resolv.conf", which is a symlink to a file created 
by systemd.
  4) optionally, recreate "/etc/resolv.conf" pointing to the (real) local DNS.

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

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

[Touch-packages] [Bug 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable

[Johannes Michael]

A simple restart fixed this for me on Ubuntu 18.04

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

Title:
  Alt+left/right arrows switch between tty consoles (Gnome Shell
  vanishes), cannot disable

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I'm used to using alt+left/right arrow to navigate back and forward in
  web browsers and elsewhere (nautilus)...  But on this fresh install of
  Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty
  consoles (the ctrl+alt+f1 ones).  But it's not listed as one of the
  shortcuts in the "keyboard" menu, so I don't know how to disable it...

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

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

[Touch-packages] [Bug 1780076] Re: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~binli/ubuntu/+source/gdm3/+git/lp1780076/+merge/353619

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

Title:
  18.04 login screen is skewed/distorted (incorrect stride) when using
  hibmc_drm graphics

Status in gdm3 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/219

  We found the login screen is blur, with Huawei's chip.

  05:00.0 VGA compatible controller [0300]: Huawei Technologies Co.,
  Ltd. Hi1710 [iBMC Intelligent Management system chip w/VGA support]
  [19e5:1711] (rev 01)

  When we set the Wayland to disable, it could login.

  [daemon]
  # Uncoment the line below to force the login screen to use Xorg
  WaylandEnable=false

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

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

[Touch-packages] [Bug 268726]

[madbiologist]

Still occurring with poppler 0.41.0-0ubuntu1.1

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

Title:
  Evince don't show the colour correctly in background-color in tables
  (create with OOo)

Status in Poppler:
  Unknown
Status in poppler package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: evince

  Hi!

  I use Ubuntu hardy 8.04 with last updates. The problem that I tell is
  very very old.

  In the tables with columns (or rows) merged with a colour background (ex, 
red) evince shows lines on each box.
  I attach an example created with OOo Calc.

  PS: if you open the PDF with Adobe Reader it shows correctly.

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

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

[Touch-packages] [Bug 1780076] Re: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics

[Bin Li]

@ubuntu-sponsors,

 Could you helped reviewed the 0001-Disable-wayland-for-Huawei-
Hi1710-LP-1780076.patch for 18.10? Thanks!

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

Title:
  18.04 login screen is skewed/distorted (incorrect stride) when using
  hibmc_drm graphics

Status in gdm3 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/219

  We found the login screen is blur, with Huawei's chip.

  05:00.0 VGA compatible controller [0300]: Huawei Technologies Co.,
  Ltd. Hi1710 [iBMC Intelligent Management system chip w/VGA support]
  [19e5:1711] (rev 01)

  When we set the Wayland to disable, it could login.

  [daemon]
  # Uncoment the line below to force the login screen to use Xorg
  WaylandEnable=false

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

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

[Touch-packages] [Bug 1780076] Re: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics

[Bin Li]

For 18.10, I made a patch for it.

  * Disable wayland for Huawei Hi1710. (LP: #1780076)
+ Add ubuntu_disable_wayland_huawei_chipsets.patch
+ gdm3.install: Fix udev path from /usr/lib/udev to lib/udev.

And I my code is based on cosmic-devel.
https://code.launchpad.net/~binli/ubuntu/+source/gdm3/+git/lp1780076


** Patch added: "0001-Disable-wayland-for-Huawei-Hi1710-LP-1780076.patch"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780076/+attachment/5179560/+files/0001-Disable-wayland-for-Huawei-Hi1710-LP-1780076.patch

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

Title:
  18.04 login screen is skewed/distorted (incorrect stride) when using
  hibmc_drm graphics

Status in gdm3 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/219

  We found the login screen is blur, with Huawei's chip.

  05:00.0 VGA compatible controller [0300]: Huawei Technologies Co.,
  Ltd. Hi1710 [iBMC Intelligent Management system chip w/VGA support]
  [19e5:1711] (rev 01)

  When we set the Wayland to disable, it could login.

  [daemon]
  # Uncoment the line below to force the login screen to use Xorg
  WaylandEnable=false

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

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

[Touch-packages] [Bug 268726]

[Gitlab-migration]

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/poppler/poppler/issues/429.

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

Title:
  Evince don't show the colour correctly in background-color in tables
  (create with OOo)

Status in Poppler:
  Unknown
Status in poppler package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: evince

  Hi!

  I use Ubuntu hardy 8.04 with last updates. The problem that I tell is
  very very old.

  In the tables with columns (or rows) merged with a colour background (ex, 
red) evince shows lines on each box.
  I attach an example created with OOo Calc.

  PS: if you open the PDF with Adobe Reader it shows correctly.

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

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

[Touch-packages] [Bug 268726] Re: Evince don't show the colour correctly in background-color in tables (create with OOo)

[Bug Watch Updater]

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

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

Title:
  Evince don't show the colour correctly in background-color in tables
  (create with OOo)

Status in Poppler:
  Unknown
Status in poppler package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: evince

  Hi!

  I use Ubuntu hardy 8.04 with last updates. The problem that I tell is
  very very old.

  In the tables with columns (or rows) merged with a colour background (ex, 
red) evince shows lines on each box.
  I attach an example created with OOo Calc.

  PS: if you open the PDF with Adobe Reader it shows correctly.

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

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

[Touch-packages] [Bug 1788486] Re: apt behaviour with strict dependencies

[Julian Andres Klode]

The solver in EDSP form is intended for use by autopkgtest, as
autopkgtest really needs the ability to install stuff from proposed as
needed. It won't make for a general purpose solver.

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

Title:
  apt behaviour with strict dependencies

Status in apt package in Ubuntu:
  Confirmed
Status in apt source package in Xenial:
  Confirmed
Status in apt source package in Bionic:
  Confirmed

Bug description:
  [Impact]

  We notice that situation while investigating a security update using
  Landscape, but it also applies to 'apt' outside the Landscape context.

  'apt' should be smarter to detect/install packages with strict
  dependencies such as systemd[1] when a version is specified for
  upgrade (Ex: $ apt-get install systemd=229-4ubuntu-21.1).

  It should automatically install the dependencies (if any) from that
  same version as well instead of failing trying to install the highest
  version available (if any) while installing the specified version for
  the one mentionned :

  
  $ apt-get install systemd=229-4ubuntu-21.1
  
  "systemd : Depends: libsystemd0 (= 229-4ubuntu21.1) but 229-4ubuntu21.4 is to 
be installed"
  =

  To face that problem :
  - Package with lower version should be found in -security ( Ex: 
systemd/229-4ubuntu21.1 )
  - Package with higher version should be found in -updates ( Ex: 
systemd/229-4ubuntu21.4 )
  - Package should have strict dependencies ( Ex: libsystemd0 (= 
${binary:Version}) )
  - The upgrade should only specify version for the package, without it's 
dependencies. (Ex: $ apt-get install systemd=229-4ubuntu-21.1" #systemd without 
libsystemd0 depends)

  Using systemd is a good reproducer, I'm sure finding other package
  with the same situation is easy.

  It has been easily reproduced with systemd on Xenial and Bionic so
  far.

  [1] debian/control
  Depends: ${shlibs:Depends},
  ${misc:Depends},
  libsystemd0 (= ${binary:Version}),
  ...

  [Workaround]
  If package + dependencies are specified, the upgrade work just fine :

  Ex: $ apt-get install systemd=229-4ubuntu-21.1
  libsystemd0=229-4ubuntu-21.1

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

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

[Touch-packages] [Bug 1788486] Re: apt behaviour with strict dependencies

[Julian Andres Klode]

I disagree. Being strict about the policy is a good thing - it gives you
a predictable result.

That said, you could install zsh/release and that does do some switching
of candidates to make that work. I don't like that. It also does not
work entirely reliably. I just closed two or three of these bugs as
Won't Fix or Invalid or something.

One exception I'd consider to be a valid thing is to switch candidates
of packages from the same source package, but that only helps for a
limited number of problems.

We are in desperate need of a new solver, and I hope to get
https://salsa.debian.org/apt-team/apt-solver-kalel/ working eventually.
But even there, by default, we're strict about policy. You'd get an
option to relax policy and determine a best solution where there is no
strict solution available. But that should require an explicit opt-in.

I do not plan to backport that solver to older releases, except as an
EDSP (external dependency solver protocol) solver. But solvers like that
are remarkably slow.

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

Title:
  apt behaviour with strict dependencies

Status in apt package in Ubuntu:
  Confirmed
Status in apt source package in Xenial:
  Confirmed
Status in apt source package in Bionic:
  Confirmed

Bug description:
  [Impact]

  We notice that situation while investigating a security update using
  Landscape, but it also applies to 'apt' outside the Landscape context.

  'apt' should be smarter to detect/install packages with strict
  dependencies such as systemd[1] when a version is specified for
  upgrade (Ex: $ apt-get install systemd=229-4ubuntu-21.1).

  It should automatically install the dependencies (if any) from that
  same version as well instead of failing trying to install the highest
  version available (if any) while installing the specified version for
  the one mentionned :

  
  $ apt-get install systemd=229-4ubuntu-21.1
  
  "systemd : Depends: libsystemd0 (= 229-4ubuntu21.1) but 229-4ubuntu21.4 is to 
be installed"
  =

  To face that problem :
  - Package with lower version should be found in -security ( Ex: 
systemd/229-4ubuntu21.1 )
  - Package with higher version should be found in -updates ( Ex: 
systemd/229-4ubuntu21.4 )
  - Package should have strict dependencies ( Ex: libsystemd0 (= 
${binary:Version}) )
  - The upgrade should only specify version for the package, without it's 
dependencies. (Ex: $ apt-get install systemd=229-4ubuntu-21.1" #systemd without 
libsystemd0 depends)

  Using systemd is a good reproducer, I'm sure finding other package
  with the same situation is easy.

  It has been easily reproduced with systemd on Xenial and Bionic so
  far.

  [1] debian/control
  Depends: ${shlibs:Depends},
  ${misc:Depends},
  libsystemd0 (= ${binary:Version}),
  ...

  [Workaround]
  If package + dependencies are specified, the upgrade work just fine :

  Ex: $ apt-get install systemd=229-4ubuntu-21.1
  libsystemd0=229-4ubuntu-21.1

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

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

[Touch-packages] [Bug 1762384] Re: libgpgme-dev installs libgpgme-pthread.so in /usr/lib/${DEB_HOST_MULTIARCH}, literally

[Julian Andres Klode]

I checked the build logs for arm64, as they were done already, and it
works:

old version -1ubuntu1:

lrwxrwxrwx root/root 0 2018-01-15 13:22
./usr/lib/${DEB_HOST_MULTIARCH}/libgpgme-pthread.so -> libgpgme.so

with the -1ubuntu2 in proposed:

lrwxrwxrwx root/root 0 2018-08-14 14:53 ./usr/lib/aarch64-linux-
gnu/libgpgme-pthread.so -> libgpgme.so


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

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

Title:
  libgpgme-dev installs libgpgme-pthread.so in
  /usr/lib/${DEB_HOST_MULTIARCH}, literally

Status in gpgme1.0 package in Ubuntu:
  Fix Released
Status in gpgme1.0 source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  In Bionic, libgpgme-pthread.so it is installed in 
/usr/lib/${DEB_HOST_MULTIARCH} instead of /usr/lib/x86_64-linux-gnu (the 
variable is not replaced)

  [Test case]
  Check that package installs to correct location

  [Regression potential]
  Packages looking for libgpgme-pthread find it now and might enable gpgme when 
they did not.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1762384/+subscriptions

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

[Touch-packages] [Bug 1788188] Re: transient systemd ordering cycle in boot with overlayroot

[ Christian Ehrhardt ]

I was pushing this through autopkgtesting on LP-Infra where we see issues with 
that sometimes.
Unfortunately when you need an issue it does not show up, I only have 4 good 
cases:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-ci-train-ppa-service-3372/cosmic/amd64/o/open-iscsi/20180823_070627_52393@/log.gz
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-ci-train-ppa-service-3372/cosmic/amd64/o/open-iscsi/20180822_061335_52393@/log.gz
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-ci-train-ppa-service-3372/cosmic/amd64/o/open-iscsi/20180821_215839_7dcd3@/log.gz
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-ci-train-ppa-service-3372/cosmic/amd64/o/open-iscsi/20180823_083835_52393@/log.gz

I won't retry further, but if anyone wants:
Retrigger is:
https://autopkgtest.ubuntu.com/request.cgi?release=cosmic=amd64=open-iscsi=open-iscsi%2F2.0.874-5ubuntu8%7Eppa0=ci-train-ppa-service%2Fstable-phone-overlay=ci-train-ppa-service%2F3372
And results after a while will show as updated link on:
https://bileto.ubuntu.com/excuses/3372/cosmic.html

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

Title:
  transient systemd ordering cycle in boot with overlayroot

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  open-iscsi test utilizes overlayroot to boot a cloud-image with root
  filesystem on a read-only iscsi server.

  The /etc/fstab file in the image looks like this:
    LABEL=cloudimg-rootfs   /ext4   defaults0 0
    #LABEL=UEFI /boot/efi   vfatdefaults0 0

  when init takes over from the initramfs, we have

    /proc/cmdline:
  nomodeset iscsi_initiator=maas-enlist
  iscsi_target_name=tgt-boot-test-2abbnj iscsi_target_ip=10.0.12.2
  iscsi_target_port=3260 iscsi_initiator=maas-enlist
  ip=maas-enlist:BOOTIF ro net.ifnames=0 BOOTIF_DEFAULT=eth0
  
root=/dev/disk/by-path/ip-10.0.12.2:3260-iscsi-tgt-boot-test-2abbnj-lun-1-part1
  overlayroot=tmpfs console=ttyS0
  ds=nocloud-net;seedfrom=http://10.0.12.2:32600/ init=/bin/bash

    /etc/fstab:
  # cat /etc/fstab
  #
  #  This fstab is in an overlay. The real one can be found at
  #  /media/root-ro/etc/fstab
  #  The original entry for '/' and other mounts have been updated to be 
placed
  #  under /media/root-ro.
  #  To permanently modify this (or any other file), you should change-root 
into
  #  a writable view of the underlying filesystem using:
  #  sudo overlayroot-chroot
  #
  #LABEL=cloudimg-rootfs /media/root-ro/ ext4 ro,defaults,noauto 0 0
  /media/root-ro/ / overlay 
lowerdir=/media/root-ro/,upperdir=/media/root-rw/over0
  #LABEL=UEFI /boot/efi vfat defaults 0 0

   /root/root-ro/etc/fstab:
  LABEL=cloudimg-rootfs   /ext4   defaults0 0
  #LABEL=UEFI /boot/efi   vfatdefaults0 0

   /proc/mounts:
     sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
     proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
     udev /dev devtmpfs 
rw,nosuid,relatime,size=233748k,nr_inodes=58437,mode=755 0 0
     devpts /dev/pts devpts 
rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
     tmpfs /run tmpfs rw,nosuid,noexec,relatime,size=49288k,mode=755 0 0
     /dev/disk/by-path/ip-10.0.12.2:3260-iscsi-tgt-boot-test-2abbnj-lun-1-part1 
/media/root-ro ext4 ro,relatime 0 0
     tmpfs-root /media/root-rw tmpfs rw,relatime 0 0
     overlayroot / overlay 
ro,relatime,lowerdir=/media/root-ro,upperdir=/media/root-rw/overlay,workdir=/media/root-rw/overlay-workdir/_
 0 0

   /proc/1/mountinfo:
     21 28 0:20 / /sys rw,nosuid,nodev,noexec,relatime - sysfs sysfs rw
     22 28 0:4 / /proc rw,nosuid,nodev,noexec,relatime - proc proc rw
     23 28 0:6 / /dev rw,nosuid,relatime - devtmpfs udev 
rw,size=233748k,nr_inodes=58437,mode=755
     24 23 0:21 / /dev/pts rw,nosuid,noexec,relatime - devpts devpts 
rw,gid=5,mode=620,ptmxmode=000
     25 28 0:22 / /run rw,nosuid,noexec,relatime - tmpfs tmpfs 
rw,size=49288k,mode=755
     26 28 8:1 / /media/root-ro ro,relatime - ext4 
/dev/disk/by-path/ip-10.0.12.2:3260-iscsi-tgt-boot-test-2abbnj-lun-1-part1 ro
     27 28 0:23 / /media/root-rw rw,relatime - tmpfs tmpfs-root rw
     28 0 0:24 / / ro,relatime - overlay overlayroot 
ro,lowerdir=/media/root-ro,upperdir=/media/root-rw/overlay,workdir=/media/root-rw/overlay-workdir/_

  overlayroot's scripts/init-bottom/overlayroot script [1] inherits a
  read-only mount of block device on mount point '$ROOTMNT'
  (ROOTMNT=/root). In order to set up the overlayroot, it does the
  following:

   mkdir /media/root-ro /media/root-rw # in the 

[Touch-packages] [Bug 1762384] Re: libgpgme-dev installs libgpgme-pthread.so in /usr/lib/${DEB_HOST_MULTIARCH}, literally

[Łukasz Zemczak]

Hello Corentin, or anyone else affected,

Accepted gpgme1.0 into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/gpgme1.0/1.10.0-1ubuntu2 in a few
hours, and then in the -proposed repository.

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

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

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

** Changed in: gpgme1.0 (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

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

Title:
  libgpgme-dev installs libgpgme-pthread.so in
  /usr/lib/${DEB_HOST_MULTIARCH}, literally

Status in gpgme1.0 package in Ubuntu:
  Fix Released
Status in gpgme1.0 source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  In Bionic, libgpgme-pthread.so it is installed in 
/usr/lib/${DEB_HOST_MULTIARCH} instead of /usr/lib/x86_64-linux-gnu (the 
variable is not replaced)

  [Test case]
  Check that package installs to correct location

  [Regression potential]
  Packages looking for libgpgme-pthread find it now and might enable gpgme when 
they did not.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1762384/+subscriptions

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

[Touch-packages] [Bug 1777994] Re: the header xcb/xinput.h is missing

[Timo Aaltonen]

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

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

Title:
  the header xcb/xinput.h is missing

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

Bug description:
  I suspect this means there should be another package, libxcb-xinput-
  dev perhaps?

  I already did sudo apt install "libxcb*dev" to get all related dev
  packages, but none of them provide xcb/xinput.h.

  The result is that when building Qt from source, it's necessary to use
  a copy of this file which Qt provides
  (qtbase/src/3rdparty/xcb/include/xcb/xinput.h), because it's missing
  from the system.  So if you don't give the option -qt-xcb to
  configure, then Qt will be built without multi-touch support.

  https://bugreports.qt.io/browse/QTBUG-69045

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libxcb1-dev 1.13-1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 21 08:32:12 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 620 [17aa:3802]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 04f2:b5da Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80Y7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic 
root=ZFS=rpool/ROOT/ubuntu ro
  SourcePackage: libxcb
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5NCN38WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 920-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr5NCN38WW:bd02/22/2018:svnLENOVO:pn80Y7:pvrLenovoYOGA920-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA920-13IKB:
  dmi.product.family: YOGA 920-13IKB
  dmi.product.name: 80Y7
  dmi.product.version: Lenovo YOGA 920-13IKB
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-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

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

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

[Touch-packages] [Bug 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable

[Nicky De Maeyer]

Confirmed that a recent "ubuntu-base" update on 18.04.1.

running `sudo kbd_mode -s` resolves the issue (havent rebooted yet)

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

Title:
  Alt+left/right arrows switch between tty consoles (Gnome Shell
  vanishes), cannot disable

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I'm used to using alt+left/right arrow to navigate back and forward in
  web browsers and elsewhere (nautilus)...  But on this fresh install of
  Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty
  consoles (the ctrl+alt+f1 ones).  But it's not listed as one of the
  shortcuts in the "keyboard" menu, so I don't know how to disable it...

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

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

[Touch-packages] [Bug 1788597] Re: ubiquity broken with console-setup 1.178ubuntu2.5

[Launchpad Bug Tracker]

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

** Changed in: console-setup (Ubuntu)
   Status: New => Confirmed

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

Title:
  ubiquity broken with console-setup 1.178ubuntu2.5

Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  Since this version of console-setup in bionic ubiquity now skips the
  Keyboard and Wireless pages.

  http://launchpadlibrarian.net/382474004/console-
  setup_1.178ubuntu2.4_1.178ubuntu2.5.diff.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1788597/+subscriptions

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

[Touch-packages] [Bug 1788597] Re: ubiquity broken with console-setup 1.178ubuntu2.5

[Rik Mills]

I can confirm this with both Ubuntu and Kubuntu isos, on:

- Bionic 18.04.1 iso, where console-setup is updated before launching ubiquity
- Bionic daily iso builds
- Cosmic daily iso builds

I have not tested other flavours so far.

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

Title:
  ubiquity broken with console-setup 1.178ubuntu2.5

Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  Since this version of console-setup in bionic ubiquity now skips the
  Keyboard and Wireless pages.

  http://launchpadlibrarian.net/382474004/console-
  setup_1.178ubuntu2.4_1.178ubuntu2.5.diff.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1788597/+subscriptions

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

[Touch-packages] [Bug 1788486] Re: apt behaviour with strict dependencies

[Julian Andres Klode]

So the problem seems to be that landscape assumes that upgrading a
binary package with the same name as a source package yields a usable
result, instead of querying which binaries are installed from that
source and upgrading them.

Like source systemd has systemd and libsystemd, so we should have a
request to upgrade both of them. Or assume source foo builds foo-bin and
libfoo.

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

Title:
  apt behaviour with strict dependencies

Status in apt package in Ubuntu:
  Confirmed
Status in apt source package in Xenial:
  Confirmed
Status in apt source package in Bionic:
  Confirmed

Bug description:
  [Impact]

  We notice that situation while investigating a security update using
  Landscape, but it also applies to 'apt' outside the Landscape context.

  'apt' should be smarter to detect/install packages with strict
  dependencies such as systemd[1] when a version is specified for
  upgrade (Ex: $ apt-get install systemd=229-4ubuntu-21.1).

  It should automatically install the dependencies (if any) from that
  same version as well instead of failing trying to install the highest
  version available (if any) while installing the specified version for
  the one mentionned :

  
  $ apt-get install systemd=229-4ubuntu-21.1
  
  "systemd : Depends: libsystemd0 (= 229-4ubuntu21.1) but 229-4ubuntu21.4 is to 
be installed"
  =

  To face that problem :
  - Package with lower version should be found in -security ( Ex: 
systemd/229-4ubuntu21.1 )
  - Package with higher version should be found in -updates ( Ex: 
systemd/229-4ubuntu21.4 )
  - Package should have strict dependencies ( Ex: libsystemd0 (= 
${binary:Version}) )
  - The upgrade should only specify version for the package, without it's 
dependencies. (Ex: $ apt-get install systemd=229-4ubuntu-21.1" #systemd without 
libsystemd0 depends)

  Using systemd is a good reproducer, I'm sure finding other package
  with the same situation is easy.

  It has been easily reproduced with systemd on Xenial and Bionic so
  far.

  [1] debian/control
  Depends: ${shlibs:Depends},
  ${misc:Depends},
  libsystemd0 (= ${binary:Version}),
  ...

  [Workaround]
  If package + dependencies are specified, the upgrade work just fine :

  Ex: $ apt-get install systemd=229-4ubuntu-21.1
  libsystemd0=229-4ubuntu-21.1

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

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

[Touch-packages] [Bug 1776475] Re: Unlocking existing session often requires several attempts.

[Vladyslav Drok]

Using lightdm 1.26.0 in arch with xfce, and experiencing the same
behaviour as described in comment #7, with no errors in the logs. In my
case the delay between "session is locked" message and actual greeter
appearance is around 10 seconds.

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

Title:
  Unlocking existing session often requires several attempts.

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  # Context

  * Computer with several X sessions opened.
  * Users switching from one opened session to another.
  * Lightdm opens new greeter, wait for typing password.
  * User types password.
  * Password is accepted.
  * System closes the current greeter (screen gets black for an instant).

  # Expected

  * User gets back to their already opened session.

  # Observed

  * System immediately opens another greeter.
  * User has to type password again.

  # Reproducible

  * Not always. At times, often, at other times, rare.

  # Additional information

  Users switch session via 
  dm-tool switch-to-user $OTHERUSER
  but I guess bug appears with other means (like menu item like "lock screen", 
etc).

  # Information requested

  lsb_release -rd

  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  
  LC_ALL=C apt-cache policy lightdm

  lightdm:
Installed: 1.26.0-0ubuntu1
Candidate: 1.26.0-0ubuntu1
Version table:
   *** 1.26.0-0ubuntu1 500
  500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Jun 12 14:14:52 2018
  ExecutablePath: /usr/sbin/lightdm
  InstallationDate: Installed on 2018-05-25 (18 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.logrotate.d.lightdm: [modified]
  mtime.conffile..etc.logrotate.d.lightdm: 2018-05-25T06:19:22.081830

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

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

[Touch-packages] [Bug 1787729] Re: [FAILED] Failed to start Process error reports when automatic reporting is enabled.

[Cristian Aravena Romero]

Hello Brian Murray,

The error continues :-(

caravena@caravena-530u3c-530u4c:/var/log$ whoopsie
caravena@caravena-530u3c-530u4c:/var/log$ systemctl status 
apport-autoreport.service
● apport-autoreport.service - Process error reports when automatic reporting is 
enabled
   Loaded: loaded (/lib/systemd/system/apport-autoreport.service; static; 
vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2018-08-23 08:02:30 -03; 1h 
24min ago
  Process: 813 ExecStart=/usr/share/apport/whoopsie-upload-all (code=exited, 
status=1/FAILURE)
 Main PID: 813 (code=exited, status=1/FAILURE)

ago 23 08:02:28 caravena-530u3c-530u4c systemd[1]: Starting Process error 
reports when automatic reporting is enabled...
ago 23 08:02:30 caravena-530u3c-530u4c whoopsie-upload-all[813]: ERROR: 
whoopsie is not running
ago 23 08:02:30 caravena-530u3c-530u4c systemd[1]: apport-autoreport.service: 
Main process exited, code=exited, status=1/FAILURE
ago 23 08:02:30 caravena-530u3c-530u4c systemd[1]: apport-autoreport.service: 
Failed with result 'exit-code'.
ago 23 08:02:30 caravena-530u3c-530u4c systemd[1]: Failed to start Process 
error reports when automatic reporting is enabled.

Kind regards,
--
Cristian Aravena Romero (caravena)

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

Title:
  [FAILED] Failed to start Process error reports when automatic
  reporting is enabled.

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  Attached image.

  Regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: apport 2.20.10-0ubuntu7
  Uname: Linux 4.18.3-041803-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.10-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 18 11:48:00 2018
  InstallationDate: Installed on 2017-10-13 (308 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1788608] [NEW] wget doesn't support compression, it needs zlib1g-dev

[Stephen Kitt]

Public bug reported:

wget can use zlib1g for a few features, notably --compression support.
The Debian package doesn't explicitly build-depend on zlib1g-dev, it
gets it via libgnutls28-dev; since the Ubuntu package drops the latter,
compression support is lost too.

Please consider adding zlib1g-dev. (I've also asked the Debian
maintainer to do so, see the linked bug; however the libgnutls28-dev
removal in Ubuntu should take this into account IMO.)

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

** Affects: wget (Debian)
 Importance: Unknown
 Status: Unknown

** Bug watch added: Debian Bug tracker #907047
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907047

** Also affects: wget (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907047
   Importance: Unknown
   Status: Unknown

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

Title:
  wget doesn't support compression, it needs zlib1g-dev

Status in wget package in Ubuntu:
  New
Status in wget package in Debian:
  Unknown

Bug description:
  wget can use zlib1g for a few features, notably --compression support.
  The Debian package doesn't explicitly build-depend on zlib1g-dev, it
  gets it via libgnutls28-dev; since the Ubuntu package drops the
  latter, compression support is lost too.

  Please consider adding zlib1g-dev. (I've also asked the Debian
  maintainer to do so, see the linked bug; however the libgnutls28-dev
  removal in Ubuntu should take this into account IMO.)

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

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

[Touch-packages] [Bug 1488620] Re: Add LZ4 support to initramfs-tools

[Balint Reczey]

** Bug watch added: Debian Bug tracker #893845
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893845

** Also affects: initramfs-tools (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893845
   Importance: Unknown
   Status: Unknown

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

Title:
  Add LZ4 support to initramfs-tools

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Debian:
  Unknown

Bug description:
  Original Bug Text
  =

  I found that I could enable LZ4 compression for initramfs on my vivid
  machine by installing liblz4-tool package, adding one line to
  mkinitramfs and installing a kernel compiled with CONFIG_CRYPTO_LZ4=y.

  Please include support for (legacy) LZ4.

  Attached patch includes changes made to the latest version (initramfs-
  tools_0.120ubuntu3).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1488620/+subscriptions

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

[Touch-packages] [Bug 1488620] Re: Add LZ4 support to initramfs-tools

[Balint Reczey]

The fix was picked by Debian and is included in Ubuntu starting with
131ubuntu1 in Cosmic.

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Fix Released

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

Title:
  Add LZ4 support to initramfs-tools

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Debian:
  Unknown

Bug description:
  Original Bug Text
  =

  I found that I could enable LZ4 compression for initramfs on my vivid
  machine by installing liblz4-tool package, adding one line to
  mkinitramfs and installing a kernel compiled with CONFIG_CRYPTO_LZ4=y.

  Please include support for (legacy) LZ4.

  Attached patch includes changes made to the latest version (initramfs-
  tools_0.120ubuntu3).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1488620/+subscriptions

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

[Touch-packages] [Bug 1788597] [NEW] ubiquity broken with console-setup 1.178ubuntu2.5

[Jonathan Riddell]

Public bug reported:

Since this version of console-setup in bionic ubiquity now skips the
Keyboard and Wireless pages.

http://launchpadlibrarian.net/382474004/console-
setup_1.178ubuntu2.4_1.178ubuntu2.5.diff.gz

** Affects: console-setup (Ubuntu)
 Importance: Undecided
 Status: Confirmed

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

Title:
  ubiquity broken with console-setup 1.178ubuntu2.5

Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  Since this version of console-setup in bionic ubiquity now skips the
  Keyboard and Wireless pages.

  http://launchpadlibrarian.net/382474004/console-
  setup_1.178ubuntu2.4_1.178ubuntu2.5.diff.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1788597/+subscriptions

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

[Touch-packages] [Bug 1788597] Re: ubiquity broken with console-setup 1.178ubuntu2.5

[Jonathan Riddell]

consistent on Kubuntu and Ubuntu

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

Title:
  ubiquity broken with console-setup 1.178ubuntu2.5

Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  Since this version of console-setup in bionic ubiquity now skips the
  Keyboard and Wireless pages.

  http://launchpadlibrarian.net/382474004/console-
  setup_1.178ubuntu2.4_1.178ubuntu2.5.diff.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1788597/+subscriptions

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

[Touch-packages] [Bug 1488620] Re: Add LZ4 support to initramfs-tools

[Bug Watch Updater]

** Changed in: initramfs-tools (Debian)
   Status: Unknown => Fix Released

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

Title:
  Add LZ4 support to initramfs-tools

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Debian:
  Fix Released

Bug description:
  Original Bug Text
  =

  I found that I could enable LZ4 compression for initramfs on my vivid
  machine by installing liblz4-tool package, adding one line to
  mkinitramfs and installing a kernel compiled with CONFIG_CRYPTO_LZ4=y.

  Please include support for (legacy) LZ4.

  Attached patch includes changes made to the latest version (initramfs-
  tools_0.120ubuntu3).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1488620/+subscriptions

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

[Touch-packages] [Bug 1788598] Re: Xorg crash

[Stefan Dangl]

** Attachment added: "apport's /var/crash/_usr_lib_xorg_Xorg.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1788598/+attachment/5179697/+files/_usr_lib_xorg_Xorg.1000.crash

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  The bug was already in the previous edition of Ubuntu (17.10) using awesome 
window manager.
  After upgrading to Ubuntu 18.04 and switched to xmonad the problem still 
occurs.

  It seems currently that the crash occurs randomly.
  Sometimes not at all for a day, sometimes after only a few minutes three 
times in a row.

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

  $ apt-cache policy xorg
  xorg:
Installed: 1:7.7+19ubuntu7.1
Candidate: 1:7.7+19ubuntu7.1
Version table:
   *** 1:7.7+19ubuntu7.1 500
  500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:7.7+19ubuntu7 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: openafs
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompositorRunning: None
  Date: Thu Aug 23 13:11:40 2018
  DistUpgraded: 2018-07-06 15:34:21,080 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   openafs, 1.8.0pre5, 4.15.0-30-generic, x86_64: installed
   openafs, 1.8.0pre5, 4.15.0-32-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 (ThinkPad X1 Carbon 5th Gen) [17aa:224f]
  InstallationDate: Installed on 2017-10-10 (316 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 20HR002RGE
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-32-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to bionic on 2018-07-06 (47 days ago)
  dmi.bios.date: 05/17/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET35W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HR002RGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET35W(1.20):bd05/17/2017:svnLENOVO:pn20HR002RGE:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HR002RGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 5th
  dmi.product.name: 20HR002RGE
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-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

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

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

[Touch-packages] [Bug 1788598] [NEW] Xorg crash

[Stefan Dangl]

Public bug reported:

The bug was already in the previous edition of Ubuntu (17.10) using awesome 
window manager.
After upgrading to Ubuntu 18.04 and switched to xmonad the problem still occurs.

It seems currently that the crash occurs randomly.
Sometimes not at all for a day, sometimes after only a few minutes three times 
in a row.

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

$ apt-cache policy xorg
xorg:
  Installed: 1:7.7+19ubuntu7.1
  Candidate: 1:7.7+19ubuntu7.1
  Version table:
 *** 1:7.7+19ubuntu7.1 500
500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1:7.7+19ubuntu7 500
500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
Uname: Linux 4.15.0-32-generic x86_64
NonfreeKernelModules: openafs
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CompositorRunning: None
Date: Thu Aug 23 13:11:40 2018
DistUpgraded: 2018-07-06 15:34:21,080 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 openafs, 1.8.0pre5, 4.15.0-30-generic, x86_64: installed
 openafs, 1.8.0pre5, 4.15.0-32-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 620 (ThinkPad X1 Carbon 5th Gen) [17aa:224f]
InstallationDate: Installed on 2017-10-10 (316 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: LENOVO 20HR002RGE
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-32-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: Upgraded to bionic on 2018-07-06 (47 days ago)
dmi.bios.date: 05/17/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: N1MET35W (1.20 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HR002RGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET35W(1.20):bd05/17/2017:svnLENOVO:pn20HR002RGE:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HR002RGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon 5th
dmi.product.name: 20HR002RGE
dmi.product.version: ThinkPad X1 Carbon 5th
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-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

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


** Tags: amd64 apport-bug bionic crash ubuntu

** Attachment added: "apport log file"
   https://bugs.launchpad.net/bugs/1788598/+attachment/5179678/+files/apport.log

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  The bug was already in the previous edition of Ubuntu (17.10) using awesome 
window manager.
  After upgrading to Ubuntu 18.04 and switched to xmonad the problem still 
occurs.

  It seems currently that the crash occurs randomly.
  Sometimes not at all for a day, sometimes after only a few minutes three 
times in a row.

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

  $ apt-cache policy xorg
  xorg:
Installed: 1:7.7+19ubuntu7.1
Candidate: 1:7.7+19ubuntu7.1
Version table:
   *** 1:7.7+19ubuntu7.1 500
  500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:7.7+19ubuntu7 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: openafs
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompositorRunning: None
  Date: Thu Aug 23 13:11:40 2018
  DistUpgraded: 2018-07-06 15:34:21,080 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  

[Touch-packages] [Bug 1788598] Re: Xorg crash

[Stefan Dangl]

** Attachment removed: "apport's /var/crash/_usr_lib_xorg_Xorg.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1788598/+attachment/5179697/+files/_usr_lib_xorg_Xorg.1000.crash

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  The bug was already in the previous edition of Ubuntu (17.10) using awesome 
window manager.
  After upgrading to Ubuntu 18.04 and switched to xmonad the problem still 
occurs.

  It seems currently that the crash occurs randomly.
  Sometimes not at all for a day, sometimes after only a few minutes three 
times in a row.

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

  $ apt-cache policy xorg
  xorg:
Installed: 1:7.7+19ubuntu7.1
Candidate: 1:7.7+19ubuntu7.1
Version table:
   *** 1:7.7+19ubuntu7.1 500
  500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:7.7+19ubuntu7 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: openafs
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompositorRunning: None
  Date: Thu Aug 23 13:11:40 2018
  DistUpgraded: 2018-07-06 15:34:21,080 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   openafs, 1.8.0pre5, 4.15.0-30-generic, x86_64: installed
   openafs, 1.8.0pre5, 4.15.0-32-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 (ThinkPad X1 Carbon 5th Gen) [17aa:224f]
  InstallationDate: Installed on 2017-10-10 (316 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 20HR002RGE
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-32-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to bionic on 2018-07-06 (47 days ago)
  dmi.bios.date: 05/17/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET35W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HR002RGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET35W(1.20):bd05/17/2017:svnLENOVO:pn20HR002RGE:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HR002RGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 5th
  dmi.product.name: 20HR002RGE
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-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

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

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

[Touch-packages] [Bug 1788597] Re: ubiquity broken with console-setup 1.178ubuntu2.5

[Jonathan Riddell]

same problem in ubuntu cosmic ISO cosmic-desktop-amd64.iso from today

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

Title:
  ubiquity broken with console-setup 1.178ubuntu2.5

Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  Since this version of console-setup in bionic ubiquity now skips the
  Keyboard and Wireless pages.

  http://launchpadlibrarian.net/382474004/console-
  setup_1.178ubuntu2.4_1.178ubuntu2.5.diff.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1788597/+subscriptions

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

[Touch-packages] [Bug 1788602] [NEW] package base-files 10.1ubuntu2.2 failed to install/upgrade: fim de ficheiro em stdin na prompt do ficheiro de configuração

[Magno dos Santos Lima]

Public bug reported:

Ubuntu Community would like the help of you to solve this problem

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: base-files 10.1ubuntu2.2
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
Uname: Linux 4.15.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
AptOrdering:
 base-files:amd64: Install
 base-files:amd64: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Thu Aug 23 08:53:13 2018
Dependencies:
 
ErrorMessage: fim de ficheiro em stdin na prompt do ficheiro de configuração
Python3Details: /usr/bin/python3.6, Python 3.6.5, unpackaged
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, unpackaged
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3ubuntu0.1
SourcePackage: base-files
Title: package base-files 10.1ubuntu2.2 failed to install/upgrade: fim de 
ficheiro em stdin na prompt do ficheiro de configuração
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.update-motd.d.50-motd-news: 2018-04-09T08:10:28

** Affects: base-files (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package base-files 10.1ubuntu2.2 failed to install/upgrade: fim de
  ficheiro em stdin na prompt do ficheiro de configuração

Status in base-files package in Ubuntu:
  New

Bug description:
  Ubuntu Community would like the help of you to solve this problem

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: base-files 10.1ubuntu2.2
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  AptOrdering:
   base-files:amd64: Install
   base-files:amd64: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Aug 23 08:53:13 2018
  Dependencies:
   
  ErrorMessage: fim de ficheiro em stdin na prompt do ficheiro de configuração
  Python3Details: /usr/bin/python3.6, Python 3.6.5, unpackaged
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: base-files
  Title: package base-files 10.1ubuntu2.2 failed to install/upgrade: fim de 
ficheiro em stdin na prompt do ficheiro de configuração
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.update-motd.d.50-motd-news: 2018-04-09T08:10:28

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1788602/+subscriptions

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