[Touch-packages] [Bug 1580865] Re: vim-gtk and/or vim-gnome icon not shown properly

[epii]

The .desktop file was provided by Debian package maintainers previously,
but now this file is provided in the original source repo and is used in
Xenial alternatively. This caused this conflict.

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

Title:
  vim-gtk and/or vim-gnome icon not shown properly

Status in vim package in Ubuntu:
  New

Bug description:
  After upgrading to Xenial, vim-gtk icon is not shown properly. ("?" is
  shown alternatively.)

  From the short examination of the current source package, the cause of
  this problem is that the icon file name specified in .desktop file
  (located in runtime/gvim.desktop) is "gvim" but actual pixmap files
  are named as "vim".

  So, please modify .desktop file or rename icon file names.
  Personally, the latter solution is preferred since the .desktop file is named 
as "gvim".

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

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

[Touch-packages] [Bug 1580865] [NEW] vim-gtk and/or vim-gnome icon not shown properly

[epii]

Public bug reported:

After upgrading to Xenial, vim-gtk icon is not shown properly. ("?" is
shown alternatively.)

>From the short examination of the current source package, the cause of
this problem is that the icon file name specified in .desktop file
(located in runtime/gvim.desktop) is "gvim" but actual pixmap files are
named as "vim".

So, please modify .desktop file or rename icon file names.
Personally, the latter solution is preferred since the .desktop file is named 
as "gvim".

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

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

Title:
  vim-gtk and/or vim-gnome icon not shown properly

Status in vim package in Ubuntu:
  New

Bug description:
  After upgrading to Xenial, vim-gtk icon is not shown properly. ("?" is
  shown alternatively.)

  From the short examination of the current source package, the cause of
  this problem is that the icon file name specified in .desktop file
  (located in runtime/gvim.desktop) is "gvim" but actual pixmap files
  are named as "vim".

  So, please modify .desktop file or rename icon file names.
  Personally, the latter solution is preferred since the .desktop file is named 
as "gvim".

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

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

[Touch-packages] [Bug 1433590] Re: apparmor dbus denial for org.freedesktop.Accounts and make Other vibrations work

[Yuan-Chen Cheng]

** Changed in: canonical-devices-system-image
Milestone: 11 => 12

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

Title:
  apparmor dbus denial for org.freedesktop.Accounts and make Other
  vibrations work

Status in Canonical System Image:
  In Progress
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed
Status in usensord package in Ubuntu:
  In Progress

Bug description:
  This affects vivid and (somewhat recently?) 14.09.

  At some point, apps started to request access to
  org.freedesktop.Accounts for something, but I'm not sure what. It has
  been conjectured in this bug that it is due to vibration settings.
  Filing against ubuntu-system-settings for now, but please feel free to
  move to the correct package.

  This happens with webapps:
  Apr  7 08:42:17 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send" 
name="org.freedesktop.Accounts" pid=2632 
profile="com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26" 
peer_pid=1596 peer_profile="unconfined"
  Apr  7 08:42:17 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.Accounts" member="FindUserById" mask="send" 
name="org.freedesktop.Accounts" pid=2632 
profile="com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26" 
peer_pid=1596 peer_profile="unconfined"

  and QML apps:
  Apr  7 08:43:40 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send" 
name="org.freedesktop.Accounts" pid=3377 
profile="com.ubuntu.calculator_calculator_1.3.339" peer_pid=1596 
peer_profile="unconfined"
  Apr  7 08:43:40 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.Accounts" member="FindUserById" mask="send" 
name="org.freedesktop.Accounts" pid=3377 
profile="com.ubuntu.calculator_calculator_1.3.339" peer_pid=1596 
peer_profile="unconfined"

  The following rules allow the requested access:
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts"
 interface="org.freedesktop.DBus.{Introspectable,Properties}"
 member=Introspect
 peer=(name=org.freedesktop.Accounts,label=unconfined),
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts"
 interface="org.freedesktop.Accounts"
 member=FindUserById
 peer=(name=org.freedesktop.Accounts,label=unconfined),
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts/User[0-9]*"
 interface="org.freedesktop.DBus.Properties"
 member=Get
 peer=(name=org.freedesktop.Accounts,label=unconfined),

  However, the above is too lenient and constitutes a privacy leak for
  apps. FindUserById could be used by a malicious app to enumerate
  usernames on multiuser systems and because we can't mediate method
  data with apparmor, the Get() method can be used to obtain any
  information provided by this interface.

  The following can be used to see what can be leaked to a malicious app:
  gdbus introspect --system -d org.freedesktop.Accounts -o 
/org/freedesktop/Accounts/User`id -u phablet`

  This can be solved in a couple of ways:
  1. add whatever information the app is trying to access to a new helper 
service that only exposes things that the app needs. This could be a single 
standalone service, perhaps something from ubuntu-system-settings, that could 
expose any number of things-- the current locale, if the locale changed, if the 
grid units changed, the vibration settings, etc. Since this service wouldn't 
have any sensitive information, you could use standard dbus 
properties/Get()/etc 
  2. add a new dbus API to an existing service such that apparmor rules can 
then be used to allow by method (eg, GetVibration() or something)

  I won't dictate the implementation except to mention that '1' seems
  like something generally useful and I believe that it was something
  the ubuntu-system-settings devs were already looking at for detecting
  locale changes without rebooting.


  Original description
  starting an app in vivid (image 135 on arale currently)

  produces a bunch of dbus denials in syslog ... (there is also a
  /dev/tty one but i think this is just because soemthing tries to write
  an error to console ... so transient)

  http://paste.ubuntu.com/10620834/

To manage notifications about this 

[Touch-packages] [Bug 1580857] [NEW] Cannot add more fields to a contact.

[freya zhang]

Public bug reported:

Information:
current build number: 331
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2016-05-12 12:57:13
version version: 331
version ubuntu: 20160512
version device: 20160329-a9bacdb
version custom: 20160505-975-38-9

Precondition:
Contacts are saved in address book.

Steps:
1.Launch Contacts app and  click on a contact
3.Click the "Edit Contact" button.
4.Click on "Add field" and select "Phone","Email" or "Address" option.Check the 
performance.

Actual Result: Nothing happens.
Expected result: Add email, phone, address field should appear.

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

** Description changed:

  Information:
  current build number: 331
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-05-12 12:57:13
  version version: 331
  version ubuntu: 20160512
  version device: 20160329-a9bacdb
  version custom: 20160505-975-38-9
  
  Precondition:
  Contacts are saved in address book.
  
  Steps:
  1.Launch Contacts app and  click on a contact
- 3.Click the "Edit Contact" link
+ 3.Click the "Edit Contact" button.
  4.Click on "Add field" and select "Phone","Email" or "Address" option.Check 
the performance.
  
  Actual Result: Nothing happens.
  Expected result: Add email, phone, address field should appear.

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

Title:
  Cannot add more fields to a contact.

Status in address-book-app package in Ubuntu:
  New

Bug description:
  Information:
  current build number: 331
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-05-12 12:57:13
  version version: 331
  version ubuntu: 20160512
  version device: 20160329-a9bacdb
  version custom: 20160505-975-38-9

  Precondition:
  Contacts are saved in address book.

  Steps:
  1.Launch Contacts app and  click on a contact
  3.Click the "Edit Contact" button.
  4.Click on "Add field" and select "Phone","Email" or "Address" option.Check 
the performance.

  Actual Result: Nothing happens.
  Expected result: Add email, phone, address field should appear.

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

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

[Touch-packages] [Bug 1317195] Re: pkgsel in preseed not working

[julien mary]

I faced the same problem in automated install of ubuntu 14.04, and the
same workaround works.

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

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

Title:
  pkgsel in preseed not working

Status in Cisco Openstack:
  Fix Released
Status in openssh package in Ubuntu:
  New

Bug description:
  Something to sort out after the cobbler module stuff

  d-i pkgsel/include string openssh-server vim vlan lvm2 ntp

  
  This is currently being ignored by the trusty installer, with the result that 
installed machines don't have an ssh server

  workaround for now is adding the above packages to the package install
  line in the late command:

  in-target /usr/bin/apt-get install openssh-server vim vlan lvm2 ntp
  puppet -y || true;\

To manage notifications about this bug go to:
https://bugs.launchpad.net/openstack-cisco/+bug/1317195/+subscriptions

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

[Touch-packages] [Bug 1235680] Re: Tab missing header after changing Page

[Launchpad Bug Tracker]

[Expired for Ubuntu Shorts App because there has been no activity for 60
days.]

** Changed in: ubuntu-rssreader-app
   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/1235680

Title:
  Tab missing header after changing Page

Status in Ubuntu Shorts App:
  Expired
Status in ubuntu-ui-toolkit package in Ubuntu:
  Won't Fix

Bug description:
  Situation: Tab contains two Pages. One of them contains ListView
  inside (flickable), so while swiping up (scrolling content down)
  header can disappear.  If I'll change Tab's "page" property to another
  Page without flickable, header will continue be disappeared without
  any ability to reveal it.

  See attached qml as example. Affects Shorts Core App.

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

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

[Touch-packages] [Bug 1528655] Re: Wily/15.10 - systemd hangs reboot + shutdown for long periods of time

[Launchpad Bug Tracker]

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

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

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

Title:
  Wily/15.10 - systemd hangs reboot + shutdown for long periods of time

Status in systemd package in Ubuntu:
  Expired

Bug description:
  Yet another horrible bug related to systemd which delays shutdowns by
  minutes.

  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1374759
  surfaces this problem + the bug I'm reporting here is a separate
  issue.

  Neither reboot or shutdown -r now work sensibly any more. Both rely on
  systemd, which appears to be the root of most Ubuntu instabilities
  now, reading the many reported systemd bugs.

  Both the reboot + shutdown -r now commands should do what the mean.
  Shutdown + Reboot now...

  Not 150-250 seconds after requested, which appears to be some
  arbitrary systemd timeout.

  Please fix this problem + update this ticket with some workaround to
  get an instant reboot, till fix is available.

  Thanks.

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

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

[Touch-packages] [Bug 1505805] Re: Repeated rebuilding of linux initrd

[Launchpad Bug Tracker]

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

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

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

Title:
  Repeated rebuilding of linux initrd

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have no idea why apt does this, but it does this frequently when
  installing many packages:

  Processing triggers for initramfs-tools (0.103ubuntu15) ...
  update-initramfs: Generating /boot/initrd.img-3.19.0-30-generic
  (Reading database ... 92116 files and directories currently installed.)
  Preparing to unpack .../ntfs-3g_1%3a2014.2.15AR.3-1ubuntu0.2_amd64.deb ...
  Unpacking ntfs-3g (1:2014.2.15AR.3-1ubuntu0.2) over 
(1:2013.1.13AR.1-2ubuntu2) ...
  Preparing to unpack .../uuid-runtime_2.25.2-4ubuntu3_amd64.deb ...
  Unpacking uuid-runtime (2.25.2-4ubuntu3) over (2.20.1-5.1ubuntu20.7) ...
  Processing triggers for initramfs-tools (0.103ubuntu15) ...
  update-initramfs: Generating /boot/initrd.img-3.19.0-30-generic

  The above is from a dist-upgrade during a do-release-upgrade to 15.04
  from 14.10.3.  It's the 8th or 12th time apt has run an update-
  initramfs in a single run.

  Can't this defer to the end of the process?  It takes a long time,
  long enough for dozens of additional packages to install.

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

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

[Touch-packages] [Bug 1576576] Re: Update to 3.20 needs work and coordination

[Robert Ancell]

Blocking babob 3.20 update (bug 1580849)

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

Title:
  Update to 3.20 needs work and coordination

Status in Mozilla Firefox:
  Fix Released
Status in Ubuntu GNOME:
  New
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  The current upstream stable/Debian version is 3.20 but that includes quite 
some changes in the css handling which means we are going to need to update/fix 
the unity themes and make sure you main application look fine before landing.
  The transition needs to be prepared in a staging ppa before being considered, 
help is welcome since it's likely the desktop team is not going to have lot of 
cycles to work on that.

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

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

[Touch-packages] [Bug 1580792] Re: Unity8 on Intel Pineview performs poorly

[Daniel van Vugt]

** Tags added: performance

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

Title:
  Unity8 on Intel Pineview performs poorly

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  (problem forked from bug 1549455)

  Unity8 on Intel Pineview performs very poorly. Frame times appears to
  be up to 900ms, Qt's renderer thread using 100% CPU.

  Running unity8 with MESA_DEBUG=1 EGL_LOG_LEVEL=debug reveals a few MESA 
errors:
  http://paste.ubuntu.com/16344427/

  Quoting @vanvugt "Those Mesa errors "Mesa: User error:" all look like
  OpenGL features that Unity8 is hitting but mir-demos don't. So those
  gl calls are also good candidates for explaining poor performance,
  especially if Mesa is falling back to software rendering for them."

  Since Qt tends to perform just fine on that hardware in X11, something
  isn't right.

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

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

[Touch-packages] [Bug 1573168] Re: [Frieza] Location service fails to start cleanly, entering restart loop

[Joan CiberSheep]

Hi. Similar behaviour here.
I use bq E5 -> updated to OTA 10.1. GPS works perfect.
I have bq m10 that came with OTA9.5 and directly updated to 10.1. GPS seems not 
to work at all (no blinking location icon but I was unable to detect exact 
position).

I wanted to test if GPS was working with OTA 9.5 so I reset the tablet but it 
restarted with OTA10.1. Location icon, this time blinks:
- Switching off GPS in battery is not possible (GPS keeps restarting)
- Switching off GPS from notification panel turns it off but keeps blinking 
(off)

Deactivated all scopes that requires location, installed SensorsStatus.
- SensorsStatus give no GPS data
- SensorsStatus: Found supported backend

Some reboots.
Location icon stopped blinking.

"sudo ubuntu-location-serviced-cli --bus system --test" give no output.
Location icon in notifications panel keeps in on position but grey. It
is not possible to tap or turn off

¿Defective GPS?

I hope those logs helps
http://paste.ubuntu.com/16371046/
http://paste.ubuntu.com/16371257/

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

Title:
  [Frieza] Location service fails to start cleanly, entering restart
  loop

Status in The Avila project:
  New
Status in Canonical System Image:
  Confirmed
Status in location-service package in Ubuntu:
  In Progress

Bug description:
  See http://makeagif.com/i/QlHXU7 for further details.

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

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

[Touch-packages] [Bug 1565236] Re: AltGr not working on external keyboards

[Daniel van Vugt]

** Changed in: mir
Milestone: None => 0.24.0

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

Title:
  AltGr not working on external keyboards

Status in Canonical System Image:
  Confirmed
Status in Mir:
  In Progress
Status in mir package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  New

Bug description:
  Using my keyboard with Spanish layout:

   - PC: Everything works perfect.
   - Ubuntu Touch: I can't write accented characters (dead acute, áéíóú).

  Extra info:

  - Keyboard: https://goo.gl/photos/xZUE8kRsReW1VKPA6 
(http://www.logitech.com/en-hk/product/wireless-touch-keyboard-k400r2)
  - Ubuntu Desktop: 12.04
  - Ubuntu Touch: bq Aquaris E4.5 15.04 (r305)

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

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

[Touch-packages] [Bug 1574777] Re: tablet connected to monitor shows black screen - Idek Iiyama PL2409HD

[Daniel van Vugt]

Yes 0.6Hz sounds bad but I'm hoping we can ignore it for a couple of
reasons:

1. Mir does not use that information to change its behaviour. Only
prints it out. Instead Mir will sync to vblank (60Hz or whatever).

1.1. Android drivers on the other hand might use that information, which
would be bad but not if #2 is proven...

2. If other M10 owners also see "0.6Hz" but can get external displays to
work fine then the 0.6Hz message is benign and is a minor bug that can
be ignored. In that case it's _not_ an indication of the speed Mir is
trying to render at.

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

Title:
  tablet connected to monitor shows black screen - Idek Iiyama PL2409HD

Status in Canonical System Image:
  New
Status in Mir:
  New
Status in mir package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  When connecting my M10 device to my monitor (Idek Iiyama PL2409HD),
  the monitor shows that there is a signal on hdmi, but the screen stays
  black.

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

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

[Touch-packages] [Bug 1537389] Re: The Desktop Never Loads and just stays on a black screen

[Daniel van Vugt]

Incorrect. dinamic is not the reporter of this bug so what dinamic
experiences is not relevant here. This bug is owned by ~ferenos.

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

Title:
  The Desktop Never Loads and just stays on a black screen

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

Bug description:
  The cursor is also not shown, neither is the Unity 8 Lock Screen or
  Indicators. Ubuntu 16.04 Daily

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8-desktop-session-mir 1.0.12+15.10.20150609-0ubuntu1
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.3-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jan 23 18:44:45 2016
  InstallationDate: Installed on 2016-01-22 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160122.2)
  PackageArchitecture: all
  SourcePackage: unity8-desktop-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1549455] Re: Unity8-dash on Intel Pineview graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]

[Daniel van Vugt]

Please keep the bug title in a form that's meaningful and relevant to
users. Not a description of the source code.

** Summary changed:

- Qt clients on Intel Pineview graphics fail to create egl context with Mir
+ Unity8-dash on Intel Pineview graphics crashes and restarts continuously 
[qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]

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

Title:
  Unity8-dash on Intel Pineview graphics crashes and restarts
  continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay,
  EglContext) == EGL_TRUE"]

Status in Mir:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in qtdeclarative package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Qt clients are failing to create an egl context when running on Intel
  Pineview systems under Mir.

  eglCreateContext fails with a EGL_BAD_MATCH error code.

  When it fails, Qt tries to delete & recreate the context, which then
  crashes the client (bug 1580118)

  
  === Original bug description ===
  This bug Makes the pc UNUSABLE
  when I try to launch Unity 8 and Mir, after writing the password on the login 
(in the image attached) the bar to enter the password disappears and my 
computer screen stays stuck without them let me do anything. the connection 
begins to separate and reattach alone and I can only move the cursor. it makes 
the computer unusable and I am forced to restart forced to then enter into 
Unity 7. represented in the screenshot is the lock status after entering the 
password.
  Version: unity8.12+16.04.201604.01.1
  Version of Mir : 0.21

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

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

[Touch-packages] [Bug 1434986] Re: Not working network connection after boot

[Tristan Cormier]

I too am affected by this bug, on Ubuntu 16.04 LTS. The bug has been
present for me, in a way or another, since 15.04.

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

Title:
  Not working network connection after boot

Status in NetworkManager:
  Expired
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Directly after boot the network connections are not working. I am
  connected and have an IP address, but I cannot establish a connection
  with any Internet server.

  I have the impression it is related to thee DNS lookup, which waits
  forever for a result.

  Cycling the connection (disconnect->reconnect) seems to fix the
  problem for some time.

  I am reporting this against network-manager, but I am not sure if it is 
directly in network manager or if it is systemd related.
  With 14.10 everything worked perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Mar 22 12:38:26 2015
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-01-30 (50 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static  metric 1024 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.26 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.29
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago)
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-02-16T00:14:50.662693
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION CON-UUID  CON-PATH   

   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Kabelnetzwerkverbindung 1  4a581685-6002-4401-a993-49aa649667eb  
/org/freedesktop/NetworkManager/ActiveConnection/4 
   wlan0   wifi  connected  /org/freedesktop/NetworkManager/Devices/1  
4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1387908] Re: [udev] FIDO u2f security keys should be supported out of the box

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 229-4ubuntu5

---
systemd (229-4ubuntu5) xenial-proposed; urgency=medium

  * debian/udev.postinst: Don't fail if /var/log/udev is a directory.
(LP: #1574004)
  * 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)
  * debian/extra/init-functions.d/40-systemd: Invoke status command with
--no-pager, to avoid blocking scripts that call an init.d script with
"status" with an unexpected pager process. (Closes: #765175, LP: #1576409)
  * Add debian/extra/rules/70-debian-uaccess.rules: Make FIDO U2F dongles
accessible to the user session. This avoids having to install libu2f-host0
(which isn't discoverable at all) to make those devices work.
(LP: #1387908)
  * On shutdown, unmount /tmp before disabling swap. (Closes: #788303)

 -- Martin Pitt   Mon, 02 May 2016 15:04:42
-0500

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

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

Title:
  [udev] FIDO u2f security keys should be supported out of the box

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Trusty:
  Confirmed
Status in systemd source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * Users plugin U2F key and it does not work in Google Chrome

  [Test Case]

   * Have stock ubuntu install, without custom U2F rules or libu2f-host0
  installed

   * Use U2F factor authentication website e.g. google apps, github,
  yubico, etc.

   * Pluging in the key, should just work and complete U2F
  authentication instead of timing out

  [Regression Potential]

   * Should not conflict with libu2f-host0 udev rules which is where
  these are currently shipped

  FIDO u2f is an emerging standard for public-private cryptography based
  2nd factor authentication, which improves on OTP by mitigating
  phishing, man-in-the-middle attacks and reply attacks.

  Google Chrome supports u2f devices which are now widely available from
  Yubico (new premium neo Yubikeys and Security keys).

  However, udev rules are required to setup permissions to allow the
  web-browsers which are running as regular users to access the devices
  in question.

  E.g.:

  KERNEL=="hidraw*", SUBSYSTEM=="hidraw", MODE="0664", GROUP="plugdev",
  ATTRS{idVendor}=="1050", ATTRS{idProduct}=="0113|0114|0115|0116|0120"

  Something like that should be enabled by default, however probably not
  encode on the vendor/productid as other vendors will also make u2f
  devices.

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

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

[Touch-packages] [Bug 1387908] Update Released

[Chris J Arges]

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

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

Title:
  [udev] FIDO u2f security keys should be supported out of the box

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Trusty:
  Confirmed
Status in systemd source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * Users plugin U2F key and it does not work in Google Chrome

  [Test Case]

   * Have stock ubuntu install, without custom U2F rules or libu2f-host0
  installed

   * Use U2F factor authentication website e.g. google apps, github,
  yubico, etc.

   * Pluging in the key, should just work and complete U2F
  authentication instead of timing out

  [Regression Potential]

   * Should not conflict with libu2f-host0 udev rules which is where
  these are currently shipped

  FIDO u2f is an emerging standard for public-private cryptography based
  2nd factor authentication, which improves on OTP by mitigating
  phishing, man-in-the-middle attacks and reply attacks.

  Google Chrome supports u2f devices which are now widely available from
  Yubico (new premium neo Yubikeys and Security keys).

  However, udev rules are required to setup permissions to allow the
  web-browsers which are running as regular users to access the devices
  in question.

  E.g.:

  KERNEL=="hidraw*", SUBSYSTEM=="hidraw", MODE="0664", GROUP="plugdev",
  ATTRS{idVendor}=="1050", ATTRS{idProduct}=="0113|0114|0115|0116|0120"

  Something like that should be enabled by default, however probably not
  encode on the vendor/productid as other vendors will also make u2f
  devices.

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

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

[Touch-packages] [Bug 1574004] Update Released

[Chris J Arges]

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

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

Title:
  package udev 229-4ubuntu4 failed to install/upgrade: /var/log/udev is
  a directory

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

Bug description:
  upgrade to 16.04 failed

  SRU INFORMATION
  ---
  Fix: 
http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial=d133b04

  Test case: Install 15.10, remove the /var/log/udev file, and make it a
  directory (sudo mkdir -p /var/log/udev). Upgrade to 16.04 (at least
  udev). This will fail on this error with the xenial version, but
  should succeed with this fix.

  Regression potential: practically zero. This only ignores errors on
  the rm of the old log file.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-36.41-generic 4.2.8-ckt8
  Uname: Linux 4.2.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Apr 23 14:34:45 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-07-16 (281 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 4174P5G
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-36-generic 
root=UUID=6d33134c-01af-4ee9-ad9e-afe117f0cff4 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: systemd
  Title: package udev 229-4ubuntu4 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (0 days ago)
  dmi.bios.date: 04/11/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8CET57WW (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4174P5G
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8CET57WW(1.37):bd04/11/2013:svnLENOVO:pn4174P5G:pvrThinkPadT420s:rvnLENOVO:rn4174P5G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4174P5G
  dmi.product.version: ThinkPad T420s
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1574483] Update Released

[Chris J Arges]

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

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

Title:
  assigns MAC-based names for devices with locally administered MAC
  address

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Yakkety:
  Fix Released
Status in systemd package in Debian:
  Fix Released

Bug description:
  Originally from https://bugs.debian.org/812575: Our current
  /lib/systemd/network/90-mac-for-usb.link assigns MAC-based names to
  all USB devices. However, this is wrong and pointless for locally
  administered MAC addresses (with the second bit set to '1', see
  https://en.wikipedia.org/wiki/MAC_address#Address_details).

  The old 75-persistent-net generator had this rule:

     ENV{MATCHADDR}=="?[2367abef]:*",ENV{MATCHADDR}=""

  which ignored these devices. We need to adjust 90-mac-for-usb.link to
  do the same, and only apply to universally administered MAC addresses
  (at least until https://lists.ubuntu.com/archives/ubuntu-
  devel/2016-April/039302.html gets concluded).

  We should simply fall through the default policy of assigning location
  based names. The kernel assigned ones have no meaning whatsoever, so
  this at least provides name stability for use cases where you can rely
  on plugging the device into the same port.

  SRU INFORMATION:
  
  Fix: 
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=ec7e332

  Test case:
   - Plug in an Android phone and enable USB tethering, or a different USB 
device which uses locally administered MAC addresses, i. e. they change after 
every reboot of the device. The first byte of the MAC address must have the 
second bit set, i. e. the hex number matches ?[2367abef].
   - Check "ip a". With current xenial version the interface name is MAC based, 
like "enx12345678", and it changes after rebooting the device.
   - With this fix, the name is location based, like "enp0s1u2", and it remains 
stable as long as you use the same USB port.

  Regression potential: This only affects naming USB network devices. It
  should be tested that devices with universally administered MACs (i.
  e. stable, second bit is zero) keep MAC based names to avoid changing
  existing stable names. For devices with locally administered MACs (i.
  e. random ones) the name currently changes all the time anyway, so any
  /etc/network/interfaces or firewall script that refers to them is
  already broken and there cannot be further regressions there. Also,
  the updated policy is only applied after a computer reboot or
  replugging the device, the name does not change while the device is
  already plugged in.

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

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

[Touch-packages] [Bug 1574483] Re: assigns MAC-based names for devices with locally administered MAC address

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 229-4ubuntu5

---
systemd (229-4ubuntu5) xenial-proposed; urgency=medium

  * debian/udev.postinst: Don't fail if /var/log/udev is a directory.
(LP: #1574004)
  * 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)
  * debian/extra/init-functions.d/40-systemd: Invoke status command with
--no-pager, to avoid blocking scripts that call an init.d script with
"status" with an unexpected pager process. (Closes: #765175, LP: #1576409)
  * Add debian/extra/rules/70-debian-uaccess.rules: Make FIDO U2F dongles
accessible to the user session. This avoids having to install libu2f-host0
(which isn't discoverable at all) to make those devices work.
(LP: #1387908)
  * On shutdown, unmount /tmp before disabling swap. (Closes: #788303)

 -- Martin Pitt   Mon, 02 May 2016 15:04:42
-0500

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

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

Title:
  assigns MAC-based names for devices with locally administered MAC
  address

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Yakkety:
  Fix Released
Status in systemd package in Debian:
  Fix Released

Bug description:
  Originally from https://bugs.debian.org/812575: Our current
  /lib/systemd/network/90-mac-for-usb.link assigns MAC-based names to
  all USB devices. However, this is wrong and pointless for locally
  administered MAC addresses (with the second bit set to '1', see
  https://en.wikipedia.org/wiki/MAC_address#Address_details).

  The old 75-persistent-net generator had this rule:

     ENV{MATCHADDR}=="?[2367abef]:*",ENV{MATCHADDR}=""

  which ignored these devices. We need to adjust 90-mac-for-usb.link to
  do the same, and only apply to universally administered MAC addresses
  (at least until https://lists.ubuntu.com/archives/ubuntu-
  devel/2016-April/039302.html gets concluded).

  We should simply fall through the default policy of assigning location
  based names. The kernel assigned ones have no meaning whatsoever, so
  this at least provides name stability for use cases where you can rely
  on plugging the device into the same port.

  SRU INFORMATION:
  
  Fix: 
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=ec7e332

  Test case:
   - Plug in an Android phone and enable USB tethering, or a different USB 
device which uses locally administered MAC addresses, i. e. they change after 
every reboot of the device. The first byte of the MAC address must have the 
second bit set, i. e. the hex number matches ?[2367abef].
   - Check "ip a". With current xenial version the interface name is MAC based, 
like "enx12345678", and it changes after rebooting the device.
   - With this fix, the name is location based, like "enp0s1u2", and it remains 
stable as long as you use the same USB port.

  Regression potential: This only affects naming USB network devices. It
  should be tested that devices with universally administered MACs (i.
  e. stable, second bit is zero) keep MAC based names to avoid changing
  existing stable names. For devices with locally administered MACs (i.
  e. random ones) the name currently changes all the time anyway, so any
  /etc/network/interfaces or firewall script that refers to them is
  already broken and there cannot be further regressions there. Also,
  the updated policy is only applied after a computer reboot or
  replugging the device, the name does not change while the device is
  already plugged in.

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

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

[Touch-packages] [Bug 1576409] Re: calling init.d script with "status" invokes pager

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 229-4ubuntu5

---
systemd (229-4ubuntu5) xenial-proposed; urgency=medium

  * debian/udev.postinst: Don't fail if /var/log/udev is a directory.
(LP: #1574004)
  * 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)
  * debian/extra/init-functions.d/40-systemd: Invoke status command with
--no-pager, to avoid blocking scripts that call an init.d script with
"status" with an unexpected pager process. (Closes: #765175, LP: #1576409)
  * Add debian/extra/rules/70-debian-uaccess.rules: Make FIDO U2F dongles
accessible to the user session. This avoids having to install libu2f-host0
(which isn't discoverable at all) to make those devices work.
(LP: #1387908)
  * On shutdown, unmount /tmp before disabling swap. (Closes: #788303)

 -- Martin Pitt   Mon, 02 May 2016 15:04:42
-0500

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

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

Title:
  calling init.d script with "status" invokes pager

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

Bug description:
  Running e. g. "/etc/init.d/networking status" runs a pager (less by
  default). This is unexpected from an init.d script, and potentially
  breaks scripts or CLI programs that do this operation, as this then
  hangs eternally in the interactive pager process until the user quits
  it. This reportedly happens with "vagrant up" (see original Debian bug
  https://bugs.debian.org/765175).

  SRU INFORMATION:
  Test case:
   Run "/etc/init.d/networking status". In current xenial this invokes less 
which you need to quit. With the proposed fix this should return to the shell 
immediately without a pager.

  Regression potential:  very low. The main visible change is the
  interactive usage of "/etc/init.d/foo status", but nothing in Ubuntu
  (nor hopefully anywhere else) *relies* on the fact that systemctl
  invokes a pager, particularly as this is not always done (it depends
  on whether stdout is a terminal and how many lines are written).

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

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

[Touch-packages] [Bug 1574004] Re: package udev 229-4ubuntu4 failed to install/upgrade: /var/log/udev is a directory

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 229-4ubuntu5

---
systemd (229-4ubuntu5) xenial-proposed; urgency=medium

  * debian/udev.postinst: Don't fail if /var/log/udev is a directory.
(LP: #1574004)
  * 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)
  * debian/extra/init-functions.d/40-systemd: Invoke status command with
--no-pager, to avoid blocking scripts that call an init.d script with
"status" with an unexpected pager process. (Closes: #765175, LP: #1576409)
  * Add debian/extra/rules/70-debian-uaccess.rules: Make FIDO U2F dongles
accessible to the user session. This avoids having to install libu2f-host0
(which isn't discoverable at all) to make those devices work.
(LP: #1387908)
  * On shutdown, unmount /tmp before disabling swap. (Closes: #788303)

 -- Martin Pitt   Mon, 02 May 2016 15:04:42
-0500

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

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

Title:
  package udev 229-4ubuntu4 failed to install/upgrade: /var/log/udev is
  a directory

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

Bug description:
  upgrade to 16.04 failed

  SRU INFORMATION
  ---
  Fix: 
http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial=d133b04

  Test case: Install 15.10, remove the /var/log/udev file, and make it a
  directory (sudo mkdir -p /var/log/udev). Upgrade to 16.04 (at least
  udev). This will fail on this error with the xenial version, but
  should succeed with this fix.

  Regression potential: practically zero. This only ignores errors on
  the rm of the old log file.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-36.41-generic 4.2.8-ckt8
  Uname: Linux 4.2.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Apr 23 14:34:45 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-07-16 (281 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 4174P5G
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-36-generic 
root=UUID=6d33134c-01af-4ee9-ad9e-afe117f0cff4 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: systemd
  Title: package udev 229-4ubuntu4 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (0 days ago)
  dmi.bios.date: 04/11/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8CET57WW (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4174P5G
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8CET57WW(1.37):bd04/11/2013:svnLENOVO:pn4174P5G:pvrThinkPadT420s:rvnLENOVO:rn4174P5G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4174P5G
  dmi.product.version: ThinkPad T420s
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1576409] Update Released

[Chris J Arges]

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

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

Title:
  calling init.d script with "status" invokes pager

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

Bug description:
  Running e. g. "/etc/init.d/networking status" runs a pager (less by
  default). This is unexpected from an init.d script, and potentially
  breaks scripts or CLI programs that do this operation, as this then
  hangs eternally in the interactive pager process until the user quits
  it. This reportedly happens with "vagrant up" (see original Debian bug
  https://bugs.debian.org/765175).

  SRU INFORMATION:
  Test case:
   Run "/etc/init.d/networking status". In current xenial this invokes less 
which you need to quit. With the proposed fix this should return to the shell 
immediately without a pager.

  Regression potential:  very low. The main visible change is the
  interactive usage of "/etc/init.d/foo status", but nothing in Ubuntu
  (nor hopefully anywhere else) *relies* on the fact that systemctl
  invokes a pager, particularly as this is not always done (it depends
  on whether stdout is a terminal and how many lines are written).

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

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

[Touch-packages] [Bug 1519499] Re: Shutdown failure: Assertion 'sd_id128_randomize() >= 0' failed at ../src/core/dbus.c:657, function bus_on_connection(). Aborting.

[Hans Deragon]

Shouldn't this bug be assigned to some LXC/LXD task?  After all, a
normal installation of the distributions on a computer works well.
16.04 shutsdown properly on a laptop, for example; systemd simply does
not hang.  Thus this bug is somewhat related to LXC/LXD.  Maybe the bare
minimum images are at fault?

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

Title:
  Shutdown failure: Assertion 'sd_id128_randomize() >= 0' failed at
  ../src/core/dbus.c:657, function bus_on_connection(). Aborting.

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  This is a follow-up on this issue here:
  https://github.com/lxc/lxd/issues/1336 I cannot stop a LXD container
  gently and as it seems the issue lies within ubuntu/systemd which does
  not handle SIGPWR correctly.

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

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

[Touch-packages] [Bug 1579978] Re: upgrade to 1:7.2p2-4ubuntu1 fails on ubuntu server

[Tomas Cassidy]

Hi Robie,

I tried purging and reinstalling openssh-server, but that failed again
with the same error.

I then rebooted the machine and was able to then successfully run apt-
get -f install to fix the package installation.  Subsequently re-
installing the package worked without a problem.

Perhaps there was a temporary file causing a problem somewhere, which
was automatically cleaned out on reboot? Something leftover from the
upgrade to xenial?

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

Title:
  upgrade to 1:7.2p2-4ubuntu1 fails on ubuntu server

Status in openssh package in Ubuntu:
  New

Bug description:
  This package upgrade failure has occurred on multiple machines, with
  the same error on each machine.  All affected machines are running
  Upstart (upstart-sysv) as /sbin/init.  The package installed/updated
  successfully on a machine running Systemd (systemd-sysv) as
  /sbin/init.

  $ sudo apt full-upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following packages were automatically installed and are no longer 
required:
    linux-image-4.2.0-35-generic linux-image-extra-4.2.0-35-generic
  Use 'sudo apt autoremove' to remove them.
  0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n]
  Setting up openssh-server (1:7.2p2-4ubuntu1) ...
  start: Job failed to start
  invoke-rc.d: initscript ssh, action "restart" failed.
  dpkg: error processing package openssh-server (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   openssh-server
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Tue May 10 11:51:58 2016
  InstallationDate: Installed on 2015-09-04 (249 days ago)
  InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: openssh
  UpgradeStatus: Upgraded to xenial on 2016-05-04 (5 days ago)

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

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

[Touch-packages] [Bug 1576784] Re: MatchIsTouchscreen also matches touchpads in 16.04

[machrider]

I'm seeing the same problem with my Dell touchpad since upgrading to
16.04. /proc/bus/input/devices shows my touchpad as:

I: Bus=0011 Vendor=0002 Product=0007 Version=01b1
N: Name="SynPS/2 Synaptics TouchPad"
P: Phys=isa0060/serio1/input0
S: Sysfs=/devices/platform/i8042/serio1/input/input5
U: Uniq=
H: Handlers=mouse0 event6 
B: PROP=5
B: EV=b
B: KEY=e520 1 0 0 0 0
B: ABS=66080001103

The touchscreen is:

I: Bus=0003 Vendor=06cb Product=1ac3 Version=0111
N: Name="SYNAPTICS Synaptics Large Touch Screen"
P: Phys=usb-:00:14.0-6/input0
S: 
Sysfs=/devices/pci:00/:00:14.0/usb3/3-6/3-6:1.0/0003:06CB:1AC3.0001/input/input14
U: Uniq=
H: Handlers=mouse1 event13 
B: PROP=2
B: EV=b
B: KEY=400 0 0 0 0 0
B: ABS=2608003

Previously MatchIsTouchscreen only matched my touchscreen, but now it's
matching the touchpad, too.

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

Title:
  MatchIsTouchscreen also matches touchpads in 16.04

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Previously in 15.10 I had the following rule in 
/usr/share/X11/xorg.conf.d/99-no-touchscreen.conf:
  Section "InputClass"
  Identifier "Touchscreen disable"
  MatchIsTouchscreen "on"

  Option "Ignore" "on"
  EndSection

  This worked in disabling the touchpad on my lenovo T440s

  After the upgrade to 16.04 I noticed that my touchpad would not work. And I 
found the following lines in the log:
  [  3107.956] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad 
(/dev/input/event6)
  [  3107.956] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass 
"Touchscreen disable"
  [  3107.956] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad 
(/dev/input/mouse0)
  [  3107.956] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass 
"Touchscreen disable"

  So I had to disable the rule in order to be able to use the touchpad,
  and now  I can't disable the touchscreen.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.38-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Apr 29 09:39:23 2016
  InstallationDate: Installed on 2015-03-18 (407 days ago)
  InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (1 days ago)

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

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

[Touch-packages] [Bug 1576784] Re: MatchIsTouchscreen also matches touchpads in 16.04

[Launchpad Bug Tracker]

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

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

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

Title:
  MatchIsTouchscreen also matches touchpads in 16.04

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Previously in 15.10 I had the following rule in 
/usr/share/X11/xorg.conf.d/99-no-touchscreen.conf:
  Section "InputClass"
  Identifier "Touchscreen disable"
  MatchIsTouchscreen "on"

  Option "Ignore" "on"
  EndSection

  This worked in disabling the touchpad on my lenovo T440s

  After the upgrade to 16.04 I noticed that my touchpad would not work. And I 
found the following lines in the log:
  [  3107.956] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad 
(/dev/input/event6)
  [  3107.956] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass 
"Touchscreen disable"
  [  3107.956] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad 
(/dev/input/mouse0)
  [  3107.956] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass 
"Touchscreen disable"

  So I had to disable the rule in order to be able to use the touchpad,
  and now  I can't disable the touchscreen.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.38-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Apr 29 09:39:23 2016
  InstallationDate: Installed on 2015-03-18 (407 days ago)
  InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (1 days ago)

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

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

[Touch-packages] [Bug 1580814] [NEW] /usr/sbin/lightdm:11:munmap:_dl_unmap_segments:_dl_unmap:_dl_close_worker:_dl_close

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding lightdm.  This problem was most recently seen with version
1.18.1-0ubuntu1, the problem page at
https://errors.ubuntu.com/problem/30ec8995938a13961d11eee682a4ae32c1dc16ca
contains more details.

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


** Tags: vivid wily xenial

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

Title:
  
/usr/sbin/lightdm:11:munmap:_dl_unmap_segments:_dl_unmap:_dl_close_worker:_dl_close

Status in lightdm package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding lightdm.  This problem was most recently seen with version
  1.18.1-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/30ec8995938a13961d11eee682a4ae32c1dc16ca
  contains more details.

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

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

[Touch-packages] [Bug 1580810] [NEW] /lib/systemd/systemd-udevd:6:recvmsg:udev_monitor_receive_device:on_uevent:on_inotify:source_dispatch

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding systemd.  This problem was most recently seen with version
229-4ubuntu4, the problem page at
https://errors.ubuntu.com/problem/aab87e97600baa6c2fb2a7e38f257fb24d5e4b5d
contains more details.

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


** Tags: wily xenial

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

Title:
  /lib/systemd/systemd-
  
udevd:6:recvmsg:udev_monitor_receive_device:on_uevent:on_inotify:source_dispatch

Status in systemd package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding systemd.  This problem was most recently seen with version
  229-4ubuntu4, the problem page at
  https://errors.ubuntu.com/problem/aab87e97600baa6c2fb2a7e38f257fb24d5e4b5d
  contains more details.

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

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

[Touch-packages] [Bug 1580577] Re: python2.7 crashes with SegFault when running Zope

[Alexander Loechel]

Hi Patrick,

I think we need to verify that this is in Ubuntu itself, while Ubuntu
just uses the upstream Package from Debian
(https://packages.debian.org/search?keywords=python2.7 /
https://packages.debian.org/stretch/python2.7 or
https://packages.debian.org/sid/python2.7) if they are also affected. If
so, we really need to go upstream for a bug Report on Debian Python 2.7

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

Title:
  python2.7 crashes with SegFault when running Zope

Status in python2.7 package in Ubuntu:
  Confirmed

Bug description:
  Source package / Package:

  python2.7_2.7.11-7ubuntu1

  System:

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  
  This is a bug report originating from the findings documented in

  https://github.com/zopefoundation/Zope/issues/56

  
  The expected behaviour is this:
  - Upon installing Zope2 in a virtualenv a default instance should work with 
no issues.

  What happens instead:
  - The freshly installed Zope instance causes Python to SegFault after only a 
few requests.

  But Python should never SegFault.

  
  The following program produces the error:

  
  #!/bin/bash
  set -e

  # Call this testing script with an argument "setup" for the first time
  # to build the testing case
  #
  # After that, the script only performs the test as described below.
  #
  # Requirements: apt-get install virtualenv python2.7-dbg
  #
  # This script needs internet access when running.

  # The python version to test:
  python=/usr/bin/python2.7-dbg

  # This part builds the testing environment

  if [ "$1" == "setup" ] ; then
  # Virtual environment with the chosen python 
  virtualenv --python ${python} --no-site-packages zope-virtualenv
  cd zope-virtualenv
  # Basic Zope installation
  ./bin/easy_install -i http://download.zope.org/Zope2/index/2.13.24 Zope2
  # Simplest possible Zope instance
  ./bin/mkzopeinstance --dir instance --user admin:admin
  cd ..
  fi

  # THE TEST

  # Run Zope instance in the background
  zope-virtualenv/instance/bin/runzope &

  # Give Zope some time to start up
  sleep 3

  # Call a few management URLs, nothing too fancy...
  urls="
  http://admin:admin@localhost:8080/Control_Panel/manage_main
  http://admin:admin@localhost:8080/Control_Panel/Database/main/manage_main
  http://admin:admin@localhost:8080/Control_Panel/Database/manage_main
  http://admin:admin@localhost:8080/Control_Panel/Database/main/manage_activity
  http://admin:admin@localhost:8080/manage
  http://admin:admin@localhost:8080/acl_users/manage_main
  http://admin:admin@localhost:8080/acl_users/manage_access
  "

  while true ; do
  for url in ${urls} ; do 
echo ${url}
  curl -s $url -o /dev/null
  done
  done

  # This test fails after about 10 requests with
  # Fatal Python error: ../Objects/descrobject.c:10 object at 0x??? has 
negative ref count -1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1580577/+subscriptions

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

[Touch-packages] [Bug 1545272] Re: reboot fails with "Failed to start reboot.target: Transaction is destructive."

[Launchpad Bug Tracker]

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

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

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

Title:
  reboot fails with "Failed to start reboot.target: Transaction is
  destructive."

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  `sudo reboot` fails with

  Failed to start reboot.target: Transaction is destructive.

  Broadcast message from richter@richter-lenovo-IdeaPad-U410 on
  pts/1 (Sa 2016-02-13 13:36:30 CET):

  The system is going down for reboot NOW!

  which seems to be caused by an incomplete suspend as stated in
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1441253 which
  isn't a duplicate because the reason seem to be a btrfs issue there
  which I don't suffer from.

  I'd suggest to let the suspend time out, provide the user with the
  information that a suspend is pending and might timeout or succeed (or
  something similar, more useful than "Failed to start reboot.target:
  Transaction is destructive.") so that reboot is possible again after
  some time.

  The issue should be fixed in the kernel as well, it makes sense as
  well to handle this situation in `systemd` because assuming that the
  kernel is always stable is naive and adding such a timeout improves
  stability and better feedback usage.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: systemd 225-1ubuntu9.1
  ProcVersionSignature: Ubuntu 4.2.0-29.34-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-29-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 13 13:36:10 2016
  InstallationDate: Installed on 2013-10-17 (848 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: LENOVO IdeaPad U410
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-29-generic 
root=UUID=8c488557-8173-43a2-a3a8-df0a24695c08 ro 
rootflags=subvol=ubuntu-main-root quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to wily on 2015-11-19 (85 days ago)
  dmi.bios.date: 09/25/2012
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 65CN90WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo
  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 U410
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr65CN90WW:bd09/25/2012:svnLENOVO:pnIdeaPadU410:pvrLenovoU410:rvnLENOVO:rnLenovo:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoU410:
  dmi.product.name: IdeaPad U410
  dmi.product.version: Lenovo U410
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1580806] [NEW] [Compaq 610, IDT 92HD75B2X5, Speaker, Internal] No sound at all

[nevbear666]

Public bug reported:

soundcard is recognized.
no sound playback through internal speakers.
external usb headphones work.
all mixers are at 100%.
soundcard is being recognized and viewable through lspci and cat'ing through 
proc.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
Uname: Linux 4.6.0-997-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  nevermind   2986 F pulseaudio
CurrentDesktop: Unity
Date: Thu May 12 00:58:48 2016
InstallationDate: Installed on 2015-05-19 (358 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
Symptom_Card: Internes Audio - HDA Intel
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  nevermind   2986 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [Compaq 610, IDT 92HD75B2X5, Speaker, Internal] No sound at all
UpgradeStatus: Upgraded to xenial on 2016-05-07 (4 days ago)
dmi.bios.date: 12/01/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PVU Ver. F.20
dmi.board.name: 308A
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 26.08
dmi.chassis.asset.tag: CNU9480YSY
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PVUVer.F.20:bd12/01/2011:svnHewlett-Packard:pnCompaq610:pvrF.20:rvnHewlett-Packard:rn308A:rvrKBCVersion26.08:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: Compaq 610
dmi.product.version: F.20
dmi.sys.vendor: Hewlett-Packard
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-05-12T00:39:28.644247

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


** Tags: amd64 apport-bug xenial

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

Title:
  [Compaq 610, IDT 92HD75B2X5, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  soundcard is recognized.
  no sound playback through internal speakers.
  external usb headphones work.
  all mixers are at 100%.
  soundcard is being recognized and viewable through lspci and cat'ing through 
proc.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.6.0-997-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nevermind   2986 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 12 00:58:48 2016
  InstallationDate: Installed on 2015-05-19 (358 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Internes Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nevermind   2986 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Compaq 610, IDT 92HD75B2X5, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to xenial on 2016-05-07 (4 days ago)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PVU Ver. F.20
  dmi.board.name: 308A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 26.08
  dmi.chassis.asset.tag: CNU9480YSY
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PVUVer.F.20:bd12/01/2011:svnHewlett-Packard:pnCompaq610:pvrF.20:rvnHewlett-Packard:rn308A:rvrKBCVersion26.08:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: Compaq 610
  dmi.product.version: F.20
  dmi.sys.vendor: Hewlett-Packard
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-05-12T00:39:28.644247

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

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

[Touch-packages] [Bug 1577768] Re: 16.04 some dvd do not mount automatically (but do in 14.04)

[Erick Brunzell]

** Also affects: util-linux (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  16.04 some dvd do not mount automatically (but do in 14.04)

Status in gvfs package in Ubuntu:
  Confirmed
Status in nautilus package in Ubuntu:
  Confirmed
Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  here is a dvd. And ubuntu 16.04.

  When I insert that dvd, it does not show anywhere, neither in launcher
  nor in nautilus.

  But I'm able to read that dvd using vlc through menu media / open a
  disc.

  I can manually mount that dvd with

  sudo mount -t iso9660 -o ro /dev/sr0 ~/Bureau/dvd/

  Once mounted there's a dvd icon in launcher and it appears also in
  nautilus left panel.

  That same dvd automatically mounts when running ubuntu 14.04 on the
  same computer.

  I have also tested other dvd's on ubuntu 16.04 and *most* of them show
  / mount as expected.

  But *all* of them automatically show / mount in ubuntu 14.04.

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

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

[Touch-packages] [Bug 1580792] Re: Unity8 on Intel Pineview performs poorly

[Gerry Boland]

I've reported https://bugs.launchpad.net/mir/+bug/1580277 to raise the
GL/GLES combination problem with the Mir team

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

Title:
  Unity8 on Intel Pineview performs poorly

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  (problem forked from bug 1549455)

  Unity8 on Intel Pineview performs very poorly. Frame times appears to
  be up to 900ms, Qt's renderer thread using 100% CPU.

  Running unity8 with MESA_DEBUG=1 EGL_LOG_LEVEL=debug reveals a few MESA 
errors:
  http://paste.ubuntu.com/16344427/

  Quoting @vanvugt "Those Mesa errors "Mesa: User error:" all look like
  OpenGL features that Unity8 is hitting but mir-demos don't. So those
  gl calls are also good candidates for explaining poor performance,
  especially if Mesa is falling back to software rendering for them."

  Since Qt tends to perform just fine on that hardware in X11, something
  isn't right.

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

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

[Touch-packages] [Bug 1549455] Re: Qt clients on Intel Pineview graphics fail to create egl context with Mir

[Gerry Boland]

http://paste.ubuntu.com/16357238/ the output Qt gave me for the failing
eglCreateContext

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

Title:
  Qt clients on Intel Pineview graphics fail to create egl context with
  Mir

Status in Mir:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in qtdeclarative package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Qt clients are failing to create an egl context when running on Intel
  Pineview systems under Mir.

  eglCreateContext fails with a EGL_BAD_MATCH error code.

  When it fails, Qt tries to delete & recreate the context, which then
  crashes the client (bug 1580118)

  
  === Original bug description ===
  This bug Makes the pc UNUSABLE
  when I try to launch Unity 8 and Mir, after writing the password on the login 
(in the image attached) the bar to enter the password disappears and my 
computer screen stays stuck without them let me do anything. the connection 
begins to separate and reattach alone and I can only move the cursor. it makes 
the computer unusable and I am forced to restart forced to then enter into 
Unity 7. represented in the screenshot is the lock status after entering the 
password.
  Version: unity8.12+16.04.201604.01.1
  Version of Mir : 0.21

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

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

[Touch-packages] [Bug 1580792] Re: Unity8 on Intel Pineview performs poorly

[Gerry Boland]

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

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

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

Title:
  Unity8 on Intel Pineview performs poorly

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  (problem forked from bug 1549455)

  Unity8 on Intel Pineview performs very poorly. Frame times appears to
  be up to 900ms, Qt's renderer thread using 100% CPU.

  Running unity8 with MESA_DEBUG=1 EGL_LOG_LEVEL=debug reveals a few MESA 
errors:
  http://paste.ubuntu.com/16344427/

  Quoting @vanvugt "Those Mesa errors "Mesa: User error:" all look like
  OpenGL features that Unity8 is hitting but mir-demos don't. So those
  gl calls are also good candidates for explaining poor performance,
  especially if Mesa is falling back to software rendering for them."

  Since Qt tends to perform just fine on that hardware in X11, something
  isn't right.

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

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

[Touch-packages] [Bug 1569357] Re: Ubuntu 16.04 - Unity desktop session broken when using non-LightDM as X Display Manager

[Kanwar Singh]

sddm to unity broken. This temporarily gets me working:

right click and open shell
run

setsid unity

gets me back working in unity.

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

Title:
  Ubuntu 16.04 - Unity desktop session broken when using non-LightDM as
  X Display Manager

Status in gnome-session package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  New
Status in lxdm package in Ubuntu:
  New
Status in sddm package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  New

Bug description:
  As title, you'll only see your desktop file icons, no launcher and
  status bar are displayed.

  You can only reproduce this issue if you choose to use SDDM as the default X 
display manager(e.g. LightDM has no this issue)  
  UPDATE: Not only SDDM!  Currently most non-LightDM I tested has the same 
issue.

  * SDDM: reproduced
  * GDM3: not even launch-able on my system so can't verify
  * LXDM: reproduced

  This issue doesn't exist in Ubuntu 15.10, only in 16.04

  ## Workaround ##
  * Switch to LightDM

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: sddm 0.13.0-1ubuntu5
  Uname: Linux 4.5.0-buo-ren-vanilla-intel-ivybridge-optimized x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr 12 20:17:23 2016
  InstallationDate: Installed on 2016-01-07 (95 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: sddm
  UpgradeStatus: Upgraded to xenial on 2016-04-07 (4 days ago)

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

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

[Touch-packages] [Bug 1580577] Re: python2.7 crashes with SegFault when running Zope

[Patrick Gerken]

Hi Matthias, I am not sure I understand what you mean by upstream. As you wrote 
this also in the github tracker, I guess you mean to Python directly.
Several Plone developers tested Plone independently with a stock, self compiled 
Python 2.7.11. and confirmed, that their Plone/Zope instance does not segfault. 
So the patches in Ubuntu Python must be the source of the problem.

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

Title:
  python2.7 crashes with SegFault when running Zope

Status in python2.7 package in Ubuntu:
  Confirmed

Bug description:
  Source package / Package:

  python2.7_2.7.11-7ubuntu1

  System:

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  
  This is a bug report originating from the findings documented in

  https://github.com/zopefoundation/Zope/issues/56

  
  The expected behaviour is this:
  - Upon installing Zope2 in a virtualenv a default instance should work with 
no issues.

  What happens instead:
  - The freshly installed Zope instance causes Python to SegFault after only a 
few requests.

  But Python should never SegFault.

  
  The following program produces the error:

  
  #!/bin/bash
  set -e

  # Call this testing script with an argument "setup" for the first time
  # to build the testing case
  #
  # After that, the script only performs the test as described below.
  #
  # Requirements: apt-get install virtualenv python2.7-dbg
  #
  # This script needs internet access when running.

  # The python version to test:
  python=/usr/bin/python2.7-dbg

  # This part builds the testing environment

  if [ "$1" == "setup" ] ; then
  # Virtual environment with the chosen python 
  virtualenv --python ${python} --no-site-packages zope-virtualenv
  cd zope-virtualenv
  # Basic Zope installation
  ./bin/easy_install -i http://download.zope.org/Zope2/index/2.13.24 Zope2
  # Simplest possible Zope instance
  ./bin/mkzopeinstance --dir instance --user admin:admin
  cd ..
  fi

  # THE TEST

  # Run Zope instance in the background
  zope-virtualenv/instance/bin/runzope &

  # Give Zope some time to start up
  sleep 3

  # Call a few management URLs, nothing too fancy...
  urls="
  http://admin:admin@localhost:8080/Control_Panel/manage_main
  http://admin:admin@localhost:8080/Control_Panel/Database/main/manage_main
  http://admin:admin@localhost:8080/Control_Panel/Database/manage_main
  http://admin:admin@localhost:8080/Control_Panel/Database/main/manage_activity
  http://admin:admin@localhost:8080/manage
  http://admin:admin@localhost:8080/acl_users/manage_main
  http://admin:admin@localhost:8080/acl_users/manage_access
  "

  while true ; do
  for url in ${urls} ; do 
echo ${url}
  curl -s $url -o /dev/null
  done
  done

  # This test fails after about 10 requests with
  # Fatal Python error: ../Objects/descrobject.c:10 object at 0x??? has 
negative ref count -1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1580577/+subscriptions

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

[Touch-packages] [Bug 1549455] Re: Qt clients on Intel Pineview graphics fail to create egl context with Mir

[Gerry Boland]

Just considering the Dash problem, the crash is a symptom of a bigger
problem: seems qtubuntu is unable to choose or manage the egl config
correctly. If a correct/working egl config was chosen, then this code
path wouldn't be entered (which has the "delete when not created" bug
seen here).

The actual problem is that eglCreateContext fails with EGL_BAD_MATCH on
the problem hardware. I'm experimenting with lp:~gerboland/qtubuntu
/adopt-more-eglconvenience2/ which uses Qt's EGL config choosing code
(that works ok on X11) in case that works.

I've update this bug title/description to match.

You're right that the unity8 performance problem is a separate issue.
I've logged bug 1580792 to encompass that.

** Summary changed:

- Unity8-dash on Intel Pineview graphics crashes and restarts continuously 
[qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"]
+ Qt clients on Intel Pineview graphics fail to create egl context with Mir

** Description changed:

+ Qt clients are failing to create an egl context when running on Intel
+ Pineview systems under Mir.
+ 
+ eglCreateContext fails with a EGL_BAD_MATCH error code.
+ 
+ When it fails, Qt tries to delete & recreate the context, which then
+ crashes the client (bug 1580118)
+ 
+ 
+ === Original bug description ===
  This bug Makes the pc UNUSABLE
  when I try to launch Unity 8 and Mir, after writing the password on the login 
(in the image attached) the bar to enter the password disappears and my 
computer screen stays stuck without them let me do anything. the connection 
begins to separate and reattach alone and I can only move the cursor. it makes 
the computer unusable and I am forced to restart forced to then enter into 
Unity 7. represented in the screenshot is the lock status after entering the 
password.
  Version: unity8.12+16.04.201604.01.1
  Version of Mir : 0.21

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

Title:
  Qt clients on Intel Pineview graphics fail to create egl context with
  Mir

Status in Mir:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in qtdeclarative package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Qt clients are failing to create an egl context when running on Intel
  Pineview systems under Mir.

  eglCreateContext fails with a EGL_BAD_MATCH error code.

  When it fails, Qt tries to delete & recreate the context, which then
  crashes the client (bug 1580118)

  
  === Original bug description ===
  This bug Makes the pc UNUSABLE
  when I try to launch Unity 8 and Mir, after writing the password on the login 
(in the image attached) the bar to enter the password disappears and my 
computer screen stays stuck without them let me do anything. the connection 
begins to separate and reattach alone and I can only move the cursor. it makes 
the computer unusable and I am forced to restart forced to then enter into 
Unity 7. represented in the screenshot is the lock status after entering the 
password.
  Version: unity8.12+16.04.201604.01.1
  Version of Mir : 0.21

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

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

[Touch-packages] [Bug 1580792] [NEW] Unity8 on Intel Pineview performs poorly

[Gerry Boland]

Public bug reported:

(problem forked from bug 1549455)

Unity8 on Intel Pineview performs very poorly. Frame times appears to be
up to 900ms, Qt's renderer thread using 100% CPU.

Running unity8 with MESA_DEBUG=1 EGL_LOG_LEVEL=debug reveals a few MESA errors:
http://paste.ubuntu.com/16344427/

Quoting @vanvugt "Those Mesa errors "Mesa: User error:" all look like
OpenGL features that Unity8 is hitting but mir-demos don't. So those gl
calls are also good candidates for explaining poor performance,
especially if Mesa is falling back to software rendering for them."

Since Qt tends to perform just fine on that hardware in X11, something
isn't right.

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

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

Title:
  Unity8 on Intel Pineview performs poorly

Status in unity8 package in Ubuntu:
  New

Bug description:
  (problem forked from bug 1549455)

  Unity8 on Intel Pineview performs very poorly. Frame times appears to
  be up to 900ms, Qt's renderer thread using 100% CPU.

  Running unity8 with MESA_DEBUG=1 EGL_LOG_LEVEL=debug reveals a few MESA 
errors:
  http://paste.ubuntu.com/16344427/

  Quoting @vanvugt "Those Mesa errors "Mesa: User error:" all look like
  OpenGL features that Unity8 is hitting but mir-demos don't. So those
  gl calls are also good candidates for explaining poor performance,
  especially if Mesa is falling back to software rendering for them."

  Since Qt tends to perform just fine on that hardware in X11, something
  isn't right.

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

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

[Touch-packages] [Bug 1538438] Re: apt-helper crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()

[Brian Murray]

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

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

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

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

** Changed in: apt (Ubuntu)
Milestone: xenial-updates => None

** Description changed:

+ Test Case
+ --
+ Given that there are thousands of these crashes in the Error Tracker, just 
make sure the new version doesn't appear there.
+ 
  Errors Bucket
  -
  
https://errors.ubuntu.com/bucket/?id=/usr/lib/apt/apt-helper%3A6%3A__gnu_cxx%3A%3A__verbose_terminate_handler%3A__cxxabiv1%3A%3A__terminate%3Astd%3A%3Aterminate%3A__cxxabiv1%3A%3A__cxa_throw%3Astd%3A%3A__throw_out_of_range_fmt
  
  Original Description
  
  After installing flashplugin-installer I get a prompt noting:
  [START]
  Failure to download extra data files
  
  The following packages requested additional data downloads after package
  installation, but the data could not be downloaded or could not be
  processed.
  
  flashplugin-installer
  
  The download will be attempted again later, or you can try the download again 
now.  Running this command requires an active Internet connection.
  [END]
  
  Clicking the button Run this action now causes this crash consistently.
  
  Unfortunately, this has the negative outcome of disallowing folks who
  use Firefox from being able to update, or install Flash.
  
  There are a fair number of these events logged in errors.ubuntu.com.
  
  ProblemType: CrashDistroRelease: Ubuntu 16.04
  Package: apt 1.1.10
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  Date: Wed Jan 27 01:36:34 2016
  ExecutablePath: /usr/lib/apt/apt-helper
  InstallationDate: Installed on 2015-04-25 (276 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: /usr/lib/apt/apt-helper download-file 
http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-flashplugin_20151228.1.orig.tar.gz
 
/var/lib/update-notifier/package-data-downloads/partial/adobe-flashplugin_20151228.1.orig.tar.gz
 SHA256:d322547d4542eeed2f57469cc0d3c10e9a55af6632c05be9fe8b6c6a0dbcffdb
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   LANGUAGE=en_US
   TERM=xterm-256color
-  PATH=(custom, no user)
- Signal: 6SourcePackage: apt
+  PATH=(custom, no user)Signal: 6SourcePackage: apt
  StacktraceTop:
   __gnu_cxx::__verbose_terminate_handler() () from 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   std::__throw_out_of_range_fmt(char const*, ...) () from 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
  Title: apt-helper crashed with SIGABRT in 
__gnu_cxx::__verbose_terminate_handler()
  UpgradeStatus: Upgraded to xenial on 2016-01-27 (0 days ago)
  UserGroups:

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

Title:
  apt-helper crashed with SIGABRT in
  __gnu_cxx::__verbose_terminate_handler()

Status in apt package in Ubuntu:
  Triaged
Status in apt source package in Xenial:
  In Progress

Bug description:
  Test Case
  --
  Given that there are thousands of these crashes in the Error Tracker, just 
make sure the new version doesn't appear there.

  Errors Bucket
  -
  
https://errors.ubuntu.com/bucket/?id=/usr/lib/apt/apt-helper%3A6%3A__gnu_cxx%3A%3A__verbose_terminate_handler%3A__cxxabiv1%3A%3A__terminate%3Astd%3A%3Aterminate%3A__cxxabiv1%3A%3A__cxa_throw%3Astd%3A%3A__throw_out_of_range_fmt

  Original Description
  
  After installing flashplugin-installer I get a prompt noting:
  [START]
  Failure to download extra data files

  The following packages requested additional data downloads after
  package installation, but the data could not be downloaded or could
  not be processed.

  flashplugin-installer

  The download will be attempted again later, or you can try the download again 
now.  Running this command requires an active Internet connection.
  [END]

  Clicking the button Run this action now causes this crash
  consistently.

  Unfortunately, this has the negative outcome of disallowing folks who
  use Firefox from being able to update, or install Flash.

  There are a fair number of these events logged in errors.ubuntu.com.

  ProblemType: CrashDistroRelease: Ubuntu 16.04
  Package: apt 1.1.10
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  Date: Wed Jan 27 01:36:34 2016
  ExecutablePath: 

[Touch-packages] [Bug 1580786] [NEW] abnormal CPU-usage

[Morten Frisch]

Public bug reported:

Logged into my computer and Xorg was using 100% -140% of CPU

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Wed May 11 23:16:08 2016
InstallationDate: Installed on 2016-04-08 (33 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  abnormal CPU-usage

Status in xorg package in Ubuntu:
  New

Bug description:
  Logged into my computer and Xorg was using 100% -140% of CPU

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed May 11 23:16:08 2016
  InstallationDate: Installed on 2016-04-08 (33 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  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/1580786/+subscriptions

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

[Touch-packages] [Bug 1572112] Re: Sync maintenance release lcms2 2.7-1 (main) from Debian testing (main)

[Launchpad Bug Tracker]

This bug was fixed in the package lcms2 - 2.7-1ubuntu1

---
lcms2 (2.7-1ubuntu1) yakkety; urgency=low

  * Merge from Debian unstable (LP: #1572112).  Remaining changes:
- debian/patches/byte-order.patch: Use endian.h to determine
  byte order in use.

lcms2 (2.7-1) unstable; urgency=medium

  * Imported Upstream version 2.7 (Closes: 819718)
  * No longer ship own copy of documentation source files
  * Removed patches (applied upstream)
+ update-manpages.patch
+ sanity-check-profiles-CVE-2014-0459.patch
+ endianness-verification-fix-powerpc.patch
  * Move to automatic dbgsym packages
  * Use secure URLs for Version Control System repository
  * Bump Standards version to 3.9.7, no changes needed
  * New patch: dont-write-uninitialized-memory-for-color-strings.patch
Thanks to Jérémy Bobbio  (Closes: 815248)
  * Update maintainers field (Closes: 820138)

 -- Michael Terry   Wed, 11 May 2016 14:04:29 -0400

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-0459

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

Title:
  Sync maintenance release lcms2 2.7-1 (main) from Debian testing (main)

Status in lcms2 package in Ubuntu:
  Fix Released

Bug description:
  Please Merge lcms2 2.7-1 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta:
    * No change rebuild to get debug symbols on all architectures.
    * Merge with Debian, remaining change:
  - debian/patches/byte-order.patch: Use endian.h to determine byte order 
in use.
  

  https://github.com/mm2/Little-CMS/blob/master/ChangeLog

  Fixed a possible segmentation fault in a non-happy path
  Fixed a macro clash on SNONE.
  Added a safety check on named color lists
  Added a function to retrieve the iohandler of a given profile object
  Remove unused vcproj files
  Some maintenance fixes
  utils/jpgicc/iccjpeg.c: Fix check if unsigned variable 'total_length'… …
  Add missing comma in CGATS parser
  Remove dead code.
  Move unused var suppresor before the `return` statements.
  Added a flag to clip negative values in unbounded transforms (only gray, rgb, 
cmyk)
  Added a global optimization that merges consecutive matrices in pipelines. 
Fixes loss of precision in some transforms
  New project for mac
  Added license for iccjpeg.c
  Added a project for VS2013
  Fixed wrong handling of extra channels in some formatters.
  Added an option in transicc for working in bounded mode
  Added a version retrieval function
  

  Changelog entries since current xenial version 2.6-3ubuntu2:

  lcms2 (2.7-1) unstable; urgency=medium

    * Imported Upstream version 2.7 (Closes: 819718)
    * No longer ship own copy of documentation source files
    * Removed patches (applied upstream)
  + update-manpages.patch
  + sanity-check-profiles-CVE-2014-0459.patch
  + endianness-verification-fix-powerpc.patch
    * Move to automatic dbgsym packages
    * Use secure URLs for Version Control System repository
    * Bump Standards version to 3.9.7, no changes needed
    * New patch: dont-write-uninitialized-memory-for-color-strings.patch
  Thanks to Jérémy Bobbio  (Closes: 815248)
    * Update maintainers field (Closes: 820138)

   -- Thomas Weber   Mon, 18 Apr 2016 15:53:10 +0200

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

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

[Touch-packages] [Bug 1519499] Re: Shutdown failure: Assertion 'sd_id128_randomize() >= 0' failed at ../src/core/dbus.c:657, function bus_on_connection(). Aborting.

[Sven R. Kunze]

Indeed it does. Glad to see the bug persists even on 16.04 and its not
just a mal-configuration on my side.

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

Title:
  Shutdown failure: Assertion 'sd_id128_randomize() >= 0' failed at
  ../src/core/dbus.c:657, function bus_on_connection(). Aborting.

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  This is a follow-up on this issue here:
  https://github.com/lxc/lxd/issues/1336 I cannot stop a LXD container
  gently and as it seems the issue lies within ubuntu/systemd which does
  not handle SIGPWR correctly.

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

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

[Touch-packages] [Bug 1261840] Re: lcms2 memory corruption results in broken profile

[Amr Ibrahim]

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

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

Title:
  lcms2 memory corruption results in broken profile

Status in lcms2 package in Ubuntu:
  Fix Released

Bug description:
  A known bug in lcms2-2.5 results in a broken profile being written to
  disk.

  https://github.com/mm2/Little-
  CMS/commit/1d2643cb8153c48dcfdee3d5cda43a38f7e719e2

  I was hit with this bug with colord/xiccd in Ubuntu Saucy, for which I
  have fixed packages on my PPA:

  https://launchpad.net/~pmjdebruijn/+archive/xiccd-testing

  However, I hope this patch could be applied to the package in Ubuntu
  Trusty.

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

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

[Touch-packages] [Bug 1580774] Re: mouse is getting stuck on a phantom edge

[kevin gunn]

@dandrader this looks really familiar to that bug last year in london
that you and anpok worked on

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

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

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

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

** Changed in: qtmir (Ubuntu)
   Importance: Undecided => Critical

** Changed in: qtmir (Ubuntu)
 Assignee: (unassigned) => Daniel d'Andrada (dandrader)

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

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Andreas Pokorny (andreas-pokorny)

** Changed in: unity8 (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  mouse is getting stuck on a phantom edge

Status in Canonical System Image:
  New
Status in mir package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  frieza build 101/rc-proposed

  Steps:
  1. connect mouse & keyboard to M10
  2. launch xchat
  3. go full screen
  4. mouse move around across the entirety of the screen (landscape)

  expected: mouse can range over entire screen
  actual: gets stuck moving right

  note: i noticed it happening on xchat, but when changing focus to dash
  it was also continuing to happen

  So, i kinda suspect this may be related to rotation maybe.
  I do admit i did the full OOBE in portrait mode

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

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

[Touch-packages] [Bug 1580774] [NEW] mouse is getting stuck on a phantom edge

[kevin gunn]

Public bug reported:

frieza build 101/rc-proposed

Steps:
1. connect mouse & keyboard to M10
2. launch xchat
3. go full screen
4. mouse move around across the entirety of the screen (landscape)

expected: mouse can range over entire screen
actual: gets stuck moving right

note: i noticed it happening on xchat, but when changing focus to dash
it was also continuing to happen

So, i kinda suspect this may be related to rotation maybe.
I do admit i did the full OOBE in portrait mode

** Affects: canonical-devices-system-image
 Importance: Critical
 Assignee: Michał Sawicz (saviq)
 Status: New

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

** Affects: qtmir (Ubuntu)
 Importance: Critical
 Assignee: Daniel d'Andrada (dandrader)
 Status: New

** Affects: unity8 (Ubuntu)
 Importance: Critical
 Assignee: Andreas Pokorny (andreas-pokorny)
 Status: New

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

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

Title:
  mouse is getting stuck on a phantom edge

Status in Canonical System Image:
  New
Status in mir package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  frieza build 101/rc-proposed

  Steps:
  1. connect mouse & keyboard to M10
  2. launch xchat
  3. go full screen
  4. mouse move around across the entirety of the screen (landscape)

  expected: mouse can range over entire screen
  actual: gets stuck moving right

  note: i noticed it happening on xchat, but when changing focus to dash
  it was also continuing to happen

  So, i kinda suspect this may be related to rotation maybe.
  I do admit i did the full OOBE in portrait mode

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

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

[Touch-packages] [Bug 1538438] Re: apt-helper crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()

[Brian Murray]

If this crash is fixed by the commit to which David pointed, then that
is fixed in version 1.2.12 of apt which is now in Debian.  Rather than
waiting to see if that version does not appear in the errors bucket,
keeping in mind there are only a handful of crashes about 1.2.11, I
think we should upload the fix to -proposed for Xenial and see what
happens.

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

Title:
  apt-helper crashed with SIGABRT in
  __gnu_cxx::__verbose_terminate_handler()

Status in apt package in Ubuntu:
  Triaged

Bug description:
  Errors Bucket
  -
  
https://errors.ubuntu.com/bucket/?id=/usr/lib/apt/apt-helper%3A6%3A__gnu_cxx%3A%3A__verbose_terminate_handler%3A__cxxabiv1%3A%3A__terminate%3Astd%3A%3Aterminate%3A__cxxabiv1%3A%3A__cxa_throw%3Astd%3A%3A__throw_out_of_range_fmt

  Original Description
  
  After installing flashplugin-installer I get a prompt noting:
  [START]
  Failure to download extra data files

  The following packages requested additional data downloads after
  package installation, but the data could not be downloaded or could
  not be processed.

  flashplugin-installer

  The download will be attempted again later, or you can try the download again 
now.  Running this command requires an active Internet connection.
  [END]

  Clicking the button Run this action now causes this crash
  consistently.

  Unfortunately, this has the negative outcome of disallowing folks who
  use Firefox from being able to update, or install Flash.

  There are a fair number of these events logged in errors.ubuntu.com.

  ProblemType: CrashDistroRelease: Ubuntu 16.04
  Package: apt 1.1.10
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  Date: Wed Jan 27 01:36:34 2016
  ExecutablePath: /usr/lib/apt/apt-helper
  InstallationDate: Installed on 2015-04-25 (276 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: /usr/lib/apt/apt-helper download-file 
http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-flashplugin_20151228.1.orig.tar.gz
 
/var/lib/update-notifier/package-data-downloads/partial/adobe-flashplugin_20151228.1.orig.tar.gz
 SHA256:d322547d4542eeed2f57469cc0d3c10e9a55af6632c05be9fe8b6c6a0dbcffdb
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
  Signal: 6SourcePackage: apt
  StacktraceTop:
   __gnu_cxx::__verbose_terminate_handler() () from 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   std::__throw_out_of_range_fmt(char const*, ...) () from 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
  Title: apt-helper crashed with SIGABRT in 
__gnu_cxx::__verbose_terminate_handler()
  UpgradeStatus: Upgraded to xenial on 2016-01-27 (0 days ago)
  UserGroups:

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

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

[Touch-packages] [Bug 1580637] Re: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv

[Martin Pitt]

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

** This bug has been marked a duplicate of bug 1560797
   apt does not configure Pre-Depends: before depending package

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

Title:
  package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre-
  dependency problem - not installing systemd-sysv

Status in systemd package in Ubuntu:
  New

Bug description:
  Error during upgrading to 16.10. I cannot boot the computer normally,
  only using the "upstart" kernel version.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd-sysv 229-4ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Wed May 11 15:56:43 2016
  ErrorMessage: pre-dependency problem - not installing systemd-sysv
  InstallationDate: Installed on 2015-10-14 (209 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: systemd
  Title: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: 
pre-dependency problem - not installing systemd-sysv
  UpgradeStatus: Upgraded to xenial on 2016-05-11 (0 days ago)

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

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

[Touch-packages] [Bug 603415] Re: Unity should have a screen magnifier

[Billy]

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

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

Title:
  Unity should have a screen magnifier

Status in Compiz:
  In Progress
Status in Nux:
  Triaged
Status in Unity:
  Triaged
Status in compiz package in Ubuntu:
  In Progress
Status in nux package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Triaged
Status in compiz source package in Xenial:
  In Progress
Status in nux source package in Xenial:
  Confirmed
Status in unity source package in Xenial:
  Fix Released

Bug description:
  Binary package hint: gnome-control-center

  In gnome-keybindings-properties, in the Accessibility section, there
  are three entries by default: toggle magnifier, toggle screen reader,
  and toggle on-screen keyboard. None of these work, whether or not
  Assistive Technologies is currently running and whether or not orca is
  currently running.

  WHAT I EXPECT TO HAPPEN: I should be able to configure a shortcut to
  any of these actions, such as Ctrl-Alt-A to the Toggle magnifier
  action. Then, pressing, Ctrl-Alt-A will start the magnifier.

  WHAT ACTUALLY HAPPENS: I am able to modify the entry in the gnome-
  keybindings-properties window, but pressing the designated key does
  not perform any action. That is, the magnifier does not open. Changing
  the hotkeys for other actions works okay.

  WHY THIS IS BAD: This is confusing and misleading behavior, and can be
  especially damaging for people who need the accessibility features.
  Ideally, the keybindings should be fixed, but otherwise they should be
  removed from the dialog.

  This is true under up-to-date Lucid 10.04 tested on several systems.

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

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

[Touch-packages] [Bug 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04

[Martin Pitt]

> "journalctl |grep systemd > log"

Sorry, that's wrong. The lid is handled by logind, can you please re-try
with

   sudo journalctl -b -t systemd-logind > /tmp/logind.log

and attach /tmp/logind.log here?

Also, from your /sys/class/drm it looks like you have an external
monitor enabled, but it's not quite clear which "enabled" applies to
which device. Can you please copy the output of

  grep -r . /sys/class/drm/*/enabled

Thanks!

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

Title:
  Notebook doesn't suspend when lid is closed after update to 16.04

Status in systemd package in Ubuntu:
  New

Bug description:
  My notebook does not suspend after upgrading from 15.10 to 16.04.

  According to system settings the notebook should suspend when lid is
  closed but actually this does not happen. Instead it continues to run
  as if nothing had happened.

  With the previous versions of ubuntu (14.04-15.10) everything worked
  fine.

  My System: HP Pavilion dv7.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: acpi (not installed)
  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: Sat Apr 23 23:11:15 2016
  InstallationDate: Installed on 2015-10-29 (176 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: acpi
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)

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

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

[Touch-packages] [Bug 1572112] Re: Sync maintenance release lcms2 2.7-1 (main) from Debian testing (main)

[Amr Ibrahim]

Sorry Michael, I thought the delta was dropped. Thanks for working on
it.

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

Title:
  Sync maintenance release lcms2 2.7-1 (main) from Debian testing (main)

Status in lcms2 package in Ubuntu:
  New

Bug description:
  Please Merge lcms2 2.7-1 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta:
    * No change rebuild to get debug symbols on all architectures.
    * Merge with Debian, remaining change:
  - debian/patches/byte-order.patch: Use endian.h to determine byte order 
in use.
  

  https://github.com/mm2/Little-CMS/blob/master/ChangeLog

  Fixed a possible segmentation fault in a non-happy path
  Fixed a macro clash on SNONE.
  Added a safety check on named color lists
  Added a function to retrieve the iohandler of a given profile object
  Remove unused vcproj files
  Some maintenance fixes
  utils/jpgicc/iccjpeg.c: Fix check if unsigned variable 'total_length'… …
  Add missing comma in CGATS parser
  Remove dead code.
  Move unused var suppresor before the `return` statements.
  Added a flag to clip negative values in unbounded transforms (only gray, rgb, 
cmyk)
  Added a global optimization that merges consecutive matrices in pipelines. 
Fixes loss of precision in some transforms
  New project for mac
  Added license for iccjpeg.c
  Added a project for VS2013
  Fixed wrong handling of extra channels in some formatters.
  Added an option in transicc for working in bounded mode
  Added a version retrieval function
  

  Changelog entries since current xenial version 2.6-3ubuntu2:

  lcms2 (2.7-1) unstable; urgency=medium

    * Imported Upstream version 2.7 (Closes: 819718)
    * No longer ship own copy of documentation source files
    * Removed patches (applied upstream)
  + update-manpages.patch
  + sanity-check-profiles-CVE-2014-0459.patch
  + endianness-verification-fix-powerpc.patch
    * Move to automatic dbgsym packages
    * Use secure URLs for Version Control System repository
    * Bump Standards version to 3.9.7, no changes needed
    * New patch: dont-write-uninitialized-memory-for-color-strings.patch
  Thanks to Jérémy Bobbio  (Closes: 815248)
    * Update maintainers field (Closes: 820138)

   -- Thomas Weber   Mon, 18 Apr 2016 15:53:10 +0200

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

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

[Touch-packages] [Bug 1578665] Re: no trust prompt appearing in clock or weather app after images on the 4th of may

[Launchpad Bug Tracker]

** Branch linked: lp:~dandrader/unity8/surfaceDrawn

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

Title:
  no trust prompt appearing in clock or weather app after images on the
  4th of may

Status in Canonical System Image:
  In Progress
Status in trust-store:
  Invalid
Status in qtmir package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  STEPS:
  1. Bootstrap the latest rc-proposed
  2. Open clock app after a long start up time you will note that you were not 
asked 
  3. Open the weather app and see similar behaviour

  EXPECTED:
  All most instant popup for trust store to allow location access

  ACTUAL:
  A long delay before the app opens and then no trust prompt and no location 
detection.

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

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

[Touch-packages] [Bug 1580700] Re: Add Let's Encrypt Authority to Package

[Marc Deslauriers]

I've uploaded a fixed wget package to precise-proposed for processing by
the SRU team.

** Also affects: wget (Ubuntu Precise)
   Importance: Undecided
   Status: New

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

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

** Changed in: wget (Ubuntu Precise)
 Assignee: (unassigned) => Marc Deslauriers (mdeslaur)

** Description changed:

+ [Impact]
+ wget in Ubuntu 12.04 doesn't have support for TLS Server Name Indication, 
which makes it incompatible with certain sites, includes sites that use the 
Let's Encrypt Authority.
+ 
+ The updated package fixes the issue with a backported patch from wget
+ 1.14.
+ 
+ [Test Case]
+ 1- wget https://www.x.org
+ 2- Connection should succeed, instead of getting an error (ERROR: no 
certificate subject alternative name matches)
+ 
+ [Regression Potential]
+ Commit is simple. If broken, could possibly break SSL support in wget.
+ 
+ 
+ Original report:
+ 
  Let's Encrypt Authority should be added to CA-certificates.
  https://www.X.org is now using a cert from this CA, wget fails when
  connecting to X.org.

** Summary changed:

- Add Let's Encrypt Authority to Package
+ wget in 12.04 does not support SNI

** Changed in: wget (Ubuntu Precise)
   Status: Confirmed => In Progress

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

Title:
  wget in 12.04 does not support SNI

Status in wget package in Ubuntu:
  Fix Released
Status in wget source package in Precise:
  In Progress

Bug description:
  [Impact]
  wget in Ubuntu 12.04 doesn't have support for TLS Server Name Indication, 
which makes it incompatible with certain sites, includes sites that use the 
Let's Encrypt Authority.

  The updated package fixes the issue with a backported patch from wget
  1.14.

  [Test Case]
  1- wget https://www.x.org
  2- Connection should succeed, instead of getting an error (ERROR: no 
certificate subject alternative name matches)

  [Regression Potential]
  Commit is simple. If broken, could possibly break SSL support in wget.

  
  Original report:

  Let's Encrypt Authority should be added to CA-certificates.
  https://www.X.org is now using a cert from this CA, wget fails when
  connecting to X.org.

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

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

[Touch-packages] [Bug 1452849] Re: initctl cannot find Upstart

[twicejr]

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

Happens now on 16.10 as well, on my system...

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

Title:
  initctl cannot find Upstart

Status in upstart :
  New
Status in upstart package in Ubuntu:
  Triaged

Bug description:
  Please see Apport's automatically generated files (attached)

  ProblemType: RecoverableProblem
  DistroRelease: Ubuntu 15.04
  Package: upstart 1.13.2-0ubuntu13
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May  7 19:03:35 2015
  DuplicateSignature: /sbin/upstart:indicator-session-unknown-user-error
  ExecutablePath: /sbin/upstart
  InstallationDate: Installed on 2011-12-08 (1246 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcCmdline: /sbin/upstart --user
  SourcePackage: upstart
  UpgradeStatus: Upgraded to vivid on 2015-04-24 (13 days ago)
  UpstartBugCategory: Session
  UpstartRunningSessionCount: 1
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: Error: command ['initctl', '--system', 
'version'] failed with exit code 1: initctl: Name "com.ubuntu.Upstart" does not 
exist
  UserGroups: adm admin avahi avahi-autoipd cdrom dialout dip fax floppy fuse 
lp lpadmin mythtv plugdev sambashare tape users video whoopsie www-data
  icon_file: (null)
  is_current_user: false
  is_logged_in: false
  real_name: (null)
  uid: 0
  upstart.upstart-event-bridge.log: upstart-event-bridge: Could not connect to 
system Upstart: Failed to connect to socket /com/ubuntu/upstart/local/bridge: 
Connection refused
  user_name: (null)

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

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

[Touch-packages] [Bug 1580768] [NEW] bluetooth keyboard flashes in ubuntu-system-settings

[kevin gunn]

Public bug reported:

on latest rc-proposed for frieza seeing the following

1. connect bt mouse, no problem
2. turn on bt keyboard (logitech k480)
3. click sync
4. u-s-s spinner goes

expect: to see keyboard icon in list and availble to click on
actual: keyboard icon flashes for just a moment, then disappears, very 
consistent once in this state

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

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

Title:
  bluetooth keyboard flashes in ubuntu-system-settings

Status in bluez package in Ubuntu:
  New

Bug description:
  on latest rc-proposed for frieza seeing the following

  1. connect bt mouse, no problem
  2. turn on bt keyboard (logitech k480)
  3. click sync
  4. u-s-s spinner goes

  expect: to see keyboard icon in list and availble to click on
  actual: keyboard icon flashes for just a moment, then disappears, very 
consistent once in this state

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

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

[Touch-packages] [Bug 1323837] Re: [phone] Sim toolkit is not available on UT

[Alexander Nilsen]

Is there any way to use sim toolkit functionality from terminal?

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

Title:
  [phone] Sim toolkit is not available on UT

Status in Canonical System Image:
  Incomplete
Status in Ubuntu UX:
  Triaged
Status in ofono package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  E.g. of SIm toolkit is http://support.vodafone.com.au/articles/FAQ
  /SIM-Toolkit

  While a lot of those addons are completely crap and useless, the SIm
  toolkit is sometimes used by some phone provider to set your sim card
  to roaming mode when you are abroad which makes it a must have.

  For the moment i need to borrow a second phone put my sim card in it,
  go to the Sim-toolkit, enable my sim card for roaming and put the sim
  card back in my UT to get my phone working while i am abroad. I need
  to do the same when i go back home.

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

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

[Touch-packages] [Bug 1578196] Re: External Display Port monitor not working

[kanschat]

This Bug affects me too. Lenovo Thinkpad x250 with Docking-Station. 
BIOS is showing up via Display Port, but when/after loading GRUB the monitor 
gets no signal.

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

Title:
  External Display Port monitor not working

Status in X.Org X server:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I have three monitors on my Lenovo X250, one built-in and two
  connected via a Lenovo docking station :

  built-in: 1920x1080
  HP 2335: 1920x1200
  BenQ GW2765: 2560x1440

  The HP is connected via DVI and the BenQ via Display Port.

  In this configuration, I get my HP and built-in ok, but the BenQ
  doesn't show up at all (using xrandr --query).

  If I connect the BenQ via HDMI, then it shows up in xrandr --query,
  but the display is still blank (bandwidth issue?).

  Here's the output with the DVI + DP config :

  $ xrandr --query
  Screen 0: minimum 8 x 8, current 3840 x 1200, maximum 32767 x 32767
  eDP1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 
276mm x 156mm
 1920x1080 60.04*+  59.93  
 1680x1050 59.9559.88  
 1600x1024 60.17  
 1400x1050 59.98  
 1600x900  60.00  
 1280x1024 60.02  
 1440x900  59.89  
 1280x960  60.00  
 1368x768  60.00  
 1360x768  59.8059.96  
 1152x864  60.00  
 1280x720  60.00  
 1024x768  60.00  
 1024x576  60.00  
 960x540   60.00  
 800x600   60.3256.25  
 864x486   60.00  
 640x480   59.94  
 720x405   60.00  
 640x360   60.00  
  DP1 disconnected (normal left inverted right x axis y axis)
  DP2 disconnected (normal left inverted right x axis y axis)
  DP2-1 disconnected (normal left inverted right x axis y axis)
  DP2-2 connected primary 1920x1200+0+0 (normal left inverted right x axis y 
axis) 495mm x 310mm
 1920x1200 59.95*+
 1600x1200 60.00  
 1280x1024 85.0275.0260.02  
 1280x960  60.00  
 1152x864  75.00  
 1024x768  85.0075.0370.0760.00  
 832x624   74.55  
 800x600   75.0060.32  
 640x480   75.0059.94  
 720x400   70.08  
  DP2-3 disconnected (normal left inverted right x axis y axis)
  HDMI1 disconnected (normal left inverted right x axis y axis)
  HDMI2 disconnected (normal left inverted right x axis y axis)
  VIRTUAL1 disconnected (normal left inverted right x axis y axis)

  and with built-in and BenQ only :

  $ xrandr --query
  Screen 0: minimum 8 x 8, current 4480 x 1440, maximum 32767 x 32767
  eDP1 connected primary 1920x1080+0+360 (normal left inverted right x axis y 
axis) 276mm x 156mm
 1920x1080 60.04*+  59.93  
 1680x1050 59.9559.88  
 1600x1024 60.17  
 1400x1050 59.98  
 1600x900  60.00  
 1280x1024 60.02  
 1440x900  59.89  
 1280x960  60.00  
 1368x768  60.00  
 1360x768  59.8059.96  
 1152x864  60.00  
 1280x720  60.00  
 1024x768  60.00  
 1024x576  60.00  
 960x540   60.00  
 800x600   60.3256.25  
 864x486   60.00  
 640x480   59.94  
 720x405   60.00  
 640x360   60.00  
  DP1 disconnected (normal left inverted right x axis y axis)
  DP2 disconnected (normal left inverted right x axis y axis)
  DP2-1 connected 2560x1440+1920+0 (normal left inverted right x axis y axis) 
597mm x 336mm
 2560x1440 59.95*+
 1920x1080 60.0050.0059.94  
 1680x1050 59.88  
 1600x900  59.98  
 1280x1024 75.0260.02  
 1280x800  59.91  
 1152x864  75.00  
 1280x720  60.0050.0059.94  
 1024x768  75.0860.00  
 832x624   74.55  
 800x600   75.0060.32  
 720x576   50.00  
 720x480   60.0059.94  
 640x480   75.0060.0059.94  
 720x400   70.08  
  DP2-2 disconnected (normal left inverted right x axis y axis)
  DP2-3 disconnected (normal left inverted right x axis y axis)
  HDMI1 disconnected (normal left inverted right x axis y axis)
  HDMI2 disconnected (normal left inverted right x axis y axis)
  VIRTUAL1 disconnected (normal left inverted right x axis y axis)

  This looks relevant :

  

  I'm running kernel 4.6.0-040600rc6-generic (installed as part of the
  debugging process).

  (This bug is the 'next step' from
  )

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.6.0-040600rc6-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  

[Touch-packages] [Bug 1578196] Re: External Display Port monitor not working

[Launchpad Bug Tracker]

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

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

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

Title:
  External Display Port monitor not working

Status in X.Org X server:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I have three monitors on my Lenovo X250, one built-in and two
  connected via a Lenovo docking station :

  built-in: 1920x1080
  HP 2335: 1920x1200
  BenQ GW2765: 2560x1440

  The HP is connected via DVI and the BenQ via Display Port.

  In this configuration, I get my HP and built-in ok, but the BenQ
  doesn't show up at all (using xrandr --query).

  If I connect the BenQ via HDMI, then it shows up in xrandr --query,
  but the display is still blank (bandwidth issue?).

  Here's the output with the DVI + DP config :

  $ xrandr --query
  Screen 0: minimum 8 x 8, current 3840 x 1200, maximum 32767 x 32767
  eDP1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 
276mm x 156mm
 1920x1080 60.04*+  59.93  
 1680x1050 59.9559.88  
 1600x1024 60.17  
 1400x1050 59.98  
 1600x900  60.00  
 1280x1024 60.02  
 1440x900  59.89  
 1280x960  60.00  
 1368x768  60.00  
 1360x768  59.8059.96  
 1152x864  60.00  
 1280x720  60.00  
 1024x768  60.00  
 1024x576  60.00  
 960x540   60.00  
 800x600   60.3256.25  
 864x486   60.00  
 640x480   59.94  
 720x405   60.00  
 640x360   60.00  
  DP1 disconnected (normal left inverted right x axis y axis)
  DP2 disconnected (normal left inverted right x axis y axis)
  DP2-1 disconnected (normal left inverted right x axis y axis)
  DP2-2 connected primary 1920x1200+0+0 (normal left inverted right x axis y 
axis) 495mm x 310mm
 1920x1200 59.95*+
 1600x1200 60.00  
 1280x1024 85.0275.0260.02  
 1280x960  60.00  
 1152x864  75.00  
 1024x768  85.0075.0370.0760.00  
 832x624   74.55  
 800x600   75.0060.32  
 640x480   75.0059.94  
 720x400   70.08  
  DP2-3 disconnected (normal left inverted right x axis y axis)
  HDMI1 disconnected (normal left inverted right x axis y axis)
  HDMI2 disconnected (normal left inverted right x axis y axis)
  VIRTUAL1 disconnected (normal left inverted right x axis y axis)

  and with built-in and BenQ only :

  $ xrandr --query
  Screen 0: minimum 8 x 8, current 4480 x 1440, maximum 32767 x 32767
  eDP1 connected primary 1920x1080+0+360 (normal left inverted right x axis y 
axis) 276mm x 156mm
 1920x1080 60.04*+  59.93  
 1680x1050 59.9559.88  
 1600x1024 60.17  
 1400x1050 59.98  
 1600x900  60.00  
 1280x1024 60.02  
 1440x900  59.89  
 1280x960  60.00  
 1368x768  60.00  
 1360x768  59.8059.96  
 1152x864  60.00  
 1280x720  60.00  
 1024x768  60.00  
 1024x576  60.00  
 960x540   60.00  
 800x600   60.3256.25  
 864x486   60.00  
 640x480   59.94  
 720x405   60.00  
 640x360   60.00  
  DP1 disconnected (normal left inverted right x axis y axis)
  DP2 disconnected (normal left inverted right x axis y axis)
  DP2-1 connected 2560x1440+1920+0 (normal left inverted right x axis y axis) 
597mm x 336mm
 2560x1440 59.95*+
 1920x1080 60.0050.0059.94  
 1680x1050 59.88  
 1600x900  59.98  
 1280x1024 75.0260.02  
 1280x800  59.91  
 1152x864  75.00  
 1280x720  60.0050.0059.94  
 1024x768  75.0860.00  
 832x624   74.55  
 800x600   75.0060.32  
 720x576   50.00  
 720x480   60.0059.94  
 640x480   75.0060.0059.94  
 720x400   70.08  
  DP2-2 disconnected (normal left inverted right x axis y axis)
  DP2-3 disconnected (normal left inverted right x axis y axis)
  HDMI1 disconnected (normal left inverted right x axis y axis)
  HDMI2 disconnected (normal left inverted right x axis y axis)
  VIRTUAL1 disconnected (normal left inverted right x axis y axis)

  This looks relevant :

  

  I'm running kernel 4.6.0-040600rc6-generic (installed as part of the
  debugging process).

  (This bug is the 'next step' from
  )

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.6.0-040600rc6-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: 

[Touch-packages] [Bug 1580700] Re: Add Let's Encrypt Authority to Package

[Marc Deslauriers]

Ubuntu 12.04 has wget 1.13.4, which doesn't have support for TLS Server
Name Indication, which was included in 1.14. That needs to get
backported.

** No longer affects: ca-certificates (Ubuntu)

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

Title:
  Add Let's Encrypt Authority to Package

Status in wget package in Ubuntu:
  New

Bug description:
  Let's Encrypt Authority should be added to CA-certificates.
  https://www.X.org is now using a cert from this CA, wget fails when
  connecting to X.org.

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

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

[Touch-packages] [Bug 1580700] Re: Add Let's Encrypt Authority to Package

[Marc Deslauriers]

I can reproduce this with wget on 12.04, but not on 14.04. Both use the
same version of ca-certificates.

Using openssl directly also works:
openssl s_client -CAfile /etc/ssl/certs/ca-certificates.crt -connect 
www.x.org:443

I suspect wget on 12.04 is doing something odd, I'll look into this.

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

Title:
  Add Let's Encrypt Authority to Package

Status in wget package in Ubuntu:
  New

Bug description:
  Let's Encrypt Authority should be added to CA-certificates.
  https://www.X.org is now using a cert from this CA, wget fails when
  connecting to X.org.

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

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

[Touch-packages] [Bug 1569856] Re: wrong status of ntp service

[Launchpad Bug Tracker]

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

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

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

Title:
  wrong status of ntp service

Status in ntp package in Ubuntu:
  Confirmed

Bug description:
  I'am using lxd containers. In the containers installed ntp package.

  Ubuntu 14.04 has old init.d script to manage a service.

  This script using status_of_proc, function from /lib/lsb/init-
  functions which is disregards that system can have ntpd processes
  running in containers. And returns success status, when ntp service is
  not running on host system but it running in container.

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

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

[Touch-packages] [Bug 1559596] Re: arale capacitive button not disabled on music playback

[Launchpad Bug Tracker]

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

** Changed in: mediaplayer-app (Ubuntu)
   Status: New => Confirmed

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

Title:
  arale capacitive button not disabled on music playback

Status in media-hub package in Ubuntu:
  Incomplete
Status in mediaplayer-app package in Ubuntu:
  Confirmed
Status in unity-scope-mediascanner package in Ubuntu:
  Invalid
Status in unity-scopes-shell package in Ubuntu:
  Invalid

Bug description:
  Arale  ( Meizu MX4)

  When playing music either from music player or my music scope the
  capacitive button doesn't deactivate on Locked screen as usual.

  Usually it deactivates but on music playback it doesn't.

  This bug is since OTA8 days afaik

  currently on rc-proposed r276 and it's still there

  if any more of the information is needed i can gladly help

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

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

[Touch-packages] [Bug 1501041] Re: No visible display in non gnome sessions when using nvidia drivers via nvidia-prime until screen goes to sleep, then waked up

[Dmitry]

Could anyone ask me in which package the main reason for this issue?

Regards,
/Dmitriy

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

Title:
  No visible display in non gnome sessions when using nvidia drivers via
  nvidia-prime until screen goes to sleep, then waked up

Status in lightdm package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers package in Ubuntu:
  Invalid
Status in ubuntu-drivers-common package in Ubuntu:
  Invalid
Status in unity-greeter package in Ubuntu:
  Invalid
Status in xfce4-session package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  ** this appears to be that the display is blanked/asleep at greeter & login.
  Forcing or waiting for screen to blank/sleep then waking up restores display
  See comments 8 & 10 for further info, demonstrations **

  Please note that this bug is being filed on a recent 15.10 Ubuntu
  image install but from a gnome session

  In a nutshell -
  Once nividia drivers are installed & used from nvidia-prime there is no 
longer a visible display in unity-greeter nor in an ubuntu session once logged 
in. (a blind log in successfully loads an ubuntu session.
  Everything in the ubuntu session works fine, there are no errors & all the 
related logs look ok, there is just no visible display.

  I can open apps, run commands, copy/create logs, play music, play
  videos, just no display so has to be done blindly from keyboard.

  On the other hand if I install gnome-shell & log in (blindly) to a
  gnome session from greeter then all is well & I get a visible
  display.

  The same behaviour is seen on an Xubuntu image install, once nvidia is
  installed & switched to, no visible display. Again there installing &
  logging into a gnome session works fine with visible display

  nvidia driver version doesn't matter, exact same is seen with current
  15.10 versions & the one I'm currently using (355) from drivers ppa.

  ** this appears to be that the display is blanked/asleep at greeter & login.
  Forcing or waiting for screen to blank/sleep then waking up restores display
  See comment 8 for further info **

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg-core 2:1.17.2-1ubuntu7
  ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1
  Uname: Linux 4.2.0-11-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue Sep 29 16:15:21 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.2.0-11-generic, x86_64: installed
   nvidia-355, 355.11, 4.2.0-11-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:3801]
   NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2015-09-28 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150928)
  MachineType: LENOVO 20217
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-11-generic.efi.signed 
root=UUID=3712249e-a4c8-4b29-9ffb-f9f9e7d5259a ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 74CN44WW(V3.05)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: VIQY0Y1
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y510P
  dmi.modalias: 
dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P:
  dmi.product.name: 20217
  dmi.product.version: Lenovo IdeaPad Y510P
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+15.10.20150908-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu2
  

[Touch-packages] [Bug 1373495] Re: sudo shouldn't preserve caller's HOME environment variable by default

[Brian Murray]

** Changed in: sudo (Ubuntu)
   Importance: Critical => Medium

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

Title:
  sudo shouldn't preserve caller's HOME environment variable by default

Status in One Hundred Papercuts:
  Triaged
Status in sudo package in Ubuntu:
  Triaged

Bug description:
  Currently Ubuntu hard-coded sudo to preserve HOME environment variable
  to point to sudo caller's home directory by default(refer bug #760140)
  however this is dangerous and error-prone because the program run by
  root may create files (e.g. $HOME/.Xauthority , program config files)
  into caller's HOME directory **AS ROOT** which, will cause issue when
  users run the same program as their normal users' account again and
  even make the user failed to login(due to .Xauthority file owner is
  incorrect)

  In my opinion the Ubuntu patch(keep_home_by_default.patch)(no, Debian
  is NOT affected by this issue) that makes $HOME variable keep in sudo
  is INSANE and should be reverted(Ubuntu should use the safest
  configuration to general users by default), any user wish to run
  command as root using their HOME directory should set env_keep in
  /etc/sudoers themselves and acknowledging the consequences.

  [RootSudo - Community Help
  Wiki](https://help.ubuntu.com/community/RootSudo) wrongly tells that
  graphical application shouldn't be launched by sudo, but in fact the
  real issue falls into this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: sudo 1.8.9p5-1ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-17.23-lowlatency 3.16.3
  Uname: Linux 3.16.0-17-lowlatency i686
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: i386
  CurrentDesktop: KDE
  Date: Thu Sep 25 00:08:44 2014
  InstallationDate: Installed on 2013-03-08 (564 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  SourcePackage: sudo
  UpgradeStatus: Upgraded to trusty on 2014-04-19 (158 days ago)
  VisudoCheck:
   /etc/sudoers: parsed OK
   /etc/sudoers.d/Preserve_input_method_required_environmental_variables: 
parsed OK
   /etc/sudoers.d/README: parsed OK
  modified.conffile..etc.sudoers.d.README: [modified]
  mtime.conffile..etc.sudoers.d.README: 2014-09-24T22:26:35.734703

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

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

[Touch-packages] [Bug 1580744] [NEW] Sound skipping/stuttering every 5-20 minutes

[Alfred Kobayashi]

Public bug reported:

My sound skips/stutters for about half a second (certainly no more than
1 second) on average every 5-20 minutes. I initially had no sound on
this computer with Ubuntu 14.04, which is probably because Ubuntu 14.04
has an outdated version of Alsa. I then tested with a live disc of
Ubuntu 16.04 (before official release date), which did give me sound. At
this point, I installed the the latest version of Alsa onto Ubuntu 14.04
from here (because 16.04 wasn't officially released at the time and I
didn't want to take chances with an unstable system):

https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS

Sound immediately worked with the latest version of Alsa's driver (March
24, 2016 at the time) on Ubuntu 14.04. However, it came with a cost:
this stuttering problem. I then retested with the live disc of Ubuntu
16.04 (this time after the official release date), which also produced
sound but with the exact same stuttering problem.

I found that on Ubuntu 14.04, the stuttering problem remains unfixed
since the March 24, 2016 release of the Alsa daily driver until at least
the version I have installed in this bug report.

These facts strongly suggest an Alsa problem:
1. The problem does not occur at all on Windows, thus ruling out the 
possibility of a hardware problem.
2. I had no sound at all before installing the Alsa daily drivers, but did have 
stuttering sound after installing them.
3. The problem persists on Ubuntu 16.04, which suggests the problem is specific 
to the driver rather than the operating system.
4. The problem occurs whether playing a locally stored media file with a media 
player installed on my computer or watching an online video, thus ruling out 
the possibility that the problem is due to a single browser or plugin issue.
5. Is my hardware too new? Probably not. Here are the results of running "grep 
"Codec:" /proc/asound/card*/codec*":

/proc/asound/card0/codec#0:Codec: Realtek ALC891
/proc/asound/card1/codec#0:Codec: Nvidia Generic

The fact that my card is identified by vendor and chip name rather than
ID as specified at https://wiki.ubuntu.com/Audio/HDAGeneric suggests
that my hardware is supported. By the way, I'm using the Realtek, not
the Nvidia HDMI.

I've tried disabling all unnecessary channels under alsamixer, but that
didn't fix the problem. I tried all 3 potential fixes at
https://wiki.ubuntu.com/Audio/PositionReporting, but none worked either.
I commented my /etc/modprobe.d/alsa-base.conf and /etc/pulse/default.pa
files appropriately to show what I tried (I know at least alsa-base.conf
is uploaded).

I really appreciate the effort you developers put in to supporting sound
on Linux. I hope my bug report will help fix this problem for a lot of
users on Skylake systems.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-86.130-generic 3.13.11-ckt39
Uname: Linux 3.13.0-86-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  theuser1915 F pulseaudio
 /dev/snd/pcmC0D0p:   theuser1915 F...m pulseaudio
CurrentDesktop: Unity
Date: Wed May 11 11:37:46 2016
InstallationDate: Installed on 2016-03-24 (47 days ago)
InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Green Line Out, Rear
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: Underruns, dropouts, or "crackling" sound
Title: [750-170se, Realtek ALC891, Green Line Out, Rear] Underruns, dropouts or 
crackling sound
UpgradeStatus: Upgraded to trusty on 2016-03-24 (47 days ago)
dmi.bios.date: 11/12/2015
dmi.bios.vendor: AMI
dmi.bios.version: A0.08
dmi.board.asset.tag: 2MD6080F88
dmi.board.name: 2B4B
dmi.board.vendor: HP
dmi.board.version: 1.04
dmi.chassis.asset.tag: 2MD6080F88
dmi.chassis.type: 3
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnAMI:bvrA0.08:bd11/12/2015:svnHP:pn750-170se:pvr1.04:rvnHP:rn2B4B:rvr1.04:cvnHP:ct3:cvr:
dmi.product.name: 750-170se
dmi.product.version: 1.04
dmi.sys.vendor: HP
mtime.conffile..etc.modprobe.d.alsa.base.conf: 2016-05-10T19:59:24.812836

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


** Tags: alsa alsa-driver amd64 apport-bug skip skipping skylake sound stutter 
stuttering trusty

** Description changed:

  My sound skips/stutters for about half a second (certainly no more than
  1 second) on average every 5-20 minutes. I initially had no sound on
  this computer with Ubuntu 14.04, which is probably because Ubuntu 14.04
  has an outdated version of Alsa. I then tested with a live disc of
  Ubuntu 16.04 (before official release date), which did give me sound. At
  this point, I installed the the 

[Touch-packages] [Bug 1578665] Re: no trust prompt appearing in clock or weather app after images on the 4th of may

[Launchpad Bug Tracker]

** Branch linked: lp:~dandrader/qtmir/surfaceDrawn

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

Title:
  no trust prompt appearing in clock or weather app after images on the
  4th of may

Status in Canonical System Image:
  In Progress
Status in trust-store:
  Invalid
Status in qtmir package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  STEPS:
  1. Bootstrap the latest rc-proposed
  2. Open clock app after a long start up time you will note that you were not 
asked 
  3. Open the weather app and see similar behaviour

  EXPECTED:
  All most instant popup for trust store to allow location access

  ACTUAL:
  A long delay before the app opens and then no trust prompt and no location 
detection.

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

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

[Touch-packages] [Bug 1580577] Re: python2.7 crashes with SegFault when running Zope

[Matthias Klose]

please report this upstream, or else you'll see that in 2.7.12 upstream.

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

Title:
  python2.7 crashes with SegFault when running Zope

Status in python2.7 package in Ubuntu:
  Confirmed

Bug description:
  Source package / Package:

  python2.7_2.7.11-7ubuntu1

  System:

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  
  This is a bug report originating from the findings documented in

  https://github.com/zopefoundation/Zope/issues/56

  
  The expected behaviour is this:
  - Upon installing Zope2 in a virtualenv a default instance should work with 
no issues.

  What happens instead:
  - The freshly installed Zope instance causes Python to SegFault after only a 
few requests.

  But Python should never SegFault.

  
  The following program produces the error:

  
  #!/bin/bash
  set -e

  # Call this testing script with an argument "setup" for the first time
  # to build the testing case
  #
  # After that, the script only performs the test as described below.
  #
  # Requirements: apt-get install virtualenv python2.7-dbg
  #
  # This script needs internet access when running.

  # The python version to test:
  python=/usr/bin/python2.7-dbg

  # This part builds the testing environment

  if [ "$1" == "setup" ] ; then
  # Virtual environment with the chosen python 
  virtualenv --python ${python} --no-site-packages zope-virtualenv
  cd zope-virtualenv
  # Basic Zope installation
  ./bin/easy_install -i http://download.zope.org/Zope2/index/2.13.24 Zope2
  # Simplest possible Zope instance
  ./bin/mkzopeinstance --dir instance --user admin:admin
  cd ..
  fi

  # THE TEST

  # Run Zope instance in the background
  zope-virtualenv/instance/bin/runzope &

  # Give Zope some time to start up
  sleep 3

  # Call a few management URLs, nothing too fancy...
  urls="
  http://admin:admin@localhost:8080/Control_Panel/manage_main
  http://admin:admin@localhost:8080/Control_Panel/Database/main/manage_main
  http://admin:admin@localhost:8080/Control_Panel/Database/manage_main
  http://admin:admin@localhost:8080/Control_Panel/Database/main/manage_activity
  http://admin:admin@localhost:8080/manage
  http://admin:admin@localhost:8080/acl_users/manage_main
  http://admin:admin@localhost:8080/acl_users/manage_access
  "

  while true ; do
  for url in ${urls} ; do 
echo ${url}
  curl -s $url -o /dev/null
  done
  done

  # This test fails after about 10 requests with
  # Fatal Python error: ../Objects/descrobject.c:10 object at 0x??? has 
negative ref count -1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1580577/+subscriptions

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

[Touch-packages] [Bug 1580700] Re: Add Let's Encrypt Authority to Package

[Mike Weiss]

The ca-certificates I have is "ca-certificates 20160104ubuntu0.12.04.1"

The issue exists with two versions of wget I've tried
wget 1.13.4-2ubuntu1.2 
and 
Wget 1.16.3 which I compiled myself

Although the error message is different for each, I believe its the same
issue.

Error with Wget 1.13.4:

"ERROR: no certificate subject alternative name matches
requested host name `www.x.org'.
To connect to www.x.org insecurely, use `--no-check-certificate'."

Error with Wget 1.16.3:
"ERROR: The certificate of 'www.x.org' is not trusted."

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

Title:
  Add Let's Encrypt Authority to Package

Status in ca-certificates package in Ubuntu:
  New
Status in wget package in Ubuntu:
  New

Bug description:
  Let's Encrypt Authority should be added to CA-certificates.
  https://www.X.org is now using a cert from this CA, wget fails when
  connecting to X.org.

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

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

[Touch-packages] [Bug 1501041] Re: No visible display in non gnome sessions when using nvidia drivers via nvidia-prime until screen goes to sleep, then waked up

[Brian Murray]

ubuntu-drivers-common only detects and helps to install driver packages,
it doesn't actually affect them.

** Changed in: ubuntu-drivers-common (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  No visible display in non gnome sessions when using nvidia drivers via
  nvidia-prime until screen goes to sleep, then waked up

Status in lightdm package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers package in Ubuntu:
  Invalid
Status in ubuntu-drivers-common package in Ubuntu:
  Invalid
Status in unity-greeter package in Ubuntu:
  Invalid
Status in xfce4-session package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  ** this appears to be that the display is blanked/asleep at greeter & login.
  Forcing or waiting for screen to blank/sleep then waking up restores display
  See comments 8 & 10 for further info, demonstrations **

  Please note that this bug is being filed on a recent 15.10 Ubuntu
  image install but from a gnome session

  In a nutshell -
  Once nividia drivers are installed & used from nvidia-prime there is no 
longer a visible display in unity-greeter nor in an ubuntu session once logged 
in. (a blind log in successfully loads an ubuntu session.
  Everything in the ubuntu session works fine, there are no errors & all the 
related logs look ok, there is just no visible display.

  I can open apps, run commands, copy/create logs, play music, play
  videos, just no display so has to be done blindly from keyboard.

  On the other hand if I install gnome-shell & log in (blindly) to a
  gnome session from greeter then all is well & I get a visible
  display.

  The same behaviour is seen on an Xubuntu image install, once nvidia is
  installed & switched to, no visible display. Again there installing &
  logging into a gnome session works fine with visible display

  nvidia driver version doesn't matter, exact same is seen with current
  15.10 versions & the one I'm currently using (355) from drivers ppa.

  ** this appears to be that the display is blanked/asleep at greeter & login.
  Forcing or waiting for screen to blank/sleep then waking up restores display
  See comment 8 for further info **

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg-core 2:1.17.2-1ubuntu7
  ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1
  Uname: Linux 4.2.0-11-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue Sep 29 16:15:21 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.2.0-11-generic, x86_64: installed
   nvidia-355, 355.11, 4.2.0-11-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:3801]
   NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2015-09-28 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150928)
  MachineType: LENOVO 20217
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-11-generic.efi.signed 
root=UUID=3712249e-a4c8-4b29-9ffb-f9f9e7d5259a ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 74CN44WW(V3.05)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: VIQY0Y1
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y510P
  dmi.modalias: 
dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P:
  dmi.product.name: 20217
  dmi.product.version: Lenovo IdeaPad Y510P
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+15.10.20150908-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  

[Touch-packages] [Bug 1527980] Re: package libxml2:i386 2.9.2+zdfsg1-4ubuntu0.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting confi

[Brian Murray]

This specific message generally occurs when the package is corrupt on
disk on in memory.  Have you tried manually reinstalling it via 'sudo
apt-get install --reinstall libxm2'?

** Changed in: libxml2 (Ubuntu)
   Importance: Critical => Medium

** Changed in: libxml2 (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  package libxml2:i386 2.9.2+zdfsg1-4ubuntu0.2 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in libxml2 package in Ubuntu:
  Incomplete

Bug description:
  continous crashes

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: libxml2:i386 2.9.2+zdfsg1-4ubuntu0.2
  ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6
  Uname: Linux 4.2.0-22-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: i386
  Date: Sun Dec 20 10:12:01 2015
  DuplicateSignature: package:libxml2:i386:2.9.2+zdfsg1-4ubuntu0.2:package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2012-05-05 (1323 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5.1
   apt  1.0.10.2ubuntu1
  SourcePackage: libxml2
  Title: package libxml2:i386 2.9.2+zdfsg1-4ubuntu0.2 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1301015] Re: Networking does not restart

[Gabriel Parrondo]

Seriously people, get over yourself. Here's what the init script did on
restart:

  ifdown -a --exclude=lo $verbose
  ifup -a --exclude=lo $exclusions $verbose && ifup_hotplug $exclusions $verbose

All the rest is message output, checking for /etc/network/options and
other boilerplate stuff. That's exactly the same suggestion feliperechia
made in #8 about 2 years ago.

"Oh, but he didn't mention ifup_hotplug or $exclusions yadda yadda"

Well, ifup_hotplug actually extracts a list of interfaces from the
output of `ifquery --list --allow=hotplug`, checks they're physical
interfaces and have physical link, and runs ifup for all of them.

I sincerely doubt any of the "oh I screwed up and now have to take a 4
hour flight to the datacenter" are hotplugging their network interfaces.
If your NIC is available on boot it should be set to 'auto' and will be
picked up by `ifup -a`. No need for ifup_hotplug on headless servers.


$exclusions is the EXCLUDE_INTERFACES parameter from /etc/default/networking. 
$verbose is either '-v' or empty. You probably don't use either.

So yeah, `( ifdown -a --exclude=lo; ifup -a --exclude=lo) &` should work
for everyone because that's exactly what `/etc/init.d/networking
restart` did.

Can we move along now? Thanks!

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

Title:
  Networking does not restart

Status in ifupdown package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu Server 14.04 it appears it is not possible to restart
  networking. This is fresh install from ISO.

  wirehive@ubuntu:~$ sudo /etc/init.d/networking restart
  wirehive@ubuntu:~$ echo $?
  1
  wirehive@ubuntu:~$ sudo service networking restart
  stop: Job failed while stopping
  start: Job is already running: networking
  wirehive@ubuntu:~$ sudo bash -x /etc/init.d/networking restart
  + PATH=/sbin:/bin
  + RUN_DIR=/run/network
  + IFSTATE=/run/network/ifstate
  + STATEDIR=/run/network/state
  + '[' -x /sbin/ifup ']'
  + '[' -x /sbin/ifdown ']'
  + . /lib/lsb/init-functions
  +++ run-parts --lsbsysinit --list /lib/lsb/init-functions.d
  ++ for hook in '$(run-parts --lsbsysinit --list /lib/lsb/init-functions.d 
2>/dev/null)'
  ++ '[' -r /lib/lsb/init-functions.d/20-left-info-blocks ']'
  ++ . /lib/lsb/init-functions.d/20-left-info-blocks
  ++ for hook in '$(run-parts --lsbsysinit --list /lib/lsb/init-functions.d 
2>/dev/null)'
  ++ '[' -r /lib/lsb/init-functions.d/50-ubuntu-logging ']'
  ++ . /lib/lsb/init-functions.d/50-ubuntu-logging
  +++ LOG_DAEMON_MSG=
  ++ FANCYTTY=
  ++ '[' -e /etc/lsb-base-logging.sh ']'
  ++ true
  + CONFIGURE_INTERFACES=yes
  + EXCLUDE_INTERFACES=
  + VERBOSE=no
  + '[' -f /etc/default/networking ']'
  + verbose=
  + '[' no = yes ']'
  + case "$1" in
  + init_is_upstart
  + '[' -x /sbin/initctl ']'
  + /bin/grep -q upstart
  + /sbin/initctl version
  + return 0
  + exit 1
  wirehive@ubuntu:~$ sudo bash -x service networking restart
  ++ basename service
  + VERSION='service ver. 0.91-ubuntu1'
  ++ basename service
  + USAGE='Usage: service < option > | --status-all | [ service_name [ command 
| --full-restart ] ]'
  + SERVICE=
  + ACTION=
  + SERVICEDIR=/etc/init.d
  + OPTIONS=
  + '[' 2 -eq 0 ']'
  + cd /
  + '[' 2 -gt 0 ']'
  + case "${1}" in
  + '[' -z '' -a 2 -eq 1 -a networking = --status-all ']'
  + '[' 2 -eq 2 -a restart = --full-restart ']'
  + '[' -z '' ']'
  + SERVICE=networking
  + shift
  + '[' 1 -gt 0 ']'
  + case "${1}" in
  + '[' -z networking -a 1 -eq 1 -a restart = --status-all ']'
  + '[' 1 -eq 2 -a '' = --full-restart ']'
  + '[' -z networking ']'
  + '[' -z '' ']'
  + ACTION=restart
  + shift
  + '[' 0 -gt 0 ']'
  + '[' -r /etc/init/networking.conf ']'
  + which initctl
  + grep -q upstart
  + initctl version
  + case "${ACTION}" in
  + stop networking
  stop: Job failed while stopping
  + :
  + exec start networking
  start: Job is already running: networking
  wirehive@ubuntu:~$

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

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

[Touch-packages] [Bug 1545212] Re: Evolution 3.18.4 package does not include translations

[nomentero]

Thanks venbea (juan-gamez) 
ya funcionando en Español

Saludos-Best regards

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

Title:
  Evolution 3.18.4 package does not include translations

Status in langpack-o-matic:
  Fix Released
Status in language-pack-fr-base package in Ubuntu:
  Fix Committed

Bug description:
  Hello,
  I upgraded to Xenial (I need to follow what happens during the last weeks 
before the release) and I notice Evolution 3.18.4 does come with the 
translations, when downloading the tarball upstream, however in my system it's 
still in English and I can't find the French mo in my system. How come the 
package for Ubuntu does not get the translation which is ready to go upstream? 
(I opened the mo in Poedit and could see the chains are all translated).
  https://download.gnome.org/sources/evolution/3.18/evolution-3.18.4.tar.xz

  Thanks for a fix!

  Best regards,
  Mélodie

To manage notifications about this bug go to:
https://bugs.launchpad.net/langpack-o-matic/+bug/1545212/+subscriptions

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

[Touch-packages] [Bug 1565236] Re: AltGr not working on external keyboards

[Andreas Pokorny]

Ok there is actually another problem here, the modifier information
provided to unity8 from usc indicates that alt is pressed even though
the currently consuming client interprets the scan code of right alt as
level 3 shift... So still a mir change is required.

** Changed in: mir
   Status: Invalid => In Progress

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

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

Title:
  AltGr not working on external keyboards

Status in Canonical System Image:
  Confirmed
Status in Mir:
  In Progress
Status in mir package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  New

Bug description:
  Using my keyboard with Spanish layout:

   - PC: Everything works perfect.
   - Ubuntu Touch: I can't write accented characters (dead acute, áéíóú).

  Extra info:

  - Keyboard: https://goo.gl/photos/xZUE8kRsReW1VKPA6 
(http://www.logitech.com/en-hk/product/wireless-touch-keyboard-k400r2)
  - Ubuntu Desktop: 12.04
  - Ubuntu Touch: bq Aquaris E4.5 15.04 (r305)

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

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

[Touch-packages] [Bug 1507957] Re: Huawei E3372 LTE modem on 15.10 works only when connecting via wvdial and not network-manager

[AzZiD]

I have a Huawei E3372 modem, and I'm also having some issues, even
though I found a way to connect.

At first the modem was not switching modes (stuck in 12d1:1f01), and
lsusb output was:

Bus 003 Device 039: ID 12d1:1f01 Huawei Technologies Co., Ltd.

At this point everytime I plugged the modem the blue led stayed on
(connected), but it wasn't recognized, and I couldn't use it or find it
in Network Manager whatsoever.

After looking around on the internet, I found this command to switch
modes which worked for me:

usb_modeswitch -J -v 0x12d1 -p 0x1f01

After issuing this command NetworkManager popup saying new ethernet
connection was available and I could connect. Still, the modem was not
recognized, but working. The output of lsusb was:

Bus 003 Device 039: ID 12d1:14dc Huawei Technologies Co., Ltd.

Playing around with usb_modeswitch found that switching to 0x1001 the
blue led started to blink instead of being always on, and after a few
seconds the modem was recognized, I tried to setup a broadband
connection but I couldn't connect. Now lsusb was printing:

Bus 003 Device 039: ID 12d1:155f Huawei Technologies Co., Ltd.

I'm attaching the system log since I plug the modem till connection
attempt finally times out.

I can use the modem, but not 'dialing' I would say.

Hope it helps, let me know if I can provide you with some more
information.

** Attachment added: "syslog modem detection"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1507957/+attachment/4660874/+files/syslog.txt

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

Title:
  Huawei E3372 LTE modem on 15.10 works only when connecting via wvdial
  and not network-manager

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  If you plug the modem first time after booting, it cannot connect.
  Hovewer, after you unplug it and plug it again, it works like a charm.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-30-generic 3.19.0-30.34
  ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  cysioland   2089 F pulseaudio
   /dev/snd/controlC0:  cysioland   2089 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Oct 20 11:28:10 2015
  HibernationDevice: RESUME=UUID=ed44c356-6a11-447b-94bc-88d54b0ead64
  InstallationDate: Installed on 2014-10-14 (370 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Acer Extensa 5635G
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic 
root=UUID=31750940-1f18-4f57-8933-4f779556f31b ro quiet splash 
libata.allow_tpm=1
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-30-generic N/A
   linux-backports-modules-3.19.0-30-generic  N/A
   linux-firmware 1.143.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-05-23 (149 days ago)
  dmi.bios.date: 12/21/2009
  dmi.bios.vendor: Phoenix
  dmi.bios.version: V1.3311
  dmi.board.name: BA50-MV
  dmi.board.vendor: Acer
  dmi.board.version: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenix:bvrV1.3311:bd12/21/2009:svnAcer:pnExtensa5635G:pvrNotApplicable:rvnAcer:rnBA50-MV:rvrNotApplicable:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5635G
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1574347] Automatically added comment

[Will Cooke]

Added to Trello: https://trello.com/c/LXqaTEnC/1-bug-1574347-wifi-
network-list-disappears-from-network-manager-applet

** Tags removed: desktop-trello-import

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

Title:
  WiFi network list disappears from network manager applet

Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Xenial:
  Confirmed

Bug description:
  Issue is in Ubuntu 16.04 LTS amd64 version.

  Steps to reproduce: -

  1. Connect to a WiFi AP.
  2. Switch off the AP OR switch off the wifi in the computer.
  3. Switch point (2) back on.
  4. The network will get connected to the AP it was connected to in point (1).

  Problems:-

  1. The network manager applet does not show the list of WiFI APs it can find.
  2. The network manager applet does not the name of the AP to which it is 
connected
  3. The icon of the applet shows two vertical arrows in opposite direction - 
the wired connection symbol and NOT the wifi connected icon.

  
  Temporary Workaround:-
  Log out and again log back in.

  Please solve this issue asap.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Apr 24 23:15:34 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-04-23 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.1.1 dev wlp18s0  proto static  metric 600 
   169.254.0.0/16 dev wlp18s0  scope link  metric 1000 
   192.168.1.0/24 dev wlp18s0  proto kernel  scope link  src 192.168.1.99  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  
AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH   
ACTIVE  DEVICE   STATE  ACTIVE-PATH
   Airtel-201  d263b201-9281-427e-94e2-762fa620813c  802-11-wireless  
1461519922  Sunday 24 April 2016 11:15:22 PM IST  yes  0
 no/org/freedesktop/NetworkManager/Settings/0  yes wlp18s0  
activated  /org/freedesktop/NetworkManager/ActiveConnection/8 
   Wired connection 1  142942d4-d247-4880-9bab-1eeafc29ca86  802-3-ethernet   
1461508904  Sunday 24 April 2016 08:11:44 PM IST  yes  4294966297   
 no/org/freedesktop/NetworkManager/Settings/2  no  --   --  
   --
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp18s0  wifi  connected/org/freedesktop/NetworkManager/Devices/1  
Airtel-201  d263b201-9281-427e-94e2-762fa620813c  
/org/freedesktop/NetworkManager/ActiveConnection/8 
   enp19s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1507957] Re: Huawei E3372 LTE modem on 15.10 works only when connecting via wvdial and not network-manager

[AzZiD]

BTW, I'm runnung 16.04

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

Title:
  Huawei E3372 LTE modem on 15.10 works only when connecting via wvdial
  and not network-manager

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  If you plug the modem first time after booting, it cannot connect.
  Hovewer, after you unplug it and plug it again, it works like a charm.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-30-generic 3.19.0-30.34
  ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  cysioland   2089 F pulseaudio
   /dev/snd/controlC0:  cysioland   2089 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Oct 20 11:28:10 2015
  HibernationDevice: RESUME=UUID=ed44c356-6a11-447b-94bc-88d54b0ead64
  InstallationDate: Installed on 2014-10-14 (370 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Acer Extensa 5635G
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic 
root=UUID=31750940-1f18-4f57-8933-4f779556f31b ro quiet splash 
libata.allow_tpm=1
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-30-generic N/A
   linux-backports-modules-3.19.0-30-generic  N/A
   linux-firmware 1.143.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-05-23 (149 days ago)
  dmi.bios.date: 12/21/2009
  dmi.bios.vendor: Phoenix
  dmi.bios.version: V1.3311
  dmi.board.name: BA50-MV
  dmi.board.vendor: Acer
  dmi.board.version: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenix:bvrV1.3311:bd12/21/2009:svnAcer:pnExtensa5635G:pvrNotApplicable:rvnAcer:rnBA50-MV:rvrNotApplicable:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5635G
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1580558] Re: Upgrade libseccomp from 2.2.3 ->2.3.1

[Frank Heimes]

** Changed in: ubuntu-z-systems
   Status: Triaged => Confirmed

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

Title:
  Upgrade libseccomp from 2.2.3 ->2.3.1

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in libseccomp package in Ubuntu:
  Confirmed

Bug description:
  == Comment: #1 - Heinz-Werner Seeck  - 
2016-05-11 05:09:09 ==
  Please upgrade package libseccomp.
  The new version 2.3.1 is available on github

  https://github.com/seccomp/libseccomp/releases

  == Comment: #2 - Heinz-Werner Seeck  - 
2016-05-11 05:10:59 ==
  ?Version 2.3.0 - February 29, 2016
  ?Added support for the s390 and s390x architectures
  ?Added support for the ppc, ppc64, and ppc64le architectures
  ?Update the internal syscall tables to match the Linux 4.5-rcX releases
  ?Filter generation for both multiplexed and direct socket syscalls on x86
  ?Support for the musl libc implementation
  ?Additions to the API to enable runtime version checking of the library
  ?Enable the use of seccomp() instead of prctl() on supported systems
  ?Added additional tests to the regression test suite

  ?Version 2.3.1 - April 20, 2016 
  ?Fixed a problem with 32-bit x86 socket syscalls on some systems
  ?Fixed problems with ipc syscalls on 32-bit x86
  ?Fixed problems with socket and ipc syscalls on s390 and s390x

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

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

[Touch-packages] [Bug 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04

[Sebastien Bacher]

thanks, the log looks fine, I don't see any hint about the problem
though and I'm out of idea for today, maybe pitti has some clue what
could be going on there...

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

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

Title:
  Notebook doesn't suspend when lid is closed after update to 16.04

Status in systemd package in Ubuntu:
  New

Bug description:
  My notebook does not suspend after upgrading from 15.10 to 16.04.

  According to system settings the notebook should suspend when lid is
  closed but actually this does not happen. Instead it continues to run
  as if nothing had happened.

  With the previous versions of ubuntu (14.04-15.10) everything worked
  fine.

  My System: HP Pavilion dv7.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: acpi (not installed)
  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: Sat Apr 23 23:11:15 2016
  InstallationDate: Installed on 2015-10-29 (176 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: acpi
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)

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

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

[Touch-packages] [Bug 211631] Re: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown)

[Max-Ulrich Farber]

Unfortunately, the bug seems to be back in Ubuntu 16.04 (Xenial) now,
probably due to changements in the boot and shutdown sequences. See also
[bug 1577885].

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

Title:
  Network is brought down before network filesystems are unmounted (CIFS
  timeout at shutdown)

Status in dbus package in Ubuntu:
  Fix Released
Status in dhcdbd package in Ubuntu:
  Invalid
Status in netbase package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in sysvinit package in Ubuntu:
  Invalid
Status in wpasupplicant package in Ubuntu:
  Fix Released
Status in dhcdbd source package in Lucid:
  Invalid
Status in dhcdbd source package in Natty:
  Invalid
Status in sysvinit package in Debian:
  New

Bug description:
  IMPORTANT: this bug has enough information; please don't post
  _anything_ unless a developer asks for specific feedback! By posting
  to this bug you only make it harder for a developer to spot the gem
  comments. Please use the "me too feature" of launchpad to signal that
  you are affected and would like to see this fixed.

  I installed smbfs,and then put some entries into /etc/fstab, so they 
automount on startup. An example of this is here:
  ///  /home/hamish/  cifs  
credentials=/home/hamish/.smbcredentials,file_mode=0777,dir_mode=0777,uid=1000,gid=1000
  0  0

  ** note the use of "cifs" in the lines above **

  (The username and password are in the .smbcredentials file)

  On startup, for each entry in the /etc/fstab file, I get the following in 
dmesg:
  [   70.495504]  CIFS VFS: Error connecting to IPv4 socket. Aborting operation
  [   70.495569]  CIFS VFS: cifs_mount failed w/return code = -101
  But the shares are mounted, and a nautilus session opens up (which is also 
annoying...)

  Also logging off with CIFS shares mounted in /etc/fstab, it sits with an 
error message:
  CIFS VFS: server not responding
  CIFS VFS: no response for cmd 50 mid 
  And takes about 2 minutes to timeout. This also happened with Gutsy

  Should the timing of the mounting and dismounting be changed so that
  it works? It is related to the starting of network-manager and CIFS
  shares trying to connect on startup *before* the network is up, and
  dismounting the shares *after* network-manager is stopped.

  Hamish

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

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

[Touch-packages] [Bug 1519499] Re: Shutdown failure: Assertion 'sd_id128_randomize() >= 0' failed at ../src/core/dbus.c:657, function bus_on_connection(). Aborting.

[Hans Deragon]

Looks like it is the same problem.

** Attachment added: "ubuntu-xenialxerus-16.04-journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1519499/+attachment/4660855/+files/ubuntu-xenialxerus-16.04-journal.txt

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

Title:
  Shutdown failure: Assertion 'sd_id128_randomize() >= 0' failed at
  ../src/core/dbus.c:657, function bus_on_connection(). Aborting.

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  This is a follow-up on this issue here:
  https://github.com/lxc/lxd/issues/1336 I cannot stop a LXD container
  gently and as it seems the issue lies within ubuntu/systemd which does
  not handle SIGPWR correctly.

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

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

[Touch-packages] [Bug 1576066] Re: 32bit glibc calls old socketcall() syscall, causing seccomp problems

[Launchpad Bug Tracker]

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

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

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

Title:
  32bit glibc calls old socketcall() syscall, causing seccomp problems

Status in glibc package in Ubuntu:
  Confirmed
Status in libseccomp package in Ubuntu:
  Confirmed

Bug description:
  Back in the day when Linux was created for i386, for who knows what
  reason, all socket calls were multiplexed through a single syscall
  API, socketcall().  This was a strange thing to do, but it probably
  made sense from the standpoint of the same part of the kernel handling
  all of those calls.

  It was realised a long time ago that this was a strange and suboptimal
  arrangement.

  By the time they got around to doing amd64 and other architectures,
  they fixed this arrangement and gave each socket call a separate
  syscall entry point.  32bit systems continued to do it this old way,
  however, multiplexing all calls through socketcall().

  This is a problem for seccomp.  If we want to allow a program to make
  casual use of the network, but not bind a listener socket, we cannot
  currently do that.  On 64bits we just filter out the bind() and
  listen() calls, but on 32bit, it's all the same syscall.

  The kernel people fixed this problem up last summer by introducing
  new, separate, syscall entries for each separate call.

http://patchwork.sourceware.org/patch/7679/

  The problem is that glibc in Y is still using the old socketcall()
  interface on i386.  It needs to be updated to use the new calls.

  A possible caveat is that this might create problems for running newer
  binaries on older kernels on i386 (as we sometimes do with builders)
  because they won't have the new syscalls.  A solution could involve
  checking for ENOSYS and trying again via the old route.

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

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

[Touch-packages] [Bug 1576066] Re: 32bit glibc calls old socketcall() syscall, causing seccomp problems

[Launchpad Bug Tracker]

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

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

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

Title:
  32bit glibc calls old socketcall() syscall, causing seccomp problems

Status in glibc package in Ubuntu:
  Confirmed
Status in libseccomp package in Ubuntu:
  Confirmed

Bug description:
  Back in the day when Linux was created for i386, for who knows what
  reason, all socket calls were multiplexed through a single syscall
  API, socketcall().  This was a strange thing to do, but it probably
  made sense from the standpoint of the same part of the kernel handling
  all of those calls.

  It was realised a long time ago that this was a strange and suboptimal
  arrangement.

  By the time they got around to doing amd64 and other architectures,
  they fixed this arrangement and gave each socket call a separate
  syscall entry point.  32bit systems continued to do it this old way,
  however, multiplexing all calls through socketcall().

  This is a problem for seccomp.  If we want to allow a program to make
  casual use of the network, but not bind a listener socket, we cannot
  currently do that.  On 64bits we just filter out the bind() and
  listen() calls, but on 32bit, it's all the same syscall.

  The kernel people fixed this problem up last summer by introducing
  new, separate, syscall entries for each separate call.

http://patchwork.sourceware.org/patch/7679/

  The problem is that glibc in Y is still using the old socketcall()
  interface on i386.  It needs to be updated to use the new calls.

  A possible caveat is that this might create problems for running newer
  binaries on older kernels on i386 (as we sometimes do with builders)
  because they won't have the new syscalls.  A solution could involve
  checking for ENOSYS and trying again via the old route.

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

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

[Touch-packages] [Bug 1579915] Re: network-manager 1.2 uses more power

[Tony Espy]

Two things I noticed while testing the powersave fix from silo-77:

1) On mako ( rc-proposed / 434 ), iwconfig doesn't report anything at
all for powersave.   This may be a driver limitation.

2) On frieza ( rc-proposed / 101 ), the powersave period is set to 0,
which may be a less than ideal value.  This should be investigated.

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

Title:
  network-manager 1.2 uses more power

Status in Canonical System Image:
  In Progress
Status in network-manager package in Ubuntu:
  In Progress

Bug description:
  On krillin and arale, power use went up significantly in new builds starting 
on May 4.  So far, I have results for:
  * krillin rc-proposed 324 and 325
  * arale rc-proposed 316 and 317

  When the radios are off, results are unchanged.  However, power went up in 
two common cases -- standby with all radios enabled, and screen-on with radios 
enabled.
  * krillin standby: ~8mA -> ~80mA
  * arale standby: ~35mA -> ~79mA
  * krillin screen-on: ~177mA -> ~215mA
  * arale screen-on: ~305mA -> ~353mA

  Quite a few things landed in that build, but some of the top suspects are:
  * network-manager got updated to 1.2
  * indicator-network got a cell data switch
  * USS got "fixes to sleep/idle settings"
  * ubuntu-push got a fix related to network-manager
  * libhybris got partial support for wireless display
  * account-polld got a new calendar plugin

  Full list:
  
http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/bq-aquaris.en/krillin/324.commitlog
  
http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/meizu.en/arale/316.commitlog

  This change cuts typical standby time anywhere from 50% to 90%, so it
  probably should be fixed before release.  However, tests suggest that
  simply turning off wifi returns the phone to a nice low standby power
  -- about 6mA for both devices.

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

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

[Touch-packages] [Bug 1575282] Re: NetworkManager applet (nm-applet) disappears after upgrading to xenial

[rmillet]

It seems it was fixed upstream:
https://bugzilla.gnome.org/show_bug.cgi?id=764502

** Bug watch added: GNOME Bug Tracker #764502
   https://bugzilla.gnome.org/show_bug.cgi?id=764502

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

Title:
  NetworkManager applet (nm-applet) disappears after upgrading to xenial

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from Ubuntu wily (15.10) to xenial (16.04, LTS), the 
NetworkManager control applet (nm-applet) ceased to show up.
  While running wily and even prior, I had modified /proc's "hidepid" argument 
to be 2, in accordance with hardening best practices in order to only allow 
users to see their own processes. Nm-applet was working just fine.

  Based on this Debian bug (https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=819808), I changed hidepid back to 0 (the
  default, which lets users see everyone's processes) and it's working
  again.

  Given that nm-applet was working just fine in wily and upgrading to
  xenial broke it, it seems like a regression.

  Wily version of network-manager: 1.0.4-0ubuntu5
  Xenial version: 1.1.93-0ubuntu4

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

  $ apt-cache policy network-manager
  network-manager:
Installed: 1.1.93-0ubuntu4
Candidate: 1.1.93-0ubuntu4
Version table:
   *** 1.1.93-0ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1580558] Re: Upgrade libseccomp from 2.2.3 ->2.3.1

[Launchpad Bug Tracker]

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

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

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

Title:
  Upgrade libseccomp from 2.2.3 ->2.3.1

Status in Ubuntu on IBM z Systems:
  Triaged
Status in libseccomp package in Ubuntu:
  Confirmed

Bug description:
  == Comment: #1 - Heinz-Werner Seeck  - 
2016-05-11 05:09:09 ==
  Please upgrade package libseccomp.
  The new version 2.3.1 is available on github

  https://github.com/seccomp/libseccomp/releases

  == Comment: #2 - Heinz-Werner Seeck  - 
2016-05-11 05:10:59 ==
  ?Version 2.3.0 - February 29, 2016
  ?Added support for the s390 and s390x architectures
  ?Added support for the ppc, ppc64, and ppc64le architectures
  ?Update the internal syscall tables to match the Linux 4.5-rcX releases
  ?Filter generation for both multiplexed and direct socket syscalls on x86
  ?Support for the musl libc implementation
  ?Additions to the API to enable runtime version checking of the library
  ?Enable the use of seccomp() instead of prctl() on supported systems
  ?Added additional tests to the regression test suite

  ?Version 2.3.1 - April 20, 2016 
  ?Fixed a problem with 32-bit x86 socket syscalls on some systems
  ?Fixed problems with ipc syscalls on 32-bit x86
  ?Fixed problems with socket and ipc syscalls on s390 and s390x

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

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

[Touch-packages] [Bug 1527374] Re: CVE-2015-8709

[Steve Beattie]

** Description changed:

  ** DISPUTED ** kernel/ptrace.c in the Linux kernel through 4.4.1
  mishandles uid and gid mappings, which allows local users to gain
  privileges by establishing a user namespace, waiting for a root process
  to enter that namespace with an unsafe uid or gid, and then using the
  ptrace system call.  NOTE: the vendor states "there is no kernel bug
  here."
+ 
+ Break-Fix: - local-2015-8709

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

Title:
  CVE-2015-8709

Status in linux package in Ubuntu:
  Fix Released
Status in linux-armadaxp package in Ubuntu:
  Confirmed
Status in linux-flo package in Ubuntu:
  Confirmed
Status in linux-goldfish package in Ubuntu:
  Confirmed
Status in linux-lts-quantal package in Ubuntu:
  Won't Fix
Status in linux-lts-raring package in Ubuntu:
  Won't Fix
Status in linux-lts-saucy package in Ubuntu:
  Won't Fix
Status in linux-lts-utopic package in Ubuntu:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Fix Released
Status in linux-lts-wily package in Ubuntu:
  Fix Released
Status in linux-lts-xenial package in Ubuntu:
  New
Status in linux-mako package in Ubuntu:
  Confirmed
Status in linux-manta package in Ubuntu:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Fix Released
Status in linux-snapdragon package in Ubuntu:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Confirmed
Status in lxc package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Wily:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  ** DISPUTED ** kernel/ptrace.c in the Linux kernel through 4.4.1
  mishandles uid and gid mappings, which allows local users to gain
  privileges by establishing a user namespace, waiting for a root
  process to enter that namespace with an unsafe uid or gid, and then
  using the ptrace system call.  NOTE: the vendor states "there is no
  kernel bug here."

  Break-Fix: - local-2015-8709

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

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

[Touch-packages] [Bug 1575282] Re: NetworkManager applet (nm-applet) disappears after upgrading to xenial

[Launchpad Bug Tracker]

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

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

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

Title:
  NetworkManager applet (nm-applet) disappears after upgrading to xenial

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from Ubuntu wily (15.10) to xenial (16.04, LTS), the 
NetworkManager control applet (nm-applet) ceased to show up.
  While running wily and even prior, I had modified /proc's "hidepid" argument 
to be 2, in accordance with hardening best practices in order to only allow 
users to see their own processes. Nm-applet was working just fine.

  Based on this Debian bug (https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=819808), I changed hidepid back to 0 (the
  default, which lets users see everyone's processes) and it's working
  again.

  Given that nm-applet was working just fine in wily and upgrading to
  xenial broke it, it seems like a regression.

  Wily version of network-manager: 1.0.4-0ubuntu5
  Xenial version: 1.1.93-0ubuntu4

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

  $ apt-cache policy network-manager
  network-manager:
Installed: 1.1.93-0ubuntu4
Candidate: 1.1.93-0ubuntu4
Version table:
   *** 1.1.93-0ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1574347] Re: WiFi network list disappears from network manager applet

[Will Cooke]

** Tags added: desktop-trello-import

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

Title:
  WiFi network list disappears from network manager applet

Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Xenial:
  Confirmed

Bug description:
  Issue is in Ubuntu 16.04 LTS amd64 version.

  Steps to reproduce: -

  1. Connect to a WiFi AP.
  2. Switch off the AP OR switch off the wifi in the computer.
  3. Switch point (2) back on.
  4. The network will get connected to the AP it was connected to in point (1).

  Problems:-

  1. The network manager applet does not show the list of WiFI APs it can find.
  2. The network manager applet does not the name of the AP to which it is 
connected
  3. The icon of the applet shows two vertical arrows in opposite direction - 
the wired connection symbol and NOT the wifi connected icon.

  
  Temporary Workaround:-
  Log out and again log back in.

  Please solve this issue asap.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Apr 24 23:15:34 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-04-23 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.1.1 dev wlp18s0  proto static  metric 600 
   169.254.0.0/16 dev wlp18s0  scope link  metric 1000 
   192.168.1.0/24 dev wlp18s0  proto kernel  scope link  src 192.168.1.99  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  
AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH   
ACTIVE  DEVICE   STATE  ACTIVE-PATH
   Airtel-201  d263b201-9281-427e-94e2-762fa620813c  802-11-wireless  
1461519922  Sunday 24 April 2016 11:15:22 PM IST  yes  0
 no/org/freedesktop/NetworkManager/Settings/0  yes wlp18s0  
activated  /org/freedesktop/NetworkManager/ActiveConnection/8 
   Wired connection 1  142942d4-d247-4880-9bab-1eeafc29ca86  802-3-ethernet   
1461508904  Sunday 24 April 2016 08:11:44 PM IST  yes  4294966297   
 no/org/freedesktop/NetworkManager/Settings/2  no  --   --  
   --
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp18s0  wifi  connected/org/freedesktop/NetworkManager/Devices/1  
Airtel-201  d263b201-9281-427e-94e2-762fa620813c  
/org/freedesktop/NetworkManager/ActiveConnection/8 
   enp19s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1577735] Re: Add missing SKL/BXT PCI-ID's

[Adam Conrad]

Hello Timo, or anyone else affected,

Accepted libdrm into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libdrm/2.4.67-1ubuntu0.14.04.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: libdrm (Ubuntu Trusty)
   Status: New => Fix Committed

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

Title:
  Add missing SKL/BXT PCI-ID's

Status in libdrm package in Ubuntu:
  Fix Released
Status in libdrm source package in Trusty:
  Fix Committed
Status in libdrm source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  Some Skylake/Broxton GPU PCI-ID's are missing from libdrm, these need
  to be added.

  [Test case]

  own such hw, run a desktop session and check that it's using native
  drivers

  [Regression potential]

  none

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

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

[Touch-packages] [Bug 1574347] Re: WiFi network list disappears from network manager applet

[Launchpad Bug Tracker]

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

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

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

Title:
  WiFi network list disappears from network manager applet

Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Xenial:
  Confirmed

Bug description:
  Issue is in Ubuntu 16.04 LTS amd64 version.

  Steps to reproduce: -

  1. Connect to a WiFi AP.
  2. Switch off the AP OR switch off the wifi in the computer.
  3. Switch point (2) back on.
  4. The network will get connected to the AP it was connected to in point (1).

  Problems:-

  1. The network manager applet does not show the list of WiFI APs it can find.
  2. The network manager applet does not the name of the AP to which it is 
connected
  3. The icon of the applet shows two vertical arrows in opposite direction - 
the wired connection symbol and NOT the wifi connected icon.

  
  Temporary Workaround:-
  Log out and again log back in.

  Please solve this issue asap.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Apr 24 23:15:34 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-04-23 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.1.1 dev wlp18s0  proto static  metric 600 
   169.254.0.0/16 dev wlp18s0  scope link  metric 1000 
   192.168.1.0/24 dev wlp18s0  proto kernel  scope link  src 192.168.1.99  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  
AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH   
ACTIVE  DEVICE   STATE  ACTIVE-PATH
   Airtel-201  d263b201-9281-427e-94e2-762fa620813c  802-11-wireless  
1461519922  Sunday 24 April 2016 11:15:22 PM IST  yes  0
 no/org/freedesktop/NetworkManager/Settings/0  yes wlp18s0  
activated  /org/freedesktop/NetworkManager/ActiveConnection/8 
   Wired connection 1  142942d4-d247-4880-9bab-1eeafc29ca86  802-3-ethernet   
1461508904  Sunday 24 April 2016 08:11:44 PM IST  yes  4294966297   
 no/org/freedesktop/NetworkManager/Settings/2  no  --   --  
   --
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp18s0  wifi  connected/org/freedesktop/NetworkManager/Devices/1  
Airtel-201  d263b201-9281-427e-94e2-762fa620813c  
/org/freedesktop/NetworkManager/ActiveConnection/8 
   enp19s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1578007] Re: apt in yakkety no longer creates partial

[Launchpad Bug Tracker]

This bug was fixed in the package snapcraft - 2.8.8+16.10

---
snapcraft (2.8.8+16.10) yakkety; urgency=medium

  * Create the 'partial' directory for apt. (#499) (LP: #1578007)

 -- Sergio Schvezov   Wed, 04 May 2016
14:22:58 -0300

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

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

Title:
  apt in yakkety no longer creates partial

Status in Snapcraft:
  In Progress
Status in apt package in Ubuntu:
  New
Status in snapcraft package in Ubuntu:
  Fix Released
Status in snapcraft source package in Xenial:
  New

Bug description:
  This now fails: http://paste.ubuntu.com/16208927/
  With an error that looks like http://paste.ubuntu.com/16208917/

  If 'partial' is created in `downloaddir` then it works again

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

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

[Touch-packages] [Bug 1565236] Re: AltGr not working on external keyboards

[Andreas Pokorny]

Those input scenarios work when unity8 is not used as mirserver.

The right alt scan code does not reach the client. Unity8 seems to
filter out the key press. In some occasions it seems to be sent at a
later timer. Long holding of right alt and then pressing sometimes help.

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

** Changed in: mir
   Status: Confirmed => Invalid

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

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

Title:
  AltGr not working on external keyboards

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  New

Bug description:
  Using my keyboard with Spanish layout:

   - PC: Everything works perfect.
   - Ubuntu Touch: I can't write accented characters (dead acute, áéíóú).

  Extra info:

  - Keyboard: https://goo.gl/photos/xZUE8kRsReW1VKPA6 
(http://www.logitech.com/en-hk/product/wireless-touch-keyboard-k400r2)
  - Ubuntu Desktop: 12.04
  - Ubuntu Touch: bq Aquaris E4.5 15.04 (r305)

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

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

[Touch-packages] [Bug 1578665] Re: no trust prompt appearing in clock or weather app after images on the 4th of may

[Pat McGowan]

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

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

Title:
  no trust prompt appearing in clock or weather app after images on the
  4th of may

Status in Canonical System Image:
  In Progress
Status in trust-store:
  Invalid
Status in qtmir package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  STEPS:
  1. Bootstrap the latest rc-proposed
  2. Open clock app after a long start up time you will note that you were not 
asked 
  3. Open the weather app and see similar behaviour

  EXPECTED:
  All most instant popup for trust store to allow location access

  ACTUAL:
  A long delay before the app opens and then no trust prompt and no location 
detection.

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

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

[Touch-packages] [Bug 1546457] Re: libc6 2.15-0ubuntu10.13 doesn't mark reboot-required

[Steve Beattie]

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

** Also affects: eglibc (Ubuntu Precise)
   Importance: Undecided
   Status: New

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

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

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

** Also affects: eglibc (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Changed in: eglibc (Ubuntu Wily)
   Status: New => Invalid

** Changed in: glibc (Ubuntu Precise)
   Status: New => Invalid

** Changed in: glibc (Ubuntu Trusty)
   Status: New => Invalid

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

Title:
  libc6 2.15-0ubuntu10.13 doesn't mark reboot-required

Status in eglibc package in Ubuntu:
  Fix Committed
Status in glibc package in Ubuntu:
  Fix Released
Status in eglibc source package in Precise:
  New
Status in glibc source package in Precise:
  Invalid
Status in eglibc source package in Trusty:
  New
Status in glibc source package in Trusty:
  Invalid
Status in eglibc source package in Wily:
  Invalid
Status in glibc source package in Wily:
  New

Bug description:
  2.15-0ubunt10.13 on ubuntu 12.04 was installed last night as a result
  of http://www.ubuntu.com/usn/usn-2900-1/ and unattended-upgrades

  However we are not getting a reboot-required file in /var/run/reboot-
  required.

  We are doing reboots by hand, but we believe this should be fixed.
  I'll have a look at the packaging to see why this didn't happen.

  Thanks for any help,

Will Pearson

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

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

[Touch-packages] [Bug 1572112] Re: Sync maintenance release lcms2 2.7-1 (main) from Debian testing (main)

[Michael Terry]

I think you mean merge, not sync here.  Debian/upstream don't use our
byte-order patch.  But I'll work on a merge for yakkety.

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

Title:
  Sync maintenance release lcms2 2.7-1 (main) from Debian testing (main)

Status in lcms2 package in Ubuntu:
  New

Bug description:
  Please Merge lcms2 2.7-1 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta:
    * No change rebuild to get debug symbols on all architectures.
    * Merge with Debian, remaining change:
  - debian/patches/byte-order.patch: Use endian.h to determine byte order 
in use.
  

  https://github.com/mm2/Little-CMS/blob/master/ChangeLog

  Fixed a possible segmentation fault in a non-happy path
  Fixed a macro clash on SNONE.
  Added a safety check on named color lists
  Added a function to retrieve the iohandler of a given profile object
  Remove unused vcproj files
  Some maintenance fixes
  utils/jpgicc/iccjpeg.c: Fix check if unsigned variable 'total_length'… …
  Add missing comma in CGATS parser
  Remove dead code.
  Move unused var suppresor before the `return` statements.
  Added a flag to clip negative values in unbounded transforms (only gray, rgb, 
cmyk)
  Added a global optimization that merges consecutive matrices in pipelines. 
Fixes loss of precision in some transforms
  New project for mac
  Added license for iccjpeg.c
  Added a project for VS2013
  Fixed wrong handling of extra channels in some formatters.
  Added an option in transicc for working in bounded mode
  Added a version retrieval function
  

  Changelog entries since current xenial version 2.6-3ubuntu2:

  lcms2 (2.7-1) unstable; urgency=medium

    * Imported Upstream version 2.7 (Closes: 819718)
    * No longer ship own copy of documentation source files
    * Removed patches (applied upstream)
  + update-manpages.patch
  + sanity-check-profiles-CVE-2014-0459.patch
  + endianness-verification-fix-powerpc.patch
    * Move to automatic dbgsym packages
    * Use secure URLs for Version Control System repository
    * Bump Standards version to 3.9.7, no changes needed
    * New patch: dont-write-uninitialized-memory-for-color-strings.patch
  Thanks to Jérémy Bobbio  (Closes: 815248)
    * Update maintainers field (Closes: 820138)

   -- Thomas Weber   Mon, 18 Apr 2016 15:53:10 +0200

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

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

[Touch-packages] [Bug 1580713] [NEW] package libjpeg8 8c-2ubuntu8 [modified: usr/share/doc/libjpeg8/changelog.Debian.gz usr/share/doc/libjpeg8/copyright] failed to install/upgrade: trying to overwrite

[Abir M Hadi]

Public bug reported:

Errors were encountered while processing:
 /var/cache/apt/archives/libjpeg8_8c-2ubuntu8_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libjpeg8 8c-2ubuntu8 [modified: 
usr/share/doc/libjpeg8/changelog.Debian.gz usr/share/doc/libjpeg8/copyright]
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
Date: Wed May 11 23:29:05 2016
Dependencies:
 gcc-6-base 6.1.1-1 [origin: Kali]
 libc6 2.23-0ubuntu3
 libgcc1 1:6.1.1-1 [origin: Kali]
 libjpeg-turbo8 1.4.2-0ubuntu3
 multiarch-support 2.23-0ubuntu3
ErrorMessage: trying to overwrite shared '/usr/share/doc/libjpeg8/copyright', 
which is different from other instances of package libjpeg8:i386
InstallationDate: Installed on 2016-05-02 (9 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.2.10ubuntu1
SourcePackage: libjpeg8-empty
Title: package libjpeg8 8c-2ubuntu8 [modified: 
usr/share/doc/libjpeg8/changelog.Debian.gz usr/share/doc/libjpeg8/copyright] 
failed to install/upgrade: trying to overwrite shared 
'/usr/share/doc/libjpeg8/copyright', which is different from other instances of 
package libjpeg8:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: libjpeg8-empty (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  package libjpeg8 8c-2ubuntu8 [modified:
  usr/share/doc/libjpeg8/changelog.Debian.gz
  usr/share/doc/libjpeg8/copyright] failed to install/upgrade: trying to
  overwrite shared '/usr/share/doc/libjpeg8/copyright', which is
  different from other instances of package libjpeg8:i386

Status in libjpeg8-empty package in Ubuntu:
  New

Bug description:
  Errors were encountered while processing:
   /var/cache/apt/archives/libjpeg8_8c-2ubuntu8_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libjpeg8 8c-2ubuntu8 [modified: 
usr/share/doc/libjpeg8/changelog.Debian.gz usr/share/doc/libjpeg8/copyright]
  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
  Date: Wed May 11 23:29:05 2016
  Dependencies:
   gcc-6-base 6.1.1-1 [origin: Kali]
   libc6 2.23-0ubuntu3
   libgcc1 1:6.1.1-1 [origin: Kali]
   libjpeg-turbo8 1.4.2-0ubuntu3
   multiarch-support 2.23-0ubuntu3
  ErrorMessage: trying to overwrite shared '/usr/share/doc/libjpeg8/copyright', 
which is different from other instances of package libjpeg8:i386
  InstallationDate: Installed on 2016-05-02 (9 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: libjpeg8-empty
  Title: package libjpeg8 8c-2ubuntu8 [modified: 
usr/share/doc/libjpeg8/changelog.Debian.gz usr/share/doc/libjpeg8/copyright] 
failed to install/upgrade: trying to overwrite shared 
'/usr/share/doc/libjpeg8/copyright', which is different from other instances of 
package libjpeg8:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1580188] Re: screen colors decays after wake up

[Umut Özdemir]

My problem is solved now. I updated the system and there is no problem
now. Thanks.

** Changed in: xorg (Ubuntu)
 Assignee: (unassigned) => Umut Özdemir (exclipit)

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

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

Title:
  screen colors decays after wake up

Status in xorg package in Ubuntu:
  Fix Released

Bug description:
  I'm using an Ubuntu 16.04 LTS. I tried to suspend the computer. Then I
  tried to wake it up. But colors were fully decayed after waking up. I
  can use computer while these colors, I can save my programs and close.
  To get colors back, I have to reboot.

  I added my screen's photo to show you how my screen were looking.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue May 10 16:30:16 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.16, 4.4.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670] [1043:0443]
  InstallationDate: Installed on 2016-05-08 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=96e24bd9-2666-45cc-b21f-7db94259d4c7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2601
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2601:bd03/24/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  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: Tue May 10 16:24:42 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   input USB OPTICAL MOUSE   MOUSE, id 8
   inputEee PC WMI hotkeys   KEYBOARD, id 9
   inputAT Translated Set 2 keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1519499] Re: Shutdown failure: Assertion 'sd_id128_randomize() >= 0' failed at ../src/core/dbus.c:657, function bus_on_connection(). Aborting.

[Sven R. Kunze]

@Hans

To confirm that it's the same issue, you might replay the instructions
Martin gave at #12:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1519499/comments/12

It should reveal the triggered assertion.

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

Title:
  Shutdown failure: Assertion 'sd_id128_randomize() >= 0' failed at
  ../src/core/dbus.c:657, function bus_on_connection(). Aborting.

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  This is a follow-up on this issue here:
  https://github.com/lxc/lxd/issues/1336 I cannot stop a LXD container
  gently and as it seems the issue lies within ubuntu/systemd which does
  not handle SIGPWR correctly.

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

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