[Touch-packages] [Bug 1719720] Re: [LTCTest][libvpd] Process '/bin/touch /run/run.vpdupdate' failed with exit code 127

[Steve Langasek]

'MemoryDenyWriteExecute=yes' is defined in systemd.exec(5) as:

If set, attempts to create memory mappings that are writable and
executable at the same time, or to change existing memory mappings to
become executable, or mapping shared memory segments as executable are
prohibited. Specifically, a system call filter is added that rejects
mmap(2) system calls with both PROT_EXEC and PROT_WRITE set, mprotect(2)
system calls with PROT_EXEC set and shmat(2) system calls with SHM_EXEC
set.

It is surprising that /bin/touch should trip this check.  This will
require investigation.

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

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

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

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

Title:
  [LTCTest][libvpd] Process '/bin/touch /run/run.vpdupdate' failed with
  exit code 127

Status in The Ubuntu-power-systems project:
  New
Status in coreutils package in Ubuntu:
  Triaged

Bug description:
  ---Problem Description---
  Currently syslog is getting flooded with below log messages ..
  Sep 25 03:16:41 ubuntu1710 systemd-udevd[2654]: Process '/bin/touch 
/run/run.vpdd
  update' failed with exit code 127.

  This is on UBuntu 17.10 latest build.. 
   
  ---uname output---
  Linux ubuntu1710 4.12.0-11-generic #12-Ubuntu SMP Fri Aug 11 12:23:06 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = ZZ-L 

  ---Steps to Reproduce---
   I have seen these messages logged more often when we do any hotplug 
operations.. ex. cpu hotplug..

  Ok. .this is the continuation of LTC #144627 / Launchpad #1682774.

  As suggested in that bug, we did change udev script to create
  temporary file under /run and that patch is available in ubuntu 17.10.

  Looks like this is udev script issue. If I modify systemd-udevd like
  below it works fine.

  I've limited udev knowledge. I don't know if you have any other better
  solution to this issue.

  root@ltc-boston123:/lib/systemd/system# diff -Naurp  
systemd-udevd.service.org systemd-udevd.service
  --- systemd-udevd.service.org 2017-09-26 04:37:47.090057318 -0500
  +++ systemd-udevd.service 2017-09-26 04:37:55.381739372 -0500
  @@ -25,7 +25,7 @@ KillMode=mixed
   WatchdogSec=3min
   TasksMax=infinity
   MountFlags=slave
  -MemoryDenyWriteExecute=yes
  +#MemoryDenyWriteExecute=yes
   RestrictRealtime=yes
   RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6
   SystemCallArchitectures=native

  
  -Vasant

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

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

[Touch-packages] [Bug 1704171] Re: WiFi connections unstable

[Kai-Heng Feng]

Can you check if v4.13 has this issue or not? 17.10 will use v4.13 and
we should make sure it doesn't have the issue.

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

Title:
  WiFi connections unstable

Status in network-manager package in Ubuntu:
  New

Bug description:
  I have 3 WiFi signals here, and use them all without issue most of the
  time.  Since upgrading to 17.04 I have issues where my wifi will not
  connect to one of the other 2 signals, then also won't re-connect to
  the signal that was just in use.  When this happens, I can do a
  'restart' and it will connect just fine to any of the 3 signals.

  While it was failing a bit ago, I captured the syslog of whats going
  on and will include it below.

  Distributor ID:   Ubuntu
  Description:  Ubuntu 17.04
  Release:  17.04
  Codename: zesty

  Linux lisa-Inspiron-7720 4.10.0-28-generic #32-Ubuntu SMP Fri Jun 30
  05:32:18 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux


  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.2717] device (wlp2s0): Activation: starting connection 'LisaN' 
(58396782-9fe4-4ce3-b0e6-f72df56c72d5)
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.2720] audit: op="connection-activate" 
uuid="58396782-9fe4-4ce3-b0e6-f72df56c72d5" name="LisaN" pid=1962 uid=1000 
result="success"
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.2723] device (wlp2s0): state change: disconnected -> prepare 
(reason 'none') [30 40 0]
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.2725] manager: NetworkManager state is now CONNECTING
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.2779] device (wlp2s0): set-hw-addr: set-cloned MAC address to 
C4:D9:87:6E:9B:0F (permanent)
  Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [  312.891148] iwlwifi 
:02:00.0: L1 Enabled - LTR Disabled
  Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [  312.898132] iwlwifi 
:02:00.0: L1 Enabled - LTR Disabled
  Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [  312.898220] iwlwifi 
:02:00.0: Radio type=0x2-0x1-0x0
  Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [  313.183332] iwlwifi 
:02:00.0: L1 Enabled - LTR Disabled
  Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [  313.190314] iwlwifi 
:02:00.0: L1 Enabled - LTR Disabled
  Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [  313.190403] iwlwifi 
:02:00.0: Radio type=0x2-0x1-0x0
  Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [  313.274573] IPv6: 
ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6644] device (wlp2s0): supplicant interface state: inactive -> 
disabled
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6649] device (wlp2s0): state change: prepare -> config (reason 
'none') [40 50 0]
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6654] device (wlp2s0): Activation: (wifi) access point 'LisaN' has 
security, but secrets are required.
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6654] device (wlp2s0): state change: config -> need-auth (reason 
'none') [50 60 0]
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6728] device (wlp2s0): state change: need-auth -> prepare (reason 
'none') [60 40 0]
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6735] device (wlp2s0): state change: prepare -> config (reason 
'none') [40 50 0]
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6738] device (wlp2s0): Activation: (wifi) connection 'LisaN' has 
security, and secrets exist.  No new secrets needed.
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6739] Config: added 'ssid' value 'LisaN'
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6740] Config: added 'scan_ssid' value '1'
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6740] Config: added 'key_mgmt' value 'WPA-PSK'
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6740] Config: added 'psk' value ''
  Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: Can't set a parent on 
widget which has a parent
  Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: gtk_widget_destroy: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: gtk_widget_destroy: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: Can't set a parent on 
widget which has a parent
  Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: gtk_widget_destroy: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: gtk_widget_destroy: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Jul 13 09:52:39 

[Touch-packages] [Bug 1707027] Re: Sound device no longer detected after closing laptop lid

[Launchpad Bug Tracker]

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

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

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

Title:
  Sound device no longer detected after closing laptop lid

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  My sound device was working ok before I closed my laptop lid last week.
  At that time I had Ubuntu 17.04, then I decided to overwrite all the disk 
contents with a fresh install of Ubuntu 16.04 LTS but I still have the same 
problem, even right after the new OS installation.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.3
  ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-27-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alan   1726 F pulseaudio
  Date: Thu Jul 27 14:21:12 2017
  InstallationDate: Installed on 2017-07-21 (5 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.2
  dmi.board.name: 09WC1G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.2:bd03/09/2017:svnDellInc.:pnInspiron7460:pvr:rvnDellInc.:rn09WC1G:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.name: Inspiron 7460
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2017-07-27T11:37:21.959813

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

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

[Touch-packages] [Bug 1716092] Re: Enabling Auto switching streams on new active output causes pulseaudio to crash

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1716092

** Tags added: iso-testing

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

Title:
  Enabling Auto switching streams on new active output causes pulseaudio
  to crash

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Not sure if this is a plasma-pa bug or a pulseaudio bug.  In plasma-pa
  -> Audio Volumue -> Advanced tab checking the "Automatically
  switch all running streams when a new output becomes available" cause
  PA to crash.  If the /etc/pulse/default.pa file is modified by
  commenting out following line:

load-module module-switch-on-connect

  PA will start as expected.  I have not checked to see if the auto
  switching works when the default.pa line is commented out.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: plasma-pa 4:5.10.5-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Sep  8 23:07:29 2017
  InstallationDate: Installed on 2016-11-15 (298 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  SourcePackage: plasma-pa
  UpgradeStatus: Upgraded to artful on 2017-08-27 (12 days ago)

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

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

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

[Launchpad Bug Tracker]

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

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

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

Title:
  Need updated libimobiledevice to mount IOS 11 devices

Status in libimobiledevice package in Ubuntu:
  Confirmed

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

  The relevant log lines from gvfs-afc are:

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

  The fix is here in the upstream github:

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

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

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

[Touch-packages] [Bug 1719765] Re: Evolution can't add new data(contact, appointment) to nextcloud

[nehrka]

gnome calendar also affected. So can't be an evolution only bug.

** Package changed: evolution (Ubuntu) => gnome-online-accounts (Ubuntu)

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

Title:
  Evolution can't add new data(contact, appointment)  to nextcloud

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

Bug description:
  Evolution is not able to add new data eg. new contacts, new
  appointments to nextcloud. Whenn trying I get the following error
  message: "... 415 (Unsupported Media Type):
  Sabre\DAV\Exception\UnsupportedMediaType ...". Synchronizing from
  nextcloud server to client works as expected.

  I'm using Ubuntu 17.10 and on the server side Ubuntu 16.04 + Nextcloud
  snap is used.

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

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

[Touch-packages] [Bug 1719765] [NEW] Evolution can't add new data(contact, appointment) to nextcloud

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Evolution is not able to add new data eg. new contacts, new appointments
to nextcloud. Whenn trying I get the following error message: "... 415
(Unsupported Media Type): Sabre\DAV\Exception\UnsupportedMediaType ...".
Synchronizing from nextcloud server to client works as expected.

I'm using Ubuntu 17.10 and on the server side Ubuntu 16.04 + Nextcloud
snap is used.

** Affects: gnome-online-accounts (Ubuntu)
 Importance: Undecided
 Status: New

-- 
Evolution can't add new data(contact, appointment)  to nextcloud
https://bugs.launchpad.net/bugs/1719765
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gnome-online-accounts in Ubuntu.

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

[Touch-packages] [Bug 1418400] Re: 'Failed to add/activate connection' error pops up when user try to connect guest wifi in login interface.

[Launchpad Bug Tracker]

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

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

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

Title:
  'Failed to add/activate connection' error pops up when user try to
  connect guest wifi in login interface.

Status in NetworkManager:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Steps:
  1. Install stock ubuntu image
  2. Do not connect wifi on OOBE stage
  3. Log in 'Guest' session
  4. Connect a available wifi
  5. Log out
  6. In login interface, select the user whom configured on OOBE stage
  7. Try to connect previous wifi which 'Guest' connected in login interface
  8. Verify the result

  Actual result:
  'Failed to add/activate connection' error pops up

  Expected result:
  User could connect the wifi successfully without error message

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

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

[Touch-packages] [Bug 1711851] Re: Disable MAC address randomization on Live system

[Mantas Kriaučiūnas]

** Summary changed:

- bad default setting
+ Disable MAC address randomization on Live system

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

Title:
  Disable MAC address randomization on Live system

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I'm using the pre-release version of artful 17.10 and network manager
  1.8.2-1ubuntu2 Much like in Debian Stretch, network-manager is set to
  use the random mac address feature of network manager, which doesn't
  allow certain wifi cards/ routers to work together. See Debian bug
  836351.  I think this feature should be disabled on a live cd, because
  it isn't fixable during an install and it might cause a user just to
  give up and not install Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.2-1ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sat Aug 19 14:00:17 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-08-19 (0 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha amd64 
(20170818)
  IpRoute:
   default via 192.168.1.1 dev wlxec086b17f6d1 proto static metric 600 
   169.254.0.0/16 dev wlxec086b17f6d1 scope link metric 1000 
   192.168.1.0/24 dev wlxec086b17f6d1 proto kernel scope link src 192.168.1.4 
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2017-08-19T13:51:03.103665
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   
STATE  ACTIVE-PATH SLAVE 
   556F02  72b161b9-3dad-4583-ae59-1d3e0402b37e  802-11-wireless  
1503165502  Sat 19 Aug 2017 01:58:22 PM EDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlxec086b17f6d1  
activated  /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  1d860881-8bc6-3d0d-8455-2b15a87f1307  802-3-ethernet   
1503165498  Sat 19 Aug 2017 01:58:18 PM EDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --   
-- --  --
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH
  CONNECTION  CON-UUID  CON-PATH
   
   wlxec086b17f6d1  wifi  connected
/org/freedesktop/NetworkManager/Devices/3  556F02  
72b161b9-3dad-4583-ae59-1d3e0402b37e  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   eno1 ethernet  unavailable  
/org/freedesktop/NetworkManager/Devices/2  --  --   
 -- 
   lo   loopback  unmanaged
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1711851] Re: bad default setting

[Launchpad Bug Tracker]

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

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

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

Title:
  Disable MAC address randomization on Live system

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I'm using the pre-release version of artful 17.10 and network manager
  1.8.2-1ubuntu2 Much like in Debian Stretch, network-manager is set to
  use the random mac address feature of network manager, which doesn't
  allow certain wifi cards/ routers to work together. See Debian bug
  836351.  I think this feature should be disabled on a live cd, because
  it isn't fixable during an install and it might cause a user just to
  give up and not install Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.2-1ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sat Aug 19 14:00:17 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-08-19 (0 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha amd64 
(20170818)
  IpRoute:
   default via 192.168.1.1 dev wlxec086b17f6d1 proto static metric 600 
   169.254.0.0/16 dev wlxec086b17f6d1 scope link metric 1000 
   192.168.1.0/24 dev wlxec086b17f6d1 proto kernel scope link src 192.168.1.4 
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2017-08-19T13:51:03.103665
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   
STATE  ACTIVE-PATH SLAVE 
   556F02  72b161b9-3dad-4583-ae59-1d3e0402b37e  802-11-wireless  
1503165502  Sat 19 Aug 2017 01:58:22 PM EDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlxec086b17f6d1  
activated  /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  1d860881-8bc6-3d0d-8455-2b15a87f1307  802-3-ethernet   
1503165498  Sat 19 Aug 2017 01:58:18 PM EDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --   
-- --  --
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH
  CONNECTION  CON-UUID  CON-PATH
   
   wlxec086b17f6d1  wifi  connected
/org/freedesktop/NetworkManager/Devices/3  556F02  
72b161b9-3dad-4583-ae59-1d3e0402b37e  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   eno1 ethernet  unavailable  
/org/freedesktop/NetworkManager/Devices/2  --  --   
 -- 
   lo   loopback  unmanaged
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1718927] Re: No hdmi sound after suspend/resume on 16.04

[Daniel van Vugt]

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

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

Title:
  No hdmi sound after suspend/resume on 16.04

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When plugging in a HDMI TV to Lenovo Carbon 3rd Edition, sound works
  perfectly, but when I suspend computer and resume it there is no sound
  via HDMI in TV. However sound via built in speakers works fine. The
  only thing I can do to restore sound is to reboot the machine. Similar
  problem was discussed in following thread
  https://ubuntuforums.org/showthread.php?t=2251651 with no solution. I
  tested it on several versions of kernel 4.4.0 and on 4.4.8. Still no
  solution.

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

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

[Touch-packages] [Bug 1661329] Re: Wifi password not taken into account if not entered rapidly

[Mantas Kriaučiūnas]

Maybe this bug is a duplicate of LP bug #1650835 (wifi association times
out while typing password)?

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

Title:
  Wifi password not taken into account if not entered rapidly

Status in network-manager package in Ubuntu:
  New

Bug description:
  Hi,

  We install ubuntu/mint to numerous people and we got multiple
  reports that the wifi password was not taken into account. We managed
  to reproduce it by

  1 - Select your wifi network
  2 - Enter a fake password (Just to simulate a user error not entering well 
his wifi password)
  3 - Obviously here we cannot connect, so we wait
  4 - Password is asked a second time, and we enter it without error but we 
take our time to do so ( or wait some time after ). By taking our time we 
simulate people who are not fluent with their keyboard.
  5 - Wait to connect
  6 - Password is asked a third time.
  7 - Here if we go into the properties of the wifi (Applet > Modify > Modify) 
and check the password… the first fake password is still there

  Nice day

  It might be a double of this bug
  https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1219171

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

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

[Touch-packages] [Bug 1650835] Re: wifi association times out while typing password

[Launchpad Bug Tracker]

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

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

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

Title:
  wifi association times out while typing password

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Visiting inlaws for the holidays.

  The wifi password is a long numeric string, which takes a long time to
  type.

  I typed it several times and failed to connect.  I verified it and
  tried again and again.  Finally typed it into text file, copied and
  pasted, it connected.

  I suspect the connection was timing out or something while I typed the
  stupid long numeric password.

  What I expected to happen:

  type password, click connect, get connection, or some useful error.
  user happy.

  What actually happened:

  type password, click connect, dialog disappears and nothing else
  happens. user confused and unhappy.

  It shouldn't silently fail because I'm taking a long time to type.

  
  thanks, love you!  <3

  
  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  $ apt-cache policy network-manager
  network-manager:
Installed: 1.2.2-0ubuntu0.16.04.3
Candidate: 1.2.2-0ubuntu0.16.04.3
Version table:
   *** 1.2.2-0ubuntu0.16.04.3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.1.93-0ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Dec 17 21:24:22 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-03 (76 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.0.1 dev wlp4s0  proto static  metric 600 
   169.254.0.0/16 dev wlp4s0  scope link  metric 1000 
   192.168.0.0/24 dev wlp4s0  proto kernel  scope link  src 192.168.0.27  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp4s0 wifi  connected/org/freedesktop/NetworkManager/Devices/0  
Harry 5G10d05741-6f9e-468e-b6fd-8f0d5a739ce2  
/org/freedesktop/NetworkManager/ActiveConnection/4 
   enp0s31f6  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  
--  ----
 
   lo loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 964705] Re: System policy prevents modification of network settings for all users

[Mantas Kriaučiūnas]

It seems Debian fix is simply to allow users from netdev (and sudo)
group add/change system-wide NetworkManager connections, this fix is
added in network-manager 0.9.4.0-7 and is merged in Ubuntu,

look at
/var/lib/polkit-1/localauthority/10-vendor.d/org.freedesktop.NetworkManager.pkla

[Adding or changing system-wide NetworkManager connections]
Identity=unix-group:netdev;unix-group:sudo
Action=org.freedesktop.NetworkManager.settings.modify.system

So, main problem is that GNOME-Shell users aren't added to netdev group
by default?

Walter Lapchynski (wxl) wrote on 2015-06-29:#38
> Mathieu, it doesn't seem that the upstream fix in Debian ever got merged into 
> Ubuntu.
> Is there a reason for this?

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

Title:
  System policy prevents modification of network settings for all users

Status in NetworkManager:
  Invalid
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager package in Debian:
  Fix Released
Status in network-manager package in openSUSE:
  Fix Released

Bug description:
  This seems like a regression? The screen shot is at
  http://thesii.org/Screenshot.jpg The nearest link I can find is from
  the forum area at http://ubuntuforums.org/showthread.php?p=1146

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  ApportVersion: 1.95-0ubuntu1
  Architecture: amd64
  CRDA: Error: [Errno 2] No such file or directory
  Date: Sun Mar 25 19:36:45 2012
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Alpha amd64 (20120323)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1719750] [NEW] QSystemTrayIcon creates an icon in the wrong place.

[Trent Nelson]

Public bug reported:

This is probably a long shot given the age, but any chance of getting
the following patches backported to the Trusty build from upstream?

https://code.qt.io/cgit/qt/qtbase.git/commit/?h=v5.2.1=d8090022f66cc6cff6af5ed2ae702212fd172ff7
https://code.qt.io/cgit/qt/qtbase.git/commit/?h=v5.2.1=612953a626ec21b8518ee23a4f5268b566cf41e5
https://code.qt.io/cgit/qt/qtbase.git/commit/?h=v5.2.1=cec103897f5109c70f2fd69460d10d21fa4feded
https://code.qt.io/cgit/qt/qtbase.git/commit/?h=v5.2.1=38abd653774aa0b3c5cdfd9a8b78619605230726

Upstream issue: https://bugreports.qt.io/browse/QTBUG-31762

I am experiencing this with the Dash Core Wallet, built from their git
tag v0.12.1.5.  The tray icon is being rendered outside the tray area.
Always the top-left of the left-most monitor.

Ubuntu 14.04.5 (fully patched as of posting)
libqt5core5a is at 5.2.1+dfsg-1ubuntu14.3, which should have these patches 
already being as they were merged in the 5.2 upstream series.  I did not see 
them in the source tree here on launchpad, though.

** Affects: qtbase-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  QSystemTrayIcon creates an icon in the wrong place.

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  This is probably a long shot given the age, but any chance of getting
  the following patches backported to the Trusty build from upstream?

  
https://code.qt.io/cgit/qt/qtbase.git/commit/?h=v5.2.1=d8090022f66cc6cff6af5ed2ae702212fd172ff7
  
https://code.qt.io/cgit/qt/qtbase.git/commit/?h=v5.2.1=612953a626ec21b8518ee23a4f5268b566cf41e5
  
https://code.qt.io/cgit/qt/qtbase.git/commit/?h=v5.2.1=cec103897f5109c70f2fd69460d10d21fa4feded
  
https://code.qt.io/cgit/qt/qtbase.git/commit/?h=v5.2.1=38abd653774aa0b3c5cdfd9a8b78619605230726

  Upstream issue: https://bugreports.qt.io/browse/QTBUG-31762

  I am experiencing this with the Dash Core Wallet, built from their git
  tag v0.12.1.5.  The tray icon is being rendered outside the tray area.
  Always the top-left of the left-most monitor.

  Ubuntu 14.04.5 (fully patched as of posting)
  libqt5core5a is at 5.2.1+dfsg-1ubuntu14.3, which should have these patches 
already being as they were merged in the 5.2 upstream series.  I did not see 
them in the source tree here on launchpad, though.

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

-- 
Mailing list: https://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 1718927] Re: No hdmi sound after suspend/resume on 16.04

[Jacek Wróbel]

Hi Daniel,
I have Ubuntu Gnome 16.04.3. After resuming I can change device in settings
but it gives no result - still silence. The sound is only on the speakers.
The only way to restore sound in HDMI is to reboot.
But I am not pretty sure if the problem relates to pulse audio. I
reinstalled the system and did not install pulseaudio at all. Still the
same. After resuming there is no sound in HDMI.
Regards

Jacek Wróbel SAC, Kielecka 33, Święta Katarzyna, 26-010 Bodzentyn

2017-09-25 21:56 GMT+02:00 Daniel van Vugt
:

> At a guess, your system is probably reverting back to the default audio
> device on resume.
>
> What does it look like in Settings after resuming? Can you change the
> audio playback device back to HDMI by hand?
>
> ** Changed in: pulseaudio (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1718927
>
> Title:
>   No hdmi sound after suspend/resume on 16.04
>
> Status in pulseaudio package in Ubuntu:
>   Incomplete
>
> Bug description:
>   When plugging in a HDMI TV to Lenovo Carbon 3rd Edition, sound works
>   perfectly, but when I suspend computer and resume it there is no sound
>   via HDMI in TV. However sound via built in speakers works fine. The
>   only thing I can do to restore sound is to reboot the machine. Similar
>   problem was discussed in following thread
>   https://ubuntuforums.org/showthread.php?t=2251651 with no solution. I
>   tested it on several versions of kernel 4.4.0 and on 4.4.8. Still no
>   solution.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+
> bug/1718927/+subscriptions
>

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

Title:
  No hdmi sound after suspend/resume on 16.04

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When plugging in a HDMI TV to Lenovo Carbon 3rd Edition, sound works
  perfectly, but when I suspend computer and resume it there is no sound
  via HDMI in TV. However sound via built in speakers works fine. The
  only thing I can do to restore sound is to reboot the machine. Similar
  problem was discussed in following thread
  https://ubuntuforums.org/showthread.php?t=2251651 with no solution. I
  tested it on several versions of kernel 4.4.0 and on 4.4.8. Still no
  solution.

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

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

[Touch-packages] [Bug 1719748] [NEW] gdebi doesn't recognize that debs are already installed

[Jeremy Bicha]

Public bug reported:

I don't have gdebi installed so I am guessing at this bug.

https://youtu.be/yDrAbBAp-1A?t=15m55s

Please verify whether gdebi can tell whether a .deb has already been
installed.

Check whether this is a regression introduced in 0.9.5.7+nmu1ubuntu1 or
0.9.5.7+nmu1ubuntu2.

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

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

Title:
  gdebi doesn't recognize that debs are already installed

Status in gdebi package in Ubuntu:
  New

Bug description:
  I don't have gdebi installed so I am guessing at this bug.

  https://youtu.be/yDrAbBAp-1A?t=15m55s

  Please verify whether gdebi can tell whether a .deb has already been
  installed.

  Check whether this is a regression introduced in 0.9.5.7+nmu1ubuntu1
  or 0.9.5.7+nmu1ubuntu2.

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

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

[Touch-packages] [Bug 1630946] Re: ubuntu-server depends on open-iscsi and runs iscsid

[clickwir]

Would like to have the ability to cleanly remove iscsi related processes
from systems that don't need it.

Sitting there, it's not hard on resources, but I'm trying to shave off
anything I can.

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

Title:
  ubuntu-server depends on open-iscsi and runs iscsid

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  ubuntu-server has a hard dependency on open-iscsi, which means there
  is a daemon running (iscsid), and the package cannot be removed. All
  unnecessary daemons are a cause of concern when auditing a system.

  Propose moving this to "Recommends" instead, which currently has:

  Recommends: lxd, snapd

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-server 1.361
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Oct  6 10:43:04 2016
  Ec2AMI: ami-c06b1eb3
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: eu-west-1a
  Ec2InstanceType: t2.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1719746] [NEW] gdebi 0.9.5.7+nmu1ubuntu3 broke being able to open .debs on default Ubuntu desktop

[Jeremy Bicha]

Public bug reported:

I don't use gdebi but this commit looks wrong:

https://launchpad.net/ubuntu/+source/gdebi/0.9.5.7+nmu1ubuntu3

See
https://lintian.debian.org/tags/desktop-mime-but-no-exec-code.html

https://standards.freedesktop.org/desktop-entry-spec/desktop-entry-spec-
latest.html#mime-types

(Do not be confused by the Type=MimeType deprecation. This file is
Type=Application.)

Here's a user video report:
https://youtu.be/yDrAbBAp-1A?t=16m19s

** Affects: gdebi (Ubuntu)
 Importance: High
 Status: New


** Tags: artful regression-release

** Description changed:

  I don't use gdebi but this commit looks wrong:
  
  https://launchpad.net/ubuntu/+source/gdebi/0.9.5.7+nmu1ubuntu3
  
  See
  https://lintian.debian.org/tags/desktop-mime-but-no-exec-code.html
  
  https://standards.freedesktop.org/desktop-entry-spec/desktop-entry-spec-
  latest.html#mime-types
  
  (Do not be confused by the Type=MimeType deprecation. This file is
  Type=Application.)
  
  Here's a user video report:
- https://youtu.be/yDrAbBAp-1A?t=15m53s
+ https://youtu.be/yDrAbBAp-1A?t=16m19s

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

Title:
  gdebi 0.9.5.7+nmu1ubuntu3 broke being able to open .debs on default
  Ubuntu desktop

Status in gdebi package in Ubuntu:
  New

Bug description:
  I don't use gdebi but this commit looks wrong:

  https://launchpad.net/ubuntu/+source/gdebi/0.9.5.7+nmu1ubuntu3

  See
  https://lintian.debian.org/tags/desktop-mime-but-no-exec-code.html

  https://standards.freedesktop.org/desktop-entry-spec/desktop-entry-
  spec-latest.html#mime-types

  (Do not be confused by the Type=MimeType deprecation. This file is
  Type=Application.)

  Here's a user video report:
  https://youtu.be/yDrAbBAp-1A?t=16m19s

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

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

[Touch-packages] [Bug 1700382] Re: Boot times slow when LXD installed, due to poorly crafted systemd dependency chain

[Julian Andres Klode]

Also, well network.target is pulled in by a lot of stuff, and ifup is
just slow unless you specify allow-hotplug for your interfaces;
unrelated to network-online.target or lxd.

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

Title:
  Boot times slow when LXD installed, due to poorly crafted systemd
  dependency chain

Status in systemd package in Ubuntu:
  New

Bug description:
  Notice the time spent inside lxd-containers.service + lxd.service
  which require network + disk subsystems to work before they can work.

  This behavior can be recreated by installing + configuring LXD, with
  no containers.

  Both lxd-containers.service + lxd.service should be run asynchronously
  or at end of boot process.

  Boot should never hang waiting on these to finish.

  Fixing this, will reduce boot time by 20secs or 10% of total boot time for 
this machine.
  ___

  net11 # systemd-analyze critical-chain
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  graphical.target @1min 16.744s
  └─multi-user.target @1min 16.744s
└─lxd-containers.service @58.554s +18.188s
  └─lxd.service @1min 14.295s +2.457s
└─network-online.target @1min 14.285s
  └─network.target @1min 14.280s
└─ifup@eth2.service @55.020s
  └─network-pre.target @54.598s
└─ebtables.service @50.416s +2.106s
  └─local-fs.target @50.212s
└─var-lib-lxd-devlxd.mount @1min 16.572s
  └─local-fs-pre.target @48.449s
└─lvm2-monitor.service @48.004s +220ms
  └─lvm2-lvmetad.service @46.720s
└─system.slice @18.745s
  └─-.slice @2.783s

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

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

[Touch-packages] [Bug 1700382] Re: Boot times slow when LXD installed, due to poorly crafted systemd dependency chain

[Julian Andres Klode]

What does a finished boot mean for you? It should indeed not affect time
to login, but the boot time reported by systemd-analyze will always be
longer even if network-online and lxd stuff is the only thing not
started yet (as it considers the boot complete when all services are
running).

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

Title:
  Boot times slow when LXD installed, due to poorly crafted systemd
  dependency chain

Status in systemd package in Ubuntu:
  New

Bug description:
  Notice the time spent inside lxd-containers.service + lxd.service
  which require network + disk subsystems to work before they can work.

  This behavior can be recreated by installing + configuring LXD, with
  no containers.

  Both lxd-containers.service + lxd.service should be run asynchronously
  or at end of boot process.

  Boot should never hang waiting on these to finish.

  Fixing this, will reduce boot time by 20secs or 10% of total boot time for 
this machine.
  ___

  net11 # systemd-analyze critical-chain
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  graphical.target @1min 16.744s
  └─multi-user.target @1min 16.744s
└─lxd-containers.service @58.554s +18.188s
  └─lxd.service @1min 14.295s +2.457s
└─network-online.target @1min 14.285s
  └─network.target @1min 14.280s
└─ifup@eth2.service @55.020s
  └─network-pre.target @54.598s
└─ebtables.service @50.416s +2.106s
  └─local-fs.target @50.212s
└─var-lib-lxd-devlxd.mount @1min 16.572s
  └─local-fs-pre.target @48.449s
└─lvm2-monitor.service @48.004s +220ms
  └─lvm2-lvmetad.service @46.720s
└─system.slice @18.745s
  └─-.slice @2.783s

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

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

[Touch-packages] [Bug 1704618] Re: gnome-control-center crashed with SIGSEGV in manager_recheck_permissions()

[Jean-Baptiste Lallement]

network-manager (1.8.4-1ubuntu1) artful; urgency=medium

  * debian/patches/manager-Disconnect-from-signals-on-the-proxy-when-we.patch,
debian/patches/vpn-remote-connection-disconnect-signal-handlers-whe.patch:
Cherry-pick two patches from upstream. Fix leaked signal connections which
caused handlers to be called on disposed objects, leading to crashes in
some situations. (LP: #1704618) (LP: #1718006)

** Package changed: gnome-control-center (Ubuntu) => network-manager
(Ubuntu)

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

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

Title:
  gnome-control-center crashed with SIGSEGV in
  manager_recheck_permissions()

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

Bug description:
  Test Case:
  1. Open the 'Users' panel in gnome-control-center
  2. Select a user then click on 'Unlock' (top right button in the title bar)

  Expected result
  The panel is unlocked

  Actual Result
  This crash.

  
  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.24.2-0ubuntu5
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Jul 16 10:09:12 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-06-26 (20 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcCmdline: gnome-control-center --overview
  SegvAnalysis:
   Segfault happened at: 0x7ff4ea6fe6e9:cmpq   $0x0,0x58(%rax)
   PC (0x7ff4ea6fe6e9) ok
   source "$0x0" ok
   destination "0x58(%rax)" (0x0058) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libnm.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in ffi_call_unix64()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1719720] Re: [LTCTest][libvpd] Process '/bin/touch /run/run.vpdupdate' failed with exit code 127

[Andrew Cloke]

** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => Canonical Foundations Team 
(canonical-foundations)

** Changed in: ubuntu-power-systems
   Importance: Undecided => Medium

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

Title:
  [LTCTest][libvpd] Process '/bin/touch /run/run.vpdupdate' failed with
  exit code 127

Status in The Ubuntu-power-systems project:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  Currently syslog is getting flooded with below log messages ..
  Sep 25 03:16:41 ubuntu1710 systemd-udevd[2654]: Process '/bin/touch 
/run/run.vpdd
  update' failed with exit code 127.

  This is on UBuntu 17.10 latest build.. 
   
  ---uname output---
  Linux ubuntu1710 4.12.0-11-generic #12-Ubuntu SMP Fri Aug 11 12:23:06 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = ZZ-L 

  ---Steps to Reproduce---
   I have seen these messages logged more often when we do any hotplug 
operations.. ex. cpu hotplug..

  Ok. .this is the continuation of LTC #144627 / Launchpad #1682774.

  As suggested in that bug, we did change udev script to create
  temporary file under /run and that patch is available in ubuntu 17.10.

  Looks like this is udev script issue. If I modify systemd-udevd like
  below it works fine.

  I've limited udev knowledge. I don't know if you have any other better
  solution to this issue.

  root@ltc-boston123:/lib/systemd/system# diff -Naurp  
systemd-udevd.service.org systemd-udevd.service
  --- systemd-udevd.service.org 2017-09-26 04:37:47.090057318 -0500
  +++ systemd-udevd.service 2017-09-26 04:37:55.381739372 -0500
  @@ -25,7 +25,7 @@ KillMode=mixed
   WatchdogSec=3min
   TasksMax=infinity
   MountFlags=slave
  -MemoryDenyWriteExecute=yes
  +#MemoryDenyWriteExecute=yes
   RestrictRealtime=yes
   RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6
   SystemCallArchitectures=native

  
  -Vasant

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

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

[Touch-packages] [Bug 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

[Daniel van Vugt]

That's great. But all we intended to fix was...
https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.4

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

Title:
  Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  In 16.04 when a bluetooth audio device is connected it freezes video
  playback and also no sound comes from online audio only streams. Issue
  does not exist with a wired headset.

  This issue does not exist with 15.10. All updates have been installed
  on 16.04 including backports but they have not fixed the issue.

  It is not browser specific and not website specific.

  It is not hardware specific as it affects my laptop with an intel 7260
  card and my pc with an intel 8260 card.

  The issue exists on both ubuntu and kubuntu 16.04.

  I have reported it on the ubuntu support forums and after
  investigation a moderator noticed changed in the kernel from 4.4 and
  4.2 that may becausing the issue and asked me to file a bug report.

  The ubuntu forum thread can be found here.
  http://ubuntuforums.org/showthread.php?t=2326672

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-23-generic 4.4.0-23.41
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stephen1435 F pulseaudio
   /dev/snd/controlC0:  stephen1435 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jun  3 23:50:00 2016
  HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6
  InstallationDate: Installed on 2016-05-06 (28 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7978
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed 
root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago)
  dmi.bios.date: 05/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H170 GAMING M3 (MS-7978)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7978
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

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

[Touch-packages] [Bug 1704618] [NEW] gnome-control-center crashed with SIGSEGV in manager_recheck_permissions()

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Test Case:
1. Open the 'Users' panel in gnome-control-center
2. Select a user then click on 'Unlock' (top right button in the title bar)

Expected result
The panel is unlocked

Actual Result
This crash.


ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.24.2-0ubuntu5
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic x86_64
ApportVersion: 2.20.5-0ubuntu5
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Jul 16 10:09:12 2017
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2017-06-26 (20 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
ProcCmdline: gnome-control-center --overview
SegvAnalysis:
 Segfault happened at: 0x7ff4ea6fe6e9:  cmpq   $0x0,0x58(%rax)
 PC (0x7ff4ea6fe6e9) ok
 source "$0x0" ok
 destination "0x58(%rax)" (0x0058) not located in a known VMA region 
(needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libnm.so.0
 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 g_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV in ffi_call_unix64()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Affects: network-manager
 Importance: Medium
 Status: Fix Released

** Affects: network-manager (Ubuntu)
 Importance: High
 Status: Fix Committed


** Tags: amd64 apport-crash artful bugpattern-needed rls-aa-incoming 
third-party-packages
-- 
gnome-control-center crashed with SIGSEGV in manager_recheck_permissions()
https://bugs.launchpad.net/bugs/1704618
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to network-manager in Ubuntu.

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

[Touch-packages] [Bug 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

[Jason Gambrel]

Received pulseaudio update last night.  Appears to have resolved issue
so far for me, still need a bit of testing.  If it is resolved then MANY
thanks to those who squashed this annoying bug.

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

Title:
  Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  In 16.04 when a bluetooth audio device is connected it freezes video
  playback and also no sound comes from online audio only streams. Issue
  does not exist with a wired headset.

  This issue does not exist with 15.10. All updates have been installed
  on 16.04 including backports but they have not fixed the issue.

  It is not browser specific and not website specific.

  It is not hardware specific as it affects my laptop with an intel 7260
  card and my pc with an intel 8260 card.

  The issue exists on both ubuntu and kubuntu 16.04.

  I have reported it on the ubuntu support forums and after
  investigation a moderator noticed changed in the kernel from 4.4 and
  4.2 that may becausing the issue and asked me to file a bug report.

  The ubuntu forum thread can be found here.
  http://ubuntuforums.org/showthread.php?t=2326672

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-23-generic 4.4.0-23.41
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stephen1435 F pulseaudio
   /dev/snd/controlC0:  stephen1435 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jun  3 23:50:00 2016
  HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6
  InstallationDate: Installed on 2016-05-06 (28 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7978
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed 
root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago)
  dmi.bios.date: 05/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H170 GAMING M3 (MS-7978)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7978
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

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

[Touch-packages] [Bug 1098362] Re: DHCP settings for network manager shared connection are hard-coded source, should be editable

[Lucas Magasweran]

This has been fixed and merged upstream in nm-applet/network-manager
1.4.2.

https://bugzilla.gnome.org/show_bug.cgi?id=763937#c14

Ubuntu 17.04 has 1.4.4. Is it possible to backport this to 16.04 LTS?

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

Title:
  DHCP settings for network manager shared connection are hard-coded
  source, should be editable

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu 10.04, but it's in all versions.
  2) any version of network manager
  3) I want to be able to change the DHCP settings for a shared network 
connection
  4) YOUR OPERATING SYSTEM WON'T LET ME!

  The file nm-device.c contains this line:

  nm-device.c:guint32 start = (guint32) ntohl (0x0a2a2b01); /*
  10.42.43.1 */

  hard-coding DHCP settings that should obviously be editable by the
  user is a TERRIBLE IDEA.  PLEASE FIX.

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

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

[Touch-packages] [Bug 1719720] [NEW] [LTCTest][libvpd] Process '/bin/touch /run/run.vpdupdate' failed with exit code 127

[bugproxy]

Public bug reported:

---Problem Description---
Currently syslog is getting flooded with below log messages ..
Sep 25 03:16:41 ubuntu1710 systemd-udevd[2654]: Process '/bin/touch 
/run/run.vpdd
update' failed with exit code 127.

This is on UBuntu 17.10 latest build.. 
 
---uname output---
Linux ubuntu1710 4.12.0-11-generic #12-Ubuntu SMP Fri Aug 11 12:23:06 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
 
Machine Type = ZZ-L 
  
---Steps to Reproduce---
 I have seen these messages logged more often when we do any hotplug 
operations.. ex. cpu hotplug..

Ok. .this is the continuation of LTC #144627 / Launchpad #1682774.

As suggested in that bug, we did change udev script to create temporary
file under /run and that patch is available in ubuntu 17.10.

Looks like this is udev script issue. If I modify systemd-udevd like
below it works fine.

I've limited udev knowledge. I don't know if you have any other better
solution to this issue.

root@ltc-boston123:/lib/systemd/system# diff -Naurp  systemd-udevd.service.org 
systemd-udevd.service
--- systemd-udevd.service.org   2017-09-26 04:37:47.090057318 -0500
+++ systemd-udevd.service   2017-09-26 04:37:55.381739372 -0500
@@ -25,7 +25,7 @@ KillMode=mixed
 WatchdogSec=3min
 TasksMax=infinity
 MountFlags=slave
-MemoryDenyWriteExecute=yes
+#MemoryDenyWriteExecute=yes
 RestrictRealtime=yes
 RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6
 SystemCallArchitectures=native


-Vasant

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New


** Tags: architecture-ppc64le bugnameltc-159280 severity-medium 
targetmilestone-inin1710

** Tags added: architecture-ppc64le bugnameltc-159280 severity-medium
targetmilestone-inin1710

** Changed in: ubuntu
 Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage 
(ubuntu-power-triage)

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

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

Title:
  [LTCTest][libvpd] Process '/bin/touch /run/run.vpdupdate' failed with
  exit code 127

Status in systemd package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  Currently syslog is getting flooded with below log messages ..
  Sep 25 03:16:41 ubuntu1710 systemd-udevd[2654]: Process '/bin/touch 
/run/run.vpdd
  update' failed with exit code 127.

  This is on UBuntu 17.10 latest build.. 
   
  ---uname output---
  Linux ubuntu1710 4.12.0-11-generic #12-Ubuntu SMP Fri Aug 11 12:23:06 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = ZZ-L 

  ---Steps to Reproduce---
   I have seen these messages logged more often when we do any hotplug 
operations.. ex. cpu hotplug..

  Ok. .this is the continuation of LTC #144627 / Launchpad #1682774.

  As suggested in that bug, we did change udev script to create
  temporary file under /run and that patch is available in ubuntu 17.10.

  Looks like this is udev script issue. If I modify systemd-udevd like
  below it works fine.

  I've limited udev knowledge. I don't know if you have any other better
  solution to this issue.

  root@ltc-boston123:/lib/systemd/system# diff -Naurp  
systemd-udevd.service.org systemd-udevd.service
  --- systemd-udevd.service.org 2017-09-26 04:37:47.090057318 -0500
  +++ systemd-udevd.service 2017-09-26 04:37:55.381739372 -0500
  @@ -25,7 +25,7 @@ KillMode=mixed
   WatchdogSec=3min
   TasksMax=infinity
   MountFlags=slave
  -MemoryDenyWriteExecute=yes
  +#MemoryDenyWriteExecute=yes
   RestrictRealtime=yes
   RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6
   SystemCallArchitectures=native

  
  -Vasant

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

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

[Touch-packages] [Bug 1132736] Re: Xorg fails to start after installing the Hardware Enablement Stack due to missing symlink after purging old xserver-xorg

[Naël]

Sounds right. I just assumed that there wasn't any users of releases <
Trusty any more, as all those releases are EOL. But actually there may
still be, indeed.

Bug should stay Confirmed until Trusty itself is EOL.

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

Title:
  Xorg fails to start after installing the Hardware Enablement Stack due
  to missing symlink after purging old xserver-xorg

Status in xorg package in Ubuntu:
  Invalid
Status in xorg-lts-trusty package in Ubuntu:
  Confirmed
Status in xorg-lts-utopic package in Ubuntu:
  Won't Fix
Status in xorg-lts-vivid package in Ubuntu:
  Fix Released

Bug description:
  Bug:

  The bug happens whenever the remaining configuration files of the
  original X stack is removed, ie purging. It does not happen for users
  who do not explicitly remove those.

  Workaround:

  For example, if upgraded 14.04 LTS to the 14.04.2 HWE stack
  (=14.10/utopic):

  sudo dpkg-reconfigure xserver-xorg-lts-utopic

  This restores the symlink /etc/X11/X -> /usr/bin/Xorg

  ---

  After installing the hardware enablement stack on precise by running:
  sudo apt-get install linux-generic-lts-quantal xserver-xorg-lts-quantal

  Xorg fail to start. There is no error message or anything, just a black 
screen. Switching to a vt i possible and lightdm/x-0.log shows that a symlink 
is missing:
  X: cannot stat /etc/X11/X (No such file or directory), aborting.

  I updates two computers running precise x86_64 and both had the
  problem.

  Just recreating the symlink fixes the problem and then precise runs
  perfectly fine with the new stack (in fact, it's more stable so far).

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

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

[Touch-packages] [Bug 1719720] [NEW] [LTCTest][libvpd] Process '/bin/touch /run/run.vpdupdate' failed with exit code 127

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

---Problem Description---
Currently syslog is getting flooded with below log messages ..
Sep 25 03:16:41 ubuntu1710 systemd-udevd[2654]: Process '/bin/touch 
/run/run.vpdd
update' failed with exit code 127.

This is on UBuntu 17.10 latest build.. 
 
---uname output---
Linux ubuntu1710 4.12.0-11-generic #12-Ubuntu SMP Fri Aug 11 12:23:06 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
 
Machine Type = ZZ-L 
  
---Steps to Reproduce---
 I have seen these messages logged more often when we do any hotplug 
operations.. ex. cpu hotplug..

Ok. .this is the continuation of LTC #144627 / Launchpad #1682774.

As suggested in that bug, we did change udev script to create temporary
file under /run and that patch is available in ubuntu 17.10.

Looks like this is udev script issue. If I modify systemd-udevd like
below it works fine.

I've limited udev knowledge. I don't know if you have any other better
solution to this issue.

root@ltc-boston123:/lib/systemd/system# diff -Naurp  systemd-udevd.service.org 
systemd-udevd.service
--- systemd-udevd.service.org   2017-09-26 04:37:47.090057318 -0500
+++ systemd-udevd.service   2017-09-26 04:37:55.381739372 -0500
@@ -25,7 +25,7 @@ KillMode=mixed
 WatchdogSec=3min
 TasksMax=infinity
 MountFlags=slave
-MemoryDenyWriteExecute=yes
+#MemoryDenyWriteExecute=yes
 RestrictRealtime=yes
 RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6
 SystemCallArchitectures=native


-Vasant

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New


** Tags: architecture-ppc64le bugnameltc-159280 severity-medium 
targetmilestone-inin1710
-- 
[LTCTest][libvpd] Process '/bin/touch /run/run.vpdupdate' failed with exit code 
127
https://bugs.launchpad.net/bugs/1719720
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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

[Touch-packages] [Bug 1719630] Re: unattended-upgrades uses dpkg-vendor but doesn't depend on dpkg-dev

[Launchpad Bug Tracker]

This bug was fixed in the package unattended-upgrades - 0.97ubuntu2

---
unattended-upgrades (0.97ubuntu2) artful; urgency=medium

  * Use lsb_release instead of dpkg-vendor in postinst (LP: #1719630)

 -- Balint Reczey   Tue, 26 Sep 2017 10:21:42 -0400

** Changed in: unattended-upgrades (Ubuntu Artful)
   Status: In Progress => Fix Released

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

Title:
  unattended-upgrades uses dpkg-vendor but doesn't depend on dpkg-dev

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Artful:
  Fix Released

Bug description:
  in its postinst script unattended-upgrade uses dpkg-vendor from dpkg-
  dev but does not depends on dpkg-dev which results in the following
  error:

  
  # apt-get update && apt-get upgrade

  Installing the packages goes well, except for, getting this warning.

  Setting up unattended-upgrades (0.97ubuntu1) ...
  /var/lib/dpkg/info/unattended-upgrades.postinst: 65:
  /var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found
  /var/lib/dpkg/info/unattended-upgrades.postinst: 66:
  /var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found
  /var/lib/dpkg/info/unattended-upgrades.postinst: 124:
  /var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found
  /var/lib/dpkg/info/unattended-upgrades.postinst: 125:
  /var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: unattended-upgrades 0.97ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 26 10:01:05 2017
  InstallationDate: Installed on 2013-09-03 (1483 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apt.apt.conf.d.50unattended-upgrades: [modified]
  mtime.conffile..etc.apt.apt.conf.d.50unattended-upgrades: 
2017-09-05T01:34:04.573213

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

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

[Touch-packages] [Bug 1719579] Re: [Ubuntu 16.04.2] [libvirt] virsh restore fails from state file saved in /var/tmp folder using virsh save

[Seth Arnold]

Someone may have to actually describe what's going on...

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

Title:
  [Ubuntu 16.04.2] [libvirt] virsh restore fails from state file saved
  in /var/tmp folder using virsh save

Status in The Ubuntu-power-systems project:
  New
Status in apparmor package in Ubuntu:
  New

Bug description:
  == Comment: #1 - SEETEENA THOUFEEK  - 2017-01-17 
00:09:16 ==
  Bala, Please mail me the machine information.

  == Comment: #3 - SEETEENA THOUFEEK  - 2017-01-17 
02:14:06 ==
  2017-01-16 12:09:37.707+: 7024: info : 
virSecurityDACRestoreFileLabelInternal:388 : Restoring DAC user and group on 
'/var/tmp/bala'
  2017-01-16 12:09:37.707+: 7024: info : 
virSecurityDACSetOwnershipInternal:290 : Setting DAC user and group on 
'/var/tmp/bala' to '0:0'
  2017-01-16 12:09:37.707+: 7024: warning : qemuDomainSaveImageStartVM:6750 
: failed to restore save state label on /var/tmp/bala
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff4ca62b00
  2017-01-16 12:09:37.707+: 7024: debug : qemuDomainObjEndAsyncJob:1848 : 
Stopping async job: start (vm=0x3fff4ca535c0 name=virt-tests-vm1-bala)
  2017-01-16 12:09:37.707+: 7024: info : virObjectRef:296 : OBJECT_REF: 
obj=0x3fff4ca62b00
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff4ca62b00
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff4ca535c0
  2017-01-16 12:09:37.707+: 7024: debug : virThreadJobClear:121 : Thread 
7024 (virNetServerHandleJob) finished job remoteDispatchDomainRestore with 
ret=-1
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff7c002c10
  2017-01-16 12:09:37.707+: 7024: debug : virNetServerProgramSendError:153 
: prog=536903814 ver=1 proc=54 type=1 serial=4 msg=0x100133d2590 
rerr=0x3fffa59be3c0
  2017-01-16 12:09:37.707+: 7024: debug : virNetMessageEncodePayload:376 : 
Encode length as 172
  2017-01-16 12:09:37.707+: 7024: debug : 
virNetServerClientSendMessageLocked:1399 : msg=0x100133d2590 proc=54 len=172 
offset=0
  2017-01-16 12:09:37.707+: 7024: info : 
virNetServerClientSendMessageLocked:1407 : RPC_SERVER_CLIENT_MSG_TX_QUEUE: 
client=0x100133d23c0 len=172 prog=536903814 vers=1 proc=54 type=1 status=1 
serial=4
  2017-01-16 12:09:37.707+: 7024: debug : 
virNetServerClientCalculateHandleMode:157 : tls=(nil) hs=-1, rx=0x100133d0670 
tx=0x100133d2590
  2017-01-16 12:09:37.707+: 7024: debug : 
virNetServerClientCalculateHandleMode:192 : mode=3
  2017-01-16 12:09:37.707+: 7024: info : virEventPollUpdateHandle:152 : 
EVENT_POLL_UPDATE_HANDLE: watch=417 events=3
  2017-01-16 12:09:37.707+: 7024: debug : virEventPollInterruptLocked:727 : 
Interrupting
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff7c002c10
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x100133caea0
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x100133d23c0
  .
  2017-01-16 12:14:28.445+: 7019: info : qemuMonitorJSONIOProcessLine:201 : 
QEMU_MONITOR_RECV_EVENT: mon=0x3fff94004d90 event={"timestamp": {"seconds": 
1484568868, "microseconds": 444620}, "event": "MIGRATION", "data": {"status": 
"failed"}}
  2017-01-16 12:14:28.445+: 7019: debug : qemuMonitorJSONIOProcessEvent:147 
: mon=0x3fff94004d90 obj=0x100133b5670
  2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToString:1762 : 
object=0x100133a8000
  2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToStringOne:1691 : 
object=0x100133a8000 type=0 gen=0x100133d1160
  2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToStringOne:1691 : 
object=0x100133d2a80 type=2 gen=0x100133d1160
  2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToString:1795 : 
result={"status":"failed"}
  2017-01-16 12:14:28.445+: 7019: debug : qemuMonitorEmitEvent:1218 : 
mon=0x3fff94004d90 event=MIGRATION
  2017-01-16 12:14:28.445+: 7019: info : virObjectRef:296 : OBJECT_REF: 
obj=0x3fff94004d90
  2017-01-16 12:14:28.445+: 7019: debug : qemuProcessHandleEvent:629 : 
vm=0x3fff4ca535c0
  2017-01-16 12:14:28.445+: 7019: info : virObjectNew:202 : OBJECT_NEW: 
obj=0x100133d2870 classname=virDomainQemuMonitorEvent
  2017-01-16 12:14:28.445+: 7019: debug : virObjectEventNew:645 : 
obj=0x100133d2870
  2017-01-16 12:14:28.445+: 7019: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x100133d2870
  2017-01-16 12:14:28.445+: 7019: info : virObjectUnref:261 : 
OBJECT_DISPOSE: obj=0x100133d2870
  2017-01-16 12:14:28.445+: 7019: debug : 
virDomainQemuMonitorEventDispose:477 : obj=0x100133d2870
  2017-01-16 12:14:28.445+: 7019: debug : virObjectEventDispose:121 : 

[Touch-packages] [Bug 1679220] Re: Installer pulls packages from other releases in the pool

[Phillip Susi]

To install the system in the first place of course.

Normally the installer iso contains a /pool directory with a single
release directory, but if someone later uses the usb creator to extract
another iso for another release, they end up with a /pool directory with
two different release directories under it, and apt searches both
releases for packages to install causing all sorts of problems.

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

Title:
  Installer pulls packages from other releases in the pool

Status in apt package in Ubuntu:
  New

Bug description:
  Frequently people reuse a USB stick to install another release, and
  the install fails because apt tries to pull packages from the wrong
  release.  Apt should only be looking in the pool for the current
  release rather than everything it can find.

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

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

[Touch-packages] [Bug 1719630] Re: unattended-upgrades uses dpkg-vendor but doesn't depend on dpkg-dev

[Balint Reczey]

** Tags removed: block-proposed

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

Title:
  unattended-upgrades uses dpkg-vendor but doesn't depend on dpkg-dev

Status in unattended-upgrades package in Ubuntu:
  In Progress
Status in unattended-upgrades source package in Artful:
  In Progress

Bug description:
  in its postinst script unattended-upgrade uses dpkg-vendor from dpkg-
  dev but does not depends on dpkg-dev which results in the following
  error:

  
  # apt-get update && apt-get upgrade

  Installing the packages goes well, except for, getting this warning.

  Setting up unattended-upgrades (0.97ubuntu1) ...
  /var/lib/dpkg/info/unattended-upgrades.postinst: 65:
  /var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found
  /var/lib/dpkg/info/unattended-upgrades.postinst: 66:
  /var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found
  /var/lib/dpkg/info/unattended-upgrades.postinst: 124:
  /var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found
  /var/lib/dpkg/info/unattended-upgrades.postinst: 125:
  /var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: unattended-upgrades 0.97ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 26 10:01:05 2017
  InstallationDate: Installed on 2013-09-03 (1483 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apt.apt.conf.d.50unattended-upgrades: [modified]
  mtime.conffile..etc.apt.apt.conf.d.50unattended-upgrades: 
2017-09-05T01:34:04.573213

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

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

[Touch-packages] [Bug 1711048] Re: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: le paquet bsdutils n'est pas prêt pour la configuration configuration impossible (état actuel « half-ins

[Phillip Susi]

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

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

Title:
  package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: le paquet
  bsdutils n'est pas prêt pour la configuration  configuration
  impossible (état actuel « half-installed »)

Status in dpkg package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  ce bug est signalé au démarrage

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: bsdutils 1:2.29-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  AptOrdering:
   bsdutils:amd64: Configure
   libgd3:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Aug 16 08:04:58 2017
  DpkgTerminalLog:
   dpkg: erreur de traitement du paquet bsdutils (--configure) :
le paquet bsdutils n'est pas prêt pour la configuration
configuration impossible (état actuel « half-installed »)
  ErrorMessage: le paquet bsdutils n'est pas prêt pour la configuration  
configuration impossible (état actuel « half-installed »)
  InstallationDate: Installed on 2017-03-19 (149 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: util-linux
  Title: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: le paquet 
bsdutils n'est pas prêt pour la configuration  configuration impossible (état 
actuel « half-installed »)
  UpgradeStatus: Upgraded to zesty on 2017-05-03 (104 days ago)

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

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

[Touch-packages] [Bug 1710694] Re: package util-linux 2.29-1ubuntu2 failed to install/upgrade: Paket util-linux ist nicht bereit zur Konfiguration kann nicht konfiguriert werden (momentaner Status »h

[Phillip Susi]

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

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

Title:
  package util-linux 2.29-1ubuntu2 failed to install/upgrade: Paket
  util-linux ist nicht bereit zur Konfiguration  kann nicht konfiguriert
  werden (momentaner Status »half-installed«)

Status in dpkg package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  package util-linux 2.29-1ubuntu2 failed to install/upgrade: Paket
  util-linux ist nicht bereit zur Konfiguration  kann nicht konfiguriert
  werden (momentaner Status »half-installed«)

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: util-linux 2.29-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Sat Aug 12 13:41:53 2017
  DpkgTerminalLog:
   dpkg: Fehler beim Bearbeiten des Paketes util-linux (--configure):
Paket util-linux ist nicht bereit zur Konfiguration
kann nicht konfiguriert werden (momentaner Status »half-installed«)
  ErrorMessage: Paket util-linux ist nicht bereit zur Konfiguration  kann nicht 
konfiguriert werden (momentaner Status »half-installed«)
  InstallationDate: Installed on 2017-05-13 (93 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: util-linux
  Title: package util-linux 2.29-1ubuntu2 failed to install/upgrade: Paket 
util-linux ist nicht bereit zur Konfiguration  kann nicht konfiguriert werden 
(momentaner 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/dpkg/+bug/1710694/+subscriptions

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

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

[Mathieu Trudel-Lapierre]

** Description changed:

+ [Impact]
+ Hosts may require a specific MTU to be set as passed by DHCP options. We 
should honor these settings to ensure proper communication of the host with the 
rest of the network.
+ 
+ [Test case]
+ 1) Run netplan on a system that should receive MTU settings from DHCP.
+ 2) Validate that the MTU configuration provided by DHCP is applied to the 
right interface.
+ 
+ [Regression Potential]
+ If DHCP settings specify an invalid MTU setting which is currently being 
ignored and letting the systems communicate correctly with the network, then 
these systems would regress.
+ 
+ ---
+ 
   Right, so as far as I can tell the neutron-api on lcy01 is
  configured to advertise an instance interface MTU of 1400, though that's
  lower than it has to be, and the new DHCP setup with networkd just
  doesn't respect that DHCP option.

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

Title:
  networkd does not accept / set advertised mtu

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

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

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

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

  ---

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

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

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

[Touch-packages] [Bug 1676547] Re: No network connectivity after upgrade from 16.04 to 16.10

[Launchpad Bug Tracker]

This bug was fixed in the package network-manager - 1.4.4-1ubuntu3.2

---
network-manager (1.4.4-1ubuntu3.2) zesty; urgency=medium

  * debian/network-manager.postinst: drop in an empty override file for
NetworkManager to manage all devices for upgrade from any version, as long
as there is no netplan configuration yet. (LP: #1676547)

 -- Brian Murray   Fri, 08 Sep 2017 11:29:32 -0700

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

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

Title:
  No network connectivity after upgrade from 16.04 to 16.10

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Yakkety:
  Fix Released
Status in network-manager source package in Zesty:
  Fix Released

Bug description:
  Impact
  --
  When upgrading from Xenial (with all updates installed) to Yakkety/Zesty you 
will boot to a system without networking - sad!

  Test Case
  -
  1) Boot a xenial desktop system
  2) Ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is 
installed
  3) Upgrade to yakkety or zesty
  3.5) Enable -proposed and download the new version of n-m "apt-get download 
network-manager"
  4) Reboot
  5) Observe you have no network

  If you install the version of network-manager from yakkety-proposed
  and then reboot you should have a network connection.

  1) Boot a xenial desktop system.
  2) ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is 
installed.
  3) Install nplan, configure to set up static network on an ethernet device 
using nplan.
  4) Upgrade to yakkety or zesty
  5) Reboot
  6) Observe that your system is still being managed by networkd rather than 
NetworkManager.

  Regression Potential
  

  Any failure to manage ethernet or wireless devices after upgrade, or
  issues with the use of netplan in conjunction with NetworkManager
  should be investigated as potential regressions. For example, if after
  upgrading, ethernet devices are no longer managed, or if devices that
  should be explicitly ignored by NetworkManager due to existing user
  configuration are now managed, these would indicate a possible
  regression caused by this update.

  Original Description
  

  nplan was installed during the upgrade process but I had no network
  connectivity after upgrading. Apparently, no package wanted to manage
  my ethernet connection.

  ProblemType: BugDistroRelease: Ubuntu 16.10
  Package: ubuntu-release-upgrader-core 1:16.10.10
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Mon Mar 27 11:34:04 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-16 (1531 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
  PackageArchitecture: allSourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to yakkety on 2017-03-17 (10 days ago)
  VarLogDistupgradeTermlog:

  modified.conffile..etc.update-manager.meta-release: [modified]
  mtime.conffile..etc.update-manager.meta-release: 2013-10-08T06:39:09.818913

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

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

[Touch-packages] [Bug 1678187] Re: Removing a linux-image-extra package fails, if /boot is about full

[Brian Murray]

** Changed in: initramfs-tools (Ubuntu)
   Status: Incomplete => 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/1678187

Title:
  Removing a linux-image-extra package fails, if /boot is about full

Status in initramfs-tools:
  New
Status in dpkg package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  System calls /etc/kernel/postinst.d/initramfs-tools when
  purging/removing a linux-image-extra package. That calls "update-
  initramfs -c" which needs significant amount of additional disk space
  in /boot temporarily. But there is no space left, if /boot is full.

  Likewise /etc/kernel/postinst.d/dkms may call "update-initramfs -u".

  The fix could be to create the new initrg.img file in different partition 
before replacing the old one by it in update-initramfs. So the update-initramfs 
script should be fixed. But there may not be such a partition..
  Anyway the likely case when space runs out is when there is a separate /boot 
partition.

  Alternatively the init scripts should remove the respective 
/boot/initrd.img- file when removing/installing the linux-image-extra 
package. That could also be done by
  update-initramfs -d -k 
  That may be worse way, as then initrd.img file is missing for longer period 
of time and system integrity may suffer in case of e.g. power cut.

  Related question: http://askubuntu.com/q/898499/21005
  The output of 'dpkg --purge' presented there shows that corresponding 
linux-image package may get successfully removed while the linux-image-extra is 
left broken. If the linux-image-extra package will be removed later, the 
post-installation script will create an initrd.img file for a non-installed 
kernel! Same would happen, if removing would be done by apt-get purge.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: initramfs-tools 0.103ubuntu4.7
  ProcVersionSignature: Ubuntu 4.4.0-71.92~14.04.1-generic 4.4.49
  Uname: Linux 4.4.0-71-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 31 17:42:35 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-21 (922 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.1)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1719579] Re: [Ubuntu 16.04.2] [libvirt] virsh restore fails from state file saved in /var/tmp folder using virsh save

[Frank Heimes]

** Changed in: ubuntu-power-systems
 Assignee: Canonical Server Team (canonical-server) => John Johansen 
(jjohansen)

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

Title:
  [Ubuntu 16.04.2] [libvirt] virsh restore fails from state file saved
  in /var/tmp folder using virsh save

Status in The Ubuntu-power-systems project:
  New
Status in apparmor package in Ubuntu:
  New

Bug description:
  == Comment: #1 - SEETEENA THOUFEEK  - 2017-01-17 
00:09:16 ==
  Bala, Please mail me the machine information.

  == Comment: #3 - SEETEENA THOUFEEK  - 2017-01-17 
02:14:06 ==
  2017-01-16 12:09:37.707+: 7024: info : 
virSecurityDACRestoreFileLabelInternal:388 : Restoring DAC user and group on 
'/var/tmp/bala'
  2017-01-16 12:09:37.707+: 7024: info : 
virSecurityDACSetOwnershipInternal:290 : Setting DAC user and group on 
'/var/tmp/bala' to '0:0'
  2017-01-16 12:09:37.707+: 7024: warning : qemuDomainSaveImageStartVM:6750 
: failed to restore save state label on /var/tmp/bala
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff4ca62b00
  2017-01-16 12:09:37.707+: 7024: debug : qemuDomainObjEndAsyncJob:1848 : 
Stopping async job: start (vm=0x3fff4ca535c0 name=virt-tests-vm1-bala)
  2017-01-16 12:09:37.707+: 7024: info : virObjectRef:296 : OBJECT_REF: 
obj=0x3fff4ca62b00
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff4ca62b00
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff4ca535c0
  2017-01-16 12:09:37.707+: 7024: debug : virThreadJobClear:121 : Thread 
7024 (virNetServerHandleJob) finished job remoteDispatchDomainRestore with 
ret=-1
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff7c002c10
  2017-01-16 12:09:37.707+: 7024: debug : virNetServerProgramSendError:153 
: prog=536903814 ver=1 proc=54 type=1 serial=4 msg=0x100133d2590 
rerr=0x3fffa59be3c0
  2017-01-16 12:09:37.707+: 7024: debug : virNetMessageEncodePayload:376 : 
Encode length as 172
  2017-01-16 12:09:37.707+: 7024: debug : 
virNetServerClientSendMessageLocked:1399 : msg=0x100133d2590 proc=54 len=172 
offset=0
  2017-01-16 12:09:37.707+: 7024: info : 
virNetServerClientSendMessageLocked:1407 : RPC_SERVER_CLIENT_MSG_TX_QUEUE: 
client=0x100133d23c0 len=172 prog=536903814 vers=1 proc=54 type=1 status=1 
serial=4
  2017-01-16 12:09:37.707+: 7024: debug : 
virNetServerClientCalculateHandleMode:157 : tls=(nil) hs=-1, rx=0x100133d0670 
tx=0x100133d2590
  2017-01-16 12:09:37.707+: 7024: debug : 
virNetServerClientCalculateHandleMode:192 : mode=3
  2017-01-16 12:09:37.707+: 7024: info : virEventPollUpdateHandle:152 : 
EVENT_POLL_UPDATE_HANDLE: watch=417 events=3
  2017-01-16 12:09:37.707+: 7024: debug : virEventPollInterruptLocked:727 : 
Interrupting
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff7c002c10
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x100133caea0
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x100133d23c0
  .
  2017-01-16 12:14:28.445+: 7019: info : qemuMonitorJSONIOProcessLine:201 : 
QEMU_MONITOR_RECV_EVENT: mon=0x3fff94004d90 event={"timestamp": {"seconds": 
1484568868, "microseconds": 444620}, "event": "MIGRATION", "data": {"status": 
"failed"}}
  2017-01-16 12:14:28.445+: 7019: debug : qemuMonitorJSONIOProcessEvent:147 
: mon=0x3fff94004d90 obj=0x100133b5670
  2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToString:1762 : 
object=0x100133a8000
  2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToStringOne:1691 : 
object=0x100133a8000 type=0 gen=0x100133d1160
  2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToStringOne:1691 : 
object=0x100133d2a80 type=2 gen=0x100133d1160
  2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToString:1795 : 
result={"status":"failed"}
  2017-01-16 12:14:28.445+: 7019: debug : qemuMonitorEmitEvent:1218 : 
mon=0x3fff94004d90 event=MIGRATION
  2017-01-16 12:14:28.445+: 7019: info : virObjectRef:296 : OBJECT_REF: 
obj=0x3fff94004d90
  2017-01-16 12:14:28.445+: 7019: debug : qemuProcessHandleEvent:629 : 
vm=0x3fff4ca535c0
  2017-01-16 12:14:28.445+: 7019: info : virObjectNew:202 : OBJECT_NEW: 
obj=0x100133d2870 classname=virDomainQemuMonitorEvent
  2017-01-16 12:14:28.445+: 7019: debug : virObjectEventNew:645 : 
obj=0x100133d2870
  2017-01-16 12:14:28.445+: 7019: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x100133d2870
  2017-01-16 12:14:28.445+: 7019: info : virObjectUnref:261 : 
OBJECT_DISPOSE: obj=0x100133d2870
  2017-01-16 12:14:28.445+: 7019: debug : 
virDomainQemuMonitorEventDispose:477 : obj=0x100133d2870
  2017-01-16 

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

[Mathieu Trudel-Lapierre]

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

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

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

Title:
  networkd does not accept / set advertised mtu

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

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

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

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

[Touch-packages] [Bug 1678187] Re: Removing a linux-image-extra package fails, if /boot is about full

[Jarno Suni]

Then not incomplete anymore?

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

Title:
  Removing a linux-image-extra package fails, if /boot is about full

Status in initramfs-tools:
  New
Status in dpkg package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  System calls /etc/kernel/postinst.d/initramfs-tools when
  purging/removing a linux-image-extra package. That calls "update-
  initramfs -c" which needs significant amount of additional disk space
  in /boot temporarily. But there is no space left, if /boot is full.

  Likewise /etc/kernel/postinst.d/dkms may call "update-initramfs -u".

  The fix could be to create the new initrg.img file in different partition 
before replacing the old one by it in update-initramfs. So the update-initramfs 
script should be fixed. But there may not be such a partition..
  Anyway the likely case when space runs out is when there is a separate /boot 
partition.

  Alternatively the init scripts should remove the respective 
/boot/initrd.img- file when removing/installing the linux-image-extra 
package. That could also be done by
  update-initramfs -d -k 
  That may be worse way, as then initrd.img file is missing for longer period 
of time and system integrity may suffer in case of e.g. power cut.

  Related question: http://askubuntu.com/q/898499/21005
  The output of 'dpkg --purge' presented there shows that corresponding 
linux-image package may get successfully removed while the linux-image-extra is 
left broken. If the linux-image-extra package will be removed later, the 
post-installation script will create an initrd.img file for a non-installed 
kernel! Same would happen, if removing would be done by apt-get purge.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: initramfs-tools 0.103ubuntu4.7
  ProcVersionSignature: Ubuntu 4.4.0-71.92~14.04.1-generic 4.4.49
  Uname: Linux 4.4.0-71-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 31 17:42:35 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-21 (922 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.1)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1678187] Re: Removing a linux-image-extra package fails, if /boot is about full

[Brian Murray]

I've recreated this on Ubuntu 16.04 now, it seems that the missing bit
was creating a sufficiently small enough amount of free space on my
/boot partition.

While running 'sudo apt install' did finish the removal and I was able
to continue using apt, I did notice that I had a leftover / abandoned
initrd.img-4.4.0-31-generic.

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

Title:
  Removing a linux-image-extra package fails, if /boot is about full

Status in initramfs-tools:
  New
Status in dpkg package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  System calls /etc/kernel/postinst.d/initramfs-tools when
  purging/removing a linux-image-extra package. That calls "update-
  initramfs -c" which needs significant amount of additional disk space
  in /boot temporarily. But there is no space left, if /boot is full.

  Likewise /etc/kernel/postinst.d/dkms may call "update-initramfs -u".

  The fix could be to create the new initrg.img file in different partition 
before replacing the old one by it in update-initramfs. So the update-initramfs 
script should be fixed. But there may not be such a partition..
  Anyway the likely case when space runs out is when there is a separate /boot 
partition.

  Alternatively the init scripts should remove the respective 
/boot/initrd.img- file when removing/installing the linux-image-extra 
package. That could also be done by
  update-initramfs -d -k 
  That may be worse way, as then initrd.img file is missing for longer period 
of time and system integrity may suffer in case of e.g. power cut.

  Related question: http://askubuntu.com/q/898499/21005
  The output of 'dpkg --purge' presented there shows that corresponding 
linux-image package may get successfully removed while the linux-image-extra is 
left broken. If the linux-image-extra package will be removed later, the 
post-installation script will create an initrd.img file for a non-installed 
kernel! Same would happen, if removing would be done by apt-get purge.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: initramfs-tools 0.103ubuntu4.7
  ProcVersionSignature: Ubuntu 4.4.0-71.92~14.04.1-generic 4.4.49
  Uname: Linux 4.4.0-71-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 31 17:42:35 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-21 (922 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.1)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1132736] Re: Xorg fails to start after installing the Hardware Enablement Stack due to missing symlink after purging old xserver-xorg

[Robie Basak]

> 13:47  Hi guys, anybody from Bug Control here can please switch
bug 1132736 xorg-lts-trusty from Confirmed to Won't Fix? Please see last
comment for rationale. Thanks!

Users may still want to upgrade from an EOL release to a supported
release though. Surely we should encourage this!

I think the bug sounds valid for Trusty still and an SRU to Trusty
shouldn't be rejected on this basis if someone wants to contribute one.
Won't Fix generally implies that we'd reject a fix even if were
contributed, and I don't think that's the case here.

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

Title:
  Xorg fails to start after installing the Hardware Enablement Stack due
  to missing symlink after purging old xserver-xorg

Status in xorg package in Ubuntu:
  Invalid
Status in xorg-lts-trusty package in Ubuntu:
  Confirmed
Status in xorg-lts-utopic package in Ubuntu:
  Won't Fix
Status in xorg-lts-vivid package in Ubuntu:
  Fix Released

Bug description:
  Bug:

  The bug happens whenever the remaining configuration files of the
  original X stack is removed, ie purging. It does not happen for users
  who do not explicitly remove those.

  Workaround:

  For example, if upgraded 14.04 LTS to the 14.04.2 HWE stack
  (=14.10/utopic):

  sudo dpkg-reconfigure xserver-xorg-lts-utopic

  This restores the symlink /etc/X11/X -> /usr/bin/Xorg

  ---

  After installing the hardware enablement stack on precise by running:
  sudo apt-get install linux-generic-lts-quantal xserver-xorg-lts-quantal

  Xorg fail to start. There is no error message or anything, just a black 
screen. Switching to a vt i possible and lightdm/x-0.log shows that a symlink 
is missing:
  X: cannot stat /etc/X11/X (No such file or directory), aborting.

  I updates two computers running precise x86_64 and both had the
  problem.

  Just recreating the symlink fixes the problem and then precise runs
  perfectly fine with the new stack (in fact, it's more stable so far).

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

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

[Touch-packages] [Bug 1719630] Re: unattended-upgrades uses dpkg-vendor but doesn't depend on dpkg-dev

[Łukasz Zemczak]

** Tags added: block-proposed

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

Title:
  unattended-upgrades uses dpkg-vendor but doesn't depend on dpkg-dev

Status in unattended-upgrades package in Ubuntu:
  In Progress
Status in unattended-upgrades source package in Artful:
  In Progress

Bug description:
  in its postinst script unattended-upgrade uses dpkg-vendor from dpkg-
  dev but does not depends on dpkg-dev which results in the following
  error:

  
  # apt-get update && apt-get upgrade

  Installing the packages goes well, except for, getting this warning.

  Setting up unattended-upgrades (0.97ubuntu1) ...
  /var/lib/dpkg/info/unattended-upgrades.postinst: 65:
  /var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found
  /var/lib/dpkg/info/unattended-upgrades.postinst: 66:
  /var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found
  /var/lib/dpkg/info/unattended-upgrades.postinst: 124:
  /var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found
  /var/lib/dpkg/info/unattended-upgrades.postinst: 125:
  /var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: unattended-upgrades 0.97ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 26 10:01:05 2017
  InstallationDate: Installed on 2013-09-03 (1483 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apt.apt.conf.d.50unattended-upgrades: [modified]
  mtime.conffile..etc.apt.apt.conf.d.50unattended-upgrades: 
2017-09-05T01:34:04.573213

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

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

[Touch-packages] [Bug 1718771] Re: Incorrect handling of link-local IPv6 DNS servers

[Dimitri John Ledkov]

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

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

Title:
  Incorrect handling of link-local IPv6 DNS servers

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Artful:
  Confirmed

Bug description:
  We've recently seen odd looking DNS failures on autopkgtest:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/amd64/d/docker.io/20170921_065231_181b8@/log.gz

  This shows a fe80:: link-local IPv6 address as one of the DNS servers
  on the interface. That's because dnsmasq includes both the link-local
  and global addresses of its DNS server in the router advertisement.

  systemd-networkd appears to pick that up and send it to resolved,
  which includes it in its config but apparently doesn't know how to
  actually query it, leading to the failure above.

  
  This is racy because once DHCPv4 completes, the resolved config will then 
work properly again.

  
  I've confirmed that dnsmasq properly answers on all addresses:
http://paste.ubuntu.com/25588197/

  
  I've uploaded a workaround for this issue as part of the docker.io package.

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

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

[Touch-packages] [Bug 1719302] Re: Please include mlx4 and mlx5 InfiniBand modules

[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/1719302

Title:
  Please include mlx4 and mlx5 InfiniBand modules

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

Bug description:
  Mellanox ConnectX architecture is:  mlx4_core is the lower level PCI
  driver which register on the PCI id, and protocol specific drivers are
  depended on it: mlx4_en - for Ethernet and mlx4_ib for Infiniband. NIC
  could have multiple ports which can change their type dynamically. We
  use the request_module() call to load the relevant protocol driver
  when needed: on loading time or at port type change event.

  The mlx4_core and mlx5_core modules are included in the initrd, but
  not mlx4_ib and mlx5_ib. Thus the request_module() call will not find
  these modules and fail load them. The mlx*_ib module loading will not
  be retried.

  Therefore also include mlx4_ib and mlx5_ib in the initrd to make
  autoloading them work. A patch is attached to the related Debian bug
  report.

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

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

[Touch-packages] [Bug 1718444] Re: systemd-sysctl in Xenial is not obeying the order of the sysctls

[Brian Murray]

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

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

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

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

Title:
  systemd-sysctl in Xenial is not obeying the order of the sysctls

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

Bug description:
  systemd-sysctl in Xenial forces itself over procps by shipping a link
  for procps.service to systemd-sysctl.service. However, it does not
  obey the order both of the files and also of the sysctls within the
  files. Instead it uses a simple hashmap. As it turns out that's fixed
  upstream and systemd master uses an ordered hashmap because of this,
  which at least preserves order within single files. Traditionally
  files in sysctl.d have been prefixed with numbers to ensure an order
  and that's now completely non-deterministic on Xenial.

  Relevant upstream commit:
  
https://github.com/systemd/systemd/commit/886cf982d3018f7451f0548dadbc05bd2d583bb6

  Note that conf_files_list_nulstr in master sorts the configuration
  files using strcmp, so even order of configuration files should be
  obeyed.

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

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

[Touch-packages] [Bug 1719630] Re: unattended-upgrades uses dpkg-vendor but doesn't depend on dpkg-dev

[Brian Murray]

** Also affects: unattended-upgrades (Ubuntu Artful)
   Importance: High
   Status: In Progress

** Tags removed: rls-aa-incoming

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

Title:
  unattended-upgrades uses dpkg-vendor but doesn't depend on dpkg-dev

Status in unattended-upgrades package in Ubuntu:
  In Progress
Status in unattended-upgrades source package in Artful:
  In Progress

Bug description:
  in its postinst script unattended-upgrade uses dpkg-vendor from dpkg-
  dev but does not depends on dpkg-dev which results in the following
  error:

  
  # apt-get update && apt-get upgrade

  Installing the packages goes well, except for, getting this warning.

  Setting up unattended-upgrades (0.97ubuntu1) ...
  /var/lib/dpkg/info/unattended-upgrades.postinst: 65:
  /var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found
  /var/lib/dpkg/info/unattended-upgrades.postinst: 66:
  /var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found
  /var/lib/dpkg/info/unattended-upgrades.postinst: 124:
  /var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found
  /var/lib/dpkg/info/unattended-upgrades.postinst: 125:
  /var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: unattended-upgrades 0.97ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 26 10:01:05 2017
  InstallationDate: Installed on 2013-09-03 (1483 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apt.apt.conf.d.50unattended-upgrades: [modified]
  mtime.conffile..etc.apt.apt.conf.d.50unattended-upgrades: 
2017-09-05T01:34:04.573213

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

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

[Touch-packages] [Bug 1719579] Re: [Ubuntu 16.04.2] [libvirt] virsh restore fails from state file saved in /var/tmp folder using virsh save

[ChristianEhrhardt]

@Frank I- I'm not allowed to change this, could you please re-assign.

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

Title:
  [Ubuntu 16.04.2] [libvirt] virsh restore fails from state file saved
  in /var/tmp folder using virsh save

Status in The Ubuntu-power-systems project:
  New
Status in apparmor package in Ubuntu:
  New

Bug description:
  == Comment: #1 - SEETEENA THOUFEEK  - 2017-01-17 
00:09:16 ==
  Bala, Please mail me the machine information.

  == Comment: #3 - SEETEENA THOUFEEK  - 2017-01-17 
02:14:06 ==
  2017-01-16 12:09:37.707+: 7024: info : 
virSecurityDACRestoreFileLabelInternal:388 : Restoring DAC user and group on 
'/var/tmp/bala'
  2017-01-16 12:09:37.707+: 7024: info : 
virSecurityDACSetOwnershipInternal:290 : Setting DAC user and group on 
'/var/tmp/bala' to '0:0'
  2017-01-16 12:09:37.707+: 7024: warning : qemuDomainSaveImageStartVM:6750 
: failed to restore save state label on /var/tmp/bala
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff4ca62b00
  2017-01-16 12:09:37.707+: 7024: debug : qemuDomainObjEndAsyncJob:1848 : 
Stopping async job: start (vm=0x3fff4ca535c0 name=virt-tests-vm1-bala)
  2017-01-16 12:09:37.707+: 7024: info : virObjectRef:296 : OBJECT_REF: 
obj=0x3fff4ca62b00
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff4ca62b00
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff4ca535c0
  2017-01-16 12:09:37.707+: 7024: debug : virThreadJobClear:121 : Thread 
7024 (virNetServerHandleJob) finished job remoteDispatchDomainRestore with 
ret=-1
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff7c002c10
  2017-01-16 12:09:37.707+: 7024: debug : virNetServerProgramSendError:153 
: prog=536903814 ver=1 proc=54 type=1 serial=4 msg=0x100133d2590 
rerr=0x3fffa59be3c0
  2017-01-16 12:09:37.707+: 7024: debug : virNetMessageEncodePayload:376 : 
Encode length as 172
  2017-01-16 12:09:37.707+: 7024: debug : 
virNetServerClientSendMessageLocked:1399 : msg=0x100133d2590 proc=54 len=172 
offset=0
  2017-01-16 12:09:37.707+: 7024: info : 
virNetServerClientSendMessageLocked:1407 : RPC_SERVER_CLIENT_MSG_TX_QUEUE: 
client=0x100133d23c0 len=172 prog=536903814 vers=1 proc=54 type=1 status=1 
serial=4
  2017-01-16 12:09:37.707+: 7024: debug : 
virNetServerClientCalculateHandleMode:157 : tls=(nil) hs=-1, rx=0x100133d0670 
tx=0x100133d2590
  2017-01-16 12:09:37.707+: 7024: debug : 
virNetServerClientCalculateHandleMode:192 : mode=3
  2017-01-16 12:09:37.707+: 7024: info : virEventPollUpdateHandle:152 : 
EVENT_POLL_UPDATE_HANDLE: watch=417 events=3
  2017-01-16 12:09:37.707+: 7024: debug : virEventPollInterruptLocked:727 : 
Interrupting
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff7c002c10
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x100133caea0
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x100133d23c0
  .
  2017-01-16 12:14:28.445+: 7019: info : qemuMonitorJSONIOProcessLine:201 : 
QEMU_MONITOR_RECV_EVENT: mon=0x3fff94004d90 event={"timestamp": {"seconds": 
1484568868, "microseconds": 444620}, "event": "MIGRATION", "data": {"status": 
"failed"}}
  2017-01-16 12:14:28.445+: 7019: debug : qemuMonitorJSONIOProcessEvent:147 
: mon=0x3fff94004d90 obj=0x100133b5670
  2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToString:1762 : 
object=0x100133a8000
  2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToStringOne:1691 : 
object=0x100133a8000 type=0 gen=0x100133d1160
  2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToStringOne:1691 : 
object=0x100133d2a80 type=2 gen=0x100133d1160
  2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToString:1795 : 
result={"status":"failed"}
  2017-01-16 12:14:28.445+: 7019: debug : qemuMonitorEmitEvent:1218 : 
mon=0x3fff94004d90 event=MIGRATION
  2017-01-16 12:14:28.445+: 7019: info : virObjectRef:296 : OBJECT_REF: 
obj=0x3fff94004d90
  2017-01-16 12:14:28.445+: 7019: debug : qemuProcessHandleEvent:629 : 
vm=0x3fff4ca535c0
  2017-01-16 12:14:28.445+: 7019: info : virObjectNew:202 : OBJECT_NEW: 
obj=0x100133d2870 classname=virDomainQemuMonitorEvent
  2017-01-16 12:14:28.445+: 7019: debug : virObjectEventNew:645 : 
obj=0x100133d2870
  2017-01-16 12:14:28.445+: 7019: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x100133d2870
  2017-01-16 12:14:28.445+: 7019: info : virObjectUnref:261 : 
OBJECT_DISPOSE: obj=0x100133d2870
  2017-01-16 12:14:28.445+: 7019: debug : 
virDomainQemuMonitorEventDispose:477 : obj=0x100133d2870
  2017-01-16 12:14:28.445+: 7019: debug : 

[Touch-packages] [Bug 1719579] Re: [Ubuntu 16.04.2] [libvirt] virsh restore fails from state file saved in /var/tmp folder using virsh save

[ChristianEhrhardt]

I like "this is an apparmor issue and there is no libvirt bug here" :-)
But if so - or even if not - please provide the dmesg with the related apparmor 
denies so that we can sort out what happens.

Assuming it is apparmor as reported assigning john johanssen instead of
me, but I subscribe myself it it comes back to libvirt to fix it.

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

Title:
  [Ubuntu 16.04.2] [libvirt] virsh restore fails from state file saved
  in /var/tmp folder using virsh save

Status in The Ubuntu-power-systems project:
  New
Status in apparmor package in Ubuntu:
  New

Bug description:
  == Comment: #1 - SEETEENA THOUFEEK  - 2017-01-17 
00:09:16 ==
  Bala, Please mail me the machine information.

  == Comment: #3 - SEETEENA THOUFEEK  - 2017-01-17 
02:14:06 ==
  2017-01-16 12:09:37.707+: 7024: info : 
virSecurityDACRestoreFileLabelInternal:388 : Restoring DAC user and group on 
'/var/tmp/bala'
  2017-01-16 12:09:37.707+: 7024: info : 
virSecurityDACSetOwnershipInternal:290 : Setting DAC user and group on 
'/var/tmp/bala' to '0:0'
  2017-01-16 12:09:37.707+: 7024: warning : qemuDomainSaveImageStartVM:6750 
: failed to restore save state label on /var/tmp/bala
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff4ca62b00
  2017-01-16 12:09:37.707+: 7024: debug : qemuDomainObjEndAsyncJob:1848 : 
Stopping async job: start (vm=0x3fff4ca535c0 name=virt-tests-vm1-bala)
  2017-01-16 12:09:37.707+: 7024: info : virObjectRef:296 : OBJECT_REF: 
obj=0x3fff4ca62b00
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff4ca62b00
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff4ca535c0
  2017-01-16 12:09:37.707+: 7024: debug : virThreadJobClear:121 : Thread 
7024 (virNetServerHandleJob) finished job remoteDispatchDomainRestore with 
ret=-1
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff7c002c10
  2017-01-16 12:09:37.707+: 7024: debug : virNetServerProgramSendError:153 
: prog=536903814 ver=1 proc=54 type=1 serial=4 msg=0x100133d2590 
rerr=0x3fffa59be3c0
  2017-01-16 12:09:37.707+: 7024: debug : virNetMessageEncodePayload:376 : 
Encode length as 172
  2017-01-16 12:09:37.707+: 7024: debug : 
virNetServerClientSendMessageLocked:1399 : msg=0x100133d2590 proc=54 len=172 
offset=0
  2017-01-16 12:09:37.707+: 7024: info : 
virNetServerClientSendMessageLocked:1407 : RPC_SERVER_CLIENT_MSG_TX_QUEUE: 
client=0x100133d23c0 len=172 prog=536903814 vers=1 proc=54 type=1 status=1 
serial=4
  2017-01-16 12:09:37.707+: 7024: debug : 
virNetServerClientCalculateHandleMode:157 : tls=(nil) hs=-1, rx=0x100133d0670 
tx=0x100133d2590
  2017-01-16 12:09:37.707+: 7024: debug : 
virNetServerClientCalculateHandleMode:192 : mode=3
  2017-01-16 12:09:37.707+: 7024: info : virEventPollUpdateHandle:152 : 
EVENT_POLL_UPDATE_HANDLE: watch=417 events=3
  2017-01-16 12:09:37.707+: 7024: debug : virEventPollInterruptLocked:727 : 
Interrupting
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff7c002c10
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x100133caea0
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x100133d23c0
  .
  2017-01-16 12:14:28.445+: 7019: info : qemuMonitorJSONIOProcessLine:201 : 
QEMU_MONITOR_RECV_EVENT: mon=0x3fff94004d90 event={"timestamp": {"seconds": 
1484568868, "microseconds": 444620}, "event": "MIGRATION", "data": {"status": 
"failed"}}
  2017-01-16 12:14:28.445+: 7019: debug : qemuMonitorJSONIOProcessEvent:147 
: mon=0x3fff94004d90 obj=0x100133b5670
  2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToString:1762 : 
object=0x100133a8000
  2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToStringOne:1691 : 
object=0x100133a8000 type=0 gen=0x100133d1160
  2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToStringOne:1691 : 
object=0x100133d2a80 type=2 gen=0x100133d1160
  2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToString:1795 : 
result={"status":"failed"}
  2017-01-16 12:14:28.445+: 7019: debug : qemuMonitorEmitEvent:1218 : 
mon=0x3fff94004d90 event=MIGRATION
  2017-01-16 12:14:28.445+: 7019: info : virObjectRef:296 : OBJECT_REF: 
obj=0x3fff94004d90
  2017-01-16 12:14:28.445+: 7019: debug : qemuProcessHandleEvent:629 : 
vm=0x3fff4ca535c0
  2017-01-16 12:14:28.445+: 7019: info : virObjectNew:202 : OBJECT_NEW: 
obj=0x100133d2870 classname=virDomainQemuMonitorEvent
  2017-01-16 12:14:28.445+: 7019: debug : virObjectEventNew:645 : 
obj=0x100133d2870
  2017-01-16 12:14:28.445+: 7019: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x100133d2870
  

[Touch-packages] [Bug 1719630] Re: unattended-upgrades uses dpkg-vendor but doesn't depend on dpkg-dev

[LocutusOfBorg]

uploaded and ended up in unapproved queue, waiting for Release Team

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

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

Title:
  unattended-upgrades uses dpkg-vendor but doesn't depend on dpkg-dev

Status in unattended-upgrades package in Ubuntu:
  In Progress

Bug description:
  in its postinst script unattended-upgrade uses dpkg-vendor from dpkg-
  dev but does not depends on dpkg-dev which results in the following
  error:

  
  # apt-get update && apt-get upgrade

  Installing the packages goes well, except for, getting this warning.

  Setting up unattended-upgrades (0.97ubuntu1) ...
  /var/lib/dpkg/info/unattended-upgrades.postinst: 65:
  /var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found
  /var/lib/dpkg/info/unattended-upgrades.postinst: 66:
  /var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found
  /var/lib/dpkg/info/unattended-upgrades.postinst: 124:
  /var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found
  /var/lib/dpkg/info/unattended-upgrades.postinst: 125:
  /var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: unattended-upgrades 0.97ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 26 10:01:05 2017
  InstallationDate: Installed on 2013-09-03 (1483 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apt.apt.conf.d.50unattended-upgrades: [modified]
  mtime.conffile..etc.apt.apt.conf.d.50unattended-upgrades: 
2017-09-05T01:34:04.573213

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

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

[Touch-packages] [Bug 1719630] Re: unattended-upgrades uses dpkg-vendor but doesn't depend on dpkg-dev

[Balint Reczey]

** Patch added: "unattended-upgrades_0.97ubuntu2.patch"
   
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1719630/+attachment/4957315/+files/unattended-upgrades_0.97ubuntu2.patch

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

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

Title:
  unattended-upgrades uses dpkg-vendor but doesn't depend on dpkg-dev

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  in its postinst script unattended-upgrade uses dpkg-vendor from dpkg-
  dev but does not depends on dpkg-dev which results in the following
  error:

  
  # apt-get update && apt-get upgrade

  Installing the packages goes well, except for, getting this warning.

  Setting up unattended-upgrades (0.97ubuntu1) ...
  /var/lib/dpkg/info/unattended-upgrades.postinst: 65:
  /var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found
  /var/lib/dpkg/info/unattended-upgrades.postinst: 66:
  /var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found
  /var/lib/dpkg/info/unattended-upgrades.postinst: 124:
  /var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found
  /var/lib/dpkg/info/unattended-upgrades.postinst: 125:
  /var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: unattended-upgrades 0.97ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 26 10:01:05 2017
  InstallationDate: Installed on 2013-09-03 (1483 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apt.apt.conf.d.50unattended-upgrades: [modified]
  mtime.conffile..etc.apt.apt.conf.d.50unattended-upgrades: 
2017-09-05T01:34:04.573213

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

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

[Touch-packages] [Bug 1719630] Re: unattended-upgrades uses dpkg-vendor but doesn't depend on dpkg-dev

[Balint Reczey]

Thank, will add the patch soon.

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

Title:
  unattended-upgrades uses dpkg-vendor but doesn't depend on dpkg-dev

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  in its postinst script unattended-upgrade uses dpkg-vendor from dpkg-
  dev but does not depends on dpkg-dev which results in the following
  error:

  
  # apt-get update && apt-get upgrade

  Installing the packages goes well, except for, getting this warning.

  Setting up unattended-upgrades (0.97ubuntu1) ...
  /var/lib/dpkg/info/unattended-upgrades.postinst: 65:
  /var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found
  /var/lib/dpkg/info/unattended-upgrades.postinst: 66:
  /var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found
  /var/lib/dpkg/info/unattended-upgrades.postinst: 124:
  /var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found
  /var/lib/dpkg/info/unattended-upgrades.postinst: 125:
  /var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: unattended-upgrades 0.97ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 26 10:01:05 2017
  InstallationDate: Installed on 2013-09-03 (1483 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apt.apt.conf.d.50unattended-upgrades: [modified]
  mtime.conffile..etc.apt.apt.conf.d.50unattended-upgrades: 
2017-09-05T01:34:04.573213

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

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

[Touch-packages] [Bug 1718006] Re: gnome-control-center segfault on vpn changes

[Launchpad Bug Tracker]

This bug was fixed in the package network-manager - 1.8.4-1ubuntu1

---
network-manager (1.8.4-1ubuntu1) artful; urgency=medium

  * debian/patches/manager-Disconnect-from-signals-on-the-proxy-when-we.patch,
debian/patches/vpn-remote-connection-disconnect-signal-handlers-whe.patch:
Cherry-pick two patches from upstream. Fix leaked signal connections which
caused handlers to be called on disposed objects, leading to crashes in
some situations. (LP: #1704618) (LP: #1718006)
  * Merge with Debian. Remaining changes:
- Use systemd-resolved instead of dnsmasq
- debian/control:
  + Depend on isc-dhcp-client instead of recommends
  + Recommend network-manager-pptp
  + Suggest avahi-autoipd for IPv4LL support
- debian/control, debian/rules:
  + Disable team support since it's in universe
- debian/rules, debian/network-manager.postinst:
  + Don't restart NetworkManager on upgrade but recommend restarting
the computer
- debian/rules, debian/network-manager.postinst:
  + Don't install sysvinit scripts or migrate from sysvinit
- debian/network-manager.postinst:
  + Don't add the netdev group.
  + Handle upgrades from unmanaged policy
  + drop in an empty override file for NetworkManager to manage all devices
for upgrade from any version, as long as there is no netplan
configuration yet. (LP: #1676547)
- debian/network-manager.maintscript
  + Remove /etc/dbus-1/system.d/nm-ofono.conf
- debian/default-wifi-powersave-on.conf, debian/rules:
  + Install a config file to enable WiFi powersave
- Enable build tests
- Add autopkgtests
- debian/source_network-manager.py, debian/network-manager.install,
  debian/network-manager.links: Add apport hook
- Update Vcs links to point to Ubuntu branch
- debian/patches/*: Add patches. See patch descriptions for more details.
- dpkg-shlibdeps doesn't parse Version Reference, thus add a manual dep
  on libc6 >= 2.25. LP: #1715641.
- Add n-m-config-connectivity-ubuntu package (LP: #997200)
- NetworkManager.conf: disable MAC randomization feature. There is no
  easy way for desktop users to disable this feature yet. And there are
  reports that it doesn't work well with some systems. (LP: #1681513)

network-manager (1.8.4-1) unstable; urgency=medium

  * New upstream version 1.8.4
  * Rebase patches
  * Switch to dh_missing and abort on uninstalled files

 -- Iain Lane   Fri, 22 Sep 2017 18:56:30 +0100

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

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

Title:
  gnome-control-center segfault on vpn changes

Status in gnome-control-center:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  Maybe when I was configuring a printer

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 18 20:55:47 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-09-03 (1475 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcCmdline: gnome-control-center printers
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=fr_FR.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fe50b4232cc : testb  
$0x4,0x16(%rdx)
   PC (0x7fe50b4232cc) ok
   source "$0x4" ok
   destination "0x16(%rdx)" (0x10016) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_type_check_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libnm.so.0
   ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
  Title: gnome-control-center crashed with SIGSEGV in g_type_check_instance()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt libvirtd lpadmin lxd plugdev 
sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1718006/+subscriptions

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

[Touch-packages] [Bug 1702326] Re: New microrelease 1.4.7+1.48/zesty, 1.2.25/xenial

[Julian Andres Klode]

** Description changed:

  [Impact]
- This is a new upstream micro release for the first point release of Debian 
stretch.
+ This is a new upstream micro release for the first point release of Debian 
stretch. Some of the changes are in 1.2.25 as well, but 1.2.25 also includes 
changes from 1.4.8 which have their own LP bugs.
  
  apt (1.4.7) stretch; urgency=medium
  
-   [ Robert Luberda ]
-   * fix a "critical" typo in old changelog entry (Closes: 866358)
+   [ Robert Luberda ]
+   * fix a "critical" typo in old changelog entry (Closes: 866358)
  => Remove a letter, and fixes some tool
  
-   [ David Kalnischkies ]
-   * use port from SRV record instead of initial port
+   [ David Kalnischkies ]
+   * use port from SRV record instead of initial port
  => Might have picked the wrong port
  
-   [ Julian Andres Klode ]
-   * Reset failure reason when connection was successful
+   [ Julian Andres Klode ]
+   * Reset failure reason when connection was successful
  => Some failures were only treated as warnings, not errors
  
-   * debian/gbp.conf: Set debian-branch to 1.4.y
+   * debian/gbp.conf: Set debian-branch to 1.4.y
  => Building ...
  
-   * http: A response with Content-Length: 0 has no content
+   * http: A response with Content-Length: 0 has no content
  
  => Downloading failed if server responded with Content-Length: 0, as
-APT was waiting for content to read.
+    APT was waiting for content to read.
  
-  -- Julian Andres Klode   Tue, 04 Jul 2017 17:11:59
+  -- Julian Andres Klode   Tue, 04 Jul 2017 17:11:59
  +0200
  
  [Test case]
  We don't really have any yet, they require DNS servers and http servers, so 
it's not really easy to test.
  
  [Regression potential]
  We basically changed just the code used in the http method, and the changes 
are both very obvious and very small. I reproduced the http change with the tls 
support from 1.5, because launchpad was causing issues with that.
  
  With the failure reason reset, some errors might not be wrongly
  considered as transient connection errors and now cause scripts to fail.
  But that's how it should be, really.

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

Title:
  New microrelease 1.4.7+1.48/zesty, 1.2.25/xenial

Status in apt package in Ubuntu:
  Invalid
Status in apt source package in Xenial:
  Triaged
Status in apt source package in Zesty:
  In Progress
Status in apt package in Debian:
  Fix Released

Bug description:
  [Impact]
  This is a new upstream micro release for the first point release of Debian 
stretch. Some of the changes are in 1.2.25 as well, but 1.2.25 also includes 
changes from 1.4.8 which have their own LP bugs.

  apt (1.4.7) stretch; urgency=medium

    [ Robert Luberda ]
    * fix a "critical" typo in old changelog entry (Closes: 866358)
  => Remove a letter, and fixes some tool

    [ David Kalnischkies ]
    * use port from SRV record instead of initial port
  => Might have picked the wrong port

    [ Julian Andres Klode ]
    * Reset failure reason when connection was successful
  => Some failures were only treated as warnings, not errors

    * debian/gbp.conf: Set debian-branch to 1.4.y
  => Building ...

    * http: A response with Content-Length: 0 has no content

  => Downloading failed if server responded with Content-Length: 0, as
     APT was waiting for content to read.

   -- Julian Andres Klode   Tue, 04 Jul 2017 17:11:59
  +0200

  [Test case]
  We don't really have any yet, they require DNS servers and http servers, so 
it's not really easy to test.

  [Regression potential]
  We basically changed just the code used in the http method, and the changes 
are both very obvious and very small. I reproduced the http change with the tls 
support from 1.5, because launchpad was causing issues with that.

  With the failure reason reset, some errors might not be wrongly
  considered as transient connection errors and now cause scripts to
  fail. But that's how it should be, really.

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

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

[Touch-packages] [Bug 1719630] Re: unattended-upgrades uses dpkg-vendor but doesn't depend on dpkg-dev

[Balint Reczey]

** Changed in: unattended-upgrades (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  unattended-upgrades uses dpkg-vendor but doesn't depend on dpkg-dev

Status in unattended-upgrades package in Ubuntu:
  In Progress

Bug description:
  in its postinst script unattended-upgrade uses dpkg-vendor from dpkg-
  dev but does not depends on dpkg-dev which results in the following
  error:

  
  # apt-get update && apt-get upgrade

  Installing the packages goes well, except for, getting this warning.

  Setting up unattended-upgrades (0.97ubuntu1) ...
  /var/lib/dpkg/info/unattended-upgrades.postinst: 65:
  /var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found
  /var/lib/dpkg/info/unattended-upgrades.postinst: 66:
  /var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found
  /var/lib/dpkg/info/unattended-upgrades.postinst: 124:
  /var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found
  /var/lib/dpkg/info/unattended-upgrades.postinst: 125:
  /var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: unattended-upgrades 0.97ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 26 10:01:05 2017
  InstallationDate: Installed on 2013-09-03 (1483 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apt.apt.conf.d.50unattended-upgrades: [modified]
  mtime.conffile..etc.apt.apt.conf.d.50unattended-upgrades: 
2017-09-05T01:34:04.573213

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

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

[Touch-packages] [Bug 1719354] Re: apparmor blocking smbd which is in complain mode

[Aravind R]

** Package changed: apparmor (Ubuntu) => samba (Ubuntu)

** Description changed:

- apparmor blocking smbd which is in complain mode
+ This error is occurring because samba is working in user profile and
+ folder '/run/samba/msg.log' has owner as root. Any log created will be
+ as root. Hence, samba not able to log anything.
+ 
  
  aravind@comp:~$ tail -f /var/log/syslog | grep -i apparmor
  Sep 25 21:25:36 comp kernel: [ 4535.034713] audit: type=1400 
audit(1506354936.898:275): apparmor="ALLOWED" operation="open" 
profile="/usr/sbin/smbd" name="/run/samba/msg.lock/4470" pid=5690 comm="smbd" 
requested_mask="w" denied_mask="w" fsuid=0 ouid=0
  Sep 25 21:25:36 comp kernel: [ 4535.034719] audit: type=1400 
audit(1506354936.898:276): apparmor="ALLOWED" operation="file_lock" 
profile="/usr/sbin/smbd" name="/run/samba/msg.lock/4470" pid=5690 comm="smbd" 
requested_mask="w" denied_mask="w" fsuid=0 ouid=0
  Sep 25 21:27:39 comp kernel: [ 4657.984668] audit: type=1400 
audit(1506355059.847:290): apparmor="ALLOWED" operation="mknod" 
profile="/usr/sbin/smbd" name="/run/samba/msg.lock/6056" pid=6056 comm="smbd" 
requested_mask="c" denied_mask="c" fsuid=0 ouid=0
  Sep 25 21:27:39 comp kernel: [ 4657.984675] audit: type=1400 
audit(1506355059.847:291): apparmor="ALLOWED" operation="open" 
profile="/usr/sbin/smbd" name="/run/samba/msg.lock/6056" pid=6056 comm="smbd" 
requested_mask="wc" denied_mask="wc" fsuid=0 ouid=0
  Sep 25 21:27:39 comp kernel: [ 4657.984679] audit: type=1400 
audit(1506355059.847:292): apparmor="ALLOWED" operation="file_lock" 
profile="/usr/sbin/smbd" name="/run/samba/msg.lock/6056" pid=6056 comm="smbd" 
requested_mask="w" denied_mask="w" fsuid=0 ouid=0
  Sep 25 21:27:39 comp kernel: [ 4657.984684] audit: type=1400 
audit(1506355059.847:293): apparmor="ALLOWED" operation="truncate" 
profile="/usr/sbin/smbd" name="/run/samba/msg.lock/6056" pid=6056 comm="smbd" 
requested_mask="w" denied_mask="w" fsuid=0 ouid=0
  Sep 25 21:27:39 comp kernel: [ 4657.991838] audit: type=1400 
audit(1506355059.855:294): apparmor="ALLOWED" operation="unlink" 
profile="/usr/sbin/smbd" name="/run/samba/msg.lock/6056" pid=6056 comm="smbd" 
requested_mask="d" denied_mask="d" fsuid=0 ouid=0
  ^C
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apparmor 2.10.95-0ubuntu2.7
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Sep 25 21:27:07 2017
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic 
root=UUID=3bdb5792-d2a2-4f98-97bd-f274c3d0dde1 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  SourcePackage: apparmor
  Syslog:
-  Sep 25 10:34:40 comp dbus[1174]: [system] AppArmor D-Bus mediation is enabled
-  Sep 25 18:34:05 comp dbus[1083]: [system] AppArmor D-Bus mediation is enabled
-  Sep 25 20:10:24 comp dbus[1066]: [system] AppArmor D-Bus mediation is enabled
+  Sep 25 10:34:40 comp dbus[1174]: [system] AppArmor D-Bus mediation is enabled
+  Sep 25 18:34:05 comp dbus[1083]: [system] AppArmor D-Bus mediation is enabled
+  Sep 25 20:10:24 comp dbus[1066]: [system] AppArmor D-Bus mediation is enabled
  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 apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1719354

Title:
  apparmor blocking smbd which is in complain mode

Status in samba package in Ubuntu:
  New

Bug description:
  This error is occurring because samba is working in user profile and
  folder '/run/samba/msg.log' has owner as root. Any log created will be
  as root. Hence, samba not able to log anything.

  
  aravind@comp:~$ tail -f /var/log/syslog | grep -i apparmor
  Sep 25 21:25:36 comp kernel: [ 4535.034713] audit: type=1400 
audit(1506354936.898:275): apparmor="ALLOWED" operation="open" 
profile="/usr/sbin/smbd" name="/run/samba/msg.lock/4470" pid=5690 comm="smbd" 
requested_mask="w" denied_mask="w" fsuid=0 ouid=0
  Sep 25 21:25:36 comp kernel: [ 4535.034719] audit: type=1400 
audit(1506354936.898:276): apparmor="ALLOWED" operation="file_lock" 
profile="/usr/sbin/smbd" name="/run/samba/msg.lock/4470" pid=5690 comm="smbd" 
requested_mask="w" denied_mask="w" fsuid=0 ouid=0
  Sep 25 21:27:39 comp kernel: [ 4657.984668] audit: type=1400 
audit(1506355059.847:290): apparmor="ALLOWED" operation="mknod" 
profile="/usr/sbin/smbd" name="/run/samba/msg.lock/6056" pid=6056 comm="smbd" 
requested_mask="c" denied_mask="c" fsuid=0 ouid=0
  Sep 25 21:27:39 comp kernel: [ 4657.984675] audit: type=1400 
audit(1506355059.847:291): apparmor="ALLOWED" operation="open" 
profile="/usr/sbin/smbd" name="/run/samba/msg.lock/6056" pid=6056 comm="smbd" 
requested_mask="wc" denied_mask="wc" fsuid=0 ouid=0
  Sep 25 21:27:39 comp kernel: [ 4657.984679] audit: 

[Touch-packages] [Bug 1539209] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from source_set_volume_cb() from pa_source_process_msg()

[Daniel van Vugt]

This crash is still occurring after the update:
https://errors.ubuntu.com/problem/49276ec9f717c5268dfc99940a28fb4a56fe1b4a

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

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

Title:
  pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from
  source_set_volume_cb() from pa_source_process_msg()

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Confirmed
Status in pulseaudio source package in Zesty:
  New
Status in pulseaudio source package in Artful:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/49276ec9f717c5268dfc99940a28fb4a56fe1b4a

  ---

  [Impact]
  pulseaudio daemon crashes, interrupting sound output/input.

  [Test Case]
  Theoretical test case (crash does not happen for all users):
  1. Find some headphones and/or microphone. Ensure you do not wear the
     headphones during the test as it may be loud.
  2. Set audio output/input volumes to maximum.
  3. Unplug and replug the headphones/microphone.
  4. Check that that pulseaudio process is still running, with a start time
     older than when you began this test case.

  [Regression Potential]
  Low. This SRU affects the pulseaudio daemon only so the worst case would be 
loss of sound output/input. The same patches have been released to
  17.10 for a month already and zero regressions of the crashes have
  occurred worldwide since then.

  [Original Description]

  Appears randomly.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:7.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   potato12883 F...m pulseaudio
   /dev/snd/controlC0:  potato12883 F pulseaudio
   /dev/snd/controlC1:  potato12883 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jan 28 22:16:03 2016
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2016-01-17 (11 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=ru_RU.UTF-8
   LANGUAGE=ru
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_alsa_path_set_volume () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   pa_source_process_msg () from /usr/lib/libpulsecore-7.1.so
   ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   ?? () from /usr/lib/libpulsecore-7.1.so
  Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()
  UpgradeStatus: Upgraded to xenial on 2016-01-28 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.11
  dmi.board.name: JV71TR
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.11:bd12/07/2009:svnAcer:pnAspire7540:pvr0100:rvnAcer:rnJV71TR:rvrRev:cvnAcer:ct10:cvrNone:
  dmi.product.name: Aspire 7540
  dmi.product.version: 0100
  dmi.sys.vendor: Acer
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2016-01-25T21:44:07.089113

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

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

[Touch-packages] [Bug 1719630] [NEW] unattended-upgrades uses dpkg-vendor but doesn't depend on dpkg-dev

[Jean-Baptiste Lallement]

Public bug reported:

in its postinst script unattended-upgrade uses dpkg-vendor from dpkg-dev
but does not depends on dpkg-dev which results in the following error:


# apt-get update && apt-get upgrade

Installing the packages goes well, except for, getting this warning.

Setting up unattended-upgrades (0.97ubuntu1) ...
/var/lib/dpkg/info/unattended-upgrades.postinst: 65:
/var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found
/var/lib/dpkg/info/unattended-upgrades.postinst: 66:
/var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found
/var/lib/dpkg/info/unattended-upgrades.postinst: 124:
/var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found
/var/lib/dpkg/info/unattended-upgrades.postinst: 125:
/var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: unattended-upgrades 0.97ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
Uname: Linux 4.13.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 26 10:01:05 2017
InstallationDate: Installed on 2013-09-03 (1483 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
PackageArchitecture: all
ProcEnviron:
 TERM=screen-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: unattended-upgrades
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apt.apt.conf.d.50unattended-upgrades: [modified]
mtime.conffile..etc.apt.apt.conf.d.50unattended-upgrades: 
2017-09-05T01:34:04.573213

** Affects: unattended-upgrades (Ubuntu)
 Importance: High
 Status: Triaged


** Tags: amd64 apport-bug artful rls-aa-incoming

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

** Changed in: unattended-upgrades (Ubuntu)
   Importance: Undecided => High

** Tags removed: wayland-session
** Tags added: rls-aa-incoming

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

Title:
  unattended-upgrades uses dpkg-vendor but doesn't depend on dpkg-dev

Status in unattended-upgrades package in Ubuntu:
  Triaged

Bug description:
  in its postinst script unattended-upgrade uses dpkg-vendor from dpkg-
  dev but does not depends on dpkg-dev which results in the following
  error:

  
  # apt-get update && apt-get upgrade

  Installing the packages goes well, except for, getting this warning.

  Setting up unattended-upgrades (0.97ubuntu1) ...
  /var/lib/dpkg/info/unattended-upgrades.postinst: 65:
  /var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found
  /var/lib/dpkg/info/unattended-upgrades.postinst: 66:
  /var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found
  /var/lib/dpkg/info/unattended-upgrades.postinst: 124:
  /var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found
  /var/lib/dpkg/info/unattended-upgrades.postinst: 125:
  /var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: unattended-upgrades 0.97ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 26 10:01:05 2017
  InstallationDate: Installed on 2013-09-03 (1483 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apt.apt.conf.d.50unattended-upgrades: [modified]
  mtime.conffile..etc.apt.apt.conf.d.50unattended-upgrades: 
2017-09-05T01:34:04.573213

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

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

[Touch-packages] [Bug 1718664] Re: Dragging folder to applications: Incorrect behaviour

[Dmitry Shachnev]

It looks like Qt behaves correctly here, but Kate is buggy. See
https://bugs.kde.org/show_bug.cgi?id=366568, which was fixed in KDE
Applications 16.12.

KWrite does not have a concept of tabs, so dropping a folder there does
not make sense to me.

Is there any other application that is affected?

** Bug watch added: KDE Bug Tracking System #366568
   https://bugs.kde.org/show_bug.cgi?id=366568

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

Title:
  Dragging folder to applications: Incorrect behaviour

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  Applies to: Kubuntu 16.04.3 (up-to-date)

  Additional PPAs: ppa:kubuntu-ppa/backports

  Reproducible: Always

  Steps to reproduce:
  1.) Create a folder with a text file and a subfolder with a text file
  2.) Write some text in the text files
  3.) Drag'n'Drop the folder into any text-processor (e.g. kate, kwrite)

  Expected behaviour:
  All text files should be opened with their content

  Actual behaviour:
  There will be the correct number of files opened, but they don't have content 
and are trying to be opened from the incorrect path. It looks like there is one 
folder missing from the path to the file

  Did this work in earlier versions:
  Yes, this works on a fully up-to-date Kubuntu 14.04

  Does this work in later version:
  Probably (can't test currently), it works e.g. in KDE Neon User Edition.

  System information:
  KDE Plasma Version: 5.8.7
  KDE Frameworks Version: 5.36.0
  QT Version: 5.6.1
  Kernel Version 4.10.0-35-generic

  Further information:
  I was told that this works fine with QT 5.6.2 but do not currently have the 
possibility to test this myself. I was also told that the fix might be this 
commit in QT:

  https://git.qt.io/consulting-usa/qtbase-xcb-
  rendering/commit/1108291e1a2e7de23440c2b36b2fd31010ae3f51

  but again, I can't test this.

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

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

[Touch-packages] [Bug 1719579] Re: [Ubuntu 16.04.2] [libvirt] virsh restore fails from state file saved in /var/tmp folder using virsh save

[Frank Heimes]

The title says 16.04.2 but the ticket is tagged as 16.04.3.
Did you saw this happened on .2 or .3?
In case you are on .2 please do an upgrade to .3 and try again on the latest 
level.

** Also affects: apparmor
   Importance: Undecided
   Status: New

** No longer affects: apparmor

** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-power-systems
   Importance: Undecided => High

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => Canonical Server Team (canonical-server)

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

Title:
  [Ubuntu 16.04.2] [libvirt] virsh restore fails from state file saved
  in /var/tmp folder using virsh save

Status in The Ubuntu-power-systems project:
  New
Status in apparmor package in Ubuntu:
  New

Bug description:
  == Comment: #1 - SEETEENA THOUFEEK  - 2017-01-17 
00:09:16 ==
  Bala, Please mail me the machine information.

  == Comment: #3 - SEETEENA THOUFEEK  - 2017-01-17 
02:14:06 ==
  2017-01-16 12:09:37.707+: 7024: info : 
virSecurityDACRestoreFileLabelInternal:388 : Restoring DAC user and group on 
'/var/tmp/bala'
  2017-01-16 12:09:37.707+: 7024: info : 
virSecurityDACSetOwnershipInternal:290 : Setting DAC user and group on 
'/var/tmp/bala' to '0:0'
  2017-01-16 12:09:37.707+: 7024: warning : qemuDomainSaveImageStartVM:6750 
: failed to restore save state label on /var/tmp/bala
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff4ca62b00
  2017-01-16 12:09:37.707+: 7024: debug : qemuDomainObjEndAsyncJob:1848 : 
Stopping async job: start (vm=0x3fff4ca535c0 name=virt-tests-vm1-bala)
  2017-01-16 12:09:37.707+: 7024: info : virObjectRef:296 : OBJECT_REF: 
obj=0x3fff4ca62b00
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff4ca62b00
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff4ca535c0
  2017-01-16 12:09:37.707+: 7024: debug : virThreadJobClear:121 : Thread 
7024 (virNetServerHandleJob) finished job remoteDispatchDomainRestore with 
ret=-1
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff7c002c10
  2017-01-16 12:09:37.707+: 7024: debug : virNetServerProgramSendError:153 
: prog=536903814 ver=1 proc=54 type=1 serial=4 msg=0x100133d2590 
rerr=0x3fffa59be3c0
  2017-01-16 12:09:37.707+: 7024: debug : virNetMessageEncodePayload:376 : 
Encode length as 172
  2017-01-16 12:09:37.707+: 7024: debug : 
virNetServerClientSendMessageLocked:1399 : msg=0x100133d2590 proc=54 len=172 
offset=0
  2017-01-16 12:09:37.707+: 7024: info : 
virNetServerClientSendMessageLocked:1407 : RPC_SERVER_CLIENT_MSG_TX_QUEUE: 
client=0x100133d23c0 len=172 prog=536903814 vers=1 proc=54 type=1 status=1 
serial=4
  2017-01-16 12:09:37.707+: 7024: debug : 
virNetServerClientCalculateHandleMode:157 : tls=(nil) hs=-1, rx=0x100133d0670 
tx=0x100133d2590
  2017-01-16 12:09:37.707+: 7024: debug : 
virNetServerClientCalculateHandleMode:192 : mode=3
  2017-01-16 12:09:37.707+: 7024: info : virEventPollUpdateHandle:152 : 
EVENT_POLL_UPDATE_HANDLE: watch=417 events=3
  2017-01-16 12:09:37.707+: 7024: debug : virEventPollInterruptLocked:727 : 
Interrupting
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff7c002c10
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x100133caea0
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x100133d23c0
  .
  2017-01-16 12:14:28.445+: 7019: info : qemuMonitorJSONIOProcessLine:201 : 
QEMU_MONITOR_RECV_EVENT: mon=0x3fff94004d90 event={"timestamp": {"seconds": 
1484568868, "microseconds": 444620}, "event": "MIGRATION", "data": {"status": 
"failed"}}
  2017-01-16 12:14:28.445+: 7019: debug : qemuMonitorJSONIOProcessEvent:147 
: mon=0x3fff94004d90 obj=0x100133b5670
  2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToString:1762 : 
object=0x100133a8000
  2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToStringOne:1691 : 
object=0x100133a8000 type=0 gen=0x100133d1160
  2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToStringOne:1691 : 
object=0x100133d2a80 type=2 gen=0x100133d1160
  2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToString:1795 : 
result={"status":"failed"}
  2017-01-16 12:14:28.445+: 7019: debug : qemuMonitorEmitEvent:1218 : 
mon=0x3fff94004d90 event=MIGRATION
  2017-01-16 12:14:28.445+: 7019: info : virObjectRef:296 : OBJECT_REF: 
obj=0x3fff94004d90
  2017-01-16 12:14:28.445+: 7019: debug : qemuProcessHandleEvent:629 : 
vm=0x3fff4ca535c0
  2017-01-16 12:14:28.445+: 7019: info : virObjectNew:202 : OBJECT_NEW: 
obj=0x100133d2870 

[Touch-packages] [Bug 1704171] Re: WiFi connections unstable

[Lisa Nelson]

I spoke too soon, this morning it failed the same way twice.
After the 3rd re-boot it worked.
Reading the logs I posted on this bug, I believe this issue is related to some 
race condition on startup.  Not related to the kernel.

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

Title:
  WiFi connections unstable

Status in network-manager package in Ubuntu:
  New

Bug description:
  I have 3 WiFi signals here, and use them all without issue most of the
  time.  Since upgrading to 17.04 I have issues where my wifi will not
  connect to one of the other 2 signals, then also won't re-connect to
  the signal that was just in use.  When this happens, I can do a
  'restart' and it will connect just fine to any of the 3 signals.

  While it was failing a bit ago, I captured the syslog of whats going
  on and will include it below.

  Distributor ID:   Ubuntu
  Description:  Ubuntu 17.04
  Release:  17.04
  Codename: zesty

  Linux lisa-Inspiron-7720 4.10.0-28-generic #32-Ubuntu SMP Fri Jun 30
  05:32:18 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux


  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.2717] device (wlp2s0): Activation: starting connection 'LisaN' 
(58396782-9fe4-4ce3-b0e6-f72df56c72d5)
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.2720] audit: op="connection-activate" 
uuid="58396782-9fe4-4ce3-b0e6-f72df56c72d5" name="LisaN" pid=1962 uid=1000 
result="success"
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.2723] device (wlp2s0): state change: disconnected -> prepare 
(reason 'none') [30 40 0]
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.2725] manager: NetworkManager state is now CONNECTING
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.2779] device (wlp2s0): set-hw-addr: set-cloned MAC address to 
C4:D9:87:6E:9B:0F (permanent)
  Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [  312.891148] iwlwifi 
:02:00.0: L1 Enabled - LTR Disabled
  Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [  312.898132] iwlwifi 
:02:00.0: L1 Enabled - LTR Disabled
  Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [  312.898220] iwlwifi 
:02:00.0: Radio type=0x2-0x1-0x0
  Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [  313.183332] iwlwifi 
:02:00.0: L1 Enabled - LTR Disabled
  Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [  313.190314] iwlwifi 
:02:00.0: L1 Enabled - LTR Disabled
  Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [  313.190403] iwlwifi 
:02:00.0: Radio type=0x2-0x1-0x0
  Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [  313.274573] IPv6: 
ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6644] device (wlp2s0): supplicant interface state: inactive -> 
disabled
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6649] device (wlp2s0): state change: prepare -> config (reason 
'none') [40 50 0]
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6654] device (wlp2s0): Activation: (wifi) access point 'LisaN' has 
security, but secrets are required.
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6654] device (wlp2s0): state change: config -> need-auth (reason 
'none') [50 60 0]
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6728] device (wlp2s0): state change: need-auth -> prepare (reason 
'none') [60 40 0]
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6735] device (wlp2s0): state change: prepare -> config (reason 
'none') [40 50 0]
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6738] device (wlp2s0): Activation: (wifi) connection 'LisaN' has 
security, and secrets exist.  No new secrets needed.
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6739] Config: added 'ssid' value 'LisaN'
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6740] Config: added 'scan_ssid' value '1'
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6740] Config: added 'key_mgmt' value 'WPA-PSK'
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6740] Config: added 'psk' value ''
  Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: Can't set a parent on 
widget which has a parent
  Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: gtk_widget_destroy: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: gtk_widget_destroy: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: Can't set a parent on 
widget which has a parent
  Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: gtk_widget_destroy: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Jul 13 09:52:39 

[Touch-packages] [Bug 1704171] Re: WiFi connections unstable

[Lisa Nelson]

[1499961159.6654] device (wlp2s0): Activation: (wifi) access point 'LisaN' has 
security, but secrets are required.
Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:  
[1499961159.6654] device (wlp2s0): state change: config -> need-auth (reason 
'none') [50 60 0]
Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:  
[1499961159.6728] device (wlp2s0): state change: need-auth -> prepare (reason 
'none') [60 40 0]
Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:  
[1499961159.6735] device (wlp2s0): state change: prepare -> config (reason 
'none') [40 50 0]
Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: 

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

Title:
  WiFi connections unstable

Status in network-manager package in Ubuntu:
  New

Bug description:
  I have 3 WiFi signals here, and use them all without issue most of the
  time.  Since upgrading to 17.04 I have issues where my wifi will not
  connect to one of the other 2 signals, then also won't re-connect to
  the signal that was just in use.  When this happens, I can do a
  'restart' and it will connect just fine to any of the 3 signals.

  While it was failing a bit ago, I captured the syslog of whats going
  on and will include it below.

  Distributor ID:   Ubuntu
  Description:  Ubuntu 17.04
  Release:  17.04
  Codename: zesty

  Linux lisa-Inspiron-7720 4.10.0-28-generic #32-Ubuntu SMP Fri Jun 30
  05:32:18 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux


  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.2717] device (wlp2s0): Activation: starting connection 'LisaN' 
(58396782-9fe4-4ce3-b0e6-f72df56c72d5)
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.2720] audit: op="connection-activate" 
uuid="58396782-9fe4-4ce3-b0e6-f72df56c72d5" name="LisaN" pid=1962 uid=1000 
result="success"
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.2723] device (wlp2s0): state change: disconnected -> prepare 
(reason 'none') [30 40 0]
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.2725] manager: NetworkManager state is now CONNECTING
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.2779] device (wlp2s0): set-hw-addr: set-cloned MAC address to 
C4:D9:87:6E:9B:0F (permanent)
  Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [  312.891148] iwlwifi 
:02:00.0: L1 Enabled - LTR Disabled
  Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [  312.898132] iwlwifi 
:02:00.0: L1 Enabled - LTR Disabled
  Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [  312.898220] iwlwifi 
:02:00.0: Radio type=0x2-0x1-0x0
  Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [  313.183332] iwlwifi 
:02:00.0: L1 Enabled - LTR Disabled
  Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [  313.190314] iwlwifi 
:02:00.0: L1 Enabled - LTR Disabled
  Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [  313.190403] iwlwifi 
:02:00.0: Radio type=0x2-0x1-0x0
  Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [  313.274573] IPv6: 
ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6644] device (wlp2s0): supplicant interface state: inactive -> 
disabled
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6649] device (wlp2s0): state change: prepare -> config (reason 
'none') [40 50 0]
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6654] device (wlp2s0): Activation: (wifi) access point 'LisaN' has 
security, but secrets are required.
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6654] device (wlp2s0): state change: config -> need-auth (reason 
'none') [50 60 0]
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6728] device (wlp2s0): state change: need-auth -> prepare (reason 
'none') [60 40 0]
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6735] device (wlp2s0): state change: prepare -> config (reason 
'none') [40 50 0]
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6738] device (wlp2s0): Activation: (wifi) connection 'LisaN' has 
security, and secrets exist.  No new secrets needed.
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6739] Config: added 'ssid' value 'LisaN'
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6740] Config: added 'scan_ssid' value '1'
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6740] Config: added 'key_mgmt' value 'WPA-PSK'
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6740] Config: added 'psk' value ''
  Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: Can't set a parent on 
widget which has a parent
  Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: 

[Touch-packages] [Bug 1719355] Re: Switcher widget background goes outside its border

[Iain Lane]

It's not supposed to look like this, we just messed up when writing the
theme somehow

** Changed in: ubuntu-themes
   Status: Incomplete => Triaged

** Changed in: ubuntu-themes (Ubuntu)
   Status: Incomplete => Triaged

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

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

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

Title:
  Switcher widget background goes outside its border

Status in Ubuntu theme:
  Triaged
Status in Ubuntu UX:
  New
Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  In both Ambiance and Radiance themes, the switcher background is
  visible outside the widget border when inside a headerbar.

  
  See picture from Gnome Control Settings -> Search

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

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

[Touch-packages] [Bug 1718664] Re: Dragging folder to applications: Incorrect behaviour

[Martin Riethmayer]

I've added the PPA from https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/stable-phone-overlay/ and ran

sudo apt update

and

sudo apt upgrade

Which gives me Qt Version 5.6.2. The bug remains the same.

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

Title:
  Dragging folder to applications: Incorrect behaviour

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  Applies to: Kubuntu 16.04.3 (up-to-date)

  Additional PPAs: ppa:kubuntu-ppa/backports

  Reproducible: Always

  Steps to reproduce:
  1.) Create a folder with a text file and a subfolder with a text file
  2.) Write some text in the text files
  3.) Drag'n'Drop the folder into any text-processor (e.g. kate, kwrite)

  Expected behaviour:
  All text files should be opened with their content

  Actual behaviour:
  There will be the correct number of files opened, but they don't have content 
and are trying to be opened from the incorrect path. It looks like there is one 
folder missing from the path to the file

  Did this work in earlier versions:
  Yes, this works on a fully up-to-date Kubuntu 14.04

  Does this work in later version:
  Probably (can't test currently), it works e.g. in KDE Neon User Edition.

  System information:
  KDE Plasma Version: 5.8.7
  KDE Frameworks Version: 5.36.0
  QT Version: 5.6.1
  Kernel Version 4.10.0-35-generic

  Further information:
  I was told that this works fine with QT 5.6.2 but do not currently have the 
possibility to test this myself. I was also told that the fix might be this 
commit in QT:

  https://git.qt.io/consulting-usa/qtbase-xcb-
  rendering/commit/1108291e1a2e7de23440c2b36b2fd31010ae3f51

  but again, I can't test this.

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

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

[Touch-packages] [Bug 1719579] [NEW] [Ubuntu 16.04.2] [libvirt] virsh restore fails from state file saved in /var/tmp folder using virsh save

[bugproxy]

Public bug reported:

== Comment: #1 - SEETEENA THOUFEEK  - 2017-01-17 00:09:16 
==
Bala, Please mail me the machine information.

== Comment: #3 - SEETEENA THOUFEEK  - 2017-01-17 02:14:06 
==
2017-01-16 12:09:37.707+: 7024: info : 
virSecurityDACRestoreFileLabelInternal:388 : Restoring DAC user and group on 
'/var/tmp/bala'
2017-01-16 12:09:37.707+: 7024: info : 
virSecurityDACSetOwnershipInternal:290 : Setting DAC user and group on 
'/var/tmp/bala' to '0:0'
2017-01-16 12:09:37.707+: 7024: warning : qemuDomainSaveImageStartVM:6750 : 
failed to restore save state label on /var/tmp/bala
2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff4ca62b00
2017-01-16 12:09:37.707+: 7024: debug : qemuDomainObjEndAsyncJob:1848 : 
Stopping async job: start (vm=0x3fff4ca535c0 name=virt-tests-vm1-bala)
2017-01-16 12:09:37.707+: 7024: info : virObjectRef:296 : OBJECT_REF: 
obj=0x3fff4ca62b00
2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff4ca62b00
2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff4ca535c0
2017-01-16 12:09:37.707+: 7024: debug : virThreadJobClear:121 : Thread 7024 
(virNetServerHandleJob) finished job remoteDispatchDomainRestore with ret=-1
2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff7c002c10
2017-01-16 12:09:37.707+: 7024: debug : virNetServerProgramSendError:153 : 
prog=536903814 ver=1 proc=54 type=1 serial=4 msg=0x100133d2590 
rerr=0x3fffa59be3c0
2017-01-16 12:09:37.707+: 7024: debug : virNetMessageEncodePayload:376 : 
Encode length as 172
2017-01-16 12:09:37.707+: 7024: debug : 
virNetServerClientSendMessageLocked:1399 : msg=0x100133d2590 proc=54 len=172 
offset=0
2017-01-16 12:09:37.707+: 7024: info : 
virNetServerClientSendMessageLocked:1407 : RPC_SERVER_CLIENT_MSG_TX_QUEUE: 
client=0x100133d23c0 len=172 prog=536903814 vers=1 proc=54 type=1 status=1 
serial=4
2017-01-16 12:09:37.707+: 7024: debug : 
virNetServerClientCalculateHandleMode:157 : tls=(nil) hs=-1, rx=0x100133d0670 
tx=0x100133d2590
2017-01-16 12:09:37.707+: 7024: debug : 
virNetServerClientCalculateHandleMode:192 : mode=3
2017-01-16 12:09:37.707+: 7024: info : virEventPollUpdateHandle:152 : 
EVENT_POLL_UPDATE_HANDLE: watch=417 events=3
2017-01-16 12:09:37.707+: 7024: debug : virEventPollInterruptLocked:727 : 
Interrupting
2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff7c002c10
2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x100133caea0
2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x100133d23c0
.
2017-01-16 12:14:28.445+: 7019: info : qemuMonitorJSONIOProcessLine:201 : 
QEMU_MONITOR_RECV_EVENT: mon=0x3fff94004d90 event={"timestamp": {"seconds": 
1484568868, "microseconds": 444620}, "event": "MIGRATION", "data": {"status": 
"failed"}}
2017-01-16 12:14:28.445+: 7019: debug : qemuMonitorJSONIOProcessEvent:147 : 
mon=0x3fff94004d90 obj=0x100133b5670
2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToString:1762 : 
object=0x100133a8000
2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToStringOne:1691 : 
object=0x100133a8000 type=0 gen=0x100133d1160
2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToStringOne:1691 : 
object=0x100133d2a80 type=2 gen=0x100133d1160
2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToString:1795 : 
result={"status":"failed"}
2017-01-16 12:14:28.445+: 7019: debug : qemuMonitorEmitEvent:1218 : 
mon=0x3fff94004d90 event=MIGRATION
2017-01-16 12:14:28.445+: 7019: info : virObjectRef:296 : OBJECT_REF: 
obj=0x3fff94004d90
2017-01-16 12:14:28.445+: 7019: debug : qemuProcessHandleEvent:629 : 
vm=0x3fff4ca535c0
2017-01-16 12:14:28.445+: 7019: info : virObjectNew:202 : OBJECT_NEW: 
obj=0x100133d2870 classname=virDomainQemuMonitorEvent
2017-01-16 12:14:28.445+: 7019: debug : virObjectEventNew:645 : 
obj=0x100133d2870
2017-01-16 12:14:28.445+: 7019: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x100133d2870
2017-01-16 12:14:28.445+: 7019: info : virObjectUnref:261 : OBJECT_DISPOSE: 
obj=0x100133d2870
2017-01-16 12:14:28.445+: 7019: debug : 
virDomainQemuMonitorEventDispose:477 : obj=0x100133d2870
2017-01-16 12:14:28.445+: 7019: debug : virObjectEventDispose:121 : 
obj=0x100133d2870
2017-01-16 12:14:28.445+: 7019: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff94004d90
2017-01-16 12:14:28.445+: 7019: debug : qemuMonitorJSONIOProcessEvent:172 : 
handle MIGRATION handler=0x3fff9d7247e0 data=0x100133a8000
2017-01-16 12:14:28.445+: 7019: debug : qemuMonitorEmitMigrationStatus:1488 
: mon=0x3fff94004d90, status=failed
2017-01-16 12:14:28.445+: 7019: info : virObjectRef:296 : OBJECT_REF: 
obj=0x3fff94004d90
2017-01-16 12:14:28.445+: 7019: debug : 

[Touch-packages] [Bug 1719579] [NEW] [Ubuntu 16.04.2] [libvirt] virsh restore fails from state file saved in /var/tmp folder using virsh save

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

== Comment: #1 - SEETEENA THOUFEEK  - 2017-01-17 00:09:16 
==
Bala, Please mail me the machine information.

== Comment: #3 - SEETEENA THOUFEEK  - 2017-01-17 02:14:06 
==
2017-01-16 12:09:37.707+: 7024: info : 
virSecurityDACRestoreFileLabelInternal:388 : Restoring DAC user and group on 
'/var/tmp/bala'
2017-01-16 12:09:37.707+: 7024: info : 
virSecurityDACSetOwnershipInternal:290 : Setting DAC user and group on 
'/var/tmp/bala' to '0:0'
2017-01-16 12:09:37.707+: 7024: warning : qemuDomainSaveImageStartVM:6750 : 
failed to restore save state label on /var/tmp/bala
2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff4ca62b00
2017-01-16 12:09:37.707+: 7024: debug : qemuDomainObjEndAsyncJob:1848 : 
Stopping async job: start (vm=0x3fff4ca535c0 name=virt-tests-vm1-bala)
2017-01-16 12:09:37.707+: 7024: info : virObjectRef:296 : OBJECT_REF: 
obj=0x3fff4ca62b00
2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff4ca62b00
2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff4ca535c0
2017-01-16 12:09:37.707+: 7024: debug : virThreadJobClear:121 : Thread 7024 
(virNetServerHandleJob) finished job remoteDispatchDomainRestore with ret=-1
2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff7c002c10
2017-01-16 12:09:37.707+: 7024: debug : virNetServerProgramSendError:153 : 
prog=536903814 ver=1 proc=54 type=1 serial=4 msg=0x100133d2590 
rerr=0x3fffa59be3c0
2017-01-16 12:09:37.707+: 7024: debug : virNetMessageEncodePayload:376 : 
Encode length as 172
2017-01-16 12:09:37.707+: 7024: debug : 
virNetServerClientSendMessageLocked:1399 : msg=0x100133d2590 proc=54 len=172 
offset=0
2017-01-16 12:09:37.707+: 7024: info : 
virNetServerClientSendMessageLocked:1407 : RPC_SERVER_CLIENT_MSG_TX_QUEUE: 
client=0x100133d23c0 len=172 prog=536903814 vers=1 proc=54 type=1 status=1 
serial=4
2017-01-16 12:09:37.707+: 7024: debug : 
virNetServerClientCalculateHandleMode:157 : tls=(nil) hs=-1, rx=0x100133d0670 
tx=0x100133d2590
2017-01-16 12:09:37.707+: 7024: debug : 
virNetServerClientCalculateHandleMode:192 : mode=3
2017-01-16 12:09:37.707+: 7024: info : virEventPollUpdateHandle:152 : 
EVENT_POLL_UPDATE_HANDLE: watch=417 events=3
2017-01-16 12:09:37.707+: 7024: debug : virEventPollInterruptLocked:727 : 
Interrupting
2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff7c002c10
2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x100133caea0
2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x100133d23c0
.
2017-01-16 12:14:28.445+: 7019: info : qemuMonitorJSONIOProcessLine:201 : 
QEMU_MONITOR_RECV_EVENT: mon=0x3fff94004d90 event={"timestamp": {"seconds": 
1484568868, "microseconds": 444620}, "event": "MIGRATION", "data": {"status": 
"failed"}}
2017-01-16 12:14:28.445+: 7019: debug : qemuMonitorJSONIOProcessEvent:147 : 
mon=0x3fff94004d90 obj=0x100133b5670
2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToString:1762 : 
object=0x100133a8000
2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToStringOne:1691 : 
object=0x100133a8000 type=0 gen=0x100133d1160
2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToStringOne:1691 : 
object=0x100133d2a80 type=2 gen=0x100133d1160
2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToString:1795 : 
result={"status":"failed"}
2017-01-16 12:14:28.445+: 7019: debug : qemuMonitorEmitEvent:1218 : 
mon=0x3fff94004d90 event=MIGRATION
2017-01-16 12:14:28.445+: 7019: info : virObjectRef:296 : OBJECT_REF: 
obj=0x3fff94004d90
2017-01-16 12:14:28.445+: 7019: debug : qemuProcessHandleEvent:629 : 
vm=0x3fff4ca535c0
2017-01-16 12:14:28.445+: 7019: info : virObjectNew:202 : OBJECT_NEW: 
obj=0x100133d2870 classname=virDomainQemuMonitorEvent
2017-01-16 12:14:28.445+: 7019: debug : virObjectEventNew:645 : 
obj=0x100133d2870
2017-01-16 12:14:28.445+: 7019: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x100133d2870
2017-01-16 12:14:28.445+: 7019: info : virObjectUnref:261 : OBJECT_DISPOSE: 
obj=0x100133d2870
2017-01-16 12:14:28.445+: 7019: debug : 
virDomainQemuMonitorEventDispose:477 : obj=0x100133d2870
2017-01-16 12:14:28.445+: 7019: debug : virObjectEventDispose:121 : 
obj=0x100133d2870
2017-01-16 12:14:28.445+: 7019: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff94004d90
2017-01-16 12:14:28.445+: 7019: debug : qemuMonitorJSONIOProcessEvent:172 : 
handle MIGRATION handler=0x3fff9d7247e0 data=0x100133a8000
2017-01-16 12:14:28.445+: 7019: debug : qemuMonitorEmitMigrationStatus:1488 
: mon=0x3fff94004d90, status=failed
2017-01-16 12:14:28.445+: 7019: info : virObjectRef:296 : OBJECT_REF: 
obj=0x3fff94004d90
2017-01-16 12:14:28.445+: 7019: debug : 

[Touch-packages] [Bug 1264368] Re: GLib-CRITICAL **: Source ID was not found when attempting to remove it - warning when leaving Network menu of g-c-c

[Juan P. Tamayo]

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

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

Title:
  GLib-CRITICAL **: Source ID was not found when attempting to remove it
  - warning when leaving Network menu of g-c-c

Status in AndroidSDK:
  New
Status in Banshee:
  New
Status in gnome-control-center:
  Incomplete
Status in GParted:
  Unknown
Status in notification-daemon:
  New
Status in anjuta package in Ubuntu:
  Confirmed
Status in consolekit package in Ubuntu:
  Confirmed
Status in f-spot package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gnome-mplayer package in Ubuntu:
  New
Status in putty package in Ubuntu:
  Confirmed

Bug description:
  Steps to recreate:
  1. Open gnome-control-center in terminal.
  2. Go to Network.
  3. Go back to All preferences.
  4. Notice that in terminal there is a warning:

  $ gnome-control-center

  (gnome-control-center:13519): GLib-CRITICAL **: Source ID 166 was not
  found when attempting to remove it

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-control-center 1:3.6.3-0ubuntu49
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.12.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Dec 26 21:03:52 2013
  InstallationDate: Installed on 2013-10-15 (71 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131015)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to trusty on 2013-11-05 (51 days ago)

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

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

[Touch-packages] [Bug 1719521] Re: Missing Icon for printer in settings

[J.Ar]

It seems that the problem has been solved by itself, although I cannot
say how...maybe and update or restart/-boot.

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

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

Title:
  Missing Icon for printer in settings

Status in ubuntu-themes package in Ubuntu:
  Invalid

Bug description:
  My Brother printer was detected automatically and correctly (which is
  great), but the icon is missing in printer settings. See screenshot...

  OS: Ubuntu 17.10 artful
  Kernel: x86_64 Linux 4.12.0-13-generic
  Uptime: 13h 2m
  Packages: 1900
  Shell: bash 4.4.12
  Resolution: 1600x900
  DE: GNOME 
  WM: GNOME Shell
  WM Theme: Adwaita
  GTK Theme: Ambiance [GTK2/3]
  Icon Theme: ubuntu-mono-dark
  Font: Ubuntu 12
  CPU: Intel Core i3-3225 @ 4x 3.3GHz [38.0°C]
  GPU: AMD Radeon (TM) RX 480 Graphics (AMD POLARIS10 / DRM 3.15.0 / 
4.12.0-13-generic, LLVM 5.0.0)
  RAM: 1431MiB / 15999MiB

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

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

[Touch-packages] [Bug 462760] Re: sprof fails to work with shared objects

[emakmel]

I am also having this problem, while trying to profile UBUNTU'S manual
example.

Example found here :
http://manpages.ubuntu.com/manpages/yakkety/man1/sprof.1.html#contenttoc7

Strace here:

execve("/usr/bin/sprof", ["sprof", "-p", "libdemo.so.1"], [/* 74 vars */]) = 0
brk(NULL)   = 0x934000
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f0a39cd2000
access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=104012, ...}) = 0
mmap(NULL, 104012, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f0a39cb8000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/libdl.so.2", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\240\r\0\0\0\0\0\0"..., 
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=14608, ...}) = 0
mmap(NULL, 2109680, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7f0a398ab000
mprotect(0x7f0a398ae000, 2093056, PROT_NONE) = 0
mmap(0x7f0a39aad000, 8192, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x2000) = 0x7f0a39aad000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\t\2\0\0\0\0\0"..., 
832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1868984, ...}) = 0
mmap(NULL, 3971488, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7f0a394e1000
mprotect(0x7f0a396a1000, 2097152, PROT_NONE) = 0
mmap(0x7f0a398a1000, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1c) = 0x7f0a398a1000
mmap(0x7f0a398a7000, 14752, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f0a398a7000
close(3)= 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f0a39cb7000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f0a39cb6000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f0a39cb5000
arch_prctl(ARCH_SET_FS, 0x7f0a39cb6700) = 0
mprotect(0x7f0a398a1000, 16384, PROT_READ) = 0
mprotect(0x7f0a39aad000, 4096, PROT_READ) = 0
mprotect(0x604000, 4096, PROT_READ) = 0
mprotect(0x7f0a39cd4000, 4096, PROT_READ) = 0
munmap(0x7f0a39cb8000, 104012)  = 0
brk(NULL)   = 0x934000
brk(0x955000)   = 0x955000
open("/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=10219008, ...}) = 0
mmap(NULL, 10219008, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f0a38b22000
close(3)= 0
open("./libdemo.so.1", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0`\6\0\0\0\0\0\0"..., 
832) = 832
fstat(3, {st_mode=S_IFREG|0775, st_size=9496, ...}) = 0
getcwd("/home/keks/work/test", 128) = 21
mmap(NULL, 2101312, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7f0a3892
mprotect(0x7f0a38921000, 2093056, PROT_NONE) = 0
mmap(0x7f0a38b2, 8192, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0) = 0x7f0a38b2
close(3)= 0
writev(2, [{"Inconsistency detected by ld.so:"..., 33}, {"dl-open.c", 9}, {": 
", 2}, {"717", 3}, {": ", 2}, {"_dl_open", 8}, {": ", 2}, {"Assertion `", 11}, 
{"_dl_debug_initialize (0, args.ns"..., 61}, {"' failed!\n", 10}], 
10Inconsistency detected by ld.so: dl-open.c: 717: _dl_open: Assertion 
`_dl_debug_initialize (0, args.nsid)->r_state == RT_CONSISTENT' failed!
) = 141
exit_group(127) = ?
+++ exited with 127 +++

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

Title:
  sprof fails to work with shared objects

Status in eglibc package in Ubuntu:
  Confirmed
Status in eglibc package in Debian:
  New
Status in eglibc package in Fedora:
  Unknown

Bug description:
  Binary package hint: libc-dev-bin

  When I try to profile a compiled shared object, sprof always fails
  with: "Inconsistency detected by ld.so: dl-open.c: 672: _dl_open:
  Assertion `_dl_debug_initialize (0, args.nsid)->r_state ==
  RT_CONSISTENT' failed!"

  I have the environment variables LD_PROFILE and LD_PROFILE_OUTPUT set
  up as you would expect and a file.so.profile file is created along
  with gmon.out.

  Both the main program and .SO are compiled and linked with -pg

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

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

[Touch-packages] [Bug 1672033] Re: Xorg does not detect displays in rootless mode on nvidia proprietary drivers (GNOME)

[Launchpad Bug Tracker]

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

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

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

Title:
  Xorg does not detect displays in rootless mode on nvidia proprietary
  drivers (GNOME)

Status in NVIDIA Drivers Ubuntu:
  New
Status in mutter package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  There are two bug reports in LP: #1559576, LP: #1632322 and also LP:
  #164, where GDM does not start on proprietary nvidia drivers. As
  it turned out, the reason for that was Xorg starting in rootless mode
  and apparently not initializing everything properly, which was causing
  gnome-shell/libmutter to crash.

  Installing xserver-xorg-legacy did partially fix those issues.

  Enabling modesetting for nvidia driver however still causes the
  problem.

  
  Here are some parts from log:
  Xorg startup:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (--) Log file 
renamed from "/var/lib/gdm3/.local/share/xorg/Xorg.pid-2027.log" to 
"/var/lib/gdm3/.local/share/xorg/Xorg.0.log"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: X.Org X Server 
1.18.4
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Release Date: 
2016-07-19
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: X Protocol Version 
11, Revision 0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Build Operating 
System: Linux 4.4.0-53-generic x86_64 Ubuntu

  glx loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"glx"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/libglx.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module glx: 
vendor="NVIDIA Corporation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 4.0.2, module version = 1.0.0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Server Extension
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) NVIDIA GLX 
Module  375.39  Tue Jan 31 19:37:12 PST 2017

  nvidia loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"nvidia"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module nvidia: 
vendor="NVIDIA Corporation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 4.0.2, module version = 1.0.0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Video Driver

  modesetting loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"modesetting"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/xorg/modules/drivers/modesetting_drv.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module 
modesetting: vendor="X.Org Foundation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 1.18.4, module version = 1.18.4
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Video Driver
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: ABI class: 
X.Org Video Driver, version 20.0

  
  gnome-shell fails to run:
  Mär 11 00:43:20 arvlin kernel: gnome-shell[2067]: segfault at 28 ip 
7fedba8da7c4 sp 7ffd2fb5f5a0 error 4 in 
libmutter-0.so.0.0.0[7fedba893000+12f000]

  xorg stops:
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:66
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:67
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:64
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:65
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) NVIDIA(GPU-0): 
Deleting GPU-0
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Server 
terminated successfully (0). Closing log file.
  Mär 11 00:43:21 arvlin gdm-launch-environment][2009]: 
pam_unix(gdm-launch-environment:session): session closed for user gdm

To manage notifications about this bug go to:

[Touch-packages] [Bug 1672033] Re: Xorg does not detect displays in rootless mode on nvidia proprietary drivers (GNOME)

[Launchpad Bug Tracker]

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

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

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

Title:
  Xorg does not detect displays in rootless mode on nvidia proprietary
  drivers (GNOME)

Status in NVIDIA Drivers Ubuntu:
  New
Status in mutter package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  There are two bug reports in LP: #1559576, LP: #1632322 and also LP:
  #164, where GDM does not start on proprietary nvidia drivers. As
  it turned out, the reason for that was Xorg starting in rootless mode
  and apparently not initializing everything properly, which was causing
  gnome-shell/libmutter to crash.

  Installing xserver-xorg-legacy did partially fix those issues.

  Enabling modesetting for nvidia driver however still causes the
  problem.

  
  Here are some parts from log:
  Xorg startup:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (--) Log file 
renamed from "/var/lib/gdm3/.local/share/xorg/Xorg.pid-2027.log" to 
"/var/lib/gdm3/.local/share/xorg/Xorg.0.log"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: X.Org X Server 
1.18.4
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Release Date: 
2016-07-19
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: X Protocol Version 
11, Revision 0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Build Operating 
System: Linux 4.4.0-53-generic x86_64 Ubuntu

  glx loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"glx"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/libglx.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module glx: 
vendor="NVIDIA Corporation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 4.0.2, module version = 1.0.0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Server Extension
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) NVIDIA GLX 
Module  375.39  Tue Jan 31 19:37:12 PST 2017

  nvidia loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"nvidia"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module nvidia: 
vendor="NVIDIA Corporation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 4.0.2, module version = 1.0.0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Video Driver

  modesetting loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"modesetting"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/xorg/modules/drivers/modesetting_drv.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module 
modesetting: vendor="X.Org Foundation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 1.18.4, module version = 1.18.4
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Video Driver
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: ABI class: 
X.Org Video Driver, version 20.0

  
  gnome-shell fails to run:
  Mär 11 00:43:20 arvlin kernel: gnome-shell[2067]: segfault at 28 ip 
7fedba8da7c4 sp 7ffd2fb5f5a0 error 4 in 
libmutter-0.so.0.0.0[7fedba893000+12f000]

  xorg stops:
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:66
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:67
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:64
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:65
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) NVIDIA(GPU-0): 
Deleting GPU-0
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Server 
terminated successfully (0). Closing log file.
  Mär 11 00:43:21 arvlin gdm-launch-environment][2009]: 
pam_unix(gdm-launch-environment:session): session closed for user gdm

To manage notifications about this bug go to:

[Touch-packages] [Bug 1714667] Re: please add old hungarian letters

[Kovács Viktor]

** Changed in: ubuntu-font-family-sources (Ubuntu)
   Status: Incomplete => Confirmed

** Tags removed: patch

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

Title:
  please add old hungarian letters

Status in ubuntu-font-family-sources package in Ubuntu:
  Confirmed

Bug description:
  Old Hungarian letters (U10c80-U10cff) missing from font-families

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-family-sources/+bug/1714667/+subscriptions

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

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

[Julian Andres Klode]

** Changed in: apt (Ubuntu Zesty)
   Status: Triaged => In Progress

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

Title:
  method mirror broken at 1.3

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Zesty:
  In Progress

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

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

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

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

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

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

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

[Touch-packages] [Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to

[Julian Andres Klode]

** Changed in: apt (Ubuntu Zesty)
   Status: Triaged => In Progress

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

Title:
  unattended-upgrades does not block shutdown of system, as it is
  designed to

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project xenial series:
  New
Status in apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Triaged
Status in unattended-upgrades source package in Xenial:
  New
Status in apt source package in Zesty:
  In Progress
Status in unattended-upgrades source package in Zesty:
  New

Bug description:
  Title: No pop-up window to warn users that system should not reboot or
  shutdown while installing security updates

  Summary:
  No pop-up window to warn users that system should not reboot or shutdown 
while installing security updates

  Steps:
  1. trigger unattended-upgrades
  2. reboot or shutdown system while installing packages

  Expected results: There is a pop-up window to warn users that system
  should not reboot or shutdown

  Actual results: There is no pop-up window to warn users

  Additional information:
  $ apt-cache policy unattended-upgrades
  unattended-upgrades:
Installed: 0.90
Candidate: 0.90ubuntu0.5
  $ lsb_release -rd
  Description:Ubuntu 16.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions

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

[Touch-packages] [Bug 1702326] Re: New microrelease 1.4.7+1.48/zesty, 1.2.25/xenial

[Julian Andres Klode]

** Changed in: apt (Ubuntu Zesty)
   Status: Triaged => In Progress

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

Title:
  New microrelease 1.4.7+1.48/zesty, 1.2.25/xenial

Status in apt package in Ubuntu:
  Invalid
Status in apt source package in Xenial:
  Triaged
Status in apt source package in Zesty:
  In Progress
Status in apt package in Debian:
  Fix Released

Bug description:
  [Impact]
  This is a new upstream micro release for the first point release of Debian 
stretch.

  apt (1.4.7) stretch; urgency=medium

[ Robert Luberda ]
* fix a "critical" typo in old changelog entry (Closes: 866358)
  => Remove a letter, and fixes some tool

[ David Kalnischkies ]
* use port from SRV record instead of initial port
  => Might have picked the wrong port

[ Julian Andres Klode ]
* Reset failure reason when connection was successful
  => Some failures were only treated as warnings, not errors

* debian/gbp.conf: Set debian-branch to 1.4.y
  => Building ...

* http: A response with Content-Length: 0 has no content

  => Downloading failed if server responded with Content-Length: 0, as
 APT was waiting for content to read.

   -- Julian Andres Klode   Tue, 04 Jul 2017 17:11:59
  +0200

  [Test case]
  We don't really have any yet, they require DNS servers and http servers, so 
it's not really easy to test.

  [Regression potential]
  We basically changed just the code used in the http method, and the changes 
are both very obvious and very small. I reproduced the http change with the tls 
support from 1.5, because launchpad was causing issues with that.

  With the failure reason reset, some errors might not be wrongly
  considered as transient connection errors and now cause scripts to
  fail. But that's how it should be, really.

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

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

[Touch-packages] [Bug 1697120] Re: artful's apt-file and aptitude complains about Ubuntu sources.list

[Julian Andres Klode]

** Changed in: apt (Ubuntu Zesty)
   Status: Triaged => In Progress

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

Title:
  artful's apt-file and aptitude complains about Ubuntu sources.list

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Zesty:
  In Progress
Status in apt package in Debian:
  Fix Released

Bug description:
  [Impact]
  apt-file is now difficult to use with about a dozen warnings like this:

  W: Target Contents-deb-legacy (Contents-amd64) is configured multiple
  times in /etc/apt/sources.list:6 and /etc/apt/sources.list:17

  For reference, this is line 6:
  deb http://us.archive.ubuntu.com/ubuntu/ artful main restricted

  And this is line 17:
  deb http://us.archive.ubuntu.com/ubuntu/ artful universe

  This is how Ubuntu's default sources.list has been structured since
  the beginning? (or at least more than a decade).

  What I expect
  -
  The warning isn't specific enough. Lines 6 and 17 are not actually 
duplicates. The warning could be removed or fixed so that it doesn't complain 
about non-duplicates.

  Or the warning could be disabled on Ubuntu.

  See also
  
  LP: #1579372

  [Test case]
  Install apt-file and update, make sure that the warnings are gone.

  [Regression potential]
  Warnings about duplicate index targets containing "legacy" in their 
configured name are not shown anymore, thus it's harder to "fix" servers. But 
apart from that, which was the goal, I don't see any.

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

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

[Touch-packages] [Bug 1716973] Re: Don't pull in network-online.target in apt-daily.timer

[Julian Andres Klode]

** Changed in: apt (Ubuntu Zesty)
   Status: Triaged => In Progress

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

Title:
  Don't pull in network-online.target in apt-daily.timer

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Triaged
Status in apt source package in Zesty:
  In Progress

Bug description:
  [Impact]
  apt-daily.timer is enabled on every boot and pulls in network-online.target 
via Wants and After. While nothing has an After=apt-daily.timer (or rather an 
After=timers.target) and this should thus not impact boot performance, the 
rc-local.service specifies an After=network-online.target and the login stuff 
(getty, gdm, etc) is ordered After=rc-local, thus severely increasing the time 
to login if nothing else pulls in network-online (like an LSB script).

  This works around the problem on most boots, the problem will only
  occur if the timer would have elapsed while the machine was off.

  [Test case]
  Well, the change is fairly obvious. Actually testing that is pointless, and 
depending on the system configuration, network-online.target might be pulled in 
by something else. So just look at the file and check that the 
network-online.target dependency moved to the service.

  [Regression potential]
  Literally none. We just move the dependency to the service which actually 
needs it.

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

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

[Touch-packages] [Bug 1719367] Re: Day button in gnome-weather is insensitive (colour does not change)

[Launchpad Bug Tracker]

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

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

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

Title:
  Day button in gnome-weather is insensitive (colour does not change)

Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Steps:

  1. Install and open gnome-weather
  2. Select a location or let it find one
  3. Switch between Today and Tomorrow
  4. No change in the colour of the button

  The colour of the button should change to indicate which day is selected.
  See screenshot.
  This does not happen in Adwaita.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170918-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 25 18:53:20 2017
  InstallationDate: Installed on 2017-09-21 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1719521] [NEW] Missing Icon for printer in settings

[J.Ar]

Public bug reported:

My Brother printer was detected automatically and correctly (which is
great), but the icon is missing in printer settings. See screenshot...

OS: Ubuntu 17.10 artful
Kernel: x86_64 Linux 4.12.0-13-generic
Uptime: 13h 2m
Packages: 1900
Shell: bash 4.4.12
Resolution: 1600x900
DE: GNOME 
WM: GNOME Shell
WM Theme: Adwaita
GTK Theme: Ambiance [GTK2/3]
Icon Theme: ubuntu-mono-dark
Font: Ubuntu 12
CPU: Intel Core i3-3225 @ 4x 3.3GHz [38.0°C]
GPU: AMD Radeon (TM) RX 480 Graphics (AMD POLARIS10 / DRM 3.15.0 / 
4.12.0-13-generic, LLVM 5.0.0)
RAM: 1431MiB / 15999MiB

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


** Tags: artful ubuntu-mono-dark

** Attachment added: "Bildschirmfoto von »2017-09-26 08-37-01«.png"
   
https://bugs.launchpad.net/bugs/1719521/+attachment/4957139/+files/Bildschirmfoto%20von%20%C2%BB2017-09-26%2008-37-01%C2%AB.png

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

Title:
  Missing Icon for printer in settings

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  My Brother printer was detected automatically and correctly (which is
  great), but the icon is missing in printer settings. See screenshot...

  OS: Ubuntu 17.10 artful
  Kernel: x86_64 Linux 4.12.0-13-generic
  Uptime: 13h 2m
  Packages: 1900
  Shell: bash 4.4.12
  Resolution: 1600x900
  DE: GNOME 
  WM: GNOME Shell
  WM Theme: Adwaita
  GTK Theme: Ambiance [GTK2/3]
  Icon Theme: ubuntu-mono-dark
  Font: Ubuntu 12
  CPU: Intel Core i3-3225 @ 4x 3.3GHz [38.0°C]
  GPU: AMD Radeon (TM) RX 480 Graphics (AMD POLARIS10 / DRM 3.15.0 / 
4.12.0-13-generic, LLVM 5.0.0)
  RAM: 1431MiB / 15999MiB

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

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

[Touch-packages] [Bug 1719355] Re: Switcher widget background goes outside its border

[Carlo Lobrano]

I considered how switchers look like in headerbar vs other places and
the first does not look really right, but I understand your point.

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

Title:
  Switcher widget background goes outside its border

Status in Ubuntu theme:
  Incomplete
Status in Ubuntu UX:
  New
Status in ubuntu-themes package in Ubuntu:
  Incomplete

Bug description:
  In both Ambiance and Radiance themes, the switcher background is
  visible outside the widget border when inside a headerbar.

  
  See picture from Gnome Control Settings -> Search

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

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