[Touch-packages] [Bug 1682340] Re: Bootup issues

[Timo Aaltonen]

Do you have a broken SD card attached? Look at bootlog.txt

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

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

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

Title:
  Bootup issues

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  2 min boot time on a ssd.

  Not sure if this is a bug or issues with grub.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  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: Thu Apr 13 00:16:58 2017
  DistUpgraded: 2017-04-01 17:41:56,251 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.32, 4.4.0-71-generic, x86_64: installed
   virtualbox, 5.0.32, 4.4.0-72-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Curacao XT [Radeon R7 370 / R9 
270X/370 OEM] [1002:6810] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Curacao XT [Radeon R7 
370 / R9 270X/370 OEM] [174b:e270]
  InstallationDate: Installed on 2017-04-01 (11 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic 
root=UUID=70e462eb-e84a-4333-9f94-c18d079a64e0 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-04-01 (11 days ago)
  dmi.bios.date: 01/23/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FA
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A78M-HD2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFA:bd01/23/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A78M-HD2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  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 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: Wed Apr 12 23:51:28 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.2
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1554795] Re: timeout on restart or shutdown with LUKS root

[Joshua Kugler]

I have this problem on a system, and it *never* finishes stopping. It
prints out a bunch of "timeout" messages about stopping various disks,
then hangs forever stopping the crypt disk.  I'll try to get an image of
it.

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

Title:
  timeout on restart or shutdown with LUKS root

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Using the server install ISO, it's possible to specify root on LUKS
  and variations thereof - for instance, root on LUKS on MD-RAID, root
  on LVM on LUKS on MD-RAID, and so forth. The installer does the right
  thing and initramfs-tools does everything necessary to support booting
  this sort of thing.

  However, systemd gives a 90-second timeout on restart or shutdown,
  presumably because it cannot dispose of the things beneath root.

  It's wholly unclear to me where the 90-second timeout is specified,
  should I wish to shorten it to reboot without the futile delay, but
  more to the point, there seems to be infrastructure for handling this
  kind of situation that doesn't exist in Ubuntu at present.

  I was pointed at this:

  https://www.freedesktop.org/wiki/Software/systemd/InitrdInterface/

  However, Ubuntu seems not to have anything in its initramfs-tools to
  facilitate "shutdown-initrd" functionality.

  I haven't tested this, but I suspect this problem will exist for folks
  running root on MD-RAID without the LUKS as well. Either way, a
  relatively common vanilla install will force 90-second timeouts on
  users, which is unfortunate.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-2ubuntu1 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
  Uname: Linux 4.4.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm 
nvidia_modeset nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Tue Mar  8 18:06:45 2016
  InstallationDate: Installed on 2016-02-24 (13 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160219)
  Lsusb:
   Bus 002 Device 002: ID 1058:0820 Western Digital Technologies, Inc. My 
Passport Ultra (WDBMWV, WDBZFP)
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c408 Logitech, Inc. Marble Mouse (4-button)
   Bus 001 Device 002: ID 046d:c318 Logitech, Inc. Illuminated Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   TERM=xterm-color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-11-generic.efi.signed 
root=/dev/mapper/hostname-root ro net.ifnames=0 biosdevname=0
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/04/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X150M-PRO ECC-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF1:bd12/04/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnX150M-PROECC-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1436330] Re: Network Manager doesn't set metric for local networks any more, causing connection issues

[magowiz]

Please stop spamming, admins please do something, this is a bug
reporting system, not a spam collector, it's not the first time that
spam comments came from this user.

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

Title:
  Network Manager doesn't set metric for local networks any more,
  causing connection issues

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Vivid:
  Fix Released

Bug description:
  [Impact]
  NM changed its method of setting routes on systems, and no longer attaches a 
metric value specific to the type of device being used. These values were used 
to prioritize connections, so that for example, when connected to both wired 
and wireless at the same time, wired can be used in priority over wireless 
without incurring packet loss.
  Currently, when connected to both wired and wireless are connected to the 
same subnet, the user may notice connectivity issues since packets are sent in 
a round-robin fashion over all default routes on the same subnet with the same 
metric.

  [Test Case]
  1- Connect to a wireless network.
  2- Connect to the same network over Ethernet both connections should come up 
on the same subnet.
  3- Make sure there is no packet loss, and that there are specific metric 
values for each default route, as displayed by 'ip route'.

  [Regression Potential]
  Since handling default routes properly involves correcting the behavior for 
all device types, VPN behavior may change to pick up the default routes in all 
cases, over a wired connection. It's also possible that a connection pick up 
the default route when it is not meant to.

  ---

  With Vivid, having two connections to the same network subnet is
  unstable due to missing metrics for local networks.

  Example:

  Being connected to 192.168.1.0/24 via both wired and wireless will
  cause connectivity issues as sent packets hop between the two
  interfaces.

  It used to be that this wasn't an issue. I would go between work and
  home and plug in and my machine would automatically connect to
  wireless and it would use the lower metric ethernet interface for all
  communications, while the wlan interface would remain connected but
  unused.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 25 09:17:27 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-01-25 (58 days ago)
  InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-03-17 (8 days ago)
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1682340] [NEW] Bootup issues

[Art Lopez]

Public bug reported:

2 min boot time on a ssd.

Not sure if this is a bug or issues with grub.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
Uname: Linux 4.4.0-72-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.5
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: Thu Apr 13 00:16:58 2017
DistUpgraded: 2017-04-01 17:41:56,251 DEBUG icon theme changed, re-reading
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.0.32, 4.4.0-71-generic, x86_64: installed
 virtualbox, 5.0.32, 4.4.0-72-generic, x86_64: installed
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Curacao XT [Radeon R7 370 / R9 270X/370 
OEM] [1002:6810] (prog-if 00 [VGA controller])
   Subsystem: PC Partner Limited / Sapphire Technology Curacao XT [Radeon R7 
370 / R9 270X/370 OEM] [174b:e270]
InstallationDate: Installed on 2017-04-01 (11 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic 
root=UUID=70e462eb-e84a-4333-9f94-c18d079a64e0 ro quiet splash
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2017-04-01 (11 days ago)
dmi.bios.date: 01/23/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FA
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: F2A78M-HD2
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFA:bd01/23/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A78M-HD2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
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 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: Wed Apr 12 23:51:28 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.2
xserver.video_driver: radeon

** 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/1682340

Title:
  Bootup issues

Status in xorg package in Ubuntu:
  New

Bug description:
  2 min boot time on a ssd.

  Not sure if this is a bug or issues with grub.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  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: Thu Apr 13 00:16:58 2017
  DistUpgraded: 2017-04-01 17:41:56,251 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.32, 4.4.0-71-generic, x86_64: installed
   virtualbox, 5.0.32, 4.4.0-72-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Curacao XT [Radeon R7 370 / R9 
270X/370 OEM] [1002:6810] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Curacao XT [Radeon R7 
370 / R9 270X/370 OEM] [174b:e270]
  InstallationDate: Installed on 2017-04-01 (11 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   

[Touch-packages] [Bug 1655804] Re: Under Unity8, mir_demo_client_target is distorted and input in the wrong place on start-up

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-zesty-2683

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

Title:
  Under Unity8, mir_demo_client_target is distorted and input in the
  wrong place on start-up

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Under Unity8, mir_demo_client_target is distorted and input in the
  wrong place on start-up.

  Test case:
   1. $ sudo apt install mir-demos
   2. $ mir_demo_client_target -- --desktop_file_hint=unity8
   3. Wiggle the mouse around over the window

  The problem goes away after you manually resize the window.

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

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

[Touch-packages] [Bug 1669524] Re: GTK window functions `Always on Top, Move and Resize' don't work in Mir/Unity8

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-zesty-2683

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

Title:
  GTK window functions `Always on Top, Move and Resize' don't work in
  Mir/Unity8

Status in Canonical System Image:
  In Progress
Status in Mir:
  Fix Committed
Status in MirAL:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Triaged
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 17.04 unity8
  [unity8] Always on Top, Move and Resize doesn't work

  open solitaire, right click on the title bar (see attachement) and
  then select Always on Top. the app doesn't stay on top. same with Move
  and Resize, does nothing

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

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

[Touch-packages] [Bug 1682322] [NEW] PCI/internal sound card not detected dummy drive only

[harry soiland]

Public bug reported:

only the dummy drive is showing in my sound preferences

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
Uname: Linux 4.8.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp3', '/dev/dsp2', 
'/dev/dsp1', '/dev/dsp', '/dev/snd/seq', '/dev/snd/timer', '/dev/sequencer'] 
failed with exit code 1:
CurrentDesktop: Unity
Date: Thu Apr 13 12:53:46 2017
InstallationDate: Installed on 2017-04-05 (7 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/30/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.9
dmi.board.name: 01W6F7
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.9:bd11/30/2016:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn01W6F7:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.name: Inspiron 5567
dmi.sys.vendor: Dell Inc.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  PCI/internal sound card not detected dummy drive only

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  only the dummy drive is showing in my sound preferences

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp3', '/dev/dsp2', 
'/dev/dsp1', '/dev/dsp', '/dev/snd/seq', '/dev/snd/timer', '/dev/sequencer'] 
failed with exit code 1:
  CurrentDesktop: Unity
  Date: Thu Apr 13 12:53:46 2017
  InstallationDate: Installed on 2017-04-05 (7 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/30/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.9
  dmi.board.name: 01W6F7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.9:bd11/30/2016:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn01W6F7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: Inspiron 5567
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1639776] Re: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface

[NJ]

I've installed dnsmasq-base_2.75-1ubuntu0.16.04.2 (on Linux Mint),
installed the 1.2.6 version of Network Manager and . . my VPN still
didn't work; the problem (that I had with network-manager 1.2.6 and the
older version of dnsmasq) wasn't solved. Still, my problem didn't begin
after suspend/resume but rather with boot. Reverting back, once again,
to the 1.2.2 version of Network Manager makes everything work again.

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

Title:
  name resolution (dnsmasq) fails to send queries out after
  suspend/resume reconnects the interface

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in dnsmasq source package in Xenial:
  Fix Released
Status in network-manager source package in Xenial:
  Invalid
Status in dnsmasq source package in Yakkety:
  Fix Released
Status in network-manager source package in Yakkety:
  Invalid
Status in dnsmasq package in Debian:
  Fix Released

Bug description:
  [Impact]

   * suspend/resume (which involves disconnection of network devices)
  leads to dnsmasq failures.

  [Test Case]

   * suspend/resume on 16.04 or 16.10 when using dnsmasq, and see
  failures upon resume.

  [Regression Potential]

   * The fix was NMU'd in Debian in the version immediately after
  16.10's. I believe the regression potential is very low as this is a
  clear bug-fix from upstream.

  ---

  Failure is caused by ENODEV return for all dns queries like:
  sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 
0, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)

  Problem is reported and fixed:
  https://bugzilla.redhat.com/show_bug.cgi?id=1367772

  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b

  I didn't yet test if applying that patch to ubuntu package works. I
  will try the patch in a few hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dnsmasq-base 2.76-4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  7 14:11:51 2016
  InstallationDate: Installed on 2037-12-25 (-7718 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)

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

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

[Touch-packages] [Bug 1669524] Re: GTK window functions `Always on Top, Move and Resize' don't work in Mir/Unity8

[Daniel van Vugt]

** Changed in: mir
Milestone: 0.28.0 => 0.27.0

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

Title:
  GTK window functions `Always on Top, Move and Resize' don't work in
  Mir/Unity8

Status in Canonical System Image:
  In Progress
Status in Mir:
  Fix Committed
Status in MirAL:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Triaged
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 17.04 unity8
  [unity8] Always on Top, Move and Resize doesn't work

  open solitaire, right click on the title bar (see attachement) and
  then select Always on Top. the app doesn't stay on top. same with Move
  and Resize, does nothing

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

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

[Touch-packages] [Bug 1655804] Re: Under Unity8, mir_demo_client_target is distorted and input in the wrong place on start-up

[Daniel van Vugt]

** Changed in: mir
Milestone: 0.28.0 => 0.27.0

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

Title:
  Under Unity8, mir_demo_client_target is distorted and input in the
  wrong place on start-up

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Under Unity8, mir_demo_client_target is distorted and input in the
  wrong place on start-up.

  Test case:
   1. $ sudo apt install mir-demos
   2. $ mir_demo_client_target -- --desktop_file_hint=unity8
   3. Wiggle the mouse around over the window

  The problem goes away after you manually resize the window.

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

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

[Touch-packages] [Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind

[spike speigel]

Also found this:

https://github.com/dell/dkms/issues/2

It's known upstream in debian and dkms, but whether dkms or initramfs-
tools should be responsible for cleaning up files left behind by
dkms...I dunno.  What you posted sounded like it made sense to me.

I just wanted to note at least dkms has an upstream bug report (which
was opened May 2016).

** Bug watch added: github.com/dell/dkms/issues #2
   https://github.com/dell/dkms/issues/2

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

Title:
  /boot/initrd.img-*.old-dkms files left behind

Status in dkms package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  New
Status in dkms package in Debian:
  New

Bug description:
  One notices *.old-dkms files being left behind still sitting on the
  disk after purging the related kernel. This can cause /boot to become
  full, and when it gets really bad, even sudo apt-get autoremove won't
  fix the problem - only deleting the old-dkms files manually solves the
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: dkms 2.2.0.3-2ubuntu3.3
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Nov 12 08:17:10 2015
  InstallationDate: Installed on 2015-05-05 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1682297] [NEW] package libdbusmenu-qt5-2 (not installed) failed to install/upgrade: poging tot overschrijven van '/usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2.6.0', wat ook in

[stefan vlaminckx]

Public bug reported:

i clicked to install a lot of software at once

ProblemType: Package
DistroRelease: Kali 2017.1
Package: libdbusmenu-qt5-2 (not installed)
ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-lowlatency 4.8.17
Uname: Linux 4.8.0-46-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Wed Apr 12 23:45:47 2017
ErrorMessage: poging tot overschrijven van 
'/usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2.6.0', wat ook in pakket 
libdbusmenu-qt5:amd64 0.9.3+16.04.20160218-0ubuntu1 zit
InstallationDate: Installed on 2017-04-11 (1 days ago)
InstallationMedia: Ubuntu-Studio 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
RelatedPackageVersions:
 dpkg 1.18.23kali1
 apt  1.2.19
SourcePackage: libdbusmenu-qt
Title: package libdbusmenu-qt5-2 (not installed) failed to install/upgrade: 
poging tot overschrijven van 
'/usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2.6.0', wat ook in pakket 
libdbusmenu-qt5:amd64 0.9.3+16.04.20160218-0ubuntu1 zit
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: libdbusmenu-qt (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package kali-rolling

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

Title:
  package libdbusmenu-qt5-2 (not installed) failed to install/upgrade:
  poging tot overschrijven van '/usr/lib/x86_64-linux-gnu/libdbusmenu-
  qt5.so.2.6.0', wat ook in pakket libdbusmenu-qt5:amd64
  0.9.3+16.04.20160218-0ubuntu1 zit

Status in libdbusmenu-qt package in Ubuntu:
  New

Bug description:
  i clicked to install a lot of software at once

  ProblemType: Package
  DistroRelease: Kali 2017.1
  Package: libdbusmenu-qt5-2 (not installed)
  ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-lowlatency 4.8.17
  Uname: Linux 4.8.0-46-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Wed Apr 12 23:45:47 2017
  ErrorMessage: poging tot overschrijven van 
'/usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2.6.0', wat ook in pakket 
libdbusmenu-qt5:amd64 0.9.3+16.04.20160218-0ubuntu1 zit
  InstallationDate: Installed on 2017-04-11 (1 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  RelatedPackageVersions:
   dpkg 1.18.23kali1
   apt  1.2.19
  SourcePackage: libdbusmenu-qt
  Title: package libdbusmenu-qt5-2 (not installed) failed to install/upgrade: 
poging tot overschrijven van 
'/usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2.6.0', wat ook in pakket 
libdbusmenu-qt5:amd64 0.9.3+16.04.20160218-0ubuntu1 zit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1682298] [NEW] package libdbusmenu-qt5-2 (not installed) failed to install/upgrade: poging tot overschrijven van '/usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2.6.0', wat ook in

[stefan vlaminckx]

Public bug reported:

i clicked to install a lot of software at once

ProblemType: Package
DistroRelease: Kali 2017.1
Package: libdbusmenu-qt5-2 (not installed)
ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-lowlatency 4.8.17
Uname: Linux 4.8.0-46-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Wed Apr 12 23:45:47 2017
ErrorMessage: poging tot overschrijven van 
'/usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2.6.0', wat ook in pakket 
libdbusmenu-qt5:amd64 0.9.3+16.04.20160218-0ubuntu1 zit
InstallationDate: Installed on 2017-04-11 (1 days ago)
InstallationMedia: Ubuntu-Studio 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
RelatedPackageVersions:
 dpkg 1.18.23kali1
 apt  1.2.19
SourcePackage: libdbusmenu-qt
Title: package libdbusmenu-qt5-2 (not installed) failed to install/upgrade: 
poging tot overschrijven van 
'/usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2.6.0', wat ook in pakket 
libdbusmenu-qt5:amd64 0.9.3+16.04.20160218-0ubuntu1 zit
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: libdbusmenu-qt (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package kali-rolling

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

Title:
  package libdbusmenu-qt5-2 (not installed) failed to install/upgrade:
  poging tot overschrijven van '/usr/lib/x86_64-linux-gnu/libdbusmenu-
  qt5.so.2.6.0', wat ook in pakket libdbusmenu-qt5:amd64
  0.9.3+16.04.20160218-0ubuntu1 zit

Status in libdbusmenu-qt package in Ubuntu:
  New

Bug description:
  i clicked to install a lot of software at once

  ProblemType: Package
  DistroRelease: Kali 2017.1
  Package: libdbusmenu-qt5-2 (not installed)
  ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-lowlatency 4.8.17
  Uname: Linux 4.8.0-46-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Wed Apr 12 23:45:47 2017
  ErrorMessage: poging tot overschrijven van 
'/usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2.6.0', wat ook in pakket 
libdbusmenu-qt5:amd64 0.9.3+16.04.20160218-0ubuntu1 zit
  InstallationDate: Installed on 2017-04-11 (1 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  RelatedPackageVersions:
   dpkg 1.18.23kali1
   apt  1.2.19
  SourcePackage: libdbusmenu-qt
  Title: package libdbusmenu-qt5-2 (not installed) failed to install/upgrade: 
poging tot overschrijven van 
'/usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2.6.0', wat ook in pakket 
libdbusmenu-qt5:amd64 0.9.3+16.04.20160218-0ubuntu1 zit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1673258] Re: Remove aptdaemon and drop or port its reverse-dependencies

[Jeremy Bicha]

Thomas, thanks, the updated version worked.

** Changed in: zeroinstall-injector (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Remove aptdaemon and drop or port its reverse-dependencies

Status in aptdaemon package in Ubuntu:
  New
Status in apturl package in Ubuntu:
  New
Status in dell-recovery package in Ubuntu:
  New
Status in gnome-software package in Ubuntu:
  New
Status in language-selector package in Ubuntu:
  New
Status in lubuntu-software-center package in Ubuntu:
  New
Status in mythbuntu-control-centre package in Ubuntu:
  New
Status in sessioninstaller package in Ubuntu:
  New
Status in software-properties package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  New
Status in ubuntu-mate-welcome package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New
Status in update-notifier package in Ubuntu:
  New
Status in zeroinstall-injector package in Ubuntu:
  Fix Released
Status in aptdaemon source package in aa-series:
  New
Status in apturl source package in aa-series:
  New
Status in dell-recovery source package in aa-series:
  New
Status in gnome-software source package in aa-series:
  New
Status in language-selector source package in aa-series:
  New
Status in lubuntu-software-center source package in aa-series:
  New
Status in mythbuntu-control-centre source package in aa-series:
  New
Status in sessioninstaller source package in aa-series:
  New
Status in software-properties source package in aa-series:
  New
Status in ubiquity source package in aa-series:
  New
Status in ubuntu-mate-meta source package in aa-series:
  New
Status in ubuntu-mate-welcome source package in aa-series:
  New
Status in update-manager source package in aa-series:
  New
Status in update-notifier source package in aa-series:
  New

Bug description:
  aptdaemon is abandoned and unmaintained.  It has already been dropped
  from Debian, but there are several reverse dependencies keeping it in
  Ubuntu.  I will add bug tasks for each of those dependencies, which
  should be ported or dropped themselves.  Then we can get rid of
  aptdaemon too.

  See this mailing list thread for more details:
  https://lists.ubuntu.com/archives/ubuntu-devel/2017-March/039722.html

  https://bitbucket.org/ubuntu-mate/ubuntu-mate-welcome/issues/48/port-
  from-aptdaemon-to-packagekit

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

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

[Touch-packages] [Bug 1682227] [NEW] dnsmasq, network manager *still* not able to relay DNS queries or respond to DNS requests after VPN connection failure / die off

[Thomas Ward]

Public bug reported:

This remains an issue.  Supposedly fixed, it's still an issue in 16.04.

When an OpenVPN connection enables, or dies off, dnsmasq ceases to
respond.  The upstream DNS servers set are two bind9 instances that both
reply to direct queries, so the core issue is that `dnsmasq` is broken.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: dnsmasq-base 2.75-1ubuntu0.16.04.2
ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
Uname: Linux 4.4.0-72-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Apr 12 15:58:28 2017
InstallationDate: Installed on 2016-12-20 (112 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: dnsmasq
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  dnsmasq, network manager *still* not able to relay DNS queries or
  respond to DNS requests after VPN connection failure / die off

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  This remains an issue.  Supposedly fixed, it's still an issue in
  16.04.

  When an OpenVPN connection enables, or dies off, dnsmasq ceases to
  respond.  The upstream DNS servers set are two bind9 instances that
  both reply to direct queries, so the core issue is that `dnsmasq` is
  broken.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: dnsmasq-base 2.75-1ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 12 15:58:28 2017
  InstallationDate: Installed on 2016-12-20 (112 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: dnsmasq
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1682218] Re: package python-minimal 2.7.11-1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1

[Apport retracing service]

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

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 #1682219, 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.

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1682219
   package python-minimal 2.7.11-1 failed to install/upgrade: 子进程 已安装 
post-installation 脚本 返回错误状态 1

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

Title:
  package python-minimal 2.7.11-1 failed to install/upgrade: 子进程 已安装
  post-installation 脚本 返回错误状态 1

Status in python-defaults package in Ubuntu:
  New

Bug description:
  nothing

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-minimal 2.7.11-1
  ProcVersionSignature: Ubuntu 3.13.0-116.163-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-116-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Thu Apr 13 03:26:02 2017
  DuplicateSignature: package:python-minimal:2.7.11-1:子进程 已安装 post-installation 
脚本 返回错误状态 1
  ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 1
  InstallationDate: Installed on 2016-03-26 (382 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: python-defaults
  Title: package python-minimal 2.7.11-1 failed to install/upgrade: 子进程 已安装 
post-installation 脚本 返回错误状态 1
  UpgradeStatus: Upgraded to xenial on 2017-04-12 (0 days ago)

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

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

[Touch-packages] [Bug 1682219] Re: package python-minimal 2.7.11-1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package python-minimal 2.7.11-1 failed to install/upgrade: 子进程 已安装
  post-installation 脚本 返回错误状态 1

Status in python-defaults package in Ubuntu:
  New

Bug description:
  nothing

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-minimal 2.7.11-1
  ProcVersionSignature: Ubuntu 3.13.0-116.163-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-116-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Thu Apr 13 03:26:02 2017
  DuplicateSignature: package:python-minimal:2.7.11-1:子进程 已安装 post-installation 
脚本 返回错误状态 1
  ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 1
  InstallationDate: Installed on 2016-03-26 (382 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: python-defaults
  Title: package python-minimal 2.7.11-1 failed to install/upgrade: 子进程 已安装 
post-installation 脚本 返回错误状态 1
  UpgradeStatus: Upgraded to xenial on 2017-04-12 (0 days ago)

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

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

[Touch-packages] [Bug 1682218] [NEW] package python-minimal 2.7.11-1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1

[justin_xu]

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

Public bug reported:

nothing

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: python-minimal 2.7.11-1
ProcVersionSignature: Ubuntu 3.13.0-116.163-generic 3.13.11-ckt39
Uname: Linux 3.13.0-116-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.23
Architecture: amd64
Date: Thu Apr 13 03:26:02 2017
DuplicateSignature: package:python-minimal:2.7.11-1:子进程 已安装 post-installation 
脚本 返回错误状态 1
ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 1
InstallationDate: Installed on 2016-03-26 (382 days ago)
InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: python-defaults
Title: package python-minimal 2.7.11-1 failed to install/upgrade: 子进程 已安装 
post-installation 脚本 返回错误状态 1
UpgradeStatus: Upgraded to xenial on 2017-04-12 (0 days ago)

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

Title:
  package python-minimal 2.7.11-1 failed to install/upgrade: 子进程 已安装
  post-installation 脚本 返回错误状态 1

Status in python-defaults package in Ubuntu:
  New

Bug description:
  nothing

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-minimal 2.7.11-1
  ProcVersionSignature: Ubuntu 3.13.0-116.163-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-116-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Thu Apr 13 03:26:02 2017
  DuplicateSignature: package:python-minimal:2.7.11-1:子进程 已安装 post-installation 
脚本 返回错误状态 1
  ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 1
  InstallationDate: Installed on 2016-03-26 (382 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: python-defaults
  Title: package python-minimal 2.7.11-1 failed to install/upgrade: 子进程 已安装 
post-installation 脚本 返回错误状态 1
  UpgradeStatus: Upgraded to xenial on 2017-04-12 (0 days ago)

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

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

[Touch-packages] [Bug 1682219] [NEW] package python-minimal 2.7.11-1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1

[justin_xu]

Public bug reported:

nothing

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: python-minimal 2.7.11-1
ProcVersionSignature: Ubuntu 3.13.0-116.163-generic 3.13.11-ckt39
Uname: Linux 3.13.0-116-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.23
Architecture: amd64
Date: Thu Apr 13 03:26:02 2017
DuplicateSignature: package:python-minimal:2.7.11-1:子进程 已安装 post-installation 
脚本 返回错误状态 1
ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 1
InstallationDate: Installed on 2016-03-26 (382 days ago)
InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: python-defaults
Title: package python-minimal 2.7.11-1 failed to install/upgrade: 子进程 已安装 
post-installation 脚本 返回错误状态 1
UpgradeStatus: Upgraded to xenial on 2017-04-12 (0 days ago)

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

Title:
  package python-minimal 2.7.11-1 failed to install/upgrade: 子进程 已安装
  post-installation 脚本 返回错误状态 1

Status in python-defaults package in Ubuntu:
  New

Bug description:
  nothing

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-minimal 2.7.11-1
  ProcVersionSignature: Ubuntu 3.13.0-116.163-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-116-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Thu Apr 13 03:26:02 2017
  DuplicateSignature: package:python-minimal:2.7.11-1:子进程 已安装 post-installation 
脚本 返回错误状态 1
  ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 1
  InstallationDate: Installed on 2016-03-26 (382 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: python-defaults
  Title: package python-minimal 2.7.11-1 failed to install/upgrade: 子进程 已安装 
post-installation 脚本 返回错误状态 1
  UpgradeStatus: Upgraded to xenial on 2017-04-12 (0 days ago)

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

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

[Touch-packages] [Bug 1356651] Re: Logrotate no longer supports symlinked configuration files not owned by root

[Launchpad Bug Tracker]

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

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

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

Title:
  Logrotate no longer supports symlinked configuration files not owned
  by root

Status in logrotate package in Ubuntu:
  Confirmed

Bug description:
  We have been using logrotate 3.7.8 (as part of an Ubuntu 12 build) for
  a long time. When we deploy our application, which has configuration
  files owned by ubuntu user, we create a symlink from the logrotate
  configuration directory (/etc/logrotate.d) to this configuration file,
  which casues our log files to be correctly rotated.

  With our new server build, Ubuntu 14 running logrotate 3.8.7, this
  behaviour has now broken. Running logrotate with the -d flag reveals
  why:

  "Ignoring app-config-file because the file owner is wrong (should be
  root)."

  This appears to be a regression from the 3.7.x release stream of
  logrotate ?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: logrotate 3.8.7-1ubuntu1
  ProcVersionSignature: User Name 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  Date: Thu Aug 14 10:43:48 2014
  Ec2AMI: ami-43128a79
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-southeast-2a
  Ec2InstanceType: m3.large
  Ec2Kernel: aki-c362fff9
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: logrotate
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1671278] Re: Xorg freeze

[Robert Hooker]

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

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

Title:
  Xorg freeze

Status in linux package in Ubuntu:
  New

Bug description:
  Freezes the screen and locks the computer, needing to reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1
  Uname: Linux 4.10.0-11-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Mar  8 20:40:04 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.10.0-11-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.10.0-9-generic, x86_64: installed
   virtualbox, 5.1.14, 4.10.0-11-generic, x86_64: installed
  GpuHangFrequency: Continuously
  GpuHangReproducibility: I don't know
  GpuHangStarted: Within the last few days
  GraphicsCard:
   NVIDIA Corporation G98M [GeForce 9300M GS] [10de:06e9] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell G98M [GeForce 9300M GS] [1028:02bb]
  InstallationDate: Installed on 2014-01-10 (1153 days ago)
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  MachineType: Dell Inc. Vostro 1320
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-11-generic 
root=UUID=5189c31e-9b68-4026-a657-b0d301136218 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/10/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0R235J
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd09/10/2009:svnDellInc.:pnVostro1320:pvrNull:rvnDellInc.:rn0R235J:rvr:cvnDellInc.:ct8:cvrN/A:
  dmi.product.name: Vostro 1320
  dmi.product.version: Null
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.75-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.8.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.13-1

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

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

[Touch-packages] [Bug 1682192] [NEW] Mes imprimantes ne sont pas reconnues par Ubuntu 16.10

[Bird Shamrock]

Public bug reported:

Mes imprimantes sont : Epson WF-3520 et Brother DCP-7030
J'ai chargé un pilote généric esc/p-r pour l'Epson WF-3520 qui a d'abord bien 
fonctionné et puis sans raison apparente, le système a dysfonctionné. Depuis 
aucune de mes imprimantes n'est reconnue par Ubuntu 16.10.

Ubuntu 16.10 est installé en dual boot avec Windows 7 depuis une
semaine.

Juste une précison : je suis nul en programmation informatique  et
comprends avec difficulté la langue anglaise !

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17
Uname: Linux 4.8.0-46-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: i386
BootLog:
 [FAILED] Failed to start Automatic USB/Bluetooth printer setup 
(-devices-pci:00-:00:14.0-usb1-1\x2d5-1\x2d5.1).
 See 'systemctl status 
"udev-configure-printer@-devices-pci:00-:00:14.0-usb1-1\\x2d5-1\\x2d5.1.service"'
 for details.
 [FAILED] Failed to start Automatic USB/Bluetooth printer setup 
(-devices-pci:00-:00:14.0-usb1-1\x2d4).
 See 'systemctl status 
"udev-configure-printer@-devices-pci:00-:00:14.0-usb1-1\\x2d4.service"' 
for details.
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Apr 12 19:12:27 2017
DistUpgraded: Fresh install
DistroCodename: yakkety
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation GF108 [GeForce GT 730] [10de:0f02] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] GF108 [GeForce GT 730] 
[1462:8a9f]
InstallationDate: Installed on 2017-04-01 (11 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2)
MachineType: Gigabyte Technology Co., Ltd. H110M-DS2
ProcEnviron:
 LANGUAGE=fr_FR
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic 
root=UUID=fbe8f99a-28b6-422e-b4fc-52de97bfa3d1 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/16/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F20
dmi.board.asset.tag: Default string
dmi.board.name: H110M-DS2-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF20:bd11/16/2016:svnGigabyteTechnologyCo.,Ltd.:pnH110M-DS2:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnH110M-DS2-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.name: H110M-DS2
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
version.libdrm2: libdrm2 2.4.70-1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.10.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.10.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
xserver.bootTime: Wed Apr 12 20:55:24 2017
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-1ubuntu6.1
xserver.video_driver: nouveau

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


** Tags: apport-bug compiz-0.9 i386 ubuntu yakkety

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

Title:
  Mes imprimantes ne sont pas reconnues par Ubuntu 16.10

Status in xorg package in Ubuntu:
  New

Bug description:
  Mes imprimantes sont : Epson WF-3520 et Brother DCP-7030
  J'ai chargé un pilote généric esc/p-r pour l'Epson WF-3520 qui a d'abord bien 
fonctionné et puis sans raison apparente, le système a dysfonctionné. Depuis 
aucune de mes imprimantes n'est reconnue par Ubuntu 16.10.

  Ubuntu 16.10 est installé en dual boot avec Windows 7 depuis une
  semaine.

  Juste une précison : je suis nul en programmation informatique  et
  comprends avec difficulté la langue anglaise !

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17
  Uname: Linux 4.8.0-46-generic i686
  

[Touch-packages] [Bug 1671278] Re: Xorg freeze

[Michael Richey]

This may be related:

https://bugs.freedesktop.org/show_bug.cgi?id=100545

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

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

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

Title:
  Xorg freeze

Status in linux package in Ubuntu:
  New

Bug description:
  Freezes the screen and locks the computer, needing to reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1
  Uname: Linux 4.10.0-11-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Mar  8 20:40:04 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.10.0-11-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.10.0-9-generic, x86_64: installed
   virtualbox, 5.1.14, 4.10.0-11-generic, x86_64: installed
  GpuHangFrequency: Continuously
  GpuHangReproducibility: I don't know
  GpuHangStarted: Within the last few days
  GraphicsCard:
   NVIDIA Corporation G98M [GeForce 9300M GS] [10de:06e9] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell G98M [GeForce 9300M GS] [1028:02bb]
  InstallationDate: Installed on 2014-01-10 (1153 days ago)
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  MachineType: Dell Inc. Vostro 1320
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-11-generic 
root=UUID=5189c31e-9b68-4026-a657-b0d301136218 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/10/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0R235J
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd09/10/2009:svnDellInc.:pnVostro1320:pvrNull:rvnDellInc.:rn0R235J:rvr:cvnDellInc.:ct8:cvrN/A:
  dmi.product.name: Vostro 1320
  dmi.product.version: Null
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.75-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.8.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.13-1

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

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

[Touch-packages] [Bug 1671278] Re: Xorg freeze

[Michael Richey]

and this:

https://bugs.freedesktop.org/show_bug.cgi?id=100431

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

Title:
  Xorg freeze

Status in linux package in Ubuntu:
  New

Bug description:
  Freezes the screen and locks the computer, needing to reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1
  Uname: Linux 4.10.0-11-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Mar  8 20:40:04 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.10.0-11-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.10.0-9-generic, x86_64: installed
   virtualbox, 5.1.14, 4.10.0-11-generic, x86_64: installed
  GpuHangFrequency: Continuously
  GpuHangReproducibility: I don't know
  GpuHangStarted: Within the last few days
  GraphicsCard:
   NVIDIA Corporation G98M [GeForce 9300M GS] [10de:06e9] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell G98M [GeForce 9300M GS] [1028:02bb]
  InstallationDate: Installed on 2014-01-10 (1153 days ago)
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  MachineType: Dell Inc. Vostro 1320
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-11-generic 
root=UUID=5189c31e-9b68-4026-a657-b0d301136218 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/10/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0R235J
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd09/10/2009:svnDellInc.:pnVostro1320:pvrNull:rvnDellInc.:rn0R235J:rvr:cvnDellInc.:ct8:cvrN/A:
  dmi.product.name: Vostro 1320
  dmi.product.version: Null
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.75-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.8.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.13-1

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

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

[Touch-packages] [Bug 1671278] Re: Xorg freeze

[Michael Richey]

I'm getting the same thing, and I think I can help with some more
information.

When I locked up, I logged in via SSH and checked dmesg. This is what I
found:

[146307.387214] Oops:  [#1] SMP
[146307.387794] Modules linked in: nls_utf8 isofs nls_iso8859_1 ccm rfcomm 
xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat 
nf_nat_ipv4 nf_nat libcrc32c nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack 
nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter 
ebtables ip6table_filter ip6_tables iptable_filter bnep snd_hda_codec_hdmi 
intel_powerclamp coretemp arc4 kvm_intel kvm iwldvm irqbypass mac80211 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 
crypto_simd glue_helper cryptd intel_cstate joydev input_leds serio_raw 
uvcvideo intel_ips videobuf2_vmalloc snd_hda_codec_conexant 
snd_hda_codec_generic videobuf2_memops videobuf2_v4l2 videobuf2_core 
snd_hda_intel lpc_ich iwlwifi snd_hda_codec videodev media snd_hda_core 
snd_hwdep
[146307.390638]  thinkpad_acpi btusb btrtl snd_pcm nvram btbcm cfg80211 btintel 
bluetooth snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device 
snd_timer snd mei_me mei shpchp soundcore mac_hid parport_pc ppdev lp nfsd 
auth_rpcgss nfs_acl lockd grace sunrpc parport ip_tables x_tables autofs4 
hid_generic usbhid hid uas usb_storage nouveau mxm_wmi i2c_algo_bit ttm 
drm_kms_helper psmouse firewire_ohci syscopyarea firewire_core sysfillrect 
crc_itu_t sysimgblt fb_sys_fops e1000e ahci sdhci_pci drm sdhci libahci ptp 
pps_core fjes wmi video
[146307.393265] CPU: 3 PID: 1127 Comm: Xorg Not tainted 4.10.0-19-generic 
#21-Ubuntu
[146307.394157] Hardware name: LENOVO 4349BP9/4349BP9, BIOS 6MET92WW (1.52 ) 
09/26/2012
[146307.395051] task: 94f0ef5f8000 task.stack: a583c367
[146307.395942] RIP: 0010:dma_fence_wait_timeout+0x36/0xf0
[146307.396829] RSP: 0018:a583c3673a38 EFLAGS: 00010206
[146307.397717] RAX: 0001 RBX: 94f0b694a780 RCX: 
c0524fa0
[146307.398623] RDX: 7fff RSI: 0001 RDI: 
94f0e8206540
[146307.399525] RBP: a583c3673a58 R08:  R09: 
94f0e9701000
[146307.400422] R10: 94f0eac1cf00 R11: 94f0f1e77308 R12: 
94f0e8206540
[146307.401323] R13: 0001 R14: 7fff R15: 
0001
[146307.402227] FS:  7f8a8d058a40() GS:94f0fbd8() 
knlGS:
[146307.403123] CS:  0010 DS:  ES:  CR0: 80050033
[146307.404023] CR2: 0021 CR3: 000227fc8000 CR4: 
06e0
[146307.404924] Call Trace:
[146307.405832]  drm_atomic_helper_wait_for_fences+0x48/0x120 [drm_kms_helper]
[146307.406779]  nv50_disp_atomic_commit+0x19c/0x2a0 [nouveau]
[146307.407666]  drm_atomic_commit+0x4b/0x50 [drm]
[146307.408559]  drm_atomic_helper_update_plane+0xec/0x150 [drm_kms_helper]
[146307.409464]  __setplane_internal+0x1b4/0x280 [drm]
[146307.410366]  drm_mode_cursor_universal+0x126/0x210 [drm]
[146307.411270]  drm_mode_cursor_common+0x86/0x180 [drm]
[146307.412172]  drm_mode_cursor_ioctl+0x50/0x70 [drm]
[146307.413067]  drm_ioctl+0x21b/0x4c0 [drm]
[146307.413948]  ? ___sys_recvmsg+0x160/0x1f0
[146307.414831]  ? drm_mode_setplane+0x1a0/0x1a0 [drm]
[146307.415714]  ? ep_ptable_queue_proc+0xa0/0xa0
[146307.416623]  nouveau_drm_ioctl+0x74/0xc0 [nouveau]
[146307.417470]  do_vfs_ioctl+0xa3/0x610
[146307.418352]  ? __sys_recvmsg+0x80/0x90
[146307.419236]  SyS_ioctl+0x79/0x90
[146307.420120]  entry_SYSCALL_64_fastpath+0x1e/0xad
[146307.420995] RIP: 0033:0x7f8a8aa5c987
[146307.421879] RSP: 002b:7fff25084678 EFLAGS: 3246 ORIG_RAX: 
0010
[146307.422779] RAX: ffda RBX: 558657142330 RCX: 
7f8a8aa5c987
[146307.423687] RDX: 7fff250846b0 RSI: c01c64a3 RDI: 
000e
[146307.424613] RBP: 7fff250848e0 R08: 0040 R09: 
0100
[146307.425509] R10: 0040 R11: 3246 R12: 
40086409
[146307.426418] R13: 000e R14: 004a R15: 
5586580445e8
[146307.427315] Code: e5 41 56 41 55 41 54 53 0f 88 b0 00 00 00 49 89 fc 41 89 
f5 49 89 d6 66 66 66 66 90 49 8b 44 24 08 41 0f b6 f5 4c 89 f2 4c 89 e7  50 
20 49 89 c5 66 66 66 66 90 5b 4c 89 e8 41 5c 41 5d 41 5e 
[146307.428288] RIP: dma_fence_wait_timeout+0x36/0xf0 RSP: a583c3673a38
[146307.429252] CR2: 0021
[146307.436588] ---[ end trace 9b23b60c61dac71d ]---

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Freezes the screen and locks the computer, needing to reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1
  Uname: Linux 4.10.0-11-generic x86_64
  

[Touch-packages] [Bug 1680226] Re: Broken SplitDNS resolution in networ-manager VPN after disconnect and reconnect

[Giovanni Panozzo]

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

Solved with dnsmasq-base 2.75-1ubuntu0.16.04.2, thank you.

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

Title:
  Broken SplitDNS resolution in networ-manager VPN after disconnect and
  reconnect

Status in network-manager package in Ubuntu:
  New

Bug description:
  Release: Ubuntu 16.04.2 LTS
  network-manager package version: 1.2.6-0ubuntu0.16.04.1

  I'm using Ubuntu Desktop 16.04 x64 and I have some VPN (OpenVPN and
  Cisco vpnc) connections defined. In all these connections I use both
  split tunnel and split dns.

  When I connect to a remote VPN server, my Ubuntu client correctly resolves 
DNS names in zones pushed by the remode server using the remote DNS server.
  For example: the remote VPN server pushes to the client "DNS resolver is 
192.168.10.1 for domain "vpndom.net"", then "host srv1.vpndom.net" is correctly 
resolved bu 192.168.10.1 and I get 192.168.10.7.

  After disconnecting and reconnecting to the VPN server, my Ubuntu
  client is no longer able to resolve DNS names in zones pushed by the
  VPN servers: "host srv1.vpndom.net" returns host not found.

  As a temporary solution, I downgraded netowrk manager to
  1.2.2-0ubuntu0.16.04.4 and all is working fine. So I think the problem
  is in network-manager 1.2.6-0ubuntu0.16.04.1

  As a workaround, with the connected VPN tunnel, I just "sudo killall
  dnsmasq": NetworkManager will then restart dnsmasq passing it all
  correct DNSes. There is no need to disconnect from the vpn.

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

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

[Touch-packages] [Bug 1589975] Re: Ubuntu 16.04 has Networking problems

[Stephen Rynas]

The bug appears to be resolved. I am not currently experiencing any
issues. I have changed the status to "confirmed", but it does not seem
appropriate from the perspective that I am not an Independent third
party to validate this but. Anyway, the issue appears to be resolved.

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

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

Title:
  Ubuntu 16.04 has Networking problems

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading to Ubuntu 16.04 from Ubuntu 15.10, Ubuntu 16.04 does
  not properly "see" the home network (LAN). Additionally, my printer
  which is also attached to the LAN does not work correctly.

  These are erratic issues, meaning that they don't appear all the time.
  Further, no crash reports are generated either.

  To explain further. The computer running 16.04 will frequently NOT
  show up on the "network" screen. When I go over to the computer
  running Ubuntu 14.04 it also does not show the computer running 16.04
  as being on the LAN.

  In terms of printing, the printer queue shows the print job as "held".
  When you try to release the print job it asks if the printer is
  connected and then goes back to "holding" the print job.

  These actions seem to imply that networking is not working correctly
  with Ubuntu 16.04.

  Please see the comment by Jerrylamos here:
  
http://discourse.ubuntu.com/t/ubuntu-16-04-does-not-display-network-frequently/2768/2?u=ascolais

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.14
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Tue Jun  7 08:41:00 2016
  InstallationDate: Installed on 2016-04-13 (54 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (44 days ago)
  VarLogDistupgradeTermlog:

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

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

[Touch-packages] [Bug 1682055] Re: dh_apparmor does not remove profiles(s) when purging package

[Christian Boltz]

I don't care too much about dh_apparmor (EWRONGDISTRO ;-) - but still:

Are you sure that unloading profiles when uninstalling a package is a
good idea? The binary installed by this package could still be running,
and unloading the profile (= unconfining the binary) might be a security
risk. (I assume there isn't a "killall -9 $binary" in the purge script
;-)

There might be rare cases where keeping a superfluous/deleted profile
loaded causes problems (if another package installs a binary with the
same name), but this is probably a corner case and would qualify as
erroring out on the safe side IMHO.

This basically also applies to renamed profiles - it's better to keep a
superfluous profile loaded than to accidently unconfine a running
process.

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

Title:
  dh_apparmor does not remove profiles(s) when purging package

Status in apparmor package in Ubuntu:
  New

Bug description:
  dh_apparmor adds an entry to remove apparmor profiles added by a
  package when purging that package. However, it leaves the profiles
  loaded in the kernel; it should unload them from the kernel before
  removing them from the disk.

  Secondly, dh_apparmor could make life easier for maintainers when
  upgrading packages and the profile changes the name of profiles, child
  profiles, or hats contained within a profile file. Without this, the
  update can leave behind profiles etc. loaded into the kernel post a
  package update. This would ideally need to be triggered only when the
  upgrading package is older than a given version.

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

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

[Touch-packages] [Bug 1658921] Re: NetworkManager does not manage wired connection

[Chip Rosenthal]

I encountered this defect defect on an upgrade from 16.04 to 16.10. I
removed the /usr/lib/NetworkManager/conf.d/10-globally-managed-
devices.conf file and it resolved the problem.

Any reason why a fix is not being applied?

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

Title:
  NetworkManager does not manage wired connection

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  NetworkManager does not manage my wired eth0 connection, no matter how
  I set /etc/network/interfaces or
  /etc/NetworkManager/NetworkManager.conf

  Using ubuntu 16.04, /etc/network/interfaces only managed lo, and
  [ifupdown] section of NetworkManager.conf had set managed=false.

  With these same settings, after upgrading to ubuntu 16.10, eth0
  appears as unmanaged in nm-applet.

  If I modify /etc/network/interfaces and add

  auto eth0
  iface eth0 inet dhcp

  And set managed=true in NetworkManager.conf [ifupdown] section, eth0
  is still unmanaged despite it does get an IP from DHCP server.

  This is happening in my five computers (two laptops and three
  desktops).

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

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

[Touch-packages] [Bug 1586659] Re: Notification don't appear when I'm in full screen mode

[Alberto Salvia Novella]

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

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

Title:
  Notification don't appear when I'm in full screen mode

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When I use full screen in different app. the notification about
  battery charge (especially when it's low) don't appear. When I don't
  use full screen, the notification appear. It's problematic because
  when the battery is low, I don't have notification before the laptop
  shut down.

  The same problem occur with Firefox and VLC.

  More info: The notification seem to be created but not showing on
  screen. If I'm in full screen and I return to regular mode, the
  notification appear. Also, if I'm in regular mode and the notification
  appear, when I change for the full screen mode, the notification stay
  on screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat May 28 11:36:06 2016
  DistUpgraded: 2016-05-11 12:46:43,015 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.248+bdcom, 4.4.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] 
[1002:9851] (rev 45) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] 
[103c:80cb]
  InstallationDate: Installed on 2016-03-02 (87 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: HP HP Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=06f354f2-97a2-48a8-8ead-4bb66400bfa1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-05-11 (16 days ago)
  dmi.bios.date: 10/19/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1C
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 80CB
  dmi.board.vendor: HP
  dmi.board.version: 99.42
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1C:bd10/19/2015:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn80CB:rvr99.42:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  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
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat May 28 06:45:13 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1589975] Re: Ubuntu 16.04 has Networking problems

[Alberto Salvia Novella]

If you are still experiencing this bug, please set status back to
"confirmed".

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

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

Title:
  Ubuntu 16.04 has Networking problems

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading to Ubuntu 16.04 from Ubuntu 15.10, Ubuntu 16.04 does
  not properly "see" the home network (LAN). Additionally, my printer
  which is also attached to the LAN does not work correctly.

  These are erratic issues, meaning that they don't appear all the time.
  Further, no crash reports are generated either.

  To explain further. The computer running 16.04 will frequently NOT
  show up on the "network" screen. When I go over to the computer
  running Ubuntu 14.04 it also does not show the computer running 16.04
  as being on the LAN.

  In terms of printing, the printer queue shows the print job as "held".
  When you try to release the print job it asks if the printer is
  connected and then goes back to "holding" the print job.

  These actions seem to imply that networking is not working correctly
  with Ubuntu 16.04.

  Please see the comment by Jerrylamos here:
  
http://discourse.ubuntu.com/t/ubuntu-16-04-does-not-display-network-frequently/2768/2?u=ascolais

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.14
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Tue Jun  7 08:41:00 2016
  InstallationDate: Installed on 2016-04-13 (54 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (44 days ago)
  VarLogDistupgradeTermlog:

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

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

[Touch-packages] [Bug 1579495] Re: Getpocket account doesnt stay

[Alberto Salvia Novella]

** Changed in: gnome-online-accounts (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Getpocket account doesnt stay

Status in gnome-online-accounts package in Ubuntu:
  Confirmed

Bug description:
  First, I had several accounts linked and with every upgrade or clean
  install, the accounts remainded unreachable.

  Had to erase "goa-1.0" and "libaccounts-glib" from .local in order to
  enable the accounts (Remove and recreate doesn't work).

  Finally, the pocket account doesn't create an account and dont know if its 
active (it seems not since getpocket.com doesnt show me so (Using firefox 
account). 
  Then, if I try to re-enable it, using a google account, it just simple doesnt 
budge after I clic the option. 

  Any clue on how to debug that?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-online-accounts 3.18.3-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun May  8 03:54:55 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-23 (14 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1682154] Re: loginctl ignoring user given sessions IDs at command-line

[Bug Watch Updater]

** Changed in: systemd
   Status: Unknown => New

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

Title:
  loginctl ignoring user given sessions IDs at command-line

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

Bug description:
  Kubuntu zesty, 232-21ubuntu2

  See upstream bug https://github.com/systemd/systemd/issues/5733 with
  patch attached.

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

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

[Touch-packages] [Bug 1264381] Re: Cryptsetup/LVM should not complain about missing crypopts option

[Launchpad Bug Tracker]

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

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Confirmed

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

Title:
  Cryptsetup/LVM should not complain about missing crypopts option

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  The Message: "cryptsetup: lvm fs found but no lvm configured" should not come 
up anymore, when not have any cmdline_cryptopts=
  in our kernel parameters. 

  Setting up a lvm2 volume group, also for crypted volumes, is a job of
  udev now, by my understanding!

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

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

[Touch-packages] [Bug 1510570] Re: BLE pairing fail

[Kai-Heng Feng]

The change is intended - please check comment #3.

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

Title:
  BLE pairing fail

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  On 15.10 we now have bluez 5 so we can pair BLE devices like the
  Microsoft Arc Touch Bluetooth Mouse.

  But this pairing doesn't work very well. Mouse is seen but pairing fail.
  More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5

  This is due to udev rule that use "hcitool" to power on device.
  Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used 
instead of udev rules.

  here is a commit with this parameter: 
http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138
  And a ppa to test it: 
https://code.launchpad.net/~guilhem-fr/+archive/ubuntu/bluez-autoenable

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

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

[Touch-packages] [Bug 1664222] Re: Update evolution-data-server to 3.22.7

[Jeremy Bicha]

I tested this update by installing evolution 3.22.6-0ubuntu0.1 which
pulled in evolution-data-server 3.22.7-0ubuntu0.1 on Ubuntu GNOME 16.10.
I restarted. I opened Settings>Online Accounts (this is GNOME Settings,
not Evolution Settings) and added my Google account. I then opened
Evolution. My Google Calendar and Contacts synced successfully. My email
synced successfully with IMAP. I was able to open plain text and HTML
emails. And I sent a test email from Evolution that I received
successfully in another account outside of Evolution.

I also verified that the GNOME Calendar and Contacts apps showed the
right data from my Google account.

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

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

Title:
  Update evolution-data-server to 3.22.7

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution-data-server source package in Yakkety:
  Fix Committed

Bug description:
  Impact
  ==
  This is the third evolution SRU for yakkety. This update includes the new 
bugfix releases 3.22.4, 3.22.5, 3.22.6 and 3.22.7. Updating e-d-s is required 
to update evolution to 3.22.6 (LP: #1664226)

  https://git.gnome.org/browse/evolution-data-server/tree/NEWS/?h=gnome-3-22
  https://git.gnome.org/browse/evolution-data-server/log/?h=gnome-3-22

  Test Case
  =
  After installing the update, restart your computer.

  Run several eds-using apps like Evolution, GNOME Calendar and verify
  that they continue to run at least as well as before this update.

  Regression Potential
  
  Low. There are a fair number of changes in this update, but they are all 
targeted towards fixing bugs. This is the same release that other GNOME 3.22 
distros (like Debian stretch) ship. This may be the last official 3.22 release 
for the Evolution stack now that 3.24.0 has been released.

  3.22.6 introduced a regression in pop3 support that was fixed within a
  week by 3.22.7.

  Other Info
  ==
  Ubuntu 17.04 will stick with Evolution 3.22 (not 3.24).

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

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

[Touch-packages] [Bug 1682154] Re: loginctl ignoring user given sessions IDs at command-line

[slodki]

** Bug watch added: github.com/systemd/systemd/issues #5733
   https://github.com/systemd/systemd/issues/5733

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

** Tags added: patch

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

Title:
  loginctl ignoring user given sessions IDs at command-line

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Kubuntu zesty, 232-21ubuntu2

  See upstream bug https://github.com/systemd/systemd/issues/5733 with
  patch attached.

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

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

[Touch-packages] [Bug 1682154] [NEW] loginctl ignoring user given sessions IDs at command-line

[slodki]

Public bug reported:

Kubuntu zesty, 232-21ubuntu2

See upstream bug https://github.com/systemd/systemd/issues/5733 with
patch attached.

** Affects: systemd
 Importance: Unknown
 Status: Unknown

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


** Tags: loginctl patch patch-forwarded-upstream zesty

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

** Tags added: loginctl patch-forwarded-upstream zesty

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

Title:
  loginctl ignoring user given sessions IDs at command-line

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Kubuntu zesty, 232-21ubuntu2

  See upstream bug https://github.com/systemd/systemd/issues/5733 with
  patch attached.

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

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

[Touch-packages] [Bug 1510570] Re: BLE pairing fail

[Robie Basak]

Rejecting from the Xenial queue due to the lack of response.

If this still needs fixing in Xenial, please see
https://wiki.ubuntu.com/StableReleaseUpdates and follow
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure.

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

Title:
  BLE pairing fail

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  On 15.10 we now have bluez 5 so we can pair BLE devices like the
  Microsoft Arc Touch Bluetooth Mouse.

  But this pairing doesn't work very well. Mouse is seen but pairing fail.
  More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5

  This is due to udev rule that use "hcitool" to power on device.
  Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used 
instead of udev rules.

  here is a commit with this parameter: 
http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138
  And a ppa to test it: 
https://code.launchpad.net/~guilhem-fr/+archive/ubuntu/bluez-autoenable

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

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

[Touch-packages] [Bug 1668813] Re: The tc man page references tc-index man page but tc-index man page does not exist

[Robie Basak]

IMHO (wearing my ~ubuntu-sru hat), we can and should bundle this with
some other iproute2 update. But users also get frustrated with the
number of updates they receive, so I don't think it's worth doing this
one on its own.

Let's see if any other ~ubuntu-sru comes by and disagrees. Otherwise, I
propose to reject this from the queue the next time I come round to it,
but we can leave the bug open so hopefully someone else preparing a
different iproute2 SRU can bundle the fix.

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

Title:
  The tc man page references tc-index man page but tc-index man page
  does not exist

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

Bug description:
  [Impact]

   * The man pages for tc make reference to a non-existent tc-index man
  page. Purely a typo that should have been tc-tcindex.

   *  Purely a documentation fix, but nice to fix for an LTS release
  that has many years left to it.

  
  [Test Case]

   * To see this issue, fire up a 16,04 image (I did so via lxd) and
  type:

 root@xi386# man tc | grep tc-index
   Filter packets based on traffic control index. See 
tc-index(8).

  , HOWEVER:

 root@xi386:~# man tc-index
 No manual entry for tc-index

  
  * on a fixed system you should only see refereces to tc-tcindex, not tc-index:

 root@x1:~# man tc | grep tc-index
 root@x1:~# man tc | grep tc-tcindex
   Filter packets based on traffic control index. See 
tc-tcindex(8).
red(8), tc-route(8), tc-sfb(8), tc-sfq(8), tc-stab(8), tc-tbf(8), 
tc-tcindex(8), tc-u32(8),


  
  [Regression Potential] 

   * This is only a change to man pages, so any regression would be non-
  functional, but this fix is trivial to fix and verify, and the fix is
  exactly from the upstream.

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

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

[Touch-packages] [Bug 1674164] Re: DVDs with restricted permissions are unreadable for normal user (regression?)

[Phillip Susi]

"differently correct" is no less a lie than "alternative facts".  Your
recorder is broken, period.  Complain to the manufacturer to fix their
firmware or see if they already have an update.  Printed DVDs use the
correct permissions.  UDF also goes on rewritable media, optical or
flash or otherwise, and the correct permissions need to be retained or
you end up with either files that are never executable or always
executable, and no ability to write protect files.

That said, it might be a reasonable workaround to detect the somewhat
silly situation of the root directory not being readable by anyone and
then override the permissions, only under that condition.  Or perhaps
there is a unique device string in the UDF header that identifies this
particular broken burner that can key on it.  What does blkid -p
/dev/sr0 have to say about this disc?


** Package changed: util-linux (Ubuntu) => udisks2 (Ubuntu)

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

** Changed in: udisks2 (Ubuntu)
   Status: Invalid => Triaged

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

Title:
  DVDs with restricted permissions are unreadable for normal user
  (regression?)

Status in udisks2 package in Ubuntu:
  Triaged

Bug description:
  I'm using 16.10. I have a DVD with strange permissions for the root
  folder:

  michele@cassandra:~$ ls -l /media/michele
  total 2
  d--x--x--- 3 michele michele 88 gen  1  2004 SONY_DVD_RECORDER_VOLUME

  The DVD is readable e.g. on windows but with ubuntu while I can access
  it as root:

  root@cassandra:~# ls -l /media/michele/SONY_DVD_RECORDER_VOLUME/
  total 4
  dr-xr-xr-x 2 michele michele 3628 gen  1  2004 VIDEO_TS

  I cannot as the non-root user that is logged in when I insert the
  disk:

  michele@cassandra:~$ ls -l /media/michele/SONY_DVD_RECORDER_VOLUME
  ls: cannot open directory '/media/michele/SONY_DVD_RECORDER_VOLUME': 
Permission denied

  Looking at the mount options it seems to me that this is a regression
  for bug #10550. The options used by udisks2 are:

  root@cassandra:~# mount |grep SONY
  /dev/sr0 on /media/michele/SONY_DVD_RECORDER_VOLUME type udf 
(ro,nosuid,nodev,relatime,uid=1000,gid=1000,iocharset=utf8,uhelper=udisks2)

  while my understanding from bug #10550 is that I should have also
  mode=0777 and dmode=0777

  And indeed this works:

  root@cassandra:~# mount -t udf -o
  
ro,nosuid,nodev,relatime,uid=1000,gid=1000,iocharset=utf8,uhelper=udisks2,mode=0777,dmode=0777
  /dev/sr0 ~michele/z

  michele@cassandra:~$ ls -l ~michele/z
  total 4
  drwxrwxrwx 2 michele michele 3628 gen  1  2004 VIDEO_TS

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

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

[Touch-packages] [Bug 1677626] Re: Lock-Screen: Unity falls-back to old screensaver lock if onscreen keyboard is enabled (Zesty)

[Andrea Azzarone]

This is the wanted behaviour considering that Unity lockscreen does not
support a11y and fixing this is too time-expensive.

** No longer affects: lightdm (Ubuntu)

** No longer affects: onboard (Ubuntu)

** No longer affects: unity-settings-daemon (Ubuntu)

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

** Changed in: unity (Ubuntu)
   Status: Invalid => Won't Fix

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

Title:
  Lock-Screen: Unity falls-back to old screensaver lock if onscreen
  keyboard is enabled (Zesty)

Status in unity package in Ubuntu:
  Won't Fix

Bug description:
  Unity falls-back to old lock from gnome-screensaver if accessibility
  is enabled because accessibility in the new lock-screen is partially
  broken. Please fix accessibility for new lock-screen

  How to reproduce:
  -
  1. Go to system-settings ⟶ Universal Access ⟶ Seeing
  2. Turn on Screen-Reader
  3. Restart lightdm or reboot
  4. Press CTRL+ALT+L

  Current Behavior:
  -
  It uses old screensaver lock instead of unity-greeter.

  Expected Behavior:
  
  It should be using new lock-screen

  Severity: High
  ---
  This bug is pretty well hidden. Sometimes when app which depends on-screen 
keyboard (ex: orca) gets updated, it automatically turns on screen-reader. It 
can also get turned on if user accidentally press CTRL+ALT+S. User will have no 
clue whats hit him.

  Reason:
  
  Accessibility is enabled because accessibility in the new lock-screen is 
partially broken. It was supposed to be fixed for 16.04, but that didn't happen.

  ⇛ Please fix accessibility for new lock-screen. Thanks

  Info:
  --
  OS: Ubuntu 17.04 (32 bit/64bit)

  unity-settings-daemon: 15.04.1+17.04.20170328-0ubuntu1

  gnome-screensaver: 3.6.1-7ubuntu5

  unity: 7.5.0+17.04.20170301-0ubuntu1

  lightdm: 1.22.0-0ubuntu1

  lignome-desktop-3-12: 3.24.0-0ubuntu1

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

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

[Touch-packages] [Bug 1682136] [NEW] dnsmasq bad hex constant with 2 mac addresses but not true

[Dash]

Public bug reported:

Following line of dnsmasq.conf will not allow dnsmasq to start giving
error "bad hex constant at line x in /etc/dnsmasq.conf" and this despite
the fact that there is no error in mac addresses.

dhcp-
host=a8:6b:ad:4b:83:bf,44:a8:42:fb:a2:df,172.16.30.47,w10-assist1,net:ordi,infinite,set:ordi

With only one of those two mac addresses, all is good, so there is no
error in mac addresses. In the dnsmasq.conf they are other dhcp-host
with multiple mac addresses like

dhcp-
host=a8:6b:ad:4a:d9:d3,44:a8:42:fb:a2:85,00:24:9b:12:71:be,172.16.30.43,w10-pierre,net:ordi,infinite,set:ordi

and they are not rejected.

When copying the default configuration line in a dnsmasq-2.72-3 of
Debian 8.7, no problem.

Description:Ubuntu 12.04.5 LTS
Release:12.04

dnsmasq:
  Installé : 2.59-4ubuntu0.2
  Candidat : 2.59-4ubuntu0.2
 Table de version :
 *** 2.59-4ubuntu0.2 0
500 http://fr.archive.ubuntu.com/ubuntu/ precise-updates/universe amd64 
Packages
500 http://security.ubuntu.com/ubuntu/ precise-security/universe amd64 
Packages
100 /var/lib/dpkg/status
 2.59-4 0
500 http://fr.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: dnsmasq 2.59-4ubuntu0.2 [modified: etc/dnsmasq.conf]
ProcVersionSignature: Ubuntu 3.13.0-116.163~precise1-generic 3.13.11-ckt39
Uname: Linux 3.13.0-116-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.15
Architecture: amd64
Date: Wed Apr 12 15:25:20 2017
MarkForUpload: True
PackageArchitecture: all
SourcePackage: dnsmasq
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.dnsmasq.conf: 2017-04-12T12:04:33.732724

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


** Tags: amd64 apport-bug precise

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

Title:
  dnsmasq bad hex constant with 2 mac addresses but not true

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  Following line of dnsmasq.conf will not allow dnsmasq to start giving
  error "bad hex constant at line x in /etc/dnsmasq.conf" and this
  despite the fact that there is no error in mac addresses.

  dhcp-
  
host=a8:6b:ad:4b:83:bf,44:a8:42:fb:a2:df,172.16.30.47,w10-assist1,net:ordi,infinite,set:ordi

  With only one of those two mac addresses, all is good, so there is no
  error in mac addresses. In the dnsmasq.conf they are other dhcp-host
  with multiple mac addresses like

  dhcp-
  
host=a8:6b:ad:4a:d9:d3,44:a8:42:fb:a2:85,00:24:9b:12:71:be,172.16.30.43,w10-pierre,net:ordi,infinite,set:ordi

  and they are not rejected.

  When copying the default configuration line in a dnsmasq-2.72-3 of
  Debian 8.7, no problem.

  Description:Ubuntu 12.04.5 LTS
  Release:12.04

  dnsmasq:
Installé : 2.59-4ubuntu0.2
Candidat : 2.59-4ubuntu0.2
   Table de version :
   *** 2.59-4ubuntu0.2 0
  500 http://fr.archive.ubuntu.com/ubuntu/ precise-updates/universe 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu/ precise-security/universe 
amd64 Packages
  100 /var/lib/dpkg/status
   2.59-4 0
  500 http://fr.archive.ubuntu.com/ubuntu/ precise/universe amd64 
Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: dnsmasq 2.59-4ubuntu0.2 [modified: etc/dnsmasq.conf]
  ProcVersionSignature: Ubuntu 3.13.0-116.163~precise1-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-116-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.15
  Architecture: amd64
  Date: Wed Apr 12 15:25:20 2017
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: dnsmasq
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.dnsmasq.conf: 2017-04-12T12:04:33.732724

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

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

[Touch-packages] [Bug 1682133] [NEW] Dual screen is broken

[Nicolas]

Public bug reported:

Hi,

After an update of Ubuntu 14.04 and a reboot, my second screen was not 
recognized by the laptop.
This is the second time I get this. Last time I had to re-install all my 
stuffs...

Laptop: Samsung NP900X3G
System: Ubuntu 14.04.5 LTS
Graphic card: Intel (00:02.0 VGA compatible controller: Intel Corporation 
Haswell-ULT Integrated Graphics Controller (rev 09))

Need more informations, tell me thx.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
Uname: Linux 4.4.0-72-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.23
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed Apr 12 09:24:07 2017
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Samsung Electronics Co Ltd Device [144d:c109]
InstallationDate: Installed on 2016-04-18 (358 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3G
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic 
root=UUID=5e26e584-5e80-41c8-9b69-9a0e61826dff ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/23/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P05ADU.025.140523.PS
dmi.board.asset.tag: No Asset Tag
dmi.board.name: SAMSUNG_NP1234567890
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SAMSUNG_SW_REVISION_1234567890ABCD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP05ADU.025.140523.PS:bd05/23/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3G:pvrP05ADU:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrSAMSUNG_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
dmi.product.name: 900X3G
dmi.product.version: P05ADU
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Wed Apr 12 09:23:02 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1495 
 vendor BOE
xserver.version: 2:1.18.3-1ubuntu2.3~trusty1

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


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

** Attachment added: "Xorg latest log"
   https://bugs.launchpad.net/bugs/1682133/+attachment/4860657/+files/Xorg.0.log

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

Title:
  Dual screen is broken

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi,

  After an update of Ubuntu 14.04 and a reboot, my second screen was not 
recognized by the laptop.
  This is the second time I get this. Last time I had to re-install all my 
stuffs...

  Laptop: Samsung NP900X3G
  System: Ubuntu 14.04.5 LTS
  Graphic card: Intel (00:02.0 VGA compatible controller: Intel Corporation 
Haswell-ULT Integrated Graphics Controller (rev 09))

  Need more informations, tell me thx.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Apr 12 09:24:07 2017
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller 

[Touch-packages] [Bug 1681652] Re: Laptop screen does not turn off when closing lid from login screen.

[slodki]

I think you don't have problems with login screen (where new desktop session is 
launched) but with screen locker tool, running in active session.
You should check if problem exists when you logout from desktop session to 
login screen - this is different piece of software, not related to selected 
user desktop session (plasma/gnome/etc. with own screenlocker).

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

Title:
  Laptop screen does not turn off when closing lid from login screen.

Status in systemd package in Ubuntu:
  New

Bug description:
  I'm running a new install of Ubuntu 16.04.2 LTS on a Dell Rugged Extreme 7414.
  I only changed in Power Settings: When plugged in >  When lid is close = Do 
Nothing
  Brightness & Lock Settings were not changed; Lock Screen after: Screen turns 
off

  If I close the laptop lid while logged in at the Unity Desktop, the
  screen will fade to black and turn off, which I think is normal and
  expected.

  Then when I open the lid I get the login screen, which I also expect.

  Now, if I don't login and just close the lid, the screen does not fade to 
black nor turn off.
  I would expect the screen to fade to black and turn off also from the login 
screen.

  This appears to be a small issue, at least on my system.
  If anyone needs specific information about the system, please ask.

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

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

[Touch-packages] [Bug 1666515] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From heinz-werner_se...@de.ibm.com 2017-04-12 08:34 EDT---
IBM Bugzilla status -> closed. This request is terminated. If a real customer 
need will come up in the future for 16.04 LTS, a new bugzilla will be launched.

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

Title:
  Enable tbb package on Ubuntu 16.04 LTS

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in tbb package in Ubuntu:
  Fix Released
Status in tbb source package in Xenial:
  Incomplete
Status in tbb source package in Yakkety:
  Fix Released
Status in tbb source package in Zesty:
  Fix Released

Bug description:
  tbb package is available since Yaketty 16.10..
  As mentioned here  https://launchpad.net/ubuntu/+source/tbb

  Potential customer case requires this package also compile on s390x for 
Xenial.
  =
  Changes (w.r.t. Intel TBB 4.4 Update 2):
  =
  - Modified parallel_sort to not require a default constructor for values
  ??? and to use iter_swap() for value swapping.
  - Added support for creating or initializing a task_arena instance that
  ??? is connected to the arena currently used by the thread.
  - graph/binpack example modified to use multifunction_node.
  - For performance analysis, use Intel(R) VTune(TM) Amplifier XE 2015
  ??? and higher; older versions are no longer supported.
  - Improved support for compilation with disabled RTTI, by omitting its use
  ??? in auxiliary code, such as assertions. However some functionality,
  ??? particularly the flow graph, does not work if RTTI is disabled.
  - The tachyon example for Android* can be built using Android Studio 1.5
  ??? and higher with experimental Gradle plugin 0.4.0.
  Preview Features:
  - Added class opencl_subbufer that allows using OpenCL* sub-buffer
  ??? objects with opencl_node.
  - Class global_control supports the value of 1 for
  ??? max_allowed_parallelism.
  Bugs fixed:
  - Fixed a race causing "TBB Warning: setaffinity syscall failed" message.
  - Fixed a compilation issue on OS X* with Intel(R) C++ Compiler 15.0.
  - Fixed a bug in queuing_rw_mutex::downgrade() that could temporarily
  ??? block new readers.
  - Fixed speculative_spin_rw_mutex to stop using the lazy subscription
  ??? technique due to its known flaws.
  - Fixed memory leaks in the tool support code.

  =
  Changes (w.r.t. Intel TBB 4.4 Update 3):
  =
  - Removed a few cases of excessive user data copying in the flow graph.
  - Improved robustness of concurrent_bounded_queue::abort() in case of
  ? ? simultaneous push and pop operations.
  Preview Features:
  - Added tbb::flow::async_msg, a special message type to support
  ? ? communications between the flow graph and external asynchronous
  ? ? activities.
  - async_node modified to support use with C++03 compilers.
  Bugs fixed:
  - Fixed a bug in dynamic memory allocation replacement for Windows* OS.
  - Fixed excessive memory consumption on Linux* OS caused by enabling
  ? ? zero-copy realloc.
  - Fixed performance regression on Intel(R) Xeon Phi(tm) coprocessor with
  ? ? auto_partitioner.

  =
  Changes (w.r.t. Intel TBB 4.4 Update 4):
  =
  - Modified graph/fgbzip2 example to remove unnecessary data queuing.
  Preview Features:
  - Added a Python* module which is able to replace Python's thread pool?
  ? ? class with the implementation based on Intel TBB task scheduler.
  Bugs fixed:
  - Fixed the implementation of 64-bit tbb::atomic for IA-32 architecture
  ? ? to work correctly with GCC 5.2 in C++11/14 mode.
  - Fixed a possible crash when tasks with affinity (e.g. specified via
  ? ? affinity_partitioner) are used simultaneously with task priority
  ? ? changes.
  You can download Intel TBB 4.4 update 5 from open source site.

  =
  After inclusion of these mentioned fixes, it runs on Yaketty..!

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

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

[Touch-packages] [Bug 1639776] Re: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface

[Launchpad Bug Tracker]

This bug was fixed in the package dnsmasq - 2.75-1ubuntu0.16.04.2

---
dnsmasq (2.75-1ubuntu0.16.04.2) xenial; urgency=medium

  * Add two upstream patches to fix binding to an interface being
destroyed and recreated. LP: #1639776.
  + 2675f2061525bc954be14988d64384b74aa7bf8b
  + 16800ea072dd0cdf14d951c4bb8d2808b3dfe53d

 -- Nishanth Aravamudan   Mon, 27 Mar
2017 17:22:13 -0700

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

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

Title:
  name resolution (dnsmasq) fails to send queries out after
  suspend/resume reconnects the interface

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in dnsmasq source package in Xenial:
  Fix Released
Status in network-manager source package in Xenial:
  Invalid
Status in dnsmasq source package in Yakkety:
  Fix Released
Status in network-manager source package in Yakkety:
  Invalid
Status in dnsmasq package in Debian:
  Fix Released

Bug description:
  [Impact]

   * suspend/resume (which involves disconnection of network devices)
  leads to dnsmasq failures.

  [Test Case]

   * suspend/resume on 16.04 or 16.10 when using dnsmasq, and see
  failures upon resume.

  [Regression Potential]

   * The fix was NMU'd in Debian in the version immediately after
  16.10's. I believe the regression potential is very low as this is a
  clear bug-fix from upstream.

  ---

  Failure is caused by ENODEV return for all dns queries like:
  sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 
0, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)

  Problem is reported and fixed:
  https://bugzilla.redhat.com/show_bug.cgi?id=1367772

  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b

  I didn't yet test if applying that patch to ubuntu package works. I
  will try the patch in a few hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dnsmasq-base 2.76-4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  7 14:11:51 2016
  InstallationDate: Installed on 2037-12-25 (-7718 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)

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

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

[Touch-packages] [Bug 1681912] Re: [Zesty] missing dnsmasq-base package breaks NetworkManager connection sharing feature

[Etienne Papegnies]

** Description changed:

  Network settings in Zesty allow users to define a connection as "Shared
  to other computers", this does not currently work in Ubuntu MATE 17.04
  Beta 2 at least for wired connections.
  
- The reason, from the logs is that dnsmasq binary, from dnsmasq package
- is not present:
+ The reason, from the logs is that dnsmasq binary is not present:
  
  [...]
  Apr 11 20:37:22 Edge NetworkManager[946]:   [1491935842.1052] 
Executing: /sbin/iptables --table nat --insert POSTROUTING --source 
10.42.0.0/255.255.255.0 ! --destination 10.42.0.0/255.255.255.0 --jump 
MASQUERADE
  Apr 11 20:37:22 Edge NetworkManager[946]:  [1491935842.1117] device 
(enp1s0f2): share: (enp1s0f2) failed to start dnsmasq: Could not find "dnsmasq" 
binary
  Apr 11 20:37:22 Edge NetworkManager[946]:   [1491935842.1119] 
Executing: /sbin/iptables --table nat --delete POSTROUTING --source 
10.42.0.0/255.
  [...]
  
  The way to setup a (wired) connection sharing is as follow:
  
  - Go to Network Connection settings and select the wired connection
  - Under [IPv4 Settings -> Method] select "Shared to other computers"
  
- 
- ouroumov@Edge:~$ apt-cache policy dnsmasq
- dnsmasq:
-   Installed: (none)
-   Candidate: 2.76-5
-   Version table:
-  2.76-5 500
- 500 http://fr.archive.ubuntu.com/ubuntu zesty/universe amd64 Packages
- 500 http://fr.archive.ubuntu.com/ubuntu zesty/universe i386 Packages
- 
- After installing package dnsmasq, connection sharing works again as
- expected.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: ubuntu-mate-core 1.190
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Apr 11 20:39:44 2017
  InstallationDate: Installed on 2017-04-05 (6 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Beta amd64 (20170321.1)
  SourcePackage: ubuntu-mate-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  [Zesty] missing dnsmasq-base package breaks NetworkManager connection
  sharing feature

Status in ubuntu-mate:
  New
Status in network-manager package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  Invalid

Bug description:
  Network settings in Zesty allow users to define a connection as
  "Shared to other computers", this does not currently work in Ubuntu
  MATE 17.04 Beta 2 at least for wired connections.

  The reason, from the logs is that dnsmasq binary is not present:

  [...]
  Apr 11 20:37:22 Edge NetworkManager[946]:   [1491935842.1052] 
Executing: /sbin/iptables --table nat --insert POSTROUTING --source 
10.42.0.0/255.255.255.0 ! --destination 10.42.0.0/255.255.255.0 --jump 
MASQUERADE
  Apr 11 20:37:22 Edge NetworkManager[946]:  [1491935842.1117] device 
(enp1s0f2): share: (enp1s0f2) failed to start dnsmasq: Could not find "dnsmasq" 
binary
  Apr 11 20:37:22 Edge NetworkManager[946]:   [1491935842.1119] 
Executing: /sbin/iptables --table nat --delete POSTROUTING --source 
10.42.0.0/255.
  [...]

  The way to setup a (wired) connection sharing is as follow:

  - Go to Network Connection settings and select the wired connection
  - Under [IPv4 Settings -> Method] select "Shared to other computers"

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: ubuntu-mate-core 1.190
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Apr 11 20:39:44 2017
  InstallationDate: Installed on 2017-04-05 (6 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Beta amd64 (20170321.1)
  SourcePackage: ubuntu-mate-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1682104] [NEW] sudo rules based on group membership from freeipa does not work

[Oscar Carlberg]

Public bug reported:

When upgrading sudo package in xenial from version 1.8.16-0ubuntu1 to
1.8.16-0ubuntu1.3, our FreeIPA-based sudo rules suddenly stopped
working. We have setup a group in FreeIPA called ldap_nopass, and
configured hbac rules to allow users in this group to run sudo (without
password / nopasswd). This have been working fine up until now when we
upgraded the sudo package. Downgrading to 1.8.16-0ubuntu1 resolves the
issue. It also work with 1.8.16-0ubuntu1.3 if we set
use_fully_qualified_names = False in /etc/sssd/sssd.conf, but this is
not an option for us.

This led me to believe this issue is related to upstream bug: 
https://bugzilla.sudo.ws/show_bug.cgi?id=757

And most likely is caused by the patchset from 1.3
https://launchpad.net/ubuntu/+source/sudo/1.8.16-0ubuntu1.3

Unfortunately, 1.8.16-0ubuntu1.2 binaries seems to be deleted from
mirrors, so I cannot try this version.

I've included the auth.log file showing the difference using sudo
1.8.16-0ubuntu1 vs 1.8.16-0ubuntu1.3. Real username and domain has been
redacted to user.name and example.com

Please let me know if any additional information is required.

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

** Attachment added: "auth.log"
   https://bugs.launchpad.net/bugs/1682104/+attachment/4860638/+files/auth.log

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

Title:
  sudo rules based on group membership from freeipa does not work

Status in sudo package in Ubuntu:
  New

Bug description:
  When upgrading sudo package in xenial from version 1.8.16-0ubuntu1 to
  1.8.16-0ubuntu1.3, our FreeIPA-based sudo rules suddenly stopped
  working. We have setup a group in FreeIPA called ldap_nopass, and
  configured hbac rules to allow users in this group to run sudo
  (without password / nopasswd). This have been working fine up until
  now when we upgraded the sudo package. Downgrading to 1.8.16-0ubuntu1
  resolves the issue. It also work with 1.8.16-0ubuntu1.3 if we set
  use_fully_qualified_names = False in /etc/sssd/sssd.conf, but this is
  not an option for us.

  This led me to believe this issue is related to upstream bug: 
  https://bugzilla.sudo.ws/show_bug.cgi?id=757

  And most likely is caused by the patchset from 1.3
  https://launchpad.net/ubuntu/+source/sudo/1.8.16-0ubuntu1.3

  Unfortunately, 1.8.16-0ubuntu1.2 binaries seems to be deleted from
  mirrors, so I cannot try this version.

  I've included the auth.log file showing the difference using sudo
  1.8.16-0ubuntu1 vs 1.8.16-0ubuntu1.3. Real username and domain has
  been redacted to user.name and example.com

  Please let me know if any additional information is required.

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

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

[Touch-packages] [Bug 1639776] Re: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface

[Launchpad Bug Tracker]

This bug was fixed in the package dnsmasq - 2.76-4ubuntu0.1

---
dnsmasq (2.76-4ubuntu0.1) yakkety; urgency=medium

  * Add two upstream patches to fix binding to an interface being
destroyed and recreated. LP: #1639776.
  + 2675f2061525bc954be14988d64384b74aa7bf8b
  + 16800ea072dd0cdf14d951c4bb8d2808b3dfe53d

 -- Nishanth Aravamudan   Tue, 28 Mar
2017 10:36:48 -0700

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

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

Title:
  name resolution (dnsmasq) fails to send queries out after
  suspend/resume reconnects the interface

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in dnsmasq source package in Xenial:
  Fix Released
Status in network-manager source package in Xenial:
  Invalid
Status in dnsmasq source package in Yakkety:
  Fix Released
Status in network-manager source package in Yakkety:
  Invalid
Status in dnsmasq package in Debian:
  Fix Released

Bug description:
  [Impact]

   * suspend/resume (which involves disconnection of network devices)
  leads to dnsmasq failures.

  [Test Case]

   * suspend/resume on 16.04 or 16.10 when using dnsmasq, and see
  failures upon resume.

  [Regression Potential]

   * The fix was NMU'd in Debian in the version immediately after
  16.10's. I believe the regression potential is very low as this is a
  clear bug-fix from upstream.

  ---

  Failure is caused by ENODEV return for all dns queries like:
  sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 
0, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)

  Problem is reported and fixed:
  https://bugzilla.redhat.com/show_bug.cgi?id=1367772

  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b

  I didn't yet test if applying that patch to ubuntu package works. I
  will try the patch in a few hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dnsmasq-base 2.76-4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  7 14:11:51 2016
  InstallationDate: Installed on 2037-12-25 (-7718 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)

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

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

[Touch-packages] [Bug 1639776] Update Released

[Robie Basak]

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

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

Title:
  name resolution (dnsmasq) fails to send queries out after
  suspend/resume reconnects the interface

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in dnsmasq source package in Xenial:
  Fix Released
Status in network-manager source package in Xenial:
  Invalid
Status in dnsmasq source package in Yakkety:
  Fix Released
Status in network-manager source package in Yakkety:
  Invalid
Status in dnsmasq package in Debian:
  Fix Released

Bug description:
  [Impact]

   * suspend/resume (which involves disconnection of network devices)
  leads to dnsmasq failures.

  [Test Case]

   * suspend/resume on 16.04 or 16.10 when using dnsmasq, and see
  failures upon resume.

  [Regression Potential]

   * The fix was NMU'd in Debian in the version immediately after
  16.10's. I believe the regression potential is very low as this is a
  clear bug-fix from upstream.

  ---

  Failure is caused by ENODEV return for all dns queries like:
  sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 
0, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)

  Problem is reported and fixed:
  https://bugzilla.redhat.com/show_bug.cgi?id=1367772

  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b

  I didn't yet test if applying that patch to ubuntu package works. I
  will try the patch in a few hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dnsmasq-base 2.76-4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  7 14:11:51 2016
  InstallationDate: Installed on 2037-12-25 (-7718 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)

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

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

[Touch-packages] [Bug 1681912] Re: [Zesty] missing dnsmasq-base package breaks NetworkManager connection sharing feature

[Etienne Papegnies]

** Description changed:

  Network settings in Zesty allow users to define a connection as "Shared
  to other computers", this does not currently work in Ubuntu MATE 17.04
  Beta 2 at least for wired connections.
  
  The reason, from the logs is that dnsmasq binary, from dnsmasq package
  is not present:
  
  [...]
  Apr 11 20:37:22 Edge NetworkManager[946]:   [1491935842.1052] 
Executing: /sbin/iptables --table nat --insert POSTROUTING --source 
10.42.0.0/255.255.255.0 ! --destination 10.42.0.0/255.255.255.0 --jump 
MASQUERADE
  Apr 11 20:37:22 Edge NetworkManager[946]:  [1491935842.1117] device 
(enp1s0f2): share: (enp1s0f2) failed to start dnsmasq: Could not find "dnsmasq" 
binary
  Apr 11 20:37:22 Edge NetworkManager[946]:   [1491935842.1119] 
Executing: /sbin/iptables --table nat --delete POSTROUTING --source 
10.42.0.0/255.
  [...]
+ 
+ The way to setup a (wired) connection sharing is as follow:
+ 
+ - Go to Network Connection settings and select the wired connection
+ - Under [IPv4 Settings -> Method] select "Shared to other computers"
+ 
  
  ouroumov@Edge:~$ apt-cache policy dnsmasq
  dnsmasq:
    Installed: (none)
    Candidate: 2.76-5
    Version table:
   2.76-5 500
  500 http://fr.archive.ubuntu.com/ubuntu zesty/universe amd64 Packages
  500 http://fr.archive.ubuntu.com/ubuntu zesty/universe i386 Packages
  
  After installing package dnsmasq, connection sharing works again as
  expected.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: ubuntu-mate-core 1.190
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Apr 11 20:39:44 2017
  InstallationDate: Installed on 2017-04-05 (6 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Beta amd64 (20170321.1)
  SourcePackage: ubuntu-mate-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  [Zesty] missing dnsmasq-base package breaks NetworkManager connection
  sharing feature

Status in ubuntu-mate:
  New
Status in network-manager package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  Invalid

Bug description:
  Network settings in Zesty allow users to define a connection as
  "Shared to other computers", this does not currently work in Ubuntu
  MATE 17.04 Beta 2 at least for wired connections.

  The reason, from the logs is that dnsmasq binary is not present:

  [...]
  Apr 11 20:37:22 Edge NetworkManager[946]:   [1491935842.1052] 
Executing: /sbin/iptables --table nat --insert POSTROUTING --source 
10.42.0.0/255.255.255.0 ! --destination 10.42.0.0/255.255.255.0 --jump 
MASQUERADE
  Apr 11 20:37:22 Edge NetworkManager[946]:  [1491935842.1117] device 
(enp1s0f2): share: (enp1s0f2) failed to start dnsmasq: Could not find "dnsmasq" 
binary
  Apr 11 20:37:22 Edge NetworkManager[946]:   [1491935842.1119] 
Executing: /sbin/iptables --table nat --delete POSTROUTING --source 
10.42.0.0/255.
  [...]

  The way to setup a (wired) connection sharing is as follow:

  - Go to Network Connection settings and select the wired connection
  - Under [IPv4 Settings -> Method] select "Shared to other computers"

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: ubuntu-mate-core 1.190
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Apr 11 20:39:44 2017
  InstallationDate: Installed on 2017-04-05 (6 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Beta amd64 (20170321.1)
  SourcePackage: ubuntu-mate-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1682102] [NEW] libseccomp should support GA and HWE kernels

[Dimitri John Ledkov]

Public bug reported:

Currently libseccomp version in Ubuntu are:

 libseccomp | 2.2.3-3ubuntu3   | xenial | source
 libseccomp | 2.3.1-2ubuntu2   | yakkety| source
 libseccomp | 2.3.1-2.1ubuntu1 | zesty  | source

The difference between 2.2.3 and 2.3.1 is 63 upstream commits.

Of those commits, 7 are already cherrypicked into xenial for s390x
support.

However that s390x support is incomplete as multiplexed syscalls are not
supported.

A request has been filed to support multiplexed syscalls in libseccomp
in xenial at
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1679691

That is a request for further 18 commits to backport, bringing the total
to 25.

Looking at the remaining 38 commits there are:
- documentation updates
- tools updates
- tests updates
- bugfixes
- updates to syscall tables for linux 4.3, 4.5-rc4+

IMHO, in the future when libseccomp is updated to support 4.10 kernel
syscalls, it should be backported back to xenial too, to properly suppor
the HWE kernels.

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

** Affects: libseccomp (Ubuntu Xenial)
 Importance: High
 Assignee: Dimitri John Ledkov (xnox)
 Status: Confirmed

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

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

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

** Changed in: libseccomp (Ubuntu Xenial)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

Title:
  libseccomp should support GA and HWE kernels

Status in libseccomp package in Ubuntu:
  New
Status in libseccomp source package in Xenial:
  Confirmed

Bug description:
  Currently libseccomp version in Ubuntu are:

   libseccomp | 2.2.3-3ubuntu3   | xenial | 
source
   libseccomp | 2.3.1-2ubuntu2   | yakkety| 
source
   libseccomp | 2.3.1-2.1ubuntu1 | zesty  | 
source

  The difference between 2.2.3 and 2.3.1 is 63 upstream commits.

  Of those commits, 7 are already cherrypicked into xenial for s390x
  support.

  However that s390x support is incomplete as multiplexed syscalls are
  not supported.

  A request has been filed to support multiplexed syscalls in libseccomp
  in xenial at
  https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1679691

  That is a request for further 18 commits to backport, bringing the
  total to 25.

  Looking at the remaining 38 commits there are:
  - documentation updates
  - tools updates
  - tests updates
  - bugfixes
  - updates to syscall tables for linux 4.3, 4.5-rc4+

  IMHO, in the future when libseccomp is updated to support 4.10 kernel
  syscalls, it should be backported back to xenial too, to properly
  suppor the HWE kernels.

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

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

[Touch-packages] [Bug 1679691] Re: libseccomp fix - s390: handle multiplexed syscalls correctly

[Dimitri John Ledkov]

0001-s390-handle-multiplexed-syscalls-correctly.patch
47516603828396f85107ea3e2a254958c2bc3ff5
-> this one is actually 66282c31034e2bb442bd9dc862d6d814f0df2f98 upstream

0001-arch-fix-the-multiplexed-ipc-syscalls.patch
3a89bd144885f54aff86f2e275859a1483992edd
-> this one is actually a58deebd1ee7bedc47bb966ebeec699421e40c65 upstream

Given the size of the backport, I will look into backporting libseccomp
2.3.1 as a whole. Let me investigate if that will be feasable or not.

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

Title:
  libseccomp fix - s390: handle multiplexed syscalls correctly

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in libseccomp package in Ubuntu:
  Confirmed
Status in libseccomp source package in Xenial:
  New
Status in libseccomp source package in Yakkety:
  New
Status in libseccomp source package in Zesty:
  Confirmed
Status in libseccomp source package in aa-series:
  New

Bug description:
  Within Xenial version 2.2.3 of seccomp is included.
  With Yaketty version 2.3.1 is available and fixed this problem.

  Even Docker is working on a SNAP solution, please provide the fix to
  16.04.

  
  With following patches this can be applied to 2.2.3 in support of the 16.04 
LTS Release
  16.04

  Here the upstream git commits for the patches:

  0001-arch-fix-a-problem-with-the-rule-rewrites-in-_seccom.patch
  1d63fad4a064b80e0b921b16ed419f3342337ed4
   
  0001-all-block-negative-syscall-numbers-from-the-filter.patch
  51c46f80c1edee863bbc4eb21b03decc44e69a45 

  0001-api-limit-errno-values-to-MAX_ERRNO.patch
  0d287caf43792239b107ee3215b32b8bc901f9c3 

  0001-db-fix-a-minor-style-problem.patch
  61c28579a984a6c4bd87ec585dc6d5cd4cc0e702 

  0001-db-make-the-individual-db-filter-ops-private.patch
  a4478ddcd4e3b34fcd9c526dcf54f0d79b33ac16

  0001-db-store-the-rules-used-to-build-the-filter.patch
  f16f405f61ecdbad202257b61004b85fce64d75c 

  0001-arch-make-use-of-function-tables-instead-of-switch-s.patch
  57df79c166b26d5044e7e27099e6e69671e727dd 

  0001-db-introduce-transaction-support.patch
  9be1538a4ac0e45047a3f1b79691505c3d11ca31 

  0001-arch-move-the-low-level-filter-rule-addition-code-in.patch
  996e445a74823c735757413fda809e1ed0afc7d4 

  0001-arch-enable-more-involved-arch-ABI-specific-rule-cre.patch
  5b42b8cfa25506fa260c8f46b4a063b5cfd09d1c 

  0001-arch-basic-support-for-multiplexed-and-direct-socket.patch
  d32c3bfa4b07add90dcd04292eb4ba278dd103ba 

  0001-arch-generate-both-multiplexed-and-direct-socket-sys.patch
  983835f3e0fd000a42c8beaea9d7fbe72665 

  0001-tests-add-a-test-for-the-different-types-of-socket-s.patch
  099f4214ce4fe5f53cf0f59e96b71bf4d54a8cd6 

  0001-api-add-a-seccomp_version-API-call.patch
  58a7c20d4c2defc1c984c5c7391ecc60093f85fa 

  0001-tests-create-a-simple-live-test-to-verify-we-can-set.patch
  8ed78c3859f476d302995b43d6739f3341f5b37d 

  0001-s390-handle-multiplexed-syscalls-correctly.patch
  47516603828396f85107ea3e2a254958c2bc3ff5 

  0001-arch-fix-the-multiplexed-ipc-syscalls.patch
  3a89bd144885f54aff86f2e275859a1483992edd

  With the following additional commit all tests pass with "make check"

  0001-tests-remove-fuzzing-from-28-sim-arch_x86.tests.patch
  0d8504bc192e0989494df06efc4b186a9f02e20a

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

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

[Touch-packages] [Bug 1679674] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From mihaj...@de.ibm.com 2017-04-12 07:24 EDT---
I believe it would be good to persist the old eth names on systemd upgrades, 
e.g. when going from 16.10 (or lower) to 17.04 (or higher) and only use the new 
naming scheme for clean installs. The reason is that these names may still be 
referenced somewhere else (e.g. in libvirt guest definitions), which could 
cause trouble.

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

Title:
  s390x: Interface order in kvm guest image not predictable

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  ---Problem Description---
  Running the Ubuntu16 cloud image on an ubuntu 16.04 KVM host. The KVM guest 
is launched with 2 network interfaces connected to 2 different open vswitch 
bridges.

  The problem is 2-fold:
  #1 In the guest it seems like that the interface order is not predicitve. 
Device names used are eth0, eth1. The device that is listed first in libvirts 
domain.xml is not necessarily eth0. 
  #2 The device names are not persistet. On the next boot eth0 might be eth1 
and vice verca.
   
  Contact Information = andreas.scheur...@de.ibm.com 
   
  ---uname output---
  Linux Ubuntu16 4.4.0-70-generic #91-Ubuntu SMP Wed Mar 22 12:48:02 UTC 2017 
s390x s390x s390x GNU/Linux
   
  Machine Type = KVM guest 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   guest Domain xml:
  
Ubuntu16VM
455e6998-cec1-4010-99a6-d033ee6d3385
524288
524288
2

  /machine


  hvm
  


destroy
restart
preserve

  /usr/bin/qemu-system-s390x
  






  
  







  
  


  
  



  





  
  



  





  
  



  
  


  


  libvirt-455e6998-cec1-4010-99a6-d033ee6d3385
  libvirt-455e6998-cec1-4010-99a6-d033ee6d3385

  

  
  in the guest check interfaces and remember the mac address
  # ip a
  Do a reboot (or multiple) and check again if the interface-mac combination is 
still the same

  The interface order should change from time to time
   
  Userspace tool common name: udev? 

  Userspace rpm: ? 
   
  The userspace tool has the following bit modes: 64 

  Userspace tool obtained from project website:  na

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

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

[Touch-packages] [Bug 1647771] Re: Undefined variable in vim netrw when netrw_browse_split = 3

[Launchpad Bug Tracker]

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

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

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

Title:
  Undefined variable in vim netrw when netrw_browse_split = 3

Status in vim package in Ubuntu:
  Confirmed

Bug description:
  To reproduce, open the netrw explorer in a new tab, and set opened
  files to go to a new tab:

  :let g:netrw_browse_split = 3
  :Texplore

  When the user selects a file from the explorer with Enter, this error
  appears:

  Error detected while processing function 20_NetrwBrowseChgDir:
  line  135:
  E121: Undefined variable: b:netrw_curdir

  And this is displayed for a second:

  Invalid arguments for function SetRexDir

  Saw this after upgrade to Ubuntu 16.04 (vim 7.4.1689-3ubuntu1.2). The
  error didn't show with vim 7.4.052-1ubuntu3.1 on Ubuntu-14.04.

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

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

[Touch-packages] [Bug 1571099] Re: [bq E5] [OTA10.1] Catalan layout differs from shift to normal

[Launchpad Bug Tracker]

** Branch linked: lp:~michael-sheldon/ubuntu-keyboard/fix-1571099

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

Title:
  [bq E5] [OTA10.1] Catalan layout differs from shift to normal

Status in ubuntu-keyboard package in Ubuntu:
  In Progress

Bug description:
  Holding dot key shows different options depending if shift key is on
  or off (write layout should be the one that appears with caps off)

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

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

[Touch-packages] [Bug 1682092] [NEW] Enabled plugins still display in the keyboard menu after having been uninstalled

[Michael Sheldon]

Public bug reported:

Steps to reproduce

1) Install ubuntu-keyboard-swedish

2) Add Swedish to the enable keyboards via system settings

3) Uninstall ubuntu-keyboard-swedish

4) Open the keyboard language menu

Expected result

Swedish shouldn't be displayed

Actual result

"Sv" (Language code for Swedish) is displayed

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

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

Title:
  Enabled plugins still display in the keyboard menu after having been
  uninstalled

Status in ubuntu-keyboard package in Ubuntu:
  New

Bug description:
  Steps to reproduce

  1) Install ubuntu-keyboard-swedish

  2) Add Swedish to the enable keyboards via system settings

  3) Uninstall ubuntu-keyboard-swedish

  4) Open the keyboard language menu

  Expected result

  Swedish shouldn't be displayed

  Actual result

  "Sv" (Language code for Swedish) is displayed

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

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

[Touch-packages] [Bug 1587749] Re: random 1-2s black screen

[Maarten Fonville]

I have the same issue on Ubuntu 16.10 and 17.04, also with Intel
hardware and displayport. Nothing weird in dmesg though :-/

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

Title:
  random 1-2s black screen

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I have a Lenovo T450s with docking station and 2 display port monitors
  on it.

  I experience black screens for about a second. Usually one of the
  external monitors only. One external display turns black and comes
  back after 1 or 2 seconds. This happens >10 times a day and is really
  annoying.

  My colleague experiencing the same issue, also using Ubuntu 16.04.
  Same hardware.

  At home I have a similar issue, also with Intel motherboard graphics.
  Different hardware.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  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: Wed Jun  1 09:14:00 2016
  DistUpgraded: 2016-04-25 11:02:09,877 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.18, 4.4.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:5036]
  InstallationDate: Installed on 2015-11-06 (207 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20BWS2YL00
  ProcEnviron:
   LANGUAGE=de_DE
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-25 (36 days ago)
  dmi.bios.date: 07/08/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET51WW (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS2YL00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET51WW(1.16):bd07/08/2015:svnLENOVO:pn20BWS2YL00:pvrThinkPadT450s:rvnLENOVO:rn20BWS2YL00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BWS2YL00
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.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
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Jun  1 07:58:12 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4925 
   vendor AUO
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Touch-packages] [Bug 1681912] Re: [Zesty] missing dnsmasq-base package breaks NetworkManager connection sharing feature

[Martin Wimpress]

** Summary changed:

- [Zesty] missing dnsmasq package breaks NetworkManager connection sharing 
feature
+ [Zesty] missing dnsmasq-base package breaks NetworkManager connection sharing 
feature

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

Title:
  [Zesty] missing dnsmasq-base package breaks NetworkManager connection
  sharing feature

Status in ubuntu-mate:
  New
Status in network-manager package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  Invalid

Bug description:
  Network settings in Zesty allow users to define a connection as
  "Shared to other computers", this does not currently work in Ubuntu
  MATE 17.04 Beta 2 at least for wired connections.

  The reason, from the logs is that dnsmasq binary, from dnsmasq package
  is not present:

  [...]
  Apr 11 20:37:22 Edge NetworkManager[946]:   [1491935842.1052] 
Executing: /sbin/iptables --table nat --insert POSTROUTING --source 
10.42.0.0/255.255.255.0 ! --destination 10.42.0.0/255.255.255.0 --jump 
MASQUERADE
  Apr 11 20:37:22 Edge NetworkManager[946]:  [1491935842.1117] device 
(enp1s0f2): share: (enp1s0f2) failed to start dnsmasq: Could not find "dnsmasq" 
binary
  Apr 11 20:37:22 Edge NetworkManager[946]:   [1491935842.1119] 
Executing: /sbin/iptables --table nat --delete POSTROUTING --source 
10.42.0.0/255.
  [...]

  ouroumov@Edge:~$ apt-cache policy dnsmasq
  dnsmasq:
    Installed: (none)
    Candidate: 2.76-5
    Version table:
   2.76-5 500
  500 http://fr.archive.ubuntu.com/ubuntu zesty/universe amd64 Packages
  500 http://fr.archive.ubuntu.com/ubuntu zesty/universe i386 Packages

  After installing package dnsmasq, connection sharing works again as
  expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: ubuntu-mate-core 1.190
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Apr 11 20:39:44 2017
  InstallationDate: Installed on 2017-04-05 (6 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Beta amd64 (20170321.1)
  SourcePackage: ubuntu-mate-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1682076] [NEW] package lightdm 1.18.3-0ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Shubham Negi]

Public bug reported:

Sometimes system is becoming less responsive and I've to wait for it for
minutes ,very long sometimes.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: lightdm 1.18.3-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-46-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Sun Apr  9 22:09:26 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2017-03-18 (25 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: lightdm
Title: package lightdm 1.18.3-0ubuntu1.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package lightdm 1.18.3-0ubuntu1.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in lightdm package in Ubuntu:
  New

Bug description:
  Sometimes system is becoming less responsive and I've to wait for it
  for minutes ,very long sometimes.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Sun Apr  9 22:09:26 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-03-18 (25 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: lightdm
  Title: package lightdm 1.18.3-0ubuntu1.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1682076] Re: package lightdm 1.18.3-0ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package lightdm 1.18.3-0ubuntu1.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in lightdm package in Ubuntu:
  New

Bug description:
  Sometimes system is becoming less responsive and I've to wait for it
  for minutes ,very long sometimes.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Sun Apr  9 22:09:26 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-03-18 (25 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: lightdm
  Title: package lightdm 1.18.3-0ubuntu1.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1674164] Re: DVDs with restricted permissions are unreadable for normal user (regression?)

[mikbini]

In my view this is not invalid: "differently correct" recorders and also
printed DVDs are common in the wild and they work on Windows, osX and
"dumb" readers. And as the average user is not able to figure out a
workaround, he will assume that ubuntu is broken and switch to something
else.

The same argument ("we are applying the permissions") was made in 2009
for bug #10550 and ubuntu decision back then was to change the mount
options (possibly only to CDs/DVDs/Blueray, this is not clear from the
bug).

And let me stress again that this is indeed a regression: people used to
be able to play their braindead DVDs and now they cannot.

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

Title:
  DVDs with restricted permissions are unreadable for normal user
  (regression?)

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  I'm using 16.10. I have a DVD with strange permissions for the root
  folder:

  michele@cassandra:~$ ls -l /media/michele
  total 2
  d--x--x--- 3 michele michele 88 gen  1  2004 SONY_DVD_RECORDER_VOLUME

  The DVD is readable e.g. on windows but with ubuntu while I can access
  it as root:

  root@cassandra:~# ls -l /media/michele/SONY_DVD_RECORDER_VOLUME/
  total 4
  dr-xr-xr-x 2 michele michele 3628 gen  1  2004 VIDEO_TS

  I cannot as the non-root user that is logged in when I insert the
  disk:

  michele@cassandra:~$ ls -l /media/michele/SONY_DVD_RECORDER_VOLUME
  ls: cannot open directory '/media/michele/SONY_DVD_RECORDER_VOLUME': 
Permission denied

  Looking at the mount options it seems to me that this is a regression
  for bug #10550. The options used by udisks2 are:

  root@cassandra:~# mount |grep SONY
  /dev/sr0 on /media/michele/SONY_DVD_RECORDER_VOLUME type udf 
(ro,nosuid,nodev,relatime,uid=1000,gid=1000,iocharset=utf8,uhelper=udisks2)

  while my understanding from bug #10550 is that I should have also
  mode=0777 and dmode=0777

  And indeed this works:

  root@cassandra:~# mount -t udf -o
  
ro,nosuid,nodev,relatime,uid=1000,gid=1000,iocharset=utf8,uhelper=udisks2,mode=0777,dmode=0777
  /dev/sr0 ~michele/z

  michele@cassandra:~$ ls -l ~michele/z
  total 4
  drwxrwxrwx 2 michele michele 3628 gen  1  2004 VIDEO_TS

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

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

[Touch-packages] [Bug 1642767] Re: starting any container with umask 007 breaks host system shutdown. lxc-stop just hangs.

[Pierre-Louis Bonicoli]

My previous comment is unclear, the two problems are:

1. 'lxc' directories below '/sys/fs/cgroup/' are created according to
the umask setting

2.  then mounting '/sys/fs/cgroup/systemd' in the container hangs (and
attempts to reboot or shut down the host system fail, a hard reset is
required).

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

Title:
  starting any container with umask 007 breaks host system shutdown.
  lxc-stop just hangs.

Status in lxc package in Ubuntu:
  New

Bug description:
  If I have umask 007 (or any other value that masks the world-execute
  bit) when I run lxc-start for the first time after logging in, my host
  system enters a state with the following problems:

  * lxc-stop hangs forever instead of stopping any container, even one that 
wasn't started with umask 007.
  * lxc-stop --kill --nolock hangs in the same way.
  * Attempts to reboot or shut down the host system fail, requiring a hard 
reset to recover.

  When lxc-stop hangs, messages like these appear in syslog every couple
  of minutes:

  Nov 17 01:22:11 hostbox kernel: [ 3360.091624] INFO: task systemd:12179 
blocked for more than 120 seconds.
  Nov 17 01:22:11 hostbox kernel: [ 3360.091629]   Tainted: P   OE  
 4.4.0-47-generic #68-Ubuntu
  Nov 17 01:22:11 hostbox kernel: [ 3360.091631] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  Nov 17 01:22:11 hostbox kernel: [ 3360.091633] systemd D 
8800c6febb58 0 12179  12168 0x0104
  Nov 17 01:22:11 hostbox kernel: [ 3360.091638]  8800c6febb58 
8800d318d280 88040c649b80 8800d318d280
  Nov 17 01:22:11 hostbox kernel: [ 3360.091641]  8800c6fec000 
8800345bc088 8800345bc070 
  Nov 17 01:22:11 hostbox kernel: [ 3360.091644]  fffe0001 
8800c6febb70 81830f15 8800d318d280
  Nov 17 01:22:11 hostbox kernel: [ 3360.091647] Call Trace:
  Nov 17 01:22:11 hostbox kernel: [ 3360.091653]  [] 
schedule+0x35/0x80
  Nov 17 01:22:11 hostbox kernel: [ 3360.091657]  [] 
rwsem_down_write_failed+0x202/0x350
  Nov 17 01:22:11 hostbox kernel: [ 3360.091662]  [] ? 
kernfs_sop_show_options+0x40/0x40
  Nov 17 01:22:11 hostbox kernel: [ 3360.091666]  [] 
call_rwsem_down_write_failed+0x13/0x20
  Nov 17 01:22:11 hostbox kernel: [ 3360.091669]  [] ? 
down_write+0x2d/0x40
  Nov 17 01:22:11 hostbox kernel: [ 3360.091672]  [] 
grab_super+0x30/0xa0
  Nov 17 01:22:11 hostbox kernel: [ 3360.091674]  [] 
sget_userns+0x152/0x450
  Nov 17 01:22:11 hostbox kernel: [ 3360.091677]  [] ? 
kernfs_sop_show_path+0x50/0x50
  Nov 17 01:22:11 hostbox kernel: [ 3360.091680]  [] 
kernfs_mount_ns+0x7e/0x230
  Nov 17 01:22:11 hostbox kernel: [ 3360.091685]  [] 
cgroup_mount+0x2eb/0x7f0
  Nov 17 01:22:11 hostbox kernel: [ 3360.091687]  [] 
mount_fs+0x38/0x160
  Nov 17 01:22:11 hostbox kernel: [ 3360.091691]  [] 
vfs_kern_mount+0x67/0x110
  Nov 17 01:22:11 hostbox kernel: [ 3360.091694]  [] 
do_mount+0x269/0xde0
  Nov 17 01:22:11 hostbox kernel: [ 3360.091698]  [] 
SyS_mount+0x9f/0x100
  Nov 17 01:22:11 hostbox kernel: [ 3360.091701] [] 
entry_SYSCALL_64_fastpath+0x16/0x71

  When system shutdown hangs, similar messages appear on the console
  every couple of minutes.

  I can reproduce this at will with a freshly-installed and fully-
  updated host OS in VirtualBox, and with either an old-ish container or
  a new one.

  I'm running lxc 2.0.5-0ubuntu1~ubuntu16.04.2 on xubuntu 16.04.1 LTS
  amd64.

  My containers are all unprivileged.

  My umask at container creation time does not seem to matter.  As far
  as I have seen, my umask only matters the first time I start a
  container in my login session.

  I can work around the bug by manually setting my umask to something
  more permissive before I start my first container of the day, and then
  setting it back again, but that's rather a hassle.  (Even worse, it's
  very easy to forget this workaround and be left with containers that
  can't be stopped and a host system that won't shut down cleanly.)

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

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

[Touch-packages] [Bug 1682055] [NEW] dh_apparmor does not remove profiles(s) when purging package

[Steve Beattie]

Public bug reported:

dh_apparmor adds an entry to remove apparmor profiles added by a package
when purging that package. However, it leaves the profiles loaded in the
kernel; it should unload them from the kernel before removing them from
the disk.

Secondly, dh_apparmor could make life easier for maintainers when
upgrading packages and the profile changes the name of profiles, child
profiles, or hats contained within a profile file. Without this, the
update can leave behind profiles etc. loaded into the kernel post a
package update. This would ideally need to be triggered only when the
upgrading package is older than a given version.

** Affects: apparmor (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/1682055

Title:
  dh_apparmor does not remove profiles(s) when purging package

Status in apparmor package in Ubuntu:
  New

Bug description:
  dh_apparmor adds an entry to remove apparmor profiles added by a
  package when purging that package. However, it leaves the profiles
  loaded in the kernel; it should unload them from the kernel before
  removing them from the disk.

  Secondly, dh_apparmor could make life easier for maintainers when
  upgrading packages and the profile changes the name of profiles, child
  profiles, or hats contained within a profile file. Without this, the
  update can leave behind profiles etc. loaded into the kernel post a
  package update. This would ideally need to be triggered only when the
  upgrading package is older than a given version.

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

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

[Touch-packages] [Bug 1506427] Re: Using calendar with keys might cause Indicator-datetime to crash unity-panel-service

[Adam Conrad]

** Also affects: ido (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

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

Title:
  Using calendar with keys might cause Indicator-datetime to crash
  unity-panel-service

Status in ido package in Ubuntu:
  Fix Released
Status in ido source package in Trusty:
  Fix Committed
Status in ido source package in Xenial:
  Fix Released
Status in ido source package in Yakkety:
  Fix Released

Bug description:
  [Impact] 
  Unity panel service crashes (removing indicators from panel) when calendar 
menu is opened and there are some key presses.

  [Test Case]
  This is a quite random bug that is not easy to reproduce, it happens 
sometimes that you open the indicator-datetime and after a keypress the panel 
crashes.

  [Regression Potential]
  Nothing expected, but calendar item in datetime might behave differently on 
key-presses.
  Although the fix is quite safe since we're just ensuring that we disconnect 
from parent widget signals on menuitem destruction.

  ===

  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity.  This problem was most recently seen with version
  7.3.2+15.10.20151002.2-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/74901303bee889a2ca807616ea267069ad252435
  contains more details.

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

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

[Touch-packages] [Bug 1506427] Re: Using calendar with keys might cause Indicator-datetime to crash unity-panel-service

[Robie Basak]

It looks like 13.10.0+14.04.20170403-0ubuntu1 still needs verifying from
trusty-proposed.

09:41  [SRU] could someone glance at bug 1506427 please? I'm not
sure how it ended up in trusty-proposed. I see no message about it (plus
it doesn't appear to have been verified in trusty, but that's a separate
matter)

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

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

Title:
  Using calendar with keys might cause Indicator-datetime to crash
  unity-panel-service

Status in ido package in Ubuntu:
  Fix Released
Status in ido source package in Xenial:
  Fix Released
Status in ido source package in Yakkety:
  Fix Released

Bug description:
  [Impact] 
  Unity panel service crashes (removing indicators from panel) when calendar 
menu is opened and there are some key presses.

  [Test Case]
  This is a quite random bug that is not easy to reproduce, it happens 
sometimes that you open the indicator-datetime and after a keypress the panel 
crashes.

  [Regression Potential]
  Nothing expected, but calendar item in datetime might behave differently on 
key-presses.
  Although the fix is quite safe since we're just ensuring that we disconnect 
from parent widget signals on menuitem destruction.

  ===

  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity.  This problem was most recently seen with version
  7.3.2+15.10.20151002.2-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/74901303bee889a2ca807616ea267069ad252435
  contains more details.

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

-- 
Mailing list: https://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 1679674] Re: s390x: Interface order in kvm guest image not predictable

[Dimitri John Ledkov]

On 12 April 2017 at 07:58, Andreas Scheuring
 wrote:
> Thanks for this fix. It's solved in 17.04, but won't be backported to
> 16.04. Is that right?

Correct, no backport to 16.04 as is as of now. This is a backwards
incompatible change which can break existing VMs networking, as
interfaces cannot have multiple names (unlike e.g. hard drives which
can have backwards compatible symlinks).

I'm not even sure yet, if I should be writing more code to e.g.
automatically transform /etc/networking/interfaces with new interface
names.

-- 
Regards,

Dimitri.

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

Title:
  s390x: Interface order in kvm guest image not predictable

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  ---Problem Description---
  Running the Ubuntu16 cloud image on an ubuntu 16.04 KVM host. The KVM guest 
is launched with 2 network interfaces connected to 2 different open vswitch 
bridges.

  The problem is 2-fold:
  #1 In the guest it seems like that the interface order is not predicitve. 
Device names used are eth0, eth1. The device that is listed first in libvirts 
domain.xml is not necessarily eth0. 
  #2 The device names are not persistet. On the next boot eth0 might be eth1 
and vice verca.
   
  Contact Information = andreas.scheur...@de.ibm.com 
   
  ---uname output---
  Linux Ubuntu16 4.4.0-70-generic #91-Ubuntu SMP Wed Mar 22 12:48:02 UTC 2017 
s390x s390x s390x GNU/Linux
   
  Machine Type = KVM guest 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   guest Domain xml:
  
Ubuntu16VM
455e6998-cec1-4010-99a6-d033ee6d3385
524288
524288
2

  /machine


  hvm
  


destroy
restart
preserve

  /usr/bin/qemu-system-s390x
  






  
  







  
  


  
  



  





  
  



  





  
  



  
  


  


  libvirt-455e6998-cec1-4010-99a6-d033ee6d3385
  libvirt-455e6998-cec1-4010-99a6-d033ee6d3385

  

  
  in the guest check interfaces and remember the mac address
  # ip a
  Do a reboot (or multiple) and check again if the interface-mac combination is 
still the same

  The interface order should change from time to time
   
  Userspace tool common name: udev? 

  Userspace rpm: ? 
   
  The userspace tool has the following bit modes: 64 

  Userspace tool obtained from project website:  na

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

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

[Touch-packages] [Bug 1681870] Re: indicator-datetime-service crashed with SIGABRT in __malloc_assert()

[Łukasz Zemczak]

** Changed in: unity-scope-click (Ubuntu)
   Status: New => Won't Fix

** Description changed:

  Install I386 version of desktop or run live desktop and the indicator is
  crashed.
+ 
+ Added other packages that could have been affected as the crash is due
+ to some ABI break in ubuntu-app-launch.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  CurrentDesktop: Unity:Unity7
  Date: Tue Apr 11 15:41:03 2017
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ExecutableTimestamp: 1490207290
  InstallationDate: Installed on 2017-04-11 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170411)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcCwd: /home/davmor2
  ProcEnviron:
-  LANG=en_GB.UTF-8
-  LANGUAGE=en_GB:en
-  PATH=(custom, no user)
-  SHELL=/bin/bash
-  XDG_RUNTIME_DIR=
+  LANG=en_GB.UTF-8
+  LANGUAGE=en_GB:en
+  PATH=(custom, no user)
+  SHELL=/bin/bash
+  XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: indicator-datetime
  StacktraceTop:
-  __malloc_assert (assertion=assertion@entry=0xb6d27f38 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0xb6d24696 "malloc.c", line=line@entry=2403, 
function=) at malloc.c:301
-  sysmalloc (nb=nb@entry=264, av=av@entry=0xb6d7a780 ) at 
malloc.c:2400
-  _int_malloc (av=av@entry=0xb6d7a780 , bytes=bytes@entry=260) at 
malloc.c:3862
-  __GI___libc_malloc (bytes=260) at malloc.c:2925
-  operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6
+  __malloc_assert (assertion=assertion@entry=0xb6d27f38 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0xb6d24696 "malloc.c", line=line@entry=2403, 
function=) at malloc.c:301
+  sysmalloc (nb=nb@entry=264, av=av@entry=0xb6d7a780 ) at 
malloc.c:2400
+  _int_malloc (av=av@entry=0xb6d7a780 , bytes=bytes@entry=260) at 
malloc.c:3862
+  __GI___libc_malloc (bytes=260) at malloc.c:2925
+  operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6
  Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

Title:
  indicator-datetime-service crashed with SIGABRT in __malloc_assert()

Status in content-hub package in Ubuntu:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  Fix Released
Status in indicator-transfer package in Ubuntu:
  Fix Released
Status in keeper package in Ubuntu:
  Confirmed
Status in libertine-scope package in Ubuntu:
  Fix Released
Status in pay-service package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Fix Released
Status in ubuntu-app-launch package in Ubuntu:
  Fix Released
Status in ubuntu-push package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Fix Released
Status in unity-scope-click package in Ubuntu:
  Won't Fix
Status in unity8 package in Ubuntu:
  Fix Released
Status in url-dispatcher package in Ubuntu:
  Fix Released

Bug description:
  Install I386 version of desktop or run live desktop and the indicator
  is crashed.

  Added other packages that could have been affected as the crash is due
  to some ABI break in ubuntu-app-launch.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  CurrentDesktop: Unity:Unity7
  Date: Tue Apr 11 15:41:03 2017
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ExecutableTimestamp: 1490207290
  InstallationDate: Installed on 2017-04-11 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170411)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcCwd: /home/davmor2
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: indicator-datetime
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0xb6d27f38 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE 

[Touch-packages] [Bug 1682044] Re: mtp-server has memory leaks

[Ubuntu Foundations Team Bug Bot]

The attachment "0001-Fix-memory-leaks.patch" seems to be a patch.  If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues 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 mtp in Ubuntu.
https://bugs.launchpad.net/bugs/1682044

Title:
  mtp-server has memory leaks

Status in mtp package in Ubuntu:
  New

Bug description:
  Attached is the patch that fixes memory leaks in the mtp-server.
  This issue is original reported by Intel, and Intel also provides a patch.

  NOTE that the name “Ubuntu touch” has been changed to “Intel
  Devices”in the patch.

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

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

[Touch-packages] [Bug 1682044] [NEW] mtp-server has memory leaks

[Robert Liu]

Public bug reported:

Attached is the patch that fixes memory leaks in the mtp-server.
This issue is original reported by Intel, and Intel also provides a patch.

NOTE that the name “Ubuntu touch” has been changed to “Intel Devices”in
the patch.

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

** Patch added: "0001-Fix-memory-leaks.patch"
   
https://bugs.launchpad.net/bugs/1682044/+attachment/4860565/+files/0001-Fix-memory-leaks.patch

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

Title:
  mtp-server has memory leaks

Status in mtp package in Ubuntu:
  New

Bug description:
  Attached is the patch that fixes memory leaks in the mtp-server.
  This issue is original reported by Intel, and Intel also provides a patch.

  NOTE that the name “Ubuntu touch” has been changed to “Intel
  Devices”in the patch.

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

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

[Touch-packages] [Bug 1666515] Re: Enable tbb package on Ubuntu 16.04 LTS

[Frank Heimes]

** Changed in: ubuntu-z-systems
   Status: New => Incomplete

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

Title:
  Enable tbb package on Ubuntu 16.04 LTS

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in tbb package in Ubuntu:
  Fix Released
Status in tbb source package in Xenial:
  Incomplete
Status in tbb source package in Yakkety:
  Fix Released
Status in tbb source package in Zesty:
  Fix Released

Bug description:
  tbb package is available since Yaketty 16.10..
  As mentioned here  https://launchpad.net/ubuntu/+source/tbb

  Potential customer case requires this package also compile on s390x for 
Xenial.
  =
  Changes (w.r.t. Intel TBB 4.4 Update 2):
  =
  - Modified parallel_sort to not require a default constructor for values
  ??? and to use iter_swap() for value swapping.
  - Added support for creating or initializing a task_arena instance that
  ??? is connected to the arena currently used by the thread.
  - graph/binpack example modified to use multifunction_node.
  - For performance analysis, use Intel(R) VTune(TM) Amplifier XE 2015
  ??? and higher; older versions are no longer supported.
  - Improved support for compilation with disabled RTTI, by omitting its use
  ??? in auxiliary code, such as assertions. However some functionality,
  ??? particularly the flow graph, does not work if RTTI is disabled.
  - The tachyon example for Android* can be built using Android Studio 1.5
  ??? and higher with experimental Gradle plugin 0.4.0.
  Preview Features:
  - Added class opencl_subbufer that allows using OpenCL* sub-buffer
  ??? objects with opencl_node.
  - Class global_control supports the value of 1 for
  ??? max_allowed_parallelism.
  Bugs fixed:
  - Fixed a race causing "TBB Warning: setaffinity syscall failed" message.
  - Fixed a compilation issue on OS X* with Intel(R) C++ Compiler 15.0.
  - Fixed a bug in queuing_rw_mutex::downgrade() that could temporarily
  ??? block new readers.
  - Fixed speculative_spin_rw_mutex to stop using the lazy subscription
  ??? technique due to its known flaws.
  - Fixed memory leaks in the tool support code.

  =
  Changes (w.r.t. Intel TBB 4.4 Update 3):
  =
  - Removed a few cases of excessive user data copying in the flow graph.
  - Improved robustness of concurrent_bounded_queue::abort() in case of
  ? ? simultaneous push and pop operations.
  Preview Features:
  - Added tbb::flow::async_msg, a special message type to support
  ? ? communications between the flow graph and external asynchronous
  ? ? activities.
  - async_node modified to support use with C++03 compilers.
  Bugs fixed:
  - Fixed a bug in dynamic memory allocation replacement for Windows* OS.
  - Fixed excessive memory consumption on Linux* OS caused by enabling
  ? ? zero-copy realloc.
  - Fixed performance regression on Intel(R) Xeon Phi(tm) coprocessor with
  ? ? auto_partitioner.

  =
  Changes (w.r.t. Intel TBB 4.4 Update 4):
  =
  - Modified graph/fgbzip2 example to remove unnecessary data queuing.
  Preview Features:
  - Added a Python* module which is able to replace Python's thread pool?
  ? ? class with the implementation based on Intel TBB task scheduler.
  Bugs fixed:
  - Fixed the implementation of 64-bit tbb::atomic for IA-32 architecture
  ? ? to work correctly with GCC 5.2 in C++11/14 mode.
  - Fixed a possible crash when tasks with affinity (e.g. specified via
  ? ? affinity_partitioner) are used simultaneously with task priority
  ? ? changes.
  You can download Intel TBB 4.4 update 5 from open source site.

  =
  After inclusion of these mentioned fixes, it runs on Yaketty..!

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

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

[Touch-packages] [Bug 1679674] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From heinz-werner_se...@de.ibm.com 2017-04-12 03:55 EDT---
IBM bugzilla status -> closed

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

Title:
  s390x: Interface order in kvm guest image not predictable

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  ---Problem Description---
  Running the Ubuntu16 cloud image on an ubuntu 16.04 KVM host. The KVM guest 
is launched with 2 network interfaces connected to 2 different open vswitch 
bridges.

  The problem is 2-fold:
  #1 In the guest it seems like that the interface order is not predicitve. 
Device names used are eth0, eth1. The device that is listed first in libvirts 
domain.xml is not necessarily eth0. 
  #2 The device names are not persistet. On the next boot eth0 might be eth1 
and vice verca.
   
  Contact Information = andreas.scheur...@de.ibm.com 
   
  ---uname output---
  Linux Ubuntu16 4.4.0-70-generic #91-Ubuntu SMP Wed Mar 22 12:48:02 UTC 2017 
s390x s390x s390x GNU/Linux
   
  Machine Type = KVM guest 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   guest Domain xml:
  
Ubuntu16VM
455e6998-cec1-4010-99a6-d033ee6d3385
524288
524288
2

  /machine


  hvm
  


destroy
restart
preserve

  /usr/bin/qemu-system-s390x
  






  
  







  
  


  
  



  





  
  



  





  
  



  
  


  


  libvirt-455e6998-cec1-4010-99a6-d033ee6d3385
  libvirt-455e6998-cec1-4010-99a6-d033ee6d3385

  

  
  in the guest check interfaces and remember the mac address
  # ip a
  Do a reboot (or multiple) and check again if the interface-mac combination is 
still the same

  The interface order should change from time to time
   
  Userspace tool common name: udev? 

  Userspace rpm: ? 
   
  The userspace tool has the following bit modes: 64 

  Userspace tool obtained from project website:  na

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

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

[Touch-packages] [Bug 1679691] Re: libseccomp fix - s390: handle multiplexed syscalls correctly

[Frank Heimes]

Patch is only required for the Xenial libseccomp package.

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

Title:
  libseccomp fix - s390: handle multiplexed syscalls correctly

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in libseccomp package in Ubuntu:
  Confirmed
Status in libseccomp source package in Xenial:
  New
Status in libseccomp source package in Yakkety:
  New
Status in libseccomp source package in Zesty:
  Confirmed
Status in libseccomp source package in aa-series:
  New

Bug description:
  Within Xenial version 2.2.3 of seccomp is included.
  With Yaketty version 2.3.1 is available and fixed this problem.

  Even Docker is working on a SNAP solution, please provide the fix to
  16.04.

  
  With following patches this can be applied to 2.2.3 in support of the 16.04 
LTS Release
  16.04

  Here the upstream git commits for the patches:

  0001-arch-fix-a-problem-with-the-rule-rewrites-in-_seccom.patch
  1d63fad4a064b80e0b921b16ed419f3342337ed4
   
  0001-all-block-negative-syscall-numbers-from-the-filter.patch
  51c46f80c1edee863bbc4eb21b03decc44e69a45 

  0001-api-limit-errno-values-to-MAX_ERRNO.patch
  0d287caf43792239b107ee3215b32b8bc901f9c3 

  0001-db-fix-a-minor-style-problem.patch
  61c28579a984a6c4bd87ec585dc6d5cd4cc0e702 

  0001-db-make-the-individual-db-filter-ops-private.patch
  a4478ddcd4e3b34fcd9c526dcf54f0d79b33ac16

  0001-db-store-the-rules-used-to-build-the-filter.patch
  f16f405f61ecdbad202257b61004b85fce64d75c 

  0001-arch-make-use-of-function-tables-instead-of-switch-s.patch
  57df79c166b26d5044e7e27099e6e69671e727dd 

  0001-db-introduce-transaction-support.patch
  9be1538a4ac0e45047a3f1b79691505c3d11ca31 

  0001-arch-move-the-low-level-filter-rule-addition-code-in.patch
  996e445a74823c735757413fda809e1ed0afc7d4 

  0001-arch-enable-more-involved-arch-ABI-specific-rule-cre.patch
  5b42b8cfa25506fa260c8f46b4a063b5cfd09d1c 

  0001-arch-basic-support-for-multiplexed-and-direct-socket.patch
  d32c3bfa4b07add90dcd04292eb4ba278dd103ba 

  0001-arch-generate-both-multiplexed-and-direct-socket-sys.patch
  983835f3e0fd000a42c8beaea9d7fbe72665 

  0001-tests-add-a-test-for-the-different-types-of-socket-s.patch
  099f4214ce4fe5f53cf0f59e96b71bf4d54a8cd6 

  0001-api-add-a-seccomp_version-API-call.patch
  58a7c20d4c2defc1c984c5c7391ecc60093f85fa 

  0001-tests-create-a-simple-live-test-to-verify-we-can-set.patch
  8ed78c3859f476d302995b43d6739f3341f5b37d 

  0001-s390-handle-multiplexed-syscalls-correctly.patch
  47516603828396f85107ea3e2a254958c2bc3ff5 

  0001-arch-fix-the-multiplexed-ipc-syscalls.patch
  3a89bd144885f54aff86f2e275859a1483992edd

  With the following additional commit all tests pass with "make check"

  0001-tests-remove-fuzzing-from-28-sim-arch_x86.tests.patch
  0d8504bc192e0989494df06efc4b186a9f02e20a

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

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

[Touch-packages] [Bug 1679674] Re: s390x: Interface order in kvm guest image not predictable

[Frank Heimes]

Yes, that is the current plan.

** Also affects: ubuntu-z-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-z-systems
   Status: New => Fix Released

** Tags added: s390x

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

Title:
  s390x: Interface order in kvm guest image not predictable

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  ---Problem Description---
  Running the Ubuntu16 cloud image on an ubuntu 16.04 KVM host. The KVM guest 
is launched with 2 network interfaces connected to 2 different open vswitch 
bridges.

  The problem is 2-fold:
  #1 In the guest it seems like that the interface order is not predicitve. 
Device names used are eth0, eth1. The device that is listed first in libvirts 
domain.xml is not necessarily eth0. 
  #2 The device names are not persistet. On the next boot eth0 might be eth1 
and vice verca.
   
  Contact Information = andreas.scheur...@de.ibm.com 
   
  ---uname output---
  Linux Ubuntu16 4.4.0-70-generic #91-Ubuntu SMP Wed Mar 22 12:48:02 UTC 2017 
s390x s390x s390x GNU/Linux
   
  Machine Type = KVM guest 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   guest Domain xml:
  
Ubuntu16VM
455e6998-cec1-4010-99a6-d033ee6d3385
524288
524288
2

  /machine


  hvm
  


destroy
restart
preserve

  /usr/bin/qemu-system-s390x
  






  
  







  
  


  
  



  





  
  



  





  
  



  
  


  


  libvirt-455e6998-cec1-4010-99a6-d033ee6d3385
  libvirt-455e6998-cec1-4010-99a6-d033ee6d3385

  

  
  in the guest check interfaces and remember the mac address
  # ip a
  Do a reboot (or multiple) and check again if the interface-mac combination is 
still the same

  The interface order should change from time to time
   
  Userspace tool common name: udev? 

  Userspace rpm: ? 
   
  The userspace tool has the following bit modes: 64 

  Userspace tool obtained from project website:  na

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

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

[Touch-packages] [Bug 1682030] [NEW] package resolvconf 1.78ubuntu2 failed to install/upgrade: package resolvconf is not ready for configuration cannot configure (current status 'half-installed')

[Kristofer St.Germain]

Public bug reported:

I have no idea what is happening

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: resolvconf 1.78ubuntu2
ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
Uname: Linux 4.8.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
AptOrdering:
 resolvconf: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Wed Apr 12 00:39:21 2017
DpkgTerminalLog:
 dpkg: error processing package resolvconf (--configure):
  package resolvconf is not ready for configuration
  cannot configure (current status 'half-installed')
ErrorMessage: package resolvconf is not ready for configuration  cannot 
configure (current status 'half-installed')
InstallationDate: Installed on 2017-04-12 (0 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: resolvconf
Title: package resolvconf 1.78ubuntu2 failed to install/upgrade: package 
resolvconf is not ready for configuration  cannot configure (current status 
'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package resolvconf 1.78ubuntu2 failed to install/upgrade: package
  resolvconf is not ready for configuration  cannot configure (current
  status 'half-installed')

Status in resolvconf package in Ubuntu:
  New

Bug description:
  I have no idea what is happening

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: resolvconf 1.78ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  AptOrdering:
   resolvconf: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Apr 12 00:39:21 2017
  DpkgTerminalLog:
   dpkg: error processing package resolvconf (--configure):
package resolvconf is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package resolvconf is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-04-12 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: resolvconf
  Title: package resolvconf 1.78ubuntu2 failed to install/upgrade: package 
resolvconf is not ready for configuration  cannot configure (current status 
'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1654406] Re: Ubuntu 16.04.1LTS - (tracker-extract:3459): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly.

[Bug Watch Updater]

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

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

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

Title:
  Ubuntu 16.04.1LTS - (tracker-extract:3459): dconf-CRITICAL **: unable
  to create file '/run/user/1000/dconf/user': Permission denied.  dconf
  will not work properly.

Status in Tracker:
  Fix Released
Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  chris@localhost:~$ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  chris@localhost:~$ apt-cache policy tracker-extract
  tracker-extract:
Installed: 1.8.2-0ubuntu1~xenial3
Candidate: 1.8.2-0ubuntu1~xenial3
Version table:
   *** 1.8.2-0ubuntu1~xenial3 500
  500 http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu 
xenial/main amd64 Packages

  Jan  5 15:10:42 localhost tracker-extract.desktop[3459]: (tracker-
  extract:3459): dconf-CRITICAL **: unable to create file
  '/run/user/1000/dconf/user': Permission denied.  dconf will not work
  properly.

  Jan  5 15:12:25 localhost tracker-extract.desktop[3459]: message
  repeated 2 times: [ (tracker-extract:3459): dconf-CRITICAL **: unable
  to create file '/run/user/1000/dconf/user': Permission denied.  dconf
  will not work properly.]

  Jan  5 15:14:27 localhost tracker-extract.desktop[3459]: (tracker-
  extract:3459): dconf-CRITICAL **: unable to create file
  '/run/user/1000/dconf/user': Permission denied.  dconf will not work
  properly.

  and so on every two minutes +- a few seconds.

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

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

[Touch-packages] [Bug 1679674] Re: s390x: Interface order in kvm guest image not predictable

[Andreas Scheuring]

Thanks for this fix. It's solved in 17.04, but won't be backported to
16.04. Is that right?

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

Title:
  s390x: Interface order in kvm guest image not predictable

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  ---Problem Description---
  Running the Ubuntu16 cloud image on an ubuntu 16.04 KVM host. The KVM guest 
is launched with 2 network interfaces connected to 2 different open vswitch 
bridges.

  The problem is 2-fold:
  #1 In the guest it seems like that the interface order is not predicitve. 
Device names used are eth0, eth1. The device that is listed first in libvirts 
domain.xml is not necessarily eth0. 
  #2 The device names are not persistet. On the next boot eth0 might be eth1 
and vice verca.
   
  Contact Information = andreas.scheur...@de.ibm.com 
   
  ---uname output---
  Linux Ubuntu16 4.4.0-70-generic #91-Ubuntu SMP Wed Mar 22 12:48:02 UTC 2017 
s390x s390x s390x GNU/Linux
   
  Machine Type = KVM guest 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   guest Domain xml:
  
Ubuntu16VM
455e6998-cec1-4010-99a6-d033ee6d3385
524288
524288
2

  /machine


  hvm
  


destroy
restart
preserve

  /usr/bin/qemu-system-s390x
  






  
  







  
  


  
  



  





  
  



  





  
  



  
  


  


  libvirt-455e6998-cec1-4010-99a6-d033ee6d3385
  libvirt-455e6998-cec1-4010-99a6-d033ee6d3385

  

  
  in the guest check interfaces and remember the mac address
  # ip a
  Do a reboot (or multiple) and check again if the interface-mac combination is 
still the same

  The interface order should change from time to time
   
  Userspace tool common name: udev? 

  Userspace rpm: ? 
   
  The userspace tool has the following bit modes: 64 

  Userspace tool obtained from project website:  na

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

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