[Touch-packages] [Bug 1742378] Re: Slight glitch in /etc/cron.daily/apt-compat Ubuntu 16.04.3 in apt-1.2.24

[rklemme]

@Julian I had considered that.  This could be more easily done with
"on_ac_power || return 1" - there is no need for full "if...then...fi".

But both those solutions would have different semantics than what the
script _apparently_ intends to do: on_ac_power returns 0 on AC, 1 on
battery and 255 if the power status cannot be determined.  The current
code of the script indicates that in this case
/usr/lib/apt/apt.systemd.daily should be executed and _only_ be omitted
if on_ac_power returns exactly 1.

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

Title:
  Slight glitch in /etc/cron.daily/apt-compat Ubuntu 16.04.3 in
  apt-1.2.24

Status in apt package in Ubuntu:
  Fix Committed

Bug description:
  I accidentally stumbled across this. If in line 22 on_ac_power returns
  a non zero exit code the next line is never reached. Instead, the
  shell terminates immediately with that non zero exit code because of
  "set -e" in line 3. In this script it does not pose a problem because
  the shell is asked to exit anyway if check_power() returns non zero
  but it works differently than is apparently intended (concluding from
  the logic).

  I will attach a suggest patch and a demo illustrating that the patch
  works as the original script seems to intend to.

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

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

[Touch-packages] [Bug 1742378] Re: Slight glitch in /etc/cron.daily/apt-compat Ubuntu 16.04.3 in apt-1.2.24

[Julian Andres Klode]

Fixed in https://salsa.debian.org/apt-
team/apt/commit/ca2fcc639c7363a04998f650b96573d806b32dd2

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

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

Title:
  Slight glitch in /etc/cron.daily/apt-compat Ubuntu 16.04.3 in
  apt-1.2.24

Status in apt package in Ubuntu:
  Fix Committed

Bug description:
  I accidentally stumbled across this. If in line 22 on_ac_power returns
  a non zero exit code the next line is never reached. Instead, the
  shell terminates immediately with that non zero exit code because of
  "set -e" in line 3. In this script it does not pose a problem because
  the shell is asked to exit anyway if check_power() returns non zero
  but it works differently than is apparently intended (concluding from
  the logic).

  I will attach a suggest patch and a demo illustrating that the patch
  works as the original script seems to intend to.

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

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

[Touch-packages] [Bug 1742378] Re: Slight glitch in /etc/cron.daily/apt-compat Ubuntu 16.04.3 in apt-1.2.24

[Julian Andres Klode]

I'd rather use if ! on_ac_power; then return 1; fi

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

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

** Changed in: apt (Ubuntu)
 Assignee: (unassigned) => Julian Andres Klode (juliank)

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

Title:
  Slight glitch in /etc/cron.daily/apt-compat Ubuntu 16.04.3 in
  apt-1.2.24

Status in apt package in Ubuntu:
  Triaged

Bug description:
  I accidentally stumbled across this. If in line 22 on_ac_power returns
  a non zero exit code the next line is never reached. Instead, the
  shell terminates immediately with that non zero exit code because of
  "set -e" in line 3. In this script it does not pose a problem because
  the shell is asked to exit anyway if check_power() returns non zero
  but it works differently than is apparently intended (concluding from
  the logic).

  I will attach a suggest patch and a demo illustrating that the patch
  works as the original script seems to intend to.

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

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

[Touch-packages] [Bug 1742378] Re: Slight glitch in /etc/cron.daily/apt-compat Ubuntu 16.04.3 in apt-1.2.24

[Julian Andres Klode]

or well, use an explicit if

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

Title:
  Slight glitch in /etc/cron.daily/apt-compat Ubuntu 16.04.3 in
  apt-1.2.24

Status in apt package in Ubuntu:
  Triaged

Bug description:
  I accidentally stumbled across this. If in line 22 on_ac_power returns
  a non zero exit code the next line is never reached. Instead, the
  shell terminates immediately with that non zero exit code because of
  "set -e" in line 3. In this script it does not pose a problem because
  the shell is asked to exit anyway if check_power() returns non zero
  but it works differently than is apparently intended (concluding from
  the logic).

  I will attach a suggest patch and a demo illustrating that the patch
  works as the original script seems to intend to.

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

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

[Touch-packages] [Bug 1742378] Re: Slight glitch in /etc/cron.daily/apt-compat Ubuntu 16.04.3 in apt-1.2.24

[rklemme]

I forgot to mention one thing about the patch: the current behavior is
that when on_ac_power returns 255 the current version of the script
returns with that non zero error code and does not execute
/usr/lib/apt/apt.systemd.daily.  The patched version will execute
/usr/lib/apt/apt.systemd.daily and terminate with whatever exit code
that process generates.

On a side note, "which" can be replaced by "type" which is POSIX
compatible and a shell built in.

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

Title:
  Slight glitch in /etc/cron.daily/apt-compat Ubuntu 16.04.3 in
  apt-1.2.24

Status in apt package in Ubuntu:
  Triaged

Bug description:
  I accidentally stumbled across this. If in line 22 on_ac_power returns
  a non zero exit code the next line is never reached. Instead, the
  shell terminates immediately with that non zero exit code because of
  "set -e" in line 3. In this script it does not pose a problem because
  the shell is asked to exit anyway if check_power() returns non zero
  but it works differently than is apparently intended (concluding from
  the logic).

  I will attach a suggest patch and a demo illustrating that the patch
  works as the original script seems to intend to.

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

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

[Touch-packages] [Bug 1742378] Re: Slight glitch in /etc/cron.daily/apt-compat Ubuntu 16.04.3 in apt-1.2.24

[rklemme]

Produces this output:

$ sh check_power_test.sh 
+ echo begin
begin
+ check_power 0
+ exit 0
+ return 0
+ check_power 1
+ exit 1
+ [ 1 -ne 1 ]
+ return 1
+ echo ignore
ignore
+ check_power 255
+ exit 255
+ [ 255 -ne 1 ]
+ return 0
+ echo end
end


** Attachment added: "Demonstration of behavior of the patch"
   
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1742378/+attachment/5034118/+files/check_power_test.sh

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

Title:
  Slight glitch in /etc/cron.daily/apt-compat Ubuntu 16.04.3 in
  apt-1.2.24

Status in apt package in Ubuntu:
  New

Bug description:
  I accidentally stumbled across this. If in line 22 on_ac_power returns
  a non zero exit code the next line is never reached. Instead, the
  shell terminates immediately with that non zero exit code because of
  "set -e" in line 3. In this script it does not pose a problem because
  the shell is asked to exit anyway if check_power() returns non zero
  but it works differently than is apparently intended (concluding from
  the logic).

  I will attach a suggest patch and a demo illustrating that the patch
  works as the original script seems to intend to.

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

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

[Touch-packages] [Bug 1742378] Re: Slight glitch in /etc/cron.daily/apt-compat Ubuntu 16.04.3 in apt-1.2.24

[rklemme]

** Patch added: "Suggested patch to fix"
   
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1742378/+attachment/5034117/+files/apt-compat-3.patch

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

Title:
  Slight glitch in /etc/cron.daily/apt-compat Ubuntu 16.04.3 in
  apt-1.2.24

Status in apt package in Ubuntu:
  New

Bug description:
  I accidentally stumbled across this. If in line 22 on_ac_power returns
  a non zero exit code the next line is never reached. Instead, the
  shell terminates immediately with that non zero exit code because of
  "set -e" in line 3. In this script it does not pose a problem because
  the shell is asked to exit anyway if check_power() returns non zero
  but it works differently than is apparently intended (concluding from
  the logic).

  I will attach a suggest patch and a demo illustrating that the patch
  works as the original script seems to intend to.

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

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

[Touch-packages] [Bug 1742378] [NEW] Slight glitch in /etc/cron.daily/apt-compat Ubuntu 16.04.3 in apt-1.2.24

[rklemme]

Public bug reported:

I accidentally stumbled across this. If in line 22 on_ac_power returns a
non zero exit code the next line is never reached. Instead, the shell
terminates immediately with that non zero exit code because of "set -e"
in line 3. In this script it does not pose a problem because the shell
is asked to exit anyway if check_power() returns non zero but it works
differently than is apparently intended (concluding from the logic).

I will attach a suggest patch and a demo illustrating that the patch
works as the original script seems to intend to.

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

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

Title:
  Slight glitch in /etc/cron.daily/apt-compat Ubuntu 16.04.3 in
  apt-1.2.24

Status in apt package in Ubuntu:
  New

Bug description:
  I accidentally stumbled across this. If in line 22 on_ac_power returns
  a non zero exit code the next line is never reached. Instead, the
  shell terminates immediately with that non zero exit code because of
  "set -e" in line 3. In this script it does not pose a problem because
  the shell is asked to exit anyway if check_power() returns non zero
  but it works differently than is apparently intended (concluding from
  the logic).

  I will attach a suggest patch and a demo illustrating that the patch
  works as the original script seems to intend to.

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

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

[Touch-packages] [Bug 1620636] Re: Fails to pair with Bose QC35 headphones

[Gaston M. Tonietti]

Hey,

I'm also having troubles trying to use my QC35 II, after dunno how many
different attempts to pair it that I'm not even able to describe, I
finally was able to pair it, but I was not so lucky to actually connect
it. Here I attach the chunk of btmon output I get on every attempt to
connect

** Attachment added: "bose-qc35-connect.snoop"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1620636/+attachment/5034102/+files/bose-qc35-connect.snoop

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

Title:
  Fails to pair with Bose QC35 headphones

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  In Progress

Bug description:
  I am unable to pair the Bose QC35 BT headphones with Ubuntu, either
  Ubuntu desktop running 16.04 LTS with bluez 5.37 (also tried bluez
  5.41 from installed from yakkety archive), nor using Ubuntu Touch rc-
  proposed build for Turbo #174. I'm trying to pair through the normal
  bluetooth control panel brought up through the bluetooth indicator.

  I've attached some logs that show it failing to pair. If I can provide
  anymore useful information about the headphones, please let me know.

  Syslog with bluetoothd debugging enabled:
  http://pastebin.ubuntu.com/23141394/

  btmon output:
  http://pastebin.ubuntu.com/23141446/

  bluetoothctl output:
  http://pastebin.ubuntu.com/23141510/

  With Linux kernel 4.8.0 and bluez 4.52:
  ---

  bluetoothctl: http://pastebin.ubuntu.com/23256457/
  btmon: http://pastebin.ubuntu.com/23256471/

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620636/+subscriptions

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

[Touch-packages] [Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system

[Ritesh Raj Sarraf]

Thanks for confirming @reckenrode. I'd appreciate if more users
confirmed the same.

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

Title:
  System fails to start (boot) on battery due to read-only root file-
  system

Status in laptop-mode-tools package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd package in Debian:
  Fix Released

Bug description:
  This report is to capture the extended diagnostic efforts done on IRC
  #ubuntu for user maszlo, who has a Lenovo T450 with SSD that was
  upgraded from 17.04 to 17.10 and since fails to complete start-up of
  services when powered on battery.

  We'd previously applied the "acpi=os=! 'acpi_osi=Windows 2015'"
  workaround in case this was an ACPI DSDT issue.

  This appears to be due to a read-only root file-system. What is not
  clear is how the rootfs goes read-only.

  The file-system (sda6, ext4) is fsck-ed successfully in the initrd
  according to the /run/initramfs/fsck.log.

  From the start-up logs (with "systemd.log_level=debug") we see the
  ext4 driver report a remount operation not once but five times.

  $ grep 'EXT4-fs.*sda6' systemd-debug.log
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): mounted filesystem with ordered 
data mode. Opts: (null)
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro
  Oct 23 18:10:46 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:47 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:49 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600

  Those last five appear to be carrying options generated by laptop-
  mode-tools.

  User has disabled laptop-mode.service and laptop-mode.timer, and lmt-
  poll.service, but the issue remains.

  We see several reports of "read-only file-system":

  $ grep 'Read-only' systemd-debug.log
  Oct 23 18:10:46 T450s grub-common[1792]: grub-editenv: error: cannot open 
`/boot/grub/grubenv': Read-only file system.
  Oct 23 18:10:46 T450s systemd[1]: colord.service: Failed to run 'start' task: 
Read-only file system
  Oct 23 18:10:46 T450s gpu-manager[1797]: Warning: writing to 
/var/log/gpu-manager.log failed (Read-only file system)
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s gdm3[1932]: Failed to create LogDir /var/log/gdm3: 
Read-only file system
  ...
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to change ownership of 
"/var/log/cups" - Read-only file system
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to open log file 
"/var/log/cups/access_log" - Read-only file system
  Oct 23 18:12:52 T450s login[9248]: pam_lastlog(login:session): unable to open 
/var/log/lastlog: Read-only file system

  We also see several problems with systemd's connection to Dbus:

  $ grep 'Transport endpoint' systemd-debug.log
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: systemd-logind.service: Failed to send unit 
change signal for systemd-logind.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 156: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: lmt-poll.service: Failed to send unit 
change signal for lmt-poll.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 182: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 95: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: polkit.service: Failed to send unit change 
signal for polkit.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: cups-browsed.service: Failed to send unit 
change signal for cups-browsed.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 161: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: gdomap.service: Failed to send unit change 
signal for gdomap.service: Transport endpoint is not connected

  When the user purged laptop-mode-tools the system starts successfully
  on battery.

  The user 

[Touch-packages] [Bug 1742365] [NEW] built-in display problem

[Susheel Rajagolkar]

Public bug reported:

display not minimize, its shows built-in display

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic x86_64
.tmp.unity.support.test.1:
 
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed Jan 10 10:52:50 2018
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.7, 3.16.0-30-generic, x86_64: installed
 virtualbox, 4.3.36, 3.16.0-30-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GF119 [GeForce GT 610] [10de:104a] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ZOTAC International (MCO) Ltd. Device [19da:6222]
InstallationDate: Installed on 2016-03-01 (679 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
MachineType: Dell Inc. Vostro 3900
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic 
root=UUID=1d25c27f-72f7-40dd-a53e-0b28eecc57c8 ro quiet splash vt.handoff=7
Renderer: Software
SourcePackage: xorg
UdevLog:
 
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/08/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: 0T1D10
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd05/08/2015:svnDellInc.:pnVostro3900:pvr:rvnDellInc.:rn0T1D10:rvrA01:cvnDellInc.:ct3:cvr:
dmi.product.name: Vostro 3900
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Wed Jan 10 10:15:15 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputPixArt USB Optical Mouse MOUSE, id 8
 inputDell Dell USB Entry Keyboard KEYBOARD, id 9
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

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


** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu

** Attachment added: "Screenshot from 2018-01-10 10:56:42.png"
   
https://bugs.launchpad.net/bugs/1742365/+attachment/5034071/+files/Screenshot%20from%202018-01-10%2010%3A56%3A42.png

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

Title:
  built-in display problem

Status in xorg package in Ubuntu:
  New

Bug description:
  display not minimize, its shows built-in display

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Jan 10 10:52:50 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.16.0-30-generic, x86_64: installed
   virtualbox, 4.3.36, 3.16.0-30-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GF119 [GeForce GT 610] [10de:104a] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. Device [19da:6222]
  InstallationDate: Installed on 2016-03-01 (679 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: Dell Inc. Vostro 3900
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic 
root=UUID=1d25c27f-72f7-40dd-a53e-0b28eecc57c8 ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UdevLog:
   
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0T1D10
  dmi.board.vendor: Dell Inc.

[Touch-packages] [Bug 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04

[Gord Kunz]

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

ppa:paulo-miguel-dias/pkppa worked for me. No problems since.

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

Title:
  Unity / Compiz in a crash loop after login, after mesa updates of
  2018-01-04

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Xenial:
  Confirmed
Status in mesa source package in Artful:
  Confirmed

Bug description:
  GUI is constantly crashing, can't start desktop

  Jan  5 11:21:29 1810 kernel: [  806.368754] compiz[10824]: segfault at 0 ip 
7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000]
  Jan  5 11:21:40 1810 kernel: [  817.279740] compiz[1]: segfault at 0 ip 
7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000]
  Jan  5 11:22:30 1810 kernel: [  867.445137] compiz[11271]: segfault at 0 ip 
7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000]
  Jan  5 11:22:46 1810 kernel: [  883.319195] compiz[11458]: segfault at 0 ip 
7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000]
  Jan  5 11:23:01 1810 kernel: [  898.587610] compiz[11516]: segfault at 0 ip 
7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000]

  In /var/crash:
  _usr_bin_compiz.999.crash

  Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not 
really usable.
  - dash not working
  - no window switching
  - sometimes all windows disappear for a few seconds

  So effectively my laptop is not usable after latest updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160906-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  .tmp.unity_support_test.0:

  .tmp.unity_support_test.1:

  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Jan  5 11:16:53 2018
  DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:029b]
     Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:029b]
  InstallationDate: Installed on 2014-04-18 (1357 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Acer Aspire 1810TZ
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic 
root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago)
  dmi.bios.date: 08/31/2010
  dmi.bios.vendor: INSYDE
  dmi.bios.version: v1.3314
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JM11-MS
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: Aspire 1810TZ
  dmi.product.version: v1.3314
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Jan  5 11:14:24 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1595695] Re: Bluetooth indicator disappears every time bluetooth is being turned off

[Po-Hsu Lin]

Tested with Bionic Daily build image, gnome-shell 3.26.2
this issue still exist.

** Tags added: artful bionic

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

Title:
  Bluetooth indicator disappears every time bluetooth is being turned
  off

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in indicator-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 16.04, every time I turn off bluetooth, the indicator icon 
disappears from the top panel.
  Each time I have to re-enable it by system setting or via dash.

  I expect it to behave in a same way as network indicator instead of
  disappearing.

  Here is the link with some info which could be helpful 
  https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1126108

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

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

[Touch-packages] [Bug 1712921] Re: enabling networkd appears to eat up entropy

[Launchpad Bug Tracker]

This bug was fixed in the package nplan - 0.32~16.04.3

---
nplan (0.32~16.04.3) xenial; urgency=medium

  * tests/integration.py: Really fix skipping test_routes_v6 for the NM
backend.

nplan (0.32~16.04.2) xenial; urgency=medium

  * tests/integration.py: Fix test_routes_v6 that I clobbered when I re-applied
the skip rules for 16.04 after merging in 0.32.

nplan (0.32~16.04.1) xenial; urgency=medium

  * Backport netplan 0.32 to 16.04. (LP: #1713142)
  * debian/control: Depend on systemd (>= 229-4ubuntu20) for the PrimarySlave
feature backported in that revision.
  * tests/integration.py: Skip tests that are still not yet supported in xenial

nplan (0.32) bionic; urgency=medium

  * src/nm.c: better handle the UUID generation; the order of iterating
through interaces may affect things here. Also make sure the tests catch
a null UUID.

nplan (0.31) bionic; urgency=medium

  [ Mathieu Trudel-Lapierre ]
  * src/nm.c: generate a UUID for a connection only as needed; when we're
dealing with NM VLANs. (LP: #1712921)
  * debian/tests/autostart: Make the autostart test more verbose and avoid
failing right from the start when systemd-networkd is disabled.
(LP: #1699371)
  * tests/integration.py: bump the NetworkManager timeout for settling to
120 seconds, autopkgtest infrastructure tends to be a little slow for the
network device configuration to be applied and noticed by NM.
(LP: #1699371)

  [ Dimitri John Ledkov ]
  * Reload udevd to invalidate configuration cache of .rules/.link files
as generate step may have changed them. LP: #1669564

  [ Dan Streetman ]
  * Add another interface driver exception to netplan replug to prevent unbind
of the Xen VIF interfaces. (LP: #1729573)

nplan (0.30) artful; urgency=medium

  * Add an "optional" syntax node for now to all devices. This is unimplemented
for now, but intended to allow users to mark some devices as optional: to
make sure they do not delay boot when configured. (LP: #1664844)

nplan (0.29) artful; urgency=medium

  * Fix autopkgtests in a world where /run/NetworkManager/conf.d already
exists. nplan is enabled by default, so it might well have the directory
already created on the filesystem.

nplan (0.28) artful; urgency=medium

  * Revert 56cd3eec which disabled IPv6 Router Advertisements by default. It
broke default network config in LXD and was contrary to the defaults used
by the kernel. Reopens LP: 1655440. (LP: #1717404)
  * Add "accept-ra:" key for all device types; this will default to OFF but
allow users to disable processing Router Advertisements when required by
their network setup. (LP: #1655440)

nplan (0.27) artful; urgency=medium

  [ Mathieu Trudel-Lapierre ]
  * Fix crash in systemd generator if called by an user on the command-line
  * coverage: fix exclusions to properly not cover our "never reached defaults"

  [ Dimitri John Ledkov ]
  * tests/integration.py: In teardown, stop systemd-networkd.socket.
  * src/networkd.c: Set UseMTU=true by default, whenever DHCP is in use.
(LP: #1717471)
  * tests/integration.py: fix resolved detection.

nplan (0.26) artful; urgency=medium

  * Bonding:
- Add support for specifying a primary slave. (LP: #1709135)
  * Rebind:
- Fix brcmfmac harder. Treat any 'brcmfmac' driver as not supporting
  rebind. (LP: #1712224)
  * Autopkgtests:
- Add allow-stderr. Systemd now bleats about a the networkd socket still
  being around and enabled when we restart the service; but we don't need
  to care since we're /restarting/ the service to load the new config.
- Fix the autostart package to be more sensible: we don't really care if
  networkd autostarts or not, but we need to make sure that our generator
  will run at boot, so instead check the state, but only assert it once
  we've added a config file and before checking the state of our dummy
  device.
- Do a bit more to make sure "mix" tests which stack virtual devices are
  as reliable as possible; by setting saner defaults.

nplan (0.25) artful; urgency=medium

  * tests/generate.py: add a test to validate that correct blacklist entries
are added when creating virtual devices.
  * tests/integration.py: clean up after br0 in networkd's test_bridge_mac; as
the remaining interface and udev configuration can confuse NetworkManager
now that it seems to manage random devices it did not create again.
(LP: #1699371)
  * src/nm.c: set the MTU even though we also specify it in systemd-networkd
for consumption by udev. NetworkManager will try to set it and might
otherwise default to the wrong value.
  * src/networkd.c: Set IPv6AcceptRA=no anytime we don't do DHCPv6 (or by the
same config, SLAAC), and don't have static addresses set. This should fix
the cases where unconfigured devices still get an IPv6 address.
(LP: #1655440)
  * src/nm.c: Explicitly set IPv6 method=ignore when IPv6 is 

[Touch-packages] [Bug 1709135] Re: add bond primary parameter

[Launchpad Bug Tracker]

This bug was fixed in the package nplan - 0.32~17.04.1

---
nplan (0.32~17.04.1) zesty; urgency=medium

  * Backport 0.32 to 17.04. (LP: #1713142)

nplan (0.32) bionic; urgency=medium

  * src/nm.c: better handle the UUID generation; the order of iterating
through interaces may affect things here. Also make sure the tests catch
a null UUID.

nplan (0.31) bionic; urgency=medium

  [ Mathieu Trudel-Lapierre ]
  * src/nm.c: generate a UUID for a connection only as needed; when we're
dealing with NM VLANs. (LP: #1712921)
  * debian/tests/autostart: Make the autostart test more verbose and avoid
failing right from the start when systemd-networkd is disabled.
(LP: #1699371)
  * tests/integration.py: bump the NetworkManager timeout for settling to
120 seconds, autopkgtest infrastructure tends to be a little slow for the
network device configuration to be applied and noticed by NM.
(LP: #1699371)

  [ Dimitri John Ledkov ]
  * Reload udevd to invalidate configuration cache of .rules/.link files
as generate step may have changed them. LP: #1669564

  [ Dan Streetman ]
  * Add another interface driver exception to netplan replug to prevent unbind
of the Xen VIF interfaces. (LP: #1729573)

nplan (0.30) artful; urgency=medium

  * Add an "optional" syntax node for now to all devices. This is unimplemented
for now, but intended to allow users to mark some devices as optional: to
make sure they do not delay boot when configured. (LP: #1664844)

nplan (0.29) artful; urgency=medium

  * Fix autopkgtests in a world where /run/NetworkManager/conf.d already
exists. nplan is enabled by default, so it might well have the directory
already created on the filesystem.

nplan (0.28) artful; urgency=medium

  * Revert 56cd3eec which disabled IPv6 Router Advertisements by default. It
broke default network config in LXD and was contrary to the defaults used
by the kernel. Reopens LP: 1655440. (LP: #1717404)
  * Add "accept-ra:" key for all device types; this will default to OFF but
allow users to disable processing Router Advertisements when required by
their network setup. (LP: #1655440)

nplan (0.27) artful; urgency=medium

  [ Mathieu Trudel-Lapierre ]
  * Fix crash in systemd generator if called by an user on the command-line
  * coverage: fix exclusions to properly not cover our "never reached defaults"

  [ Dimitri John Ledkov ]
  * tests/integration.py: In teardown, stop systemd-networkd.socket.
  * src/networkd.c: Set UseMTU=true by default, whenever DHCP is in use.
(LP: #1717471)
  * tests/integration.py: fix resolved detection.

nplan (0.26) artful; urgency=medium

  * Bonding:
- Add support for specifying a primary slave. (LP: #1709135)
  * Rebind:
- Fix brcmfmac harder. Treat any 'brcmfmac' driver as not supporting
  rebind. (LP: #1712224)
  * Autopkgtests:
- Add allow-stderr. Systemd now bleats about a the networkd socket still
  being around and enabled when we restart the service; but we don't need
  to care since we're /restarting/ the service to load the new config.
- Fix the autostart package to be more sensible: we don't really care if
  networkd autostarts or not, but we need to make sure that our generator
  will run at boot, so instead check the state, but only assert it once
  we've added a config file and before checking the state of our dummy
  device.
- Do a bit more to make sure "mix" tests which stack virtual devices are
  as reliable as possible; by setting saner defaults.

nplan (0.25) artful; urgency=medium

  * tests/generate.py: add a test to validate that correct blacklist entries
are added when creating virtual devices.
  * tests/integration.py: clean up after br0 in networkd's test_bridge_mac; as
the remaining interface and udev configuration can confuse NetworkManager
now that it seems to manage random devices it did not create again.
(LP: #1699371)
  * src/nm.c: set the MTU even though we also specify it in systemd-networkd
for consumption by udev. NetworkManager will try to set it and might
otherwise default to the wrong value.
  * src/networkd.c: Set IPv6AcceptRA=no anytime we don't do DHCPv6 (or by the
same config, SLAAC), and don't have static addresses set. This should fix
the cases where unconfigured devices still get an IPv6 address.
(LP: #1655440)
  * src/nm.c: Explicitly set IPv6 method=ignore when IPv6 is otherwise not
configured; this follows the same logic as setting IPv6AcceptRA=no in
networkd, with the exception that NM does not currently disable RAs. When
it does, an unconfigured device for IPv6 will truly be left with no config.

nplan (0.24) artful; urgency=medium

  * debian/control: set Priority to important to make sure we can get into
minimal.

 -- Mathieu Trudel-Lapierre   Thu, 16 Nov 2017
10:43:28 -0500

-- 
You received this bug notification because you are a 

[Touch-packages] [Bug 1712921] Re: enabling networkd appears to eat up entropy

[Launchpad Bug Tracker]

This bug was fixed in the package nplan - 0.32~17.04.1

---
nplan (0.32~17.04.1) zesty; urgency=medium

  * Backport 0.32 to 17.04. (LP: #1713142)

nplan (0.32) bionic; urgency=medium

  * src/nm.c: better handle the UUID generation; the order of iterating
through interaces may affect things here. Also make sure the tests catch
a null UUID.

nplan (0.31) bionic; urgency=medium

  [ Mathieu Trudel-Lapierre ]
  * src/nm.c: generate a UUID for a connection only as needed; when we're
dealing with NM VLANs. (LP: #1712921)
  * debian/tests/autostart: Make the autostart test more verbose and avoid
failing right from the start when systemd-networkd is disabled.
(LP: #1699371)
  * tests/integration.py: bump the NetworkManager timeout for settling to
120 seconds, autopkgtest infrastructure tends to be a little slow for the
network device configuration to be applied and noticed by NM.
(LP: #1699371)

  [ Dimitri John Ledkov ]
  * Reload udevd to invalidate configuration cache of .rules/.link files
as generate step may have changed them. LP: #1669564

  [ Dan Streetman ]
  * Add another interface driver exception to netplan replug to prevent unbind
of the Xen VIF interfaces. (LP: #1729573)

nplan (0.30) artful; urgency=medium

  * Add an "optional" syntax node for now to all devices. This is unimplemented
for now, but intended to allow users to mark some devices as optional: to
make sure they do not delay boot when configured. (LP: #1664844)

nplan (0.29) artful; urgency=medium

  * Fix autopkgtests in a world where /run/NetworkManager/conf.d already
exists. nplan is enabled by default, so it might well have the directory
already created on the filesystem.

nplan (0.28) artful; urgency=medium

  * Revert 56cd3eec which disabled IPv6 Router Advertisements by default. It
broke default network config in LXD and was contrary to the defaults used
by the kernel. Reopens LP: 1655440. (LP: #1717404)
  * Add "accept-ra:" key for all device types; this will default to OFF but
allow users to disable processing Router Advertisements when required by
their network setup. (LP: #1655440)

nplan (0.27) artful; urgency=medium

  [ Mathieu Trudel-Lapierre ]
  * Fix crash in systemd generator if called by an user on the command-line
  * coverage: fix exclusions to properly not cover our "never reached defaults"

  [ Dimitri John Ledkov ]
  * tests/integration.py: In teardown, stop systemd-networkd.socket.
  * src/networkd.c: Set UseMTU=true by default, whenever DHCP is in use.
(LP: #1717471)
  * tests/integration.py: fix resolved detection.

nplan (0.26) artful; urgency=medium

  * Bonding:
- Add support for specifying a primary slave. (LP: #1709135)
  * Rebind:
- Fix brcmfmac harder. Treat any 'brcmfmac' driver as not supporting
  rebind. (LP: #1712224)
  * Autopkgtests:
- Add allow-stderr. Systemd now bleats about a the networkd socket still
  being around and enabled when we restart the service; but we don't need
  to care since we're /restarting/ the service to load the new config.
- Fix the autostart package to be more sensible: we don't really care if
  networkd autostarts or not, but we need to make sure that our generator
  will run at boot, so instead check the state, but only assert it once
  we've added a config file and before checking the state of our dummy
  device.
- Do a bit more to make sure "mix" tests which stack virtual devices are
  as reliable as possible; by setting saner defaults.

nplan (0.25) artful; urgency=medium

  * tests/generate.py: add a test to validate that correct blacklist entries
are added when creating virtual devices.
  * tests/integration.py: clean up after br0 in networkd's test_bridge_mac; as
the remaining interface and udev configuration can confuse NetworkManager
now that it seems to manage random devices it did not create again.
(LP: #1699371)
  * src/nm.c: set the MTU even though we also specify it in systemd-networkd
for consumption by udev. NetworkManager will try to set it and might
otherwise default to the wrong value.
  * src/networkd.c: Set IPv6AcceptRA=no anytime we don't do DHCPv6 (or by the
same config, SLAAC), and don't have static addresses set. This should fix
the cases where unconfigured devices still get an IPv6 address.
(LP: #1655440)
  * src/nm.c: Explicitly set IPv6 method=ignore when IPv6 is otherwise not
configured; this follows the same logic as setting IPv6AcceptRA=no in
networkd, with the exception that NM does not currently disable RAs. When
it does, an unconfigured device for IPv6 will truly be left with no config.

nplan (0.24) artful; urgency=medium

  * debian/control: set Priority to important to make sure we can get into
minimal.

 -- Mathieu Trudel-Lapierre   Thu, 16 Nov 2017
10:43:28 -0500

-- 
You received this bug notification because you are a 

[Touch-packages] [Bug 1717471] Update Released

[Chris Halse Rogers]

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

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

Title:
  networkd does not accept / set advertised mtu

Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in nplan source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  New
Status in nplan source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  Hosts may require a specific MTU to be set as passed by DHCP options. We 
should honor these settings to ensure proper communication of the host with the 
rest of the network.

  [Test case]
  1) Run netplan on a system that should receive MTU settings from DHCP.
  2) Validate that the MTU configuration provided by DHCP is applied to the 
right interface.

  [Regression Potential]
  If DHCP settings specify an invalid MTU setting which is currently being 
ignored and letting the systems communicate correctly with the network, then 
these systems would regress.

  ---

   Right, so as far as I can tell the neutron-api on lcy01 is
  configured to advertise an instance interface MTU of 1400, though
  that's lower than it has to be, and the new DHCP setup with networkd
  just doesn't respect that DHCP option.

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

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

[Touch-packages] [Bug 1709135] Re: add bond primary parameter

[Launchpad Bug Tracker]

This bug was fixed in the package nplan - 0.32~16.04.3

---
nplan (0.32~16.04.3) xenial; urgency=medium

  * tests/integration.py: Really fix skipping test_routes_v6 for the NM
backend.

nplan (0.32~16.04.2) xenial; urgency=medium

  * tests/integration.py: Fix test_routes_v6 that I clobbered when I re-applied
the skip rules for 16.04 after merging in 0.32.

nplan (0.32~16.04.1) xenial; urgency=medium

  * Backport netplan 0.32 to 16.04. (LP: #1713142)
  * debian/control: Depend on systemd (>= 229-4ubuntu20) for the PrimarySlave
feature backported in that revision.
  * tests/integration.py: Skip tests that are still not yet supported in xenial

nplan (0.32) bionic; urgency=medium

  * src/nm.c: better handle the UUID generation; the order of iterating
through interaces may affect things here. Also make sure the tests catch
a null UUID.

nplan (0.31) bionic; urgency=medium

  [ Mathieu Trudel-Lapierre ]
  * src/nm.c: generate a UUID for a connection only as needed; when we're
dealing with NM VLANs. (LP: #1712921)
  * debian/tests/autostart: Make the autostart test more verbose and avoid
failing right from the start when systemd-networkd is disabled.
(LP: #1699371)
  * tests/integration.py: bump the NetworkManager timeout for settling to
120 seconds, autopkgtest infrastructure tends to be a little slow for the
network device configuration to be applied and noticed by NM.
(LP: #1699371)

  [ Dimitri John Ledkov ]
  * Reload udevd to invalidate configuration cache of .rules/.link files
as generate step may have changed them. LP: #1669564

  [ Dan Streetman ]
  * Add another interface driver exception to netplan replug to prevent unbind
of the Xen VIF interfaces. (LP: #1729573)

nplan (0.30) artful; urgency=medium

  * Add an "optional" syntax node for now to all devices. This is unimplemented
for now, but intended to allow users to mark some devices as optional: to
make sure they do not delay boot when configured. (LP: #1664844)

nplan (0.29) artful; urgency=medium

  * Fix autopkgtests in a world where /run/NetworkManager/conf.d already
exists. nplan is enabled by default, so it might well have the directory
already created on the filesystem.

nplan (0.28) artful; urgency=medium

  * Revert 56cd3eec which disabled IPv6 Router Advertisements by default. It
broke default network config in LXD and was contrary to the defaults used
by the kernel. Reopens LP: 1655440. (LP: #1717404)
  * Add "accept-ra:" key for all device types; this will default to OFF but
allow users to disable processing Router Advertisements when required by
their network setup. (LP: #1655440)

nplan (0.27) artful; urgency=medium

  [ Mathieu Trudel-Lapierre ]
  * Fix crash in systemd generator if called by an user on the command-line
  * coverage: fix exclusions to properly not cover our "never reached defaults"

  [ Dimitri John Ledkov ]
  * tests/integration.py: In teardown, stop systemd-networkd.socket.
  * src/networkd.c: Set UseMTU=true by default, whenever DHCP is in use.
(LP: #1717471)
  * tests/integration.py: fix resolved detection.

nplan (0.26) artful; urgency=medium

  * Bonding:
- Add support for specifying a primary slave. (LP: #1709135)
  * Rebind:
- Fix brcmfmac harder. Treat any 'brcmfmac' driver as not supporting
  rebind. (LP: #1712224)
  * Autopkgtests:
- Add allow-stderr. Systemd now bleats about a the networkd socket still
  being around and enabled when we restart the service; but we don't need
  to care since we're /restarting/ the service to load the new config.
- Fix the autostart package to be more sensible: we don't really care if
  networkd autostarts or not, but we need to make sure that our generator
  will run at boot, so instead check the state, but only assert it once
  we've added a config file and before checking the state of our dummy
  device.
- Do a bit more to make sure "mix" tests which stack virtual devices are
  as reliable as possible; by setting saner defaults.

nplan (0.25) artful; urgency=medium

  * tests/generate.py: add a test to validate that correct blacklist entries
are added when creating virtual devices.
  * tests/integration.py: clean up after br0 in networkd's test_bridge_mac; as
the remaining interface and udev configuration can confuse NetworkManager
now that it seems to manage random devices it did not create again.
(LP: #1699371)
  * src/nm.c: set the MTU even though we also specify it in systemd-networkd
for consumption by udev. NetworkManager will try to set it and might
otherwise default to the wrong value.
  * src/networkd.c: Set IPv6AcceptRA=no anytime we don't do DHCPv6 (or by the
same config, SLAAC), and don't have static addresses set. This should fix
the cases where unconfigured devices still get an IPv6 address.
(LP: #1655440)
  * src/nm.c: Explicitly set IPv6 method=ignore when IPv6 is 

[Touch-packages] [Bug 1717471] Re: networkd does not accept / set advertised mtu

[Launchpad Bug Tracker]

This bug was fixed in the package nplan - 0.32~17.04.1

---
nplan (0.32~17.04.1) zesty; urgency=medium

  * Backport 0.32 to 17.04. (LP: #1713142)

nplan (0.32) bionic; urgency=medium

  * src/nm.c: better handle the UUID generation; the order of iterating
through interaces may affect things here. Also make sure the tests catch
a null UUID.

nplan (0.31) bionic; urgency=medium

  [ Mathieu Trudel-Lapierre ]
  * src/nm.c: generate a UUID for a connection only as needed; when we're
dealing with NM VLANs. (LP: #1712921)
  * debian/tests/autostart: Make the autostart test more verbose and avoid
failing right from the start when systemd-networkd is disabled.
(LP: #1699371)
  * tests/integration.py: bump the NetworkManager timeout for settling to
120 seconds, autopkgtest infrastructure tends to be a little slow for the
network device configuration to be applied and noticed by NM.
(LP: #1699371)

  [ Dimitri John Ledkov ]
  * Reload udevd to invalidate configuration cache of .rules/.link files
as generate step may have changed them. LP: #1669564

  [ Dan Streetman ]
  * Add another interface driver exception to netplan replug to prevent unbind
of the Xen VIF interfaces. (LP: #1729573)

nplan (0.30) artful; urgency=medium

  * Add an "optional" syntax node for now to all devices. This is unimplemented
for now, but intended to allow users to mark some devices as optional: to
make sure they do not delay boot when configured. (LP: #1664844)

nplan (0.29) artful; urgency=medium

  * Fix autopkgtests in a world where /run/NetworkManager/conf.d already
exists. nplan is enabled by default, so it might well have the directory
already created on the filesystem.

nplan (0.28) artful; urgency=medium

  * Revert 56cd3eec which disabled IPv6 Router Advertisements by default. It
broke default network config in LXD and was contrary to the defaults used
by the kernel. Reopens LP: 1655440. (LP: #1717404)
  * Add "accept-ra:" key for all device types; this will default to OFF but
allow users to disable processing Router Advertisements when required by
their network setup. (LP: #1655440)

nplan (0.27) artful; urgency=medium

  [ Mathieu Trudel-Lapierre ]
  * Fix crash in systemd generator if called by an user on the command-line
  * coverage: fix exclusions to properly not cover our "never reached defaults"

  [ Dimitri John Ledkov ]
  * tests/integration.py: In teardown, stop systemd-networkd.socket.
  * src/networkd.c: Set UseMTU=true by default, whenever DHCP is in use.
(LP: #1717471)
  * tests/integration.py: fix resolved detection.

nplan (0.26) artful; urgency=medium

  * Bonding:
- Add support for specifying a primary slave. (LP: #1709135)
  * Rebind:
- Fix brcmfmac harder. Treat any 'brcmfmac' driver as not supporting
  rebind. (LP: #1712224)
  * Autopkgtests:
- Add allow-stderr. Systemd now bleats about a the networkd socket still
  being around and enabled when we restart the service; but we don't need
  to care since we're /restarting/ the service to load the new config.
- Fix the autostart package to be more sensible: we don't really care if
  networkd autostarts or not, but we need to make sure that our generator
  will run at boot, so instead check the state, but only assert it once
  we've added a config file and before checking the state of our dummy
  device.
- Do a bit more to make sure "mix" tests which stack virtual devices are
  as reliable as possible; by setting saner defaults.

nplan (0.25) artful; urgency=medium

  * tests/generate.py: add a test to validate that correct blacklist entries
are added when creating virtual devices.
  * tests/integration.py: clean up after br0 in networkd's test_bridge_mac; as
the remaining interface and udev configuration can confuse NetworkManager
now that it seems to manage random devices it did not create again.
(LP: #1699371)
  * src/nm.c: set the MTU even though we also specify it in systemd-networkd
for consumption by udev. NetworkManager will try to set it and might
otherwise default to the wrong value.
  * src/networkd.c: Set IPv6AcceptRA=no anytime we don't do DHCPv6 (or by the
same config, SLAAC), and don't have static addresses set. This should fix
the cases where unconfigured devices still get an IPv6 address.
(LP: #1655440)
  * src/nm.c: Explicitly set IPv6 method=ignore when IPv6 is otherwise not
configured; this follows the same logic as setting IPv6AcceptRA=no in
networkd, with the exception that NM does not currently disable RAs. When
it does, an unconfigured device for IPv6 will truly be left with no config.

nplan (0.24) artful; urgency=medium

  * debian/control: set Priority to important to make sure we can get into
minimal.

 -- Mathieu Trudel-Lapierre   Thu, 16 Nov 2017
10:43:28 -0500

** Changed in: nplan (Ubuntu Zesty)
   Status: Fix 

[Touch-packages] [Bug 1717471] Re: networkd does not accept / set advertised mtu

[Launchpad Bug Tracker]

This bug was fixed in the package nplan - 0.32~16.04.3

---
nplan (0.32~16.04.3) xenial; urgency=medium

  * tests/integration.py: Really fix skipping test_routes_v6 for the NM
backend.

nplan (0.32~16.04.2) xenial; urgency=medium

  * tests/integration.py: Fix test_routes_v6 that I clobbered when I re-applied
the skip rules for 16.04 after merging in 0.32.

nplan (0.32~16.04.1) xenial; urgency=medium

  * Backport netplan 0.32 to 16.04. (LP: #1713142)
  * debian/control: Depend on systemd (>= 229-4ubuntu20) for the PrimarySlave
feature backported in that revision.
  * tests/integration.py: Skip tests that are still not yet supported in xenial

nplan (0.32) bionic; urgency=medium

  * src/nm.c: better handle the UUID generation; the order of iterating
through interaces may affect things here. Also make sure the tests catch
a null UUID.

nplan (0.31) bionic; urgency=medium

  [ Mathieu Trudel-Lapierre ]
  * src/nm.c: generate a UUID for a connection only as needed; when we're
dealing with NM VLANs. (LP: #1712921)
  * debian/tests/autostart: Make the autostart test more verbose and avoid
failing right from the start when systemd-networkd is disabled.
(LP: #1699371)
  * tests/integration.py: bump the NetworkManager timeout for settling to
120 seconds, autopkgtest infrastructure tends to be a little slow for the
network device configuration to be applied and noticed by NM.
(LP: #1699371)

  [ Dimitri John Ledkov ]
  * Reload udevd to invalidate configuration cache of .rules/.link files
as generate step may have changed them. LP: #1669564

  [ Dan Streetman ]
  * Add another interface driver exception to netplan replug to prevent unbind
of the Xen VIF interfaces. (LP: #1729573)

nplan (0.30) artful; urgency=medium

  * Add an "optional" syntax node for now to all devices. This is unimplemented
for now, but intended to allow users to mark some devices as optional: to
make sure they do not delay boot when configured. (LP: #1664844)

nplan (0.29) artful; urgency=medium

  * Fix autopkgtests in a world where /run/NetworkManager/conf.d already
exists. nplan is enabled by default, so it might well have the directory
already created on the filesystem.

nplan (0.28) artful; urgency=medium

  * Revert 56cd3eec which disabled IPv6 Router Advertisements by default. It
broke default network config in LXD and was contrary to the defaults used
by the kernel. Reopens LP: 1655440. (LP: #1717404)
  * Add "accept-ra:" key for all device types; this will default to OFF but
allow users to disable processing Router Advertisements when required by
their network setup. (LP: #1655440)

nplan (0.27) artful; urgency=medium

  [ Mathieu Trudel-Lapierre ]
  * Fix crash in systemd generator if called by an user on the command-line
  * coverage: fix exclusions to properly not cover our "never reached defaults"

  [ Dimitri John Ledkov ]
  * tests/integration.py: In teardown, stop systemd-networkd.socket.
  * src/networkd.c: Set UseMTU=true by default, whenever DHCP is in use.
(LP: #1717471)
  * tests/integration.py: fix resolved detection.

nplan (0.26) artful; urgency=medium

  * Bonding:
- Add support for specifying a primary slave. (LP: #1709135)
  * Rebind:
- Fix brcmfmac harder. Treat any 'brcmfmac' driver as not supporting
  rebind. (LP: #1712224)
  * Autopkgtests:
- Add allow-stderr. Systemd now bleats about a the networkd socket still
  being around and enabled when we restart the service; but we don't need
  to care since we're /restarting/ the service to load the new config.
- Fix the autostart package to be more sensible: we don't really care if
  networkd autostarts or not, but we need to make sure that our generator
  will run at boot, so instead check the state, but only assert it once
  we've added a config file and before checking the state of our dummy
  device.
- Do a bit more to make sure "mix" tests which stack virtual devices are
  as reliable as possible; by setting saner defaults.

nplan (0.25) artful; urgency=medium

  * tests/generate.py: add a test to validate that correct blacklist entries
are added when creating virtual devices.
  * tests/integration.py: clean up after br0 in networkd's test_bridge_mac; as
the remaining interface and udev configuration can confuse NetworkManager
now that it seems to manage random devices it did not create again.
(LP: #1699371)
  * src/nm.c: set the MTU even though we also specify it in systemd-networkd
for consumption by udev. NetworkManager will try to set it and might
otherwise default to the wrong value.
  * src/networkd.c: Set IPv6AcceptRA=no anytime we don't do DHCPv6 (or by the
same config, SLAAC), and don't have static addresses set. This should fix
the cases where unconfigured devices still get an IPv6 address.
(LP: #1655440)
  * src/nm.c: Explicitly set IPv6 method=ignore when IPv6 is 

[Touch-packages] [Bug 1742269] Re: Keyboard focus not visible on popover menu entries

[Launchpad Bug Tracker]

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

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Confirmed

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

Title:
  Keyboard focus not visible on popover menu entries

Status in Ubuntu theme:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Open a popover menu with text entries, such as:

  - Files (Nautilus): "hamburger" menu on the upper right

  - Tilix: "hamburger" menu, or right-click over the terminal area, or
  Profiles -> a triangle in the left-hand sidebar

  Use the keyboard (Tab, or Up and Down) to navigate in the entries.

  When an icon entry (wherever present) is focused, it has a thin orange
  border. But when simple text (or checkbox, radiobutton) entries are
  focused, there is no visual feedback at all, you can't see which item
  is selected and hence which item would be activated by Enter or Space.

  This makes popovers pretty unusable via the keyboard.

  Does not happen with Adwaita.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20171115-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Tue Jan  9 20:54:27 2018
  InstallationDate: Installed on 2016-11-09 (425 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to artful on 2017-09-21 (109 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1742269/+subscriptions

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

[Touch-packages] [Bug 1742269] Re: Keyboard focus not visible on popover menu entries

[Daniel van Vugt]

** Also affects: ubuntu-themes
   Importance: Undecided
   Status: New

** Changed in: ubuntu-themes
   Status: New => Confirmed

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

Title:
  Keyboard focus not visible on popover menu entries

Status in Ubuntu theme:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Open a popover menu with text entries, such as:

  - Files (Nautilus): "hamburger" menu on the upper right

  - Tilix: "hamburger" menu, or right-click over the terminal area, or
  Profiles -> a triangle in the left-hand sidebar

  Use the keyboard (Tab, or Up and Down) to navigate in the entries.

  When an icon entry (wherever present) is focused, it has a thin orange
  border. But when simple text (or checkbox, radiobutton) entries are
  focused, there is no visual feedback at all, you can't see which item
  is selected and hence which item would be activated by Enter or Space.

  This makes popovers pretty unusable via the keyboard.

  Does not happen with Adwaita.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20171115-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Tue Jan  9 20:54:27 2018
  InstallationDate: Installed on 2016-11-09 (425 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to artful on 2017-09-21 (109 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1742269/+subscriptions

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

[Touch-packages] [Bug 1731467] Re: Cannot pair BLE remote devices when using combo BT SoC

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.13.0-25.29

---
linux (4.13.0-25.29) artful; urgency=low

  * linux: 4.13.0-25.29 -proposed tracker (LP: #1741955)

  * CVE-2017-5754
- Revert "UBUNTU: [Config] updateconfigs to enable PTI"
- [Config] Enable PTI with UNWINDER_FRAME_POINTER

linux (4.13.0-24.28) artful; urgency=low

  * linux: 4.13.0-24.28 -proposed tracker (LP: #1741745)

  * CVE-2017-5754
- x86/cpu, x86/pti: Do not enable PTI on AMD processors

linux (4.13.0-23.27) artful; urgency=low

  * linux: 4.13.0-23.27 -proposed tracker (LP: #1741556)

  [ Kleber Sacilotto de Souza ]
  * CVE-2017-5754
- x86/mm: Add the 'nopcid' boot option to turn off PCID
- x86/mm: Enable CR4.PCIDE on supported systems
- x86/mm: Document how CR4.PCIDE restore works
- x86/entry/64: Refactor IRQ stacks and make them NMI-safe
- x86/entry/64: Initialize the top of the IRQ stack before switching stacks
- x86/entry/64: Add unwind hint annotations
- xen/x86: Remove SME feature in PV guests
- x86/xen/64: Rearrange the SYSCALL entries
- irq: Make the irqentry text section unconditional
- x86/xen/64: Fix the reported SS and CS in SYSCALL
- x86/paravirt/xen: Remove xen_patch()
- x86/traps: Simplify pagefault tracing logic
- x86/idt: Unify gate_struct handling for 32/64-bit kernels
- x86/asm: Replace access to desc_struct:a/b fields
- x86/xen: Get rid of paravirt op adjust_exception_frame
- x86/paravirt: Remove no longer used paravirt functions
- x86/entry: Fix idtentry unwind hint
- x86/mm/64: Initialize CR4.PCIDE early
- objtool: Add ORC unwind table generation
- objtool, x86: Add facility for asm code to provide unwind hints
- x86/unwind: Add the ORC unwinder
- x86/kconfig: Consolidate unwinders into multiple choice selection
- objtool: Upgrade libelf-devel warning to error for CONFIG_ORC_UNWINDER
- x86/ldt/64: Refresh DS and ES when modify_ldt changes an entry
- x86/mm: Give each mm TLB flush generation a unique ID
- x86/mm: Track the TLB's tlb_gen and update the flushing algorithm
- x86/mm: Rework lazy TLB mode and TLB freshness tracking
- x86/mm: Implement PCID based optimization: try to preserve old TLB entries
  using PCID
- x86/mm: Factor out CR3-building code
- x86/mm/64: Stop using CR3.PCID == 0 in ASID-aware code
- x86/mm: Flush more aggressively in lazy TLB mode
- Revert "x86/mm: Stop calling leave_mm() in idle code"
- kprobes/x86: Set up frame pointer in kprobe trampoline
- x86/tracing: Introduce a static key for exception tracing
- x86/boot: Add early cmdline parsing for options with arguments
- mm, x86/mm: Fix performance regression in get_user_pages_fast()
- x86/asm: Remove unnecessary \n\t in front of CC_SET() from asm templates
- objtool: Don't report end of section error after an empty unwind hint
- x86/head: Remove confusing comment
- x86/head: Remove unused 'bad_address' code
- x86/head: Fix head ELF function annotations
- x86/boot: Annotate verify_cpu() as a callable function
- x86/xen: Fix xen head ELF annotations
- x86/xen: Add unwind hint annotations
- x86/head: Add unwind hint annotations
- ACPI / APEI: adjust a local variable type in ghes_ioremap_pfn_irq()
- x86/unwinder: Make CONFIG_UNWINDER_ORC=y the default in the 64-bit 
defconfig
- x86/fpu/debug: Remove unused 'x86_fpu_state' and 
'x86_fpu_deactivate_state'
  tracepoints
- x86/unwind: Rename unwinder config options to 'CONFIG_UNWINDER_*'
- x86/unwind: Make CONFIG_UNWINDER_ORC=y the default in kconfig for 64-bit
- bitops: Add clear/set_bit32() to linux/bitops.h
- x86/cpuid: Add generic table for CPUID dependencies
- x86/fpu: Parse clearcpuid= as early XSAVE argument
- x86/fpu: Make XSAVE check the base CPUID features before enabling
- x86/fpu: Remove the explicit clearing of XSAVE dependent features
- x86/platform/UV: Convert timers to use timer_setup()
- objtool: Print top level commands on incorrect usage
- x86/cpuid: Prevent out of bound access in do_clear_cpu_cap()
- x86/entry: Use SYSCALL_DEFINE() macros for sys_modify_ldt()
- mm/sparsemem: Allocate mem_section at runtime for 
CONFIG_SPARSEMEM_EXTREME=y
- x86/kasan: Use the same shadow offset for 4- and 5-level paging
- x86/xen: Provide pre-built page tables only for CONFIG_XEN_PV=y and
  CONFIG_XEN_PVH=y
- x86/xen: Drop 5-level paging support code from the XEN_PV code
- ACPI / APEI: remove the unused dead-code for SEA/NMI notification type
- x86/asm: Don't use the confusing '.ifeq' directive
- x86/build: Beautify build log of syscall headers
- x86/mm/64: Rename the register_page_bootmem_memmap() 'size' parameter to
  'nr_pages'
- x86/cpufeatures: Enable new SSE/AVX/AVX512 CPU features
- x86/mm: Relocate page fault error codes to traps.h
- x86/boot: Relocate definition of the 

[Touch-packages] [Bug 1535840] Re: systemd ignoring /etc/modules due to blacklist

[David]

This problem still exists.

The problem is that these modules are listed in the blacklist files
provided with the kernel(/lib/modprobe.d/blacklist_linux-*.conf). Given
that these files aren't located in /etc they apparently are not
configuration files. Also very new kernel package you get a new file
with a different name.

Why are they blacklisted in this way? Why not only in /etc/modprobe.d
/blacklist-watchdog.conf? Is there a way to overwrite this blacklisting
through configuration files?

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

Title:
  systemd ignoring /etc/modules due to blacklist

Status in systemd package in Ubuntu:
  Opinion

Bug description:
  I tried the daily build of 16.04 32-bit to test out the watchdog
  daemon code. Usually (Ubuntu 10.04-14.04) I add the watchdog module in
  /etc/modules so it is loaded at boot-time, as watchdog timer modules
  are not normally auto-loaded due to the risk of an unexpected reboot.

  However I now find that systemd is choosing to ignore my command to
  load the module in /etc/modules since it appears in the watchdog
  blacklist. Typical syslog entries look like this:

  Jan 19 16:46:14 ubuntu systemd-modules-load[337]: Module 'softdog' is 
blacklisted
  Jan 19 17:53:23 ubuntu systemd-modules-load[342]: Module 'softdog' is 
blacklisted

  This is just dumb! I have explicitly told the system to load the
  module, an action that works perfectly well using modprobe or by
  adding it to the start script for the watchdog, and yet systemd
  chooses to override that because of the blacklist for auto-loaded
  modules (in this case in /etc/modprobe.d/blacklist-watchdog.conf).

  $ lsb_release -rd
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  $ apt-cache policy systemd
  systemd:
Installed: 228-4ubuntu1
Candidate: 228-4ubuntu1
Version table:
   *** 228-4ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status

  What I expect to happen is modules added to /etc/modules are loaded at
  boot time, and not subject to the blacklist for hardware detect /
  automatic loading.

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

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

[Touch-packages] [Bug 961679] Re: gtkrc is producing light menus from dark elements

[Treviño]

** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done

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

Title:
  gtkrc is producing light menus from dark elements

Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  Menu items for apps using gtk2 use a light color, which is
  inconsistent with all other system apps using gtk3 and that are using
  dark menus.

  [Test case]

  Right click on any window's title bar
  In app window menus of gtk 2 apps, examples -  synaptic, browsers where 
global menus aren't used, vlc with no global menu, ect.
  Right click in a browser's  menu bar
  Systray right click menus

  The in app window  context menu of gtk2 windows should be dark.

  [Regression potential]

  Menu items not usable or readable in some apps.

  ProblemType: BugDistroRelease: Ubuntu 12.04
  Package: light-themes 0.1.8.31-0ubuntu1 [modified: 
usr/share/themes/Ambiance/gtk-2.0/gtkrc 
usr/share/themes/Ambiance/gtk-3.0/apps/nautilus.css 
usr/share/themes/Ambiance/gtk-3.0/gtk-widgets.css 
usr/share/themes/Ambiance/gtk-3.0/gtk.css 
usr/share/themes/Ambiance/gtk-3.0/settings.ini 
usr/share/themes/Ambiance/metacity-1/close.png 
usr/share/themes/Ambiance/metacity-1/close_focused_normal.png 
usr/share/themes/Ambiance/metacity-1/close_focused_prelight.png 
usr/share/themes/Ambiance/metacity-1/close_focused_pressed.png 
usr/share/themes/Ambiance/metacity-1/metacity-theme-1.xml]
  ProcVersionSignature: Ubuntu 3.2.0-19.30-generic-pae 3.2.11
  Uname: Linux 3.2.0-19-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: i386
  Date: Wed Mar 21 17:42:27 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: light-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1736757] Re: [PATCH] Avahi does not support local-only services via the loopback interface

[Till Kamppeter]

I have applied the patch to the current package now and locally tested
it. It is also working with this new version of Avahi.

A new debdiff for the Ubuntu package is attached. Please upload this
version. Thanks.

** Patch added: "avahi_0.7-3ubuntu1_0.7-3ubuntu2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1736757/+attachment/5033865/+files/avahi_0.7-3ubuntu1_0.7-3ubuntu2.debdiff

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

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

Title:
  [PATCH] Avahi does not support local-only services via the loopback
  interface

Status in avahi package in Ubuntu:
  In Progress

Bug description:
  To allow the more sophisticated functionality of IPP network printers (web 
admin interface, query printer capabilities and job status from printer) also 
on USB printers, newer USB printers support the IPP-over-USB standard which is 
supported under Linux via the ippusbxd package from OpenPrinting. The ippusbxd 
daemon connects to the USB printer and mirrors it into a virtual IPP network 
printer on localhost, port 6.
  CUPS and cups-browsed find IPP printers by the printer's DNS-SD broadcasts. 
On Linux systems avahi-daemon is handling the registration of local services 
and also the discovery of remote services. This works well with local services 
shared to the network as Avahi does appropriate broadcasts on network 
interfaces (eth0, wlan0, ...) but Avahi does not handle the loopback device lo 
for local services ("localhost"). So the local-only IPP-over-USB printer on 
localhost:6, registered by ippusbxd does not get advertised, not even 
locally.
  The attached patchfor the Ubuntu package of Avahi adds support for such 
services.
  See also the upstream bug report https://github.com/lathiat/avahi/issues/125

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

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

[Touch-packages] [Bug 1742310] [NEW] No network in recovery mode (systemd-resolved does not start)

[Lastique]

Public bug reported:

When booting into recovery mode and enabling networking, networking does
not get enabled. DNS lookup doesn't work because systemd-resolved does
not start and /etc/resolv.conf is a broken symlink.

Steps to reproduce:

1. Reboot.
2. In the grub menu, select "Advanced options for Ubuntu" and then select boot 
in recovery mode.
3. When the menu appears, select "networking". In the console you may notice a 
few errors that /etc/resolv.conf file not found.
4. Select "drop to root" console.
5. Try pinging some hosts, like "ping ubuntu.com". You will see that name 
resolution doesn't work.
6. You can check that the network interface is up, "ip addr" displays valid 
info and the interface has an assigned local IP.
7. You can check that /etc/resolv.conf is in fact a dangling link to 
../run/resolvconf/resolv.conf.
8. You can see that systemd-resolved is not running: "systemctl status 
systemd-resolved" shows the service is dead.
9. Invoking "systemctl start systemd-resolved" hangs indefinitely, the service 
not starting.

The workaround to get DNS working is to replace /etc/resolv.conf with a
valid link or a file with a DNS server.

The DNS lookup and networking in general works fine if the system is
booted normally.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: systemd 234-2ubuntu12.1
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: KDE
Date: Wed Jan 10 02:18:14 2018
InstallationDate: Installed on 2015-05-01 (984 days ago)
InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf 
nomdmonisw
SourcePackage: systemd
SystemdDelta:
 [MASKED] /etc/systemd/system/samba-ad-dc.service → 
/lib/systemd/system/samba-ad-dc.service
 [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
 
 3 overridden configuration files found.
UpgradeStatus: Upgraded to artful on 2017-11-03 (67 days ago)
dmi.bios.date: 11/09/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3603
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8Z68-V PRO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug artful

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

Title:
  No network in recovery mode (systemd-resolved does not start)

Status in systemd package in Ubuntu:
  New

Bug description:
  When booting into recovery mode and enabling networking, networking
  does not get enabled. DNS lookup doesn't work because systemd-resolved
  does not start and /etc/resolv.conf is a broken symlink.

  Steps to reproduce:

  1. Reboot.
  2. In the grub menu, select "Advanced options for Ubuntu" and then select 
boot in recovery mode.
  3. When the menu appears, select "networking". In the console you may notice 
a few errors that /etc/resolv.conf file not found.
  4. Select "drop to root" console.
  5. Try pinging some hosts, like "ping ubuntu.com". You will see that name 
resolution doesn't work.
  6. You can check that the network interface is up, "ip addr" displays valid 
info and the interface has an assigned local IP.
  7. You can check that /etc/resolv.conf is in fact a dangling link to 
../run/resolvconf/resolv.conf.
  8. You can see that systemd-resolved is not running: "systemctl status 
systemd-resolved" shows the service is dead.
  9. Invoking "systemctl start systemd-resolved" hangs indefinitely, the 
service not starting.

  The workaround to get DNS working is to replace /etc/resolv.conf with
  a valid link or a file with a DNS server.

  The DNS lookup and networking in general works fine if the system is
  booted normally.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  

Re: [Touch-packages] [Bug 1735798] Re: Unable to access any subdomain provided by VPN provider until reboot.

[Austin Hester]

I have figured this out as well. It would be nice to be able to use
gnome-network-manager though.

On Jan 9, 2018 18:25, "mash" <1735...@bugs.launchpad.net> wrote:

> The problem occurs when I use network-manager to initiate the VPN.
>
>
> The problem does not occur when I run openconnect from the command line:
>
> sudo openconnect --cafile /etc/ssl/certs/ca-certificates.crt --juniper
> https://vpn.myschool.edu
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1735798
>
> Title:
>   Unable to access any subdomain provided by VPN provider until reboot.
>
> Status in network-manager package in Ubuntu:
>   Confirmed
> Status in openconnect package in Ubuntu:
>   Confirmed
>
> Bug description:
>   After disconnecting from VPN, ubuntu is unable to reconnect to the VPN
>   and any domain hosted by the server. For reference, this is my
>   school's VPN, and I am unable to get on mygateway or even the school's
>   main website after I disconnect from the VPN or the computer sleeps
>   after the VPN has been started. It uses EAP authentication.
>
>   Here is the log after connecting once, turning off, and restarting:
>   LOG:
>   POST https://vpn.myschool.edu/
>   getaddrinfo failed for host 'vpn.myschool.edu': Name or service not
> known
>   Failed to open HTTPS connection to vpn.myschool.edu
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 17.10
>   Package: network-manager 1.8.4-1ubuntu3
>   ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
>   Uname: Linux 4.13.0-17-generic x86_64
>   ApportVersion: 2.20.7-0ubuntu3.5
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Fri Dec  1 11:39:56 2017
>   IfupdownConfig:
># interfaces(5) file used by ifup(8) and ifdown(8)
>auto lo
>iface lo inet loopback
>   InstallationDate: Installed on 2016-12-02 (364 days ago)
>   InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64
> (20161012.2)
>   IpRoute:
>default via 192.168.1.1 dev wlp5s0 proto static metric 600
>169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
>192.168.1.0/24 dev wlp5s0 proto kernel scope link src 192.168.1.144
> metric 600
>192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
> linkdown
>   NetworkManager.state:
>[main]
>NetworkingEnabled=true
>WirelessEnabled=true
>WWANEnabled=true
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: network-manager
>   UpgradeStatus: Upgraded to artful on 2017-10-24 (38 days ago)
>   nmcli-nm:
>RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING
> WIFI-HW  WIFI WWAN-HW  WWAN
>running  1.8.4connected  started  full  enabled
>  enabled  enabled  enabled  enabled
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1735798/+
> subscriptions
>

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

Title:
  Unable to access any subdomain provided by VPN provider until reboot.

Status in network-manager package in Ubuntu:
  Confirmed
Status in openconnect package in Ubuntu:
  Confirmed

Bug description:
  After disconnecting from VPN, ubuntu is unable to reconnect to the VPN
  and any domain hosted by the server. For reference, this is my
  school's VPN, and I am unable to get on mygateway or even the school's
  main website after I disconnect from the VPN or the computer sleeps
  after the VPN has been started. It uses EAP authentication.

  Here is the log after connecting once, turning off, and restarting:
  LOG:
  POST https://vpn.myschool.edu/
  getaddrinfo failed for host 'vpn.myschool.edu': Name or service not known
  Failed to open HTTPS connection to vpn.myschool.edu

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  1 11:39:56 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-12-02 (364 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IpRoute:
   default via 192.168.1.1 dev wlp5s0 proto static metric 600
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.1.0/24 dev wlp5s0 proto kernel scope link src 192.168.1.144 metric 
600
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   

[Touch-packages] [Bug 1736757] Re: [PATCH] Avahi does not support local-only services via the loopback interface

[Till Kamppeter]

Patch did not get overtaken into 0.7-3ubuntu1, reopening.

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

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

Title:
  [PATCH] Avahi does not support local-only services via the loopback
  interface

Status in avahi package in Ubuntu:
  New

Bug description:
  To allow the more sophisticated functionality of IPP network printers (web 
admin interface, query printer capabilities and job status from printer) also 
on USB printers, newer USB printers support the IPP-over-USB standard which is 
supported under Linux via the ippusbxd package from OpenPrinting. The ippusbxd 
daemon connects to the USB printer and mirrors it into a virtual IPP network 
printer on localhost, port 6.
  CUPS and cups-browsed find IPP printers by the printer's DNS-SD broadcasts. 
On Linux systems avahi-daemon is handling the registration of local services 
and also the discovery of remote services. This works well with local services 
shared to the network as Avahi does appropriate broadcasts on network 
interfaces (eth0, wlan0, ...) but Avahi does not handle the loopback device lo 
for local services ("localhost"). So the local-only IPP-over-USB printer on 
localhost:6, registered by ippusbxd does not get advertised, not even 
locally.
  The attached patchfor the Ubuntu package of Avahi adds support for such 
services.
  See also the upstream bug report https://github.com/lathiat/avahi/issues/125

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

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

[Touch-packages] [Bug 1735798] Re: Unable to access any subdomain provided by VPN provider until reboot.

[mash]

The problem occurs when I use network-manager to initiate the VPN.


The problem does not occur when I run openconnect from the command line:

sudo openconnect --cafile /etc/ssl/certs/ca-certificates.crt --juniper
https://vpn.myschool.edu

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

Title:
  Unable to access any subdomain provided by VPN provider until reboot.

Status in network-manager package in Ubuntu:
  Confirmed
Status in openconnect package in Ubuntu:
  Confirmed

Bug description:
  After disconnecting from VPN, ubuntu is unable to reconnect to the VPN
  and any domain hosted by the server. For reference, this is my
  school's VPN, and I am unable to get on mygateway or even the school's
  main website after I disconnect from the VPN or the computer sleeps
  after the VPN has been started. It uses EAP authentication.

  Here is the log after connecting once, turning off, and restarting:
  LOG:
  POST https://vpn.myschool.edu/
  getaddrinfo failed for host 'vpn.myschool.edu': Name or service not known
  Failed to open HTTPS connection to vpn.myschool.edu

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  1 11:39:56 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-12-02 (364 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IpRoute:
   default via 192.168.1.1 dev wlp5s0 proto static metric 600
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.1.0/24 dev wlp5s0 proto kernel scope link src 192.168.1.144 metric 
600
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to artful on 2017-10-24 (38 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1742301] Re: /usr/bin/software-properties-gtk:UnboundLocalError:show_drivers:gather_device_data

[Brian Murray]

Here's the traceback:

Traceback (most recent call last):
  File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 1349, in show_drivers
(overall_status, icon, drivers) = 
self.gather_device_data(self.devices[device])
  File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 1337, in gather_device_data
return (overall_status, icon, returned_drivers)
UnboundLocalError: local variable 'overall_status' referenced before assignment

It seems like overall_status and icon should be set to something so we
don't hit this situation.

** Tags added: rls-bb-incoming

** Changed in: software-properties (Ubuntu)
   Status: New => Triaged

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => High

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

Title:
  /usr/bin/software-properties-
  gtk:UnboundLocalError:show_drivers:gather_device_data

Status in software-properties package in Ubuntu:
  Triaged

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

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

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

[Touch-packages] [Bug 1742301] [NEW] /usr/bin/software-properties-gtk:UnboundLocalError:show_drivers:gather_device_data

[errors.ubuntu.com bug bridge]

Public bug reported:

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

** Affects: software-properties (Ubuntu)
 Importance: High
 Status: Triaged


** Tags: artful rls-bb-incoming trusty utopic vivid wily xenial yakkety zesty

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

Title:
  /usr/bin/software-properties-
  gtk:UnboundLocalError:show_drivers:gather_device_data

Status in software-properties package in Ubuntu:
  Triaged

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

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

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

[Touch-packages] [Bug 1070873] Re: kde-telepathy, impossible to connect to gmail accounts

[Florian Fainelli]

I can confirm that signon-ui-service
(0.17+17.10.20171027+really20160406-0ubuntu1~ppa1) and signon-ui-x11
(0.17+17.10.20171027+really20160406-0ubuntu1~ppa1) allow me to get past
the Google account error. The account shows up, but going online does
not quite work yet (which I have seen before).

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

Title:
  kde-telepathy, impossible to connect to gmail accounts

Status in meta-kde-telepathy package in Ubuntu:
  Confirmed
Status in signon-ui package in Ubuntu:
  Confirmed

Bug description:
  Im running ubuntu 12.10 quantal and i have installed kde, when running
  kde-telepathy i have added a gmail account, and after entering the
  password it has revealed impossible to connect to it, it always says
  that the password is wrong when that is false.

  When using empathy, i have removed the gmail account and have added it
  again, now appears a XMLL window asking ubuntu permission to conenct
  to it, and now i was able to conenct to the gmail account.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/meta-kde-telepathy/+bug/1070873/+subscriptions

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

[Touch-packages] [Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade

[Timo Aaltonen]

this is a more complete command to install stock hwe stack on 16.04

sudo apt install --install-recommends xserver-xorg xserver-xorg-core
xserver-xorg-video-all xserver-xorg-input-all xserver-xorg-video-intel
xserver-xorg-video-qxl

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Xenial:
  Confirmed
Status in mesa source package in Artful:
  Confirmed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

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

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

[Touch-packages] [Bug 1725333] Re: do-release-upgrade broke WSL

[Bug Watch Updater]

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

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

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

Title:
  do-release-upgrade broke WSL

Status in GLibC:
  Fix Released
Status in Gnu Bash:
  Fix Released
Status in bash package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  New

Bug description:
  I had Ubuntu 17.04 installed in WSL and decided to upgrade it to
  17.10, so I had run do-release-upgrade, as I did before to upgrade to
  17.04. Everything was fine before script started upgrading packages.
  It's started from bash updating, and somehow there is a problem
  revealed that locale files is missing, and locale-gen can't be run
  (because of bug in WSL). I've tried to install language-pack-en as was
  suggested, but problem haven't resolved, any attempt to update leads
  to this error.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: bash 4.4-2ubuntu1.1
  ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
  Uname: Linux 4.4.0-43-Microsoft x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Fri Oct 20 18:03:30 2017
  Dmesg:
   
  DpkgTerminalLog:
   Preparing to unpack .../bash_4.4-5ubuntu1_amd64.deb ...
   preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec 
>= 0' failed.
   dpkg: error processing archive 
/var/cache/apt/archives/bash_4.4-5ubuntu1_amd64.deb (--unpack):
subprocess new pre-installation script was killed by signal (Aborted), core 
dumped
  DuplicateSignature:
   package:bash:4.4-2ubuntu1.1
   Preparing to unpack .../bash_4.4-5ubuntu1_amd64.deb ...
   preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec 
>= 0' failed.
   dpkg: error processing archive 
/var/cache/apt/archives/bash_4.4-5ubuntu1_amd64.deb (--unpack):
subprocess new pre-installation script was killed by signal (Aborted), core 
dumped
  ErrorMessage: subprocess new pre-installation script was killed by signal 
(Aborted), core dumped
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4.6~17.04.1
  SourcePackage: bash
  Title: package bash 4.4-2ubuntu1.1 failed to install/upgrade: subprocess new 
pre-installation script was killed by signal (Aborted), core dumped
  UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago)

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

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

[Touch-packages] [Bug 1741925] Re: Unity launcher disappears on mouse-over launcher

[Timo Aaltonen]

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

not emails but replies/edits to that bug

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

Title:
  Unity launcher disappears on mouse-over launcher

Status in mesa package in Ubuntu:
  New

Bug description:
  Move the mouse over the launcher and the EVERYTHING on the desktop
  disappears for a few seconds. Only the wallpaper remains. Failed
  immediately after the latest update (installed by me on 5 Jan 2018)
  and a reboot. Reboot doesn't help.

  Launcher and the other desktop displays return after a 10 to 30 second
  pause. No disk activity is observed during recovery.

  "ClassicMenu Indicator" is installed and it is the only way to start
  an application.

  Executing the bug and then immediately examining all the /var/log logs
  showed no recorded error or incident in any log.

  uname -a = Linux bruce-Latitude-D630 4.10.0-42-generic
  #46~16.04.1-Ubuntu SMP Mon Dec 4 15:57:59 UTC 2017 i686 i686 i686
  GNU/Linux

  Abridged hardware list from  sudo lshw
   
  description: Portable Computer
  product: Latitude D630
  vendor: Dell Inc.
  width: 32 bits
  capabilities: smbios-2.4 dmi-2.4
  configuration: boot=normal chassis=portable 
uuid=44454C4C-6E00-1039-8032-B2C04F376831
*-core
 description: Motherboard
 vendor: Dell Inc.
 physical id: 0
 serial: .2n927h1.  .
   *-firmware
description: BIOS
vendor: Dell Inc.
physical id: 0
version: A12
date: 06/20/2008
size: 64KiB
capacity: 1984KiB
capabilities: isa pci pcmcia pnp upgrade shadowing cdboot 
bootselect int13floppy720 int5printscreen int9keyboard int14serial int17printer 
int10video acpi usb agp smartbattery biosbootspecification netboot
   *-cpu
description: CPU
product: Intel(R) Core(TM)2 Duo CPU T7250  @ 2.00GHz
vendor: Intel Corp.
physical id: 400
bus info: cpu@0
version: 6.15.13
serial: -06FD----
slot: Microprocessor
size: 2GHz
capacity: 2001MHz
width: 64 bits
clock: 200MHz
capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae 
mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 
ss ht tm pbe nx constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 
monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm tpr_shadow vnmi 
flexpriority dtherm ida cpufreq
configuration: cores=2 enabledcores=2 id=0 threads=2
  *-cache:0
   description: L1 cache
   physical id: 700
   size: 32KiB
   capacity: 32KiB
   capabilities: internal write-back data
   configuration: level=1
  *-cache:1
   description: L2 cache
   physical id: 701
   size: 2MiB
   capacity: 2MiB
   clock: 66MHz (15.0ns)
   capabilities: pipeline-burst internal varies unified
   configuration: level=2
  *-logicalcpu:0
   description: Logical CPU
   physical id: 0.1
   width: 64 bits
   capabilities: logical
  *-logicalcpu:1
   description: Logical CPU
   physical id: 0.2
   width: 64 bits
   capabilities: logical
   *-memory
description: System Memory
physical id: 1000
slot: System board or motherboard
size: 2GiB
  *-bank:0
   description: DIMM DDR Synchronous 667 MHz (1.5 ns)
   product: V916765G24QCFW-F5
   vendor: ProMOS/Mosel Vitelic
   physical id: 0
   serial: 07B02E7C
   slot: DIMM_A
   size: 1GiB
   width: 64 bits
   clock: 667MHz (1.5ns)
  *-bank:1
   description: DIMM DDR Synchronous 667 MHz (1.5 ns)
   product: V916765G24QCFW-F5
   vendor: ProMOS/Mosel Vitelic
   physical id: 1
   serial: E9AE2E7D
   slot: DIMM_B
   size: 1GiB
   width: 64 bits
   clock: 667MHz (1.5ns)
   *-pci
description: Host bridge
product: Mobile PM965/GM965/GL960 Memory Controller Hub
vendor: Intel Corporation
physical id: 100
bus info: pci@:00:00.0
version: 0c
width: 32 bits
clock: 33MHz

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

-- 
Mailing list: 

[Touch-packages] [Bug 1741925] Re: Unity launcher disappears on mouse-over launcher

[Timo Aaltonen]

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

no need to debug anymore, the issue is well known by now and 1735594 has
more information, you should have received my emails about it

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

Title:
  Unity launcher disappears on mouse-over launcher

Status in mesa package in Ubuntu:
  New

Bug description:
  Move the mouse over the launcher and the EVERYTHING on the desktop
  disappears for a few seconds. Only the wallpaper remains. Failed
  immediately after the latest update (installed by me on 5 Jan 2018)
  and a reboot. Reboot doesn't help.

  Launcher and the other desktop displays return after a 10 to 30 second
  pause. No disk activity is observed during recovery.

  "ClassicMenu Indicator" is installed and it is the only way to start
  an application.

  Executing the bug and then immediately examining all the /var/log logs
  showed no recorded error or incident in any log.

  uname -a = Linux bruce-Latitude-D630 4.10.0-42-generic
  #46~16.04.1-Ubuntu SMP Mon Dec 4 15:57:59 UTC 2017 i686 i686 i686
  GNU/Linux

  Abridged hardware list from  sudo lshw
   
  description: Portable Computer
  product: Latitude D630
  vendor: Dell Inc.
  width: 32 bits
  capabilities: smbios-2.4 dmi-2.4
  configuration: boot=normal chassis=portable 
uuid=44454C4C-6E00-1039-8032-B2C04F376831
*-core
 description: Motherboard
 vendor: Dell Inc.
 physical id: 0
 serial: .2n927h1.  .
   *-firmware
description: BIOS
vendor: Dell Inc.
physical id: 0
version: A12
date: 06/20/2008
size: 64KiB
capacity: 1984KiB
capabilities: isa pci pcmcia pnp upgrade shadowing cdboot 
bootselect int13floppy720 int5printscreen int9keyboard int14serial int17printer 
int10video acpi usb agp smartbattery biosbootspecification netboot
   *-cpu
description: CPU
product: Intel(R) Core(TM)2 Duo CPU T7250  @ 2.00GHz
vendor: Intel Corp.
physical id: 400
bus info: cpu@0
version: 6.15.13
serial: -06FD----
slot: Microprocessor
size: 2GHz
capacity: 2001MHz
width: 64 bits
clock: 200MHz
capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae 
mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 
ss ht tm pbe nx constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 
monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm tpr_shadow vnmi 
flexpriority dtherm ida cpufreq
configuration: cores=2 enabledcores=2 id=0 threads=2
  *-cache:0
   description: L1 cache
   physical id: 700
   size: 32KiB
   capacity: 32KiB
   capabilities: internal write-back data
   configuration: level=1
  *-cache:1
   description: L2 cache
   physical id: 701
   size: 2MiB
   capacity: 2MiB
   clock: 66MHz (15.0ns)
   capabilities: pipeline-burst internal varies unified
   configuration: level=2
  *-logicalcpu:0
   description: Logical CPU
   physical id: 0.1
   width: 64 bits
   capabilities: logical
  *-logicalcpu:1
   description: Logical CPU
   physical id: 0.2
   width: 64 bits
   capabilities: logical
   *-memory
description: System Memory
physical id: 1000
slot: System board or motherboard
size: 2GiB
  *-bank:0
   description: DIMM DDR Synchronous 667 MHz (1.5 ns)
   product: V916765G24QCFW-F5
   vendor: ProMOS/Mosel Vitelic
   physical id: 0
   serial: 07B02E7C
   slot: DIMM_A
   size: 1GiB
   width: 64 bits
   clock: 667MHz (1.5ns)
  *-bank:1
   description: DIMM DDR Synchronous 667 MHz (1.5 ns)
   product: V916765G24QCFW-F5
   vendor: ProMOS/Mosel Vitelic
   physical id: 1
   serial: E9AE2E7D
   slot: DIMM_B
   size: 1GiB
   width: 64 bits
   clock: 667MHz (1.5ns)
   *-pci
description: Host bridge
product: Mobile PM965/GM965/GL960 Memory Controller Hub
vendor: Intel Corporation
physical id: 100
bus info: pci@:00:00.0
version: 0c
width: 32 bits
clock: 33MHz

To manage notifications about this bug go to:

[Touch-packages] [Bug 774071] Re: Indicator-datetime-service renders 100% CPU usage

[Rüdiger Kupper]

No. I see it in 17.10 as of today (2018-01-09). I cannot log intro Unity
because of this bug. Right after login, indicator-datetime-service" eats
all of my CPU, breaks, starts again, eats all of my CPU, breaks, starts
again, eats all of my CPU, breaks, starts again, eats all of my CPU,
breaks, starts again, eats all of my CPU, breaks, starts again, eats all
of my CPU, breaks, starts again, eats all of my CPU, breaks, starts
again, eats all of my CPU, breaks, starts again, eats all of my CPU,
breaks, starts again, eats all of my CPU, breaks, starts again, eats all
of my CPU, breaks, starts again, eats all of my CPU, breaks, starts
again, eats all of my CPU, breaks, starts again, eats all of my CPU,
breaks, starts again, eats all of my CPU, breaks, starts again, eats all
of my CPU, breaks, starts again, eats all of my CPU, breaks, starts
again, eats all of my CPU, breaks, starts again, eats all of my CPU,
breaks, starts again, eats all of my CPU, breaks, starts again, eats all
of my CPU, breaks, starts again, eats all of my CPU, breaks, starts
again...

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

Title:
  Indicator-datetime-service renders 100% CPU usage

Status in Indicator Date and Time:
  Fix Released
Status in Unity Foundations:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: indicator-datetime

  On my laptop "indicator-datetime-service" occasionally make my CPU to
  use 100% of its resources. It does not happen every time I log in to
  Ubuntu, but when it happens, it stays hogging 100% of CPU until I kill
  the process. If it helps, I've noticed in "System Monitor" that there
  are two instances of "indicator-datetime-service" running, but only
  one of them is hogging recourses. So far I was unable to determine
  after what actions/events this bug pups up.

  I'm using Ubuntu 11.04 64-bit.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: indicator-datetime 0.2.3-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Sat Apr 30 15:27:58 2011
  ExecutablePath: /usr/lib/indicator-datetime/indicator-datetime-service
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to natty on 2011-04-28 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/774071/+subscriptions

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

[Touch-packages] [Bug 1605189] Re: Authentication is required for suspending the system

[Heitor Moreira]

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

** This bug has been marked a duplicate of bug 1441460
   [xubuntu] Failing to sleep after inactivity - power manager error?

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

Title:
  Authentication is required for suspending the system

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Automatic suspend from the xfce power manager does not work, as a
  window opens and asks for my password. Well, if it wants to suspend
  the system after a given timeout, I cannot enter my password as I'm
  not in front of my system then. Once I'm able to enter my password it
  is too late to run the suspend action.

  The window asking for my password prints:

  Password: 

  Details

  Action: org.freedesktop.login1.suspend
  Vendor: The systemd project

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu7
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Jul 21 13:13:12 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-08-17 (703 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: LENOVO 4236ML1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic 
root=/dev/mapper/ubuntu--vg-root ro intel_pstate=enable
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   
   2 overridden configuration files found.
  UpgradeStatus: Upgraded to xenial on 2016-05-28 (53 days ago)
  dmi.bios.date: 07/05/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83ET76WW (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4236ML1
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr83ET76WW(1.46):bd07/05/2013:svnLENOVO:pn4236ML1:pvrThinkPadT420:rvnLENOVO:rn4236ML1:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4236ML1
  dmi.product.version: ThinkPad T420
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1613184] Re: method mirror broken at 1.3

[Julian Andres Klode]

Marked xenial as verified, because, while the problem itself does not
exist, it still fixes the same underlying bug from an API perspective.

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

Title:
  method mirror broken at 1.3

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  The mirror method always dies with a SEGV. It does not initialize _system but 
calls a function that sometimes uses it.

  [Test case]
  Use a mirror sources.list entry like

  deb mirror://mirrors.ubuntu.com/mirrors.txt zesty main restricted
  universe multiverse

  [Regression potential]
  The fix is small, and simply avoids using _system if _system is NULL in the 
called method. There should not be any regressions due to this.

  
https://anonscm.debian.org/cgit/apt/apt.git/commit/?id=cba5c5a26a9bf00724f8ea647ac61b30e32734ba

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

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

[Touch-packages] [Bug 1735798] Re: Unable to access any subdomain provided by VPN provider until reboot.

[Launchpad Bug Tracker]

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

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

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

Title:
  Unable to access any subdomain provided by VPN provider until reboot.

Status in network-manager package in Ubuntu:
  Confirmed
Status in openconnect package in Ubuntu:
  Confirmed

Bug description:
  After disconnecting from VPN, ubuntu is unable to reconnect to the VPN
  and any domain hosted by the server. For reference, this is my
  school's VPN, and I am unable to get on mygateway or even the school's
  main website after I disconnect from the VPN or the computer sleeps
  after the VPN has been started. It uses EAP authentication.

  Here is the log after connecting once, turning off, and restarting:
  LOG:
  POST https://vpn.myschool.edu/
  getaddrinfo failed for host 'vpn.myschool.edu': Name or service not known
  Failed to open HTTPS connection to vpn.myschool.edu

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  1 11:39:56 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-12-02 (364 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IpRoute:
   default via 192.168.1.1 dev wlp5s0 proto static metric 600
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.1.0/24 dev wlp5s0 proto kernel scope link src 192.168.1.144 metric 
600
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to artful on 2017-10-24 (38 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1735798] Re: Unable to access any subdomain provided by VPN provider until reboot.

[Launchpad Bug Tracker]

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

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

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

Title:
  Unable to access any subdomain provided by VPN provider until reboot.

Status in network-manager package in Ubuntu:
  Confirmed
Status in openconnect package in Ubuntu:
  Confirmed

Bug description:
  After disconnecting from VPN, ubuntu is unable to reconnect to the VPN
  and any domain hosted by the server. For reference, this is my
  school's VPN, and I am unable to get on mygateway or even the school's
  main website after I disconnect from the VPN or the computer sleeps
  after the VPN has been started. It uses EAP authentication.

  Here is the log after connecting once, turning off, and restarting:
  LOG:
  POST https://vpn.myschool.edu/
  getaddrinfo failed for host 'vpn.myschool.edu': Name or service not known
  Failed to open HTTPS connection to vpn.myschool.edu

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  1 11:39:56 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-12-02 (364 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IpRoute:
   default via 192.168.1.1 dev wlp5s0 proto static metric 600
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.1.0/24 dev wlp5s0 proto kernel scope link src 192.168.1.144 metric 
600
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to artful on 2017-10-24 (38 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1613184] Re: method mirror broken at 1.3

[Julian Andres Klode]

** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial

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

Title:
  method mirror broken at 1.3

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  The mirror method always dies with a SEGV. It does not initialize _system but 
calls a function that sometimes uses it.

  [Test case]
  Use a mirror sources.list entry like

  deb mirror://mirrors.ubuntu.com/mirrors.txt zesty main restricted
  universe multiverse

  [Regression potential]
  The fix is small, and simply avoids using _system if _system is NULL in the 
called method. There should not be any regressions due to this.

  
https://anonscm.debian.org/cgit/apt/apt.git/commit/?id=cba5c5a26a9bf00724f8ea647ac61b30e32734ba

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

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

[Touch-packages] [Bug 1742276] [NEW] package findutils (not installed) failed to install/upgrade: в новой версии пакета нет этого сценария, отказ

[Vyacheslav]

Public bug reported:

!

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: findutils (not installed)
ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Wed Jan  3 18:28:17 2018
ErrorMessage: в новой версии пакета нет этого сценария, отказ
InstallationDate: Installed on 2017-07-20 (173 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: findutils
Title: package findutils (not installed) failed to install/upgrade: в новой 
версии пакета нет этого сценария, отказ
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package findutils (not installed) failed to install/upgrade: в новой
  версии пакета нет этого сценария, отказ

Status in findutils package in Ubuntu:
  New

Bug description:
  !

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: findutils (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Jan  3 18:28:17 2018
  ErrorMessage: в новой версии пакета нет этого сценария, отказ
  InstallationDate: Installed on 2017-07-20 (173 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: findutils
  Title: package findutils (not installed) failed to install/upgrade: в новой 
версии пакета нет этого сценария, отказ
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade

[Timo Aaltonen]

PPA builders are unfortunately still offline because of SPECTRE :(

One quick workaround for this issue is to downgrade to stock 16.04
xserver and install x-x-v-intel:

sudo apt install --install-recommends xserver-xorg xserver-xorg-video-
all xserver-xorg-input-all xserver-xorg-video-intel

that should do it.. it'll remove a bunch of packages named -hwe-16.04
and replace them with the stock packages.

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Xenial:
  Confirmed
Status in mesa source package in Artful:
  Confirmed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

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

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

[Touch-packages] [Bug 1742269] [NEW] Keyboard focus not visible on popover menu entries

[Egmont Koblinger]

Public bug reported:

Open a popover menu with text entries, such as:

- Files (Nautilus): "hamburger" menu on the upper right

- Tilix: "hamburger" menu, or right-click over the terminal area, or
Profiles -> a triangle in the left-hand sidebar

Use the keyboard (Tab, or Up and Down) to navigate in the entries.

When an icon entry (wherever present) is focused, it has a thin orange
border. But when simple text (or checkbox, radiobutton) entries are
focused, there is no visual feedback at all, you can't see which item is
selected and hence which item would be activated by Enter or Space.

This makes popovers pretty unusable via the keyboard.

Does not happen with Adwaita.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: light-themes 16.10+17.10.20171115-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Tue Jan  9 20:54:27 2018
InstallationDate: Installed on 2016-11-09 (425 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
PackageArchitecture: all
SourcePackage: ubuntu-themes
UpgradeStatus: Upgraded to artful on 2017-09-21 (109 days ago)

** Affects: ubuntu-themes (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful

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

Title:
  Keyboard focus not visible on popover menu entries

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Open a popover menu with text entries, such as:

  - Files (Nautilus): "hamburger" menu on the upper right

  - Tilix: "hamburger" menu, or right-click over the terminal area, or
  Profiles -> a triangle in the left-hand sidebar

  Use the keyboard (Tab, or Up and Down) to navigate in the entries.

  When an icon entry (wherever present) is focused, it has a thin orange
  border. But when simple text (or checkbox, radiobutton) entries are
  focused, there is no visual feedback at all, you can't see which item
  is selected and hence which item would be activated by Enter or Space.

  This makes popovers pretty unusable via the keyboard.

  Does not happen with Adwaita.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20171115-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Tue Jan  9 20:54:27 2018
  InstallationDate: Installed on 2016-11-09 (425 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to artful on 2017-09-21 (109 days ago)

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

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

[Touch-packages] [Bug 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04

[Janghou]

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

@laurel, to find your version, try in a terminal
 lsb_release -a

If you have further questions for support or how to deal with his matter, 
please read:
https://askubuntu.com/questions/992571/gui-unity-crashing-in-16-04-lts-after-latest-updates-compiz-segfaults

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

Title:
  Unity / Compiz in a crash loop after login, after mesa updates of
  2018-01-04

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Xenial:
  Confirmed
Status in mesa source package in Artful:
  Confirmed

Bug description:
  GUI is constantly crashing, can't start desktop

  Jan  5 11:21:29 1810 kernel: [  806.368754] compiz[10824]: segfault at 0 ip 
7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000]
  Jan  5 11:21:40 1810 kernel: [  817.279740] compiz[1]: segfault at 0 ip 
7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000]
  Jan  5 11:22:30 1810 kernel: [  867.445137] compiz[11271]: segfault at 0 ip 
7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000]
  Jan  5 11:22:46 1810 kernel: [  883.319195] compiz[11458]: segfault at 0 ip 
7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000]
  Jan  5 11:23:01 1810 kernel: [  898.587610] compiz[11516]: segfault at 0 ip 
7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000]

  In /var/crash:
  _usr_bin_compiz.999.crash

  Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not 
really usable.
  - dash not working
  - no window switching
  - sometimes all windows disappear for a few seconds

  So effectively my laptop is not usable after latest updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160906-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  .tmp.unity_support_test.0:

  .tmp.unity_support_test.1:

  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Jan  5 11:16:53 2018
  DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:029b]
     Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:029b]
  InstallationDate: Installed on 2014-04-18 (1357 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Acer Aspire 1810TZ
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic 
root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago)
  dmi.bios.date: 08/31/2010
  dmi.bios.vendor: INSYDE
  dmi.bios.version: v1.3314
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JM11-MS
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: Aspire 1810TZ
  dmi.product.version: v1.3314
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Jan  5 11:14:24 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

To manage notifications about this bug go to:

[Touch-packages] [Bug 433926] Re: xkbcomp error: Type "ONE_LEVEL" has 1 levels, but has 2 symbols

[Gunnar Hjalmarsson]

On 2018-01-09 18:45, H.-Dirk Schmitt wrote:
> Still in xenial
> affected: xkb-data 2.16-1ubuntu1
> 
> │Jan  8 11:49:55 user.warning /usr/lib/gdm3/gdm-x-session[3463 >
> Warning:  Type "ONE_LEVEL" has 1 levels, but  has 2 │

This seems to be an old one. If I understand it correctly, Sergey posted
a suggestion in comment #17, but got no feedback. Can someone who is
affected provide some feedback to that suggestion?

Please note that this is not important enough to update 16.04 or any
other stable release. However, if the change would be committed
upstream, it might make it into Ubuntu 18.04.

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

Title:
  xkbcomp error: Type "ONE_LEVEL" has 1 levels, but  has 2 symbols

Status in xkeyboard-config:
  Confirmed
Status in xkeyboard-config package in Ubuntu:
  Confirmed

Bug description:
  I can confirm that the bug reported upstream is also present in Karmic alpha 
6:
  https://bugs.freedesktop.org/show_bug.cgi?id=21761

  This bug was also reported in gentoo
  http://bugs.gentoo.org/show_bug.cgi?id=269931

  and in debian
  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=291853

  Apparently a fix was released upstream, it would be nice to have it in
  Karmic as well.

  Many thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/433926/+subscriptions

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

[Touch-packages] [Bug 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04

[Angel González]

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

ppa:paulo-miguel-dias/pkppa works for me too

No more issues

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

Title:
  Unity / Compiz in a crash loop after login, after mesa updates of
  2018-01-04

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Xenial:
  Confirmed
Status in mesa source package in Artful:
  Confirmed

Bug description:
  GUI is constantly crashing, can't start desktop

  Jan  5 11:21:29 1810 kernel: [  806.368754] compiz[10824]: segfault at 0 ip 
7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000]
  Jan  5 11:21:40 1810 kernel: [  817.279740] compiz[1]: segfault at 0 ip 
7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000]
  Jan  5 11:22:30 1810 kernel: [  867.445137] compiz[11271]: segfault at 0 ip 
7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000]
  Jan  5 11:22:46 1810 kernel: [  883.319195] compiz[11458]: segfault at 0 ip 
7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000]
  Jan  5 11:23:01 1810 kernel: [  898.587610] compiz[11516]: segfault at 0 ip 
7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000]

  In /var/crash:
  _usr_bin_compiz.999.crash

  Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not 
really usable.
  - dash not working
  - no window switching
  - sometimes all windows disappear for a few seconds

  So effectively my laptop is not usable after latest updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160906-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  .tmp.unity_support_test.0:

  .tmp.unity_support_test.1:

  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Jan  5 11:16:53 2018
  DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:029b]
     Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:029b]
  InstallationDate: Installed on 2014-04-18 (1357 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Acer Aspire 1810TZ
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic 
root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago)
  dmi.bios.date: 08/31/2010
  dmi.bios.vendor: INSYDE
  dmi.bios.version: v1.3314
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JM11-MS
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: Aspire 1810TZ
  dmi.product.version: v1.3314
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Jan  5 11:14:24 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1741925] Re: Unity launcher disappears on mouse-over launcher

[Bruce MacAlister]

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

Answers:
Do you have an additional monitor connected? NO What is the display resolution 
you use? 12??X800 Do things still crash if you change the resolution to 
something smaller than the native NO

Thank you for your direction. In attempt to narrow the failure down I examined 
the two visible symptoms:
1. Mouse-over the launcher causes the launcher and the task line at the top to 
disappear
2. There appears to be a recovery time of 10 to 30 seconds and then the 
launcher and all reappear
The most likely culprits appear to be:
1. Mouse software; I assume that is part of the Lunux kernel. I was unable to 
find any information on the Ubuntu software stack or architecture so I could 
not identify the process(es) used for the mouse.
To evaluate mouse malfunction I (a) tried both the laptop’s mouse-pad and a USB 
mouse with no difference in behavior and (b) did a mouse-over of some Linux 
apps where the button or widget reacts to a mouse-over; the mouse-over behavior 
worked as expected.
My conclusion is that the mouse and the mouse code is behaving properly.
2. Launcher code; without a software stack the name of the process is 
unknowable. Doing a query in the System Monitor gave a likely 
“api-spi-bus-launcher” (see that attached image, “Launcher properties  
2018-01-09 12-44-12.png”).
An strace on that pid
sudo strace -p 1488 -b execve -o launcher.txt
[sudo] password for bruce: 
yielded
   restart_syscall(<... resuming interrupted poll ...>) = 1
   read(3, "\2\0\0\0\0\0\0\0", 16) = 8
   poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}], 2, -1) = 1 ([{fd=3, 
revents=POLLIN}])
   read(3, "\2\0\0\0\0\0\0\0", 16) = 8
   poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}], 2, -1) = 1 ([{fd=3, 
revents=POLLIN}])
   read(3, "\2\0\0\0\0\0\0\0", 16) = 8
   poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}], 2, -1
I do not know how to read strace output. The “restart_syscall” line looks 
suspiciously like an error recover execution.
The launcher disappearance behavior is captured in two images, before the 
failure “Launcher failure a 2018-01-09 12-23-23.png” and during recovery 
“Launcher failure b 2018-01-09 12-24-39.png”. They are 
attached.?field.comment=Answers:
Do you have an additional monitor connected? NO What is the display resolution 
you use? 12??X800 Do things still crash if you change the resolution to 
something smaller than the native NO

Thank you for your direction. In attempt to narrow the failure down I examined 
the two visible symptoms:
1. Mouse-over the launcher causes the launcher and the task line at the top to 
disappear
2. There appears to be a recovery time of 10 to 30 seconds and then the 
launcher and all reappear
The most likely culprits appear to be:
1. Mouse software; I assume that is part of the Lunux kernel. I was unable to 
find any information on the Ubuntu software stack or architecture so I could 
not identify the process(es) used for the mouse.
To evaluate mouse malfunction I (a) tried both the laptop’s mouse-pad and a USB 
mouse with no difference in behavior and (b) did a mouse-over of some Linux 
apps where the button or widget reacts to a mouse-over; the mouse-over behavior 
worked as expected.
My conclusion is that the mouse and the mouse code is behaving properly.
2. Launcher code; without a software stack the name of the process is 
unknowable. Doing a query in the System Monitor gave a likely 
“api-spi-bus-launcher” (see that attached image, “Launcher properties  
2018-01-09 12-44-12.png”).
An strace on that pid
sudo strace -p 1488 -b execve -o launcher.txt
[sudo] password for bruce: 
yielded
   restart_syscall(<... resuming interrupted poll ...>) = 1
   read(3, "\2\0\0\0\0\0\0\0", 16) = 8
   poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}], 2, -1) = 1 ([{fd=3, 
revents=POLLIN}])
   read(3, "\2\0\0\0\0\0\0\0", 16) = 8
   poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}], 2, -1) = 1 ([{fd=3, 
revents=POLLIN}])
   read(3, "\2\0\0\0\0\0\0\0", 16) = 8
   poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}], 2, -1
I do not know how to read strace output. The “restart_syscall” line looks 
suspiciously like an error recover execution.
The launcher disappearance behavior is captured in two images, before the 
failure “Launcher failure a 2018-01-09 12-23-23.png” and during recovery 
“Launcher failure b 2018-01-09 12-24-39.png”. They are attached.

** Attachment added: "before launcher failur"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1741925/+attachment/5033648/+files/Launcher%20failure%20a%202018-01-09%2012-23-23.png

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

Title:
  Unity launcher disappears on mouse-over launcher

Status in mesa package in Ubuntu:
  New

[Touch-packages] [Bug 1742250] [NEW] Adding and deleting a veth leaks a systemd unit

[Shaun Crampton]

Public bug reported:

When I add a veth device:

sudo ip link add name test1 type veth

I see these systemd units appear:

systemctl list-units --all | grep test

 sys-devices-virtual-net-test1.device
 loadedactive   plugged   /sys/devices/virtual/net/test1

 sys-subsystem-net-devices-test1.device
 loadedactive   plugged   /sys/subsystem/net/devices/test1

However, if I then delete the veth:

sudo ip link del dev test1

Then only one of the units is removed:

systemctl list-units --all | grep test

  sys-devices-virtual-net-test1.device
 loadedactive   plugged   /sys/devices/virtual/net/test1

This is a big problem when running, for example, a Kubernetes cluster
since each pod creation/deletion leaks a systemd unit.  When enough have
been leaked, systemd becomes unresponsive and the system is broken until
reboot.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: systemd 234-2ubuntu12.1
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
Date: Tue Jan  9 18:57:34 2018
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: Google Google Compute Engine
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=c66b8cf4-2a6c-4fb3-9f39-59483a6a025c ro scsi_mod.use_blk_mq=Y 
console=ttyS0
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Google
dmi.bios.version: Google
dmi.board.asset.tag: 1AF4A7E8-D62B-D331-0693-3511A041DD96
dmi.board.name: Google Compute Engine
dmi.board.vendor: Google
dmi.chassis.type: 1
dmi.chassis.vendor: Google
dmi.modalias: 
dmi:bvnGoogle:bvrGoogle:bd01/01/2011:svnGoogle:pnGoogleComputeEngine:pvr:rvnGoogle:rnGoogleComputeEngine:rvr:cvnGoogle:ct1:cvr:
dmi.product.name: Google Compute Engine
dmi.sys.vendor: Google

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


** Tags: amd64 apport-bug artful uec-images

** Description changed:

  When I add a veth device:
  
- sudo ip link add name test1 type veth
+ sudo ip link add name test1 type veth
  
  I see these systemd units appear:
  
- systemctl list-units --all | grep test
- smc-kubeadm-node-0: Tue Jan  9 19:02:41 2018
+ systemctl list-units --all | grep test
  
-  sys-devices-virtual-net-test1.device
-  loadedactive   plugged   /sys/devices/virtual/net/test1
+  sys-devices-virtual-net-test1.device
+  loadedactive   plugged   /sys/devices/virtual/net/test1
  
-  sys-subsystem-net-devices-test1.device
-  loadedactive   plugged   /sys/subsystem/net/devices/test1
+  sys-subsystem-net-devices-test1.device
+  loadedactive   plugged   /sys/subsystem/net/devices/test1
  
  However, if I then delete the veth:
  
- sudo ip link del dev test1
+ sudo ip link del dev test1
  
  Then only one of the units is removed:
  
- systemctl list-units --all | grep test
- smc-kubeadm-node-0: Tue Jan  9 19:03:53 2018
+ systemctl list-units --all | grep test
  
-   sys-devices-virtual-net-test1.device
-  loadedactive   plugged   /sys/devices/virtual/net/test1
+   sys-devices-virtual-net-test1.device
+  loadedactive   plugged   /sys/devices/virtual/net/test1
  
  This is a big problem when running, for example, a Kubernetes cluster
  since each pod creation/deletion leaks a systemd unit.  When enough have
  been leaked, systemd becomes unresponsive and the system is broken until
  reboot.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  Date: Tue Jan  9 18:57:34 2018
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Google Google Compute Engine
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=c66b8cf4-2a6c-4fb3-9f39-59483a6a025c ro scsi_mod.use_blk_mq=Y 
console=ttyS0
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/01/2011
  dmi.bios.vendor: Google
  dmi.bios.version: Google
  dmi.board.asset.tag: 1AF4A7E8-D62B-D331-0693-3511A041DD96
  dmi.board.name: Google Compute Engine
  dmi.board.vendor: Google
  dmi.chassis.type: 1
  dmi.chassis.vendor: Google
  dmi.modalias: 
dmi:bvnGoogle:bvrGoogle:bd01/01/2011:svnGoogle:pnGoogleComputeEngine:pvr:rvnGoogle:rnGoogleComputeEngine:rvr:cvnGoogle:ct1:cvr:
  dmi.product.name: Google Compute Engine
  dmi.sys.vendor: Google

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

Title:
  Adding and deleting a veth leaks a systemd unit

Status in 

[Touch-packages] [Bug 1742250] Re: Adding and deleting a veth leaks a systemd unit

[Shaun Crampton]

As a workaround, running

systemctl daemon-reload

removes all the leaked units.

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

Title:
  Adding and deleting a veth leaks a systemd unit

Status in systemd package in Ubuntu:
  New

Bug description:
  When I add a veth device:

  sudo ip link add name test1 type veth

  I see these systemd units appear:

  systemctl list-units --all | grep test

   sys-devices-virtual-net-test1.device
   loadedactive   plugged   /sys/devices/virtual/net/test1

   sys-subsystem-net-devices-test1.device
   loadedactive   plugged   /sys/subsystem/net/devices/test1

  However, if I then delete the veth:

  sudo ip link del dev test1

  Then only one of the units is removed:

  systemctl list-units --all | grep test

    sys-devices-virtual-net-test1.device
   loadedactive   plugged   /sys/devices/virtual/net/test1

  This is a big problem when running, for example, a Kubernetes cluster
  since each pod creation/deletion leaks a systemd unit.  When enough
  have been leaked, systemd becomes unresponsive and the system is
  broken until reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  Date: Tue Jan  9 18:57:34 2018
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Google Google Compute Engine
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=c66b8cf4-2a6c-4fb3-9f39-59483a6a025c ro scsi_mod.use_blk_mq=Y 
console=ttyS0
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/01/2011
  dmi.bios.vendor: Google
  dmi.bios.version: Google
  dmi.board.asset.tag: 1AF4A7E8-D62B-D331-0693-3511A041DD96
  dmi.board.name: Google Compute Engine
  dmi.board.vendor: Google
  dmi.chassis.type: 1
  dmi.chassis.vendor: Google
  dmi.modalias: 
dmi:bvnGoogle:bvrGoogle:bd01/01/2011:svnGoogle:pnGoogleComputeEngine:pvr:rvnGoogle:rnGoogleComputeEngine:rvr:cvnGoogle:ct1:cvr:
  dmi.product.name: Google Compute Engine
  dmi.sys.vendor: Google

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

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

[Touch-packages] [Bug 1742243] [NEW] Please merge with Debian unstable 2.2.0-11.1

[Nish Aravamudan]

Public bug reported:

TBD

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

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

Title:
  Please merge with Debian unstable 2.2.0-11.1

Status in openexr package in Ubuntu:
  New

Bug description:
  TBD

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

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

[Touch-packages] [Bug 1733870] Re: [Ubuntu 18.04] Add GDB support to access/display POWER8 registers

[bugproxy]

** Tags removed: targetmilestone-inin1804
** Tags added: targetmilestone-inin1810

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

Title:
  [Ubuntu 18.04] Add GDB support to access/display POWER8 registers

Status in The Ubuntu-power-systems project:
  Incomplete
Status in gdb package in Ubuntu:
  Incomplete

Bug description:
  This feature request is for GDB support for access to Power registers
  that are currently not accessible: PPR, DSCR, TAR, EBB, PMU and HTM
  registers.

  The feature is currently being worked on, so no upstream code is
  available yet.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1733870/+subscriptions

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

[Touch-packages] [Bug 433926] Re: xkbcomp error: Type "ONE_LEVEL" has 1 levels, but has 2 symbols

[H.-Dirk Schmitt]

Still in xenial
affected: xkb-data 2.16-1ubuntu1 

│Jan  8 11:49:55 user.warning /usr/lib/gdm3/gdm-x-session[3463 >
Warning:  Type "ONE_LEVEL" has 1 levels, but  has 2 │

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

Title:
  xkbcomp error: Type "ONE_LEVEL" has 1 levels, but  has 2 symbols

Status in xkeyboard-config:
  Confirmed
Status in xkeyboard-config package in Ubuntu:
  Confirmed

Bug description:
  I can confirm that the bug reported upstream is also present in Karmic alpha 
6:
  https://bugs.freedesktop.org/show_bug.cgi?id=21761

  This bug was also reported in gentoo
  http://bugs.gentoo.org/show_bug.cgi?id=269931

  and in debian
  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=291853

  Apparently a fix was released upstream, it would be nice to have it in
  Karmic as well.

  Many thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/433926/+subscriptions

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

[Touch-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

[Norbert]

synaptic confirmed on 18.04.

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

Title:
  Unable to launch pkexec'ed applications on Wayland session

Status in Back In Time:
  Fix Released
Status in Boot-Info:
  Fix Committed
Status in Boot-Repair:
  Fix Committed
Status in GNOME Terminal:
  New
Status in Settings editor for LightDM GTK+ Greeter:
  New
Status in OS-Uninstaller:
  Fix Committed
Status in Y PPA Manager:
  New
Status in apport package in Ubuntu:
  New
Status in apt-offline package in Ubuntu:
  New
Status in backintime package in Ubuntu:
  Confirmed
Status in budgie-welcome package in Ubuntu:
  Invalid
Status in caja-admin package in Ubuntu:
  New
Status in cinnamon package in Ubuntu:
  Invalid
Status in ettercap package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in gdm3 package in Ubuntu:
  Won't Fix
Status in gnunet-gtk package in Ubuntu:
  Confirmed
Status in gparted package in Ubuntu:
  Invalid
Status in gui-ufw package in Ubuntu:
  Confirmed
Status in guidedog package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in italc package in Ubuntu:
  New
Status in laptop-mode-tools package in Ubuntu:
  New
Status in lightdm-gtk-greeter-settings package in Ubuntu:
  Confirmed
Status in nautilus-admin package in Ubuntu:
  New
Status in needrestart-session package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Invalid
Status in scanmem package in Ubuntu:
  New
Status in scap-workbench package in Ubuntu:
  Confirmed
Status in sirikali package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  New
Status in tuned package in Ubuntu:
  New
Status in ubuntustudio-controls package in Ubuntu:
  New
Status in ubuntustudio-default-settings package in Ubuntu:
  Invalid
Status in update-notifier package in Ubuntu:
  New
Status in xdiagnose package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  Invalid
Status in zulucrypt package in Ubuntu:
  Fix Released

Bug description:
  *
  Main upstream discussion & fixes example to deal with wayland:
  https://bugzilla.gnome.org/show_bug.cgi?id=776437
  *

  


  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install backintime-qt4 or gparted application from above list (full may be 
acquired from 
https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1=4
 )
  3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located 
in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec
  ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec
  Exec=pkexec backintime-qt4)
  3b. Try to launch Gparted from shortcut "GParted" (located in 
/usr/share/applications/gparted.desktop, it uses gparted-pkexec)
  4a.1. Back In Time does not start from GUI.
  4a.2. Back In Time shows error message in console:
  4b. gparted-pkexec does not start, reports error
  $ gparted-pkexec
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-121.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-121.mount.
  Removed /run/systemd/system/tmp.mount.

  $ pkexec backintime-qt4

  Back In Time
  Version: 1.1.12

  Back In Time comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to redistribute it
  under certain conditions; type `backintime --license' for details.

  No protocol specified
  app.py: cannot connect to X server :0

  Expected results:
  * backintime-qt4 may be run as root

  Actual results:
  * unable to run backintime-qt4 as root

  Workaround:
  * setting "xhost +si:localuser:root" helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: backintime-qt4 1.1.12-2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Aug 27 14:23:14 2017
  InstallationDate: Installed on 2017-08-26 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  PackageArchitecture: all
  SourcePackage: backintime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Touch-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

[Norbert]

Problem with `nemo` "Open as Root" is confirmed on 18.04.

** Tags added: bionic

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

Title:
  Unable to launch pkexec'ed applications on Wayland session

Status in Back In Time:
  Fix Released
Status in Boot-Info:
  Fix Committed
Status in Boot-Repair:
  Fix Committed
Status in GNOME Terminal:
  New
Status in Settings editor for LightDM GTK+ Greeter:
  New
Status in OS-Uninstaller:
  Fix Committed
Status in Y PPA Manager:
  New
Status in apport package in Ubuntu:
  New
Status in apt-offline package in Ubuntu:
  New
Status in backintime package in Ubuntu:
  Confirmed
Status in budgie-welcome package in Ubuntu:
  Invalid
Status in caja-admin package in Ubuntu:
  New
Status in cinnamon package in Ubuntu:
  Invalid
Status in ettercap package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in gdm3 package in Ubuntu:
  Won't Fix
Status in gnunet-gtk package in Ubuntu:
  Confirmed
Status in gparted package in Ubuntu:
  Invalid
Status in gui-ufw package in Ubuntu:
  Confirmed
Status in guidedog package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in italc package in Ubuntu:
  New
Status in laptop-mode-tools package in Ubuntu:
  New
Status in lightdm-gtk-greeter-settings package in Ubuntu:
  Confirmed
Status in nautilus-admin package in Ubuntu:
  New
Status in needrestart-session package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Invalid
Status in scanmem package in Ubuntu:
  New
Status in scap-workbench package in Ubuntu:
  Confirmed
Status in sirikali package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  New
Status in tuned package in Ubuntu:
  New
Status in ubuntustudio-controls package in Ubuntu:
  New
Status in ubuntustudio-default-settings package in Ubuntu:
  Invalid
Status in update-notifier package in Ubuntu:
  New
Status in xdiagnose package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  Invalid
Status in zulucrypt package in Ubuntu:
  Fix Released

Bug description:
  *
  Main upstream discussion & fixes example to deal with wayland:
  https://bugzilla.gnome.org/show_bug.cgi?id=776437
  *

  


  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install backintime-qt4 or gparted application from above list (full may be 
acquired from 
https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1=4
 )
  3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located 
in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec
  ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec
  Exec=pkexec backintime-qt4)
  3b. Try to launch Gparted from shortcut "GParted" (located in 
/usr/share/applications/gparted.desktop, it uses gparted-pkexec)
  4a.1. Back In Time does not start from GUI.
  4a.2. Back In Time shows error message in console:
  4b. gparted-pkexec does not start, reports error
  $ gparted-pkexec
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-121.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-121.mount.
  Removed /run/systemd/system/tmp.mount.

  $ pkexec backintime-qt4

  Back In Time
  Version: 1.1.12

  Back In Time comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to redistribute it
  under certain conditions; type `backintime --license' for details.

  No protocol specified
  app.py: cannot connect to X server :0

  Expected results:
  * backintime-qt4 may be run as root

  Actual results:
  * unable to run backintime-qt4 as root

  Workaround:
  * setting "xhost +si:localuser:root" helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: backintime-qt4 1.1.12-2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Aug 27 14:23:14 2017
  InstallationDate: Installed on 2017-08-26 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  PackageArchitecture: all
  SourcePackage: backintime
  UpgradeStatus: No upgrade log present (probably fresh install)

To 

[Touch-packages] [Bug 1693464] Re: Bluetooth Audio broken for Bose SoundLink Mini

[Launchpad Bug Tracker]

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

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

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

Title:
  Bluetooth Audio broken for Bose SoundLink Mini

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Bluetooth Audio stopped working when upgrading/clean install of Ubuntu
  17.04. The Bose SoundLink Mini Bluetooth Connection works fine in
  16.04.

  I have tried restarting and re configuring pulseaudio, but nothing seems to 
work.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D8p:   tangarora   2844 F...m pulseaudio
   /dev/snd/controlC1:  tangarora   2844 F pulseaudio
   /dev/snd/controlC2:  tangarora   2844 F pulseaudio
   /dev/snd/controlC0:  tangarora   2844 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-04-27 (140 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: pulseaudio 1:10.0-1ubuntu2 [modified: usr/bin/start-pulseaudio-x11]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Tags:  zesty
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/20/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V8.1
  dmi.board.name: MS-78511
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: 3.1
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV8.1:bd07/20/2015:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-B08911:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-78511:rvr3.1:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
  dmi.product.name: MS-B08911
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD

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

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

[Touch-packages] [Bug 1741172] Re: package apport 2.20.1-0ubuntu2.15 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Launchpad Bug Tracker]

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

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

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

Title:
  package apport 2.20.1-0ubuntu2.15 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  please solve problem

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.15
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CrashReports: 600:0:116:238808:2018-01-04 06:15:17.775570392 +0530:2018-01-04 
06:15:18.775570392 +0530:/var/crash/apport.0.crash
  Date: Thu Jan  4 06:15:18 2018
  DpkgHistoryLog:
   Start-Date: 2018-01-04  06:15:03
   Commandline: /usr/bin/unattended-upgrade
   Upgrade: apport:amd64 (2.20.1-0ubuntu2.14, 2.20.1-0ubuntu2.15), 
python3-apport:amd64 (2.20.1-0ubuntu2.14, 2.20.1-0ubuntu2.15), 
libwebkit2gtk-4.0-37:amd64 (2.18.3-0ubuntu0.16.04.1, 2.18.4-0ubuntu0.16.04.1), 
apport-gtk:amd64 (2.20.1-0ubuntu2.14, 2.20.1-0ubuntu2.15), 
gir1.2-webkit2-4.0:amd64 (2.18.3-0ubuntu0.16.04.1, 2.18.4-0ubuntu0.16.04.1), 
libjavascriptcoregtk-4.0-18:amd64 (2.18.3-0ubuntu0.16.04.1, 
2.18.4-0ubuntu0.16.04.1), python3-problem-report:amd64 (2.20.1-0ubuntu2.14, 
2.20.1-0ubuntu2.15), libwebkit2gtk-4.0-37-gtk2:amd64 (2.18.3-0ubuntu0.16.04.1, 
2.18.4-0ubuntu0.16.04.1), gir1.2-javascriptcoregtk-4.0:amd64 
(2.18.3-0ubuntu0.16.04.1, 2.18.4-0ubuntu0.16.04.1)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-01-25 (343 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.15 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1692111] Re: Unable to configure raw.id_map with multiple entries

[Stéphane Graber]

I think we have that fix in liblxc 2.0.9 which still needs SRUing to the
various Ubuntu stable releases.

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

Title:
  Unable to configure raw.id_map with multiple entries

Status in lxc package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Invalid

Bug description:
  I am trying to map two users (999, 1001) to one of my containers. I
  added both IDs to /etc/subgid and /etc/subuid. I followed by setting
  raw.id_map property value (as instructed here
  https://lists.linuxcontainers.org/pipermail/lxc-
  users/2017-March/013034.html):

  "echo -e "both 999 999\nboth 1001 1001" |  lxc config set mycontainer
  raw.idmap -"

  However upon starting the container, I get errors (log excerpt below).
  If, on the other hand, I set idmap to either "both 999 999" or "both
  1001 1001" only - i.e. if I map only one user at the time, the
  container starts just fine and the user is mapped as expected.

  My subgid and subuid look as follows:

  lxd:10:65536
  root:10:65536
  root:1001:1
  root:999:1

  Log excerpt:

  Name: mycontainer
  Remote: unix:/var/lib/lxd/unix.socket
  Architecture: x86_64
  Created: 2017/02/22 18:54 UTC
  Status: Stopped
  Type: persistent
  Profiles: default

  Log:

  lxc 20170519204102.895 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer" already existed.
  lxc 20170519204102.896 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to 
create /sys/fs/cgroup/systemd//lxc/mycontainer: No such file or directory
  lxc 20170519204102.897 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer-1" already existed.
  lxc 20170519204102.897 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to 
create /sys/fs/cgroup/systemd//lxc/mycontainer-1: No such file or directory
  lxc 20170519204102.897 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer-2" already existed.
  lxc 20170519204102.898 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to 
create /sys/fs/cgroup/systemd//lxc/mycontainer-2: No such file or directory
  lxc 20170519204102.898 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer-3" already existed.
  lxc 20170519204102.898 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to 
create /sys/fs/cgroup/systemd//lxc/mycontainer-3: No such file or directory
  lxc 20170519204102.898 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer-4" already existed.
  lxc 20170519204102.898 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to 
create /sys/fs/cgroup/systemd//lxc/mycontainer-4: No such file or directory
  lxc 20170519204102.899 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer-5" already existed.
  lxc 20170519204102.899 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to 
create /sys/fs/cgroup/systemd//lxc/mycontainer-5: No such file or directory
  lxc 20170519204102.899 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer-6" already existed.
  lxc 20170519204102.899 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to 
create /sys/fs/cgroup/systemd//lxc/mycontainer-6: No such file or directory
  lxc 20170519204102.900 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer-7" already existed.
  lxc 20170519204102.900 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to 
create /sys/fs/cgroup/systemd//lxc/mycontainer-7: No such file or directory
  lxc 20170519204102.900 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer-8" already existed.
  lxc 20170519204102.900 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to 
create /sys/fs/cgroup/systemd//lxc/mycontainer-8: No such file or directory
  lxc 20170519204102.901 ERRORlxc_cgfsng - 

[Touch-packages] [Bug 1741563] Re: initramfs compression changed in bionic for shipped kernel

[Robert C Jennings]

My understanding had been incorrect and this is not an issue in this
package at all.  The initramfs present in the cloud-image at first boot
is created by live-build with lzma compression.  Subsequent kernel
installs that produce a new initramfs or updates to an existing
initramfs will be compressed with the default gzip compression per the
shipped default in initramfs-tools.  This mismatch is due to live-build
invocation and not this package.  Marking invalid.

** Changed in: initramfs-tools (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  initramfs compression changed in bionic for shipped kernel

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  The shipped initrd doesn't match the compression that you'd get if you
  update the initrd on bionic:

  # A clean bionic cloud-image
  $ file /boot/initrd.img-4.13.0-17-generic
  /boot/initrd.img-4.13.0-17-generic: LZMA compressed data, streamed

  # Update the initramfs (notice the deprecation warnings too)
  $ sudo update-initramfs -k all -u
  update-initramfs: Generating /boot/initrd.img-4.13.0-17-generic
  WARNING: Setting CRYPTSETUP in /etc/initramfs-tools/initramfs.conf is 
deprecated and will stop working in the future. Use 
/etc/cryptsetup-initramfs/conf-hook instead.

  # Now initramfs is gzip compressed when packaged initramfs was LZMA
  $ file /boot/initrd.img-4.13.0-17-generic
  /boot/initrd.img-4.13.0-17-generic: gzip compressed data, last modified: Fri 
Jan 5 20:54:07 2018, from Unix

  $ apt-cache policy initramfs-tools
  initramfs-tools:
Installed: 0.125ubuntu13
Candidate: 0.125ubuntu13
Version table:
   *** 0.125ubuntu13 500
  500 http://us-west-2.ec2.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/initramfs-tools/+bug/1741563/+subscriptions

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

[Touch-packages] [Bug 1742202] [NEW] apport sends crashfiles to nirvana

[Majestyx]

Public bug reported:

apport came up whit a crash notice, klick on: submit the bug  
nothing happens (more)

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: apport 2.20.7-0ubuntu3.7
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
ApportLog:
 ERROR: apport (pid 1452) Tue Jan  9 18:08:24 2018: called for pid 1449, signal 
6, core limit 0, dump mode 1
 ERROR: apport (pid 1452) Tue Jan  9 18:08:24 2018: executable: 
/usr/lib/android-sdk/platform-tools/adb (command line "adb -P 5037 fork-server 
server --reply-fd 4")
 ERROR: apport (pid 1452) Tue Jan  9 18:08:24 2018: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
 ERROR: apport (pid 1452) Tue Jan  9 18:08:24 2018: wrote report 
/var/crash/_usr_lib_android-sdk_platform-tools_adb.0.crash
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CrashReports:
 600:113:121:0:2018-01-09 18:10:13.071120741 +0100:2018-01-06 
18:08:50.832819680 
+0100:/var/crash/_usr_lib_android-sdk_platform-tools_adb.0.uploaded
 644:0:121:0:2018-01-09 18:10:12.011104680 +0100:2018-01-09 18:10:12.011104680 
+0100:/var/crash/_usr_lib_android-sdk_platform-tools_adb.0.upload
 640:0:121:212568:2018-01-09 18:10:00.466965198 +0100:2018-01-09 
18:10:01.466965198 
+0100:/var/crash/_usr_lib_android-sdk_platform-tools_adb.0.crash
CurrentDesktop: XFCE
Date: Tue Jan  9 18:15:31 2018
InstallationDate: Installed on 2017-12-10 (30 days ago)
InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=de_DE
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful

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

Title:
  apport sends crashfiles to nirvana

Status in apport package in Ubuntu:
  New

Bug description:
  apport came up whit a crash notice, klick on: submit the bug  
  nothing happens (more)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apport 2.20.7-0ubuntu3.7
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportLog:
   ERROR: apport (pid 1452) Tue Jan  9 18:08:24 2018: called for pid 1449, 
signal 6, core limit 0, dump mode 1
   ERROR: apport (pid 1452) Tue Jan  9 18:08:24 2018: executable: 
/usr/lib/android-sdk/platform-tools/adb (command line "adb -P 5037 fork-server 
server --reply-fd 4")
   ERROR: apport (pid 1452) Tue Jan  9 18:08:24 2018: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
   ERROR: apport (pid 1452) Tue Jan  9 18:08:24 2018: wrote report 
/var/crash/_usr_lib_android-sdk_platform-tools_adb.0.crash
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CrashReports:
   600:113:121:0:2018-01-09 18:10:13.071120741 +0100:2018-01-06 
18:08:50.832819680 
+0100:/var/crash/_usr_lib_android-sdk_platform-tools_adb.0.uploaded
   644:0:121:0:2018-01-09 18:10:12.011104680 +0100:2018-01-09 
18:10:12.011104680 
+0100:/var/crash/_usr_lib_android-sdk_platform-tools_adb.0.upload
   640:0:121:212568:2018-01-09 18:10:00.466965198 +0100:2018-01-09 
18:10:01.466965198 
+0100:/var/crash/_usr_lib_android-sdk_platform-tools_adb.0.crash
  CurrentDesktop: XFCE
  Date: Tue Jan  9 18:15:31 2018
  InstallationDate: Installed on 2017-12-10 (30 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  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/1742202/+subscriptions

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

[Touch-packages] [Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system

[ryan eckenrode]

I want to confirm that changing 'force' to 'auto' for the last entry in
/lib/udev/rules.d/99-laptop-mode.rules did allow me to boot
successfully.

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

Title:
  System fails to start (boot) on battery due to read-only root file-
  system

Status in laptop-mode-tools package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd package in Debian:
  Fix Released

Bug description:
  This report is to capture the extended diagnostic efforts done on IRC
  #ubuntu for user maszlo, who has a Lenovo T450 with SSD that was
  upgraded from 17.04 to 17.10 and since fails to complete start-up of
  services when powered on battery.

  We'd previously applied the "acpi=os=! 'acpi_osi=Windows 2015'"
  workaround in case this was an ACPI DSDT issue.

  This appears to be due to a read-only root file-system. What is not
  clear is how the rootfs goes read-only.

  The file-system (sda6, ext4) is fsck-ed successfully in the initrd
  according to the /run/initramfs/fsck.log.

  From the start-up logs (with "systemd.log_level=debug") we see the
  ext4 driver report a remount operation not once but five times.

  $ grep 'EXT4-fs.*sda6' systemd-debug.log
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): mounted filesystem with ordered 
data mode. Opts: (null)
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro
  Oct 23 18:10:46 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:47 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:49 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600

  Those last five appear to be carrying options generated by laptop-
  mode-tools.

  User has disabled laptop-mode.service and laptop-mode.timer, and lmt-
  poll.service, but the issue remains.

  We see several reports of "read-only file-system":

  $ grep 'Read-only' systemd-debug.log
  Oct 23 18:10:46 T450s grub-common[1792]: grub-editenv: error: cannot open 
`/boot/grub/grubenv': Read-only file system.
  Oct 23 18:10:46 T450s systemd[1]: colord.service: Failed to run 'start' task: 
Read-only file system
  Oct 23 18:10:46 T450s gpu-manager[1797]: Warning: writing to 
/var/log/gpu-manager.log failed (Read-only file system)
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s gdm3[1932]: Failed to create LogDir /var/log/gdm3: 
Read-only file system
  ...
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to change ownership of 
"/var/log/cups" - Read-only file system
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to open log file 
"/var/log/cups/access_log" - Read-only file system
  Oct 23 18:12:52 T450s login[9248]: pam_lastlog(login:session): unable to open 
/var/log/lastlog: Read-only file system

  We also see several problems with systemd's connection to Dbus:

  $ grep 'Transport endpoint' systemd-debug.log
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: systemd-logind.service: Failed to send unit 
change signal for systemd-logind.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 156: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: lmt-poll.service: Failed to send unit 
change signal for lmt-poll.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 182: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 95: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: polkit.service: Failed to send unit change 
signal for polkit.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: cups-browsed.service: Failed to send unit 
change signal for cups-browsed.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 161: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: gdomap.service: Failed to send unit change 
signal for gdomap.service: Transport endpoint is not connected

  When the user purged laptop-mode-tools 

[Touch-packages] [Bug 1725333] Re: do-release-upgrade broke WSL

[Peter Würtz]

This issue was also reported at the WSL GitHub project:
https://github.com/Microsoft/WSL/issues/2615

The reason seems to be a bug in glibc that has been fixed a few months ago:
https://sourceware.org/bugzilla/show_bug.cgi?id=22273

To fix this we need this patch for glibc in 17.10.

** Bug watch added: github.com/Microsoft/WSL/issues #2615
   https://github.com/Microsoft/WSL/issues/2615

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

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

Title:
  do-release-upgrade broke WSL

Status in GLibC:
  Unknown
Status in Gnu Bash:
  Fix Released
Status in bash package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  New

Bug description:
  I had Ubuntu 17.04 installed in WSL and decided to upgrade it to
  17.10, so I had run do-release-upgrade, as I did before to upgrade to
  17.04. Everything was fine before script started upgrading packages.
  It's started from bash updating, and somehow there is a problem
  revealed that locale files is missing, and locale-gen can't be run
  (because of bug in WSL). I've tried to install language-pack-en as was
  suggested, but problem haven't resolved, any attempt to update leads
  to this error.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: bash 4.4-2ubuntu1.1
  ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
  Uname: Linux 4.4.0-43-Microsoft x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Fri Oct 20 18:03:30 2017
  Dmesg:
   
  DpkgTerminalLog:
   Preparing to unpack .../bash_4.4-5ubuntu1_amd64.deb ...
   preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec 
>= 0' failed.
   dpkg: error processing archive 
/var/cache/apt/archives/bash_4.4-5ubuntu1_amd64.deb (--unpack):
subprocess new pre-installation script was killed by signal (Aborted), core 
dumped
  DuplicateSignature:
   package:bash:4.4-2ubuntu1.1
   Preparing to unpack .../bash_4.4-5ubuntu1_amd64.deb ...
   preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec 
>= 0' failed.
   dpkg: error processing archive 
/var/cache/apt/archives/bash_4.4-5ubuntu1_amd64.deb (--unpack):
subprocess new pre-installation script was killed by signal (Aborted), core 
dumped
  ErrorMessage: subprocess new pre-installation script was killed by signal 
(Aborted), core dumped
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4.6~17.04.1
  SourcePackage: bash
  Title: package bash 4.4-2ubuntu1.1 failed to install/upgrade: subprocess new 
pre-installation script was killed by signal (Aborted), core dumped
  UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago)

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

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

[Touch-packages] [Bug 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04

[laurel]

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

I'm a newbie and after updating Ubuntu 16.04 on Jan 5, 2018, I
experienced launcher disappearing when running over with mouse, windows
disappearing and appearing, Dash not working and cannot shutdown.  I get
Internal Error Message: compiz crashed with SIGSERV.  The error report
incorrectly prints that I have amd64 architecture and that I have Ubuntu
16.04.2 LTS Release amd64 (20170215.2) when I have Ubuntu 16.04.3  This
result seems not to have been commented on in the previous bug #1735594.

I'm working on a Toshiba Satellite M645 laptop (2011) with an Intel Core
i5 CPU, 64 bit OS and graphics is Intel Ironlake Mobile.

I'm afraid to try the ppa:paulo-miguel-dias/pkppa suggestion because I
am so new to this.  I installed  August 2017 and had no problems until
Jan 5, 2018 when using the Software Updater.

The good news is: I learned to use terminal commands and can access all
the browsers, word processors, files, etc. that I have on my machine so
I'm not down just inconvenienced. 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/1741447

Title:
  Unity / Compiz in a crash loop after login, after mesa updates of
  2018-01-04

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Xenial:
  Confirmed
Status in mesa source package in Artful:
  Confirmed

Bug description:
  GUI is constantly crashing, can't start desktop

  Jan  5 11:21:29 1810 kernel: [  806.368754] compiz[10824]: segfault at 0 ip 
7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000]
  Jan  5 11:21:40 1810 kernel: [  817.279740] compiz[1]: segfault at 0 ip 
7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000]
  Jan  5 11:22:30 1810 kernel: [  867.445137] compiz[11271]: segfault at 0 ip 
7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000]
  Jan  5 11:22:46 1810 kernel: [  883.319195] compiz[11458]: segfault at 0 ip 
7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000]
  Jan  5 11:23:01 1810 kernel: [  898.587610] compiz[11516]: segfault at 0 ip 
7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000]

  In /var/crash:
  _usr_bin_compiz.999.crash

  Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not 
really usable.
  - dash not working
  - no window switching
  - sometimes all windows disappear for a few seconds

  So effectively my laptop is not usable after latest updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160906-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  .tmp.unity_support_test.0:

  .tmp.unity_support_test.1:

  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Jan  5 11:16:53 2018
  DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:029b]
     Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:029b]
  InstallationDate: Installed on 2014-04-18 (1357 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Acer Aspire 1810TZ
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic 
root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago)
  dmi.bios.date: 08/31/2010
  dmi.bios.vendor: INSYDE
  dmi.bios.version: v1.3314
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JM11-MS
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: Aspire 1810TZ
  dmi.product.version: v1.3314
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  

[Touch-packages] [Bug 1725333] Re: do-release-upgrade broke WSL

[Peter Würtz]

** Bug watch added: Sourceware.org Bugzilla #22273
   https://sourceware.org/bugzilla/show_bug.cgi?id=22273

** Also affects: glibc via
   https://sourceware.org/bugzilla/show_bug.cgi?id=22273
   Importance: Unknown
   Status: Unknown

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

Title:
  do-release-upgrade broke WSL

Status in GLibC:
  Unknown
Status in Gnu Bash:
  Fix Released
Status in bash package in Ubuntu:
  Confirmed

Bug description:
  I had Ubuntu 17.04 installed in WSL and decided to upgrade it to
  17.10, so I had run do-release-upgrade, as I did before to upgrade to
  17.04. Everything was fine before script started upgrading packages.
  It's started from bash updating, and somehow there is a problem
  revealed that locale files is missing, and locale-gen can't be run
  (because of bug in WSL). I've tried to install language-pack-en as was
  suggested, but problem haven't resolved, any attempt to update leads
  to this error.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: bash 4.4-2ubuntu1.1
  ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
  Uname: Linux 4.4.0-43-Microsoft x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Fri Oct 20 18:03:30 2017
  Dmesg:
   
  DpkgTerminalLog:
   Preparing to unpack .../bash_4.4-5ubuntu1_amd64.deb ...
   preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec 
>= 0' failed.
   dpkg: error processing archive 
/var/cache/apt/archives/bash_4.4-5ubuntu1_amd64.deb (--unpack):
subprocess new pre-installation script was killed by signal (Aborted), core 
dumped
  DuplicateSignature:
   package:bash:4.4-2ubuntu1.1
   Preparing to unpack .../bash_4.4-5ubuntu1_amd64.deb ...
   preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec 
>= 0' failed.
   dpkg: error processing archive 
/var/cache/apt/archives/bash_4.4-5ubuntu1_amd64.deb (--unpack):
subprocess new pre-installation script was killed by signal (Aborted), core 
dumped
  ErrorMessage: subprocess new pre-installation script was killed by signal 
(Aborted), core dumped
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4.6~17.04.1
  SourcePackage: bash
  Title: package bash 4.4-2ubuntu1.1 failed to install/upgrade: subprocess new 
pre-installation script was killed by signal (Aborted), core dumped
  UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago)

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

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

[Touch-packages] [Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system

[Ritesh Raj Sarraf]

This would still be a flaky device or a kernel bug. Because the
mentioned laptop-mode-tools version (1.71) brought in forced execution
mode, so that it could apply proper power saving values. That's pretty
much it. That does not result in read only rootfs because if it
logically did, it'd be seen on every machine.

BTW, does Ubuntu have the systemd/udevd mount propagation fix included ?

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

Title:
  System fails to start (boot) on battery due to read-only root file-
  system

Status in laptop-mode-tools package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd package in Debian:
  Fix Released

Bug description:
  This report is to capture the extended diagnostic efforts done on IRC
  #ubuntu for user maszlo, who has a Lenovo T450 with SSD that was
  upgraded from 17.04 to 17.10 and since fails to complete start-up of
  services when powered on battery.

  We'd previously applied the "acpi=os=! 'acpi_osi=Windows 2015'"
  workaround in case this was an ACPI DSDT issue.

  This appears to be due to a read-only root file-system. What is not
  clear is how the rootfs goes read-only.

  The file-system (sda6, ext4) is fsck-ed successfully in the initrd
  according to the /run/initramfs/fsck.log.

  From the start-up logs (with "systemd.log_level=debug") we see the
  ext4 driver report a remount operation not once but five times.

  $ grep 'EXT4-fs.*sda6' systemd-debug.log
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): mounted filesystem with ordered 
data mode. Opts: (null)
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro
  Oct 23 18:10:46 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:47 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:49 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600

  Those last five appear to be carrying options generated by laptop-
  mode-tools.

  User has disabled laptop-mode.service and laptop-mode.timer, and lmt-
  poll.service, but the issue remains.

  We see several reports of "read-only file-system":

  $ grep 'Read-only' systemd-debug.log
  Oct 23 18:10:46 T450s grub-common[1792]: grub-editenv: error: cannot open 
`/boot/grub/grubenv': Read-only file system.
  Oct 23 18:10:46 T450s systemd[1]: colord.service: Failed to run 'start' task: 
Read-only file system
  Oct 23 18:10:46 T450s gpu-manager[1797]: Warning: writing to 
/var/log/gpu-manager.log failed (Read-only file system)
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s gdm3[1932]: Failed to create LogDir /var/log/gdm3: 
Read-only file system
  ...
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to change ownership of 
"/var/log/cups" - Read-only file system
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to open log file 
"/var/log/cups/access_log" - Read-only file system
  Oct 23 18:12:52 T450s login[9248]: pam_lastlog(login:session): unable to open 
/var/log/lastlog: Read-only file system

  We also see several problems with systemd's connection to Dbus:

  $ grep 'Transport endpoint' systemd-debug.log
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: systemd-logind.service: Failed to send unit 
change signal for systemd-logind.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 156: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: lmt-poll.service: Failed to send unit 
change signal for lmt-poll.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 182: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 95: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: polkit.service: Failed to send unit change 
signal for polkit.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: cups-browsed.service: Failed to send unit 
change signal for cups-browsed.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job 

[Touch-packages] [Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system

[Ritesh Raj Sarraf]

Folks...

Does changing to following in /lib/udev/rules.d/99-laptop-mode.rules
help ?

ACTION=="add", SUBSYSTEM=="usb", RUN+="lmt-udev auto"

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

Title:
  System fails to start (boot) on battery due to read-only root file-
  system

Status in laptop-mode-tools package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd package in Debian:
  Fix Released

Bug description:
  This report is to capture the extended diagnostic efforts done on IRC
  #ubuntu for user maszlo, who has a Lenovo T450 with SSD that was
  upgraded from 17.04 to 17.10 and since fails to complete start-up of
  services when powered on battery.

  We'd previously applied the "acpi=os=! 'acpi_osi=Windows 2015'"
  workaround in case this was an ACPI DSDT issue.

  This appears to be due to a read-only root file-system. What is not
  clear is how the rootfs goes read-only.

  The file-system (sda6, ext4) is fsck-ed successfully in the initrd
  according to the /run/initramfs/fsck.log.

  From the start-up logs (with "systemd.log_level=debug") we see the
  ext4 driver report a remount operation not once but five times.

  $ grep 'EXT4-fs.*sda6' systemd-debug.log
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): mounted filesystem with ordered 
data mode. Opts: (null)
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro
  Oct 23 18:10:46 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:47 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:49 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600

  Those last five appear to be carrying options generated by laptop-
  mode-tools.

  User has disabled laptop-mode.service and laptop-mode.timer, and lmt-
  poll.service, but the issue remains.

  We see several reports of "read-only file-system":

  $ grep 'Read-only' systemd-debug.log
  Oct 23 18:10:46 T450s grub-common[1792]: grub-editenv: error: cannot open 
`/boot/grub/grubenv': Read-only file system.
  Oct 23 18:10:46 T450s systemd[1]: colord.service: Failed to run 'start' task: 
Read-only file system
  Oct 23 18:10:46 T450s gpu-manager[1797]: Warning: writing to 
/var/log/gpu-manager.log failed (Read-only file system)
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s gdm3[1932]: Failed to create LogDir /var/log/gdm3: 
Read-only file system
  ...
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to change ownership of 
"/var/log/cups" - Read-only file system
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to open log file 
"/var/log/cups/access_log" - Read-only file system
  Oct 23 18:12:52 T450s login[9248]: pam_lastlog(login:session): unable to open 
/var/log/lastlog: Read-only file system

  We also see several problems with systemd's connection to Dbus:

  $ grep 'Transport endpoint' systemd-debug.log
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: systemd-logind.service: Failed to send unit 
change signal for systemd-logind.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 156: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: lmt-poll.service: Failed to send unit 
change signal for lmt-poll.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 182: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 95: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: polkit.service: Failed to send unit change 
signal for polkit.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: cups-browsed.service: Failed to send unit 
change signal for cups-browsed.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 161: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: gdomap.service: Failed to send unit change 
signal for gdomap.service: Transport endpoint is not connected

  When the user purged laptop-mode-tools the 

[Touch-packages] [Bug 1692111] Re: Unable to configure raw.id_map with multiple entries

[Dawid Wróbel]

Is there any chance this can get backported to Xenial? I can see this
fix was included in 2.1.0-0ubuntu1, but the LTS package is still at
2.0.8-0ubuntu1~16.04.2.

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

Title:
  Unable to configure raw.id_map with multiple entries

Status in lxc package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Invalid

Bug description:
  I am trying to map two users (999, 1001) to one of my containers. I
  added both IDs to /etc/subgid and /etc/subuid. I followed by setting
  raw.id_map property value (as instructed here
  https://lists.linuxcontainers.org/pipermail/lxc-
  users/2017-March/013034.html):

  "echo -e "both 999 999\nboth 1001 1001" |  lxc config set mycontainer
  raw.idmap -"

  However upon starting the container, I get errors (log excerpt below).
  If, on the other hand, I set idmap to either "both 999 999" or "both
  1001 1001" only - i.e. if I map only one user at the time, the
  container starts just fine and the user is mapped as expected.

  My subgid and subuid look as follows:

  lxd:10:65536
  root:10:65536
  root:1001:1
  root:999:1

  Log excerpt:

  Name: mycontainer
  Remote: unix:/var/lib/lxd/unix.socket
  Architecture: x86_64
  Created: 2017/02/22 18:54 UTC
  Status: Stopped
  Type: persistent
  Profiles: default

  Log:

  lxc 20170519204102.895 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer" already existed.
  lxc 20170519204102.896 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to 
create /sys/fs/cgroup/systemd//lxc/mycontainer: No such file or directory
  lxc 20170519204102.897 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer-1" already existed.
  lxc 20170519204102.897 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to 
create /sys/fs/cgroup/systemd//lxc/mycontainer-1: No such file or directory
  lxc 20170519204102.897 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer-2" already existed.
  lxc 20170519204102.898 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to 
create /sys/fs/cgroup/systemd//lxc/mycontainer-2: No such file or directory
  lxc 20170519204102.898 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer-3" already existed.
  lxc 20170519204102.898 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to 
create /sys/fs/cgroup/systemd//lxc/mycontainer-3: No such file or directory
  lxc 20170519204102.898 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer-4" already existed.
  lxc 20170519204102.898 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to 
create /sys/fs/cgroup/systemd//lxc/mycontainer-4: No such file or directory
  lxc 20170519204102.899 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer-5" already existed.
  lxc 20170519204102.899 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to 
create /sys/fs/cgroup/systemd//lxc/mycontainer-5: No such file or directory
  lxc 20170519204102.899 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer-6" already existed.
  lxc 20170519204102.899 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to 
create /sys/fs/cgroup/systemd//lxc/mycontainer-6: No such file or directory
  lxc 20170519204102.900 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer-7" already existed.
  lxc 20170519204102.900 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to 
create /sys/fs/cgroup/systemd//lxc/mycontainer-7: No such file or directory
  lxc 20170519204102.900 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer-8" already existed.
  lxc 20170519204102.900 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to 
create /sys/fs/cgroup/systemd//lxc/mycontainer-8: No such file or directory
  lxc 20170519204102.901 

Re: [Touch-packages] [Bug 1735160] Re: [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from bionic

[Andrea Azzarone]

"snapcraft login" seems to work fine here.

On Tue, Jan 9, 2018 at 4:02 PM, Colin Watson 
wrote:

> pymacaroons does have one potentially-interesting backward-incompatible
> change, which is that Caveat.caveat_id and Macaroon.identifier are now
> bytes rather than str.  I think the only place this is at all likely to
> cause a problem in xenial is in snapcraft, and it's definitely worth
> checking whether "snapcraft login" still works.
>
> The py-macaroon-bakery change looks OK-ish, as long as (obviously)
> somebody confirms that it's wire-compatible with the servers this is
> intended to talk to.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1735160
>
> Title:
>   [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from
>   bionic
>
> Status in httmock package in Ubuntu:
>   Fix Released
> Status in protobuf package in Ubuntu:
>   New
> Status in pymacaroons package in Ubuntu:
>   New
> Status in python-nacl package in Ubuntu:
>   New
> Status in httmock source package in Xenial:
>   In Progress
> Status in protobuf source package in Xenial:
>   New
> Status in pymacaroons source package in Xenial:
>   New
> Status in python-nacl source package in Xenial:
>   New
>
> Bug description:
>   [Impact]
>   As part of allowing Ubuntu users to enable canonical-livepatch from
> software-properties GUI (https://wiki.ubuntu.com/SoftwareUpdates#Update_
> settings) we need to backport python3-macaroonbakery 0.0.6-1 [universe]
> from bionic. This will requires quite few changes:
>
>   - backport httmock 1.2.6-1 [universe] from bionic - no httmock in xenial
>   - backport pymacaroons 0.12.0-1 [universe] from bionic - xenial has
> 0.9.2-0ubuntu1
>   - SRU some changes in google-apputils-python -
> https://bugs.launchpad.net/ubuntu/+source/google-
> apputils-python/+bug/1735162
>   - add python3-protobuf to python-protobuf 2.6.1-1.3 - Right now the
> python3 package is not built.
>
>   [Test case]
>   - for python3-protobuf: $ python3 -c "import google.protobuf"
>   - for python3-macaroonbakery: make sure all the tests pass
>
>   [Regression Potential]
>   - httmock, none has it's not in xenial
>   - python3-protobuf, none has the python2 code was not edited
>   TBC
>   - pymacaroons, none has 0.12 is backward compatible with 0.9.2
>   - python3-protobuf, none has it's not in xenial.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/httmock/+bug/
> 1735160/+subscriptions
>
> Launchpad-Notification-Type: bug
> Launchpad-Bug: distribution=ubuntu; sourcepackage=httmock;
> component=universe; status=Fix Released; importance=Undecided; assignee=
> andrea.azzar...@canonical.com;
> Launchpad-Bug: distribution=ubuntu; sourcepackage=protobuf;
> component=main; status=New; importance=Undecided; assignee=None;
> Launchpad-Bug: distribution=ubuntu; sourcepackage=pymacaroons;
> component=universe; status=New; importance=Undecided; assignee=None;
> Launchpad-Bug: distribution=ubuntu; sourcepackage=python-nacl;
> component=universe; status=New; importance=Undecided; assignee=None;
> Launchpad-Bug: distribution=ubuntu; distroseries=xenial;
> sourcepackage=httmock; component=None; status=In Progress;
> importance=Undecided; assignee=andrea.azzar...@canonical.com;
> Launchpad-Bug: distribution=ubuntu; distroseries=xenial;
> sourcepackage=protobuf; component=main; status=New; importance=Undecided;
> assignee=None;
> Launchpad-Bug: distribution=ubuntu; distroseries=xenial;
> sourcepackage=pymacaroons; component=universe; status=New;
> importance=Undecided; assignee=None;
> Launchpad-Bug: distribution=ubuntu; distroseries=xenial;
> sourcepackage=python-nacl; component=universe; status=New;
> importance=Undecided; assignee=None;
> Launchpad-Bug-Tags: patch
> Launchpad-Bug-Information-Type: Public
> Launchpad-Bug-Private: no
> Launchpad-Bug-Security-Vulnerability: no
> Launchpad-Bug-Commenters: azzar1 cjwatson crichton laney tsimonq2
> Launchpad-Bug-Reporter: Andrea Azzarone (azzar1)
> Launchpad-Bug-Modifier: Colin Watson (cjwatson)
> Launchpad-Message-Rationale: Subscriber
> Launchpad-Message-For: azzar1
>

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

Title:
  [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from
  bionic

Status in httmock package in Ubuntu:
  Fix Released
Status in protobuf package in Ubuntu:
  New
Status in pymacaroons package in Ubuntu:
  New
Status in python-nacl package in Ubuntu:
  New
Status in httmock source package in Xenial:
  In Progress
Status in protobuf source package in Xenial:
  New
Status in pymacaroons source package in Xenial:
  New
Status in python-nacl source package in Xenial:
  New

Bug description:
  [Impact]
  As part of allowing Ubuntu users to enable canonical-livepatch from 

Re: [Touch-packages] [Bug 1735160] Re: [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from bionic

[Andrea Azzarone]

On Tue, Jan 9, 2018 at 12:38 PM, Iain Lane 
wrote:

> Andy asked me to have a look, so here's my initial feedback.
>
> General
> ===
>
> I'm not sure if these changes should be backported to Artful too, to
> maintain the upgrade path for users transitioning off Xenial. Could you
> please ask the SRU team?
>

At least for our usecase there is no need to backport this to Artful. Who
should I ask?


>
> Otherwise, the changes are risky but I think they should be in principle
> okay.
>
> The test cases and regression potential in the description here could do
> with fleshing out a bit - could you do that please? For example,
> snapcraft depends on pymacaroons - probably want to make sure that keeps
> working. And it is supposed to be compatible, but that doesn't mean
> there is no bug in the newer version - it is a regression potential IMO.
>

I tested snapcraft-login as in above question.


>
> httmock
> ===
>
> Since this is completely new and a no-change backport, I think it's
> okay. Uploaded.
>
> protobuf
> 
>
> I'm a bit worried about bugs coming from the use of 2to3 which is best
> used as a starting point for a manual port, not for an automatic
> conversion - how about taking the upstream patches instead?
>
> https://github.com/google/protobuf/commit/f336d4b7a5c1d369ed508e513d482c
> 885705e939
>
> https://github.com/google/protobuf/commit/fe7d9379df3ce7c951bc0652a45141
> 3cff02382a
>
> https://github.com/google/protobuf/commit/47ee4d37c17db8e97fe5b15cf918ab
> 56ff93bb18
>
> I tried the testsuite with this and it works after resolving some minor
> conflicts.
>

I'll take a look into it.


>
> pymacaroons
> ===
>
> Seems okay if it's compatible - can you check with Colin please? I'm
> happy to handle the actual upload.
>
> py-macaroon-bakery
> ==
>
> I'm not qualified to review this - maybe also check with Colin as the
> maintainer? The patch says it's editing a generated file - is that
> right?
>

It's editing the protobuf generated file. It seems like these changes are
wire-compatible with the livepatch servers".


>
> ** Changed in: httmock (Ubuntu)
>Status: New => In Progress
>
> ** Changed in: httmock (Ubuntu)
>  Assignee: (unassigned) => Andrea Azzarone (azzar1)
>
> ** Also affects: protobuf (Ubuntu Xenial)
>Importance: Undecided
>Status: New
>
> ** Also affects: python-nacl (Ubuntu Xenial)
>Importance: Undecided
>Status: New
>
> ** Also affects: pymacaroons (Ubuntu Xenial)
>Importance: Undecided
>Status: New
>
> ** Also affects: httmock (Ubuntu Xenial)
>Importance: Undecided
>Status: New
>
> ** Changed in: httmock (Ubuntu)
>Status: In Progress => Fix Released
>
> ** Changed in: httmock (Ubuntu Xenial)
>Status: New => In Progress
>
> ** Changed in: httmock (Ubuntu Xenial)
>  Assignee: (unassigned) => Andrea Azzarone (azzar1)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1735160
>
> Title:
>   [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from
>   bionic
>
> Status in httmock package in Ubuntu:
>   Fix Released
> Status in protobuf package in Ubuntu:
>   New
> Status in pymacaroons package in Ubuntu:
>   New
> Status in python-nacl package in Ubuntu:
>   New
> Status in httmock source package in Xenial:
>   In Progress
> Status in protobuf source package in Xenial:
>   New
> Status in pymacaroons source package in Xenial:
>   New
> Status in python-nacl source package in Xenial:
>   New
>
> Bug description:
>   [Impact]
>   As part of allowing Ubuntu users to enable canonical-livepatch from
> software-properties GUI (https://wiki.ubuntu.com/SoftwareUpdates#Update_
> settings) we need to backport python3-macaroonbakery 0.0.6-1 [universe]
> from bionic. This will requires quite few changes:
>
>   - backport httmock 1.2.6-1 [universe] from bionic - no httmock in xenial
>   - backport pymacaroons 0.12.0-1 [universe] from bionic - xenial has
> 0.9.2-0ubuntu1
>   - SRU some changes in google-apputils-python -
> https://bugs.launchpad.net/ubuntu/+source/google-
> apputils-python/+bug/1735162
>   - add python3-protobuf to python-protobuf 2.6.1-1.3 - Right now the
> python3 package is not built.
>
>   [Test case]
>   - for python3-protobuf: $ python3 -c "import google.protobuf"
>   - for python3-macaroonbakery: make sure all the tests pass
>
>   [Regression Potential]
>   - httmock, none has it's not in xenial
>   - python3-protobuf, none has the python2 code was not edited
>   TBC
>   - pymacaroons, none has 0.12 is backward compatible with 0.9.2
>   - python3-protobuf, none has it's not in xenial.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/httmock/+bug/
> 1735160/+subscriptions
>
> Launchpad-Notification-Type: bug
> Launchpad-Bug: distribution=ubuntu; sourcepackage=httmock;
> component=universe; status=Fix Released; 

[Touch-packages] [Bug 1735160] Re: [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from bionic

[Colin Watson]

pymacaroons does have one potentially-interesting backward-incompatible
change, which is that Caveat.caveat_id and Macaroon.identifier are now
bytes rather than str.  I think the only place this is at all likely to
cause a problem in xenial is in snapcraft, and it's definitely worth
checking whether "snapcraft login" still works.

The py-macaroon-bakery change looks OK-ish, as long as (obviously)
somebody confirms that it's wire-compatible with the servers this is
intended to talk to.

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

Title:
  [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from
  bionic

Status in httmock package in Ubuntu:
  Fix Released
Status in protobuf package in Ubuntu:
  New
Status in pymacaroons package in Ubuntu:
  New
Status in python-nacl package in Ubuntu:
  New
Status in httmock source package in Xenial:
  In Progress
Status in protobuf source package in Xenial:
  New
Status in pymacaroons source package in Xenial:
  New
Status in python-nacl source package in Xenial:
  New

Bug description:
  [Impact]
  As part of allowing Ubuntu users to enable canonical-livepatch from 
software-properties GUI 
(https://wiki.ubuntu.com/SoftwareUpdates#Update_settings) we need to backport 
python3-macaroonbakery 0.0.6-1 [universe] from bionic. This will requires quite 
few changes:

  - backport httmock 1.2.6-1 [universe] from bionic - no httmock in xenial
  - backport pymacaroons 0.12.0-1 [universe] from bionic - xenial has 
0.9.2-0ubuntu1
  - SRU some changes in google-apputils-python - 
https://bugs.launchpad.net/ubuntu/+source/google-apputils-python/+bug/1735162
  - add python3-protobuf to python-protobuf 2.6.1-1.3 - Right now the python3 
package is not built.

  [Test case]
  - for python3-protobuf: $ python3 -c "import google.protobuf"
  - for python3-macaroonbakery: make sure all the tests pass

  [Regression Potential]
  - httmock, none has it's not in xenial
  - python3-protobuf, none has the python2 code was not edited
  TBC
  - pymacaroons, none has 0.12 is backward compatible with 0.9.2
  - python3-protobuf, none has it's not in xenial.

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

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

[Touch-packages] [Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade

[Timo Aaltonen]

** Summary changed:

- [regression] compiz crashes when hovering over sidebar
+ [regression] compiz crashes after Mesa upgrade

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Xenial:
  Confirmed
Status in mesa source package in Artful:
  Confirmed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

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

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

[Touch-packages] [Bug 1708409] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From hasri...@in.ibm.com 2018-01-09 09:15 EDT---
After boot on Bionic Beaver , issue is not observed.

# uname -a
Linux ltc-wspoon12 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:03:08 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux

# kdump-config show
DUMP_MODE:kdump
USE_KDUMP:1
KDUMP_SYSCTL: kernel.panic_on_oops=1
KDUMP_COREDIR:/var/crash
crashkernel addr:
/var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.13.0-17-generic
kdump initrd:
/var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.13.0-17-generic
current state:ready to kdump

kexec command:
/sbin/kexec -p --command-line="root=UUID=f009e6ec-b67d-4e08-89c9-b35b2b9e657f 
ro quiet splash xmon=on irqpoll noirqdistrib nr_cpus=1 nousb 
systemd.unit=kdump-tools.service ata_piix.prefer_ms_hyperv=0" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

Dmesg
---
[   32.866017] kdump-tools[3949]: Starting kdump-tools: Modified 
cmdline:root=UUID=f009e6ec-b67d-4e08-89c9-b35b2b9e657f ro quiet splash irqpoll 
noirqdistrib nr_cpus=1 nousb systemd.unit=kdump-tools.service 
ata_piix.prefer_ms_hyperv=0 elfcorehdr=157184K
[   33.277170] kdump-tools[3949]:  * loaded kdump kernel

Regards,
Harish

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

Title:
  kdump service does not start after configure/reboot

Status in The Ubuntu-power-systems project:
  Triaged
Status in makedumpfile package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Artful:
  New
Status in systemd source package in Artful:
  In Progress
Status in makedumpfile source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  == Comment: #0 - Harish Sriram  - 2017-08-02 01:45:01 ==
  kdump service does not start after configure/reboot

  --Problem Description---
  kdump service does not start after configure/reboot. It has to be 
started/loaded manually, everytime after reboot.

  # kdump-config status
  current state   : Not ready to kdump

  
  ---uname output---
  Linux ltc-test-ci2 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux 
   
  Machine Type/Model = Power 8/8247-22L 

  Additional Info-
  # cat /proc/cmdline
  root=UUID=974df602-c0e4-4e67-8853-78ad15884c59 ro console=tty0 
console=ttyS0,115200 quiet splash cgroup_enable=memory swapaccount=1 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
   
  ---Steps to Reproduce---
  1. installed linux-crashdump
  2. edited the kdump-tools.cfg crashkernel cmdline to above
  3. update-grub
  4. reboot

  Expected:
  kdump-config to be loaded by default after reboot

  # kdump-config status
  current state   : Not ready to kdump

  # service kdump-tools status
  * kdump-tools.service - Kernel crash dump capture service
 Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
pres
 Active: inactive (dead)

  ...
  https://github.com/systemd/systemd/issues/6334

  systemd in artful is not properly picking up the unit files in 
  /etc/systemd/system/default.target.wants

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1708409/+subscriptions

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

[Touch-packages] [Bug 1735594] Re: [regression] compiz crashes when hovering over sidebar

[Timo Aaltonen]

** Description changed:

- When I use the Unity session I automatically get logged out under these
- conditions:
+ [Impact]
+ When I use the Unity session I automatically get logged out under these 
conditions:
  
  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.
  
  running dmesg after this unwanted logout happens I get following
  information:
  
  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]
  
- The info about my installed compiz:
+ This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
+ - gen4 / gen5 Intel
+ - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)
  
- compiz:
-   Instal·lat: 1:0.9.13.1+17.10.20170901-0ubuntu1
-   Candidat:   1:0.9.13.1+17.10.20170901-0ubuntu1
-   Taula de versió:
-  *** 1:0.9.13.1+17.10.20170901-0ubuntu1 500
- 500 http://es.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
- 500 http://es.archive.ubuntu.com/ubuntu artful/universe i386 Packages
- 100 /var/lib/dpkg/status
+ [Test case]
+ Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.
+ 
+ [Regression potential]
+ The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).
+ 
+ Best to test on a wide array of Intel HW:
+ gen4 (965GM/GM45/G45)
+ gen5 (Ironlake)
+ gen6 (Sandy Bridge)
+ gen7 (Bay Trail, Ivy Bridge, Haswell)
+ gen8 (Braswell, Broadwell)
+ gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

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

Title:
  [regression] compiz crashes when hovering over sidebar

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Xenial:
  Confirmed
Status in mesa source package in Artful:
  Confirmed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

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

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

[Touch-packages] [Bug 1742011] Re: `find --name` ignores files with non-printable character in the filename

[H.-Dirk Schmitt]

Having a second look I found the mitigation cleaning up the filename
with the help of: `tr  --delete --complement '[:print:]`

So it is obvious that the characters breaking `find … -name` are non-
printable characters.

** Summary changed:

- find can't find several files with unicode characters if --name is used
+ `find --name` ignores files with non-printable character in the filename

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

Title:
  `find --name` ignores files with non-printable character in the
  filename

Status in findutils package in Ubuntu:
  New

Bug description:
  Downloading some files from ARTE via Mediathekview I retrieved files
  like this:

  ARTE_Concert_-_Jazz-Avishai_Cohen__Au_Gr�s_du_Jazz-1734575236.mp4

  find . is showing the the file:

  > $ find .
  > .
  > ./ARTE_Concert_-_Jazz-Avishai_Cohen__Au_Gr?s_du_Jazz-1734575236.mp4

  But if I invoke `find . -name "*mp4"` nothing is found.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: findutils 4.6.0+git+20160126-2
  ProcVersionSignature: Ubuntu 4.10.0-43.47~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-43-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jan  9 01:12:36 2018
  SourcePackage: findutils
  UpgradeStatus: No upgrade log present (probably fresh install)

  c42-bugnr: #3922

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

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

[Touch-packages] [Bug 1742156] [NEW] network-manager wired DHCP mode doesn't work on Ubuntu 18.04

[Cui Wei]

Public bug reported:

In virtualbox with NAT configured (10.0.2.2 as defaul DHCP IP), network-
manager on ubuntu 18.04 cannot find any wired interface and also cannot
connect to network via DHCP.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: network-manager (not installed)
ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12
Uname: Linux 4.14.0-15-generic x86_64
ApportVersion: 2.20.8-0ubuntu6
Architecture: amd64
CurrentDesktop: MATE
Date: Tue Jan  9 21:44:54 2018
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  network-manager wired DHCP mode doesn't work on Ubuntu 18.04

Status in network-manager package in Ubuntu:
  New

Bug description:
  In virtualbox with NAT configured (10.0.2.2 as defaul DHCP IP),
  network-manager on ubuntu 18.04 cannot find any wired interface and
  also cannot connect to network via DHCP.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager (not installed)
  ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12
  Uname: Linux 4.14.0-15-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Jan  9 21:44:54 2018
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits

[Eric Desrochers]

I note that the Seyeong's Artful debdiff proposed version
"2.11.0-2ubuntu18" and bionic "2.11.0-2ubuntu19"

# Current rmadison output
 apparmor | 2.11.0-2ubuntu17   | artful  
 apparmor | 2.11.0-2ubuntu18   | bionic  

Bionic version is good.

No need to change the debdiff, I'll do the change myself later, but I'm
afraid for Artful we can't use the same version twice for 2 separate
releases as it has, IMHO, high potential risk of rejection from SRU
team.

I would go with that versionning approach instead:

apparmor | 2.11.0-2ubuntu17.1 | artful  
apparmor | 2.11.0-2ubuntu19   | bionic

- Eric

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

Title:
  @{pid} variable broken on systems with pid_max more than 6 digits

Status in AppArmor:
  Fix Committed
Status in AppArmor 2.11 series:
  Fix Committed
Status in apparmor package in Ubuntu:
  Confirmed
Status in apparmor source package in Trusty:
  New
Status in apparmor source package in Xenial:
  New
Status in apparmor source package in Zesty:
  New
Status in apparmor source package in Artful:
  New
Status in apparmor source package in Bionic:
  Confirmed

Bug description:
  [Impact]

  If PID is larger than 6 digits.

  apparmor denies process.

  this fix is committed, but not released. so all supporting version are
  affected.

  [Test Case]

  1. making pid over 6 digits
  - i used touch command to do it
  2. snap install canonical-livepatch ( just picked this pkg )

  you can see denied msg as original description

  [Regression]
  this fix changes regex only, i don't think there is severe regression. also 
if there is regression, we can revert manually temporarily.
  denied services need to be restarted after fixing this.

  [Others]

  * Upstream commit:
   
https://gitlab.com/apparmor/apparmor/commit/630cb2a981cdc731847e8fdaafc45bcd337fe747

  * commit 630cb2a981cdc731847e8fdaafc45bcd337fe747
  Author: Vincas Dargis 
  Date:   Sat Sep 30 15:28:15 2017 +0300

  Allow seven digit pid

  * Affecting releases : TXZAB
  --
  $ git describe --contains 630cb2a9
  v2.11.95~5^2

  $ rmadison apparmor
   apparmor | 2.8.95~2430-0ubuntu5   | trusty
   apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-security
   apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-updates
   apparmor | 2.10.95-0ubuntu2   | xenial
   apparmor | 2.10.95-0ubuntu2.6 | xenial-security
   apparmor | 2.10.95-0ubuntu2.7 | xenial-updates
   apparmor | 2.11.0-2ubuntu4| zesty
   apparmor | 2.11.0-2ubuntu17   | artful
   apparmor | 2.11.0-2ubuntu18   | bionic

  $ rmadison -u debian apparmor
   apparmor   | 2.11.1-4 | unstable
  --

  * Revision :
  http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3722

  [Original Description]

  If your kernel.pid_max sysctl is set higher than the default, say at 7
  digits, the @{pid} variable no longer matches all pids, causing some
  breakage in any profile using it.

  @{pid} is defined in /etc/apparmor.d/tunables:
  
@{pid}={[1-9],[1-9][0-9],[1-9][0-9][0-9],[1-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9][0-9]}

  It only covers up to 6 digits.

  This Ubuntu 17.04 system has:
  kernel.pid_max = 4194303

  And is showing
  type=1400 audit(1505588857.828:792): apparmor="DENIED" operation="open" 
profile="libvirt-55e9e12c-e6dc-4f56-a547-8514cf7d9bf3" 
name="/proc/2168180/task/2769256/comm" pid=2168180 comm="qemu-system-x86" 
requested_mask="wr" denied_mask="wr" fsuid=111 ouid=111

  Which should be matched by
  @{PROC}/sys/vm/overcommit_memory r,
  in /etc/apparmor.d/abstractions/libvirt-qemu

  I'm seeing similar failures on 16.04 (2.10.95-0ubuntu2.7), 17.04
  (2.11.0-2ubuntu4) and 17.10 (2.11.0-2ubuntu17)

  I am aware this is a non-default configuration, but I think this
  should work.

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

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

[Touch-packages] [Bug 1735594] Re: [regression] compiz crashes when hovering over sidebar

[Timo Aaltonen]

** Summary changed:

- ubuntu automatically logs out when hovering sidebar
+ [regression] compiz crashes when hovering over sidebar

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

Title:
  [regression] compiz crashes when hovering over sidebar

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Xenial:
  Confirmed
Status in mesa source package in Artful:
  Confirmed

Bug description:
  When I use the Unity session I automatically get logged out under
  these conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  The info about my installed compiz:

  compiz:
    Instal·lat: 1:0.9.13.1+17.10.20170901-0ubuntu1
    Candidat:   1:0.9.13.1+17.10.20170901-0ubuntu1
    Taula de versió:
   *** 1:0.9.13.1+17.10.20170901-0ubuntu1 500
  500 http://es.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  500 http://es.archive.ubuntu.com/ubuntu artful/universe i386 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04

[Timo Aaltonen]

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

** This bug has been marked a duplicate of bug 1735594
   ubuntu automatically logs out when hovering sidebar

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

Title:
  Unity / Compiz in a crash loop after login, after mesa updates of
  2018-01-04

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Xenial:
  Confirmed
Status in mesa source package in Artful:
  Confirmed

Bug description:
  GUI is constantly crashing, can't start desktop

  Jan  5 11:21:29 1810 kernel: [  806.368754] compiz[10824]: segfault at 0 ip 
7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000]
  Jan  5 11:21:40 1810 kernel: [  817.279740] compiz[1]: segfault at 0 ip 
7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000]
  Jan  5 11:22:30 1810 kernel: [  867.445137] compiz[11271]: segfault at 0 ip 
7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000]
  Jan  5 11:22:46 1810 kernel: [  883.319195] compiz[11458]: segfault at 0 ip 
7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000]
  Jan  5 11:23:01 1810 kernel: [  898.587610] compiz[11516]: segfault at 0 ip 
7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000]

  In /var/crash:
  _usr_bin_compiz.999.crash

  Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not 
really usable.
  - dash not working
  - no window switching
  - sometimes all windows disappear for a few seconds

  So effectively my laptop is not usable after latest updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160906-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  .tmp.unity_support_test.0:

  .tmp.unity_support_test.1:

  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Jan  5 11:16:53 2018
  DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:029b]
     Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:029b]
  InstallationDate: Installed on 2014-04-18 (1357 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Acer Aspire 1810TZ
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic 
root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago)
  dmi.bios.date: 08/31/2010
  dmi.bios.vendor: INSYDE
  dmi.bios.version: v1.3314
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JM11-MS
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: Aspire 1810TZ
  dmi.product.version: v1.3314
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Jan  5 11:14:24 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1741925] Re: Unity launcher disappears on mouse-over launcher

[Timo Aaltonen]

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

I was able to reproduce after all, marking as a dupe

** This bug has been marked a duplicate of bug 1735594
   ubuntu automatically logs out when hovering sidebar

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

Title:
  Unity launcher disappears on mouse-over launcher

Status in mesa package in Ubuntu:
  New

Bug description:
  Move the mouse over the launcher and the EVERYTHING on the desktop
  disappears for a few seconds. Only the wallpaper remains. Failed
  immediately after the latest update (installed by me on 5 Jan 2018)
  and a reboot. Reboot doesn't help.

  Launcher and the other desktop displays return after a 10 to 30 second
  pause. No disk activity is observed during recovery.

  "ClassicMenu Indicator" is installed and it is the only way to start
  an application.

  Executing the bug and then immediately examining all the /var/log logs
  showed no recorded error or incident in any log.

  uname -a = Linux bruce-Latitude-D630 4.10.0-42-generic
  #46~16.04.1-Ubuntu SMP Mon Dec 4 15:57:59 UTC 2017 i686 i686 i686
  GNU/Linux

  Abridged hardware list from  sudo lshw
   
  description: Portable Computer
  product: Latitude D630
  vendor: Dell Inc.
  width: 32 bits
  capabilities: smbios-2.4 dmi-2.4
  configuration: boot=normal chassis=portable 
uuid=44454C4C-6E00-1039-8032-B2C04F376831
*-core
 description: Motherboard
 vendor: Dell Inc.
 physical id: 0
 serial: .2n927h1.  .
   *-firmware
description: BIOS
vendor: Dell Inc.
physical id: 0
version: A12
date: 06/20/2008
size: 64KiB
capacity: 1984KiB
capabilities: isa pci pcmcia pnp upgrade shadowing cdboot 
bootselect int13floppy720 int5printscreen int9keyboard int14serial int17printer 
int10video acpi usb agp smartbattery biosbootspecification netboot
   *-cpu
description: CPU
product: Intel(R) Core(TM)2 Duo CPU T7250  @ 2.00GHz
vendor: Intel Corp.
physical id: 400
bus info: cpu@0
version: 6.15.13
serial: -06FD----
slot: Microprocessor
size: 2GHz
capacity: 2001MHz
width: 64 bits
clock: 200MHz
capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae 
mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 
ss ht tm pbe nx constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 
monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm tpr_shadow vnmi 
flexpriority dtherm ida cpufreq
configuration: cores=2 enabledcores=2 id=0 threads=2
  *-cache:0
   description: L1 cache
   physical id: 700
   size: 32KiB
   capacity: 32KiB
   capabilities: internal write-back data
   configuration: level=1
  *-cache:1
   description: L2 cache
   physical id: 701
   size: 2MiB
   capacity: 2MiB
   clock: 66MHz (15.0ns)
   capabilities: pipeline-burst internal varies unified
   configuration: level=2
  *-logicalcpu:0
   description: Logical CPU
   physical id: 0.1
   width: 64 bits
   capabilities: logical
  *-logicalcpu:1
   description: Logical CPU
   physical id: 0.2
   width: 64 bits
   capabilities: logical
   *-memory
description: System Memory
physical id: 1000
slot: System board or motherboard
size: 2GiB
  *-bank:0
   description: DIMM DDR Synchronous 667 MHz (1.5 ns)
   product: V916765G24QCFW-F5
   vendor: ProMOS/Mosel Vitelic
   physical id: 0
   serial: 07B02E7C
   slot: DIMM_A
   size: 1GiB
   width: 64 bits
   clock: 667MHz (1.5ns)
  *-bank:1
   description: DIMM DDR Synchronous 667 MHz (1.5 ns)
   product: V916765G24QCFW-F5
   vendor: ProMOS/Mosel Vitelic
   physical id: 1
   serial: E9AE2E7D
   slot: DIMM_B
   size: 1GiB
   width: 64 bits
   clock: 667MHz (1.5ns)
   *-pci
description: Host bridge
product: Mobile PM965/GM965/GL960 Memory Controller Hub
vendor: Intel Corporation
physical id: 100
bus info: pci@:00:00.0
version: 0c
width: 32 bits
clock: 33MHz

To manage 

[Touch-packages] [Bug 1741874] Re: if I move the arrow to the Unity, all the unity disappear , only the background still appear , and all the action freezed

[Timo Aaltonen]

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

no need, marking as a duplicate

** This bug has been marked a duplicate of bug 1735594
   ubuntu automatically logs out when hovering sidebar

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

Title:
  if I move the arrow to the Unity, all the unity disappear ,only the
  background still appear ,and all the action freezed

Status in mesa package in Ubuntu:
  New

Bug description:
  My OS is Ubuntu 16.04 lts,and I upgrader last week (2018/01/07),and
  whe I restart my computer,if I move the mouse arrow to the lift Unity
  ,the OS will freeze,all the icon disappear,it keeps for one minutes,if
  the arrow touch the Unity again ,as the same issue would happen ,so I
  cant touch the Unity, now I use the cairo-dock and terminal to control
  my Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.23
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Mon Jan  8 18:16:32 2018
  InstallationDate: Installed on 2017-09-19 (110 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)

[Timo Aaltonen]

This patch broke the DRI driver on older gen4/4.5/5 Intel HW, see bugs
1735594 and 1741447

I've backported five commits from upstream to fix this properly, at
least this backport doesn't crash on my HW anymore.

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

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

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

Title:
  Corruption on windowed 3D apps running on dGPU (Intel/AMD)

Status in Mesa:
  In Progress
Status in OEM Priority Project:
  Fix Released
Status in mesa package in Ubuntu:
  In Progress
Status in mesa source package in Xenial:
  Triaged
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  Corruption is seen on windowed 3D apps running on dGPU

  [Test case]

  Get a certain Intel/AMD hybrid machine, run 'DRI_PRIME=1 glxgears',
  see how the window has corrupted gfx.

  The fix is to patch Intel i965_dri driver.

  [Regression potential]

  There could be a slight loss of performance, but corruption free
  behaviour.

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

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

[Touch-packages] [Bug 1735594] Re: ubuntu automatically logs out when hovering sidebar

[Timo Aaltonen]

The culprit is a patch added for bug 1727401, it needs to be replaced
with a larger set of backports from 17.3...

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

Title:
  ubuntu automatically logs out when hovering sidebar

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Xenial:
  Confirmed
Status in mesa source package in Artful:
  Confirmed

Bug description:
  When I use the Unity session I automatically get logged out under
  these conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  The info about my installed compiz:

  compiz:
    Instal·lat: 1:0.9.13.1+17.10.20170901-0ubuntu1
    Candidat:   1:0.9.13.1+17.10.20170901-0ubuntu1
    Taula de versió:
   *** 1:0.9.13.1+17.10.20170901-0ubuntu1 500
  500 http://es.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  500 http://es.archive.ubuntu.com/ubuntu artful/universe i386 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1742144] Re: Only noise on Buildin Audio headphone output

[yoann]

** Description changed:

  For a few weeks, as soon as I plug headphone or sound system to the Jack
- input, I just got lots of noise.
+ output, I just got lots of noise.
  
  $ lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  root@kveikur:/var/log# uname -a
  Linux kveikur 4.14.12-041412-generic #201801051649 SMP Fri Jan 5 16:50:54 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  
  $ apt-cache policy alsa-utils
  alsa-utils:
-   Installed: 1.1.0-0ubuntu5
-   Candidate: 1.1.0-0ubuntu5
-   Version table:
-  *** 1.1.0-0ubuntu5 500
- 500 http://ch.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 1.1.0-0ubuntu5
+   Candidate: 1.1.0-0ubuntu5
+   Version table:
+  *** 1.1.0-0ubuntu5 500
+ 500 http://ch.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
+ 100 /var/lib/dpkg/status
  
  $ apt-cache policy alsa-base
  alsa-base:
-   Installed: 1.0.25+dfsg-0ubuntu5
-   Candidate: 1.0.25+dfsg-0ubuntu5
-   Version table:
-  *** 1.0.25+dfsg-0ubuntu5 500
- 500 http://ch.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
- 500 http://ch.archive.ubuntu.com/ubuntu xenial/main i386 Packages
- 100 /var/lib/dpkg/status
- 
+   Installed: 1.0.25+dfsg-0ubuntu5
+   Candidate: 1.0.25+dfsg-0ubuntu5
+   Version table:
+  *** 1.0.25+dfsg-0ubuntu5 500
+ 500 http://ch.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
+ 500 http://ch.archive.ubuntu.com/ubuntu xenial/main i386 Packages
+ 100 /var/lib/dpkg/status
  
  Here the information I have in syslog :
  
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c: snd_pcm_avail() returned a value that is exceptionally large: 
376480 bytes (2134 ms).
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. 
Please report this issue to the ALSA developers.
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c: snd_pcm_dump():
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c: Hardware PCM card 0 'HDA Intel PCH' device 0 subdevice 0
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c: Its setup is:
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   stream   : CAPTURE
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   access   : MMAP_INTERLEAVED
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   format   : S16_LE
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   subformat: STD
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   channels : 2
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   rate : 44100
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   exact rate   : 44100 (44100/1)
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   msbits   : 16
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   buffer_size  : 16384
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   period_size  : 8192
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   period_time  : 185759
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   tstamp_mode  : ENABLE
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   tstamp_type  : MONOTONIC
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   period_step  : 1
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   avail_min: 8192
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   period_event : 0
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   start_threshold  : -1
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   stop_threshold   : 4611686018427387904
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   silence_threshold: 0
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   silence_size : 0
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   boundary : 4611686018427387904
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   appl_ptr : 1113200
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   hw_ptr   : 1207320
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  

[Touch-packages] [Bug 997020] Re: apport-collect does not work on headless servers

[Maraschin]

I just run on another use case for this:

A kernel upgrade made gnome unable to start, apport-collect needs to have a 
confirmation from a browser but since I can't start a normal desktop, I can't 
send the report.
The workaround using w3m may work but than after that I need to set back to 
firefox, not the easiest way. We could improve here a lot!

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

Title:
  apport-collect does not work on headless servers

Status in apport package in Ubuntu:
  Triaged

Bug description:
  It is essential that apport-collect  works on a headless/non-X
  installs in order to report bugs. In this case, apport-collect tries
  to use a text-based browser to attempt to login to Launchpad.

  I tried lynx, links2, elinks and w3m. With elinks I get the following
  message: "Your Page Was Stale" after selecting "continue".

  This bug is related to #556927, #645024 and #683337. As these only
  concern the functioning of w3m, I would here like to raise the issue
  that a proper installation must make sure that a compatible text-based
  browser is installed and set as default.

  WORKAROUND: Execute the following:
  sudo apt-get install w3m
  sudo update-alternatives --set www-browser /usr/bin/w3m

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

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

[Touch-packages] [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits

[Eric Desrochers]

Meanwhile, please make sure you have submitted the patch to Debian and
link the debbug in this LP.

- Eric

** Changed in: apparmor (Ubuntu Trusty)
 Assignee: (unassigned) => Seyeong Kim (xtrusia)

** Changed in: apparmor (Ubuntu Xenial)
 Assignee: (unassigned) => Seyeong Kim (xtrusia)

** Changed in: apparmor (Ubuntu Zesty)
 Assignee: (unassigned) => Seyeong Kim (xtrusia)

** Changed in: apparmor (Ubuntu Artful)
 Assignee: (unassigned) => Seyeong Kim (xtrusia)

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

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

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

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

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

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

Title:
  @{pid} variable broken on systems with pid_max more than 6 digits

Status in AppArmor:
  Fix Committed
Status in AppArmor 2.11 series:
  Fix Committed
Status in apparmor package in Ubuntu:
  Confirmed
Status in apparmor source package in Trusty:
  New
Status in apparmor source package in Xenial:
  New
Status in apparmor source package in Zesty:
  New
Status in apparmor source package in Artful:
  New
Status in apparmor source package in Bionic:
  Confirmed

Bug description:
  [Impact]

  If PID is larger than 6 digits.

  apparmor denies process.

  this fix is committed, but not released. so all supporting version are
  affected.

  [Test Case]

  1. making pid over 6 digits
  - i used touch command to do it
  2. snap install canonical-livepatch ( just picked this pkg )

  you can see denied msg as original description

  [Regression]
  this fix changes regex only, i don't think there is severe regression. also 
if there is regression, we can revert manually temporarily.
  denied services need to be restarted after fixing this.

  [Others]

  * Upstream commit:
   
https://gitlab.com/apparmor/apparmor/commit/630cb2a981cdc731847e8fdaafc45bcd337fe747

  * commit 630cb2a981cdc731847e8fdaafc45bcd337fe747
  Author: Vincas Dargis 
  Date:   Sat Sep 30 15:28:15 2017 +0300

  Allow seven digit pid

  * Affecting releases : TXZAB
  --
  $ git describe --contains 630cb2a9
  v2.11.95~5^2

  $ rmadison apparmor
   apparmor | 2.8.95~2430-0ubuntu5   | trusty
   apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-security
   apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-updates
   apparmor | 2.10.95-0ubuntu2   | xenial
   apparmor | 2.10.95-0ubuntu2.6 | xenial-security
   apparmor | 2.10.95-0ubuntu2.7 | xenial-updates
   apparmor | 2.11.0-2ubuntu4| zesty
   apparmor | 2.11.0-2ubuntu17   | artful
   apparmor | 2.11.0-2ubuntu18   | bionic

  $ rmadison -u debian apparmor
   apparmor   | 2.11.1-4 | unstable
  --

  * Revision :
  http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3722

  [Original Description]

  If your kernel.pid_max sysctl is set higher than the default, say at 7
  digits, the @{pid} variable no longer matches all pids, causing some
  breakage in any profile using it.

  @{pid} is defined in /etc/apparmor.d/tunables:
  
@{pid}={[1-9],[1-9][0-9],[1-9][0-9][0-9],[1-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9][0-9]}

  It only covers up to 6 digits.

  This Ubuntu 17.04 system has:
  kernel.pid_max = 4194303

  And is showing
  type=1400 audit(1505588857.828:792): apparmor="DENIED" operation="open" 
profile="libvirt-55e9e12c-e6dc-4f56-a547-8514cf7d9bf3" 
name="/proc/2168180/task/2769256/comm" pid=2168180 comm="qemu-system-x86" 
requested_mask="wr" denied_mask="wr" fsuid=111 ouid=111

  Which should be matched by
  @{PROC}/sys/vm/overcommit_memory r,
  in /etc/apparmor.d/abstractions/libvirt-qemu

  I'm seeing similar failures on 16.04 (2.10.95-0ubuntu2.7), 17.04
  (2.11.0-2ubuntu4) and 17.10 (2.11.0-2ubuntu17)

  I am aware this is a non-default configuration, but I think this
  should work.

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

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

[Touch-packages] [Bug 1742143] Re: package systemd 235-3ubuntu3 failed to install/upgrade: triggers looping, abandoned

[Jean-Baptiste Lallement]

** Description changed:

  it happened during an upgrade from 17.10 to 18.04
+ 
+ Full upgrade logs attached to bug 1742147
  
  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd 235-3ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  Date: Tue Jan  9 13:39:24 2018
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2014-07-23 (1265 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Inspiron 3138
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 
root=UUID=21502cb7-5c71-4695-90bc-c7d2c44e12ee ro 
init=/lib/systemd/systemd-bootchart
  Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
-  dpkg 1.19.0.4ubuntu1
-  apt  1.6~alpha5
+  dpkg 1.19.0.4ubuntu1
+  apt  1.6~alpha5
  SourcePackage: systemd
  Title: package systemd 235-3ubuntu3 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: Upgraded to bionic on 2018-01-09 (0 days ago)
  dmi.bios.date: 08/30/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0FC0K2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A06
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd08/30/2013:svnDellInc.:pnInspiron3138:pvr:rvnDellInc.:rn0FC0K2:rvrA00:cvnDellInc.:ct8:cvrA06:
  dmi.product.family: 103C_5335KV
  dmi.product.name: Inspiron 3138
  dmi.sys.vendor: Dell Inc.

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

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

Title:
  package systemd 235-3ubuntu3 failed to install/upgrade: triggers
  looping, abandoned

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  it happened during an upgrade from 17.10 to 18.04

  Full upgrade logs attached to bug 1742147

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd 235-3ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  Date: Tue Jan  9 13:39:24 2018
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2014-07-23 (1265 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Inspiron 3138
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 
root=UUID=21502cb7-5c71-4695-90bc-c7d2c44e12ee ro 
init=/lib/systemd/systemd-bootchart
  Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.19.0.4ubuntu1
   apt  1.6~alpha5
  SourcePackage: systemd
  Title: package systemd 235-3ubuntu3 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: Upgraded to bionic on 2018-01-09 (0 days ago)
  dmi.bios.date: 08/30/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0FC0K2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A06
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd08/30/2013:svnDellInc.:pnInspiron3138:pvr:rvnDellInc.:rn0FC0K2:rvrA00:cvnDellInc.:ct8:cvrA06:
  dmi.product.family: 103C_5335KV
  dmi.product.name: Inspiron 3138
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1738660] Re: package systemd 235-3ubuntu2 failed to install/upgrade: triggers looping, abandoned

[Jean-Baptiste Lallement]

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

** This bug has been marked a duplicate of bug 1742143
   package systemd 235-3ubuntu3 failed to install/upgrade: triggers looping, 
abandoned

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

Title:
  package systemd 235-3ubuntu2 failed to install/upgrade: triggers
  looping, abandoned

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I cannot understand this error.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd 235-3ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.8-0ubuntu5
  Architecture: amd64
  Date: Sun Dec 17 13:30:04 2017
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2017-05-13 (218 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Sony Corporation VPCL117FX
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=49c6d767-f0a3-40e4-9371-afba6ac27484 ro quiet splash
  Python3Details: /usr/bin/python3.6, Python 3.6.4rc1, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.19.0.4ubuntu1
   apt  1.6~alpha5
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  Title: package systemd 235-3ubuntu2 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: Upgraded to bionic on 2017-12-17 (0 days ago)
  dmi.bios.date: 07/23/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R0200T5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 13
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR0200T5:bd07/23/2009:svnSonyCorporation:pnVPCL117FX:pvrC6U1CAX1:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct13:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: VPCL117FX
  dmi.product.version: C6U1CAX1
  dmi.sys.vendor: Sony Corporation

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

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

[Touch-packages] [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits

[Eric Desrochers]

Thanks Seyeong !

I'll do a 2nd review when the build farm will be back and will do the
other changes if necessary.

- Eric

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

Title:
  @{pid} variable broken on systems with pid_max more than 6 digits

Status in AppArmor:
  Fix Committed
Status in AppArmor 2.11 series:
  Fix Committed
Status in apparmor package in Ubuntu:
  Confirmed
Status in apparmor source package in Trusty:
  New
Status in apparmor source package in Xenial:
  New
Status in apparmor source package in Zesty:
  New
Status in apparmor source package in Artful:
  New
Status in apparmor source package in Bionic:
  Confirmed

Bug description:
  [Impact]

  If PID is larger than 6 digits.

  apparmor denies process.

  this fix is committed, but not released. so all supporting version are
  affected.

  [Test Case]

  1. making pid over 6 digits
  - i used touch command to do it
  2. snap install canonical-livepatch ( just picked this pkg )

  you can see denied msg as original description

  [Regression]
  this fix changes regex only, i don't think there is severe regression. also 
if there is regression, we can revert manually temporarily.
  denied services need to be restarted after fixing this.

  [Others]

  * Upstream commit:
   
https://gitlab.com/apparmor/apparmor/commit/630cb2a981cdc731847e8fdaafc45bcd337fe747

  * commit 630cb2a981cdc731847e8fdaafc45bcd337fe747
  Author: Vincas Dargis 
  Date:   Sat Sep 30 15:28:15 2017 +0300

  Allow seven digit pid

  * Affecting releases : TXZAB
  --
  $ git describe --contains 630cb2a9
  v2.11.95~5^2

  $ rmadison apparmor
   apparmor | 2.8.95~2430-0ubuntu5   | trusty
   apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-security
   apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-updates
   apparmor | 2.10.95-0ubuntu2   | xenial
   apparmor | 2.10.95-0ubuntu2.6 | xenial-security
   apparmor | 2.10.95-0ubuntu2.7 | xenial-updates
   apparmor | 2.11.0-2ubuntu4| zesty
   apparmor | 2.11.0-2ubuntu17   | artful
   apparmor | 2.11.0-2ubuntu18   | bionic

  $ rmadison -u debian apparmor
   apparmor   | 2.11.1-4 | unstable
  --

  * Revision :
  http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3722

  [Original Description]

  If your kernel.pid_max sysctl is set higher than the default, say at 7
  digits, the @{pid} variable no longer matches all pids, causing some
  breakage in any profile using it.

  @{pid} is defined in /etc/apparmor.d/tunables:
  
@{pid}={[1-9],[1-9][0-9],[1-9][0-9][0-9],[1-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9][0-9]}

  It only covers up to 6 digits.

  This Ubuntu 17.04 system has:
  kernel.pid_max = 4194303

  And is showing
  type=1400 audit(1505588857.828:792): apparmor="DENIED" operation="open" 
profile="libvirt-55e9e12c-e6dc-4f56-a547-8514cf7d9bf3" 
name="/proc/2168180/task/2769256/comm" pid=2168180 comm="qemu-system-x86" 
requested_mask="wr" denied_mask="wr" fsuid=111 ouid=111

  Which should be matched by
  @{PROC}/sys/vm/overcommit_memory r,
  in /etc/apparmor.d/abstractions/libvirt-qemu

  I'm seeing similar failures on 16.04 (2.10.95-0ubuntu2.7), 17.04
  (2.11.0-2ubuntu4) and 17.10 (2.11.0-2ubuntu17)

  I am aware this is a non-default configuration, but I think this
  should work.

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

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

[Touch-packages] [Bug 1738670] Re: package systemd 235-3ubuntu2 failed to install/upgrade: triggers looping, abandoned

[Jean-Baptiste Lallement]

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

** This bug has been marked a duplicate of bug 1742143
   package systemd 235-3ubuntu3 failed to install/upgrade: triggers looping, 
abandoned

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

Title:
  package systemd 235-3ubuntu2 failed to install/upgrade: triggers
  looping, abandoned

Status in systemd package in Ubuntu:
  New

Bug description:
  tried to do a release upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd 235-3ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu5
  Architecture: amd64
  Date: Sun Dec 17 16:46:21 2017
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2016-04-23 (603 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic 
root=UUID=8ccfe2c6-3d43-4efd-afec-10f81a10901d ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.6, Python 3.6.4rc1, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.19.0.4ubuntu1
   apt  1.6~alpha5
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  Title: package systemd 235-3ubuntu2 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: Upgraded to bionic on 2017-12-17 (0 days ago)
  dmi.bios.date: 10/16/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1604
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1604:bd10/16/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

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

[Touch-packages] [Bug 1740997] Re: package systemd 235-3ubuntu2 failed to install/upgrade: triggers looping, abandoned

[Jean-Baptiste Lallement]

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

** This bug has been marked a duplicate of bug 1742143
   package systemd 235-3ubuntu3 failed to install/upgrade: triggers looping, 
abandoned

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

Title:
  package systemd 235-3ubuntu2 failed to install/upgrade: triggers
  looping, abandoned

Status in systemd package in Ubuntu:
  New

Bug description:
  systemd and dpkg crashed during dist-upgrade from artful to bionic

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd 235-3ubuntu2
  ProcVersionSignature: Ubuntu 4.14.0-11.13-generic 4.14.3
  Uname: Linux 4.14.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu5
  Architecture: amd64
  Date: Tue Jan  2 20:00:27 2018
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2016-11-01 (428 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Hewlett-Packard HP Z420 Workstation
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.14.0-11-generic 
root=UUID=836402c4-db45-4f3c-adf2-0a1cfe22af77 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.19.0.4ubuntu1
   apt  1.6~alpha5
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  Title: package systemd 235-3ubuntu2 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J61 v03.91
  dmi.board.name: 1589
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 0.00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ61v03.91:bd10/17/2016:svnHewlett-Packard:pnHPZ420Workstation:pvr:rvnHewlett-Packard:rn1589:rvr0.00:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53335X G=D
  dmi.product.name: HP Z420 Workstation
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1742143] Re: package systemd 235-3ubuntu3 failed to install/upgrade: triggers looping, abandoned

[Jean-Baptiste Lallement]

** Tags added: rls-bb-incoming

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

Title:
  package systemd 235-3ubuntu3 failed to install/upgrade: triggers
  looping, abandoned

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  it happened during an upgrade from 17.10 to 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd 235-3ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  Date: Tue Jan  9 13:39:24 2018
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2014-07-23 (1265 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Inspiron 3138
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 
root=UUID=21502cb7-5c71-4695-90bc-c7d2c44e12ee ro 
init=/lib/systemd/systemd-bootchart
  Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.19.0.4ubuntu1
   apt  1.6~alpha5
  SourcePackage: systemd
  Title: package systemd 235-3ubuntu3 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: Upgraded to bionic on 2018-01-09 (0 days ago)
  dmi.bios.date: 08/30/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0FC0K2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A06
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd08/30/2013:svnDellInc.:pnInspiron3138:pvr:rvnDellInc.:rn0FC0K2:rvrA00:cvnDellInc.:ct8:cvrA06:
  dmi.product.family: 103C_5335KV
  dmi.product.name: Inspiron 3138
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1742143] [NEW] package systemd 235-3ubuntu3 failed to install/upgrade: triggers looping, abandoned

[Jean-Baptiste Lallement]

Public bug reported:

it happened during an upgrade from 17.10 to 18.04

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: systemd 235-3ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
ApportVersion: 2.20.8-0ubuntu6
Architecture: amd64
Date: Tue Jan  9 13:39:24 2018
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2014-07-23 (1265 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: Dell Inc. Inspiron 3138
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 
root=UUID=21502cb7-5c71-4695-90bc-c7d2c44e12ee ro 
init=/lib/systemd/systemd-bootchart
Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.19.0.4ubuntu1
 apt  1.6~alpha5
SourcePackage: systemd
Title: package systemd 235-3ubuntu3 failed to install/upgrade: triggers 
looping, abandoned
UpgradeStatus: Upgraded to bionic on 2018-01-09 (0 days ago)
dmi.bios.date: 08/30/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0FC0K2
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A06
dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd08/30/2013:svnDellInc.:pnInspiron3138:pvr:rvnDellInc.:rn0FC0K2:rvrA00:cvnDellInc.:ct8:cvrA06:
dmi.product.family: 103C_5335KV
dmi.product.name: Inspiron 3138
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-package bionic rls-bb-incoming

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

Title:
  package systemd 235-3ubuntu3 failed to install/upgrade: triggers
  looping, abandoned

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  it happened during an upgrade from 17.10 to 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd 235-3ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  Date: Tue Jan  9 13:39:24 2018
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2014-07-23 (1265 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Inspiron 3138
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 
root=UUID=21502cb7-5c71-4695-90bc-c7d2c44e12ee ro 
init=/lib/systemd/systemd-bootchart
  Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.19.0.4ubuntu1
   apt  1.6~alpha5
  SourcePackage: systemd
  Title: package systemd 235-3ubuntu3 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: Upgraded to bionic on 2018-01-09 (0 days ago)
  dmi.bios.date: 08/30/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0FC0K2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A06
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd08/30/2013:svnDellInc.:pnInspiron3138:pvr:rvnDellInc.:rn0FC0K2:rvrA00:cvnDellInc.:ct8:cvrA06:
  dmi.product.family: 103C_5335KV
  dmi.product.name: Inspiron 3138
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1742143] Re: package systemd 235-3ubuntu3 failed to install/upgrade: triggers looping, abandoned

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

Title:
  package systemd 235-3ubuntu3 failed to install/upgrade: triggers
  looping, abandoned

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  it happened during an upgrade from 17.10 to 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd 235-3ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  Date: Tue Jan  9 13:39:24 2018
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2014-07-23 (1265 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Inspiron 3138
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 
root=UUID=21502cb7-5c71-4695-90bc-c7d2c44e12ee ro 
init=/lib/systemd/systemd-bootchart
  Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.19.0.4ubuntu1
   apt  1.6~alpha5
  SourcePackage: systemd
  Title: package systemd 235-3ubuntu3 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: Upgraded to bionic on 2018-01-09 (0 days ago)
  dmi.bios.date: 08/30/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0FC0K2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A06
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd08/30/2013:svnDellInc.:pnInspiron3138:pvr:rvnDellInc.:rn0FC0K2:rvrA00:cvnDellInc.:ct8:cvrA06:
  dmi.product.family: 103C_5335KV
  dmi.product.name: Inspiron 3138
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1742143] Re: package systemd 235-3ubuntu3 failed to install/upgrade: triggers looping, abandoned

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package systemd 235-3ubuntu3 failed to install/upgrade: triggers
  looping, abandoned

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  it happened during an upgrade from 17.10 to 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd 235-3ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  Date: Tue Jan  9 13:39:24 2018
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2014-07-23 (1265 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Inspiron 3138
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 
root=UUID=21502cb7-5c71-4695-90bc-c7d2c44e12ee ro 
init=/lib/systemd/systemd-bootchart
  Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.19.0.4ubuntu1
   apt  1.6~alpha5
  SourcePackage: systemd
  Title: package systemd 235-3ubuntu3 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: Upgraded to bionic on 2018-01-09 (0 days ago)
  dmi.bios.date: 08/30/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0FC0K2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A06
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd08/30/2013:svnDellInc.:pnInspiron3138:pvr:rvnDellInc.:rn0FC0K2:rvrA00:cvnDellInc.:ct8:cvrA06:
  dmi.product.family: 103C_5335KV
  dmi.product.name: Inspiron 3138
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1741940] Re: package systemd 235-3ubuntu3 failed to install/upgrade: triggers looping, abandoned

[Jean-Baptiste Lallement]

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

** This bug has been marked a duplicate of bug 1742143
   package systemd 235-3ubuntu3 failed to install/upgrade: triggers looping, 
abandoned

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

Title:
  package systemd 235-3ubuntu3 failed to install/upgrade: triggers
  looping, abandoned

Status in systemd package in Ubuntu:
  New

Bug description:
  Upgrading from Artful

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd 235-3ubuntu3
  Uname: Linux 4.15.0-999-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  Date: Mon Jan  8 17:47:35 2018
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2016-10-30 (435 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-999-generic 
root=UUID=85588768-f139-4db0-8652-92f7319df86a ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.19.0.4ubuntu1
   apt  1.6~alpha5
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/clamav-daemon.service → 
/etc/systemd/system/clamav-daemon.service.d/extend.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  Title: package systemd 235-3ubuntu3 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: Upgraded to bionic on 2018-01-08 (0 days ago)
  dmi.bios.date: 04/06/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: GA-990FX-GAMING
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd04/06/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990FX-GAMING:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1742144] [NEW] Only noise on Buildin Audio headphone output

[yoann]

Public bug reported:

For a few weeks, as soon as I plug headphone or sound system to the Jack
input, I just got lots of noise.

$ lsb_release -rd
Description:Ubuntu 16.04.3 LTS
Release:16.04
root@kveikur:/var/log# uname -a
Linux kveikur 4.14.12-041412-generic #201801051649 SMP Fri Jan 5 16:50:54 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

$ apt-cache policy alsa-utils
alsa-utils:
  Installed: 1.1.0-0ubuntu5
  Candidate: 1.1.0-0ubuntu5
  Version table:
 *** 1.1.0-0ubuntu5 500
500 http://ch.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

$ apt-cache policy alsa-base
alsa-base:
  Installed: 1.0.25+dfsg-0ubuntu5
  Candidate: 1.0.25+dfsg-0ubuntu5
  Version table:
 *** 1.0.25+dfsg-0ubuntu5 500
500 http://ch.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
500 http://ch.archive.ubuntu.com/ubuntu xenial/main i386 Packages
100 /var/lib/dpkg/status


Here the information I have in syslog :

Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c: snd_pcm_avail() returned a value that is exceptionally large: 
376480 bytes (2134 ms).
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. 
Please report this issue to the ALSA developers.
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c: snd_pcm_dump():
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c: Hardware PCM card 0 'HDA Intel PCH' device 0 subdevice 0
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c: Its setup is:
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   stream   : CAPTURE
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   access   : MMAP_INTERLEAVED
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   format   : S16_LE
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   subformat: STD
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   channels : 2
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   rate : 44100
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   exact rate   : 44100 (44100/1)
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   msbits   : 16
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   buffer_size  : 16384
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   period_size  : 8192
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   period_time  : 185759
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   tstamp_mode  : ENABLE
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   tstamp_type  : MONOTONIC
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   period_step  : 1
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   avail_min: 8192
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   period_event : 0
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   start_threshold  : -1
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   stop_threshold   : 4611686018427387904
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   silence_threshold: 0
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   silence_size : 0
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   boundary : 4611686018427387904
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   appl_ptr : 1113200
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   hw_ptr   : 1207320

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
Uname: Linux 4.14.12-041412-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  yoann  7801 F pulseaudio
 /dev/snd/controlC1:  yoann  7801 F pulseaudio
Date: Tue Jan  9 14:02:51 2018
InstallationDate: Installed on 2015-11-30 (770 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
PackageArchitecture: all
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: alsa-driver
UpgradeStatus: Upgraded to 

[Touch-packages] [Bug 1452291] Re: Browser cannot use system proxy settings

[Rüdiger Kupper]

Problem still exists in the UBPorts image.

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

Title:
  Browser cannot use system proxy settings

Status in Canonical System Image:
  Confirmed
Status in Oxide:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Confirmed
Status in webbrowser-app package in Ubuntu RTM:
  Confirmed

Bug description:
  While I can create successfully system proxy settings using

  gsettings set org.gnome.system.proxy use-same-proxy false
  gsettings set org.gnome.system.proxy mode "'manual'"
  gsettings set org.gnome.system.proxy ignore-hosts "['localhost',
  '127.0.0.0/8', '192.168.0.0/16', '::1']"
  gsettings set org.gnome.system.proxy.ftp host "'192.168.112.1'"
  gsettings set org.gnome.system.proxy.ftp port 800
  gsettings set org.gnome.system.proxy.socks host "'192.168.112.1'"
  gsettings set org.gnome.system.proxy.socks port 800
  gsettings set org.gnome.system.proxy.http host "'192.168.112.1'"
  gsettings set org.gnome.system.proxy.http port 800
  gsettings set org.gnome.system.proxy.http use-authentication false
  gsettings set org.gnome.system.proxy.http enabled true
  gsettings set org.gnome.system.proxy.https host "'192.168.112.1'"
  gsettings set org.gnome.system.proxy.https port 800

  those settings are currently not being used by the browser app.
  Accordingly I would like to request the addition of a feature to use the 
system proxy settings in the browser app.

  I have tested this on an by Aquaris E4.5 with Ubuntu 14.10 (r21).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1452291/+subscriptions

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

[Touch-packages] [Bug 1735160] Re: [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from bionic

[Iain Lane]

Andy asked me to have a look, so here's my initial feedback.

General
===

I'm not sure if these changes should be backported to Artful too, to
maintain the upgrade path for users transitioning off Xenial. Could you
please ask the SRU team?

Otherwise, the changes are risky but I think they should be in principle
okay.

The test cases and regression potential in the description here could do
with fleshing out a bit - could you do that please? For example,
snapcraft depends on pymacaroons - probably want to make sure that keeps
working. And it is supposed to be compatible, but that doesn't mean
there is no bug in the newer version - it is a regression potential IMO.

httmock
===

Since this is completely new and a no-change backport, I think it's
okay. Uploaded.

protobuf


I'm a bit worried about bugs coming from the use of 2to3 which is best
used as a starting point for a manual port, not for an automatic
conversion - how about taking the upstream patches instead?

https://github.com/google/protobuf/commit/f336d4b7a5c1d369ed508e513d482c885705e939

https://github.com/google/protobuf/commit/fe7d9379df3ce7c951bc0652a451413cff02382a

https://github.com/google/protobuf/commit/47ee4d37c17db8e97fe5b15cf918ab56ff93bb18

I tried the testsuite with this and it works after resolving some minor
conflicts.

pymacaroons
===

Seems okay if it's compatible - can you check with Colin please? I'm
happy to handle the actual upload.

py-macaroon-bakery
==

I'm not qualified to review this - maybe also check with Colin as the
maintainer? The patch says it's editing a generated file - is that
right?

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

** Changed in: httmock (Ubuntu)
 Assignee: (unassigned) => Andrea Azzarone (azzar1)

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

** Also affects: python-nacl (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

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

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

** Changed in: httmock (Ubuntu Xenial)
 Assignee: (unassigned) => Andrea Azzarone (azzar1)

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

Title:
  [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from
  bionic

Status in httmock package in Ubuntu:
  Fix Released
Status in protobuf package in Ubuntu:
  New
Status in pymacaroons package in Ubuntu:
  New
Status in python-nacl package in Ubuntu:
  New
Status in httmock source package in Xenial:
  In Progress
Status in protobuf source package in Xenial:
  New
Status in pymacaroons source package in Xenial:
  New
Status in python-nacl source package in Xenial:
  New

Bug description:
  [Impact]
  As part of allowing Ubuntu users to enable canonical-livepatch from 
software-properties GUI 
(https://wiki.ubuntu.com/SoftwareUpdates#Update_settings) we need to backport 
python3-macaroonbakery 0.0.6-1 [universe] from bionic. This will requires quite 
few changes:

  - backport httmock 1.2.6-1 [universe] from bionic - no httmock in xenial
  - backport pymacaroons 0.12.0-1 [universe] from bionic - xenial has 
0.9.2-0ubuntu1
  - SRU some changes in google-apputils-python - 
https://bugs.launchpad.net/ubuntu/+source/google-apputils-python/+bug/1735162
  - add python3-protobuf to python-protobuf 2.6.1-1.3 - Right now the python3 
package is not built.

  [Test case]
  - for python3-protobuf: $ python3 -c "import google.protobuf"
  - for python3-macaroonbakery: make sure all the tests pass

  [Regression Potential]
  - httmock, none has it's not in xenial
  - python3-protobuf, none has the python2 code was not edited
  TBC
  - pymacaroons, none has 0.12 is backward compatible with 0.9.2
  - python3-protobuf, none has it's not in xenial.

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

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