[Touch-packages] [Bug 1308979] Re: test_ubuntushape started failing with no change

[Launchpad Bug Tracker]

[Expired for ubuntu-ui-toolkit (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  test_ubuntushape started failing with no change

Status in ubuntu-ui-toolkit package in Ubuntu:
  Expired
Status in ubuntu-ui-toolkit package in Ubuntu RTM:
  Incomplete

Bug description:
  Testability driver loaded. Wire protocol version is "1.4".
  unity::action::ActionManager::ActionManager(QObject*):
Could not determine application identifier. HUD will not work properly.
Provide your application identifier in $APP_ID environment variable.
  callbacks 0xb3d7c5f9 0xb3d7c5a5
  creating surface at (0, 58) with size (768, 1222) with title 'qmlscene: 
mainView'file:///usr/lib/ubuntu-ui-toolkit/examples/ubuntu-ui-toolkit-gallery/ubuntu-ui-toolkit-gallery.qml:120:33:
 Unable to assign [undefined] to QString

  ** (process:10043): WARNING **: Unable to register app: 
GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Invalid application ID
  }}}

  Traceback (most recent call last):
File 
"/usr/lib/python2.7/dist-packages/ubuntuuitoolkit/tests/gallery/test_gallery.py",
 line 79, in test_ubuntushape
  self.loadItem(item)
File "/usr/lib/python2.7/dist-packages/ubuntuuitoolkit/tests/__init__.py", 
line 165, in loadItem
  self.selectItem(item)
File "/usr/lib/python2.7/dist-packages/ubuntuuitoolkit/tests/__init__.py", 
line 228, in selectItem
  self.assertThat(item.selected, Eventually(Equals(True)))
File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 406, in 
assertThat
  raise mismatch_error
  MismatchError: After 10.0 seconds test on Standard.selected failed: True != 
dbus.Boolean(False, variant_level=1)

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

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

[Touch-packages] [Bug 715141] Re: Default NTP servers do not have AAAA records

[Launchpad Bug Tracker]

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

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

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

Title:
  Default NTP servers do not have  records

Status in ntp package in Ubuntu:
  Expired

Bug description:
  Binary package hint: ntp

  When installing ntp on an IPv6 only host, the kindly provided ntp.ubuntu.com 
does not work, because it does not have a  record. 
  Please provide IPv6 connectivity for this host.
  This affects all releases.

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

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

[Touch-packages] [Bug 1497090] Re: Clients in Unity8 don't receive motion/hover mouse events

[Launchpad Bug Tracker]

[Expired for QtMir because there has been no activity for 60 days.]

** Changed in: qtmir
   Status: Incomplete => Expired

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

Title:
  Clients in Unity8 don't receive motion/hover mouse events

Status in QtMir:
  Expired
Status in qtmir package in Ubuntu:
  Expired
Status in unity8 package in Ubuntu:
  Expired

Bug description:
  Clients don't receive motion/hover mouse events.

  Trying these demos under unity8:

     mir_demo_client_target -n--desktop_file_hint=unity8
     mir_demo_client_eglsquare -n -- --desktop_file_hint=unity8

  They kind of work, but they don't sense the mouse pointer moving over
  them like they do in the Mir demo servers. At least not till you hold
  a mouse button down.

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

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

[Touch-packages] [Bug 1497090] Re: Clients in Unity8 don't receive motion/hover mouse events

[Launchpad Bug Tracker]

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

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

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

Title:
  Clients in Unity8 don't receive motion/hover mouse events

Status in QtMir:
  Expired
Status in qtmir package in Ubuntu:
  Expired
Status in unity8 package in Ubuntu:
  Expired

Bug description:
  Clients don't receive motion/hover mouse events.

  Trying these demos under unity8:

     mir_demo_client_target -n--desktop_file_hint=unity8
     mir_demo_client_eglsquare -n -- --desktop_file_hint=unity8

  They kind of work, but they don't sense the mouse pointer moving over
  them like they do in the Mir demo servers. At least not till you hold
  a mouse button down.

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

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

[Touch-packages] [Bug 1561861] Re: UbuntuColors.Orange should be Ubuntu.orange instead

[Launchpad Bug Tracker]

[Expired for ubuntu-ui-toolkit (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  UbuntuColors.Orange should be Ubuntu.orange instead

Status in ubuntu-ui-toolkit package in Ubuntu:
  Expired

Bug description:
  
https://developer.ubuntu.com/api/apps/qml/sdk-15.04.1/Ubuntu.Components.ListItemLayout/

  The code:

  ListItemLayout {
  id: layout
  title.text: "Hello..."
  title.color: UbuntuColors.Orange
  subtitle.text: "...world!"
  Rectangle {
  SlotsLayout.position: SlotsLayout.Leading
  color: "pink"
  height: units.gu(6)
  width: height
  }

  
  UbuntuColors.Orange should be Ubuntu.orange

  Best regards,
  XiaoGuo

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

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

[Touch-packages] [Bug 1569481] Re: ota 10.1 rotation lock disappeared

[Launchpad Bug Tracker]

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

** Changed in: indicator-display (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  ota 10.1 rotation lock disappeared

Status in indicator-display package in Ubuntu:
  Expired
Status in ubuntu-system-settings package in Ubuntu:
  Expired
Status in unity8 package in Ubuntu:
  Expired

Bug description:
  Hi all!
  After today's Ota 10.1, on my Aquaris E5, in the top bar, the "Rotation lock" 
page disappeared.
  I think images can give a better idea of what happened.

  Here you can see that the icon on the top disappeared:
  https://postimg.org/image/rs058nprd/

  And here's what the device displays between the "notification" and the "file" 
pages:
  https://postimg.org/image/sweoe1e2r/

  Thanks
  pgcor

  Edit: I just noticed I've surely mistaken the section where to post
  the bug, I'm very sorry, and I don't know how to  move it :(

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

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

[Touch-packages] [Bug 1551020] Re: IpUtils Ping can be in wait forever

[Launchpad Bug Tracker]

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

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

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

Title:
  IpUtils Ping can be in wait forever

Status in iputils package in Ubuntu:
  Expired

Bug description:
  Ping is using round trip time from previous incoming echo response
  packet to determine max waittime for next packet, but the validation
  of the value read from incoming echo response packet is poor. It only
  checks for non-negative values.

  To reproduce the Bug: 
  Step 1: Apply the following diff to the Ping command- (this simulates the 
condition that triptime value read from incoming echo response was some 
arbitrary large value)-
  diff -r iputils/ping_common.c iputils_ping_hang_repro/ping_common.c
  709c709,711
  <   triptime = tv->tv_sec * 100 + tv->tv_usec;
  ---
  >   /*SNAP: To repro Ping hang, set this value to some large long 
value. Since this is read from */
  >   /*  incoming echo reply and not validated for 0 or too 
large, this will cause hang/long wait.
  >   /* triptime = tv->tv_sec * 100 + tv->tv_usec; */
  >   triptime = 1000123456789;
  /tmp/diff.out (END)

  Step 2: Run the following ping command targeted at a host that is at
  first successfully replying to the Ping echo requests, but at some
  point during the execution (before the last ping echo request) take
  the target offline(to trigger the waittime).  This will cause Ping to
  set the waittime to tmax which is 2 X the max RTT which we just set to
  a very large value.

  sudo ./ping -c 10 -i 0.5 $TARGET_IP > /tmp/out.log

  
  AS A RESULT,

  1. The Ping will keep running for a few hundred years, no big deal. In
  strace there will be a periodic recvmsg to check for response every
  few ms, something like this-

  Process 11373 attached - interrupt to quit
  ...
  recvmsg(3, 0x7ffed06dc650, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(3, 0x7ffed06dc650, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(3, 0x7ffed06dc650, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  ...

  2. In the /proc/timer_list file I see a large value for the process' timer-
  ...
   #14: <>, it_real_fn, S:01, hrtimer_start, ping/11373
   # expires at 611433835413-611433835413 nsecs [in 2000179546163581 to 
2000179546163581 nsecs]
  ...

  So we can see that when a large timeval is read from the echo
  response, it is not validated.

  Possible causes for invalid timeval values could be:
  Malicious destination, buggy OS, Malformed packets, interference with echo 
response belonging to "traceroute" command but had the same ID and Seq No.

  Impact-
  Ping runs forever.

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

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

[Touch-packages] [Bug 1572061] Re: login sessions hangs in lxc

[Launchpad Bug Tracker]

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

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

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

Title:
  login sessions hangs in lxc

Status in lxc package in Ubuntu:
  Expired

Bug description:
  login to lxc container hangs after login prompt. This happends to randomly 
lxc container while other containers on same host work as expected. 
  Several protocols affected,  ssh, dovecot & smtp for example. DNS config is 
ok. lxc-attach -n name works and I'm able to reach outside network, do 
resolving etc.
  if I do a lxc-stop and start the container works again. after a day or two  
samething occurs again to a random container on the same host.
   Could it be some kind of apparmor blocking ?

  
  HostOs 
  Description:Ubuntu 16.04 LTS
  Release:16.04

  network mode

  iface br0 inet static
  bridge_ports eno1
   address x.x.x.x
  netmask 255.255.255.0
  network x.x.x.x
  broadcast x.x.x.x
  gateway x.x.x.x
  dns-nameservers x.x.x.x
  dns-search domain.com

  lxc-os ubuntu xenial &  debian jessie

  configured with static ip

  best regards
  Bjorn

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

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

[Touch-packages] [Bug 1569481] Re: ota 10.1 rotation lock disappeared

[Launchpad Bug Tracker]

[Expired for ubuntu-system-settings (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: ubuntu-system-settings (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  ota 10.1 rotation lock disappeared

Status in indicator-display package in Ubuntu:
  Expired
Status in ubuntu-system-settings package in Ubuntu:
  Expired
Status in unity8 package in Ubuntu:
  Expired

Bug description:
  Hi all!
  After today's Ota 10.1, on my Aquaris E5, in the top bar, the "Rotation lock" 
page disappeared.
  I think images can give a better idea of what happened.

  Here you can see that the icon on the top disappeared:
  https://postimg.org/image/rs058nprd/

  And here's what the device displays between the "notification" and the "file" 
pages:
  https://postimg.org/image/sweoe1e2r/

  Thanks
  pgcor

  Edit: I just noticed I've surely mistaken the section where to post
  the bug, I'm very sorry, and I don't know how to  move it :(

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

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

[Touch-packages] [Bug 1569481] Re: ota 10.1 rotation lock disappeared

[Launchpad Bug Tracker]

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

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

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

Title:
  ota 10.1 rotation lock disappeared

Status in indicator-display package in Ubuntu:
  Expired
Status in ubuntu-system-settings package in Ubuntu:
  Expired
Status in unity8 package in Ubuntu:
  Expired

Bug description:
  Hi all!
  After today's Ota 10.1, on my Aquaris E5, in the top bar, the "Rotation lock" 
page disappeared.
  I think images can give a better idea of what happened.

  Here you can see that the icon on the top disappeared:
  https://postimg.org/image/rs058nprd/

  And here's what the device displays between the "notification" and the "file" 
pages:
  https://postimg.org/image/sweoe1e2r/

  Thanks
  pgcor

  Edit: I just noticed I've surely mistaken the section where to post
  the bug, I'm very sorry, and I don't know how to  move it :(

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

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

[Touch-packages] [Bug 1497090] Re: Clients in Unity8 don't receive motion/hover mouse events

[Launchpad Bug Tracker]

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

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

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

Title:
  Clients in Unity8 don't receive motion/hover mouse events

Status in QtMir:
  Expired
Status in qtmir package in Ubuntu:
  Expired
Status in unity8 package in Ubuntu:
  Expired

Bug description:
  Clients don't receive motion/hover mouse events.

  Trying these demos under unity8:

     mir_demo_client_target -n--desktop_file_hint=unity8
     mir_demo_client_eglsquare -n -- --desktop_file_hint=unity8

  They kind of work, but they don't sense the mouse pointer moving over
  them like they do in the Mir demo servers. At least not till you hold
  a mouse button down.

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

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

[Touch-packages] [Bug 1598345] [NEW] /usr/bin/messaging-app:11:QScopedPointer:qGetPtrHelper:QOpenGLContext::d_func:QOpenGLContext::functions:QSGDefaultLayer::invalidated

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding messaging-app.  This problem was most recently seen with
version 0.1+15.04.20160624.1-0ubuntu1, the problem page at
https://errors.ubuntu.com/problem/916b22c9ba5704b6ef5214c22e3cc129b4636437
contains more details.

** Affects: messaging-app (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: vivid

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

Title:
  /usr/bin/messaging-
  
app:11:QScopedPointer:qGetPtrHelper:QOpenGLContext::d_func:QOpenGLContext::functions:QSGDefaultLayer::invalidated

Status in messaging-app package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding messaging-app.  This problem was most recently seen with
  version 0.1+15.04.20160624.1-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/916b22c9ba5704b6ef5214c22e3cc129b4636437
  contains more details.

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

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

[Touch-packages] [Bug 1598350] [NEW] /usr/bin/dialer-app:6:qt_message_fatal:QMessageLogger::fatal:qt_assert:UbuntuOpenGLContext::swapBuffers:QOpenGLContext::swapBuffers

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding dialer-app.  This problem was most recently seen with version
0.1+15.04.20160624.1-0ubuntu1, the problem page at
https://errors.ubuntu.com/problem/640a2bcb9733867fd866704fd4f7fa9d3b54988b
contains more details.

** Affects: dialer-app (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: vivid

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

Title:
  /usr/bin/dialer-
  
app:6:qt_message_fatal:QMessageLogger::fatal:qt_assert:UbuntuOpenGLContext::swapBuffers:QOpenGLContext::swapBuffers

Status in dialer-app package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding dialer-app.  This problem was most recently seen with
  version 0.1+15.04.20160624.1-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/640a2bcb9733867fd866704fd4f7fa9d3b54988b
  contains more details.

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

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

[Touch-packages] [Bug 1588123] Re: binutils - Bugzilla ID 20159

[Paul Braman]

Updated with proposed binutils in 16.04 and now software behaves
uniformly regardless of whether it was built on 14.04 or 16.04.

Package: binutils
Status: install ok installed
Priority: optional
Section: devel
Installed-Size: 13328
Maintainer: Ubuntu Core developers 
Architecture: amd64
Version: 2.26.1-1ubuntu1~16.04

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

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

Title:
  binutils - Bugzilla ID 20159

Status in binutils package in Ubuntu:
  Fix Released
Status in binutils source package in Xenial:
  Fix Committed

Bug description:
  Moved to Ubuntu 16.04 from Ubuntu 14.04 and was doing some Test Driven
  Development where we began to override the "time" system call from
  glibc. Failed on Ubuntu 16.04 and I filed a report with the binutils
  Bugzilla.

  https://sourceware.org/bugzilla/show_bug.cgi?id=20159

  (Turns out it was not dynamic linking that was the problem but GNU ld
  itself at link-time.)

  They have since developed a patch and I want to get this into the
  binutils 1.26 line that is maintained for 16.04 so we can continue to
  properly develop software on this distribution.

  Thanks!

  - Paul Braman

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

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

[Touch-packages] [Bug 1574020] Re: Can't use networkmanager from lightdm

[Bug Watch Updater]

** Changed in: network-manager
   Status: Confirmed => Invalid

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

Title:
  Can't use networkmanager from lightdm

Status in NetworkManager:
  Invalid
Status in network-manager package in Ubuntu:
  Confirmed
Status in unity-greeter package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 16.04  desktop (unity) (clean install) from 14.04,
  (so not really upgrading, but you get the point) I noticed that
  lightdm with unity-greeter (all stock, nothing changed) can't connect
  to WiFi with network-manager.

  WiFi works after loggin it, but it should be working before also, if
  not, what's the point in having an icon there :)

  I get the following message: Failed to add/activate connection. - (1) 
Insufficient privileges. - see image.
  This worked fine in 14.04.

  I have noticed this problem in both my desktop (Broadcom WiFi) and
  Laptop (Intel WiFi) - So it has nothing to be with the chip.

  Feel free to ask for more info.

  Edit:

  From syslog:

  Apr 23 16:50:46 desktop NetworkManager[979]: nm_settings_connection_delete: 
assertion 'NM_IS_SETTINGS_CONNECTION (self)' failed
  Apr 23 16:50:46 desktop NetworkManager[979]:   [1461423046.1662] audit: 
op="connection-add-activate" pid=1275 uid=108 result="fail" 
reason="Insufficient privileges."
  Apr 23 16:50:46 desktop NetworkManager[979]: (NetworkManager:979): 
GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' 
failed

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

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

[Touch-packages] [Bug 1543351] Re: Add on-screen-keyboard support for Xmir/Libertine apps

[Aiman]

Hi everybody,
The OSK work with Xapps. However I found that in Firefox the keyboard appears 
in user name fields but not in the password one.
It happened in gmail login and online banking site.

I have M10 FHD and use RC proposed channel.

I thougt to let you know.

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

Title:
  Add on-screen-keyboard support for Xmir/Libertine apps

Status in Canonical System Image:
  Fix Committed
Status in Canonical Pocket Desktop:
  Fix Committed
Status in Libertine:
  Fix Released
Status in Libertine devel series:
  Fix Released
Status in Libertine trunk series:
  Fix Released
Status in Ubuntu UX:
  New
Status in libertine package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  From perspective of product management - this is currently not a
  requirement, just want to capture it for future

  we currently can't interact with puritine apps relying on the OSK

  to add this feature in where text-box selection on an xapp results in
  triggering the osk, in unity8 would be a very large/complicated
  effort. However, with a manual capability to trigger the OSK this
  could be achieved.

  For design team
  one idea was to add a show/hide button for the OSK.
  realizing this may be undesirable to add another indicator item - a follow-on 
idea might be to add an alpha button in the corner of the xmir-root window (the 
window that holds any xapp at the moment)
  this way the button presence would only be limited to the Xapp interaction.

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

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

[Touch-packages] [Bug 1575078] Re: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while

[Cruz Fernandez]

Regarding @shinyblue , on my configuration (lightdm/unity), sounds seems
to work in all cases (new kernel 4.4.0-28-generic).

Only caveat I want to mention is that System Settings->Sound->Output
shows two options with headphone connected, and selecting "Speakers.
Built-in Audio" just mutes and produces no sound.

I'm tempted to report that last caveat in a new bug, but I'm not sure if
it was one of the original problems reported by @ivan.koptiev and he
didn't realize about this current limitation.

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

Title:
  [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a
  while

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I'm experiencing a strange behavior with a headphone jack on my
  laptop.

  I have an external audio speaker connected to it. When I disconnect the 
speaker and reconnect it again it stops working.
  Even more, laptop audio stops working too. And after the reboot, I don't even 
see any of the audio devices.

  I've googled a lot and tried different fixes from forums with no luck.
  After a while, I've accidentally discovered that putting the laptop to
  the sleep mode and rebooting system after brings audio back to live.
  Even more, if speakers were attached during this sleep-reboot
  procedure, they are starting to work as well.

  However, after the next reboot speakers are not working again. And if
  I will plug them out and in - problem with completely missing audio
  returns.

  P.S. I'm using laptop-mode-tools package on my laptop. Recovery after
  hibernation made me believe that it's somehow related. But after
  uninstalling this package nothing really changed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   kop3224 F...m pulseaudio
   /dev/snd/controlC0:  kop3224 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Apr 26 12:17:03 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (3 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Встроенное аудио - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: Sound works for a while, then breaks
  Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] fails after 
a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1443052] Re: User accounts login history showing incorrect history

[Bug Watch Updater]

** Changed in: gnome-control-center
   Status: Confirmed => Unknown

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

Title:
  User accounts login history showing incorrect history

Status in accountsservice:
  Unknown
Status in gnome-control-center:
  Unknown
Status in Ubuntu GNOME:
  Confirmed
Status in accountsservice package in Ubuntu:
  New
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  I have found that in "System Settings > User Accounts" that if you
  select an account and then select the button called "History" (which
  is meant to show the login history for that account), it will show you
  when you last logged in as "Session Started", but it will show that
  you "Session Ended" just before you login the next time.

  To clarify what I mean, let's say that yesterday I logged into my
  account on this machine at 14:29, and then sometime near 23:00 I
  logged out, and then this morning I logged into my account somewhere
  around 11:20, it will show this:

  Today 11:20 Session Started
  Today 11:19 Session Ended
  Yesterday, 14:29 Session Started

  So it assumes that the last session ended when you log into a new one,
  so the bug seems to be that it does not log when a session ends
  properly, and only logs it when a new session starts.

  I have attached a screenshot to show my example as I see it in the
  History GUI.

  I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04,
  Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME
  3.20.

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

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

[Touch-packages] [Bug 1542033] Re: avahi-daemon doesn't start

[Alberto Salvia Novella]

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

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

Title:
  avahi-daemon doesn't start

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  While upgrading from 14.04 to 16.04 yesterday, I notived that avahi-
  daemon doesn't start.

  Log:
  Feb 04 22:00:15 michis-ibm-haupt systemd[1]: Starting Avahi mDNS/DNS-SD 
Stack...
  -- Subject: Unit avahi-daemon.service has begun start-up
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  -- 
  -- Unit avahi-daemon.service has begun starting up.
  Feb 04 22:00:15 michis-ibm-haupt audit[13101]: AVC apparmor="DENIED" 
operation="open" profile="/usr/sbin/avahi-daemon" name="/etc/ld.so.preload" 
pid=13101 comm="avahi-daemon" requested_mask="r" denied_ma
  Feb 04 22:00:15 michis-ibm-haupt kernel: audit: type=1400 
audit(1454619615.281:301): apparmor="DENIED" operation="open" 
profile="/usr/sbin/avahi-daemon" name="/etc/ld.so.preload" pid=13101 
comm="avahi-da
  Feb 04 22:00:15 michis-ibm-haupt kernel: audit: type=1400 
audit(1454619615.285:302): apparmor="DENIED" operation="chown" 
profile="/usr/sbin/avahi-daemon" name="/run/avahi-daemon/" pid=13101 
comm="avahi-d
  Feb 04 22:00:15 michis-ibm-haupt audit[13101]: AVC apparmor="DENIED" 
operation="chown" profile="/usr/sbin/avahi-daemon" name="/run/avahi-daemon/" 
pid=13101 comm="avahi-daemon" requested_mask="w" denied_m
  Feb 04 22:00:15 michis-ibm-haupt avahi-daemon[13101]: Failed to create 
runtime directory /var/run/avahi-daemon/.
  Feb 04 22:00:15 michis-ibm-haupt systemd[1]: avahi-daemon.service: Main 
process exited, code=exited, status=255/n/a
  Feb 04 22:00:15 michis-ibm-haupt systemd[1]: Failed to start Avahi 
mDNS/DNS-SD Stack.

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

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

[Touch-packages] [Bug 1576565] Re: HDMI Sound drops out after screen blank/suspend (must use pacmd to reset0

[Alberto Salvia Novella]

** Changed in: alsa-driver (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  HDMI Sound drops out after screen blank/suspend (must use pacmd to
  reset0

Status in ALSA driver:
  New
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sound is outputted through HDMI. Upon suspend/resume or resume from
  screen blank, output switches to analog and HDMI is not an available
  option from the GUI although still listed using "aplay-l". Sound
  returns after resetting HDMI as default using the following command:
  pacmd set-card-profile 1 output:hdmi-stereo-extra1+input:analog-stereo

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 29 09:52:09 2016
  InstallationDate: Installed on 2015-12-15 (135 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: Sound works for a while, then breaks
  Title: [, Intel CougarPoint HDMI, Digital Out, HDMI] fails after a while
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (6 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67GD
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10206-210
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67GD:rvrAAG10206-210:cvn:ct3:cvr:

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

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

[Touch-packages] [Bug 1594587] Re: package keyboard-configuration 1.108ubuntu15.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Alberto Salvia Novella]

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

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

Title:
  package keyboard-configuration 1.108ubuntu15.2 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 128

Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  Running update manager and suddenly its freezing.

  Running back update manager giving the following problem.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: keyboard-configuration 1.108ubuntu15.2
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Tue Jun 21 05:50:37 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2016-03-30 (82 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: console-setup
  Title: package keyboard-configuration 1.108ubuntu15.2 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 128
  UpgradeStatus: Upgraded to xenial on 2016-04-14 (67 days ago)
  modified.conffile..etc.init.d.keyboard-setup: [deleted]

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

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

[Touch-packages] [Bug 1594035] Re: unable to shut down the system after suspend / resume

[Alberto Salvia Novella]

** Changed in: systemd (Ubuntu)
   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/1594035

Title:
  unable to shut down the system after suspend / resume

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  In the case of a system that has gone through a suspend / resume
  cycle, the "shutdown now" command fails with the following output:

  $ shutdown now
  Failed to power off system via logind: Transaction is destructive.
  Failed to start poweroff.target: Interactive authentication required.
  See system logs and 'systemctl status poweroff.target' for details.
  Failed to open /dev/initctl: Permission denied
  Failed to talk to init daemon.

  ---

  $ systemctl status poweroff.target
  ● poweroff.target - Power-Off
 Loaded: loaded (/lib/systemd/system/poweroff.target; disabled; vendor 
preset:
 Active: inactive (dead)
   Docs: man:systemd.special(7)

  ---

  $ systemctl list-jobs
  JOB UNIT  TYPE  STATE  
  438 dev-mapper-cryptswap1.device  start running
  439 dev-mapper-cryptswap1.swapstart waiting
  436 systemd-cryptsetup@cryptswap1.service start running

  3 jobs listed.

  ---

  Steps to reproduce:

  1. Boot system
  2. User login to graphical session
  3. Close lid while on battery power triggering a suspend
  4. Open lid while on battery power triggering a resume
  5. Run "shutdown now" from a terminal. Note that the command must be run from 
the terminal to see output. Selecting "Shut Down..." from the system menu in 
the menu bar will hide the error output.
  6. Observe that the system fails to shut down

  Expected behavior:

  At step 6, the system should shut down gracefully.

  Note that the shutdown process works as expected if steps 3 and 4 are
  skipped. I suspect that something about the suspend / resume cycle
  during the session has an interaction effect with the shutdown
  process, preventing it from executing correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun 18 18:04:26 2016
  EcryptfsInUse: Yes
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b550 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System76, Inc. Lemur
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed 
root=UUID=7aecd352-8a3f-4ce9-88b8-0fc048dc9660 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/29/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06RS76
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Lemur
  dmi.board.vendor: System76, Inc.
  dmi.board.version: lemu6
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06RS76:bd11/29/2015:svnSystem76,Inc.:pnLemur:pvrlemu6:rvnSystem76,Inc.:rnLemur:rvrlemu6:cvnSystem76,Inc.:ct10:cvrN/A:
  dmi.product.name: Lemur
  dmi.product.version: lemu6
  dmi.sys.vendor: System76, Inc.

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

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

[Touch-packages] [Bug 1575899] Re: Text disappears after suspend

[Christopher M. Penalver]

Henrik Blidh, to further root cause, if you boot into a 4.2.x kernel
(the one from Ubuntu 15.10) does the issue go away?

** Tags added: regression-release

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

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

Title:
  Text disappears after suspend

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After waking my laptop running Xenial after it having been suspended,
  a lot of applications (e.g. Terminal and all settings) does not render
  most of the text that should be there. Some of it shows up on
  mouseover, but most is just permanently invisible until reboot of
  system.

  Detected a very similar bug after I created this issue:
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1528843

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Apr 27 21:44:36 2016
  DistUpgraded: 2016-04-25 10:36:20,651 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics 
Controller [1043:13bd]
  InstallationDate: Installed on 2015-09-05 (234 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 03eb:8a0c Atmel Corp.
   Bus 001 Device 003: ID 1bcf:2987 Sunplus Innovation Technology Inc.
   Bus 001 Device 005: ID 8087:07dc Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX301LAA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=6cc41411-46cb-4a14-a79a-038ee820f1aa ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-25 (2 days ago)
  dmi.bios.date: 12/31/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX301LAA.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX301LAA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX301LAA.206:bd12/31/2013:svnASUSTeKCOMPUTERINC.:pnUX301LAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX301LAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX301LAA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Apr 27 16:42:36 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5126
   vendor SHP
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Touch-packages] [Bug 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in [XPS 15 9550]

[Alberto Salvia Novella]

** Changed in: alsa-driver (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  No sound via headphones (headset) when Ubuntu boots with them plugged
  in [XPS 15 9550]

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The bug is twofold, first when computer boots if the headset
  (headphones with built-in mic, one audio jack) is plugged in, then
  there is no sound (via headphones or otherwise). If you plug
  headphones out and back in, then it usually works as expected.

  The second scenario is the same, except that plugging out and back in
  again doesn't help. In that case, I just restart the laptop, then plug
  them back in again and it works.

  In all cases, microphone works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 19 22:13:20 2016
  InstallationDate: Installed on 2016-05-07 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 962616] Re: mii-tool assumes NIC names of the form eth* when given no interface(s) as argument

[Alberto Salvia Novella]

** Changed in: net-tools (Ubuntu)
   Importance: Undecided => High

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

Title:
  mii-tool assumes NIC names of the form eth* when given no interface(s)
  as argument

Status in net-tools package in Ubuntu:
  Confirmed

Bug description:
  On a system with biosdevname enabled, which names NICs in the forms
  em* and p*p*, mii-tool will return the message "no MII interfaces
  found" if mii-tool is called without specifying an interface. The
  correct behavior would be to iterate through em* and p*p*. (More
  information on biosdevname can be found at
  
http://linux.dell.com/files/whitepapers/consistent_network_device_naming_in_linux.pdf.)

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

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

[Touch-packages] [Bug 1591411] Re: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay

[Alberto Salvia Novella]

** Changed in: systemd (Ubuntu)
   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/1591411

Title:
  systemd-logind must be restarted every ~1000 SSH logins to prevent a
  ~25 second delay

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I noticed on a system that accepts large numbers of SSH connections
  that after awhile, SSH sessions were taking ~25 seconds to complete.

  Looking in /var/log/auth.log, systemd-logind starts failing with the
  following:

  Jun 10 23:55:28 test sshd[3666]: pam_unix(sshd:session): session opened for 
user ubuntu by (uid=0)
  Jun 10 23:55:28 test systemd-logind[105]: New session c1052 of user ubuntu.
  Jun 10 23:55:28 test systemd-logind[105]: Failed to abandon session scope: 
Transport endpoint is not connected
  Jun 10 23:55:28 test sshd[3666]: pam_systemd(sshd:session): Failed to create 
session: Message recipient disconnected from message bus without replying

  I reproduced this in an LXD container by doing something like:

  lxc launch ubuntu:x test
  lxc exec test -- login -f ubuntu
  ssh-import-id 

  Then ran a script as follows (passing in ubuntu@):

  while [ 1 ]; do
  (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log
  done

  In my case, after 1052 logins, the 1053rd and thereafter were taking
  25+ seconds to complete. Here are some snippets from the log file:

  $ cat log | grep 0m0 | wc -l
  1052

  $ cat log | grep 0m25 | wc -l
  4

  $ tail -5 log
  real  0m0.222s
  real  0m25.232s
  real  0m25.235s
  real  0m25.236s
  real  0m25.239s

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Jun 11 00:09:34 2016
  MachineType: Notebook W230SS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W230SS
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W230SS
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

[Touch-packages] [Bug 1570157] Re: ubuntu session: missing channels & search items

[Amr Ibrahim]

** Changed in: grilo-plugins (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 grilo-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1570157

Title:
  ubuntu session: missing channels & search items

Status in grilo-plugins package in Ubuntu:
  Fix Released

Bug description:
  In a gnome session there are 5 channels & 7 search items.
  In an ubuntu session there is 1 channel & 5 search items

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: totem 3.18.1-1ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 13 21:57:14 2016
  InstallationDate: Installed on 2016-02-06 (67 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1598153] Re: ubuntu 16.04 thinkpad t560 死机

[Tyler Hicks]

** Information type changed from Private Security to Public

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

Title:
  ubuntu 16.04  thinkpad t560 死机

Status in xorg package in Ubuntu:
  New

Bug description:
  刚完全重新安装完成的系统用一段时间都有可能死机。查日志无明显错误信息！
  系统硬件如下：
  00:00.0 Host bridge: Intel Corporation Sky Lake Host Bridge/DRAM Registers 
(rev 08)
  00:02.0 VGA compatible controller: Intel Corporation Sky Lake Integrated 
Graphics (rev 07)
  00:08.0 System peripheral: Intel Corporation Sky Lake Gaussian Mixture Model
  00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller (rev 21)
  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP 
Thermal subsystem (rev 21)
  00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME 
HECI (rev 21)
  00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller 
[AHCI mode] (rev 21)
  00:1c.0 PCI bridge: Intel Corporation Device 9d10 (rev f1)
  00:1c.2 PCI bridge: Intel Corporation Device 9d12 (rev f1)
  00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21)
  00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
  00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
  00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
  00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection I219-LM 
(rev 21)
  02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI 
Express Card Reader (rev 01)
  04:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.4.14-040414-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Jul  1 20:18:17 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: tp-smapi, 0.41, 4.4.14-040414-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Skylake Integrated Graphics [17aa:2231]
  InstallationDate: Installed on 2016-07-01 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 138a:0017 Validity Sensors, Inc. Fingerprint Reader
   Bus 001 Device 004: ID 04f2:b52c Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 17ef:6050 Lenovo 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FHCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.14-040414-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/10/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1KET19W (1.06 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1KET19W(1.06):bd03/10/2016:svnLENOVO:pn20FHCTO1WW:pvrThinkPadT560:rvnLENOVO:rn20FHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FHCTO1WW
  dmi.product.version: ThinkPad T560
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Jul  1 19:06:20 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   38562 
   vendor MEI
  xserver.version: 2:1.18.3-1ubuntu2.2

To manage notifications about this bug go to:

[Touch-packages] [Bug 1594035] Re: unable to shut down the system after suspend / resume

[Donald Pellegrino]

As noted by @loyeyoung, a better work-around than the one in Comment #2
may be to disable swap rather than running with an encrypted home
directory and unencrypted swap as that state is a security liability.
For the case where hibernate depends on swap, hibernate would also need
to be disabled.

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

Title:
  unable to shut down the system after suspend / resume

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  In the case of a system that has gone through a suspend / resume
  cycle, the "shutdown now" command fails with the following output:

  $ shutdown now
  Failed to power off system via logind: Transaction is destructive.
  Failed to start poweroff.target: Interactive authentication required.
  See system logs and 'systemctl status poweroff.target' for details.
  Failed to open /dev/initctl: Permission denied
  Failed to talk to init daemon.

  ---

  $ systemctl status poweroff.target
  ● poweroff.target - Power-Off
 Loaded: loaded (/lib/systemd/system/poweroff.target; disabled; vendor 
preset:
 Active: inactive (dead)
   Docs: man:systemd.special(7)

  ---

  $ systemctl list-jobs
  JOB UNIT  TYPE  STATE  
  438 dev-mapper-cryptswap1.device  start running
  439 dev-mapper-cryptswap1.swapstart waiting
  436 systemd-cryptsetup@cryptswap1.service start running

  3 jobs listed.

  ---

  Steps to reproduce:

  1. Boot system
  2. User login to graphical session
  3. Close lid while on battery power triggering a suspend
  4. Open lid while on battery power triggering a resume
  5. Run "shutdown now" from a terminal. Note that the command must be run from 
the terminal to see output. Selecting "Shut Down..." from the system menu in 
the menu bar will hide the error output.
  6. Observe that the system fails to shut down

  Expected behavior:

  At step 6, the system should shut down gracefully.

  Note that the shutdown process works as expected if steps 3 and 4 are
  skipped. I suspect that something about the suspend / resume cycle
  during the session has an interaction effect with the shutdown
  process, preventing it from executing correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun 18 18:04:26 2016
  EcryptfsInUse: Yes
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b550 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System76, Inc. Lemur
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed 
root=UUID=7aecd352-8a3f-4ce9-88b8-0fc048dc9660 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/29/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06RS76
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Lemur
  dmi.board.vendor: System76, Inc.
  dmi.board.version: lemu6
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06RS76:bd11/29/2015:svnSystem76,Inc.:pnLemur:pvrlemu6:rvnSystem76,Inc.:rnLemur:rvrlemu6:cvnSystem76,Inc.:ct10:cvrN/A:
  dmi.product.name: Lemur
  dmi.product.version: lemu6
  dmi.sys.vendor: System76, Inc.

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

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

[Touch-packages] [Bug 1342400] Re: avahi-daemon constantly reporting "Invalid response packet from host"

[Mathew Hodson]

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

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

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

Title:
  avahi-daemon constantly reporting "Invalid response packet from host"

Status in avahi package in Ubuntu:
  Fix Released
Status in avahi source package in Precise:
  Fix Committed
Status in avahi source package in Trusty:
  Fix Committed
Status in avahi package in Debian:
  Fix Released

Bug description:
  After installing Ubuntu 14.04 (Release: 14.04) and looking for other
  information in /var/log/syslog, I see that syslog is being flooded by
  "Invalid response packet from host" messages from avahi-daemon.

  I searched around to see why this might be and ran across the following avahi 
mailing list post along with a patch to fix it:
  http://lists.freedesktop.org/archives/avahi/2012-July/002171.html

  >>>
  I would say you can safely ignore it, since any machine on your
  network running a recent OSX version will cause these messages.
  Here's a patch with what we change to avoid these messages flooding
  syslog.

  -Justin
  <<<

  The patch which fixes this is here:
  
http://lists.freedesktop.org/archives/avahi/attachments/20120719/1e71846e/attachment.obj

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

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

[Touch-packages] [Bug 1574020] Re: Can't use networkmanager from lightdm

[Vincent Cheng]

A use case is that I would like to be able to ssh into my Ubuntu 16.04
laptop when I'm logged out, which is of course only possible if it's
connected to a network.

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

Title:
  Can't use networkmanager from lightdm

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in unity-greeter package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 16.04  desktop (unity) (clean install) from 14.04,
  (so not really upgrading, but you get the point) I noticed that
  lightdm with unity-greeter (all stock, nothing changed) can't connect
  to WiFi with network-manager.

  WiFi works after loggin it, but it should be working before also, if
  not, what's the point in having an icon there :)

  I get the following message: Failed to add/activate connection. - (1) 
Insufficient privileges. - see image.
  This worked fine in 14.04.

  I have noticed this problem in both my desktop (Broadcom WiFi) and
  Laptop (Intel WiFi) - So it has nothing to be with the chip.

  Feel free to ask for more info.

  Edit:

  From syslog:

  Apr 23 16:50:46 desktop NetworkManager[979]: nm_settings_connection_delete: 
assertion 'NM_IS_SETTINGS_CONNECTION (self)' failed
  Apr 23 16:50:46 desktop NetworkManager[979]:   [1461423046.1662] audit: 
op="connection-add-activate" pid=1275 uid=108 result="fail" 
reason="Insufficient privileges."
  Apr 23 16:50:46 desktop NetworkManager[979]: (NetworkManager:979): 
GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' 
failed

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

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

[Touch-packages] [Bug 1598303] [NEW] No HDMI sound with ATI Radeon HD 8570D & Asus VS238H-P Monitor

[Mopar1973Man]

Public bug reported:

As stated I've got a ATI Radeon HD 8570D video card with HDMI port. The
video part works fine but the audio does not function. The monitor
volume is turned up to 100%. Alsamixer shows 00 and unadjustable for the
volume control for this port. This is a Asus A78M-A motherboard with a
AMD A8-6600K APU with Radeon(tm) HD Graphics.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11
Uname: Linux 4.2.0-41-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  michael2148 F pulseaudio
 /dev/snd/pcmC1D0p:   michael2148 F...m pulseaudio
 /dev/snd/controlC1:  michael2148 F pulseaudio
CurrentDesktop: Unity
Date: Fri Jul  1 15:03:53 2016
InstallationDate: Installed on 2016-06-12 (19 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1)
PackageArchitecture: all
SourcePackage: alsa-driver
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/05/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1204
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: A78M-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1204:bd12/05/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA78M-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug trusty

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

Title:
  No HDMI sound with ATI Radeon HD 8570D & Asus VS238H-P Monitor

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  As stated I've got a ATI Radeon HD 8570D video card with HDMI port.
  The video part works fine but the audio does not function. The monitor
  volume is turned up to 100%. Alsamixer shows 00 and unadjustable for
  the volume control for this port. This is a Asus A78M-A motherboard
  with a AMD A8-6600K APU with Radeon(tm) HD Graphics.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11
  Uname: Linux 4.2.0-41-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael2148 F pulseaudio
   /dev/snd/pcmC1D0p:   michael2148 F...m pulseaudio
   /dev/snd/controlC1:  michael2148 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Jul  1 15:03:53 2016
  InstallationDate: Installed on 2016-06-12 (19 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/05/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1204
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A78M-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1204:bd12/05/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA78M-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1575899] Re: Text disappears after suspend

[Henrik Blidh]

I had Ubuntu Desktop 15.10 installed on the laptop prior to 16.04, and
upgraded using the update-manager. I did not have this problem before.

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

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

Title:
  Text disappears after suspend

Status in xorg package in Ubuntu:
  New

Bug description:
  After waking my laptop running Xenial after it having been suspended,
  a lot of applications (e.g. Terminal and all settings) does not render
  most of the text that should be there. Some of it shows up on
  mouseover, but most is just permanently invisible until reboot of
  system.

  Detected a very similar bug after I created this issue:
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1528843

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Apr 27 21:44:36 2016
  DistUpgraded: 2016-04-25 10:36:20,651 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics 
Controller [1043:13bd]
  InstallationDate: Installed on 2015-09-05 (234 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 03eb:8a0c Atmel Corp.
   Bus 001 Device 003: ID 1bcf:2987 Sunplus Innovation Technology Inc.
   Bus 001 Device 005: ID 8087:07dc Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX301LAA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=6cc41411-46cb-4a14-a79a-038ee820f1aa ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-25 (2 days ago)
  dmi.bios.date: 12/31/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX301LAA.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX301LAA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX301LAA.206:bd12/31/2013:svnASUSTeKCOMPUTERINC.:pnUX301LAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX301LAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX301LAA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Apr 27 16:42:36 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5126
   vendor SHP
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Touch-packages] [Bug 1588349] Re: Checking for updates never finishes on 3G

[Pat McGowan]

I was not able to reproduce it, perhaps the cellular data connection is
not really active?

** Changed in: canonical-devices-system-image
   Status: Confirmed => Incomplete

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

Title:
  Checking for updates never finishes on 3G

Status in Canonical System Image:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  If I'm using wi-fi and go to settings and then select updates, "Checking for 
updates..." screen appears with a spinner for a few seconds; if there is any 
update available it shows, otherwise informs about the unavailability of 
updates.
  But while using mobile data (3G/H) *if there is no update available*, it gets 
stuck on the "Checking for updates..." screen and the spinner keeps spinning. I 
waited as long as 10-15 minutes.
  Note: If there is an update available then the behaviour is normal, i.e. 
shows the available update(s) after a few seconds.
  I'm seeing this behaviour from the very beginning (OTA-6 days).

  Related to bug #1528886

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

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

[Touch-packages] [Bug 1588349] Re: Checking for updates never finishes on 3G

[Pat McGowan]

Seems the fix from the referenced bug regressed

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

** Changed in: canonical-devices-system-image
   Importance: Undecided => High

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => John McAleely (john.mcaleely)

** Changed in: qtbase-opensource-src (Ubuntu)
 Assignee: (unassigned) => Lorn Potter (lorn-potter)

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

Title:
  Checking for updates never finishes on 3G

Status in Canonical System Image:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  If I'm using wi-fi and go to settings and then select updates, "Checking for 
updates..." screen appears with a spinner for a few seconds; if there is any 
update available it shows, otherwise informs about the unavailability of 
updates.
  But while using mobile data (3G/H) *if there is no update available*, it gets 
stuck on the "Checking for updates..." screen and the spinner keeps spinning. I 
waited as long as 10-15 minutes.
  Note: If there is an update available then the behaviour is normal, i.e. 
shows the available update(s) after a few seconds.
  I'm seeing this behaviour from the very beginning (OTA-6 days).

  Related to bug #1528886

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

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

[Touch-packages] [Bug 1598300] [NEW] cups hang after a while

[dominix]

Public bug reported:

after 6 minutes or so, cups is not responding.
it do not produce error on the log, just stop working, worse, it exit with 0

⌌—⌍
|root@cupsmachine :~# systemctl status cups 
  |
|● cups.service - CUPS Scheduler
  |
|   Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: 
enabled)|
|   Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago   
  |
| Docs: man:cupsd(8)
  |
|  Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, status=0/SUCCESS)  
  |
| Main PID: 28686 (code=exited, status=0/SUCCESS)   
  |
|   
  |
|juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler. 
  |
⌎—⌏

I got to launch it again, so I have finish with a cron job like
*/10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && 
systemctl start cups

but it is a dirty solution. I have no idea of what make it stop.
NB: I have seen problems related to apparmor, this machine has no apparmor 
package.

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

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

Title:
  cups hang after a while

Status in cups package in Ubuntu:
  New

Bug description:
  after 6 minutes or so, cups is not responding.
  it do not produce error on the log, just stop working, worse, it exit with 0

  
⌌—⌍
  |root@cupsmachine :~# systemctl status cups   
|
  |● cups.service - CUPS Scheduler  
|
  |   Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: 
enabled)|
  |   Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago 
|
  | Docs: man:cupsd(8)  
|
  |  Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, 
status=0/SUCCESS)|
  | Main PID: 28686 (code=exited, status=0/SUCCESS) 
|
  | 
|
  |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler.   
|
  
⌎—⌏

  I got to launch it again, so I have finish with a cron job like
  */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && 
systemctl start cups

  but it is a dirty solution. I have no idea of what make it stop.
  NB: I have seen problems related to apparmor, this machine has no apparmor 
package.

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

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

[Touch-packages] [Bug 1588312] Re: [vegeta]camera app crashed while saving video in full SD card

[Pat McGowan]

** Also affects: camera-app (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Bill Filler (bfiller)

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

Title:
  [vegeta]camera app crashed while saving video in full SD card

Status in Canonical System Image:
  Confirmed
Status in camera-app package in Ubuntu:
  New

Bug description:
  Product: bq Aquaris E5 
  FW version: OTA-11
  HW version: MP

  Preconditions: 
  - Insert full SD card

  STEPS TO REPRO:
  1. Open camera app and switch to video mode
  2. Select SD card to save videos(once I did it, a warning pop up appears 
informing about space and recommend to format SD card)
  3. Record a video 

  Actual Result:
  When I wanted to stop recording the camera app got frozen(watch vídeo 
attached)

  Expected Result:
  Camera app shouldn't try to save video if SD or internal memory is full, and 
it should not freeze

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

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

[Touch-packages] [Bug 1587965] Re: [OTA11][m10] long swipe or home button doesn't "mazimize" dash

[Pat McGowan]

All 3 are working here for me on rc-proposed, and I don't recall the gestures 
not working
what are gestures 2 and 3 doing on your device?

** Changed in: canonical-devices-system-image
   Status: New => Incomplete

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Michał Sawicz (saviq)

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

Title:
  [OTA11][m10] long swipe or home button doesn't "mazimize" dash

Status in Canonical System Image:
  Incomplete
Status in unity8 package in Ubuntu:
  New

Bug description:
  1) swipe from outside of the screen from the right to get the apps that are 
opened
  2) outside long swipe from the left, moves the most left app to move to the 
right but it doesn't "maximize" main scope.
  3) outside short swipe from the left shows dash but tapping on home button 
has no effect (before it was "maximizing" main scope)

  PS: All in all good work, OTA 11 feels really faster!

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

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

[Touch-packages] [Bug 1588237] Re: inconsistent behaviour of the numblock

[Pat McGowan]

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Stephen M. Webb (bregma)

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

Title:
  inconsistent behaviour of the numblock

Status in Canonical System Image:
  Confirmed
Status in mir package in Ubuntu:
  New

Bug description:
  How to reproduce:
  M10 with external Keyboard and Screen, after restart on OTA11.
  To use numbers in the unlock screen, the num key has to be active.
  After unlocking, use a search field in the homescope or any other scope.

  Expected behaviour:
  The numblock should work, as the num key is still active.

  Actual behaviour:
  The numblock only works, when you deactivate the num key.

  This is the same for the browserbar or the telegram chat.
  After some time, the behaviour changes, so the numblock behaviour seems to be 
inconsistent.

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

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

[Touch-packages] [Bug 1587525] Re: [address-book] contacts duplicated

[Pat McGowan]

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Bill Filler (bfiller)

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

Title:
  [address-book] contacts duplicated

Status in Canonical System Image:
  Confirmed
Status in address-book-app package in Ubuntu:
  New

Bug description:
  After inserting the SIM (with contacts already) and several
  synchronizations with google contacts, now i have many duplicated
  contacts and no easy way to remove then other than delete one by one.

  please allow one to sync back to google, so we can merge contacts and
  allow one to remove contacts not in the google contact list

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

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

[Touch-packages] [Bug 1587016] Re: Tap / Swipe don't work well

[Pat McGowan]

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Bill Filler (bfiller)

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

Title:
  Tap / Swipe don't work well

Status in Canonical System Image:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  Browsing the Web or using Web Apps like Twitter are not really
  pleasant on my BQ E5 HD with OTA-10. At least 50 per cent of the time
  when I want to scroll up or down the page using my index finger, the
  phone reacts by following a link below my finger where I start the
  swiping/scrolling.

  To me it seems like Ubuntu interprets a gesture as a tap way too
  early.

  If you want to try, visit a page like msn.com, yahoo news or
  spiegel.de and try to just scroll the page without accidentally
  following any of the links to the full article or some ad.

  This is really annoying for me as I constantly need to go back and
  retry my scrolling. Feels like the phone does what it wants instead of
  doing what I want.

  I suspect this is just a question of a few additional milliseconds
  more to wait if a touch gesture is a swipe or a tap. I am quite sure
  this is not (only) my fault, because I owned an iPhone and an Android
  tablet and very rarely expereinced similar problems.

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

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

[Touch-packages] [Bug 914507] Re: Feature Request: special Browser window for logging in to WiFi Hotspots

[Pat McGowan]

Gaining a lot of heat with dupes

** Changed in: canonical-devices-system-image
   Importance: Undecided => Wishlist

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Bill Filler (bfiller)

** Changed in: canonical-devices-system-image
Milestone: None => backlog

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

Title:
  Feature Request: special Browser window for logging in to WiFi
  Hotspots

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Problem occurs with: Ubuntu, all versions
  Does not occur with: Fedora 21 and later, elementary OS 0.3 and later, OS X 
10.7 and later

  WiFi Hotspots normally redirect all traffic to a special IP address which 
provides a Welcome page with a login form. Accessing this server with another 
protocol does not work, which is not a problem for POP3, IMAP or SSH, but it is 
a problem if you connect by https, because your browser will recognise the 
wrong security certificate or the port is not even used (which is even better 
in my opinion).
  1) So if I open a browser it automatically tries to open its Start page which 
is https in my case (I use the HTTPS Everywhere plugin in my firefox). Because 
it uses https, I will not be redirected to the login page and am waiting in 
front of an empty page. Then I manually have to open a link which does not use 
https and get redirected to the login page.
  2) Another annoying thing are other users who open a saved browser session. 
All saved (http-)tabs will be redirected to the welcome page so that it does 
not make any sense anymore to save the browser session.
  3) Firefox also sometimes does compatibility checks and plugin updates at 
start time. These also fail when trying to login to a Hotspot network.

  How can we solve this problem?

  First, network manager should check if the connected wireless network is a 
Hotspot network. This chan be done by a simple http request to a stable and 
well-known page, for example http://gnome.org/netcheck which returns a known 
token (something like "Yes, you are connected to the Internet").
  - If the token is returned, everything is fine and the user has connection
  - If it does not receive this token but a redirect, it should open a special 
browser-window (not the default browser because of the reasons above) which 
allows to log-in to the network before other internet applications are started.
  - In any other case, network manager could try another server (backup) or 
stop probing.

  For known wireless networks, network manager could also provide a
  setting to disable/autodetect/force hotspot login.

  : "Whenever Ubuntu
  makes a new network connection, if 'Prompt whenever a new connection
  requires Web login' is checked, it should perform HTTP and DNS checks
  that the connection is valid. If it is not..."

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

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

[Touch-packages] [Bug 1586800] Re: Captive portal experience is bad

[Pat McGowan]

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

** This bug has been marked a duplicate of bug 914507
   Feature Request: special Browser window for logging in to WiFi Hotspots

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

Title:
  Captive portal experience is bad

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  If you connect to a wifi AP that uses a captive portal (a login screen
  before granting full internet access, often seen in cafes and hotels)
  with your phone, the experience is quite lacking right now.

  - Webapps won't work. They try to connect to their site, are smart
  enough to know something is wrong when it doesn't get the right site
  back, and never finishes loading anything.

  - Apps in general fail to gracefully handle the case of getting back
  an unexpected result to their connections.

  - You may very reasonably auto connect to a wifi AP and not receive
  notifications for internet services like Telegram until you log in to
  the portal or turn off wifi.

  - If Browser is closed or OOM, when you open it, the last page you
  were at is overridden with the captive portal page. That's lost
  information! I hope you remember what it was.

  - If whatever page you try to go to first on the captive portal
  happens to be an https site, you will get an error instead of the
  portal.

  - If you know what to expect with the captive portal, you basically
  have to open a new browser tab and navigate to a site you have no
  intention of actually using just to get the log in page. It's a bit of
  a farce and not a great UX.

  - If you are *trying* to trigger the captive portal but the site you
  try happens to be cached (in some way? DNS or content caching or
  something), you will see that cached page instead of the portal. Which
  is unexpected for you. (I *think* this happens, maybe I am
  misremembering though.)

  And there are probably more pain points involved. This is just off the
  top of my head. Can we please guide the user through this experience
  instead of leaving them with a system that acts busted?

  Maybe prompt the user and open a page for them? Maybe keep using
  mobile data until the portal is past? Maybe don't tell apps that they
  are connected to the internet when they really aren't? Maybe have the
  Browser not overwrite the last open tab with a portal?

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

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

[Touch-packages] [Bug 1561657] Re: not all captive portals work

[Pat McGowan]

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

** This bug has been marked a duplicate of bug 914507
   Feature Request: special Browser window for logging in to WiFi Hotspots

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

Title:
  not all captive portals work

Status in Canonical System Image:
  Incomplete
Status in webbrowser-app package in Ubuntu:
  Expired

Bug description:
  It has happened to me that many captive portals don't work with my
  phone; as in it doesn't even offer me the chance to enter the login
  details. This is somehow important for someone that travels and uses
  airport and hotel's wifis. Can I help in any way to help to better
  understand the problem and solve it? It's not even that the system
  doesn't tell me to login; sometimes the browser won't take me anywhere
  useful to login and get access.

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

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

[Touch-packages] [Bug 1528965] Re: "systemctl restart cups.service" hangs

[Launchpad Bug Tracker]

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

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

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

Title:
  "systemctl restart cups.service" hangs

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Being stuck at a print job `sudo systemctl restart cups.service`
  doesn't show any progress for 30 minutes.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: cups 2.1.0-4ubuntu3
  Uname: Linux 4.3.3-040303-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: Unity
  Date: Wed Dec 23 23:09:06 2015
  InstallationDate: Installed on 2015-12-12 (11 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lpstat:
   device for Hewlett-Packard-HP-Color-LaserJet-MFP-M476dn_(Netzwerk): 
hp:/net/HP_Color_LaserJet_MFP_M476dn?ip=192.168.179.42
   device for Hewlett-Packard-HP-Color-LaserJet-MFP-M476dn_(USB): 
hp:/usb/HP_Color_LaserJet_MFP_M476dn?serial=CNB8H415Z5
  MachineType: LENOVO 20221
  Papersize: a4
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Hewlett-Packard-HP-Color-LaserJet-MFP-M476dn_(Netzwerk).ppd', 
'/etc/cups/ppd/Hewlett-Packard-HP-Color-LaserJet-MFP-M476dn_(USB).ppd'] failed 
with exit code 2: grep: 
/etc/cups/ppd/Hewlett-Packard-HP-Color-LaserJet-MFP-M476dn_(Netzwerk).ppd: 
Keine Berechtigung
   grep: /etc/cups/ppd/Hewlett-Packard-HP-Color-LaserJet-MFP-M476dn_(USB).ppd: 
Keine Berechtigung
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.3-040303-generic 
root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro 
rootflags=subvol=ubuntu-main-root
  SourcePackage: cups
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 71CN51WW(V1.21)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Z500 Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch:
  dmi.product.name: 20221
  dmi.product.version: Lenovo IdeaPad Z500 Touch
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1598295] [NEW] $GTK_IM_MODULE ignored after upgrade

[Constantine]

Public bug reported:

After upgrade trusty → xenial, Compose key stopped producing configured
through ~/.XCompose characters for GTK3 only apps. To be sure that its
the GTK problem, I created a simple GTK3 window with textbox, launched
it like:

$ GTK_IM_MODULE=xim XMODIFIERS=@im=none ./a

and the textbox produces wrong characters for Compose key. (the
variables are actually set globally, I wrote them here just for
clarity).

XCompose works fine for all other toolkit's apps, including GTK2 and Qt
ones.

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System
-> About Ubuntu

$ lsb_release -rd
Description:Ubuntu 16.04 LTS
Release:16.04

2) The version of the package you are using, via 'apt-cache policy pkgname' or 
by checking in Software Center
$ apt-cache policy libgtk-3-0
libgtk-3-0:
  Installed: 3.18.9-1ubuntu3
  Candidate: 3.18.9-1ubuntu3
  Version table:
 *** 3.18.9-1ubuntu3 500
500 http://ru.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

3) What you expected to happen

«Compose + - + space» would produce «— » in GTK3 apps.

4) What happened instead

«Compose + - + space» producing «~» in GTK3 apps.

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

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

Title:
  $GTK_IM_MODULE ignored after upgrade

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  After upgrade trusty → xenial, Compose key stopped producing
  configured through ~/.XCompose characters for GTK3 only apps. To be
  sure that its the GTK problem, I created a simple GTK3 window with
  textbox, launched it like:

  $ GTK_IM_MODULE=xim XMODIFIERS=@im=none ./a

  and the textbox produces wrong characters for Compose key. (the
  variables are actually set globally, I wrote them here just for
  clarity).

  XCompose works fine for all other toolkit's apps, including GTK2 and
  Qt ones.

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  $ lsb_release -rd
  Description:Ubuntu 16.04 LTS
  Release:16.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  $ apt-cache policy libgtk-3-0
  libgtk-3-0:
Installed: 3.18.9-1ubuntu3
Candidate: 3.18.9-1ubuntu3
Version table:
   *** 3.18.9-1ubuntu3 500
  500 http://ru.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen

  «Compose + - + space» would produce «— » in GTK3 apps.

  4) What happened instead

  «Compose + - + space» producing «~» in GTK3 apps.

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

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

[Touch-packages] [Bug 1593379] Re: systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink

[Bug Watch Updater]

** Changed in: systemd (Debian)
   Status: Fix Committed => Fix Released

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

Title:
  systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or
  /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Xenial:
  In Progress
Status in systemd package in Debian:
  Fix Released

Bug description:
  Description:Ubuntu 16.04 LTS
  Release:16.04

  The upgrade to systemd/udev 229-4ubuntu6 breaks net.ifnames=0 for USB
  devices.

  It appears the regression is here:
  * Set MAC based name for USB network interfaces only for universally
  administered (i. e. stable) MACs, not for locally administered (i. e.
  randomly generated) ones. Drop /lib/systemd/network/90-mac-for-usb.link
  (as link files don't currently support globs for MACAddress=) and replace
  with an udev rule in /lib/udev/rules.d/73-special-net-names.rules.
  (Closes: #812575, LP: #1574483)

  As Raspberry Pi's use eth0 via USB, this breaks running systems.

  Before:
  ii  systemd229-4ubuntu4 armhfsystem and service manager
  ii  udev   229-4ubuntu4 armhf/dev/ and hotplug management daem

  3: eth0:  mtu 1500 qdisc pfifo_fast state UP 
mode DEFAULT group default qlen 1000
  link/ether b8:27:eb:16:39:e9 brd ff:ff:ff:ff:ff:ff

  After:

  ii  systemd  229-4ubuntu6armhf   
system and service manager
  ii  udev 229-4ubuntu6armhf   
/dev/ and hotplug management daemon

  3: enxb827eb1639e9:  mtu 1500 qdisc 
pfifo_fast state UP mode DEFAULT group default qlen 1000
  link/ether b8:27:eb:16:39:e9 brd ff:ff:ff:ff:ff:ff

  cat /proc/cmdline
  dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 
bcm2709.boardrev=0xa01041 bcm2709.serial=0x37b38253 
smsc95xx.macaddr=B8:27:EB:B3:82:53 bcm2708_fb.fbswap=1 bcm2709.disk_led_gpio=47 
bcm2709.disk_led_active_low=0 sdhci-bcm2708.emmc_clock_freq=25000 
vc_mem.mem_base=0x3dc0 vc_mem.mem_size=0x3f00  net.ifnames=0 
dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 
rootfstype=ext4 elevator=deadline rootwait

  With the default interfaces configuration, all networking is lost on
  reboot after upgrade.

  
  SRU TEST CASE
  =
   * Boot with "net.ifnames=0" on the kernel command line, and connect an USB 
ethernet device. It will still be called enxDEADBEEF with current xenial. With 
the -proposed version it will instead keep the kernel name, like "usb0" as 
intended.

   * Do "sudo ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules"
  (the other documented way to disable ifnames) and do the above
  connect/name check test again.

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

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

[Touch-packages] [Bug 1536353] Re: [regression] Printer drivers install is broken as lsb package is not available anymore

[Douglas Santos]

I was using LSB from Trusty's repo, and right now I've received the
update for this packages:   libappstream-glib8 lsb lsb-base lsb-core
lsb-invalid-mta lsb-printing lsb-release lsb-security

Also this packages was deleted with "autoremove":   libpod-plainer-perl
libqt4-opengl libqt4-svg lsb-cxx lsb-desktop  lsb-graphics lsb-languages
lsb-multimedia

The printer is still working perfectly. Thanks!

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

Title:
  [regression] Printer drivers install is broken as lsb package is not
  available anymore

Status in cups-filters package in Ubuntu:
  Fix Released
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Fix Released
Status in cups-filters source package in Xenial:
  Fix Released
Status in epson-inkjet-printer-escpr source package in Xenial:
  Fix Released
Status in lsb source package in Xenial:
  Fix Released

Bug description:
  [SRU justification]
  Previous releases were compatible with third-party printer drivers provided 
in LSB package format (and also as .deb packages depending on the lsb package). 
 As of 16.04, because the LSB specifies ABIs for various libraries that are no 
longer supported in Ubuntu as obsolete, the packages for the lsb modules have 
been dropped in both Debian and Ubuntu.  This includes dropping of lsb-core, 
which is the component which provides the LSB-mandated ELF loader path - 
without which no lsb executable will work.

  This SRU will restore the bare minimum of LSB compatibility necessary
  to support known third-party LSB printer driver packages on Ubuntu
  16.04.

  [Regression potential]
  The reintroduced 'lsb' binary package is known to not fully satisfy the 
requirements for a complete LSB-compliant system.  This is a regression vs. 
Ubuntu 14.04; so anyone using LSB packages on Ubuntu 14.04 who upgrades to 
Ubuntu 16.04 may have the upgrade succeed without any warning from the package 
manager.

  As there are very few lsb packages in use in the wild, this is
  considered an acceptable regression, especially as this will land
  before the first 16.04 point release.

  [Test case]
  1. Download the epsion 201106w printer driver package from 
http://download.ebz.epson.net/dsc/op/stable/debian/dists/lsb3.2/main/binary-amd64/epson-inkjet-printer-201106w_1.0.1-1lsb3.2_amd64.deb
  2. Install the package and confirm that its dependencies are not satisfiable.
  3. Enable xenial-proposed.
  4. Install the package again and confirm that the dependencies are satisfied.
  5. Verify that 
/opt/epson-inkjet-printer-201106w/cups/lib/filter/epson_inkjet_printer_filter 
can be run without errors about missing lsb ld.so or missing libraries.

  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's

   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

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

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

[Touch-packages] [Bug 1581065] Re: incorrect parsing of != dependency versions

[Steve Langasek]

Hello James, or anyone else affected,

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

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

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

** Changed in: dh-python (Ubuntu Wily)
   Status: New => Fix Committed

** Tags removed: verification-done

** Tags added: verification-needed

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

Title:
  incorrect parsing of != dependency versions

Status in dh-python package in Ubuntu:
  Fix Released
Status in dh-python source package in Wily:
  Fix Committed
Status in dh-python source package in Xenial:
  Fix Released
Status in dh-python source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  dh-python incorrectly used != version operators in some cases, resulting in 
failed package builds; this impacts a number of stable updates for Xenial which 
blacklist a specific cryptography version.

  [Test Case]
  Build stable release of glance/keystone/nova for xenial/mitaka (parse problem 
in original bug report)

  [Regression Potential]
  Testing OK in yakkety; change is minimal and ensures != operator is ignored 
when detected.

  [Original Bug Report]
  Some updates to requirements for openstack projects (glance and keystone 
specifically) is causing dh-python to incorrectly generate a != version 
dependency; this is the requires.txt entry:

   cryptography!=1.3.0,>=1.0

  which causes (utimately):

  dpkg-gencontrol: warning: can't parse dependency python-cryptography
  (!= 1.3.0)

  from the generated dependency line:

  "python-castellan, python-crypto (>= 2.6), python-cryptography (!=
  1.3.0), python-debtcollector, python-eventlet, python-futurist,
  python-glance-store, python-httplib2, python-iso8601, python-
  jsonschema, python-keystoneauth1, python-keystoneclient, python-
  keystonemiddleware, python-migrate, python-monotonic, python-openssl,
  python-oslo.concurrency, python-oslo.config, python-oslo.context,
  python-oslo.db, python-oslo.i18n, python-oslo.log, python-
  oslo.messaging, python-oslo.middleware, python-oslo.policy, python-
  oslo.serialization, python-oslo.service, python-oslo.utils, python-
  osprofiler, python-paste, python-pastedeploy, python-pbr, python-
  prettytable, python-retrying, python-semantic-version, python-six (>=
  1.9.0), python-sqlalchemy (>= 1.0~), python-sqlalchemy (<< 1.1),
  python-stevedore, python-taskflow, python-webob, python-wsme,
  python:any (<< 2.8), python:any (>= 2.6~), python:any (>= 2.7.5-5~),
  python:any (>= 2.7~),"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dh-python 2.20151103ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May 12 15:15:36 2016
  Dependencies:

  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-01-17 (115 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  PackageArchitecture: all
  SourcePackage: dh-python
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1597755] Re: No ringtone or message tone in headphones in silent mode

[Jim Hodapp]

@marcustomlinson: thanks for the reply. I wanted to make sure that was
intentional in the UX design. I could also think of situations where you
have your headphones on and you wouldn't want the ringtone to come
through the main speaker so as to not disturb the public around you
(assuming you would not answer the call and start talking because then
that would be a moot point).

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

Title:
  No ringtone or message tone in headphones in silent mode

Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu RTM:
  Confirmed

Bug description:
  When in silent mode, ringtones and message tones do not play in
  headphones.

  They are supposed to according to: https://wiki.ubuntu.com/Sound

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

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

[Touch-packages] [Bug 1591528] Re: Merge poppler 0.44.0-3 (main) from Debian unstable (main)

[Launchpad Bug Tracker]

This bug was fixed in the package poppler - 0.44.0-3ubuntu1

---
poppler (0.44.0-3ubuntu1) yakkety; urgency=medium

  * Merge with Debian. (LP: #1591528) Remaining changes:
- debian/control:
  + Don't build-depend on libopenjp2-7-dev since it's in universe
- debian/rules:
  + Use --disable-libopenjpeg
  * Dropped changes:
- Only suggest poppler-data since it's too big for CDs and
  language-selector automatically installs it after install
- debian/patches/revert_api_change.patch:
  + revert upstream commit that removed an enum, they claim it's
not an abi change because it's unused, but other packages (bindings)
rely on it to build still, we can drop the patch later once the
rdepends have been updated

poppler (0.44.0-3) unstable; urgency=medium

  * Switch from OpenJPEG 1.x to 2.x: (Closes: #826825)
- replace the libopenjpeg-dev build dependency with libopenjp2-7-dev
- pass --enable-libopenjpeg=openjpeg2 to configure, to be sure OpenJPEG 2.x
  is used

 -- Jeremy Bicha   Sat, 11 Jun 2016 18:16:34 -0400

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

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

Title:
  Merge poppler 0.44.0-3 (main) from Debian unstable (main)

Status in poppler package in Ubuntu:
  Fix Released

Bug description:
  Please merge poppler 0.44.0-3 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
  ===
    * Updated for soname change libpoppler58 -> 61
    * New upstream version (soname update 57->58)
    * debian/patchres/revert_api_change.patch:
  - revert upstream commit that removed an enum, they claim it's
    not an abi change because it's unused, but other packages (bindings)
    rely on it to build still, we can drop the patch later once the
    redpends have been updated
    * Updated for soname change libpoppler56 -> 57
    * Updated for soname change libpoppler52 -> 56
    * Set hardening flags to "+all,-pie" to build with all hardening flags
  except -fPIE.
    * New upstream release (LP: #1449991)
    * Rename packages according to the new SONAMEs:
  - libpoppler49 -> libpoppler52
    * debian/libpoppler-glib8.symbols.in:
    * debian/libpoppler-qt4-4.symbols.in:
    * debian/libpoppler-qt5-1.symbols.in:
  - Updated
    * Explicitly pass --disable-libopenjpeg now - this support was auto-disabled
  before but now configure fails without this flag.
    * Rename packages according to the new SONAMEs:
  - libpoppler47 -> libpoppler49
    * Resynchronise with Debian, remaining changes:
  - Drop libopenjpeg-dev build depends, it is in universe.
  - Lower poppler-data to Suggests, it is too big for CD images,
    handled by language-selector.

  All of that is in the Debian package except for these:
  
  1. Drop libopenjpeg-dev build-depends, it is in universe
  - We still need this dropped, except it is now libopenjp2-7-dev
  2. Use --disable-libopenjpeg
  - Still needed
  3. debian/patches/revert_api_change.patch:
  - Not needed, see test build results below
  4. Lower poppler-data to Suggests since it's too big for CD images
  - Since we aren't as concerned about 1 or 2 MBs since we do DVDs instead
  of CDs, this seems like an obsolete change. See bug 893920 where we have
  language-selector install this for everyone after install anyway.

  $ apt show poppler-data
  Installed-Size: 12.4 MB
  Download-Size: 1,495 kB

  Changelog entries since current yakkety version 0.44.0-0ubuntu1:
  =

  poppler (0.44.0-3) unstable; urgency=medium

    * Switch from OpenJPEG 1.x to 2.x: (Closes: #826825)
  - replace the libopenjpeg-dev build dependency with libopenjp2-7-dev
  - pass --enable-libopenjpeg=openjpeg2 to configure, to be sure OpenJPEG 
2.x
    is used

   -- Pino Toscano   Thu, 09 Jun 2016 23:14:49 +0200

  poppler (0.44.0-2) unstable; urgency=medium

    * Upload to unstable. (See #823667)

   -- Pino Toscano   Fri, 27 May 2016 22:13:46 +0200

  poppler (0.44.0-1) experimental; urgency=medium

    * New upstream release.
    * Rename packages according to the new SONAMEs:
  - libpoppler60 -> libpoppler61
    * Update copyright.

   -- Pino Toscano   Sun, 22 May 2016 08:46:59 +0200

  poppler (0.43.0-1) experimental; urgency=medium

    * New upstream release: (Closes: #822644)
  - fixes pdfinfo man page (Closes: #813500)
  - fixes build with GCC 6 (Closes: #811901)
    * Rename packages according to the new SONAMEs:
  - libpoppler57 -> libpoppler60
    * Update copyright.
    * Update symbols files:
  - adapt to the different internal symbols with GCC 6
    * Update build 

[Touch-packages] [Bug 1506744] Re: Newly installed applications do not show in the dash

[Launchpad Bug Tracker]

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

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

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

Title:
  Newly installed applications do not show in the dash

Status in GLib:
  Confirmed
Status in bamf package in Ubuntu:
  In Progress
Status in gnome-menus package in Ubuntu:
  Fix Released
Status in libunity package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Invalid
Status in gnome-menus source package in Xenial:
  Fix Committed
Status in libunity source package in Xenial:
  Confirmed

Bug description:
  I am running 15.10 development version fully up to date, I installed
  it a few days ago and I have an issue with newly installed
  applications not appearing in the dash when I search for them, they
  can be started via console but the icons/launchers of newly installed
  applications will only appear in the dash after session is restarted.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: unity 7.3.2+15.10.20151002.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Oct 16 08:41:39 2015
  InstallationDate: Installed on 2015-10-11 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151011)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1536353] Re: [regression] Printer drivers install is broken as lsb package is not available anymore

[Bruno Nova]

Thank you people! My printer now works perfectly!

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

Title:
  [regression] Printer drivers install is broken as lsb package is not
  available anymore

Status in cups-filters package in Ubuntu:
  Fix Released
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Fix Released
Status in cups-filters source package in Xenial:
  Fix Released
Status in epson-inkjet-printer-escpr source package in Xenial:
  Fix Released
Status in lsb source package in Xenial:
  Fix Released

Bug description:
  [SRU justification]
  Previous releases were compatible with third-party printer drivers provided 
in LSB package format (and also as .deb packages depending on the lsb package). 
 As of 16.04, because the LSB specifies ABIs for various libraries that are no 
longer supported in Ubuntu as obsolete, the packages for the lsb modules have 
been dropped in both Debian and Ubuntu.  This includes dropping of lsb-core, 
which is the component which provides the LSB-mandated ELF loader path - 
without which no lsb executable will work.

  This SRU will restore the bare minimum of LSB compatibility necessary
  to support known third-party LSB printer driver packages on Ubuntu
  16.04.

  [Regression potential]
  The reintroduced 'lsb' binary package is known to not fully satisfy the 
requirements for a complete LSB-compliant system.  This is a regression vs. 
Ubuntu 14.04; so anyone using LSB packages on Ubuntu 14.04 who upgrades to 
Ubuntu 16.04 may have the upgrade succeed without any warning from the package 
manager.

  As there are very few lsb packages in use in the wild, this is
  considered an acceptable regression, especially as this will land
  before the first 16.04 point release.

  [Test case]
  1. Download the epsion 201106w printer driver package from 
http://download.ebz.epson.net/dsc/op/stable/debian/dists/lsb3.2/main/binary-amd64/epson-inkjet-printer-201106w_1.0.1-1lsb3.2_amd64.deb
  2. Install the package and confirm that its dependencies are not satisfiable.
  3. Enable xenial-proposed.
  4. Install the package again and confirm that the dependencies are satisfied.
  5. Verify that 
/opt/epson-inkjet-printer-201106w/cups/lib/filter/epson_inkjet_printer_filter 
can be run without errors about missing lsb ld.so or missing libraries.

  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's

   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

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

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

[Touch-packages] [Bug 1579570] Re: Text messages: Available sound notifications are too short and quiet

[Pat McGowan]

Pending new sounds from UX

** Changed in: canonical-devices-system-image
   Importance: Undecided => Medium

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Bill Filler (bfiller)

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

Title:
  Text messages: Available sound notifications are too short and quiet

Status in Canonical System Image:
  Confirmed
Status in ubuntu-system-settings:
  New
Status in Ubuntu UX:
  New
Status in messaging-app package in Ubuntu:
  Confirmed

Bug description:
  I simply do not hear when a new message arrives. Please add some
  louder and longer tone that user is able to hear on the street.

  Reported for Aquaris 4.5 with Ubuntu 15.04 (OTA-10.1)

  [This report previously also mentioned inability to add custom sounds,
  now covered by bug 1589229.]

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

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

[Touch-packages] [Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones

[Joakim Koed]

I just downgraded to 6.0 from wily in xenial, now bluetooth is perfect.
Will hold those packages until this is resolved.

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

Title:
  pulseaudio crashes when connecting to bluetooth headphones

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04
  pulseaudio crashes, this does *NOT* happen with a Jambox which leads
  me to believe it's an intermittent problem with some hardware. This
  did not happen on Ubuntu 15.10 (which was an upgrade of 15.04).

  Ubuntu Release:

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Pulseaudio Version:

  pulseaudio:
Installed: 1:8.0-0ubuntu3
Candidate: 1:8.0-0ubuntu3
Version table:
   *** 1:8.0-0ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  Device info:

  [bluetooth]# info 44:5E:F3:B4:07:29 
  Device 44:5E:F3:B4:07:29
Name: BlueBuds X
Alias: BlueBuds X
Class: 0x240404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
UUID: Headset   (1108--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Handsfree (111e--1000-8000-00805f9b34fb)
UUID: Unknown   (80ff--1000-8000-00805f9b34fb)

  I have also attached a debug dump of Pulseaudio when attempting to
  connect to the headphones.

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

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

[Touch-packages] [Bug 1589443] Re: I don't know what is the problem

[Paul White]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).

Thanks!

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

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

Title:
  I don't know what is the problem

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I don't know what is the problem. Simply, I have just turned on
  xdiagnose and showed me some bag about nvidia m840.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia wl
  .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:04:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2.1)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Jun  6 11:58:53 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-22-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-21-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-22-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-22-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics 
Controller [1043:16cd]
 Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 840M] [1043:16cd]
  InstallationDate: Installed on 2016-06-03 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK COMPUTER INC. X555LN
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=7d0453c9-ea92-4810-b9f0-751c43c5d78f ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555LN.309
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555LN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555LN.309:bd08/14/2014:svnASUSTeKCOMPUTERINC.:pnX555LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X555LN
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Jun  6 07:34:28 2016
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2.2

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

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

[Touch-packages] [Bug 1589778] Re: I really don't know why a debug report was sent in

[Paul White]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).

Thanks!

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

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

Title:
  I really don't know why a debug report was sent in

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I dOn't know what is wrong.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Jun  6 22:55:34 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
  InstallationDate: Installed on 2016-06-05 (2 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: Gigabyte Technology Co., Ltd. G1.Sniper H6
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=bd73f3ee-4d43-48cd-bdb5-5bcc9328e1a7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: G1.Sniper H6
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF6:bd04/21/2015:svnGigabyteTechnologyCo.,Ltd.:pnG1.SniperH6:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnG1.SniperH6:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: G1.Sniper H6
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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

[Touch-packages] [Bug 1597389] Re: Resolution does not get set to 1024x900

[Paul White]

** Summary changed:

- Please fix probleam
+ Resolution does not get set to 1024x900

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

Title:
  Resolution does not get set to 1024x900

Status in xorg package in Ubuntu:
  New

Bug description:
  Resolution do not set 1024x900.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Jun 29 20:52:15 2016
  InstallationDate: Installed on 2016-06-10 (19 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1594035] Re: unable to shut down the system after suspend / resume

[Loye Young]

Correcting error:

"This is so no matter which path to the swap partition I use, including:
/dev/disks/by-uuid/, the device show by "grep /proc/swaps", or
/dev/mapper/cryptswap1."

헦헵헼혂헹헱 혀헮혆:

"This is so no matter which path to the swap partition I use, including:
/dev/disks/by-uuid/, the device show by "헰헮혁 /proc/swaps", or
/dev/mapper/cryptswap1."

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

Title:
  unable to shut down the system after suspend / resume

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  In the case of a system that has gone through a suspend / resume
  cycle, the "shutdown now" command fails with the following output:

  $ shutdown now
  Failed to power off system via logind: Transaction is destructive.
  Failed to start poweroff.target: Interactive authentication required.
  See system logs and 'systemctl status poweroff.target' for details.
  Failed to open /dev/initctl: Permission denied
  Failed to talk to init daemon.

  ---

  $ systemctl status poweroff.target
  ● poweroff.target - Power-Off
 Loaded: loaded (/lib/systemd/system/poweroff.target; disabled; vendor 
preset:
 Active: inactive (dead)
   Docs: man:systemd.special(7)

  ---

  $ systemctl list-jobs
  JOB UNIT  TYPE  STATE  
  438 dev-mapper-cryptswap1.device  start running
  439 dev-mapper-cryptswap1.swapstart waiting
  436 systemd-cryptsetup@cryptswap1.service start running

  3 jobs listed.

  ---

  Steps to reproduce:

  1. Boot system
  2. User login to graphical session
  3. Close lid while on battery power triggering a suspend
  4. Open lid while on battery power triggering a resume
  5. Run "shutdown now" from a terminal. Note that the command must be run from 
the terminal to see output. Selecting "Shut Down..." from the system menu in 
the menu bar will hide the error output.
  6. Observe that the system fails to shut down

  Expected behavior:

  At step 6, the system should shut down gracefully.

  Note that the shutdown process works as expected if steps 3 and 4 are
  skipped. I suspect that something about the suspend / resume cycle
  during the session has an interaction effect with the shutdown
  process, preventing it from executing correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun 18 18:04:26 2016
  EcryptfsInUse: Yes
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b550 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System76, Inc. Lemur
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed 
root=UUID=7aecd352-8a3f-4ce9-88b8-0fc048dc9660 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/29/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06RS76
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Lemur
  dmi.board.vendor: System76, Inc.
  dmi.board.version: lemu6
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06RS76:bd11/29/2015:svnSystem76,Inc.:pnLemur:pvrlemu6:rvnSystem76,Inc.:rnLemur:rvrlemu6:cvnSystem76,Inc.:ct10:cvrN/A:
  dmi.product.name: Lemur
  dmi.product.version: lemu6
  dmi.sys.vendor: System76, Inc.

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

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

[Touch-packages] [Bug 1597881] Re: Fix for CVE-2016-1234 in Ubuntu for eglibc 2.15-0ubuntu10.15

[Paul White]

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

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

Title:
  Fix for CVE-2016-1234 in Ubuntu for eglibc 2.15-0ubuntu10.15

Status in Juniper Openstack:
  In Progress
Status in Juniper Openstack r2.20 series:
  In Progress
Status in Juniper Openstack r2.22.x series:
  In Progress
Status in Juniper Openstack r3.0 series:
  In Progress
Status in Juniper Openstack trunk series:
  In Progress
Status in eglibc package in Ubuntu:
  New

Bug description:
  CVE-2016-1234 has to be fixed for eglibc 2.15-0ubuntu10.15

  I have found Debian guys have patched this in wheezy
  (https://packages.debian.org/wheezy/all/eglibc-source/download)  which
  is on 2.13 , Couldn't find this for 2-15 in Ubuntu repositories.

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

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

[Touch-packages] [Bug 1597881] [NEW] Fix for CVE-2016-1234 in Ubuntu for eglibc 2.15-0ubuntu10.15

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

CVE-2016-1234 has to be fixed for eglibc 2.15-0ubuntu10.15

I have found Debian guys have patched this in wheezy
(https://packages.debian.org/wheezy/all/eglibc-source/download)  which
is on 2.13 , Couldn't find this for 2-15 in Ubuntu repositories.

** Affects: juniperopenstack
 Importance: Undecided
 Status: In Progress

** Affects: juniperopenstack/r2.20
 Importance: Undecided
 Status: In Progress

** Affects: juniperopenstack/r2.22.x
 Importance: Undecided
 Status: In Progress

** Affects: juniperopenstack/r3.0
 Importance: Undecided
 Status: In Progress

** Affects: juniperopenstack/trunk
 Importance: Undecided
 Status: In Progress

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

-- 
Fix for CVE-2016-1234 in Ubuntu for eglibc 2.15-0ubuntu10.15
https://bugs.launchpad.net/bugs/1597881
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to eglibc 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 1594452] Re: Add vulcan support

[dann frazier]

gcc-5 5.4.0-5ubuntu1~16.04 from ppa:ubuntu-toolchain-r/ppa does accept
vulcan as an -mcpu option, and it does pass the correct -march settings
down to the assembler:

$ gcc -v hello.c -o hello 2>&1 | grep ' as '
 as -v -EL -mabi=lp64 -o /tmp/ccgyMnhl.o /tmp/cchw8EFH.s
$ gcc -mcpu=vulcan -v hello.c -o hello 2>&1 | grep ' as '
 as -v -EL -march=armv8.1-a+crypto -mabi=lp64 -o /tmp/ccgkHPq1.o /tmp/cc32DdK2.s

binutils 2.26.1-1ubuntu1~16.04 from proposed also accepts -mcpu vulcan
now:

$ (gcc -Wa,-mcpu=vulcan -mcpu=vulcan -v hello.c -o hello 2>&1 && echo exitcode 
$? 1>&2)| grep ' as '
 as -v -EL -march=armv8.1-a+crypto -mabi=lp64 -mcpu=vulcan -o /tmp/cc2Hf3Ve.o 
/tmp/ccMVgC69.s
exitcode 0

I expected gcc -mcpu=vulcan to pass down -mcpu=vulcan to the assembler
as well, but it didn't. I tested using -mcpu=xgene1 instead, and that
also does not pass -mcpu=xgene1 down to the assembler, so I assume this
is normal.


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

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

Title:
  Add vulcan support

Status in binutils package in Ubuntu:
  Fix Released
Status in gcc-5 package in Ubuntu:
  Fix Released
Status in gcc-6 package in Ubuntu:
  Fix Released
Status in binutils source package in Xenial:
  Fix Committed
Status in gcc-5 source package in Xenial:
  New

Bug description:
  Vulcan support has recently landed upstream. Please include this
  backport in Ubuntu.

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

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

[Touch-packages] [Bug 1594035] Re: unable to shut down the system after suspend / resume

[Loye Young]

Being a fellow pilgrim in the Way of the Penguin, I can confirm the
exact same facts as Mr. Pellegrino on clean install of Ubuntu Mate
16.04.

It appears that the swap partition is not actually encrypted at all.
Syslog shows that encryption failed, and "cryptsetup -v isLuks
/path/to/partition" shows not LUKS partition. This is so no matter which
path to the swap partition I use, including: /dev/disks/by-uuid/,
the device show by "grep /proc/swaps", or /dev/mapper/cryptswap1.

Looking at /var/log/syslog, I see that cryptsetup failed because
/dev/urandom is not available. ("grep crypt /var/log/syslog" for
details.)

Further, I notice that poweroff.target is disabled. When I enable it
(systemctl enable poweroff.target), shutdown works as expected unless
the computer has resumed from suspend.

The work around suggested by Mr. Pellegrino works, but of course that
means that swap is not encrypted, which is of course a security
vulnerability.

Here is my working theory: On boot-up, systemd tries to create an
encrypted swap, but when it cannot, systemd creates an unencrypted swap.
(Feature or bug? There would be competing considerations, so it is hard
to say.) After resume from suspend, which of course involves (on
suspend) writing RAM to swap and then (on resume) reading from swap to
RAM, the system thinks there should be an encrypted swap (because that's
what /etc/fstab and /etc/crypttab say), but can't find it and gets
confused when time comes to shutdown.

This being a security issue, it should be given attention.

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

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

Title:
  unable to shut down the system after suspend / resume

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  In the case of a system that has gone through a suspend / resume
  cycle, the "shutdown now" command fails with the following output:

  $ shutdown now
  Failed to power off system via logind: Transaction is destructive.
  Failed to start poweroff.target: Interactive authentication required.
  See system logs and 'systemctl status poweroff.target' for details.
  Failed to open /dev/initctl: Permission denied
  Failed to talk to init daemon.

  ---

  $ systemctl status poweroff.target
  ● poweroff.target - Power-Off
 Loaded: loaded (/lib/systemd/system/poweroff.target; disabled; vendor 
preset:
 Active: inactive (dead)
   Docs: man:systemd.special(7)

  ---

  $ systemctl list-jobs
  JOB UNIT  TYPE  STATE  
  438 dev-mapper-cryptswap1.device  start running
  439 dev-mapper-cryptswap1.swapstart waiting
  436 systemd-cryptsetup@cryptswap1.service start running

  3 jobs listed.

  ---

  Steps to reproduce:

  1. Boot system
  2. User login to graphical session
  3. Close lid while on battery power triggering a suspend
  4. Open lid while on battery power triggering a resume
  5. Run "shutdown now" from a terminal. Note that the command must be run from 
the terminal to see output. Selecting "Shut Down..." from the system menu in 
the menu bar will hide the error output.
  6. Observe that the system fails to shut down

  Expected behavior:

  At step 6, the system should shut down gracefully.

  Note that the shutdown process works as expected if steps 3 and 4 are
  skipped. I suspect that something about the suspend / resume cycle
  during the session has an interaction effect with the shutdown
  process, preventing it from executing correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun 18 18:04:26 2016
  EcryptfsInUse: Yes
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b550 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System76, Inc. Lemur
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed 
root=UUID=7aecd352-8a3f-4ce9-88b8-0fc048dc9660 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/29/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06RS76
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Lemur
  dmi.board.vendor: System76, Inc.
  dmi.board.version: lemu6
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 

[Touch-packages] [Bug 1577596] Re: ntpd not started when using ntpdate

[John Sopko]

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

Another observation, the ntpdate command is really slow on Ubuntu 14.04
and 16.04. On average it takes about 6.1 seconds to run the ntpdate
command, I am running ntpdate after boot. Our Red hat 6.8 machines take
about 0.1 seconds. We manage 300+ Ubuntu 14.04 and 16.04 systems and I
checked ntpdate on several of them. Still can't figure out why most
machines work but some consistently fail to start ntpd. Even the ones
that do start ntpd ntpdate still takes 6+ seconds to run. And we have
our own in house stratum 1 time servers that are on the same internal
network.

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

Title:
  ntpd not started when using ntpdate

Status in init-system-helpers package in Ubuntu:
  Confirmed
Status in ntp package in Ubuntu:
  Confirmed

Bug description:
  After updating from 14.04 to 16.04 on a number of my systems, ntpd no
  longer starts at boot on any of those systems.

  `systemctl status ntp` shows:
 ntp.service - LSB: Start NTP daemon
 Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
 Active: inactive (dead)
   Docs: man:systemd-sysv-generator(8)
  May 02 19:10:14 host systemd[1]: Stopped LSB: Start NTP daemon.
  May 02 19:10:17 host systemd[1]: Stopped LSB: Start NTP daemon.

  Manually starting it using `systemctl start ntp` works fine.  However,
  systemd does not seem to want to start it automatically at boot time.


  As best as I can tell based on trial and error, there is something
  special about the combination of the service being named "ntp.service"
  and the service depending on network.target.  However, I haven't been
  able to identify exactly what is causing this.

  If I copy the init script to any other name, everything works fine:
  cp /etc/init.d/ntp /etc/init.d/ntpd
  Edit /etc/init.d/ntpd and change "Provides: ntp" to "Provides: ntpd"
  systemctl enable ntpd
  # After a reboot, ntpd.service is started, but ntp.service is not.

  If I remove "$network" from the "# Required-Start: $network $remote_fs
  $syslog" line in /etc/init.d/ntp, then systemd starts it automatically
  ... But of course it is started before the network comes up, so it
  fails.

  If I replace /etc/init.d/ntp with a file containing only the following, 
systemd won't try to start it automatically at boot:
  #!/bin/sh
  ### BEGIN INIT INFO
  # Provides: ntp
  # Required-Start: $network
  # Required-Stop: $network
  # Default-Start: 2 3 4 5
  # Default-Stop: 1
  # Short-Description: Start NTP daemon
  ### END INIT INFO
  echo "script was run" >> /ntp.log

  If I rename that same dummy script to /etc/init.d/ntp2, it is started
  automatically at boot.

  However, grepping the systemd source code and my systemd config files for ntp 
doesn't seem to find anything that might cause this behavior:
  /etc/systemd# grep -iR ntp *
  timesyncd.conf:#NTP=
  timesyncd.conf:#FallbackNTP=ntp.ubuntu.com
  /lib/systemd# grep -R ntp *
  
system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/ntpd
  
system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/openntpd
  Binary file systemd-networkd matches
  Binary file systemd-timedated matches
  Binary file systemd-timesyncd matches

  What else can I do to debug this further?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1577596/+subscriptions

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

[Touch-packages] [Bug 1596713] Re: apport-cli crashes if a hook provides a python list which is a directory w/o files

[Brian Murray]

** Changed in: apport (Ubuntu)
 Assignee: (unassigned) => Martin Pitt (pitti)

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

Title:
  apport-cli crashes if a hook provides a python list which is a
  directory w/o files

Status in apport package in Ubuntu:
  New

Bug description:
  I was reviewing an apport hook for somebody and noticed that apport-
  cli would crash when you try to save a report (option K) if the apport
  hook does something odd.  As an example:

  1) mkdir -p /tmp/directory1/directory2
  2) modify an apport package hook to contain the following:
 contents = os.listdir('/tmp/directory1')
 report['DirContents'] = contents
  3) run apport-cli ubuntu-release-upgrader (package hook I modified)
  4) observe the following crash

  Traceback (most recent call last):
File "/usr/bin/apport-cli", line 370, in 
  if not app.run_argv():
File "/usr/lib/python3/dist-packages/apport/ui.py", line 645, in run_argv
  self.run_symptom()
File "/usr/lib/python3/dist-packages/apport/ui.py", line 636, in run_symptom
  self.run_report_bug(script)
File "/usr/lib/python3/dist-packages/apport/ui.py", line 489, in 
run_report_bug
  response = self.ui_present_report_details(allowed_to_report)
File "/usr/bin/apport-cli", line 220, in ui_present_report_details
  self.report.write(f)
File "/usr/lib/python3/dist-packages/problem_report.py", line 448, in write
  f = open(v[0], 'rb')  # file name
  FileNotFoundError: [Errno 2] No such file or directory: 'directory2'

  If DirContents is a folder that contains at least one file we see the
  following error raised instead.

  TypeError: value for key DirContents must be a string,
  CompressedValue, or a file reference

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

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

[Touch-packages] [Bug 1583802] Re: Keyboard layout is not respected in some places

[Guillaume F]

Well, I seem to be alone with this problem, but today I found that the
password prompt for connecting to a WiFi source is also affected and
stuck in QWERTY. Strangely enough, it is not the case with the whole
"hidden network" form: there, I can type my password in AZERTY quite
normally. (I was forced to cheat and connect to my network with the
"hidden network" feature, since the regular password prompt didn't work.
Probably another bug though).

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

Title:
  Keyboard layout is not respected in some places

Status in Mir:
  New
Status in mir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed
Status in unity8-desktop-session package in Ubuntu:
  Incomplete

Bug description:
  I'm trying Unity8 on my desktop (and reporting bugs from there,
  cool!), I've followed Michael Hall's how to, so I have the same PPAs
  on my system.

  The keyboard layout is not the same everywhere in the OS. I switched
  to French and it works in most places, but in some others, an English
  keyboard persists. These other places include the greeter and the
  Online Accounts (the rest of the System Settings app seems fine). I'm
  not sure where else but I'll keep searching.

  I have to say, it has its advantages, since alt-gr does not work and I
  have to copy/paste things like "@"!

  Thanks for your great work, it's really exciting to see the progress!

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

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

[Touch-packages] [Bug 1598212] Re: /etc/os-release: Please specify VERSION_CODENAME

[Bug Watch Updater]

** Changed in: base-files (Debian)
   Status: Unknown => New

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

Title:
  /etc/os-release: Please specify VERSION_CODENAME

Status in base-files package in Ubuntu:
  New
Status in base-files package in Debian:
  New

Bug description:
  The os-release specification was updated in systemd > 230 to also
  include a VERSION_CODENAME parameter:
  
https://github.com/systemd/systemd/commit/646b997c118e261c5ececc434dd40d0dbdbac4d8

  Please replace the custom UBUNTU_CODENAME parameter by
  VERSION_CODENAME in yakkety and add VERSION_CODENAME to /etc/os-
  release to all stable releases.

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

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

[Touch-packages] [Bug 1598246] [NEW] package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade: il sottoprocesso installato script di post-installation è stato terminato dal segnale (Ucciso)

[Gabriele De Luca]

Public bug reported:

I faced it while starting the Unity Desktop environment

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: shared-mime-info 1.5-2ubuntu0.1
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Fri Jul  1 18:51:54 2016
ErrorMessage: il sottoprocesso installato script di post-installation è stato 
terminato dal segnale (Ucciso)
InstallationDate: Installed on 2016-05-15 (47 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: shared-mime-info
Title: package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade: il 
sottoprocesso installato script di post-installation è stato terminato dal 
segnale (Ucciso)
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: shared-mime-info (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade: il
  sottoprocesso installato script di post-installation è stato terminato
  dal segnale (Ucciso)

Status in shared-mime-info package in Ubuntu:
  New

Bug description:
  I faced it while starting the Unity Desktop environment

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: shared-mime-info 1.5-2ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Fri Jul  1 18:51:54 2016
  ErrorMessage: il sottoprocesso installato script di post-installation è stato 
terminato dal segnale (Ucciso)
  InstallationDate: Installed on 2016-05-15 (47 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: shared-mime-info
  Title: package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade: il 
sottoprocesso installato script di post-installation è stato terminato dal 
segnale (Ucciso)
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1598246/+subscriptions

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

[Touch-packages] [Bug 1568094] Re: Many error message such as "Start request repeated too quickly."

[Laurent Bonnaud]

** Attachment added: "journal-with-lmt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1568094/+attachment/4693712/+files/journal-with-lmt

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

Title:
  Many error message such as "Start request repeated too quickly."

Status in laptop-mode-tools package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in laptop-mode-tools source package in Xenial:
  New
Status in systemd source package in Xenial:
  In Progress

Bug description:
  * Analysis:

  The error messages are caused by a bad interaction between systemd and
  laptop-mode-tools.

  * Fixes:

  There is a fix in systemd:
  https://github.com/systemd/systemd/pull/3148

  The problem can also be fixed by updating laptop-mode-tools.

  * Symptoms:

  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary 
Formats.
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root 
Device.
  Apr 08 20:23:50 xeelee systemd[1]: Started Show Plymouth Boot Screen.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-hwdb-update.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Rebuild Hardware Database.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary 
Formats.
  Apr 08 20:23:50 xeelee systemd[1]: Starting Show Plymouth Boot Screen...
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root 
Device.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary 
Formats.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-hwdb-update.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Rebuild Hardware Database.
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root 
Device.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: Started Show Plymouth Boot Screen.
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root 
Device.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-hwdb-update.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Rebuild Hardware Database.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary 
Formats.
  Apr 08 20:23:50 xeelee systemd[1]: plymouth-start.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Show Plymouth Boot Screen.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-ask-password-console.path: Start 
request repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Dispatch Password Requests 
to Console Directory 

[Touch-packages] [Bug 1568094] Re: Many error message such as "Start request repeated too quickly."

[Laurent Bonnaud]

** Attachment added: "journal-without-lmt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1568094/+attachment/4693713/+files/journal-without-lmt

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

Title:
  Many error message such as "Start request repeated too quickly."

Status in laptop-mode-tools package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in laptop-mode-tools source package in Xenial:
  New
Status in systemd source package in Xenial:
  In Progress

Bug description:
  * Analysis:

  The error messages are caused by a bad interaction between systemd and
  laptop-mode-tools.

  * Fixes:

  There is a fix in systemd:
  https://github.com/systemd/systemd/pull/3148

  The problem can also be fixed by updating laptop-mode-tools.

  * Symptoms:

  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary 
Formats.
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root 
Device.
  Apr 08 20:23:50 xeelee systemd[1]: Started Show Plymouth Boot Screen.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-hwdb-update.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Rebuild Hardware Database.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary 
Formats.
  Apr 08 20:23:50 xeelee systemd[1]: Starting Show Plymouth Boot Screen...
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root 
Device.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary 
Formats.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-hwdb-update.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Rebuild Hardware Database.
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root 
Device.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: Started Show Plymouth Boot Screen.
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root 
Device.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-hwdb-update.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Rebuild Hardware Database.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary 
Formats.
  Apr 08 20:23:50 xeelee systemd[1]: plymouth-start.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Show Plymouth Boot Screen.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-ask-password-console.path: Start 
request repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Dispatch Password Requests 
to Console 

[Touch-packages] [Bug 1568094] Re: Many error message such as "Start request repeated too quickly."

[Laurent Bonnaud]

I tried to boot my system with this package version:

Package: systemd
Version: 229-4ubuntu6pitti1

both with and without the laptop-mode-tools package.  In both cases my
system boots and is usable.

Without laptop-mode-tools, there are no "Start request repeated too
quickly" error messages.

With laptop-mode-tools, I get the following error messages:

juil. 01 17:45:19 vougeot systemd[1]: plymouth-read-write.service: Start 
request repeated too quickly.
juil. 01 17:45:19 vougeot systemd[1]: Failed to start Tell Plymouth To Write 
Out Runtime Data.
juil. 01 17:45:19 vougeot systemd[1]: plymouth-start.service: Start request 
repeated too quickly.
juil. 01 17:45:19 vougeot systemd[1]: Failed to start Show Plymouth Boot Screen.
juil. 01 17:45:19 vougeot systemd-udevd[383]: Process '/lib/udev/hdparm' failed 
with exit code 5.
juil. 01 17:45:19 vougeot systemd[1]: plymouth-read-write.service: Start 
request repeated too quickly.
juil. 01 17:45:19 vougeot systemd[1]: Failed to start Tell Plymouth To Write 
Out Runtime Data.
juil. 01 17:45:19 vougeot systemd[1]: plymouth-start.service: Start request 
repeated too quickly.
juil. 01 17:45:19 vougeot systemd[1]: Failed to start Show Plymouth Boot Screen.
juil. 01 17:45:19 vougeot systemd[1]: Found device SAMSUNG_SSD_830_Series 5.
juil. 01 17:45:19 vougeot systemd[1]: Starting Cryptography Setup for 
cryptswap1...
juil. 01 17:45:19 vougeot systemd[1]: plymouth-start.service: Start request 
repeated too quickly.
juil. 01 17:45:19 vougeot systemd[1]: Failed to start Show Plymouth Boot Screen.
juil. 01 17:45:19 vougeot systemd[1]: plymouth-read-write.service: Start 
request repeated too quickly.
juil. 01 17:45:19 vougeot systemd[1]: Failed to start Tell Plymouth To Write 
Out Runtime Data.

and more of the same kind a bit later (I will post complete boot
logs...).

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

Title:
  Many error message such as "Start request repeated too quickly."

Status in laptop-mode-tools package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in laptop-mode-tools source package in Xenial:
  New
Status in systemd source package in Xenial:
  In Progress

Bug description:
  * Analysis:

  The error messages are caused by a bad interaction between systemd and
  laptop-mode-tools.

  * Fixes:

  There is a fix in systemd:
  https://github.com/systemd/systemd/pull/3148

  The problem can also be fixed by updating laptop-mode-tools.

  * Symptoms:

  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary 
Formats.
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root 
Device.
  Apr 08 20:23:50 xeelee systemd[1]: Started Show Plymouth Boot Screen.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-hwdb-update.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Rebuild Hardware Database.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary 
Formats.
  Apr 08 20:23:50 xeelee systemd[1]: Starting Show Plymouth Boot Screen...
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root 
Device.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary 
Formats.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-hwdb-update.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Rebuild Hardware Database.
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: 

[Touch-packages] [Bug 1597681] Re: [CTA] Enable WAPI support

[Alejandro J. Cura]

** Changed in: indicator-network (Ubuntu)
   Importance: Undecided => High

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

** Changed in: indicator-network (Ubuntu)
 Assignee: (unassigned) => Pete Woods (pete-woods)

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

Title:
  [CTA] Enable WAPI support

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  The phone does not currently support WAPI [1]

  It should do so. As part of this, support for the SMS4 [2] cipher is
  also required.

  
  [1] 
https://en.wikipedia.org/wiki/WLAN_Authentication_and_Privacy_Infrastructure
  [2]: https://en.wikipedia.org/wiki/SMS4

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

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

[Touch-packages] [Bug 1274167] Re: Webkit broken on PowerPC - JSC::LLInt::CLoop

[Herminio]

I can confirm that everything is working now. This can be closed

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

Title:
  Webkit broken on PowerPC - JSC::LLInt::CLoop

Status in ubiquity:
  New
Status in WebKit:
  Unknown
Status in qtwebkit-opensource-src package in Ubuntu:
  Fix Released
Status in qtwebkit-source package in Ubuntu:
  Confirmed
Status in webkitgtk package in Ubuntu:
  Fix Released
Status in qtwebkit package in Debian:
  Fix Released
Status in webkitgtk package in Debian:
  Fix Released

Bug description:
  Midori crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: midori 0.4.3+dfsg-0.1
  Uname: Linux 3.13.0_A-EON_AmigaOne_X1000_Nemo ppc64
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: powerpc
  CrashCounter: 1
  CurrentDesktop: LXDE
  Date: Wed Jan 29 16:58:54 2014
  ExecutablePath: /usr/bin/midori
  ProcCmdline: midori
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: midori
  StacktraceTop:
   JSC::LLInt::CLoop::execute(JSC::ExecState*, void*, bool) () from 
/usr/lib/powerpc-linux-gnu/libjavascriptcoregtk-1.0.so.0
   callToJavaScript () from 
/usr/lib/powerpc-linux-gnu/libjavascriptcoregtk-1.0.so.0
   JSC::JITCode::execute(JSC::VM*, JSC::ProtoCallFrame*, JSC::Register*) () 
from /usr/lib/powerpc-linux-gnu/libjavascriptcoregtk-1.0.so.0
   JSC::Interpreter::execute(JSC::ProgramExecutable*, JSC::ExecState*, 
JSC::JSObject*) () from /usr/lib/powerpc-linux-gnu/libjavascriptcoregtk-1.0.so.0
   JSC::evaluate(JSC::ExecState*, JSC::SourceCode const&, JSC::JSValue, 
JSC::JSValue*) () from /usr/lib/powerpc-linux-gnu/libjavascriptcoregtk-1.0.so.0
  Title: midori crashed with SIGSEGV in JSC::LLInt::CLoop::execute()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video

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

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

[Touch-packages] [Bug 1586673] Re: Backport GCC 5.4.0 and binutils 2.26.1 to 16.04 LTS

[Martin Pitt]

** Changed in: gcc-5 (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  Backport GCC 5.4.0 and binutils 2.26.1 to 16.04 LTS

Status in binutils package in Ubuntu:
  Fix Released
Status in gcc-5 package in Ubuntu:
  Fix Committed
Status in binutils source package in Xenial:
  Fix Committed
Status in gcc-5 source package in Xenial:
  New

Bug description:
  Backport GCC 5.4.0 and binutils 2.26.1 to 16.04 LTS.  16.04 LTS ships
  binutils and gcc-5 versions taken from the release branches, which saw
  more regression fixes and support for new hardware until the 5.4.0 and
  2.26.1 point releases. The idea is to include these final point
  releases into 16.04.1 LTS, with test rebuilds done for all packages,
  and regression checks for seeded packages.

  Acceptance criteria should be no regressions for the seeded packages,
  plus a best effort for unseeded packages.  During the analysis of the
  build failures, one gcc regression (libstdc++ header reorg) was found
  and reverted, and validated, that these build failures are fixed (plus
  affected seeded packages were uploaded to xenial-proposed anyway).

  reference test rebuild:
  
http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20160614-baseline-xenial.html

  test rebuild (xenial-release):
  
http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20160614-xenial.html

  test rebuild (xenial-updates):
  
http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20160614-updates-xenial.html

  The test rebuild was done using packages from the ubuntu-
  toolchain-r/ppa.

  Attached is an analysis of the build failures, and whether they are
  regressions, or already are present in the xenial release.

  main component
  ==

  bzr
LP: #1592731, fixed in -proposed
  ecj
LP: #1592801, fixed in -updates
  freerdp
not a regression
  gcc-5-cross
needs update after gcc-5 acceptance
  gnutls28
LP: #1592693, fixed in -updates
  kmod
unrelated, tracked in LP: #1592722
  libnih
not a regression
  llvm-toolchain-3.6
not a regression
  migrate
unrelated (mysql-5.7), tracked in LP: #1592663
  neon27 (s390x)
unrelated, traked in LP: #1592698
  openvswitch
not a regression, tracked in LP: #1592793
  python-pymysql
unrelated (mysql-5.7), tracked in LP: #1592664
  python-tooz
unrelated, tracked in LP: #1592660
  sbsigntool
not a regression
  shim
not a regression
  strongswan
racy test, unrelated, tracked in LP: #1592706
  ubuntu-defaults-builder
unrelated, LP: #1597370, waiting for approval
  upstart
not a regression
  whoopsie
LP: #1592649, fixed in -updates
  yaboot
not a regression

  bzr package set
  ===

  bzr-builder
  bzr-upload
no regressions

  cli-mono package set
  

  gbrainy
  ikvm
  monodevelop
  tangerine
no regressions

  desktop-extra package set
  =

  java-gnome
not a regressions

  edubuntu package set
  

  atomix
  gbrainy
no regressions

  input-methods package set
  =

  fcitx-table-other
  libkkc
no regressions

  kubuntu package set (minus packages from main)
  ==

  avogadro
not a regression
  eigen2
not a regression
  fam
not a regression
  farstream-0.2
not a regression
  gst-plugins-base0.10
not a regression
  gst-plugins-good0.10
not a regression
  gstreamer0.10
not a regression
  kqoauth
not a regression
  kubuntu-web-shortcuts
not a regression
  libmpc
not a regression
  libmygpo-qt
not a regression
  libspe2
not a regression
  networkmanager-qt
obsoleted by version in -updates
  plotutils
not a regression
  qtcurve
not a regression
  tbb
not a regression
  telepathy-haze
not a regression
  telepathy-qt
not a regression

  
  lubuntu package set
  

  hardinfo
not a regression
  libguess
not a regression

  mozilla package set
  

  eclipse
  xiphos
no regressions

  mythbuntu package set
  =

  piston-mini-client
not a regression

  schooltool package set
  ==

  schooltool-book
not a regression

  ubuntu-cloud package set
  

  virtualbox
needs fix for bad GCC version check, in progress (LocutusOfBorg)

  ubuntu-qt-packages package set
  ==

  ciborium
not a regression

  ubuntukylin package set
  ===

  libguess
  

[Touch-packages] [Bug 1461873] Re: [CTA] Ability to forward SMS without copy 'n past approach

[Launchpad Bug Tracker]

This bug was fixed in the package messaging-app -
0.1+16.10.20160630-0ubuntu1

---
messaging-app (0.1+16.10.20160630-0ubuntu1) yakkety; urgency=medium

  * Implement support for message forwarding. (LP: #1461873)

 -- Tiago Salem Herrmann   Thu, 30 Jun
2016 12:52:56 +

** Changed in: messaging-app (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  [CTA] Ability to forward SMS without copy 'n past approach

Status in Canonical System Image:
  Fix Committed
Status in Ubuntu UX:
  Fix Committed
Status in messaging-app package in Ubuntu:
  Fix Released

Bug description:
  It would be nice if the SMS app swipe left context had the ability to forward 
the SMS to other receivers.
  The existing approah where one can swipe left and copy the content and then 
paste into a new SMS seems less intuitive.

  **

  This feature is in the new designs but has yet to be implemented.
  https://docs.google.com/presentation/d/1hkrF2g-
  ad7fhJ0UVLKmu_5ZXSFK1EkcWS129JxmAAI4/edit#slide=id.p97

  **

  This is a certification requirement

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

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

[Touch-packages] [Bug 1342400] Re: avahi-daemon constantly reporting "Invalid response packet from host"

[Pali]

Ubuntu precise version working, verified.

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

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

Title:
  avahi-daemon constantly reporting "Invalid response packet from host"

Status in avahi package in Ubuntu:
  Fix Released
Status in avahi source package in Precise:
  Fix Committed
Status in avahi source package in Trusty:
  Fix Committed
Status in avahi package in Debian:
  Fix Released

Bug description:
  After installing Ubuntu 14.04 (Release: 14.04) and looking for other
  information in /var/log/syslog, I see that syslog is being flooded by
  "Invalid response packet from host" messages from avahi-daemon.

  I searched around to see why this might be and ran across the following avahi 
mailing list post along with a patch to fix it:
  http://lists.freedesktop.org/archives/avahi/2012-July/002171.html

  >>>
  I would say you can safely ignore it, since any machine on your
  network running a recent OSX version will cause these messages.
  Here's a patch with what we change to avoid these messages flooding
  syslog.

  -Justin
  <<<

  The patch which fixes this is here:
  
http://lists.freedesktop.org/archives/avahi/attachments/20120719/1e71846e/attachment.obj

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

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

[Touch-packages] [Bug 1598136] Re: Fails to produce a loop-mountable FS on powerpc/armhf

[Theodore Ts'o]

Looks like you are using a pre-3.18 kernel with e2fsprogs 1.43.1.   I'm
guessing this is because whatever cloud service you are using is using a
very old kernel?   (In contrast, Yakkety Yak is using a 4.x kernel.)

What kernel version is this cloud service using, anyway?   I want to
make a mental note to stay far, far, far away.  :-)

We'd have to see the exact kernel version to be sure (and there should
be some hints in the log messages), but at a guess, try building the
file system with "mke2fs -O ^metadata_csum" and see if that fixes things
for you.

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

Title:
  Fails to produce a loop-mountable FS on powerpc/armhf

Status in cloud-images:
  New
Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  In yakkety cloud image builds for each of powerpc and armhf (but not
  amd64, i386, ppc64el, arm64 or s390x) we see the following failure:

  [2016-07-01 09:51:08] lb_binary_chroot
  P: Begin copying chroot...
  [2016-07-01 09:51:08] lb_binary_rootfs
  P: Begin building root filesystem image...
  0+0 records in
  0+0 records out
  0 bytes copied, 3.7116e-05 s, 0.0 kB/s
  mke2fs 1.43.1 (08-Jun-2016)
  ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing 
mtab file while determining whether binary/boot/filesystem.ext4 is mounted.
  Suggestion: Use Linux kernel >= 3.18 for improved stability of the metadata 
and journal checksum features.
  Discarding device blocks:   4096/343040 
done
  Creating filesystem with 343040 4k blocks and 171600 inodes
  Filesystem UUID: 43ff7fc9-12bb-4151-8549-77c8e1e35e2c
  Superblock backups stored on blocks:
   32768, 98304, 163840, 229376, 294912

  Allocating group tables:  0/11 done
  Writing inode tables:  0/11 done
  Creating journal (8192 blocks): done
  Writing superblocks and filesystem accounting information:  0/11 
done

  mount: wrong fs type, bad option, bad superblock on /dev/loop0,
     missing codepage or helper program, or other error

     In some cases useful info is found in syslog - try
     dmesg | tail or so.

  This is caused by this code in live-build's lb_binary_rootfs script:

  dd if=/dev/zero of=binary/${INITFS}/filesystem.${LB_CHROOT_FILESYSTEM} 
bs=1024k count=0 seek=${REAL_DIM}
  mkfs.${LB_CHROOT_FILESYSTEM} -F -b ${LB_EXT_BLOCKSIZE:-1024} -i 8192 -m 0 -L 
${LB_HDD_LABEL} ${LB_EXT_RESIZEBLOCKS:+-E resize=${LB_EXT_RESIZEBLOCKS}} 
binary/${INITFS}/filesystem.${LB_CHROOT_FILESYSTEM}

  mkdir -p filesystem.tmp
  ${LB_ROOT_COMMAND} mount -o loop 
binary/${INITFS}/filesystem.${LB_CHROOT_FILESYSTEM} filesystem.tmp

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1598136/+subscriptions

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

[Touch-packages] [Bug 1451525] Re: package libcurl4-gnutls-dev 7.37.1-1ubuntu3.4 failed to install/upgrade: trying to overwrite shared '/usr/bin/curl-config', which is different from other instances o

[Launchpad Bug Tracker]

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

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

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

Title:
  package libcurl4-gnutls-dev 7.37.1-1ubuntu3.4 failed to
  install/upgrade: trying to overwrite shared '/usr/bin/curl-config',
  which is different from other instances of package libcurl4-gnutls-
  dev:i386

Status in curl package in Ubuntu:
  Confirmed

Bug description:
  i install i386 version on amd64

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: libcurl4-gnutls-dev 7.37.1-1ubuntu3.4
  Uname: Linux 3.19.0-031900-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.4
  Architecture: amd64
  Date: Mon May  4 18:22:25 2015
  DuplicateSignature: package:libcurl4-gnutls-dev:7.37.1-1ubuntu3.4:trying to 
overwrite shared '/usr/bin/curl-config', which is different from other 
instances of package libcurl4-gnutls-dev:i386
  ErrorMessage: trying to overwrite shared '/usr/bin/curl-config', which is 
different from other instances of package libcurl4-gnutls-dev:i386
  SourcePackage: curl
  Title: package libcurl4-gnutls-dev 7.37.1-1ubuntu3.4 failed to 
install/upgrade: trying to overwrite shared '/usr/bin/curl-config', which is 
different from other instances of package libcurl4-gnutls-dev:i386
  UpgradeStatus: Upgraded to utopic on 2015-04-27 (6 days ago)

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

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

[Touch-packages] [Bug 1597755] Re: No ringtone or message tone in headphones in silent mode

[Marcus Tomlinson]

@jhodapp: I'd say yes, makes sense to me that the ringtone should come
through both the speaker and the headphones.

E.g.
- when you're listening to music on headphones, you may not hear the phone 
speaker.
- you've got headphones plugged in but temporarily not using them, you'd still 
want to hear your phone ring.

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

Title:
  No ringtone or message tone in headphones in silent mode

Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu RTM:
  Confirmed

Bug description:
  When in silent mode, ringtones and message tones do not play in
  headphones.

  They are supposed to according to: https://wiki.ubuntu.com/Sound

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

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

[Touch-packages] [Bug 1590804] Re: fontconfig initialization spends most of its time parsing XML configuration files in /etc/fonts/conf.d/

[Alberto Aguirre]

So actually, fontconfig does not cache conf files at all... it caches
fonts but not conf files...

fontconfg needs support to also cache the result of the parsing of the
xml config file parsing. It seems a low priority effort for less than a
35ms improvement in startup.

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

Title:
  fontconfig initialization spends most of its time parsing XML
  configuration files in /etc/fonts/conf.d/

Status in Canonical System Image:
  In Progress
Status in fontconfig package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  Invalid

Bug description:
  While profiling the startup of QML apps on the BQ E4.5 phone (armhf) I 
noticed that a significant amount of time (around 35ms) was spent solely on 
parsing the XML configuration files in /etc/fonts/conf.d/ 
  There seems to be around 40 files on Ubuntu Phone in that directory.

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

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

[Touch-packages] [Bug 1590804] Re: fontconfig initialization spends most of its time parsing XML configuration files in /etc/fonts/conf.d/

[Alberto Aguirre]

Also FcInitReinitialize and FcInitBringUptoDate both will do the same
thing the first time is called in the process, so wouldn't help for
startup either.


** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Invalid

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

Title:
  fontconfig initialization spends most of its time parsing XML
  configuration files in /etc/fonts/conf.d/

Status in Canonical System Image:
  In Progress
Status in fontconfig package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  Invalid

Bug description:
  While profiling the startup of QML apps on the BQ E4.5 phone (armhf) I 
noticed that a significant amount of time (around 35ms) was spent solely on 
parsing the XML configuration files in /etc/fonts/conf.d/ 
  There seems to be around 40 files on Ubuntu Phone in that directory.

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

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

[Touch-packages] [Bug 1552928] Re: New bottom edge component is harder to flick up

[Pat McGowan]

I agree with the report as described and by default the edge should be easier 
to enable.
@zsombi I didn't understand your comment on the clock implementation

** Changed in: canonical-devices-system-image
   Importance: Undecided => High

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

** Changed in: canonical-devices-system-image
Milestone: None => 13

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Zoltan Balogh (bzoltan)

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Zsombor Egri (zsombi)

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

Title:
  New bottom edge component is harder to flick up

Status in Canonical System Image:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  I usually hold the phone in one hand and open the bottom edge by
  flicking up from the bottom with the thumb. This worked fine with the
  previous bottom edge, however, with the new one, there seems to be
  larger amount of dragging required. I keep on failing to open the
  bottom edge in the messages-app and clock app, now that they use the
  new component.

  When dragging very slowly such an big required distance does make
  sense, but for quick flicks with the thumb, it should also take the
  speed and/or touch points history into account and reduce the required
  distance if it detects a fast flick gesture.

  In the right edge implementation for instance, it tracks the touch
  points and already activates the gesture after a rather short distance
  (2 grid units), provided it is a one-way gesture with increasing
  distance from the edge in each recognized point. Such a logic would
  imo also make sense for the bottom edge.

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

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

[Touch-packages] [Bug 1598218] Re: package linux-image-extra-3.16.0-73-generic 3.16.0-73.95~14.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-extra-3.16.0-73-generic 3.16.0-73.95~14.04.1
  failed to install/upgrade: run-parts: /etc/kernel/postinst.d
  /initramfs-tools exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Partial upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-extra-3.16.0-73-generic 3.16.0-73.95~14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-71.92~14.04.1-generic 3.16.7-ckt27
  Uname: Linux 3.16.0-71-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  AptOrdering:
   linux-image-extra-3.16.0-73-generic: Remove
   linux-image-3.16.0-73-generic: Remove
   linux-image-extra-3.16.0-76-generic: Remove
   linux-image-3.16.0-71-generic: Configure
   linux-image-extra-3.16.0-71-generic: Configure
  Architecture: amd64
  Date: Fri Jul  1 11:16:18 2016
  DuplicateSignature: 
package:linux-image-extra-3.16.0-73-generic:3.16.0-73.95~14.04.1:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 1
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2015-12-06 (207 days ago)
  InstallationMedia: Edubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-3.16.0-73-generic 3.16.0-73.95~14.04.1 
failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools 
exited with return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1598220] Re: package linux-image-extra-3.16.0-71-generic 3.16.0-71.92~14.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-extra-3.16.0-71-generic 3.16.0-71.92~14.04.1
  failed to install/upgrade: run-parts: /etc/kernel/postinst.d
  /initramfs-tools exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I am using this kernel but the partial upgrade needs to install it??

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-extra-3.16.0-71-generic 3.16.0-71.92~14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-71.92~14.04.1-generic 3.16.7-ckt27
  Uname: Linux 3.16.0-71-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Fri Jul  1 11:40:55 2016
  DpkgHistoryLog:
   Start-Date: 2016-07-01  11:40:33
   Install: linux-image-3.16.0-73-generic:amd64 (3.16.0-73.95~14.04.1, 
automatic), linux-image-3.16.0-76-generic:amd64 (3.16.0-76.98~14.04.1, 
automatic)
   Upgrade: oneconf:amd64 (0.3.7, 0.3.7.14.04.1), libgail-3-0:amd64 
(3.10.8-0ubuntu1.4, 3.10.8-0ubuntu1.6), libnautilus-extension1a:amd64 
(3.10.1-0ubuntu9.6, 3.10.1-0ubuntu9.11), gir1.2-gtk-3.0:amd64 
(3.10.8-0ubuntu1.4, 3.10.8-0ubuntu1.6), python3-oneconf:amd64 (0.3.7, 
0.3.7.14.04.1), libgtk-3-bin:amd64 (3.10.8-0ubuntu1.4, 3.10.8-0ubuntu1.6), 
nautilus:amd64 (3.10.1-0ubuntu9.6, 3.10.1-0ubuntu9.11), libmm-glib0:amd64 
(1.0.0-2ubuntu1, 1.0.0-2ubuntu1.1), libgtk-3-0:amd64 (3.10.8-0ubuntu1.4, 
3.10.8-0ubuntu1.6), oneconf-common:amd64 (0.3.7, 0.3.7.14.04.1), 
modemmanager:amd64 (1.0.0-2ubuntu1, 1.0.0-2ubuntu1.1), nautilus-data:amd64 
(3.10.1-0ubuntu9.6, 3.10.1-0ubuntu9.11), libgtk-3-common:amd64 
(3.10.8-0ubuntu1.4, 3.10.8-0ubuntu1.6), python-oneconf:amd64 (0.3.7, 
0.3.7.14.04.1)
  DuplicateSignature: 
package:linux-image-extra-3.16.0-71-generic:3.16.0-71.92~14.04.1:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 1
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2015-12-06 (207 days ago)
  InstallationMedia: Edubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-3.16.0-71-generic 3.16.0-71.92~14.04.1 
failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools 
exited with return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1598212] Re: /etc/os-release: Please specify VERSION_CODENAME

[Benjamin Drung]

** Bug watch added: Debian Bug tracker #829245
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829245

** Also affects: base-files (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829245
   Importance: Unknown
   Status: Unknown

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

Title:
  /etc/os-release: Please specify VERSION_CODENAME

Status in base-files package in Ubuntu:
  New
Status in base-files package in Debian:
  Unknown

Bug description:
  The os-release specification was updated in systemd > 230 to also
  include a VERSION_CODENAME parameter:
  
https://github.com/systemd/systemd/commit/646b997c118e261c5ececc434dd40d0dbdbac4d8

  Please replace the custom UBUNTU_CODENAME parameter by
  VERSION_CODENAME in yakkety and add VERSION_CODENAME to /etc/os-
  release to all stable releases.

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

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

[Touch-packages] [Bug 1598218] [NEW] package linux-image-extra-3.16.0-73-generic 3.16.0-73.95~14.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return co

[cltien]

Public bug reported:

Partial upgrade

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-extra-3.16.0-73-generic 3.16.0-73.95~14.04.1
ProcVersionSignature: Ubuntu 3.16.0-71.92~14.04.1-generic 3.16.7-ckt27
Uname: Linux 3.16.0-71-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
AptOrdering:
 linux-image-extra-3.16.0-73-generic: Remove
 linux-image-3.16.0-73-generic: Remove
 linux-image-extra-3.16.0-76-generic: Remove
 linux-image-3.16.0-71-generic: Configure
 linux-image-extra-3.16.0-71-generic: Configure
Architecture: amd64
Date: Fri Jul  1 11:16:18 2016
DuplicateSignature: 
package:linux-image-extra-3.16.0-73-generic:3.16.0-73.95~14.04.1:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 1
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
InstallationDate: Installed on 2015-12-06 (207 days ago)
InstallationMedia: Edubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.14
SourcePackage: initramfs-tools
Title: package linux-image-extra-3.16.0-73-generic 3.16.0-73.95~14.04.1 failed 
to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited 
with return code 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package trusty

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

Title:
  package linux-image-extra-3.16.0-73-generic 3.16.0-73.95~14.04.1
  failed to install/upgrade: run-parts: /etc/kernel/postinst.d
  /initramfs-tools exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Partial upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-extra-3.16.0-73-generic 3.16.0-73.95~14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-71.92~14.04.1-generic 3.16.7-ckt27
  Uname: Linux 3.16.0-71-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  AptOrdering:
   linux-image-extra-3.16.0-73-generic: Remove
   linux-image-3.16.0-73-generic: Remove
   linux-image-extra-3.16.0-76-generic: Remove
   linux-image-3.16.0-71-generic: Configure
   linux-image-extra-3.16.0-71-generic: Configure
  Architecture: amd64
  Date: Fri Jul  1 11:16:18 2016
  DuplicateSignature: 
package:linux-image-extra-3.16.0-73-generic:3.16.0-73.95~14.04.1:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 1
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2015-12-06 (207 days ago)
  InstallationMedia: Edubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-3.16.0-73-generic 3.16.0-73.95~14.04.1 
failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools 
exited with return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1598220] [NEW] package linux-image-extra-3.16.0-71-generic 3.16.0-71.92~14.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return co

[cltien]

Public bug reported:

I am using this kernel but the partial upgrade needs to install it??

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-extra-3.16.0-71-generic 3.16.0-71.92~14.04.1
ProcVersionSignature: Ubuntu 3.16.0-71.92~14.04.1-generic 3.16.7-ckt27
Uname: Linux 3.16.0-71-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
Date: Fri Jul  1 11:40:55 2016
DpkgHistoryLog:
 Start-Date: 2016-07-01  11:40:33
 Install: linux-image-3.16.0-73-generic:amd64 (3.16.0-73.95~14.04.1, 
automatic), linux-image-3.16.0-76-generic:amd64 (3.16.0-76.98~14.04.1, 
automatic)
 Upgrade: oneconf:amd64 (0.3.7, 0.3.7.14.04.1), libgail-3-0:amd64 
(3.10.8-0ubuntu1.4, 3.10.8-0ubuntu1.6), libnautilus-extension1a:amd64 
(3.10.1-0ubuntu9.6, 3.10.1-0ubuntu9.11), gir1.2-gtk-3.0:amd64 
(3.10.8-0ubuntu1.4, 3.10.8-0ubuntu1.6), python3-oneconf:amd64 (0.3.7, 
0.3.7.14.04.1), libgtk-3-bin:amd64 (3.10.8-0ubuntu1.4, 3.10.8-0ubuntu1.6), 
nautilus:amd64 (3.10.1-0ubuntu9.6, 3.10.1-0ubuntu9.11), libmm-glib0:amd64 
(1.0.0-2ubuntu1, 1.0.0-2ubuntu1.1), libgtk-3-0:amd64 (3.10.8-0ubuntu1.4, 
3.10.8-0ubuntu1.6), oneconf-common:amd64 (0.3.7, 0.3.7.14.04.1), 
modemmanager:amd64 (1.0.0-2ubuntu1, 1.0.0-2ubuntu1.1), nautilus-data:amd64 
(3.10.1-0ubuntu9.6, 3.10.1-0ubuntu9.11), libgtk-3-common:amd64 
(3.10.8-0ubuntu1.4, 3.10.8-0ubuntu1.6), python-oneconf:amd64 (0.3.7, 
0.3.7.14.04.1)
DuplicateSignature: 
package:linux-image-extra-3.16.0-71-generic:3.16.0-71.92~14.04.1:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 1
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
InstallationDate: Installed on 2015-12-06 (207 days ago)
InstallationMedia: Edubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.14
SourcePackage: initramfs-tools
Title: package linux-image-extra-3.16.0-71-generic 3.16.0-71.92~14.04.1 failed 
to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited 
with return code 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package trusty

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

Title:
  package linux-image-extra-3.16.0-71-generic 3.16.0-71.92~14.04.1
  failed to install/upgrade: run-parts: /etc/kernel/postinst.d
  /initramfs-tools exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I am using this kernel but the partial upgrade needs to install it??

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-extra-3.16.0-71-generic 3.16.0-71.92~14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-71.92~14.04.1-generic 3.16.7-ckt27
  Uname: Linux 3.16.0-71-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Fri Jul  1 11:40:55 2016
  DpkgHistoryLog:
   Start-Date: 2016-07-01  11:40:33
   Install: linux-image-3.16.0-73-generic:amd64 (3.16.0-73.95~14.04.1, 
automatic), linux-image-3.16.0-76-generic:amd64 (3.16.0-76.98~14.04.1, 
automatic)
   Upgrade: oneconf:amd64 (0.3.7, 0.3.7.14.04.1), libgail-3-0:amd64 
(3.10.8-0ubuntu1.4, 3.10.8-0ubuntu1.6), libnautilus-extension1a:amd64 
(3.10.1-0ubuntu9.6, 3.10.1-0ubuntu9.11), gir1.2-gtk-3.0:amd64 
(3.10.8-0ubuntu1.4, 3.10.8-0ubuntu1.6), python3-oneconf:amd64 (0.3.7, 
0.3.7.14.04.1), libgtk-3-bin:amd64 (3.10.8-0ubuntu1.4, 3.10.8-0ubuntu1.6), 
nautilus:amd64 (3.10.1-0ubuntu9.6, 3.10.1-0ubuntu9.11), libmm-glib0:amd64 
(1.0.0-2ubuntu1, 1.0.0-2ubuntu1.1), libgtk-3-0:amd64 (3.10.8-0ubuntu1.4, 
3.10.8-0ubuntu1.6), oneconf-common:amd64 (0.3.7, 0.3.7.14.04.1), 
modemmanager:amd64 (1.0.0-2ubuntu1, 1.0.0-2ubuntu1.1), nautilus-data:amd64 
(3.10.1-0ubuntu9.6, 3.10.1-0ubuntu9.11), libgtk-3-common:amd64 
(3.10.8-0ubuntu1.4, 3.10.8-0ubuntu1.6), python-oneconf:amd64 (0.3.7, 
0.3.7.14.04.1)
  DuplicateSignature: 
package:linux-image-extra-3.16.0-71-generic:3.16.0-71.92~14.04.1:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 1
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2015-12-06 (207 days ago)
  InstallationMedia: Edubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-3.16.0-71-generic 3.16.0-71.92~14.04.1 
failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools 
exited with return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: 

[Touch-packages] [Bug 1492252] Re: Allow direct linking to a Preview via uri

[Pat McGowan]

** Changed in: canonical-devices-system-image
   Importance: Undecided => Wishlist

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Alejandro J. Cura (alecu)

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

Title:
  Allow direct linking to a Preview via uri

Status in Client Developer Experience:
  New
Status in Canonical System Image:
  Confirmed
Status in unity-scopes-api package in Ubuntu:
  Confirmed
Status in unity-scopes-shell package in Ubuntu:
  Confirmed

Bug description:
  I can already link to a scopes search via the scope:// protocol but it
  would be great to be able to link directly to a preview page via a
  scope:// uri. This would be especially helpful for uApp Explorer to
  link directly to an app in the official store (rather than the search
  page like it does now).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-developer-experience/+bug/1492252/+subscriptions

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

[Touch-packages] [Bug 1552318] Re: unity-scope-click relies on unity8 Preview Item for communication with libpay

[Pat McGowan]

Is there a way to fix this by modifying the UI to contain the user
through the entire process?

** Changed in: canonical-devices-system-image
   Importance: Undecided => High

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Alejandro J. Cura (alecu)

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

Title:
  unity-scope-click relies on unity8 Preview Item for communication with
  libpay

Status in Canonical System Image:
  Confirmed
Status in unity-scope-click package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  On unity8 PreviewPayments.qml has a Payments item that listens to
    onPurchaseCompleted
    onPurchaseError
    onPurchaseCancelled
  and relies those to the scope.

  The problem is that there's no guarantee that the PreviewPayments item
  will be around for the whole buying process, since i can press the buy
  button and quickly press the back button before the payui shows up so
  it will get destroyed.

  We need to evaluate how bad is if those signals from libpay are lost
  and if it is bad think of a way to make this more resilient.

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

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

[Touch-packages] [Bug 1457400] Re: reduce 90s session kill timeout if the session does not shutdown cleanly

[Andre T]

Hi

Had the same issue with a VirtualBox Ubuntu Mate 16.04.
I upgrade kernel to version 4.6.3 and for the time being the issue is gone.

Thanks

A

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

Title:
  reduce 90s session kill timeout if the session does not shutdown
  cleanly

Status in lvm2 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I use Ubuntu 15.04 with Unity, I have a SSD drive also. Very recently
  onwards the ubuntu is taking long to shut down nearly 1:30 minutes.

  I checked the shutdown log messages and I get the follow message.

  A stop job is running for Session c2 of user * (25s/ 1min 30 s)

  It count downs till 1:30 minutes and then shutdown the machine.

  Why is it happening.

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

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

[Touch-packages] [Bug 1586419] Re: sms drafts are lost when hitting "back" when composing

[Pat McGowan]

** No longer affects: address-book-app (Ubuntu)

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

Title:
  sms drafts are lost when hitting "back" when composing

Status in Canonical System Image:
  Confirmed
Status in messaging-app:
  New

Bug description:
  I'm used to be able to start composing an sms, maybe going back to the
  dialog, send another (maybe more urgent one), or check some info in
  another sms, and go back to the one I was composing to finish it. In
  UP all drafts get lost, maybe we could save the state for each
  conversation?

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

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

[Touch-packages] [Bug 1587517] Re: add sms draft

[Pat McGowan]

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

** This bug has been marked a duplicate of bug 1586419
   sms drafts are lost when hitting "back" when composing

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

Title:
  add sms draft

Status in Canonical System Image:
  Triaged
Status in Ubuntu UX:
  New
Status in messaging-app package in Ubuntu:
  Confirmed

Bug description:
  Right now, when you start a sms, you have to send it or you will lose
  any typed text.

  the sms app should save the typed text as a draft and allow one to
  continue the message later

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

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

[Touch-packages] [Bug 1598212] Re: /etc/os-release: Please specify VERSION_CODENAME

[Steve Langasek]

should be an addition of VERSION_CODENAME in yakkety rather than a
straight replace. snapd, for instance, consumes UBUNTU_CODENAME, since
it's the only field in /etc/os-release with this information
currently

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

Title:
  /etc/os-release: Please specify VERSION_CODENAME

Status in base-files package in Ubuntu:
  New

Bug description:
  The os-release specification was updated in systemd > 230 to also
  include a VERSION_CODENAME parameter:
  
https://github.com/systemd/systemd/commit/646b997c118e261c5ececc434dd40d0dbdbac4d8

  Please replace the custom UBUNTU_CODENAME parameter by
  VERSION_CODENAME in yakkety and add VERSION_CODENAME to /etc/os-
  release to all stable releases.

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

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

[Touch-packages] [Bug 1598212] Re: /etc/os-release: Please specify VERSION_CODENAME

[Martin Pitt]

This warrants an archive grep for UBUNTU_CODENAME first; I think Michael
Vogt added that the other day, so presumably it's being used in snappy?
So for the time being it'd be better to have both until users of
UBUNTU_CODENAME get updated.

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

Title:
  /etc/os-release: Please specify VERSION_CODENAME

Status in base-files package in Ubuntu:
  New

Bug description:
  The os-release specification was updated in systemd > 230 to also
  include a VERSION_CODENAME parameter:
  
https://github.com/systemd/systemd/commit/646b997c118e261c5ececc434dd40d0dbdbac4d8

  Please replace the custom UBUNTU_CODENAME parameter by
  VERSION_CODENAME in yakkety and add VERSION_CODENAME to /etc/os-
  release to all stable releases.

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

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

[Touch-packages] [Bug 1589703] Re: Alarm clock icon doesn't disappear (appears randomly) when alarm inactive

[Pat McGowan]

** Changed in: canonical-devices-system-image
   Importance: Undecided => Medium

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

** Changed in: canonical-devices-system-image
Milestone: None => 13

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Alejandro J. Cura (alecu)

** Changed in: indicator-datetime (Ubuntu)
 Assignee: (unassigned) => Charles Kerr (charlesk)

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

Title:
  Alarm clock icon doesn't disappear (appears randomly) when alarm
  inactive

Status in Canonical System Image:
  Confirmed
Status in Ubuntu Clock App:
  New
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  As in description. In my bq i see sometimes an alarm clock icon even
  if the alarm time passed and the alarm clock is no longer active.

  Set the alarm clock
  Let it ring and turn it off. The icon stays visible for some time which i can 
not exactly specify.

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

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

[Touch-packages] [Bug 1598212] [NEW] /etc/os-release: Please specify VERSION_CODENAME

[Benjamin Drung]

Public bug reported:

The os-release specification was updated in systemd > 230 to also
include a VERSION_CODENAME parameter:
https://github.com/systemd/systemd/commit/646b997c118e261c5ececc434dd40d0dbdbac4d8

Please replace the custom UBUNTU_CODENAME parameter by VERSION_CODENAME
in yakkety and add VERSION_CODENAME to /etc/os-release to all stable
releases.

** Affects: base-files (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  /etc/os-release: Please specify VERSION_CODENAME

Status in base-files package in Ubuntu:
  New

Bug description:
  The os-release specification was updated in systemd > 230 to also
  include a VERSION_CODENAME parameter:
  
https://github.com/systemd/systemd/commit/646b997c118e261c5ececc434dd40d0dbdbac4d8

  Please replace the custom UBUNTU_CODENAME parameter by
  VERSION_CODENAME in yakkety and add VERSION_CODENAME to /etc/os-
  release to all stable releases.

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

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

[Touch-packages] [Bug 1587305] Re: Add support for USB-LAN adapter

[Pat McGowan]

another ip6 related issue?

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

** Changed in: network-manager (Ubuntu)
 Assignee: (unassigned) => Tony Espy (awe)

** Changed in: canonical-devices-system-image
   Status: Incomplete => Confirmed

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

Title:
  Add support for USB-LAN adapter

Status in Canonical System Image:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  Some users contacted BQ because the USB-LAN adapters they own are not
  recognized by Frieza. They expect the device to automatically
  config/connect to their LAN network. They want the tablet to behave
  the same way as a Ubuntu PC does when LAN/Wi-Fi network is
  connected/disconnected. (I think they should be able to set the
  network through nmcli)

  Product: bq Aquaris E4.5, E5 & M10
  FW version: OTA-10.1
  HW version: MP

  STEPS TO REPRO:
  1. Connect DUT>USB-OTG>USB-LAN adapter>Rj45(picture attached)

  Actual Result:
  USB-LAN adapter is not recognized or it does not auto-connect to home LAN

  Expected Result:
  Whether Wifi is on or off, once LAN adapter is connected, it should 
auto-connect to home LAN

  Additional info: here is the link provided by one of the users
  http://de.anker.com/product/A7522012

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

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

[Touch-packages] [Bug 1598210] Re: package linux-image-extra-3.16.0-76-generic 3.16.0-76.98~14.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-extra-3.16.0-76-generic 3.16.0-76.98~14.04.1
  failed to install/upgrade: run-parts: /etc/kernel/postinst.d
  /initramfs-tools exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Tried to uninstall the kernel 3.16.0.73 and 3.16.0.76, which are not
  usable and caused kernel panic during boot. The process reports that
  it failed to uninstall because it is not configured. Hope I can find
  what to do.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-extra-3.16.0-76-generic 3.16.0-76.98~14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-71.92~14.04.1-generic 3.16.7-ckt27
  Uname: Linux 3.16.0-71-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Fri Jul  1 11:10:18 2016
  DuplicateSignature: 
package:linux-image-extra-3.16.0-76-generic:3.16.0-76.98~14.04.1:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 1
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2015-12-06 (207 days ago)
  InstallationMedia: Edubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-3.16.0-76-generic 3.16.0-76.98~14.04.1 
failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools 
exited with return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1591895] Re: SRU: backport python 2.7.12 to 16.04 LTS

[Matthias Klose]

** Description changed:

  SRU: backport python 2.7.12 to 16.04 LTS
+ 
+ The idea is to ship a released version with the first point release of
+ 16.04 LTS.  We updated python2.7 from the the 2.7 branch up to the final
+ 2.7.12 release, and then made a test rebuild of the archive using the
+ new python2.7 (and some other toolchain packages).
+ 
+ The test rebuild was done using the release candidate of 2.7.12, however
+ the only changes between the rc and the final release are Windows
+ related, and include one change in the idle lib. From my point of view
+ we don't need another test rebuild.
+ 
+ The evaluation of the test rebuild is found in LP: #1586673. I'm pretty
+ sure that none of the possible regressions can be attributed to the
+ python2.7 update.

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

Title:
  SRU: backport python 2.7.12 to 16.04 LTS

Status in python2.7 package in Ubuntu:
  New

Bug description:
  SRU: backport python 2.7.12 to 16.04 LTS

  The idea is to ship a released version with the first point release of
  16.04 LTS.  We updated python2.7 from the the 2.7 branch up to the
  final 2.7.12 release, and then made a test rebuild of the archive
  using the new python2.7 (and some other toolchain packages).

  The test rebuild was done using the release candidate of 2.7.12,
  however the only changes between the rc and the final release are
  Windows related, and include one change in the idle lib. From my point
  of view we don't need another test rebuild.

  The evaluation of the test rebuild is found in LP: #1586673. I'm
  pretty sure that none of the possible regressions can be attributed to
  the python2.7 update.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1591895/+subscriptions

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

[Touch-packages] [Bug 1598210] [NEW] package linux-image-extra-3.16.0-76-generic 3.16.0-76.98~14.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return co

[cltien]

Public bug reported:

Tried to uninstall the kernel 3.16.0.73 and 3.16.0.76, which are not
usable and caused kernel panic during boot. The process reports that it
failed to uninstall because it is not configured. Hope I can find what
to do.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-extra-3.16.0-76-generic 3.16.0-76.98~14.04.1
ProcVersionSignature: Ubuntu 3.16.0-71.92~14.04.1-generic 3.16.7-ckt27
Uname: Linux 3.16.0-71-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
Date: Fri Jul  1 11:10:18 2016
DuplicateSignature: 
package:linux-image-extra-3.16.0-76-generic:3.16.0-76.98~14.04.1:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 1
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
InstallationDate: Installed on 2015-12-06 (207 days ago)
InstallationMedia: Edubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.14
SourcePackage: initramfs-tools
Title: package linux-image-extra-3.16.0-76-generic 3.16.0-76.98~14.04.1 failed 
to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited 
with return code 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package trusty

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

Title:
  package linux-image-extra-3.16.0-76-generic 3.16.0-76.98~14.04.1
  failed to install/upgrade: run-parts: /etc/kernel/postinst.d
  /initramfs-tools exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Tried to uninstall the kernel 3.16.0.73 and 3.16.0.76, which are not
  usable and caused kernel panic during boot. The process reports that
  it failed to uninstall because it is not configured. Hope I can find
  what to do.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-extra-3.16.0-76-generic 3.16.0-76.98~14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-71.92~14.04.1-generic 3.16.7-ckt27
  Uname: Linux 3.16.0-71-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Fri Jul  1 11:10:18 2016
  DuplicateSignature: 
package:linux-image-extra-3.16.0-76-generic:3.16.0-76.98~14.04.1:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 1
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2015-12-06 (207 days ago)
  InstallationMedia: Edubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-3.16.0-76-generic 3.16.0-76.98~14.04.1 
failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools 
exited with return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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