date:20180416

That's mostly because fixing bug 1702558 is a prerequisite.

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

Title:
  Enable support for libsoxr

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'd like to ask to enable support for libsoxr-based resamplers in the 
official Ubuntu packages for pulseaudio. The upstream already supports libsoxr 
and automatically detects its availability, so the only change really needed is 
to add the build dependency to debian/control.
   
  The resamplers based in libsoxr offer better quality and better performace 
while introducing more delay compared to the speex resamplers that are used by 
default. The resamplers are documented in the man pages of pulseaudio in Ubuntu 
16.04 but unfortunately are not enabled at build time ('pulseaudio 
--dump-resample-methods' doesn't list them). I've built local packages with 
libsoxr and verified that the resampler works as expected.

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

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

[Touch-packages] [Bug 1574746] Re: Enable support for libsoxr

2018-04-16 Thread Neo

Still not included in 18.04 delivery ...

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

Title:
  Enable support for libsoxr

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'd like to ask to enable support for libsoxr-based resamplers in the 
official Ubuntu packages for pulseaudio. The upstream already supports libsoxr 
and automatically detects its availability, so the only change really needed is 
to add the build dependency to debian/control.
   
  The resamplers based in libsoxr offer better quality and better performace 
while introducing more delay compared to the speex resamplers that are used by 
default. The resamplers are documented in the man pages of pulseaudio in Ubuntu 
16.04 but unfortunately are not enabled at build time ('pulseaudio 
--dump-resample-methods' doesn't list them). I've built local packages with 
libsoxr and verified that the resampler works as expected.

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

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

Re: [Touch-packages] [Bug 1763182] Re: remove landscape-common from minimal image

2018-04-16 Thread Steve Langasek

On Thu, Apr 12, 2018 at 06:00:46AM -, ChristianEhrhardt wrote:
> @Steve - just to be sure, in https://bazaar.launchpad.net/~vorlon
> /livecd-rootfs/lp.1763182/revision/1662 when removing landscape-common
> for minimization, would you need something like an apt autoremove to get
> rid of the dependencies it brought in before?

There is already an autoremove in the code further on.

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

Title:
  remove landscape-common from minimal image

Status in livecd-rootfs package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  In Progress

Bug description:
  The stated goal of minimal image is to strip out packages useful only
  to humans so that a smaller base can be used to build smaller
  applications running in clouds and in containers.

  To this end, please remove landscape-common as it pulls in a few
  python3 deps, and its goal is only to provide an entry in the dynamic
  MOTD that shows system statistics (disk usage, memory usage, etc) that
  a human would look at when logging in interactively.

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

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

[Touch-packages] [Bug 1704250] Re: ERROR

[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

** Changed in: xorg (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  ERROR

Status in xorg package in Ubuntu:
  Expired

Bug description:
  The system has a breakdown problem since the new update from ubuntu
  15.04, I would like to know how to repair it. From already thank you
  very much.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: i386
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Jul 13 22:20:10 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-62-generic, i686: installed
   bbswitch, 0.8, 4.4.0-66-generic, i686: installed
   bbswitch, 0.8, 4.4.0-75-generic, i686: installed
   bbswitch, 0.8, 4.4.0-83-generic, i686: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation G84 [GeForce 8600 GT] [10de:0402] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] NX8600GT-T2D256EZ 
[1462:0910]
  InstallationDate: Installed on 2017-02-09 (154 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  Lsusb:
   Bus 001 Device 004: ID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0b38:0010 Gear Head 107-Key Keyboard
   Bus 002 Device 002: ID 04f3:0230 Elan Microelectronics Corp. 3D Optical Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Gigabyte Technology Co., Ltd. GA-73VM-S2
  ProcEnviron:
   LANGUAGE=es_ES
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic 
root=UUID=73161ce2-6cf4-4d9d-8c08-a11a9e14405b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/07/2008
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4c
  dmi.board.name: GA-73VM-S2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4c:bd10/07/2008:svnGigabyteTechnologyCo.,Ltd.:pnGA-73VM-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-73VM-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-73VM-S2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Jul 13 22:17:49 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB+PS/2 Optical Mouse MOUSE, id 8
   inputHID 0b38:0010KEYBOARD, id 9
   inputHID 0b38:0010KEYBOARD, id 10
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.2
  xserver.video_driver: nouveau

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

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

[Touch-packages] [Bug 1679704] Re: libvirt profile is blocking global setrlimit despite having no rlimit rule

2018-04-16 Thread ChristianEhrhardt

Test kernel somewhere that supports PPC64?

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

Title:
  libvirt profile is blocking global setrlimit despite having no rlimit
  rule

Status in The Ubuntu-power-systems project:
  In Progress
Status in apparmor package in Ubuntu:
  In Progress

Bug description:
  Hi,
  while debugging bug 1678322 I was running along apparmor issues.
  Thanks to jjohansen we debugged some of it and eventually I was asked to 
report to a bug.

  Symptom:
  [ 8976.950635] audit: type=1400 audit(1491310016.224:48): apparmor="DENIED" 
operation="setrlimit" profile="/usr/sbin/libvirtd" pid=10034 comm="libvirtd" 
rlimit=memlock value=1610612736

  But none of the profiles has any rlimit statement in it:
  $ grep -Hirn limit /etc/apparmor*
  /etc/apparmor.d/sbin.dhclient:58:  # such, if the dhclient3 daemon is 
subverted, this effectively limits it to
  /etc/apparmor.d/abstractions/ubuntu-helpers:16:# Limitations:
  /etc/apparmor.d/abstractions/ubuntu-helpers:64:  # in limited libraries so 
glibc's secure execution should be enough to not
  /etc/apparmor.d/cache/.features:13:rlimit {mask {cpu fsize data stack core 
rss nproc nofile memlock as locks sigpending msgqueue nice rtprio rttime

  
  The profile contains a child profile which makes reading the dumps a bit 
painful, but I'll attach them anyway for you to take a look.
  To "recreate" if needed check out bug 1678322 - TL;DR hot-add some VFs via 
libvirt.

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

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

[Touch-packages] [Bug 1749692] Re: My Resolution is verry Low

[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

** Changed in: xorg (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  My Resolution is verry Low

Status in xorg package in Ubuntu:
  Expired

Bug description:
  My monitor is HD but the system only shows low resolution.The highest is 
1024x768.
  What can I do to get more resolution options?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 15 10:04:20 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4th Generation Core Processor Family Integrated Graphics 
Controller [8086:041e] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 4th Generation Core Processor Family 
Integrated Graphics Controller [103c:0266]
  InstallationDate: Installed on 2018-02-06 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Hewlett-Packard HP 402 G1 SFF Business PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=a8d31c50-2e57-46fd-bbfb-a8f11d427e0a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/03/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0405
  dmi.board.asset.tag: BRJ448DM7Q
  dmi.board.name: 0266
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 1.02
  dmi.chassis.asset.tag: BRJ448DM7Q
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: 1.02
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0405:bd04/03/2014:svnHewlett-Packard:pnHP402G1SFFBusinessPC:pvr1.02:rvnHewlett-Packard:rn0266:rvr1.02:cvnHewlett-Packard:ct3:cvr1.02:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP 402 G1 SFF Business PC
  dmi.product.version: 1.02
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1704409] Re: Flickering screen on ubuntu 16.04.2 Lenovo B70

[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

** Changed in: xorg (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Flickering screen on ubuntu 16.04.2 Lenovo B70

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Tested both unity & ubuntu-gnome on 16.04.2
  and both are constantly flickering from login to desktop and on LIVEusb on a 
product: 

  Haswell-ULT Integrated Graphics Controller and driver=i915

  and kernel: Linux fernand-Lenovo-B70-80 4.8.0-58-generic
  #63~16.04.1-Ubuntu SMP Mon Jun 26 18:08:51 UTC 2017 x86_64 x86_64
  x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.9
  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 Jul 14 17:18:12 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:3987]
  InstallationDate: Installed on 2017-07-14 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp.
   Bus 001 Device 003: ID 0bda:579a Realtek Semiconductor Corp.
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MR
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-58-generic 
root=UUID=c471367f-a9a5-4e15-a987-f7b614634a1d ro quiet splash 
"acpi_osi=Windows 2013" vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: D1CN06WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo B70-80
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo B70-80
  dmi.modalias: 
dmi:bvnLENOVO:bvrD1CN06WW:bd05/18/2015:svnLENOVO:pn80MR:pvrLenovoB70-80:rvnLENOVO:rnLenovoB70-80:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoB70-80:
  dmi.product.name: 80MR
  dmi.product.version: Lenovo B70-80
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  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 Jul 14 17:06:37 2017
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5921
   vendor CMN
  xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1

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

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

[Touch-packages] [Bug 1718554] Re: Need updated libimobiledevice to mount IOS 11 devices

2018-04-16 Thread William F Hammond

I could not replicate for my latest photos this evening what I reported
in #8.

Yet by fiddling in various ways, after a reboot I was able to coax
shotwell to import the photos on the iPhone. I then had command line
access to those photos in the location where shotwell dropped them.

As for /run/user/1000/gvfs: the robotic gphoto name appeared there on
and off, but when it was there it appeared to be empty from the command
line.

As a comment on my #8, it would seem that the appearance of the robotic
gphoto name in /run/user/1000/gvfs has something to do with a prior
running of shotwell.  (The shotwell executable in Xenial links to two
gphoto runtime libraries.)

I don't know what is going on.

It's certainly less than transparent access through the lightning port
to the usb file system on the iPhone.

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

Title:
  Need updated libimobiledevice to mount IOS 11 devices

Status in libimobiledevice package in Ubuntu:
  Fix Released

Bug description:
  After upgrading to IOS 11, I stopped being able to mount my ipad in
  ubuntu.

  The relevant log lines from gvfs-afc are:

  gvfsd[1855]: afc: Added new job source 0x55802a00f130 (GVfsBackendAfc)
  gvfsd[1855]: afc: Queued new job 0x558029ff36d0 (GVfsJobMount)
  gvfsd[1855]: afc: Lockdown client try #0
  gvfsd[1855]: afc: Got lockdown error '-3' while doing 'initial paired client'
  gvfsd[1855]: afc: send_reply(0x558029ff36d0), failed=1 (Unhandled Lockdown 
error (-3))

  The fix is here in the upstream github:

  
https://github.com/libimobiledevice/libimobiledevice/commit/5a85432719fb3d18027d528f87d2a44b76fd3e12

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

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

[Touch-packages] [Bug 1718554] Re: Need updated libimobiledevice to mount IOS 11 devices

2018-04-16 Thread William F Hammond

My last sentence in #9 should be:

It's certainly less than transparent usb access through the lightning
port to the file system on the iPhone.

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

Title:
  Need updated libimobiledevice to mount IOS 11 devices

Status in libimobiledevice package in Ubuntu:
  Fix Released

Bug description:
  After upgrading to IOS 11, I stopped being able to mount my ipad in
  ubuntu.

  The relevant log lines from gvfs-afc are:

  gvfsd[1855]: afc: Added new job source 0x55802a00f130 (GVfsBackendAfc)
  gvfsd[1855]: afc: Queued new job 0x558029ff36d0 (GVfsJobMount)
  gvfsd[1855]: afc: Lockdown client try #0
  gvfsd[1855]: afc: Got lockdown error '-3' while doing 'initial paired client'
  gvfsd[1855]: afc: send_reply(0x558029ff36d0), failed=1 (Unhandled Lockdown 
error (-3))

  The fix is here in the upstream github:

  
https://github.com/libimobiledevice/libimobiledevice/commit/5a85432719fb3d18027d528f87d2a44b76fd3e12

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

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

[Touch-packages] [Bug 1764614] Re: package libperl5.26 5.26.0-8ubuntu1 [modified: usr/share/doc/libperl5.26/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/l

** Tags removed: need-duplicate-check

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

Title:
  package libperl5.26 5.26.0-8ubuntu1 [modified:
  usr/share/doc/libperl5.26/changelog.Debian.gz] failed to
  install/upgrade: trying to overwrite shared
  '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different
  from other instances of package libperl5.26:amd64

Status in perl package in Ubuntu:
  New

Bug description:
  Gestionnaire de mise à jour
  Echec de traitement du paquet
  l'installation ou la desinstallation du paquet a échoué

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libperl5.26 5.26.0-8ubuntu1 [modified: 
usr/share/doc/libperl5.26/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  Date: Tue Apr 17 04:25:22 2018
  DuplicateSignature:
   package:libperl5.26:5.26.0-8ubuntu1 [modified: 
usr/share/doc/libperl5.26/changelog.Debian.gz]
   Unpacking libperl5.26:amd64 (5.26.0-8ubuntu1.1) over (5.26.0-8ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libperl5.26_5.26.0-8ubuntu1.1_amd64.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other 
instances of package libperl5.26:amd64
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other 
instances of package libperl5.26:amd64
  InstallationDate: Installed on 2017-11-15 (152 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: perl
  Title: package libperl5.26 5.26.0-8ubuntu1 [modified: 
usr/share/doc/libperl5.26/changelog.Debian.gz] failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', 
which is different from other instances of package libperl5.26:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1764614] [NEW] package libperl5.26 5.26.0-8ubuntu1 [modified: usr/share/doc/libperl5.26/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc

2018-04-16 Thread Mike2A

Public bug reported:

Gestionnaire de mise à jour
Echec de traitement du paquet
l'installation ou la desinstallation du paquet a échoué

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libperl5.26 5.26.0-8ubuntu1 [modified: 
usr/share/doc/libperl5.26/changelog.Debian.gz]
ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
Uname: Linux 4.13.0-38-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.8
Architecture: amd64
Date: Tue Apr 17 04:25:22 2018
DuplicateSignature:
 package:libperl5.26:5.26.0-8ubuntu1 [modified: 
usr/share/doc/libperl5.26/changelog.Debian.gz]
 Unpacking libperl5.26:amd64 (5.26.0-8ubuntu1.1) over (5.26.0-8ubuntu1) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libperl5.26_5.26.0-8ubuntu1.1_amd64.deb (--unpack):
  trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', 
which is different from other instances of package libperl5.26:amd64
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other 
instances of package libperl5.26:amd64
InstallationDate: Installed on 2017-11-15 (152 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: perl
Title: package libperl5.26 5.26.0-8ubuntu1 [modified: 
usr/share/doc/libperl5.26/changelog.Debian.gz] failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', 
which is different from other instances of package libperl5.26:amd64
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package artful package-conflict

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

Title:
  package libperl5.26 5.26.0-8ubuntu1 [modified:
  usr/share/doc/libperl5.26/changelog.Debian.gz] failed to
  install/upgrade: trying to overwrite shared
  '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different
  from other instances of package libperl5.26:amd64

Status in perl package in Ubuntu:
  New

Bug description:
  Gestionnaire de mise à jour
  Echec de traitement du paquet
  l'installation ou la desinstallation du paquet a échoué

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libperl5.26 5.26.0-8ubuntu1 [modified: 
usr/share/doc/libperl5.26/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  Date: Tue Apr 17 04:25:22 2018
  DuplicateSignature:
   package:libperl5.26:5.26.0-8ubuntu1 [modified: 
usr/share/doc/libperl5.26/changelog.Debian.gz]
   Unpacking libperl5.26:amd64 (5.26.0-8ubuntu1.1) over (5.26.0-8ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libperl5.26_5.26.0-8ubuntu1.1_amd64.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other 
instances of package libperl5.26:amd64
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other 
instances of package libperl5.26:amd64
  InstallationDate: Installed on 2017-11-15 (152 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: perl
  Title: package libperl5.26 5.26.0-8ubuntu1 [modified: 
usr/share/doc/libperl5.26/changelog.Debian.gz] failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', 
which is different from other instances of package libperl5.26:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1641284] Re: libatk-adaptor breaks down the LibreOffice TexMaths extension

** Changed in: at-spi2-atk (Debian)
   Status: New => Fix Released

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

Title:
  libatk-adaptor breaks down the LibreOffice TexMaths extension

Status in at-spi2-atk package in Ubuntu:
  Confirmed
Status in at-spi2-atk package in Debian:
  Fix Released

Bug description:
  Package: libatk-adaptor 2.18.1-2ubuntu1
  System: Ubuntu 16.04.1 LTS (Xenial Xerus)

  If the package libatk-adaptor is installed on Ubuntu (as a depency of
  gnome-orca for example), it breaks down the LibreOffice TexMaths
  extension. TexMaths is a popular extension used to enter / edit LaTeX
  equations on LibreOffice (see http://roland65.free.fr/texmaths).

  Step to reproduce the bug:

  1. It is assumed that LibreOffice 5.1.4 (with at least the Writer and
  Draw components) is installed on Ubuntu. It is also assumed that
  libatk-adaptor is installed.

  2. Install texlive:
  sudo apt-get install texlive

  3. Download and install the TexMaths extension (version 0.42) from
  there: https://sourceforge.net/projects/texmaths/files/0.42/

  4. Create a new empty Writer document, then click on the Pi icon (this
  is the TexMaths icon) and in the window that opens, type: 'x(t)+y(t)'
  (without the quotes), then click on the LaTeX button. This generates
  an SVG image of the 'x(t)+y(t)' equation.

  5. Select the SVG image of the equation by left clicking on it. Then
  click on the Pi icon. Now, instead of editing the equation, an error
  message is displayed: "The selected object is not a TexMaths
  equation... Please unselect it and call the macro again...".

  6. Now, right click on the SVG image and select the 'Description' menu
  voice. In the window that opens, the description is empty and does not
  contain the equation text, as it should.

  7. Now purge (and not just remove) the libatk-adaptor package:

  sudo apt-get purge libatk-adaptor

  then logout and login and repeat the steps 4, 5, and 6: everything is
  OK and the equation can be edited as usual.

  Another way to remove the bug instead of purging libatk-adaptor is to
  rename the file: /etc/X11/Xsession.d/90atk-adaptor to
  /etc/X11/Xsession.d/90atk-adaptor.orig . Then logout and login.

  Note there is another bug #1584795 that relates libatk-adaptor and
  LibreOffice, see there https://bugs.launchpad.net/ubuntu/+source/at-
  spi2-atk/+bug/1584795

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1641284/+subscriptions

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

[Touch-packages] [Bug 1764414] Re: + and - buttons are not themed in LibreOffice

** Changed in: ubuntu-themes (Ubuntu)
   Importance: Undecided => Low

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

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

** Changed in: ubuntu-themes
   Importance: Undecided => Low

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

Title:
  + and - buttons are not themed in LibreOffice

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

Bug description:
  Steps:
  1. Start Writer
  2. Go to Tools -> Options -> LibreOffice -> General
  3. You will see an input field with + and - buttons

  The buttons are not properly themed in Ambiance:
  1. The - button has no left border
  2. The + button has an extra right border
  3. There is no hover effect (only touching without pressing the button)

  All those three issues do not exist in Adwaita.

  See the attached screencast.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180328-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 16 15:37:38 2018
  InstallationDate: Installed on 2017-10-02 (195 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to bionic on 2018-03-27 (19 days ago)

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

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

[Touch-packages] [Bug 1764414] Re: + and - buttons are not themed in LibreOffice

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

Title:
  + and - buttons are not themed in LibreOffice

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

Bug description:
  Steps:
  1. Start Writer
  2. Go to Tools -> Options -> LibreOffice -> General
  3. You will see an input field with + and - buttons

  The buttons are not properly themed in Ambiance:
  1. The - button has no left border
  2. The + button has an extra right border
  3. There is no hover effect (only touching without pressing the button)

  All those three issues do not exist in Adwaita.

  See the attached screencast.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180328-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 16 15:37:38 2018
  InstallationDate: Installed on 2017-10-02 (195 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to bionic on 2018-03-27 (19 days ago)

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

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

[Touch-packages] [Bug 1764518] Re: package pulseaudio-module-bluetooth 1:8.0-0ubuntu3.8 [origin: Ubuntu] failed to install/upgrade: problemas com dependências - a deixar por configurar [The libpam-sys

** Summary changed:

- package pulseaudio-module-bluetooth 1:8.0-0ubuntu3.8 [origin: Ubuntu] failed 
to install/upgrade: problemas com dependências - a deixar por configurar
+ package pulseaudio-module-bluetooth 1:8.0-0ubuntu3.8 [origin: Ubuntu] failed 
to install/upgrade: problemas com dependências - a deixar por configurar [The 
libpam-systemd: amd64 package is not yet configured.]

** Tags added: xenial

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

Title:
  package pulseaudio-module-bluetooth 1:8.0-0ubuntu3.8 [origin: Ubuntu]
  failed to install/upgrade: problemas com dependências - a deixar por
  configurar [The libpam-systemd: amd64 package is not yet configured.]

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  On system startup

  ProblemType: Package
  DistroRelease: elementary 0.4.1
  Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3.8 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  antonio1431 F pulseaudio
  Date: Mon Apr 16 00:50:52 2018
  ErrorMessage: problemas com dependências - a deixar por configurar
  InstallationDate: Installed on 2018-04-15 (0 days ago)
  InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20180214)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: pulseaudio
  Title: package pulseaudio-module-bluetooth 1:8.0-0ubuntu3.8 [origin: Ubuntu] 
failed to install/upgrade: problemas com dependências - a deixar por configurar
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/15/2009
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: V5.10
  dmi.board.name: Satellite U300-130
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrV5.10:bd01/15/2009:svnTOSHIBA:pnSatelliteU300-130:pvrPSU30E-03D013PT:rvnTOSHIBA:rnSatelliteU300-130:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A:
  dmi.product.name: Satellite U300-130
  dmi.product.version: PSU30E-03D013PT
  dmi.sys.vendor: TOSHIBA

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

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

[Touch-packages] [Bug 1759468] Re: gnome-control-center (11) gtk_style_context_clear_property_cache → gtk_css_widget_node_update_style → gtk_css_node_ensure_style → gtk_css_node_ensure_style → gtk_css

2018-04-16 Thread Jeremy Bicha

I am unsubscribing ubuntu-sponsors since this has been uploaded to the
bionic queue.

Actually, the GTK devs just released 3.22.30 which I have also uploaded
to the queue so this fix is in the queue twice now!

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

Title:
  gnome-control-center (11) gtk_style_context_clear_property_cache →
  gtk_css_widget_node_update_style → gtk_css_node_ensure_style →
  gtk_css_node_ensure_style → gtk_css_node_validate_internal

Status in gnome-control-center package in Ubuntu:
  In Progress
Status in gtk+3.0 package in Ubuntu:
  In Progress

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-control-center.  This problem was most recently seen with package version 
1:3.28.0-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/6b1f4dd86167bf5eb53ddca8469b5084208ddd22 
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/gnome-control-center/+bug/1759468/+subscriptions

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

[Touch-packages] [Bug 1764548] Re: Update gtk+3.0 to 3.22.30 for bionic

2018-04-16 Thread Jeremy Bicha

** Description changed:

  New upstream bugfix release in the stable 3.22.x series.
  
  gtk3 is part of the GNOME microrelease exception and we did an SRU with
  it for Ubuntu 17.10.
  
  https://gitlab.gnome.org/GNOME/gtk/blob/gtk-3-22/NEWS
  https://gitlab.gnome.org/GNOME/gtk/commits/gtk-3-22
  https://gitlab.gnome.org/GNOME/gtk/compare/3.22.30...3.22.29
  
  Testing Done
  
- Pending
+ Built successfully on amd64. Apps seem to run ok after installing it.

** Description changed:

  New upstream bugfix release in the stable 3.22.x series.
  
  gtk3 is part of the GNOME microrelease exception and we did an SRU with
  it for Ubuntu 17.10.
  
  https://gitlab.gnome.org/GNOME/gtk/blob/gtk-3-22/NEWS
  https://gitlab.gnome.org/GNOME/gtk/commits/gtk-3-22
- https://gitlab.gnome.org/GNOME/gtk/compare/3.22.30...3.22.29
+ https://gitlab.gnome.org/GNOME/gtk/compare/3.22.29...3.22.30
  
  Testing Done
  
  Built successfully on amd64. Apps seem to run ok after installing it.

** Description changed:

  New upstream bugfix release in the stable 3.22.x series.
  
- gtk3 is part of the GNOME microrelease exception and we did an SRU with
- it for Ubuntu 17.10.
+ gtk3 is part of the GNOME microrelease exception. (For Ubuntu 17.10, we
+ did an earlier gtk3 point release SRU using the GNOME microrelease
+ exception.)
  
  https://gitlab.gnome.org/GNOME/gtk/blob/gtk-3-22/NEWS
  https://gitlab.gnome.org/GNOME/gtk/commits/gtk-3-22
  https://gitlab.gnome.org/GNOME/gtk/compare/3.22.29...3.22.30
  
  Testing Done
  
  Built successfully on amd64. Apps seem to run ok after installing it.

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

Title:
  Update gtk+3.0 to 3.22.30 for bionic

Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  New upstream bugfix release in the stable 3.22.x series.

  gtk3 is part of the GNOME microrelease exception. (For Ubuntu 17.10,
  we did an earlier gtk3 point release SRU using the GNOME microrelease
  exception.)

  https://gitlab.gnome.org/GNOME/gtk/blob/gtk-3-22/NEWS
  https://gitlab.gnome.org/GNOME/gtk/commits/gtk-3-22
  https://gitlab.gnome.org/GNOME/gtk/compare/3.22.29...3.22.30

  Testing Done
  
  Built successfully on amd64. Apps seem to run ok after installing it.

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

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

[Touch-packages] [Bug 1760128] Re: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

Well Launchpad kept timing out when I tried to edit the description so
here's the SRU info.

[Impact]
avahi-dnsconfd fails to upgrade causing lots of bug reports.

[Test Case]
1) sudo apt install avahi-daemon=0.6.32~rc+dfsg-1ubuntu2 
avahi-dnsconfd=0.6.32~rc+dfsg-1ubuntu2 avahi-utils=0.6.32~rc+dfsg-1ubuntu2
2) in a separate terminal run 'while true; do avahi-browse -a -t; done
3) sudo apt upgrade avahi-daemon avahi-dnsconfd avahi-utils

With the version of the package from -proposed you should not receive a
crash report and should see the following instead:

Preparing to unpack avahi-dnsconfd_0.6.32~rc+dfsg-1ubuntu3_amd64.deb ...
Job for avahi-daemon.socket canceled.
dpkg: warning: subprocess old pre-removal script returned error exit status 1
dpkg: trying script from the new package instead ...
dpkg: ... it looks like that went OK

[Regression Potential]
This has been in bionic for a while with no regressions.

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

Title:
  package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 1

Status in avahi package in Ubuntu:
  Fix Released
Status in avahi source package in Xenial:
  In Progress

Bug description:
  Ubuntu Update 30.03.18

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Mar 30 16:32:50 2018
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-01-31 (788 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160131)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: avahi
  Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1763926] Re: receiving this messagem after reboot crash and use noapic nolapic acpi=offpackage avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: sub-processo novo

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

** This bug has been marked a duplicate of bug 1760128
   package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1

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

Title:
  receiving this messagem after reboot crash and use noapic nolapic
  acpi=offpackage avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to
  install/upgrade: sub-processo novo script pre-removal retornou estado
  de saída de erro 1

Status in avahi package in Ubuntu:
  New

Bug description:
  receiving this messagem after reboot crash and use noapic nolapic acpi=off at 
grub config
  package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: 
sub-processo novo script pre-removal retornou estado de saída de erro 1

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: i386
  Date: Sat Apr 14 08:03:43 2018
  ErrorMessage: sub-processo novo script pre-removal retornou estado de saída 
de erro 1
  InstallationDate: Installed on 2018-04-14 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.4 LTS "Xenial Xerus" - Release i386 
(20180228)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: avahi
  Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to 
install/upgrade: sub-processo novo script pre-removal retornou estado de saída 
de erro 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1764181] Re: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: подпроцесс новый сценарий pre-removal возвратил код ошибки 1

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

** This bug has been marked a duplicate of bug 1760128
   package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1

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

Title:
  package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to
  install/upgrade: подпроцесс новый сценарий pre-removal возвратил код
  ошибки 1

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  Unfortunately, no extra information. It had just appeared.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Mon Apr 16 00:06:15 2018
  ErrorMessage: подпроцесс новый сценарий pre-removal возвратил код ошибки 1
  InstallationDate: Installed on 2018-03-08 (38 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: avahi
  Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to 
install/upgrade: подпроцесс новый сценарий pre-removal возвратил код ошибки 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 237721] Re: Secure attention key

** Changed in: kde-baseapps
   Status: Confirmed => Unknown

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

Title:
  Secure attention key

Status in gdm:
  New
Status in KDE Base:
  Unknown
Status in Light Display Manager:
  Won't Fix
Status in Unity System Compositor:
  New
Status in gdm package in Ubuntu:
  Confirmed
Status in kdebase-workspace package in Ubuntu:
  Won't Fix
Status in lightdm package in Ubuntu:
  Won't Fix
Status in ubuntu-meta package in Ubuntu:
  Invalid
Status in unity-system-compositor package in Ubuntu:
  New
Status in xdm package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: gdm

  In many environments computers are left unattended (e.g. schools,
  libraries, etc) and people can launch applications which mimic the
  look-and-feel of the login application (GDM) in order to get the users
  username and password.

  This is called login spoofing.
  * http://en.wikipedia.org/wiki/Login_spoofing

  Login spoofing can be prevented by using a secure attention key which is a 
key combination pressed before the user login to launch the password request 
dialog. This key can only be seen by the kernel, and not sniffed by any 
application.
  * http://en.wikipedia.org/wiki/Secure_attention_key

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

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

[Touch-packages] [Bug 1760128] Re: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

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

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

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

** Changed in: avahi (Ubuntu Xenial)
 Assignee: (unassigned) => Brian Murray (brian-murray)

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

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

Title:
  package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 1

Status in avahi package in Ubuntu:
  Fix Released
Status in avahi source package in Xenial:
  In Progress

Bug description:
  Ubuntu Update 30.03.18

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Mar 30 16:32:50 2018
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-01-31 (788 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160131)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: avahi
  Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1763100] Re: FONT="x/y/z" is not applied due to setupcon script bug

** Tags added: bionic patch

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

Title:
  FONT="x/y/z" is not applied due to setupcon script bug

Status in console-setup package in Ubuntu:
  New

Bug description:
  apt-cache policy console-setup
  console-setup:
Installed: 1.178ubuntu1
Candidate: 1.178ubuntu1
Version table:
   *** 1.178ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main i386 Packages
  100 /var/lib/dpkg/status

  On 18.04 I wanted to set the TTY font to use a Powerline font. Despite
  being able to set the font manually it wasn't being set at boot-time.

  /etc/default/console-setup contains:

  FONT="/usr/local/share/fonts/ter-powerline-v22n.psf.gz"

  "setupcon -v -f" reported an error:

  putfont: KDFONTOP: Invalid argument

  due to passing the font filename twice:

  executing setfont -C /dev/tty1 /usr/local/share/fonts/ter-powerline-
  v22n.psf.gz /usr/local/share/fonts/ter-powerline-v22n.psf.gz.

  The problem is in /bin/setupcon where the collecting variable
  FONTFILES has the font added twice, once at the top of the for loop

  FONTFILES="$FONTFILES `findfile $fontdir $f`"

  and again at the bottom

  FONTFILES="$FONTFILES $RES"

  Removing the first assignment fixes it.

  FONTFILES=''
  echo "DEBUG: FONT=$FONT"
  if [ "$FONT" ]; then
  for f in $FONT; do
echo "DEBUG: for loop"
  FONTFILES="$FONTFILES `findfile $fontdir $f`"
  RES=`findfile $fontdir $f`
  if [ -z "$RES" ]; then
  fdec="${f%.gz}"
  RES=`findfile $fontdir $fdec`
  fi
  FONTFILES="$FONTFILES $RES"
  done
  fi
  FONTFILES=`echo $FONTFILES` # remove extra spaces

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

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

[Touch-packages] [Bug 1764551] Re: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1

** Tags removed: need-duplicate-check

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 1

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  I have no prior idea it showed me that there's some error while
  upgrading the system.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  Date: Mon Apr 16 23:00:44 2018
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-02-14 (61 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~rc1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to bionic on 2018-04-16 (0 days ago)

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

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

[Touch-packages] [Bug 1764551] [NEW] package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1

2018-04-16 Thread Tathagata Basu

Public bug reported:

I have no prior idea it showed me that there's some error while
upgrading the system.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: ca-certificates 20180409
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
Date: Mon Apr 16 23:00:44 2018
ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2018-02-14 (61 days ago)
InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.14-4
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu1
 apt  1.6~rc1
SourcePackage: ca-certificates
Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 1
UpgradeStatus: Upgraded to bionic on 2018-04-16 (0 days ago)

** Affects: ca-certificates (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 1

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  I have no prior idea it showed me that there's some error while
  upgrading the system.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  Date: Mon Apr 16 23:00:44 2018
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-02-14 (61 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~rc1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to bionic on 2018-04-16 (0 days ago)

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

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

[Touch-packages] [Bug 1764548] [NEW] Update gtk+3.0 to 3.22.30 for bionic

2018-04-16 Thread Jeremy Bicha

Public bug reported:

New upstream bugfix release in the stable 3.22.x series.

gtk3 is part of the GNOME microrelease exception and we did an SRU with
it for Ubuntu 17.10.

https://gitlab.gnome.org/GNOME/gtk/blob/gtk-3-22/NEWS
https://gitlab.gnome.org/GNOME/gtk/commits/gtk-3-22
https://gitlab.gnome.org/GNOME/gtk/compare/3.22.30...3.22.29

Testing Done

Pending

** Affects: gtk+3.0 (Ubuntu)
 Importance: Medium
 Status: Triaged


** Tags: bionic upgrade-software-version

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

Title:
  Update gtk+3.0 to 3.22.30 for bionic

Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  New upstream bugfix release in the stable 3.22.x series.

  gtk3 is part of the GNOME microrelease exception and we did an SRU
  with it for Ubuntu 17.10.

  https://gitlab.gnome.org/GNOME/gtk/blob/gtk-3-22/NEWS
  https://gitlab.gnome.org/GNOME/gtk/commits/gtk-3-22
  https://gitlab.gnome.org/GNOME/gtk/compare/3.22.30...3.22.29

  Testing Done
  
  Pending

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

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

[Touch-packages] [Bug 1764312] Re: fails to start in Bionic

2018-04-16 Thread Seth Arnold

Hello Tom, can you please provide the output of

sudo apparmor_parser --replace /etc/apparmor.d/usr.lib.snapd.snap-
confine.real

Thanks

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

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

Title:
  fails to start in Bionic

Status in apparmor package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New

Bug description:
  $ systemctl status apparmor
  ● apparmor.service - AppArmor initialization
 Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Mon 2018-04-16 07:46:13 BST; 1h 
10min ago
   Docs: man:apparmor(7)
 http://wiki.apparmor.net/
Process: 635 ExecStart=/etc/init.d/apparmor start (code=exited, status=123)
   Main PID: 635 (code=exited, status=123)

  Apr 16 07:46:12 ev34 apparmor[635]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
  Apr 16 07:46:12 ev34 apparmor[635]: AppArmor parser error for 
/etc/apparmor.d/usr.lib.snapd.snap-confine.real in /etc/ap
  Apr 16 07:46:13 ev34 apparmor[635]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  Apr 16 07:46:13 ev34 apparmor[635]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
  Apr 16 07:46:13 ev34 apparmor[635]: AppArmor parser error for 
/etc/apparmor.d/usr.lib.snapd.snap-confine.real in /etc/ap
  Apr 16 07:46:13 ev34 apparmor[635]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  Apr 16 07:46:13 ev34 apparmor[635]:...fail!
  Apr 16 07:46:13 ev34 systemd[1]: apparmor.service: Main process exited, 
code=exited, status=123/n/a
  Apr 16 07:46:13 ev34 systemd[1]: apparmor.service: Failed with result 
'exit-code'.
  Apr 16 07:46:13 ev34 systemd[1]: Failed to start AppArmor initialization.

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

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

Re: [Touch-packages] [Bug 1763534] Re: ifconfig -s (or -a -s) only outputs 8 characters of the interface name, when interfaces are 10+ characters.

2018-04-16 Thread Steve Langasek

On Sat, Apr 14, 2018 at 12:51:49AM -, Mike Pontillo wrote:
> Note: if you are using a Xenial based MAAS that has not been patched to
> use `ip` instead, and you use it to commission on Bionic, it will fail
> due to this issue.

Indeed.  Is this something that would be fixed in an SRU of maas to xenial
in the near term?  I think that is ultimately the right solution, but if
it's not going to land soon, we would certainly look at restoring ifconfig
compatibility.

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

Title:
  ifconfig -s (or -a -s) only outputs 8 characters of the interface
  name, when interfaces are 10+ characters.

Status in net-tools package in Ubuntu:
  Confirmed
Status in net-tools source package in Bionic:
  Confirmed

Bug description:
  When executing ifconfig, it outputs the whole 10 characters of the
  interface name. However, when using ifconfig -s (or ifconfig -a -s) it
  doesn't include all the name of the interface (or 10+ characters).
  Instead, it outputs only 8 characters of the interface.

  ubuntu@dradis:~$ ifconfig -a
  enP2p1s0f0: flags=4163  mtu 1500
  inet 10.245.71.108  netmask 255.255.248.0  broadcast 10.245.71.255
  inet6 fe80::ae1f:6bff:fe09:c052  prefixlen 64  scopeid 0x20
  ether ac:1f:6b:09:c0:52  txqueuelen 1000  (Ethernet)
  RX packets 154570  bytes 229998298 (229.9 MB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 61080  bytes 6131460 (6.1 MB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  enP2p1s0f1: flags=4098  mtu 1500
  ether ac:1f:6b:09:c0:53  txqueuelen 1000  (Ethernet)
  RX packets 0  bytes 0 (0.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 0  bytes 0 (0.0 B)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  
  ubuntu@dradis:~$ ifconfig -a -s
  Iface  MTURX-OK RX-ERR RX-DRP RX-OVRTX-OK TX-ERR TX-DRP TX-OVR Flg
  enP2p1s0  1500   154607  0  0 0 61101  0  0  0 
BMRU
  enP2p1s0  15000  0  0 0 0  0  0  0 BM

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

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

[Touch-packages] [Bug 1764533] [NEW] package ca-certificates 20180409 failed to install/upgrade: Unterprozess installed ca-certificates package post-installation script gab den Fehler-Ausgangsstatus 2

2018-04-16 Thread Kitsab

Public bug reported:

Hello,

after apt-get update && apt-get upgrade -y an error appeared with CA-
certificates. While apt-get upgrade process there was a terminal entry
which certs I trust and I've got to select them manually (all mozilla
certs). Mozilla Firefox is working anyway.

Best regards

Kitsab

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: ca-certificates 20180409
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
Date: Mon Apr 16 23:10:31 2018
ErrorMessage: Unterprozess installed ca-certificates package post-installation 
script gab den Fehler-Ausgangsstatus 24 zurück
InstallationDate: Installed on 2015-02-14 (1157 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.14-4
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu1
 apt  1.6~beta1
SourcePackage: ca-certificates
Title: package ca-certificates 20180409 failed to install/upgrade: Unterprozess 
installed ca-certificates package post-installation script gab den 
Fehler-Ausgangsstatus 24 zurück
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ca-certificates (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package ca-certificates 20180409 failed to install/upgrade:
  Unterprozess installed ca-certificates package post-installation
  script gab den Fehler-Ausgangsstatus 24 zurück

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  Hello,

  after apt-get update && apt-get upgrade -y an error appeared with CA-
  certificates. While apt-get upgrade process there was a terminal entry
  which certs I trust and I've got to select them manually (all mozilla
  certs). Mozilla Firefox is working anyway.

  Best regards

  Kitsab

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  Date: Mon Apr 16 23:10:31 2018
  ErrorMessage: Unterprozess installed ca-certificates package 
post-installation script gab den Fehler-Ausgangsstatus 24 zurück
  InstallationDate: Installed on 2015-02-14 (1157 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: 
Unterprozess installed ca-certificates package post-installation script gab den 
Fehler-Ausgangsstatus 24 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1763273] Re: kernel panic in Radeon driver while screen blank

2018-04-16 Thread Chris Darroch

One further historical detail: when these machines were running 14.04.3
and we made the mistake of accepting the HardWare Enablement (HWE)
upgrade:

https://wiki.ubuntu.com/1404_HWE_EOL

which replaced the old fglrx driver with the radeon one, that's when we
first encountered this unable-to-unblank problem.

Fortunately, at that time we were able to roll back Xorg to 1.16 and
keep things sort-of working:

https://askubuntu.com/questions/815591/ubuntu-14-04-5-16-04-and-newer-on-amd-graphics
https://askubuntu.com/questions/676216/downgrade-xorg-server

When we performed a clean, full re-install with 16.04 we were hoping
this problem would be resolved, but as I've documented here it continues
to affect the systems.

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

Title:
  kernel panic in Radeon driver while screen blank

Status in linux package in Ubuntu:
  Incomplete
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I maintain a set of older kiosks running a mix of stock Ubuntu 14.04
  LTS and 16.04.  As we have gradually transitioned them to 16.04, we
  have noticed that the machines running 16.04.1 now regularly exhibit
  problems restoring from the blank screen which appears after a period
  of inactivity.

  This only occurs on the machines where we've installed 16.04.  All of
  the 16.04.1 installations are "fresh", that is, complete re-installs
  from scratch, and we install all security and other updates on a
  regular basis.  This problem has persisted right from the beginning
  when we started using 16.04.

  Following a period of user inactivity, the screen goes blank; this is,
  of course, expected.  When the user tries to restore the session by
  typing a key or moving the mouse, one of three outcomes occurs.

  Sometimes, the session restores normally.  Other times, the screen
  remains blank regardless of all normal keyboard input, until a magic
  SysRq  sequence is performed.  After Alt-SysRq-k, either the virtual
  console resets to a login screen (as expected after this SysRq
  sequence), or we get a kernel panic text screen (see attached screen
  photo) and can only restore via a hard power-cycle reboot.

  I will continue to try to capture a better trace output from one of
  these conditions, perhaps from /var/log/kern.log or by installing
  linux-crashdump (although these old machines may not have enough
  memory for the stock package).  But in the meantime, I'm attaching a
  photo of the kernel panic we see, which suggests a problem may reside
  in the Radeon driver ... which would seem possible, given the general
  blank-screen no-resume problem on these systems.

  Any advice on how to further capture any other needed details would be
  appreciated.  Thanks very much!

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

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

[Touch-packages] [Bug 1764312] Re: fails to start in Bionic

2018-04-16 Thread Tom Chiverton

** Tags added: bionic

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

Title:
  fails to start in Bionic

Status in apparmor package in Ubuntu:
  New

Bug description:
  $ systemctl status apparmor
  ● apparmor.service - AppArmor initialization
 Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Mon 2018-04-16 07:46:13 BST; 1h 
10min ago
   Docs: man:apparmor(7)
 http://wiki.apparmor.net/
Process: 635 ExecStart=/etc/init.d/apparmor start (code=exited, status=123)
   Main PID: 635 (code=exited, status=123)

  Apr 16 07:46:12 ev34 apparmor[635]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
  Apr 16 07:46:12 ev34 apparmor[635]: AppArmor parser error for 
/etc/apparmor.d/usr.lib.snapd.snap-confine.real in /etc/ap
  Apr 16 07:46:13 ev34 apparmor[635]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  Apr 16 07:46:13 ev34 apparmor[635]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
  Apr 16 07:46:13 ev34 apparmor[635]: AppArmor parser error for 
/etc/apparmor.d/usr.lib.snapd.snap-confine.real in /etc/ap
  Apr 16 07:46:13 ev34 apparmor[635]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  Apr 16 07:46:13 ev34 apparmor[635]:...fail!
  Apr 16 07:46:13 ev34 systemd[1]: apparmor.service: Main process exited, 
code=exited, status=123/n/a
  Apr 16 07:46:13 ev34 systemd[1]: apparmor.service: Failed with result 
'exit-code'.
  Apr 16 07:46:13 ev34 systemd[1]: Failed to start AppArmor initialization.

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

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

[Touch-packages] [Bug 1764523] [NEW] xorg

Public bug reported:

display problems

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-35.39~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-35-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.8
Architecture: amd64
Date: Mon Apr 16 16:46:13 2018
SourcePackage: xorg
UpgradeStatus: Upgraded to artful on 2018-02-17 (58 days ago)

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

Title:
  xorg

Status in xorg package in Ubuntu:
  New

Bug description:
  display problems

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-35.39~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-35-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  Date: Mon Apr 16 16:46:13 2018
  SourcePackage: xorg
  UpgradeStatus: Upgraded to artful on 2018-02-17 (58 days ago)

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

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

[Touch-packages] [Bug 1326954] Re: Sierra Wireless EM7305 (Fujitsu Lifebook S904) does not work after suspend/hibernate

** Changed in: modemmanager
   Status: Incomplete => Confirmed

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

Title:
  Sierra Wireless EM7305 (Fujitsu Lifebook S904) does not work after
  suspend/hibernate

Status in ModemManager:
  Confirmed
Status in libmbim package in Ubuntu:
  Confirmed
Status in modemmanager package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04, x86_64, ModemManager-1.0.0-2ubuntu1

  Card: Sierra Wireless EM7305 (PCI Express M.2 form factor)

  Expected: Sierra plugin is used
  Happens: Generic plugin is used instead

  After cold start the card seems to work almost fine, but does not come
  back after suspend or hibernate. At least after hibernate MM may go
  into a tight loop consuming 100% CPU.

  MM debug log output (full log attached):

   [1401992536.121631] [mm-plugin-manager.c:576] build_plugins_list(): 
(Plugin Manager) [wwan0] Found '1' plugins to try...
   [1401992536.125236] [mm-plugin-manager.c:580] build_plugins_list(): 
(Plugin Manager) [wwan0]   Will try with plugin 'Generic'
   [1401992536.128923] [mm-plugin.c:700] mm_plugin_supports_port(): 
(Generic) [wwan0] probing deferred until result suggested
   [1401992536.132687] [mm-plugin-manager.c:505] 
plugin_supports_port_ready(): (Plugin Manager) [wwan0] deferring support check 
until result suggested
   [1401992536.142664] [mm-port-probe.c:536] wdm_probe_mbim(): 
(usbmisc/cdc-wdm0) probing MBIM...
   [1401992538.202591] [mm-plugin-manager.c:646] 
min_probing_timeout_cb(): (Plugin Manager) 
[/sys/devices/pci:00/:00:14.0/usb1/1-6] Minimum probing time consumed
  [/dev/cdc-wdm0] Queried max control message size: 4096[/dev/cdc-wdm0] Sent 
message...
  << RAW:
  <<   length = 16
  <<   data   = 01:00:00:00:10:00:00:00:01:00:00:00:00:10:00:00
  [/dev/cdc-wdm0] Sent message (translated)...
  << Header:
  <<   length  = 16
  <<   type= open (0x0001)
  <<   transaction = 1
  << Contents:
  <<   max_control_transfer = 4096
  [/dev/cdc-wdm0] Received message...
  >> RAW:
  >>   length = 16
  >>   data   = 01:00:00:80:10:00:00:00:01:00:00:00:00:00:00:00
   [1401992539.481429] [mm-port-probe.c:300] 
mm_port_probe_set_result_mbim(): (usbmisc/cdc-wdm0) port is MBIM-capable
  [/dev/cdc-wdm0] Sent message...
  << RAW:
  <<   length = 12
  <<   data   = 02:00:00:00:0C:00:00:00:02:00:00:00
  [/dev/cdc-wdm0] Sent message (translated)...
  << Header:
  <<   length  = 12
  <<   type= close (0x0002)
  <<   transaction = 2
  [/dev/cdc-wdm0] Received message...
  >> RAW:
  >>   length = 16
  >>   data   = 02:00:00:80:10:00:00:00:02:00:00:00:00:00:00:00
   [1401992539.545529] [mm-plugin-manager.c:417] 
plugin_supports_port_ready(): (Plugin Manager) (Generic) [cdc-wdm0] found best 
plugin for port
   [1401992539.549361] [mm-plugin-manager.c:334] 
suggest_port_probe_result(): (Plugin Manager) (Generic) [wwan0] deferred task 
completed, got suggested plugin
   [1401992539.553247] [mm-plugin-manager.c:274] 
port_probe_context_finished(): (Plugin Manager) 'cdc-wdm0' port probe finished, 
still 1 running probes in this device (wwan0)
   [1401992539.556995] [mm-plugin.c:700] mm_plugin_supports_port(): 
(Generic) [wwan0] probing deferred until result suggested
   [1401992539.560690] [mm-plugin-manager.c:485] 
plugin_supports_port_ready(): (Plugin Manager) (Generic) [wwan0] task 
completed, got suggested plugin
   [1401992539.564175] [mm-plugin-manager.c:285] 
port_probe_context_finished(): (Plugin Manager) 'wwan0' port probe finished, 
last one in device
   [1401992539.567868] [mm-plugin-manager.c:107] 
find_device_support_context_complete_and_free(): (Plugin Manager) 
[/sys/devices/pci:00/:00:14.0/usb1/1-6] device support check finished 
in '3.677528' seconds
[1401992539.571611] [mm-device.c:486] mm_device_create_modem(): 
Creating modem with plugin 'Generic' and '2' ports
   [1401992539.575477] [generic/mm-plugin-generic.c:73] create_modem(): 
MBIM-powered generic modem found...

  mmcli output:

  /org/freedesktop/ModemManager1/Modem/0 (device id 
'b3a77501ed8da196baa804a4142ff280766f6f98')
-
Hardware |   manufacturer: 'Generic'
 |  model: 'MBIM [1199:9063]'
 |   revision: 'SWI9X15C_01.12'
 |  supported: 'gsm-umts, lte'
 |current: 'gsm-umts, lte'
 |   equipment id: '356906050069168'
-
System   | device: '/sys/devices/pci:00/:00:14.0/usb1/1-6'
 |drivers: 'cdc_mbim'
 | plugin: 'Generic'
 |   primary port: 'cdc-wdm0'
 |  ports: 'cdc-wdm0 (mbim), wwan0 (net)'
-
Numbers  |   own : 'unknown'

[Touch-packages] [Bug 1480387] Re: Clicking a date to go back or forward a month causes repeated jumps between two dates

** Changed in: gtk
   Status: Expired => Confirmed

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

Title:
  Clicking a date to go back or forward a month causes repeated jumps
  between two dates

Status in GTK+:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  I asked in #ubuntu-desktop and people couldn't reproduce this in vivid
  or trusty. It happened for me in the most recent wily iso.

  Open the indicator, click one of the greyed dates at the start or end
  of the month (sometimes requires more than one go). The active date
  starts to repeatedly jump between this date and another one. I ran
  with G_MESSAGES_DEBUG=all and when it's happening this is spammed (I
  clicked a date in 2015-05).

  (process:32382): Indicator-Datetime-DEBUG: PlannerMonth 0x2727310 setting 
calendar month range: [2015-05-01 00:00:00..2015-05-31 23:59:59]
  (process:32382): Indicator-Datetime-DEBUG: 0x2728730 setting date range to 
[2015-05-30 00:00:00..2015-06-30 00:00:00]
  (process:32382): Indicator-Datetime-DEBUG: rebuilding because the date range 
changed
  (process:32382): Indicator-Datetime-DEBUG: PlannerMonth 0x2727310 setting 
calendar month range: [2015-05-01 00:00:00..2015-05-31 23:59:59]
  (process:32382): Indicator-Datetime-DEBUG: 0x2728730 setting date range to 
[2015-05-29 00:00:00..2015-06-29 00:00:00]
  (process:32382): Indicator-Datetime-DEBUG: rebuilding because the date range 
changed
  (process:32382): Indicator-Datetime-DEBUG: PlannerMonth 0x2727310 setting 
calendar month range: [2015-05-01 00:00:00..2015-05-31 23:59:59]
  (process:32382): Indicator-Datetime-DEBUG: 0x2728730 setting date range to 
[2015-05-30 00:00:00..2015-06-30 00:00:00]
  (process:32382): Indicator-Datetime-DEBUG: rebuilding because the date range 
changed
  (process:32382): Indicator-Datetime-DEBUG: PlannerMonth 0x2727310 setting 
calendar month range: [2015-05-01 00:00:00..2015-05-31 23:59:59]
  (process:32382): Indicator-Datetime-DEBUG: 0x2728730 setting date range to 
[2015-05-29 00:00:00..2015-06-29 00:00:00]
  (process:32382): Indicator-Datetime-DEBUG: rebuilding because the date range 
changed
  (process:32382): Indicator-Datetime-DEBUG: PlannerMonth 0x2727310 setting 
calendar month range: [2015-05-01 00:00:00..2015-05-31 23:59:59]
  (process:32382): Indicator-Datetime-DEBUG: 0x2728730 setting date range to 
[2015-05-30 00:00:00..2015-06-30 00:00:00]
  (process:32382): Indicator-Datetime-DEBUG: rebuilding because the date range 
changed
  (process:32382): Indicator-Datetime-DEBUG: PlannerMonth 0x2727310 setting 
calendar month range: [2015-05-01 00:00:00..2015-05-31 23:59:59]
  (process:32382): Indicator-Datetime-DEBUG: 0x2728730 setting date range to 
[2015-05-29 00:00:00..2015-06-29 00:00:00]
  (process:32382): Indicator-Datetime-DEBUG: rebuilding because the date range 
changed

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: indicator-datetime 13.10.0+15.10.20150728-0ubuntu1
  ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3
  Uname: Linux 4.1.0-2-generic x86_64
  ApportVersion: 2.18-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jul 31 17:09:43 2015
  InstallationDate: Installed on 2012-10-07 (1026 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to wily on 2013-05-07 (815 days ago)

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

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

[Touch-packages] [Bug 1764515] [NEW] wifi crashes in ubuntu 16.04 lts xenial

2018-04-16 Thread israel oluwole

Public bug reported:


‎I dual boot windows and ubuntu studio 16.4 lts on my Hp 15 notebook pc. When I 
installed afresh, wifi was alright until recently, everyone time I connect, it 
pops the dialog that the wifi key is needed for authentication over and again, 
so it never gets connected to the internet.i have tried reinstalling network 
manager, service restart, boot and reboot, adding [device] wifi.scan 
nothing worked
What do I need? I barely use windows now 'Cause linux is just dope...‎

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


** Tags: manager network

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

Title:
  wifi crashes in ubuntu 16.04 lts xenial

Status in network-manager package in Ubuntu:
  New

Bug description:
  
  ‎I dual boot windows and ubuntu studio 16.4 lts on my Hp 15 notebook pc. When 
I installed afresh, wifi was alright until recently, everyone time I connect, 
it pops the dialog that the wifi key is needed for authentication over and 
again, so it never gets connected to the internet.i have tried reinstalling 
network manager, service restart, boot and reboot, adding [device] 
wifi.scan nothing worked
  What do I need? I barely use windows now 'Cause linux is just dope...‎

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

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

[Touch-packages] [Bug 1764518] [NEW] package pulseaudio-module-bluetooth 1:8.0-0ubuntu3.8 [origin: Ubuntu] failed to install/upgrade: problemas com dependências - a deixar por configurar

2018-04-16 Thread Antonio Marues Pereira

Public bug reported:

On system startup

ProblemType: Package
DistroRelease: elementary 0.4.1
Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3.8 [origin: Ubuntu]
ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  antonio1431 F pulseaudio
Date: Mon Apr 16 00:50:52 2018
ErrorMessage: problemas com dependências - a deixar por configurar
InstallationDate: Installed on 2018-04-15 (0 days ago)
InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20180214)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: pulseaudio
Title: package pulseaudio-module-bluetooth 1:8.0-0ubuntu3.8 [origin: Ubuntu] 
failed to install/upgrade: problemas com dependências - a deixar por configurar
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/15/2009
dmi.bios.vendor: TOSHIBA
dmi.bios.version: V5.10
dmi.board.name: Satellite U300-130
dmi.board.vendor: TOSHIBA
dmi.board.version: Not Applicable
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnTOSHIBA:bvrV5.10:bd01/15/2009:svnTOSHIBA:pnSatelliteU300-130:pvrPSU30E-03D013PT:rvnTOSHIBA:rnSatelliteU300-130:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A:
dmi.product.name: Satellite U300-130
dmi.product.version: PSU30E-03D013PT
dmi.sys.vendor: TOSHIBA

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


** Tags: amd64 apport-package loki third-party-packages

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

Title:
  package pulseaudio-module-bluetooth 1:8.0-0ubuntu3.8 [origin: Ubuntu]
  failed to install/upgrade: problemas com dependências - a deixar por
  configurar

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  On system startup

  ProblemType: Package
  DistroRelease: elementary 0.4.1
  Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3.8 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  antonio1431 F pulseaudio
  Date: Mon Apr 16 00:50:52 2018
  ErrorMessage: problemas com dependências - a deixar por configurar
  InstallationDate: Installed on 2018-04-15 (0 days ago)
  InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20180214)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: pulseaudio
  Title: package pulseaudio-module-bluetooth 1:8.0-0ubuntu3.8 [origin: Ubuntu] 
failed to install/upgrade: problemas com dependências - a deixar por configurar
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/15/2009
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: V5.10
  dmi.board.name: Satellite U300-130
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrV5.10:bd01/15/2009:svnTOSHIBA:pnSatelliteU300-130:pvrPSU30E-03D013PT:rvnTOSHIBA:rnSatelliteU300-130:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A:
  dmi.product.name: Satellite U300-130
  dmi.product.version: PSU30E-03D013PT
  dmi.sys.vendor: TOSHIBA

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

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

[Touch-packages] [Bug 1759468] Re: gnome-control-center (11) gtk_style_context_clear_property_cache → gtk_css_widget_node_update_style → gtk_css_node_ensure_style → gtk_css_node_ensure_style → gtk_css

2018-04-16 Thread Ubuntu Foundations Team Bug Bot

The attachment "gtk3.debdiff" seems to be a debdiff.  The ubuntu-
sponsors team has been subscribed to the bug report so that they can
review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  gnome-control-center (11) gtk_style_context_clear_property_cache →
  gtk_css_widget_node_update_style → gtk_css_node_ensure_style →
  gtk_css_node_ensure_style → gtk_css_node_validate_internal

Status in gnome-control-center package in Ubuntu:
  In Progress
Status in gtk+3.0 package in Ubuntu:
  In Progress

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-control-center.  This problem was most recently seen with package version 
1:3.28.0-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/6b1f4dd86167bf5eb53ddca8469b5084208ddd22 
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/gnome-control-center/+bug/1759468/+subscriptions

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

[Touch-packages] [Bug 1750253] Re: ibus-daemon crashed with SIGABRT in g_mutex_clear()

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

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

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

Title:
  ibus-daemon crashed with SIGABRT in g_mutex_clear()

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  With sddm Displaymanger. gdm3 goes automatic to Ubuntu Wayland. No
  change possible.

  No Mouse click possibele but mouse moved. Can't change the
  Displaymanger.

  SDDM Change possible. Ubuntu or Gnome not started.

  Scroll Lock flashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun Feb 18 15:20:13 2018
  ExecutablePath: /usr/bin/ibus-daemon
  ProcCmdline: ibus-daemon --xim --panel disable
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/false
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   g_mutex_clear () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: ibus-daemon crashed with SIGABRT in g_mutex_clear()
  UpgradeStatus: Upgraded to bionic on 2017-12-04 (76 days ago)
  UserGroups:

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

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

[Touch-packages] [Bug 1764494] Re: X fails to start upon boot

2018-04-16 Thread yannek

** Attachment added: "X after the manual start"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1764494/+attachment/5118364/+files/Xorg.0.log.second_time

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

Title:
  X fails to start upon boot

Status in xorg package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd
  Description:Ubuntu Bionic Beaver (development branch)
  Release:18.04

  $ apt-cache policy xorg
  xorg:
Installed:   1:7.7+19ubuntu6

  
  The system is an upgrade from 17.10 to 18.04. The X-server fails to start 
initially, on each boot. After switching to tty2 I can start the login daemon 
via

  $ systemctl start sddm

  and X and sddm work as expected. (i.e. X starts, the login daemon
  starts, I can login to an X session)

  The system in question is a Lenovo X220 Thinkpad with integrated
  graphics. As lspci puts it:

  00:02.0 VGA compatible controller: Intel Corporation 2nd Generation
  Core Processor Family Integrated Graphics Controller (rev 09)

  This behaviour started as a result of the upgrade.

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

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

[Touch-packages] [Bug 1764494] [NEW] X fails to start upon boot

2018-04-16 Thread yannek

Public bug reported:

$ lsb_release -rd
Description:Ubuntu Bionic Beaver (development branch)
Release:18.04

$ apt-cache policy xorg
xorg:
  Installed:   1:7.7+19ubuntu6


The system is an upgrade from 17.10 to 18.04. The X-server fails to start 
initially, on each boot. After switching to tty2 I can start the login daemon 
via

$ systemctl start sddm

and X and sddm work as expected. (i.e. X starts, the login daemon
starts, I can login to an X session)

The system in question is a Lenovo X220 Thinkpad with integrated
graphics. As lspci puts it:

00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core
Processor Family Integrated Graphics Controller (rev 09)

This behaviour started as a result of the upgrade.

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

** Attachment added: "Xorg.0.log.failed"
   
https://bugs.launchpad.net/bugs/1764494/+attachment/5118363/+files/Xorg.0.log.failed

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

Title:
  X fails to start upon boot

Status in xorg package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd
  Description:Ubuntu Bionic Beaver (development branch)
  Release:18.04

  $ apt-cache policy xorg
  xorg:
Installed:   1:7.7+19ubuntu6

  
  The system is an upgrade from 17.10 to 18.04. The X-server fails to start 
initially, on each boot. After switching to tty2 I can start the login daemon 
via

  $ systemctl start sddm

  and X and sddm work as expected. (i.e. X starts, the login daemon
  starts, I can login to an X session)

  The system in question is a Lenovo X220 Thinkpad with integrated
  graphics. As lspci puts it:

  00:02.0 VGA compatible controller: Intel Corporation 2nd Generation
  Core Processor Family Integrated Graphics Controller (rev 09)

  This behaviour started as a result of the upgrade.

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

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

[Touch-packages] [Bug 1764478] Re: dhclient in 'stateless' mode does not wait for ipv6 dad

2018-04-16 Thread Dan Streetman

** Also affects: isc-dhcp (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: isc-dhcp (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: isc-dhcp (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: isc-dhcp (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: isc-dhcp (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: isc-dhcp (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: isc-dhcp (Ubuntu Artful)
   Importance: Undecided => Medium

** Changed in: isc-dhcp (Ubuntu Bionic)
   Importance: Undecided => Medium

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

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

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

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

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

Title:
  dhclient in 'stateless' mode does not wait for ipv6 dad

Status in isc-dhcp package in Ubuntu:
  New
Status in isc-dhcp source package in Trusty:
  New
Status in isc-dhcp source package in Xenial:
  New
Status in isc-dhcp source package in Artful:
  New
Status in isc-dhcp source package in Bionic:
  New

Bug description:
  [impact]

  when configuring an interface in ifupdown to use 'inet6 auto' (SLAAC),
  the option 'dhcp 1' can also be used, which will use isc-dhcp-client
  to perform 'stateless' dhcpv6, which does not get a dhcpv6 address,
  only config info, like DNS domain and server, etc.

  bug 1633479 fixed isc-dhcp-client to properly bring up and wait for
  the interface's ipv6 Duplicate Address Detection (DAD) to complete,
  which is required for isc-dhcp-client to be able to open a socket and
  begin broadcasting DHCPv6 requests.  However, that fix is skipped when
  isc-dhcp-client is used in 'stateless' mode, so it fails in exactly
  the same way, for the same reason; isc-dhcp-client needs to be updated
  to perform the 'PREINIT6' call to the dhclient script, which properly
  sets up the interface for dhclient to use.

  Without that setup, isc-dhcp-client in DHCPv6 'stateless' mode will
  always fail immediately when the interface it's using is down.  If the
  interface is up, it will already have completed DAD and dhclient will
  work.

  [test case]

  configure ifupdown with:

  auto eth0
  iface eth0 inet6 auto
dhcp 1

  replacing eth0 with the interface to test.  Make sure the interface is
  down, then ifup the interface.  isc-dhcp-client will fail claiming
  that:

  no link-local IPv6 address for eth0

  
  Alternately, ifupdown can be bypassed; for an interface that is currently 
down, do:

  $ sudo dhclient -6 -S eth0

  which will fail immediately (the -S param uses 'stateless' mode).

  [regression potential]

  changing isc-dhcp-client to perform PREINIT6 adds a new point of
  failure for doing DHCPv6, so there is the potential to break existing
  DHCPv6 clients if the preinit fails.  However, 'normal' DHCPv6 already
  does preinit6 - this only adds it to 'stateless' DHCPv6, so the
  failure potential should be limited to only users of 'stateless'
  DHCPv6, and those users are likely already seeing failures as
  described in this bug.

  [other info]

  This is related to bug 1633479

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

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

[Touch-packages] [Bug 1764478] [NEW] dhclient in 'stateless' mode does not wait for ipv6 dad

2018-04-16 Thread Dan Streetman

Public bug reported:

[impact]

when configuring an interface in ifupdown to use 'inet6 auto' (SLAAC),
the option 'dhcp 1' can also be used, which will use isc-dhcp-client to
perform 'stateless' dhcpv6, which does not get a dhcpv6 address, only
config info, like DNS domain and server, etc.

bug 1633479 fixed isc-dhcp-client to properly bring up and wait for the
interface's ipv6 Duplicate Address Detection (DAD) to complete, which is
required for isc-dhcp-client to be able to open a socket and begin
broadcasting DHCPv6 requests.  However, that fix is skipped when isc-
dhcp-client is used in 'stateless' mode, so it fails in exactly the same
way, for the same reason; isc-dhcp-client needs to be updated to perform
the 'PREINIT6' call to the dhclient script, which properly sets up the
interface for dhclient to use.

Without that setup, isc-dhcp-client in DHCPv6 'stateless' mode will
always fail immediately when the interface it's using is down.  If the
interface is up, it will already have completed DAD and dhclient will
work.

[test case]

configure ifupdown with:

auto eth0
iface eth0 inet6 auto
  dhcp 1

replacing eth0 with the interface to test.  Make sure the interface is
down, then ifup the interface.  isc-dhcp-client will fail claiming that:

no link-local IPv6 address for eth0


Alternately, ifupdown can be bypassed; for an interface that is currently down, 
do:

$ sudo dhclient -6 -S eth0

which will fail immediately (the -S param uses 'stateless' mode).

[regression potential]

changing isc-dhcp-client to perform PREINIT6 adds a new point of failure
for doing DHCPv6, so there is the potential to break existing DHCPv6
clients if the preinit fails.  However, 'normal' DHCPv6 already does
preinit6 - this only adds it to 'stateless' DHCPv6, so the failure
potential should be limited to only users of 'stateless' DHCPv6, and
those users are likely already seeing failures as described in this bug.

[other info]

This is related to bug 1633479

** Affects: isc-dhcp (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  dhclient in 'stateless' mode does not wait for ipv6 dad

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  [impact]

  when configuring an interface in ifupdown to use 'inet6 auto' (SLAAC),
  the option 'dhcp 1' can also be used, which will use isc-dhcp-client
  to perform 'stateless' dhcpv6, which does not get a dhcpv6 address,
  only config info, like DNS domain and server, etc.

  bug 1633479 fixed isc-dhcp-client to properly bring up and wait for
  the interface's ipv6 Duplicate Address Detection (DAD) to complete,
  which is required for isc-dhcp-client to be able to open a socket and
  begin broadcasting DHCPv6 requests.  However, that fix is skipped when
  isc-dhcp-client is used in 'stateless' mode, so it fails in exactly
  the same way, for the same reason; isc-dhcp-client needs to be updated
  to perform the 'PREINIT6' call to the dhclient script, which properly
  sets up the interface for dhclient to use.

  Without that setup, isc-dhcp-client in DHCPv6 'stateless' mode will
  always fail immediately when the interface it's using is down.  If the
  interface is up, it will already have completed DAD and dhclient will
  work.

  [test case]

  configure ifupdown with:

  auto eth0
  iface eth0 inet6 auto
dhcp 1

  replacing eth0 with the interface to test.  Make sure the interface is
  down, then ifup the interface.  isc-dhcp-client will fail claiming
  that:

  no link-local IPv6 address for eth0

  
  Alternately, ifupdown can be bypassed; for an interface that is currently 
down, do:

  $ sudo dhclient -6 -S eth0

  which will fail immediately (the -S param uses 'stateless' mode).

  [regression potential]

  changing isc-dhcp-client to perform PREINIT6 adds a new point of
  failure for doing DHCPv6, so there is the potential to break existing
  DHCPv6 clients if the preinit fails.  However, 'normal' DHCPv6 already
  does preinit6 - this only adds it to 'stateless' DHCPv6, so the
  failure potential should be limited to only users of 'stateless'
  DHCPv6, and those users are likely already seeing failures as
  described in this bug.

  [other info]

  This is related to bug 1633479

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

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

[Touch-packages] [Bug 1764474] Re: software-properties-gtk should not store the goa account-id used for livepatch in the keyring.

** Summary changed:

- software-properties-gtk should not store the gnome-online-account id used to 
authenticate using libsecrets
+ software-properties-gtk should not store the goa account-id used for 
livepatch in the keyring.

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

Title:
  software-properties-gtk should not store the goa account-id used for
  livepatch in the keyring.

Status in software-properties package in Ubuntu:
  New

Bug description:
  There is no need to store the goa account id in the keyring. gsettings
  should be enough.

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

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

[Touch-packages] [Bug 1761016] Re: cherry-pick https://codereview.qt-project.org/#/c/224684/ to fix image slideshows in KDE Plasma

2018-04-16 Thread Nate Graham

Yay, thanks!

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

Title:
  cherry-pick https://codereview.qt-project.org/#/c/224684/ to fix
  image slideshows in KDE Plasma

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

Bug description:
  KDE Plasma is affected by a Qt bug that causes image slideshows to
  leak memory, eventually exhausting all available memory and crashing
  the system: https://bugs.kde.org/show_bug.cgi?id=368838

  This principally affects people who use the popular slideshow
  wallpaper feature. Thankfully, there's a Qt patch to fix it the issue:
  https://codereview.qt-project.org/#/c/224684/

  It's slated to go into Qt 5.11. We should strongly consider cherry-
  picking it into 5.9.x to get this important fix into our users' hands
  as soon as possible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1761016/+subscriptions

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

[Touch-packages] [Bug 1764474] [NEW] software-properties-gtk should not store the gnome-online-account id used to authenticate using libsecrets

Public bug reported:

There is no need to store the goa account id in the keyring. gsettings
should be enough.

** Affects: software-properties (Ubuntu)
 Importance: Low
 Assignee: Andrea Azzarone (azzar1)
 Status: New

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

** Changed in: software-properties (Ubuntu)
 Assignee: (unassigned) => Andrea Azzarone (azzar1)

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

Title:
  software-properties-gtk should not store the gnome-online-account id
  used to authenticate using libsecrets

Status in software-properties package in Ubuntu:
  New

Bug description:
  There is no need to store the goa account id in the keyring. gsettings
  should be enough.

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

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

[Touch-packages] [Bug 1763446] Re: LIvepatch says I need to sign in after completing Ubuntu Welcome

Possible fix: https://gitlab.gnome.org/azzaronea/gnome-initial-
setup/commit/757355d371d21f725741f6376285481083f0c391

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

Title:
  LIvepatch says I need to sign in after completing Ubuntu Welcome

Status in software-properties package in Ubuntu:
  In Progress

Bug description:
  Test Case
  =
  From a clean Ubuntu 18.04 install,

  1. Install gnome-initial-setup
  2. Log out then log back in.
  3. Complete the Welcome to Ubuntu wizard, making sure to enable Livepatch.
  4. Afterwards, run the Software & Updates app (software-properties-gtk).
  5. Switch to the Updates tab.

  The page says "To use Livepatch you need to sign in."

  Workaround
  ==
  Click Sign In and then click your Ubuntu One account to get Software & 
Updates to correctly recognize your account.

  Screenshot attached. (Sorry about the blue colors; that should be
  fixed in mutter 3.28.1 available in Ubuntu 18.04 "soon".)

  Other Info
  ==
  gnome-initial-setup 3.28.0-2ubuntu3

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

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

[Touch-packages] [Bug 1762438] Re: traceback when gathering dmi information

This bug was fixed in the package apport - 2.20.9-0ubuntu5

---
apport (2.20.9-0ubuntu5) bionic; urgency=medium

  * apport/hookutils.py: When gathering dmi information use read_file() which
handles UTF-8. (LP: #1762438)

 -- Brian Murray   Fri, 13 Apr 2018 11:19:31 -0700

** Changed in: apport (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  traceback when gathering dmi information

Status in apport package in Ubuntu:
  Fix Released

Bug description:
  # ubuntu-bug systemd

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  .ERROR: hook /usr/share/apport/package-hooks/systemd.py crashed:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 198, in 
_run_hook
  symb['add_info'](report, ui)
  TypeError: add_info() takes 1 positional argument but 2 were given

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 203, in 
_run_hook
  symb['add_info'](report)
File "/usr/share/apport/package-hooks/systemd.py", line 11, in add_info
  apport.hookutils.attach_hardware(report)
File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 265, in 
attach_hardware
  attach_dmi(report)
File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 221, in 
attach_dmi
  value = fd.read().strip()
File "/usr/lib/python3.6/codecs.py", line 321, in decode
  (result, consumed) = self._buffer_decode(data, self.errors, final)
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 0: 
invalid start byte
  ..

  *** Send problem report to the developers?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: python3-apport 2.20.9-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  Date: Mon Apr  9 14:32:17 2018
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  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/1762438/+subscriptions

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

[Touch-packages] [Bug 1764181] Re: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: подпроцесс новый сценарий pre-removal возвратил код ошибки 1

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

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

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

Title:
  package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to
  install/upgrade: подпроцесс новый сценарий pre-removal возвратил код
  ошибки 1

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  Unfortunately, no extra information. It had just appeared.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Mon Apr 16 00:06:15 2018
  ErrorMessage: подпроцесс новый сценарий pre-removal возвратил код ошибки 1
  InstallationDate: Installed on 2018-03-08 (38 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: avahi
  Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to 
install/upgrade: подпроцесс новый сценарий pre-removal возвратил код ошибки 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1761016] Re: cherry-pick https://codereview.qt-project.org/#/c/224684/ to fix image slideshows in KDE Plasma

2018-04-16 Thread Simon Quigley

This has been uploaded to Bionic.

** Changed in: qtdeclarative-opensource-src (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  cherry-pick https://codereview.qt-project.org/#/c/224684/ to fix
  image slideshows in KDE Plasma

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

Bug description:
  KDE Plasma is affected by a Qt bug that causes image slideshows to
  leak memory, eventually exhausting all available memory and crashing
  the system: https://bugs.kde.org/show_bug.cgi?id=368838

  This principally affects people who use the popular slideshow
  wallpaper feature. Thankfully, there's a Qt patch to fix it the issue:
  https://codereview.qt-project.org/#/c/224684/

  It's slated to go into Qt 5.11. We should strongly consider cherry-
  picking it into 5.9.x to get this important fix into our users' hands
  as soon as possible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1761016/+subscriptions

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

[Touch-packages] [Bug 1752876] Re: sfdisk: allow disabling boot flag on MBR partition table

2018-04-16 Thread Simon Quigley

** Changed in: util-linux (Ubuntu)
 Assignee: (unassigned) => Simon Quigley (tsimonq2)

** Changed in: util-linux (Ubuntu)
   Importance: Undecided => Medium

** Changed in: util-linux (Ubuntu)
   Status: New => Confirmed

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

Title:
  sfdisk: allow disabling boot flag on MBR partition table

Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  I would like to propose the following patch for Ubuntu 18.04 LTS

  
  
https://github.com/karelzak/util-linux/commit/8175ed3d74adacc895657ded7546cb3c5deeabad


  [Impact]

   * This patch allows to use sfdisk to remove boot flag from all MBR 
partitions.
  At the moment you can only "move" boot flag to other partitions.

  
   * Derivatives of Ubuntu that use Calamares might be impacted by this. At the 
moment
  KDE Partition Manager and KPMcore (which is used by Calamares installer) are 
working on migrating to Polkit, so that they won't need to run GUI as root. One 
of the steps was moving from libparted backend to sfdisk backend for 
partitioning operations, so kpmcore will require 2.32 or 2.31.1 with this patch 
to have full functionality.

  
  [Test Case]

  Assuming that your want to deactivate boot flag on /dev/sdb which has
  MBR partition table:

  sudo sfdisk --activate /dev/sdb -

  Without this patch you should see an error message.

  With the patch it will print:


 
  The bootable flag on partition 1 is disabled now. 





  The partition table has been altered. 


  Calling ioctl() to re-read partition table.   


  Syncing disks.


  [Regression Potential]
  .
   * Should be extremely low. The change only adds a couple of lines in one file
  which parses arguments of "sfdisk --activate". Nothing would change unless you
  run sfdisk --activate

   * This patch does not change any libraries in util-linux, no need to
  worry about API/ABI stability.

   * GPT users are not affected at all.

  
  [Other Info]
   * This patch is part of util-linux 2.32.

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

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

[Touch-packages] [Bug 1764181] Re: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: подпроцесс новый сценарий pre-removal возвратил код ошибки 1

2018-04-16 Thread sacnoth

Preparing to unpack .../avahi-dnsconfd_0.6.32~rc+dfsg-1ubuntu2.1_amd64.deb ...
Job for avahi-daemon.socket canceled.
dpkg: warning: subprocess old pre-removal script returned error exit status 1
dpkg: trying script from the new package instead ...
Job for avahi-daemon.socket canceled.
dpkg: error processing archive 
/var/cache/apt/archives/avahi-dnsconfd_0.6.32~rc+dfsg-1ubuntu2.1_amd64.deb 
(--unpack):
 subprocess new pre-removal script returned error exit status 1
Errors were encountered while processing:
 /var/cache/apt/archives/avahi-dnsconfd_0.6.32~rc+dfsg-1ubuntu2.1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

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

Title:
  package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to
  install/upgrade: подпроцесс новый сценарий pre-removal возвратил код
  ошибки 1

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  Unfortunately, no extra information. It had just appeared.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Mon Apr 16 00:06:15 2018
  ErrorMessage: подпроцесс новый сценарий pre-removal возвратил код ошибки 1
  InstallationDate: Installed on 2018-03-08 (38 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: avahi
  Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to 
install/upgrade: подпроцесс новый сценарий pre-removal возвратил код ошибки 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1764467] Re: A strange symbol looking like a rhombus instead of apostroph in VT in Ukrainian keyboard layout

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

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

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

Title:
  A strange symbol looking like a rhombus instead of apostroph in VT in
  Ukrainian keyboard layout

Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  I found that in VT if to push Shift+~ on Ukrainian keyboard layout, as
  a result appears a strange symbol looking like a rhombus but it should
  be an apostrophe symbol "ʼ" as in X session.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: keyboard-configuration 1.178ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Apr 16 20:16:03 2018
  InstallationDate: Installed on 2014-06-08 (1408 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.1)
  PackageArchitecture: all
  SourcePackage: console-setup
  UpgradeStatus: Upgraded to bionic on 2018-03-05 (41 days ago)

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

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

[Touch-packages] [Bug 1764467] Re: A strange symbol looking like a rhombus instead of apostroph in VT in Ukrainian keyboard layout

2018-04-16 Thread Gannet

** Attachment added: "Rhombus instead of apostrophe in Uk kayboard layout in VT"
   
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1764467/+attachment/5118320/+files/rhombus.png

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

Title:
  A strange symbol looking like a rhombus instead of apostroph in VT in
  Ukrainian keyboard layout

Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  I found that in VT if to push Shift+~ on Ukrainian keyboard layout, as
  a result appears a strange symbol looking like a rhombus but it should
  be an apostrophe symbol "ʼ" as in X session.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: keyboard-configuration 1.178ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Apr 16 20:16:03 2018
  InstallationDate: Installed on 2014-06-08 (1408 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.1)
  PackageArchitecture: all
  SourcePackage: console-setup
  UpgradeStatus: Upgraded to bionic on 2018-03-05 (41 days ago)

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

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

[Touch-packages] [Bug 1732030] Re: 'apt update' dies with seccomp error

This bug was fixed in the package apt - 1.6~rc1

---
apt (1.6~rc1) unstable; urgency=medium

  [ Julian Andres Klode ]
  * Experimental support for zstd (LP: #1763839)
  * Fix debian/NEWS entry for 1.6~beta1
  * Use https for Ubuntu changelogs
  * Bump cache major version to allow different 1.5 and 1.6 updates
  * CI: Switch testing to use ubuntu:bionic for 1.6.y
  * Turn off seccomp sandboxing by default (LP: #1732030) (Closes: #890489)
  * Allow restart_syscall() syscall in seccomp sandboxes (Closes: #891644)
  * Delete /etc/dpkg/dpkg.cfg.d/excludes on Docker CI images
  * test: export GCOV_ERROR_FILE=/dev/null to make it fail less/no tests
  * apt-private: Collect not found packages in CacheSetHelperAPTGet
  * Introduce experimental new hooks for command-line tools (LP: #1763839)

  [ David Kalnischkies ]
  * remove duplicate changelog lines from 1.6~beta1 entry
  * fix communication typo in https manpage
  * set our two libapt libraries to prio:optional
  * document Acquire::AllowReleaseInfoChange without extra s

  [ jean-pierre giraud ]
  * French man pages translation (Closes: #895117)

 -- Julian Andres Klode   Sun, 15 Apr 2018 21:41:44
+0200

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

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

Title:
  'apt update' dies with seccomp error

Status in apt package in Ubuntu:
  Fix Released
Status in libvirt package in Ubuntu:
  Fix Released

Bug description:
  $ apt-get update
  0% [Working]
    Seccomp prevented execution of syscall 78 on architecture amd64 

  Reading package lists... Done
  E: Method mirror has died unexpectedly!
  E: Sub-process mirror returned an error code (31)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6~alpha5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  Date: Mon Nov 13 23:10:57 2017
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: apt
  UpgradeStatus: Upgraded to bionic on 2017-05-20 (177 days ago)

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

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

[Touch-packages] [Bug 1763839] Re: [FFe] apt 1.6~rc1, zstd & hook support

This bug was fixed in the package apt - 1.6~rc1

---
apt (1.6~rc1) unstable; urgency=medium

  [ Julian Andres Klode ]
  * Experimental support for zstd (LP: #1763839)
  * Fix debian/NEWS entry for 1.6~beta1
  * Use https for Ubuntu changelogs
  * Bump cache major version to allow different 1.5 and 1.6 updates
  * CI: Switch testing to use ubuntu:bionic for 1.6.y
  * Turn off seccomp sandboxing by default (LP: #1732030) (Closes: #890489)
  * Allow restart_syscall() syscall in seccomp sandboxes (Closes: #891644)
  * Delete /etc/dpkg/dpkg.cfg.d/excludes on Docker CI images
  * test: export GCOV_ERROR_FILE=/dev/null to make it fail less/no tests
  * apt-private: Collect not found packages in CacheSetHelperAPTGet
  * Introduce experimental new hooks for command-line tools (LP: #1763839)

  [ David Kalnischkies ]
  * remove duplicate changelog lines from 1.6~beta1 entry
  * fix communication typo in https manpage
  * set our two libapt libraries to prio:optional
  * document Acquire::AllowReleaseInfoChange without extra s

  [ jean-pierre giraud ]
  * French man pages translation (Closes: #895117)

 -- Julian Andres Klode   Sun, 15 Apr 2018 21:41:44
+0200

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

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

Title:
  [FFe] apt 1.6~rc1, zstd & hook support

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  As discussed previously, we want to have zstd support in 18.04 to evaluate 
and potentially enable it in later releases. We also want to add hooks for
  snap integration to apt, this release is supposed to add them too.

  The new features are not invasive - they are new code with a few
  places too hook them in. If no zstd is used, or if no hooks are
  registered, then there will be basically no change in behavior (or
  code paths).

  # FEATURE: zstd
  The zstd support adds a dependency on libzstd1 to libapt-pkg5.0. This should 
not have any effect on live images, since libzstd1 is part of the various live 
tasks, as btrfs-progs need it. For installed systems, this might be a new 
dependency (if they do not use btrfs, tor, or some other tools), so an increase 
of ~520 KB, as that's the size of the library and the library only depends on 
libc6.

  This also depends on the zstd patch in dpkg being uploaded. If this
  unexpectedly does not happen, and I upload apt first, I'd revert it
  later before the release.

  # FEATURE: hooks
  The concrete code is still undergoing review, some option names might change 
for the hooks before release (e.g. pre-download might become 
pre-install-prompt, and the AptCli::Hooks config section only gets Install and 
Search lists for hooks to register, rather than individual pre-, post-, and 
fail- lists).

  # other changes
  We disable the seccomp sandbox for methods for the release, as it turns out 
there are still too many failure cases for it to be worthwhile to enable (NSS 
modules, weird libc functions calling weird syscalls, etc). People can 
re-enable it with a config option.

  the rest is bug fixes. some change translatable strings in
  documentation, but fix up the translation too. A few additional
  strings are added to the sources.list man page ("mention mirror method
  in sources.list (Closes: 679580)", but I'm happy to back them out.

  There are also some CI fixes, and the major cache version is bumped so
  we can issue updates independently for 1.5 and 1.6 apt release series.

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

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

[Touch-packages] [Bug 1764467] [NEW] A strange symbol looking like a rhombus instead of apostroph in VT in Ukrainian keyboard layout

2018-04-16 Thread Gannet

Public bug reported:

I found that in VT if to push Shift+~ on Ukrainian keyboard layout, as a
result appears a strange symbol looking like a rhombus but it should be
an apostrophe symbol "ʼ" as in X session.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: keyboard-configuration 1.178ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CurrentDesktop: KDE
Date: Mon Apr 16 20:16:03 2018
InstallationDate: Installed on 2014-06-08 (1408 days ago)
InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1)
PackageArchitecture: all
SourcePackage: console-setup
UpgradeStatus: Upgraded to bionic on 2018-03-05 (41 days ago)

** Affects: console-setup (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 console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1764467

Title:
  A strange symbol looking like a rhombus instead of apostroph in VT in
  Ukrainian keyboard layout

Status in console-setup package in Ubuntu:
  New

Bug description:
  I found that in VT if to push Shift+~ on Ukrainian keyboard layout, as
  a result appears a strange symbol looking like a rhombus but it should
  be an apostrophe symbol "ʼ" as in X session.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: keyboard-configuration 1.178ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Apr 16 20:16:03 2018
  InstallationDate: Installed on 2014-06-08 (1408 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.1)
  PackageArchitecture: all
  SourcePackage: console-setup
  UpgradeStatus: Upgraded to bionic on 2018-03-05 (41 days ago)

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

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

[Touch-packages] [Bug 1764161] Re: Translation template for ibus is missing some strings

2018-04-16 Thread Gunnar Hjalmarsson

Thanks for your report!

Right, the LP template was almost three years old. I created and
uploaded a new template for now. That ought to help a bit. But it
resulted in 64 untranslated strings, which indicates that the upstream
PO files were created with an old template.

3 days before deadline. Some translators will hate me...

Looking at the build log, dh_translations isn't mentioned and -
consequently - the latest translation tarball is without a POT file.

@Sebastien: What determines whether dh_translations should be run when
building?

** Changed in: ubuntu-translations
   Importance: Undecided => Medium

** Changed in: ubuntu-translations
   Status: New => In Progress

** Changed in: ubuntu-translations
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

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

Title:
  Translation template for ibus is missing some strings

Status in Ubuntu Translations:
  In Progress
Status in ibus package in Ubuntu:
  New

Bug description:
  There are some strings missing in the translation template for ibus,
  at least in my (Czech) language. For example these strings:

  #: ../setup/setup.ui.h:50
  msgid "Emoji choice:"
  msgstr "Výběr emoji:"

  #: ../setup/setup.ui.h:51
  msgid "Set a font of emoji candidates on the emoji dialog"
  msgstr "Nastavit písmo kandidátů emoji v dialogu emoji"

  #: ../setup/setup.ui.h:52
  msgid "Emoji font:"
  msgstr "Font emoji:"

  #: ../setup/setup.ui.h:53
  msgid "Set a language of emoji annotations on the emoji dialog"
  msgstr "Nastavit jazyk anotací emoji v dialogu emoji"

  #: ../setup/setup.ui.h:54
  msgid "Emoji annotation language:"
  msgstr "Jazyk anotací emoji:"

  They are fully translated upstream, but are missing on Launchpad and
  are untranslated in Ubuntu 18.04 (see the attached screenshot).

  But there are more strings missing.

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

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

[Touch-packages] [Bug 1759468] Re: gnome-control-center (11) gtk_style_context_clear_property_cache → gtk_css_widget_node_update_style → gtk_css_node_ensure_style → gtk_css_node_ensure_style → gtk_css

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

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

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

** Changed in: gtk+3.0 (Ubuntu)
 Assignee: (unassigned) => Andrea Azzarone (azzar1)

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

Title:
  gnome-control-center (11) gtk_style_context_clear_property_cache →
  gtk_css_widget_node_update_style → gtk_css_node_ensure_style →
  gtk_css_node_ensure_style → gtk_css_node_validate_internal

Status in gnome-control-center package in Ubuntu:
  In Progress
Status in gtk+3.0 package in Ubuntu:
  In Progress

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-control-center.  This problem was most recently seen with package version 
1:3.28.0-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/6b1f4dd86167bf5eb53ddca8469b5084208ddd22 
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/gnome-control-center/+bug/1759468/+subscriptions

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

[Touch-packages] [Bug 1754186] Re: Night Light only affects a single monitor now

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

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

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

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

Title:
  Night Light only affects a single monitor now

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  The Display settings have a "Night Light" option which allows reducing blue 
light at night.
  In Ubuntu 17.10, this worked great, and the setting took effect on all 3 of 
my monitors.
  In Bionic, only the 1st monitor is affected; the other 2 remain at the 
default color temperature.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Wed Mar  7 17:51:02 2018
  DistUpgraded: 2018-03-07 12:52:16,474 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / 
R9 280X] [1002:6798] (prog-if 00 [VGA controller])
 Subsystem: XFX Pine Group Inc. Double D HD 7970 Black Edition [1682:3211]
  InstallationDate: Installed on 2014-08-21 (1294 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=98fea0b5-8fa6-4625-bae5-b85a70783a13 ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-03-07 (0 days ago)
  dmi.bios.date: 04/18/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1208
  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.:bvr1208:bd04/18/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.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sat Oct  7 12:18:20 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1.1
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1755885] Re: Night Light won't turn on after start on display #1

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

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

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

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

Title:
  Night Light won't turn on after start on display #1

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I have two displays and have Night Light mode enabled with Sunset to
  Sunrise setting (tried to change it into Manual, but this didn't make
  any difference).

  It was perfectly OK some time before, but now only display #2 is
  started with the Night Light mode switched on.

  I can work around it: go to the Display Settings, try to switch into
  non-native mode for Display #1 and it switched into it with Night
  Light enabled. Then choose not to keep settings and it returns into
  native resolution with Night Light on.

  Not all changes help to switch the mode on though. For instance,
  mirroring screen doesn't switch it on.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.42  Sat Mar  3 04:10:22 
PST 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-5ubuntu1)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Wed Mar 14 21:31:45 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.15.0-10-generic, x86_64: installed
   nvidia, 390.42, 4.15.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e5]
  InstallationDate: Installed on 2018-02-05 (37 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=68661197-00b4-4652-9c8f-2ef606012d2d ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/17/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0702
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-K/USB 3.1
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  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.:bvr0702:bd03/17/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-K/USB3.1:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1759468] Re: gnome-control-center (11) gtk_style_context_clear_property_cache → gtk_css_widget_node_update_style → gtk_css_node_ensure_style → gtk_css_node_ensure_style → gtk_css

Plese find attached a debdiff with the fix cherry-fixed from upstream.

** Patch added: "gtk3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1759468/+attachment/5118260/+files/gtk3.debdiff

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

Title:
  gnome-control-center (11) gtk_style_context_clear_property_cache →
  gtk_css_widget_node_update_style → gtk_css_node_ensure_style →
  gtk_css_node_ensure_style → gtk_css_node_validate_internal

Status in gnome-control-center package in Ubuntu:
  In Progress
Status in gtk+3.0 package in Ubuntu:
  In Progress

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-control-center.  This problem was most recently seen with package version 
1:3.28.0-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/6b1f4dd86167bf5eb53ddca8469b5084208ddd22 
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/gnome-control-center/+bug/1759468/+subscriptions

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

Re: [Touch-packages] [Bug 1764180] Re: System slows down to almost freeze

2018-04-16 Thread Guus Ellenkamp

Hi Theodore,

Thanks for your reply.

As far as I know the system is not swapping, at least not a lot, but as 
indicated, very hard to figure out what is going on without being able 
to use a terminal screen. I also set the swap space to another disk than 
the disk that seems to be causing the issue.

And yes, I know it has (probably) nothing to do with e2fsprogs, but I 
had to choose something when reporting the error (using command line 
utility).

And to me no matter what it is, it is still kind of a bug. I think an OS 
virtually freezing like this is not a stable OS.

I am trying to change the disk scheduler now to see if that changes 
anything.

Please note I started using ionice and nice for the suspect processes. 
That doesn't seem to make any difference.

Looking forward to more info about how I can figure out what is going
on,

Kind regards,

Guus

On Monday, 16 April, 2018 10:58 PM, Theodore Ts'o wrote:
> Your system sounds like its thrashing due your processes wanting to you
> more memory than is available in your system.  (BTW, this has nothing to
> do with e2fsprogs).
>
> Some links to pages that might be helpful:
>
> http://blog.scoutapp.com/articles/2015/04/10/understanding-page-faults-and-memory-swap-in-outs-when-should-you-worry
> https://serverfault.com/questions/77461/how-do-i-measure-disk-thrashing-on-linux
> https://unix.stackexchange.com/questions/259223/memory-usage-inexorably-creeping-upward
>

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

Title:
  System slows down to almost freeze

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  For quite a while sometimes my system slows down to almost freeze
  where it becomes unusable. The problem seems to be related to heavy
  disk i/o, but I have not been able to pinpoint the cause. The problem
  seems to occur when I both use the bitcoin core application for
  Bitcoin Gold and VirtualBox. I normally use VirtualBox to run two
  Windows 2008 servers.

  It seems in the end the system sorts itself out and starts running
  normal again, but it often causes to destroy the status of the Virtual
  Machines, sometimes resulting in a Virtual Machine going into 'guru-
  meditation' mode.

  Normally my system is fast enough to run everything. I have 8 Gb
  memory, 5 hard disks and an Intel I5. I tried to spread the load over
  the hard disks, but that doesn't seem to have any effect on the
  slowing down of the system.

  My feeling is that the problem is somehow related to some disk i/o
  system independent of the individual disks. Mostly the problem is
  solved by stopping the Bitcoin Core Gold program, but that is very
  hard to do, as even a terminal window takes minutes or up to an hour
  or so to respond. That also makes it very hard to identify the
  problem. I have several monitoring programs installed, but can't use
  them when the system is in this 'almost frozen' mode.

  I am using Ubuntu 16.04.4. The problem is not to x.x.4 version of
  Ubuntu 16.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: e2fslibs 1.42.13-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Mon Apr 16 04:45:11 2018
  Dependencies:
   gcc-7-base 7.1.0-10ubuntu1~16.04.york0 [origin: LP-PPA-jonathonf-gcc-7.1]
   libc6 2.23-0ubuntu10
   libgcc1 1:7.1.0-10ubuntu1~16.04.york0 [origin: LP-PPA-jonathonf-gcc-7.1]
  InstallationDate: Installed on 2017-01-21 (449 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: e2fsprogs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1764445] [NEW] the system is running in low-graphics mode

2018-04-16 Thread damiano

Public bug reported:

Ubuntu probably not recognizing installed Intel graphics driver

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
Uname: Linux 4.4.0-119-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
BootLog:
 
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: Mon Apr 16 17:38:17 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v2/3rd Gen Core processor 
Graphics Controller [1043:844d]
InstallationDate: Installed on 2016-06-01 (684 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-119-generic 
root=UUID=108b2d66-e751-447b-8aed-a462e8ece73b ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/02/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1501
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8H61-M LX2 R2.0
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1501:bd09/02/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX2R2.0:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.12.3+16.04.20180221-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.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Mon Apr 16 16:59:16 2018
xserver.configfile: default
xserver.devices:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.7

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


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

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

Title:
  the system is running in low-graphics mode

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu probably not recognizing installed Intel graphics driver

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  BootLog:
   
  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: Mon Apr 16 17:38:17 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v2/3rd Gen Core processor 
Graphics Controller [1043:844d]
  InstallationDate: Installed on 2016-06-01 (684 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-119-generic 
root=UUID=108b2d66-e751-447b-8aed-a462e8ece73b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/02/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1501
  dmi.board.asset.tag: To be filled by

[Touch-packages] [Bug 1764437] [NEW] x

2018-04-16 Thread Baljaa

Public bug reported:

x

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.16
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: Mon Apr 16 23:21:59 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics 
Controller [103c:183e]
 Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] 
[1002:6840] (rev ff) (prog-if ff)
InstallationDate: Installed on 2018-04-16 (0 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=7f424bd3-4785-4184-ab31-dd3870c7c934 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/07/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.27
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 183E
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 56.32
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.27:bd09/07/2016:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr07911020561620100:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
dmi.product.name: HP Pavilion g6 Notebook PC
dmi.product.version: 07911020561620100
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.3+16.04.20180221-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.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
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: Mon Apr 16 15:51:23 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2~16.04.1
xserver.video_driver: modeset

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


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

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

Title:
  x

Status in xorg package in Ubuntu:
  New

Bug description:
  x

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.16
  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: Mon Apr 16 23:21:59 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics 
Controller [103c:183e]
   Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] 
[1002:6840] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2018-04-16 (0 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=7f424bd3-4785-4184-ab31-dd3870c7c934 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/07/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.27
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 183E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 56.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias:

[Touch-packages] [Bug 1754693] Re: Xwayland crashed with SIGABRT in st_renderbuffer_delete()

2018-04-16 Thread Timo Aaltonen

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

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

Title:
  Xwayland crashed with SIGABRT in st_renderbuffer_delete()

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca

  ---

  Steps to reproduce:
  Install 'slack' snap:

     sudo snap install slack --classic

  Run slack:

     slack

  Instacrash.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.6-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell]
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Mar  9 10:31:06 2018
  DistUpgraded: 2018-03-06 13:58:47,853 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  MachineType: ASUS All Series
  ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 
4 -listen 5 -displayfd 6
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw 
crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M vt.handoff=1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
  Title: Xwayland crashed with SIGABRT
  UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago)
  UserGroups: adm admin audio cdrom chroot-admin dialout dip egbuild fax floppy 
fuse libvirt libvirtd lpadmin lxd plugdev sambashare sudo tape video wireshark
  dmi.bios.date: 10/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2702
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-PRO
  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.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Oct 16 18:18:18 2017
  xserver.configfile: default
  xserver.devices:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.19.3-1ubuntu1.2

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

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

[Touch-packages] [Bug 1754693] [NEW] Xwayland crashed with SIGABRT in st_renderbuffer_delete()

You have been subscribed to a public bug:

https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca

---

Steps to reproduce:
Install 'slack' snap:

   sudo snap install slack --classic

Run slack:

   slack

Instacrash.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: xwayland 2:1.19.6-1ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
.tmp.unity_support_test.0:

ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell]
CompositorRunning: None
CurrentDesktop: GNOME
Date: Fri Mar  9 10:31:06 2018
DistUpgraded: 2018-03-06 13:58:47,853 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: bionic
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/Xwayland
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
MachineType: ASUS All Series
ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 4 
-listen 5 -displayfd 6
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw 
crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M vt.handoff=1
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
Title: Xwayland crashed with SIGABRT
UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago)
UserGroups: adm admin audio cdrom chroot-admin dialout dip egbuild fax floppy 
fuse libvirt libvirtd lpadmin lxd plugdev sambashare sudo tape video wireshark
dmi.bios.date: 10/27/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2702
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97-PRO
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.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.90-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Mon Oct 16 18:18:18 2017
xserver.configfile: default
xserver.devices:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:

xserver.version: 2:1.19.3-1ubuntu1.2

** Affects: mesa (Ubuntu)
 Importance: High
 Status: Confirmed


** Tags: amd64 apport-crash bionic reproducible ubuntu wayland-session
-- 
Xwayland crashed with SIGABRT in st_renderbuffer_delete()
https://bugs.launchpad.net/bugs/1754693
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to mesa in Ubuntu.

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

[Touch-packages] [Bug 1764431] [NEW] package ca-certificates 20180409 failed to install/upgrade: підпроцес installed ca-certificates package post-installation script повернув помилковий код завершення

2018-04-16 Thread Viktor Mishkovskyi

Public bug reported:

Xubuntu 18.04


ca-certificates 20180409

During updating:
Sub-process /usr/bin/dpkg returned an error code

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: ca-certificates 20180409
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
Date: Mon Apr 16 17:49:58 2018
ErrorMessage: підпроцес installed ca-certificates package post-installation 
script повернув помилковий код завершення 1
InstallationDate: Installed on 2016-03-26 (751 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.14-4
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu1
 apt  1.6~rc1
SourcePackage: ca-certificates
Title: package ca-certificates 20180409 failed to install/upgrade: підпроцес 
installed ca-certificates package post-installation script повернув помилковий 
код завершення 1
UpgradeStatus: Upgraded to bionic on 2018-03-09 (38 days ago)

** Affects: ca-certificates (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: підпроцес
  installed ca-certificates package post-installation script повернув
  помилковий код завершення 1

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  Xubuntu 18.04

  
  ca-certificates 20180409

  During updating:
  Sub-process /usr/bin/dpkg returned an error code

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  Date: Mon Apr 16 17:49:58 2018
  ErrorMessage: підпроцес installed ca-certificates package post-installation 
script повернув помилковий код завершення 1
  InstallationDate: Installed on 2016-03-26 (751 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~rc1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: підпроцес 
installed ca-certificates package post-installation script повернув помилковий 
код завершення 1
  UpgradeStatus: Upgraded to bionic on 2018-03-09 (38 days ago)

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

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

[Touch-packages] [Bug 1764180] Re: System slows down to almost freeze

2018-04-16 Thread Theodore Ts'o

Your system sounds like its thrashing due your processes wanting to you
more memory than is available in your system. (BTW, this has nothing to
do with e2fsprogs).

Some links to pages that might be helpful:

http://blog.scoutapp.com/articles/2015/04/10/understanding-page-faults-and-memory-swap-in-outs-when-should-you-worry
https://serverfault.com/questions/77461/how-do-i-measure-disk-thrashing-on-linux
https://unix.stackexchange.com/questions/259223/memory-usage-inexorably-creeping-upward

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

Title:
System slows down to almost freeze

Status in e2fsprogs package in Ubuntu:
New

Bug description:
For quite a while sometimes my system slows down to almost freeze
where it becomes unusable. The problem seems to be related to heavy
disk i/o, but I have not been able to pinpoint the cause. The problem
seems to occur when I both use the bitcoin core application for
Bitcoin Gold and VirtualBox. I normally use VirtualBox to run two
Windows 2008 servers.

It seems in the end the system sorts itself out and starts running
normal again, but it often causes to destroy the status of the Virtual
Machines, sometimes resulting in a Virtual Machine going into 'guru-
meditation' mode.

Normally my system is fast enough to run everything. I have 8 Gb
memory, 5 hard disks and an Intel I5. I tried to spread the load over
the hard disks, but that doesn't seem to have any effect on the
slowing down of the system.

My feeling is that the problem is somehow related to some disk i/o
system independent of the individual disks. Mostly the problem is
solved by stopping the Bitcoin Core Gold program, but that is very
hard to do, as even a terminal window takes minutes or up to an hour
or so to respond. That also makes it very hard to identify the
problem. I have several monitoring programs installed, but can't use
them when the system is in this 'almost frozen' mode.

I am using Ubuntu 16.04.4. The problem is not to x.x.4 version of
Ubuntu 16.04.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: e2fslibs 1.42.13-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: LXDE
Date: Mon Apr 16 04:45:11 2018
Dependencies:
gcc-7-base 7.1.0-10ubuntu1~16.04.york0 [origin: LP-PPA-jonathonf-gcc-7.1]
libc6 2.23-0ubuntu10
libgcc1 1:7.1.0-10ubuntu1~16.04.york0 [origin: LP-PPA-jonathonf-gcc-7.1]
InstallationDate: Installed on 2017-01-21 (449 days ago)
InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: e2fsprogs
UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1732865] Re: [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min frequencies

2018-04-16 Thread Manoj Iyer

** Tags removed: triage-g
** Tags added: triage-a

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

Title:
  [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min
  frequencies

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Committed
Status in util-linux source package in Artful:
  Fix Released

Bug description:
  [Impact]
  lscpu fails to list CPU max and min frequencies if some CPUs are guarded.

  [Regression potential]
  Isolated change to lscpu min/max CPU frequency output, so the worst that 
could happen is that it fails to work elsewhere.

  [Test case]
  1. Clone https://github.com/open-power/op-test-framework
  2. Run this command to GUARD the cpu.
  ./op-test --bmc-type FSP --bmc-ip $FSPIP --bmc-username dev --bmc-password 
FipSdev --host-ip $HOSTIP --host-user root --host-password passw0rd --ffdcdir 
test-reports/ --run testcases.OpTestHMIHandling.MalfunctionAlert
  3. Repeat again, so that multiple CPUs are guarded.
  4. Run lscpu
  5. Observe that no CPU frequencies are displayed:
  CPU max MHz: (null)
  CPU min MHz: (null)
  6. Install util-linux from -proposed.
  7. Run lscpu again
  8. Observe that max and min CPU frequencies are correctly displayed.

  == Comment: #0 - Pridhiviraj Paidipeddi  - 2017-01-03 
05:34:32 ==
  ---Problem Description---
  After 3 CPU's are garded, lscpu failed to list CPU max and min frequencies

  Contact Information = ppaid...@in.ibm.com

  ---uname output---
  Linux p8wookie 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 
UTC 2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = PowerNV 8284-22A

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   1. Read lscpu output
  2. Inject HMI Non recoverable error three times
  3. Read lscpu output again
  compare the output cpu frequencies will list as NULL

  Stack trace output:
   no

  Oops output:
   no

  Userspace tool common name: lscpu

  Userspace rpm: util-linux

  The userspace tool has the following bit modes: 64-bit

  System Dump Info:
    The system is not configured to capture a system dump.

  Userspace tool obtained from project website:  na

  *Additional Instructions for ppaid...@in.ibm.com:
  -Post a private note with access information to the machine that the bug is 
occuring on.
  -Attach sysctl -a output output to the bug.
  -Attach ltrace and strace of userspace application.

  Before CPU's are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):112
  On-line CPU(s) list:   0-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   4322.
  CPU min MHz:   2061.
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 0-31
  NUMA node1 CPU(s): 32-63
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  After 4 cores are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):96
  On-line CPU(s) list:   8-55,64-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   (null)
  CPU min MHz:   (null)
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 8-31
  NUMA node1 CPU(s): 32-55
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  == Comment: #1 - Pridhiviraj Paidipeddi  - 2017-01-11 
07:06:59 ==
  root@p8wookie:~# dmesg |grep -i powernv
  [0.00] Using PowerNV machine description
  [0.331564] EEH: PowerNV platform initialized
  [0.907250] powernv-rng: Registering arch random hook.
  [1.504063] powernv-cpufreq: cpufreq pstate min -68 nominal -5 max 0
  [1.507167] powernv_idle_driver registered
  [   34.184048] powernv_rng: Registered powernv hwrng.
  [   34.185619] ipmi-powernv ibm,opal:ipmi: Unable to map irq from device tree
  [   34.210966] ipmi-powernv ibm,opal:ipmi: Found new BMC (man_id: 0x00, 
prod_id: 0x, dev_id: 0x00)
  root@p8wookie:~# cat /sys/firmware/opal/msglog | grep -i occ
  [   42.297825315,7]   OCC Common Area at 0x3b0 size 1MB
  [   42.297854780,7]   OCC Common Area at 0x200080 size 1MB
  [

[Touch-packages] [Bug 1764412] Re: systemd-logind crashed with SIGABRT in log_assert_failed_realm()

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

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

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1764412/+attachment/5118068/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1764412/+attachment/5118071/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1764412/+attachment/5118079/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1764412/+attachment/5118081/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1764412/+attachment/5118082/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1764412/+attachment/5118083/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1764412/+attachment/5118085/+files/ThreadStacktrace.txt

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  systemd-logind crashed with SIGABRT in log_assert_failed_realm()

Status in systemd package in Ubuntu:
  New

Bug description:
  I tried to add a HandlePowerKey directive in logind.conf

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu8
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Mon Apr 16 16:35:07 2018
  ExecutablePath: /lib/systemd/systemd-logind
  InstallationDate: Installed on 2018-04-16 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  MachineType: LENOVO 20L5000BRT
  ProcCmdline: /lib/systemd/systemd-logind
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic.efi.signed 
root=UUID=945903ad-3021-45a4-9eac-ce8593a50911 ro quiet splash 
resume=/dev/nvme0n1p2 resume_offset=3856384
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   log_assert_failed_realm () from /lib/systemd/libsystemd-shared-237.so
   close_nointr () from /lib/systemd/libsystemd-shared-237.so
   ?? ()
   ?? ()
   ?? ()
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-hibernate.service → 
/etc/systemd/system/systemd-hibernate.service.d/override.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  Title: systemd-logind crashed with SIGABRT in log_assert_failed_realm()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 02/12/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET35W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L5000BRT
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET35W(1.10):bd02/12/2018:svnLENOVO:pn20L5000BRT:pvrThinkPadT480:rvnLENOVO:rn20L5000BRT:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L5000BRT
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.systemd.logind.conf: 2018-04-16T16:34:43.637287

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

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

[Touch-packages] [Bug 1679704] Re: libvirt profile is blocking global setrlimit despite having no rlimit rule

2018-04-16 Thread Frank Heimes

A merge proposal to incl. the fixes was sent to the kernel-team.

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

Title:
  libvirt profile is blocking global setrlimit despite having no rlimit
  rule

Status in The Ubuntu-power-systems project:
  In Progress
Status in apparmor package in Ubuntu:
  In Progress

Bug description:
  Hi,
  while debugging bug 1678322 I was running along apparmor issues.
  Thanks to jjohansen we debugged some of it and eventually I was asked to 
report to a bug.

  Symptom:
  [ 8976.950635] audit: type=1400 audit(1491310016.224:48): apparmor="DENIED" 
operation="setrlimit" profile="/usr/sbin/libvirtd" pid=10034 comm="libvirtd" 
rlimit=memlock value=1610612736

  But none of the profiles has any rlimit statement in it:
  $ grep -Hirn limit /etc/apparmor*
  /etc/apparmor.d/sbin.dhclient:58:  # such, if the dhclient3 daemon is 
subverted, this effectively limits it to
  /etc/apparmor.d/abstractions/ubuntu-helpers:16:# Limitations:
  /etc/apparmor.d/abstractions/ubuntu-helpers:64:  # in limited libraries so 
glibc's secure execution should be enough to not
  /etc/apparmor.d/cache/.features:13:rlimit {mask {cpu fsize data stack core 
rss nproc nofile memlock as locks sigpending msgqueue nice rtprio rttime

  
  The profile contains a child profile which makes reading the dumps a bit 
painful, but I'll attach them anyway for you to take a look.
  To "recreate" if needed check out bug 1678322 - TL;DR hot-add some VFs via 
libvirt.

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

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

[Touch-packages] [Bug 1764161] Re: Translation template for ibus is missing some strings

2018-04-16 Thread AsciiWolf

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

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

Title:
  Translation template for ibus is missing some strings

Status in Ubuntu Translations:
  New
Status in ibus package in Ubuntu:
  New

Bug description:
  There are some strings missing in the translation template for ibus,
  at least in my (Czech) language. For example these strings:

  #: ../setup/setup.ui.h:50
  msgid "Emoji choice:"
  msgstr "Výběr emoji:"

  #: ../setup/setup.ui.h:51
  msgid "Set a font of emoji candidates on the emoji dialog"
  msgstr "Nastavit písmo kandidátů emoji v dialogu emoji"

  #: ../setup/setup.ui.h:52
  msgid "Emoji font:"
  msgstr "Font emoji:"

  #: ../setup/setup.ui.h:53
  msgid "Set a language of emoji annotations on the emoji dialog"
  msgstr "Nastavit jazyk anotací emoji v dialogu emoji"

  #: ../setup/setup.ui.h:54
  msgid "Emoji annotation language:"
  msgstr "Jazyk anotací emoji:"

  They are fully translated upstream, but are missing on Launchpad and
  are untranslated in Ubuntu 18.04 (see the attached screenshot).

  But there are more strings missing.

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

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

[Touch-packages] [Bug 1763446] Re: LIvepatch says I need to sign in after completing Ubuntu Welcome

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

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

Title:
  LIvepatch says I need to sign in after completing Ubuntu Welcome

Status in software-properties package in Ubuntu:
  In Progress

Bug description:
  Test Case
  =
  From a clean Ubuntu 18.04 install,

  1. Install gnome-initial-setup
  2. Log out then log back in.
  3. Complete the Welcome to Ubuntu wizard, making sure to enable Livepatch.
  4. Afterwards, run the Software & Updates app (software-properties-gtk).
  5. Switch to the Updates tab.

  The page says "To use Livepatch you need to sign in."

  Workaround
  ==
  Click Sign In and then click your Ubuntu One account to get Software & 
Updates to correctly recognize your account.

  Screenshot attached. (Sorry about the blue colors; that should be
  fixed in mutter 3.28.1 available in Ubuntu 18.04 "soon".)

  Other Info
  ==
  gnome-initial-setup 3.28.0-2ubuntu3

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

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

[Touch-packages] [Bug 1763446] Re: LIvepatch says I need to sign in after completing Ubuntu Welcome

2018-04-16 Thread Will Cooke

** Changed in: software-properties (Ubuntu)
   Importance: Low => 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/1763446

Title:
  LIvepatch says I need to sign in after completing Ubuntu Welcome

Status in software-properties package in Ubuntu:
  In Progress

Bug description:
  Test Case
  =
  From a clean Ubuntu 18.04 install,

  1. Install gnome-initial-setup
  2. Log out then log back in.
  3. Complete the Welcome to Ubuntu wizard, making sure to enable Livepatch.
  4. Afterwards, run the Software & Updates app (software-properties-gtk).
  5. Switch to the Updates tab.

  The page says "To use Livepatch you need to sign in."

  Workaround
  ==
  Click Sign In and then click your Ubuntu One account to get Software & 
Updates to correctly recognize your account.

  Screenshot attached. (Sorry about the blue colors; that should be
  fixed in mutter 3.28.1 available in Ubuntu 18.04 "soon".)

  Other Info
  ==
  gnome-initial-setup 3.28.0-2ubuntu3

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

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

[Touch-packages] [Bug 1764414] [NEW] + and - buttons are not themed in LibreOffice

2018-04-16 Thread Amr Ibrahim

Public bug reported:

Steps:
1. Start Writer
2. Go to Tools -> Options -> LibreOffice -> General
3. You will see an input field with + and - buttons

The buttons are not properly themed in Ambiance:
1. The - button has no left border
2. The + button has an extra right border
3. There is no hover effect (only touching without pressing the button)

All those three issues do not exist in Adwaita.

See the attached screencast.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: light-themes 16.10+18.04.20180328-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 16 15:37:38 2018
InstallationDate: Installed on 2017-10-02 (195 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930)
PackageArchitecture: all
SourcePackage: ubuntu-themes
UpgradeStatus: Upgraded to bionic on 2018-03-27 (19 days ago)

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


** Tags: amd64 apport-bug bionic

** Attachment added: "Plus-Minus-buttons-Libreoffice.ogv"
   
https://bugs.launchpad.net/bugs/1764414/+attachment/5118091/+files/Plus-Minus-buttons-Libreoffice.ogv

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

Title:
  + and - buttons are not themed in LibreOffice

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Steps:
  1. Start Writer
  2. Go to Tools -> Options -> LibreOffice -> General
  3. You will see an input field with + and - buttons

  The buttons are not properly themed in Ambiance:
  1. The - button has no left border
  2. The + button has an extra right border
  3. There is no hover effect (only touching without pressing the button)

  All those three issues do not exist in Adwaita.

  See the attached screencast.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180328-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 16 15:37:38 2018
  InstallationDate: Installed on 2017-10-02 (195 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to bionic on 2018-03-27 (19 days ago)

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

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

[Touch-packages] [Bug 1763874] Re: Cherry-pick cairo good patch from 0.63 to improve performance

This bug was fixed in the package poppler - 0.62.0-2ubuntu2

---
poppler (0.62.0-2ubuntu2) bionic; urgency=medium

  * Cherry-pick cairo-good-filter.patch from 0.63:
Use cairo's GOOD filter instead of BEST to significantly improve
performance. Thanks Rogério Brito for suggesting this patch.
(Closes: #895487) (LP: #1763874)

 -- Jeremy Bicha   Fri, 13 Apr 2018 22:08:42 -0400

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

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

Title:
  Cherry-pick cairo good patch from 0.63 to improve performance

Status in poppler package in Ubuntu:
  Fix Released
Status in poppler package in Debian:
  Fix Released

Bug description:
  Bug filed for potential SRU purposes.

  See Debian bug for details.

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

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

[Touch-packages] [Bug 1764401] Re: package initramfs-tools 0.122ubuntu8.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

** Tags removed: need-duplicate-check

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

Title:
  package initramfs-tools 0.122ubuntu8.11 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  My login page gets corrupted and creates problem while opening the
  disk manager and the window manager.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8.11
  ProcVersionSignature: Ubuntu 3.13.0-145.194-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-145-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Mon Apr 16 18:02:35 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2018-02-11 (63 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.122ubuntu8.11 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2018-04-16 (0 days ago)
  mtime.conffile..etc.initramfs-tools.initramfs.conf: 2016-12-09T23:11:30

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

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

[Touch-packages] [Bug 1666203] Re: pam_tty_audit failed in pam_open_session

2018-04-16 Thread Toru Ikezoe

** Description changed:

  Dear Maintainer.
  
  I found a bug in pam_tty_audit.
  When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it failed 
in pam_open_session.
  It was triggared by use uninitialized variable in 
pam_tty_audit.c::pam_open_session.
  
  * Enviroments
  Ubuntu 14.04.4 LTS
  linux-image-3.16.0-71-generic3.16.0-71.92~14.04.1
  libpam-ldap:amd64184-8.5ubuntu3
  libpam-modules:amd641.1.8-1ubuntu2.2
  
  Ubuntu 16.04.2 TLS
  linux-image-4.4.0-62-generic4.4.0-62.83
  libpam-ldap:amd64184-8.7ubuntu1
  libpam-modules:amd641.1.8-3.2ubuntu2
  
  * Reproduction method
  1. Install libpam-ldap.
  2. Add the following to the end of /etc/pam.d/common-sessions
  
  session required pam_tty_audit.so enable=* open_only
  
  3. When logging in with ssh etc., pam_tty_audit will fail and login fails
  
- * Solution
+ * Solution (== 2018/04/16 Link updated ==)
  apply upstream patch
- 
https://git.fedorahosted.org/cgit/linux-pam.git/commit/modules/pam_tty_audit/pam_tty_audit.c?id=c5f829931a22c65feffee16570efdae036524bee
+ 
https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee
  
  * Logs (on Ubuntu14.04)
  -- auth.log --
  May 18 14:47:03 vm sshd[2272]: Accepted publickey for test from 10.99.0.1 
port 51398 ssh2: RSA 8f:39:1c:3a:f4:9d:ca:99:67:fc:e3:fd:1e:0c:5b:a8
  May 18 14:47:03 vm sshd[2272]: pam_unix(sshd:session): session opened for 
user test by (uid=0)
  May 18 14:47:03 vm sshd[2272]: pam_tty_audit(sshd:session): error setting 
current audit status: Invalid argument
  May 18 14:47:03 vm sshd[2272]: error: PAM: pam_open_session(): Cannot 
make/remove an entry for the specified session
  May 18 14:47:03 vm sshd[2297]: Received disconnect from 10.99.0.1: 11: 
disconnected by user
  
  -- syslog --
  May 18 14:47:03 vm audispd: node=vm type=USER_ACCT 
msg=audit(1463550423.399:58): pid=2272 uid=0 auid=4294967295 ses=4294967295 
msg='op=PAM:accounting acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ssh res=success'
  May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ 
msg=audit(1463550423.403:59): pid=2272 uid=0 auid=4294967295 ses=4294967295 
msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ssh res=success'
  May 18 14:47:03 vm audispd: node=vm type=LOGIN msg=audit(1463550423.403:60): 
pid=2272 uid=0 old-auid=4294967295 auid=20299 old-ses=4294967295 ses=3 res=1
  May 18 14:47:03 vm audispd: node=vm type=CONFIG_CHANGE 
msg=audit(1463550423.403:61): pid=2272 uid=0 auid=20299 ses=3 op=tty_set 
old-enabled=0 new-enabled=1 old-log_passwd=0 new-log_passwd=32743 res=0
  May 18 14:47:03 vm audispd: node=vm type=USER_START 
msg=audit(1463550423.447:62): pid=2272 uid=0 auid=20299 ses=3 
msg='op=PAM:session_open acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ssh res=failed'
  May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ 
msg=audit(1463550423.447:63): pid=2297 uid=0 auid=20299 ses=3 
msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ssh res=success'
  May 18 14:47:03 vm audispd: node=vm type=CRED_DISP 
msg=audit(1463550423.451:64): pid=2272 uid=0 auid=20299 ses=3 
msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ssh res=success'
  
- 
  Thanks regards.

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

Title:
  pam_tty_audit failed in pam_open_session

Status in pam package in Ubuntu:
  Confirmed

Bug description:
  Dear Maintainer.

  I found a bug in pam_tty_audit.
  When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it failed 
in pam_open_session.
  It was triggared by use uninitialized variable in 
pam_tty_audit.c::pam_open_session.

  * Enviroments
  Ubuntu 14.04.4 LTS
  linux-image-3.16.0-71-generic3.16.0-71.92~14.04.1
  libpam-ldap:amd64184-8.5ubuntu3
  libpam-modules:amd641.1.8-1ubuntu2.2

  Ubuntu 16.04.2 TLS
  linux-image-4.4.0-62-generic4.4.0-62.83
  libpam-ldap:amd64184-8.7ubuntu1
  libpam-modules:amd641.1.8-3.2ubuntu2

  * Reproduction method
  1. Install libpam-ldap.
  2. Add the following to the end of /etc/pam.d/common-sessions
  
  session required pam_tty_audit.so enable=* open_only
  
  3. When logging in with ssh etc., pam_tty_audit will fail and login fails

  * Solution (== 2018/04/16 Link updated ==)
  apply upstream patch
  
https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee

  * Logs (on Ubuntu14.04)
  -- auth.log --
  May 18 14:47:03 vm sshd[2272]: Accepted publickey for test from 10.99.0.1 
port 51398 ssh2: RSA 8f:39:1c:3a:f4:9d:ca:99:67:fc:e3:fd:1e:0c:5b:a8
  May 18 14:47:03 vm sshd[2272]: pam_unix(sshd:session): session opened for 
user test by (uid=0)
  May 18 14:47:03 vm

[Touch-packages] [Bug 1762545] Re: No dashed line to indicate that more content is scrollable

2018-04-16 Thread Amr Ibrahim

In this screecast Nautilus using Adwaita, notice the dashed lines at the
top and bottom. They appear when there is more content to scroll to, and
disappear when there isn't.

** Attachment added: "Dashed-lines.ogv"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1762545/+attachment/5117971/+files/Dashed-lines.ogv

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

Title:
  No dashed line to indicate that more content is scrollable

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

Bug description:
  Ambiance does not show a dashed line to indicate that more content is
  scrollable. I have been using another theme than Ambiance for some
  time and I find the dashed line very helpful.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180328-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 22:25:00 2018
  InstallationDate: Installed on 2017-10-02 (189 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to bionic on 2018-03-27 (13 days ago)

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

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

[Touch-packages] [Bug 1764401] [NEW] package initramfs-tools 0.122ubuntu8.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2018-04-16 Thread Mohit Kumar Jaiswal

Public bug reported:

My login page gets corrupted and creates problem while opening the disk
manager and the window manager.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: initramfs-tools 0.122ubuntu8.11
ProcVersionSignature: Ubuntu 3.13.0-145.194-generic 3.13.11-ckt39
Uname: Linux 3.13.0-145-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
Date: Mon Apr 16 18:02:35 2018
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-20140620-0
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2018-02-11 (63 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.122ubuntu8.11 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2018-04-16 (0 days ago)
mtime.conffile..etc.initramfs-tools.initramfs.conf: 2016-12-09T23:11:30

** Affects: initramfs-tools (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 initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1764401

Title:
  package initramfs-tools 0.122ubuntu8.11 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  My login page gets corrupted and creates problem while opening the
  disk manager and the window manager.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8.11
  ProcVersionSignature: Ubuntu 3.13.0-145.194-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-145-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Mon Apr 16 18:02:35 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2018-02-11 (63 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.122ubuntu8.11 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2018-04-16 (0 days ago)
  mtime.conffile..etc.initramfs-tools.initramfs.conf: 2016-12-09T23:11:30

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

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

[Touch-packages] [Bug 1763839] Re: [FFe] apt 1.6~rc1, zstd & hook support

2018-04-16 Thread Francis Ginther

** Tags added: id-5a9f9b96fff3bd2877ffa9de

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

Title:
  [FFe] apt 1.6~rc1, zstd & hook support

Status in apt package in Ubuntu:
  Triaged

Bug description:
  As discussed previously, we want to have zstd support in 18.04 to evaluate 
and potentially enable it in later releases. We also want to add hooks for
  snap integration to apt, this release is supposed to add them too.

  The new features are not invasive - they are new code with a few
  places too hook them in. If no zstd is used, or if no hooks are
  registered, then there will be basically no change in behavior (or
  code paths).

  # FEATURE: zstd
  The zstd support adds a dependency on libzstd1 to libapt-pkg5.0. This should 
not have any effect on live images, since libzstd1 is part of the various live 
tasks, as btrfs-progs need it. For installed systems, this might be a new 
dependency (if they do not use btrfs, tor, or some other tools), so an increase 
of ~520 KB, as that's the size of the library and the library only depends on 
libc6.

  This also depends on the zstd patch in dpkg being uploaded. If this
  unexpectedly does not happen, and I upload apt first, I'd revert it
  later before the release.

  # FEATURE: hooks
  The concrete code is still undergoing review, some option names might change 
for the hooks before release (e.g. pre-download might become 
pre-install-prompt, and the AptCli::Hooks config section only gets Install and 
Search lists for hooks to register, rather than individual pre-, post-, and 
fail- lists).

  # other changes
  We disable the seccomp sandbox for methods for the release, as it turns out 
there are still too many failure cases for it to be worthwhile to enable (NSS 
modules, weird libc functions calling weird syscalls, etc). People can 
re-enable it with a config option.

  the rest is bug fixes. some change translatable strings in
  documentation, but fix up the translation too. A few additional
  strings are added to the sources.list man page ("mention mirror method
  in sources.list (Closes: 679580)", but I'm happy to back them out.

  There are also some CI fixes, and the major cache version is bumped so
  we can issue updates independently for 1.5 and 1.6 apt release series.

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

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

[Touch-packages] [Bug 1761567] Re: Characters of selected text are vertically flipped

2018-04-16 Thread Degrange Thomas

https://bugzilla.gnome.org/show_bug.cgi?id=760876 seems very similar,
except that the reversed text is just perfectly vertically mirrored, not
also garbled like mine.

** Bug watch added: GNOME Bug Tracker #760876
   https://bugzilla.gnome.org/show_bug.cgi?id=760876

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

Title:
  Characters of selected text are vertically flipped

Status in poppler package in Ubuntu:
  New

Bug description:
  In the attached PDF, I expect that selected text remains readable, but
  here selected characters become vertically flipped.

  -

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  -

  $ apt-cache policy evince
  evince:
Installed: 3.26.0-1
Candidate: 3.26.0-1
Version table:
   *** 3.26.0-1 500
  500 http://fr.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.26.0-1
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  5 20:58:15 2018
  ExecutablePath: /usr/bin/evince
  InstallationDate: Installed on 2018-02-19 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1761567] Re: Characters of selected text are vertically flipped

2018-04-16 Thread Sebastien Bacher

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

** Package changed: evince (Ubuntu) => poppler (Ubuntu)

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

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

Title:
  Characters of selected text are vertically flipped

Status in poppler package in Ubuntu:
  New

Bug description:
  In the attached PDF, I expect that selected text remains readable, but
  here selected characters become vertically flipped.

  -

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  -

  $ apt-cache policy evince
  evince:
Installed: 3.26.0-1
Candidate: 3.26.0-1
Version table:
   *** 3.26.0-1 500
  500 http://fr.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.26.0-1
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  5 20:58:15 2018
  ExecutablePath: /usr/bin/evince
  InstallationDate: Installed on 2018-02-19 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1762545] Re: No dashed line to indicate that more content is scrollable

2018-04-16 Thread Sebastien Bacher

You could maybe add a screenshot to the bug showing the feature you
request?

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

Title:
  No dashed line to indicate that more content is scrollable

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

Bug description:
  Ambiance does not show a dashed line to indicate that more content is
  scrollable. I have been using another theme than Ambiance for some
  time and I find the dashed line very helpful.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180328-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 22:25:00 2018
  InstallationDate: Installed on 2017-10-02 (189 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to bionic on 2018-03-27 (13 days ago)

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

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

[Touch-packages] [Bug 1761567] [NEW] Characters of selected text are vertically flipped

You have been subscribed to a public bug:

In the attached PDF, I expect that selected text remains readable, but
here selected characters become vertically flipped.

-

$ lsb_release -rd
Description:Ubuntu 17.10
Release:17.10

-

$ apt-cache policy evince
evince:
  Installed: 3.26.0-1
  Candidate: 3.26.0-1
  Version table:
 *** 3.26.0-1 500
500 http://fr.archive.ubuntu.com/ubuntu artful/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: evince 3.26.0-1
ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
Uname: Linux 4.13.0-38-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr  5 20:58:15 2018
ExecutablePath: /usr/bin/evince
InstallationDate: Installed on 2018-02-19 (44 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
SourcePackage: evince
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: poppler (Ubuntu)
 Importance: Low
 Status: New


** Tags: amd64 apport-bug artful
-- 
Characters of selected text are vertically flipped
https://bugs.launchpad.net/bugs/1761567
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to poppler in Ubuntu.

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

[Touch-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

2018-04-16 Thread ChristianEhrhardt

Lets break this into use cases in Bionic:

I was not sure who should win in each case.
We might either want the clear "order" chrony > ntp > openntp > 
systemd-timesyncd
Or we might want a "last installed" approach, but that is hard as upgrades to 
not count here only real "install". What would "--reinstall" be in these cases?
Maybe we should stick with the clear order, that at least seems more 
deterministic.
Cases 4-6 try to cover testing that order invariancy.

This is an "ideal world" approach, not sure if we can achieve that in the short 
term.
After the "=>" assignment is the service that should run (and only this one).

0. default install - systemd-timesyncd

1. default install - install chrony => Chrony
1b.- remove chrony => systemd-timesyncd

2. default install - install ntp  => NTP
2b.- remove ntp => systemd-timesyncd

3. default install - install openntp => openntp
3b.- remove openntp => systemd-timesyncd

4. default install - install ntp, install chrony => Chrony
4b.  remove chrony => NTP
4c.  remove NTP => systemd-timesyncd

5. default install - install chrony, install NTP => Chrony
5b.  remove Chrony => NTP
5c.  remove NTP => systemd-timesyncd

6. default install - install openntp => openntp
6b.  install NTP => NTP
6c.  install chrony => chrony
6d.  remote NTP & Chrony => openntp
6e.  remove openntp => systemd-timesyncd

7. xenial with ntp - upgrade to B => NTP

8. xenial with ntp - upgrade to B, install chrony => Chrony

9. xenial with ntp - upgrade to B, remove NTP => systemd-timesyncd

10. xenial without ntp - upgrade to B => systemd-timesyncd

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

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Confirmed
Status in clamav package in Ubuntu:
  Triaged
Status in controlaula package in Ubuntu:
  New
Status in epoptes package in Ubuntu:
  New
Status in ethtool package in Ubuntu:
  New
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  Won't Fix
Status in ifmetric package in Ubuntu:
  Won't Fix
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  Invalid
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  New
Status in ntp package in Ubuntu:
  New
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  Won't Fix
Status in openssh package in Ubuntu:
  New
Status in openvpn package in Ubuntu:
  New
Status in openvswitch package in Ubuntu:
  New
Status in postfix package in Ubuntu:
  New
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  Won't Fix
Status in vzctl package in Ubuntu:
  Triaged
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan

[Touch-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

2018-04-16 Thread ChristianEhrhardt

Nice summary, but wrong bug - sorry for the noise here :-/

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

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Confirmed
Status in clamav package in Ubuntu:
  Triaged
Status in controlaula package in Ubuntu:
  New
Status in epoptes package in Ubuntu:
  New
Status in ethtool package in Ubuntu:
  New
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  Won't Fix
Status in ifmetric package in Ubuntu:
  Won't Fix
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  Invalid
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  New
Status in ntp package in Ubuntu:
  New
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  Won't Fix
Status in openssh package in Ubuntu:
  New
Status in openvpn package in Ubuntu:
  New
Status in openvswitch package in Ubuntu:
  New
Status in postfix package in Ubuntu:
  New
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  Won't Fix
Status in vzctl package in Ubuntu:
  Triaged
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-dhcpv6
  wpa

  
  Related bugs:
   * bug 1718227: replacement of ifupdown with netplan needs integration for 
/etc/network/if{up,down}.d scripts 
   * bug 1713803: replacement of resolvconf with systemd needs integration 
   * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: netplan (not installed)
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep 19 10:53:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (789 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: plan
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1764381] [NEW] startup failure

2018-04-16 Thread Schuppisser

Public bug reported:

Ubuntu showing up only on right third of the screen. Going to sleep mode
and putting in ubuntu password the only way to show the whole screen and
getting started with ubuntu 16.04 LTS 32bit.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-38-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Apr 16 12:50:12 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Mobile 945GSE Express Integrated Graphics Controller 
[8086:27ae] (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Mobile 945GSE Express Integrated Graphics 
Controller [1025:015b]
   Subsystem: Acer Incorporated [ALI] Mobile 945GM/GMS/GME, 943/940GML Express 
Integrated Graphics Controller [1025:015b]
InstallationDate: Installed on 2018-01-16 (89 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
MachineType: Acer AOA150
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic 
root=UUID=be9b3832-9952-4cd9-9a95-6e297eef977c ro splash drm.debug=0xe quiet 
plymouth:debug vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/06/2008
dmi.bios.vendor: Acer
dmi.bios.version: v0.3310
dmi.board.asset.tag: Base Board Asset Tag
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:bvnAcer:bvrv0.3310:bd10/06/2008:svnAcer:pnAOA150:pvr1:rvnAcer:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
dmi.product.family: Intel_Mobile
dmi.product.name: AOA150
dmi.product.version: 1
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
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: Mon Apr 16 12:47:57 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id4546 
 vendor AUO
xserver.version: 2:1.19.5-0ubuntu2~16.04.1

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


** Tags: apport-bug compiz-0.9 i386 ubuntu xenial

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

Title:
  startup failure

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu showing up only on right third of the screen. Going to sleep
  mode and putting in ubuntu password the only way to show the whole
  screen and getting started with ubuntu 16.04 LTS 32bit.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Apr 16 12:50:12 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 945GSE Express Integrated Graphics Controller 
[8086:27ae] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Mobile 945GSE Express Integrated 
Graphics Controller [1025:015b]
 Subsystem: Acer Incorporated [ALI] Mobile 945GM/GMS/GME, 943/940GML 
Express Integrated Graphics Controller [1025:015b]
  InstallationDate: Installed on 2018-01-16 (89 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
  MachineType: Acer AOA150
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic 
root=UUID=be9b3832-9952-4cd9-9a95-6e297eef977c ro splash drm.debug=0xe quiet 
plymouth:debug vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/06/2008

[Touch-packages] [Bug 1752202] Re: U2F not working after upgrade: systemd dropped udev rules and libu2f-udev not installed

2018-04-16 Thread Dimitri John Ledkov

If you have removed ubuntu-desktop, your system is a custom install, and
unfortunately, you need to install libu2f-udev yourself

Have you tried installing ubuntu-desktop _without recommends_ ? it
should be a very minimal install, without any additional installs in
bionic onwords.

$ sudo apt install ubuntu-desktop --no-install-recommends

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

Title:
  U2F not working after upgrade: systemd dropped udev rules and libu2f-
  udev not installed

Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Summary:
  * libu2f-udev is not installed automatically, and after upgrading systemd it 
has lost its udev rules for U2F devices.
  * installing u2f-host (which pulls in libu2f-udev) doesn't seem to be enough 
to get it working either, had to manually reload the rules

  Long version:

  I upgraded from XUbuntu 17.10 to 18.04 daily build for testing.
  Previously I was able to use a Yubikey U2F device with Chromium and Firefox, 
however after the upgrade no U2F device was detected, the browser just timed 
out the U2F detection.

  I installed u2f-host to debug the problem further but it told me that it 
couldn't find any U2F devices. I looked in /dev/hidraw* and my user couldn't 
access any.
  Running this and repluggingt the device fixed the permissions: sudo udevadm 
control --reload-rules.

  It looks like that systemd used to have udev rules for U2F devices but they 
got dropped recently, pointing to libu2f-udev:
  
https://salsa.debian.org/systemd-team/systemd/commit/655e466caf37af36f527d42f164901b658203a2d

  Which is fine, except libu2f-udev is not installed automatically:
  libu2f-udev
  Reverse Depends:
libu2f-host0
ubuntu-mate-desktop
ubuntu-mate-core
ubuntu-budgie-desktop
  libu2f-host0
  Reverse Depends:
libu2f-host-dev
u2f-host
pamu2fcfg
libpam-u2f

  This seems wrong, individual desktop environments shouldn't bring this
  in, either the applications that use them (firefox, chromium) should
  recommend it, or a package common to all desktop flavours should pull
  it in.

  Please make libu2f-udev automatically installed as it was before when
  it was part of systemd, and reload the udev rules when it is
  installed.

  I'm filing this bug against systemd because the package that broke the
  behaviour was systemd, when udev rules got dropped from it the other
  packages' dependencies should've been updated so that the rules are
  not lost.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Feb 28 00:22:33 2018
  InstallationDate: Installed on 2017-12-02 (87 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20171018)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcKernelCmdLine: root=UUID=0cc81157-5ab2-46eb-b70b-cb3c62f635e8 ro quiet 
vt.handoff=7 initrd=\EFI\ubuntu\initrd.img resume=/dev/nvme0n1p2
  SourcePackage: systemd
  UpgradeStatus: Upgraded to bionic on 2018-02-24 (3 days ago)
  dmi.bios.date: 04/07/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A99FX PRO R2.0
  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.:bvr2501:bd04/07/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99FXPROR2.0: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/ubuntu-meta/+bug/1752202/+subscriptions

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

[Touch-packages] [Bug 1679704] Comment bridged from LTC Bugzilla

2018-04-16 Thread bugproxy

--- Comment From bssrika...@in.ibm.com 2018-04-16 05:49 EDT---
Any updates on this one? when are we getting this fixed?

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

Title:
  libvirt profile is blocking global setrlimit despite having no rlimit
  rule

Status in The Ubuntu-power-systems project:
  In Progress
Status in apparmor package in Ubuntu:
  In Progress

Bug description:
  Hi,
  while debugging bug 1678322 I was running along apparmor issues.
  Thanks to jjohansen we debugged some of it and eventually I was asked to 
report to a bug.

  Symptom:
  [ 8976.950635] audit: type=1400 audit(1491310016.224:48): apparmor="DENIED" 
operation="setrlimit" profile="/usr/sbin/libvirtd" pid=10034 comm="libvirtd" 
rlimit=memlock value=1610612736

  But none of the profiles has any rlimit statement in it:
  $ grep -Hirn limit /etc/apparmor*
  /etc/apparmor.d/sbin.dhclient:58:  # such, if the dhclient3 daemon is 
subverted, this effectively limits it to
  /etc/apparmor.d/abstractions/ubuntu-helpers:16:# Limitations:
  /etc/apparmor.d/abstractions/ubuntu-helpers:64:  # in limited libraries so 
glibc's secure execution should be enough to not
  /etc/apparmor.d/cache/.features:13:rlimit {mask {cpu fsize data stack core 
rss nproc nofile memlock as locks sigpending msgqueue nice rtprio rttime

  
  The profile contains a child profile which makes reading the dumps a bit 
painful, but I'll attach them anyway for you to take a look.
  To "recreate" if needed check out bug 1678322 - TL;DR hot-add some VFs via 
libvirt.

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

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

[Touch-packages] [Bug 1763839] Re: [FFe] apt 1.6~rc1, zstd & hook support

2018-04-16 Thread Łukasz Zemczak

FFe approved.

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

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

Title:
  [FFe] apt 1.6~rc1, zstd & hook support

Status in apt package in Ubuntu:
  Triaged

Bug description:
  As discussed previously, we want to have zstd support in 18.04 to evaluate 
and potentially enable it in later releases. We also want to add hooks for
  snap integration to apt, this release is supposed to add them too.

  The new features are not invasive - they are new code with a few
  places too hook them in. If no zstd is used, or if no hooks are
  registered, then there will be basically no change in behavior (or
  code paths).

  # FEATURE: zstd
  The zstd support adds a dependency on libzstd1 to libapt-pkg5.0. This should 
not have any effect on live images, since libzstd1 is part of the various live 
tasks, as btrfs-progs need it. For installed systems, this might be a new 
dependency (if they do not use btrfs, tor, or some other tools), so an increase 
of ~520 KB, as that's the size of the library and the library only depends on 
libc6.

  This also depends on the zstd patch in dpkg being uploaded. If this
  unexpectedly does not happen, and I upload apt first, I'd revert it
  later before the release.

  # FEATURE: hooks
  The concrete code is still undergoing review, some option names might change 
for the hooks before release (e.g. pre-download might become 
pre-install-prompt, and the AptCli::Hooks config section only gets Install and 
Search lists for hooks to register, rather than individual pre-, post-, and 
fail- lists).

  # other changes
  We disable the seccomp sandbox for methods for the release, as it turns out 
there are still too many failure cases for it to be worthwhile to enable (NSS 
modules, weird libc functions calling weird syscalls, etc). People can 
re-enable it with a config option.

  the rest is bug fixes. some change translatable strings in
  documentation, but fix up the translation too. A few additional
  strings are added to the sources.list man page ("mention mirror method
  in sources.list (Closes: 679580)", but I'm happy to back them out.

  There are also some CI fixes, and the major cache version is bumped so
  we can issue updates independently for 1.5 and 1.6 apt release series.

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

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

[Touch-packages] [Bug 1750328] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1750328/+attachment/5117839/+files/ProcEnviron.txt

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

Title:
  ubuntu17.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  ubuntu 17.10 can not see or fix screen saver or wallpaper

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-35.39~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-35-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Mon Feb 19 02:04:44 2018
  SourcePackage: xorg
  UpgradeStatus: Upgraded to artful on 2018-02-17 (1 days ago)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-35.39~16.04.1-generic 4.13.13
  Tags:  artful
  Uname: Linux 4.13.0-35-generic x86_64
  UpgradeStatus: Upgraded to artful on 2018-02-17 (57 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1750328] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1750328/+attachment/5117838/+files/ProcCpuinfoMinimal.txt

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

Title:
  ubuntu17.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  ubuntu 17.10 can not see or fix screen saver or wallpaper

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-35.39~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-35-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Mon Feb 19 02:04:44 2018
  SourcePackage: xorg
  UpgradeStatus: Upgraded to artful on 2018-02-17 (1 days ago)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-35.39~16.04.1-generic 4.13.13
  Tags:  artful
  Uname: Linux 4.13.0-35-generic x86_64
  UpgradeStatus: Upgraded to artful on 2018-02-17 (57 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1750328] Re: ubuntu17.10

apport information

** Tags added: apport-collected

** Description changed:

  ubuntu 17.10 can not see or fix screen saver or wallpaper
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-35.39~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-35-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Mon Feb 19 02:04:44 2018
  SourcePackage: xorg
  UpgradeStatus: Upgraded to artful on 2018-02-17 (1 days ago)
+ --- 
+ ApportVersion: 2.20.7-0ubuntu3.8
+ Architecture: amd64
+ CurrentDesktop: Unity:Unity7:ubuntu
+ DistroRelease: Ubuntu 17.10
+ Package: xorg 1:7.7+13ubuntu3
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.13.0-35.39~16.04.1-generic 4.13.13
+ Tags:  artful
+ Uname: Linux 4.13.0-35-generic x86_64
+ UpgradeStatus: Upgraded to artful on 2018-02-17 (57 days ago)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1750328/+attachment/5117837/+files/Dependencies.txt

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

Title:
  ubuntu17.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  ubuntu 17.10 can not see or fix screen saver or wallpaper

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-35.39~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-35-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Mon Feb 19 02:04:44 2018
  SourcePackage: xorg
  UpgradeStatus: Upgraded to artful on 2018-02-17 (1 days ago)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-35.39~16.04.1-generic 4.13.13
  Tags:  artful
  Uname: Linux 4.13.0-35-generic x86_64
  UpgradeStatus: Upgraded to artful on 2018-02-17 (57 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1764338] Re: systemd-nspawn container networking lost after systemd-container upgrade

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

Title:
  systemd-nspawn container networking lost after systemd-container
  upgrade

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I have 2 systemd-nspawn containers running on an ubuntu 18.04 server used for 
an internal test automation service.
  They each use a private network using the nethork-veth option and expose a 
single port.
  The host system runs nginx and routes traffic to the two containers.

  After running apt upgrade the container ports were no longer reachable
  from the outside causing the server to repond with HTTP 502 bad
  gateway on the host.

  To resolve the situation I had to restart the two containers running:
  - machinectl stop helvetest-prod
  - machinectl start helvetest-prod
  - machinestl stop helvetest-dev
  - machinectl start helvetest-dev

  Everything was fine after that.

  The two containers are run as instances of the built-in systemd-nspawn@ 
service.
  I use the following nspawn configuration:

  
  root@helvetest:/etc/systemd/nspawn# ls -lrth
  total 8.0K
  -rw-r--r-- 1 root root 92 Apr 11 07:09 helvetest-dev.nspawn
  -rw-r--r-- 1 root root 92 Apr 12 11:34 helvetest-prod.nspawn

  
  root@helvetest:/etc/systemd/nspawn# cat helvetest-prod.nspawn 
  [Files]
  BindReadOnly=/etc/systemd/network

  [Network]
  VirtualEthernet=yes
  Port=tcp:6640:6640

  
  root@helvetest:/etc/systemd/nspawn# cat helvetest-dev.nspawn 
  [Files]
  BindReadOnly=/etc/systemd/network

  [Network]
  VirtualEthernet=yes
  Port=tcp:5540:5540

  
  Host details

  # lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  Partial apt upgrade logs

  Preparing to unpack .../libnss-systemd_237-3ubuntu8_amd64.deb ...
  Unpacking libnss-systemd:amd64 (237-3ubuntu8) over (237-3ubuntu7) ...
  Preparing to unpack .../libnss-mymachines_237-3ubuntu8_amd64.deb ...
  Unpacking libnss-mymachines:amd64 (237-3ubuntu8) over (237-3ubuntu7) ...
  Preparing to unpack .../systemd-container_237-3ubuntu8_amd64.deb ...
  Unpacking systemd-container (237-3ubuntu8) over (237-3ubuntu7) ...
  Preparing to unpack .../libsystemd0_237-3ubuntu8_amd64.deb ...
  Unpacking libsystemd0:amd64 (237-3ubuntu8) over (237-3ubuntu7) ...
  Setting up libsystemd0:amd64 (237-3ubuntu8) ...

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd-container 237-3ubuntu8
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Mon Apr 16 08:53:20 2018
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1764338] [NEW] systemd-nspawn container networking lost after systemd-container upgrade

2018-04-16 Thread Thomas Cellerier

Public bug reported:

I have 2 systemd-nspawn containers running on an ubuntu 18.04 server used for 
an internal test automation service.
They each use a private network using the nethork-veth option and expose a 
single port.
The host system runs nginx and routes traffic to the two containers.

After running apt upgrade the container ports were no longer reachable
from the outside causing the server to repond with HTTP 502 bad gateway
on the host.

To resolve the situation I had to restart the two containers running:
- machinectl stop helvetest-prod
- machinectl start helvetest-prod
- machinestl stop helvetest-dev
- machinectl start helvetest-dev

Everything was fine after that.

The two containers are run as instances of the built-in systemd-nspawn@ service.
I use the following nspawn configuration:


root@helvetest:/etc/systemd/nspawn# ls -lrth
total 8.0K
-rw-r--r-- 1 root root 92 Apr 11 07:09 helvetest-dev.nspawn
-rw-r--r-- 1 root root 92 Apr 12 11:34 helvetest-prod.nspawn


root@helvetest:/etc/systemd/nspawn# cat helvetest-prod.nspawn 
[Files]
BindReadOnly=/etc/systemd/network

[Network]
VirtualEthernet=yes
Port=tcp:6640:6640


root@helvetest:/etc/systemd/nspawn# cat helvetest-dev.nspawn 
[Files]
BindReadOnly=/etc/systemd/network

[Network]
VirtualEthernet=yes
Port=tcp:5540:5540


Host details

# lsb_release -rd
Description:Ubuntu Bionic Beaver (development branch)
Release:18.04

Partial apt upgrade logs

Preparing to unpack .../libnss-systemd_237-3ubuntu8_amd64.deb ...
Unpacking libnss-systemd:amd64 (237-3ubuntu8) over (237-3ubuntu7) ...
Preparing to unpack .../libnss-mymachines_237-3ubuntu8_amd64.deb ...
Unpacking libnss-mymachines:amd64 (237-3ubuntu8) over (237-3ubuntu7) ...
Preparing to unpack .../systemd-container_237-3ubuntu8_amd64.deb ...
Unpacking systemd-container (237-3ubuntu8) over (237-3ubuntu7) ...
Preparing to unpack .../libsystemd0_237-3ubuntu8_amd64.deb ...
Unpacking libsystemd0:amd64 (237-3ubuntu8) over (237-3ubuntu7) ...
Setting up libsystemd0:amd64 (237-3ubuntu8) ...

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd-container 237-3ubuntu8
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
Date: Mon Apr 16 08:53:20 2018
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  systemd-nspawn container networking lost after systemd-container
  upgrade

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I have 2 systemd-nspawn containers running on an ubuntu 18.04 server used for 
an internal test automation service.
  They each use a private network using the nethork-veth option and expose a 
single port.
  The host system runs nginx and routes traffic to the two containers.

  After running apt upgrade the container ports were no longer reachable
  from the outside causing the server to repond with HTTP 502 bad
  gateway on the host.

  To resolve the situation I had to restart the two containers running:
  - machinectl stop helvetest-prod
  - machinectl start helvetest-prod
  - machinestl stop helvetest-dev
  - machinectl start helvetest-dev

  Everything was fine after that.

  The two containers are run as instances of the built-in systemd-nspawn@ 
service.
  I use the following nspawn configuration:

  
  root@helvetest:/etc/systemd/nspawn# ls -lrth
  total 8.0K
  -rw-r--r-- 1 root root 92 Apr 11 07:09 helvetest-dev.nspawn
  -rw-r--r-- 1 root root 92 Apr 12 11:34 helvetest-prod.nspawn

  
  root@helvetest:/etc/systemd/nspawn# cat helvetest-prod.nspawn 
  [Files]
  BindReadOnly=/etc/systemd/network

  [Network]
  VirtualEthernet=yes
  Port=tcp:6640:6640

  
  root@helvetest:/etc/systemd/nspawn# cat helvetest-dev.nspawn 
  [Files]
  BindReadOnly=/etc/systemd/network

  [Network]
  VirtualEthernet=yes
  Port=tcp:5540:5540

  
  Host details

  # lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  Partial apt upgrade logs

  Preparing to unpack .../libnss-systemd_237-3ubuntu8_amd64.deb ...
  Unpacking libnss-systemd:amd64 (237-3ubuntu8) over (237-3ubuntu7) ...
  Preparing to unpack .../libnss-mymachines_237-3ubuntu8_amd64.deb ...
  Unpacking libnss-mymachines:amd64 (237-3ubuntu8) over (237-3ubuntu7) ...
  Preparing to unpack .../systemd-container_237-3ubuntu8_amd64.deb ...
  Unpacking systemd-container (237-3ubuntu8) over (237-3ubuntu7) ...
  Preparing to unpack .../libsystemd0_237-3ubuntu8_amd64.deb ...
  Unpacking libsystemd0:amd64 (237-3ubuntu8) over (237-3ubuntu7) ...
  Setting up libsystemd0:amd64 (237-3ubuntu8) ...

  ProblemType: Bug
  DistroRelease:

[Touch-packages] [Bug 1764333] [NEW] Nach dem Neustart

2018-04-16 Thread Jürgen Frenzel

Public bug reported:

Begleiterscheinung kann auf der Maschine kein Ubuntu 17.04 oder 17.10
installieren.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-120.144-generic 4.4.117
Uname: Linux 4.4.0-120-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.16
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
Date: Mon Apr 16 10:49:18 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.1.34, 4.4.0-118-generic, x86_64: installed
 virtualbox, 5.1.34, 4.4.0-120-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation NV43 [GeForce 6600 GT] [10de:0140] (rev a2) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. NV43 [GeForce 6600 GT] [1043:81cf]
InstallationDate: Installed on 2016-06-22 (662 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: FUJITSU SIEMENS ESPRIMO P
ProcEnviron:
 LANGUAGE=de_DE
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-120-generic 
root=UUID=e5cf3fb8-1082-4bca-a343-3fc7ac7f335a ro drm.debug=0xe quiet splash 
plymouth:debug
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/22/2007
dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd.
dmi.bios.version: 6.00 R1.15.2461.A1
dmi.board.name: D2461-A1
dmi.board.vendor: FUJITSU SIEMENS
dmi.board.version: S26361-D2461-A1
dmi.chassis.type: 2
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.chassis.version: ESPP
dmi.modalias: 
dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr6.00R1.15.2461.A1:bd10/22/2007:svnFUJITSUSIEMENS:pnESPRIMOP:pvr:rvnFUJITSUSIEMENS:rnD2461-A1:rvrS26361-D2461-A1:cvnFUJITSUSIEMENS:ct2:cvrESPP:
dmi.product.name: ESPRIMO P
dmi.sys.vendor: FUJITSU SIEMENS
version.compiz: compiz 1:0.9.12.3+16.04.20180221-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.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Mon Apr 16 10:38:12 2018
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.7
xserver.video_driver: nouveau

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


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

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

Title:
  Nach dem Neustart

Status in xorg package in Ubuntu:
  New

Bug description:
  Begleiterscheinung kann auf der Maschine kein Ubuntu 17.04 oder 17.10
  installieren.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-120.144-generic 4.4.117
  Uname: Linux 4.4.0-120-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.16
  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
  Date: Mon Apr 16 10:49:18 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.34, 4.4.0-118-generic, x86_64: installed
   virtualbox, 5.1.34, 4.4.0-120-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation NV43 [GeForce 6600 GT] [10de:0140] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. NV43 [GeForce 6600 GT] [1043:81cf]
  InstallationDate: Installed on 2016-06-22 (662 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: FUJITSU SIEMENS ESPRIMO P
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-120-generic 
root=UUID=e5cf3fb8-1082-4bca-a343-3fc7ac7f335a ro drm.debug=0xe quiet splash

[Touch-packages] [Bug 1762465] Re: Nautilus sidebar theming is confusing