date:20160511

the issue seems an upower on, reported upstream on
https://bugs.freedesktop.org/show_bug.cgi?id=95350 with a simple
testcase

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

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

Title:
  unity-settings-daemon crashed with SIGSEGV in
  up_exported_daemon_get_lid_is_closed()

Status in unity-settings-daemon package in Ubuntu:
  Triaged
Status in upower package in Ubuntu:
  Confirmed
Status in unity-settings-daemon source package in Xenial:
  Triaged
Status in upower source package in Xenial:
  Confirmed
Status in unity-settings-daemon source package in Yakkety:
  Triaged
Status in upower source package in Yakkety:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/8ca9c548fc4e2fc1d4bf827bbd85c72df59313f8

  Ubuntu 16.04 crashes immediately on login. Default settings not
  applied and appearance is a bit ugly (incorrect font hinting, in-
  window menus etc).

  ---

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Feb 17 13:52:13 2016
  ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
  InstallationDate: Installed on 2016-02-08 (8 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
  ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x3aae60fe69 : 
mov(%rbx),%rdi
   PC (0x3aae60fe69) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity-settings-daemon
  StacktraceTop:
   up_exported_daemon_get_lid_is_closed () from 
/usr/lib/x86_64-linux-gnu/libupower-glib.so.3
   gsd_power_manager_start () from 
/usr/lib/unity-settings-daemon-1.0/libpower.so
   ?? () from /usr/lib/unity-settings-daemon-1.0/libpower.so
   gnome_settings_plugin_info_activate ()
   ?? ()
  Title: unity-settings-daemon crashed with SIGSEGV in 
up_exported_daemon_get_lid_is_closed()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 565592] Re: pdf is slow to load while processing images

2016-05-11 Thread Gemini

how to resolve cpu loading high(almost 98%) when render a pdf page at
platform am3354 by poppler

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

Title:
  pdf is slow to load while processing images

Status in Poppler:
  Confirmed
Status in poppler package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: evince

  When using the mouse to navigate through PDFs, it works great. But
  PgUp and PgDn sometimes doesn't work at all for some PDFs.

  The PDF causing the problem was attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: evince 2.30.0-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-21-generic i686
  Architecture: i386
  Date: Sat Apr 17 16:39:49 2010
  ExecutablePath: /usr/bin/evince
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100406.1)
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince

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

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

[Touch-packages] [Bug 1580509] [NEW] old kernels block distribution upgrade

2016-05-11 Thread Michael

Public bug reported:

When trying to upgrade from 15.10 to 16.04 the upgrade process stops 
complaining about too little diskspace. The hint to run 'aptitude clean' does 
not help, because the diskspace is blocked by several old kernels which are not 
affected by the cleanup.
At least the hint should be extended to give an unexperienced user a chance to 
run the update without help of a more experienced user.

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

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

Title:
  old kernels block distribution upgrade

Status in apt package in Ubuntu:
  New

Bug description:
  When trying to upgrade from 15.10 to 16.04 the upgrade process stops 
complaining about too little diskspace. The hint to run 'aptitude clean' does 
not help, because the diskspace is blocked by several old kernels which are not 
affected by the cleanup.
  At least the hint should be extended to give an unexperienced user a chance 
to run the update without help of a more experienced user.

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

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

[Touch-packages] [Bug 1565763] Re: Unity8 scopes squeezed on Qt 5.6

2016-05-11 Thread Gerry Boland

** Branch linked: lp:~aacid/unity8/lvwph_qt56_fix

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

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

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Albert Astals Cid (aacid)

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

Title:
  Unity8 scopes squeezed on Qt 5.6

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  See attached screenshot. One can scroll it up/down and it stays like
  that. Seems to be just Unity 8 though, applications look normal.

  More information about Qt 5.6 at
  https://wiki.ubuntu.com/Touch/QtTesting

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

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

[Touch-packages] [Bug 1579825] Re: IP Address not displayed for wifi access points

2016-05-11 Thread Jean-Baptiste Lallement

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

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

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

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

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

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

Title:
  IP Address not displayed for wifi access points

Status in Canonical System Image:
  In Progress
Status in indicator-network package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  latest rc-proposed build 319

  Open system settings
  expand the connected access point by pressing right arrow

  expected results:
  ip address is displayed

  actual results:
  ip address is not displayed, just a label "IP Address" with no value

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

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

[Touch-packages] [Bug 1546641] Re: unity-settings-daemon crashed with SIGSEGV in up_exported_daemon_get_lid_is_closed()

https://wiki.ubuntu.com/Kernel/Bugs has details on how to file kernel
bugs with useful details

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

Title:
  unity-settings-daemon crashed with SIGSEGV in
  up_exported_daemon_get_lid_is_closed()

Status in unity-settings-daemon package in Ubuntu:
  Triaged
Status in upower package in Ubuntu:
  Confirmed
Status in unity-settings-daemon source package in Xenial:
  Triaged
Status in upower source package in Xenial:
  Confirmed
Status in unity-settings-daemon source package in Yakkety:
  Triaged
Status in upower source package in Yakkety:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/8ca9c548fc4e2fc1d4bf827bbd85c72df59313f8

  Ubuntu 16.04 crashes immediately on login. Default settings not
  applied and appearance is a bit ugly (incorrect font hinting, in-
  window menus etc).

  ---

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Feb 17 13:52:13 2016
  ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
  InstallationDate: Installed on 2016-02-08 (8 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
  ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x3aae60fe69 : 
mov(%rbx),%rdi
   PC (0x3aae60fe69) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity-settings-daemon
  StacktraceTop:
   up_exported_daemon_get_lid_is_closed () from 
/usr/lib/x86_64-linux-gnu/libupower-glib.so.3
   gsd_power_manager_start () from 
/usr/lib/unity-settings-daemon-1.0/libpower.so
   ?? () from /usr/lib/unity-settings-daemon-1.0/libpower.so
   gnome_settings_plugin_info_activate ()
   ?? ()
  Title: unity-settings-daemon crashed with SIGSEGV in 
up_exported_daemon_get_lid_is_closed()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1546641] Re: unity-settings-daemon crashed with SIGSEGV in up_exported_daemon_get_lid_is_closed()

Those having slow system start/usb enumeration issues should report a
kernel bug as well, fixing upower is going to resolve the segfault but
not the kernel

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

Title:
  unity-settings-daemon crashed with SIGSEGV in
  up_exported_daemon_get_lid_is_closed()

Status in unity-settings-daemon package in Ubuntu:
  Triaged
Status in upower package in Ubuntu:
  Confirmed
Status in unity-settings-daemon source package in Xenial:
  Triaged
Status in upower source package in Xenial:
  Confirmed
Status in unity-settings-daemon source package in Yakkety:
  Triaged
Status in upower source package in Yakkety:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/8ca9c548fc4e2fc1d4bf827bbd85c72df59313f8

  Ubuntu 16.04 crashes immediately on login. Default settings not
  applied and appearance is a bit ugly (incorrect font hinting, in-
  window menus etc).

  ---

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Feb 17 13:52:13 2016
  ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
  InstallationDate: Installed on 2016-02-08 (8 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
  ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x3aae60fe69 : 
mov(%rbx),%rdi
   PC (0x3aae60fe69) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity-settings-daemon
  StacktraceTop:
   up_exported_daemon_get_lid_is_closed () from 
/usr/lib/x86_64-linux-gnu/libupower-glib.so.3
   gsd_power_manager_start () from 
/usr/lib/unity-settings-daemon-1.0/libpower.so
   ?? () from /usr/lib/unity-settings-daemon-1.0/libpower.so
   gnome_settings_plugin_info_activate ()
   ?? ()
  Title: unity-settings-daemon crashed with SIGSEGV in 
up_exported_daemon_get_lid_is_closed()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1579949] Re: add_gdb_info hides OSErrors when running gdb during retracing

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

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

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

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

Title:
  add_gdb_info hides OSErrors when running gdb during retracing

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Committed

Bug description:
  I've been trying to debug an issue with apport trunk and retracing
  crashes from Xenial.  Come to find out I was receiving an OSError when
  running gdb (see bug 1579897) but didn't know it because of this code
  in report.py's add_gdb_info.

   721 # call gdb
   722 try:
   723 out = _command_output(gdb_cmd).decode('UTF-8', 
errors='replace')
   724 except OSError:
   725 return

  If _command_output tries to raise an OSError, it seems to me like we
  shouldn't just return in line 725.

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

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

[Touch-packages] [Bug 1579897] Re: report's _command_output function doesn't always return the error

Reproduced with "sudo dpkg --force-all -P libbabeltrace1" which breaks
gdb (but keeps python3.5 intact).

Fixed in http://bazaar.launchpad.net/~apport-
hackers/apport/trunk/revision/3079

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

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

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

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

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

Title:
  report's _command_output function doesn't always return the error

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Committed

Bug description:
  Apparently, the following gdb command fails but the error output is
  not in subprocess's err output but in stdout.

  > 
/srv/daisy.staging.ubuntu.com/staging/apport-2984/apport/report.py(104)_command_output()
  -> if sp.returncode == 0:
  (Pdb) l
   99 '''
  100 sp = subprocess.Popen(command, stdout=subprocess.PIPE, 
stderr=stderr)
  101 
  102 (out, err) = sp.communicate(input)
  103 import pdb; pdb.set_trace()
  104  -> if sp.returncode == 0:
  105 return out
  106 else:
  107 if err:
  108 err = err.decode('UTF-8', errors='replace')
  109 else:
  (Pdb) command
  ['/tmp/apport_sandbox__6uwrvhm/usr/bin/gdb', '--ex', 'set 
debug-file-directory /tmp/apport_sandbox__6uwrvhm/usr/lib/debug', '--ex', 'set 
solib-absolute-prefix /tmp/apport_sandbox__6uwrvhm', '--ex', 'file 
"/tmp/apport_sandbox__6uwrvhm//usr/bin/cdparanoia"', '--ex', 'core-file 
/tmp/apport_core_756rypvb', '--batch', '--ex', 'set backtrace limit 2000', 
'--ex', 'p -99', '--ex', 'print (char*) __nih_abort_msg', '--ex', 'p -99', 
'--ex', 'print __abort_msg->msg', '--ex', 'p -99', '--ex', 'print 
__glib_assert_msg', '--ex', 'p -99', '--ex', 'bt full', '--ex', 'p -99', 
'--ex', 'x/16i $pc', '--ex', 'p -99', '--ex', 'thread apply all bt full', 
'--ex', 'p -99', '--ex', 'info registers']
  (Pdb) out
  b'/tmp/apport_sandbox__6uwrvhm/usr/bin/gdb: error while loading shared 
libraries: libpython3.5m.so.1.0: cannot open shared object file: No such file 
or directory\n'

  Because stdout is not included in the raised error message it ended up
  being hard to find out what the error really was.

  111 raise OSError('Error: command %s failed with exit code %i: 
%s' % (
  112 str(command), sp.returncode, err))

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

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

[Touch-packages] [Bug 1313513] Re: mountall does not honour _netdev

2016-05-11 Thread Elias Abacioglu

I have a similar problem when trying to mount a cephfs volume on ubuntu 14.04.
It just freezes and I can't do anything about it.
I'm unable to figure out why it fails. I am running OpenvSwitch, what I see in
boot log is something like this:

* Starting configure network device
* Starting configure network device security
* Starting configure network device security
* Starting Mount network filesystems
* Starting configure network device
* Starting configure network device security
* Stopping Mount network filesystems
* Starting Mount network filesystems
* Starting configure network device
* Starting Open vSwitch switch
* Stopping Mount network filesystems
_

(it's stuck here forever)

And my fstab looks like this
10.3.60.25,10.3.60.23,10.3.60.21:/opennebula /var/lib/one ceph
_netdev,mount_timeout=10,name=opennebula_cephfs,secretfile=/etc/ceph/ceph.client.opennebula_cephfs.secret
0 0

However worth mentioning that one of the IP's in the list is this
machine itself.. In this case second in the list, 10.3.60.23.

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

Title:
mountall does not honour _netdev

Status in mountall package in Ubuntu:
Confirmed

Bug description:
Hi,

This is a fresh install of Ubuntu 14.04 LTS AMD64. I tried
configuring a Ceph Rados Block Device (rbd) to be mounted during boot
on /var/lib/one, containing my OpenNebula configuration and database.

The idea being that should the machine go belly up, I'll have an up-
to-date snapshot of the OpenNebula data on Ceph to mount on the new
frontend machine.

/etc/ceph/rbdmap is configured, I set up /etc/fstab with an entry:

/dev/rbd/pool/rbdname /var/lib/one xfs defaults,_netdev 0 1

then rebooted. According to mount(8), _netdev is supposed to tell
mountall to skip mounting this device until the network is up.

As seen from the attached snapshot, it doesn't bother to wait, and
blindly tries to mount the RBD before connecting to Ceph: this will
never work.

mountall seems to rely on *knowing* a list of network file systems:
this means when someone comes up with a new network file system, or
uses a conventional disk file system with a remote block device,
mountall's heuristic falls flat on its face as has been demonstrated
here. The problem would also exist for iSCSI, AoE, FibreChannel, nbd
and drbd devices.

Due to bug 1313497, the keyboard is non-functional. Recovery is
useless as the keyboard is broken there too, and now the machine is
waiting for a keypress it will never see due to that bug. A headless
system would similarly have this problem.

Two suggestions I would have:
1. mountall should honour _netdev to decide whether to mount a device or not:
this gives the user the means to manually tell mountall that the device needs
network access to operate even if the filesystem looks to be local. I'd wager
that if the user specified _netdev, they probably meant it and likely know
better than mountall.
2. mountall should time out after a predefined period and NEVER wait
indefinitely: even if the disk is local. If a disk goes missing, then it is
better the machine tries to boot in its degraded state so it can be remotely
managed and raise an alarm, than to wait for someone to notice the machine
being down.

Unfortunately since the machine is now effectively bricked, I can only
grep proxy server logs to see what packages got installed.
mountall_2.53_amd64.deb seems to be the culprit.

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

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

[Touch-packages] [Bug 1313042] Re: console-kit-daemon Glib-CRITICAL warning

2016-05-11 Thread Laurent Bonnaud

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

** This bug has been marked a duplicate of bug 1264368
   GLib-CRITICAL **: Source ID was not found when attempting to remove it - 
warning when leaving Network menu of g-c-c

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

Title:
  console-kit-daemon Glib-CRITICAL warning

Status in consolekit package in Ubuntu:
  Confirmed

Bug description:
  The day I upgraded from 13.10 to 14.04 some of my ssh sessions into
  the new system (server side is Ubuntu 14.04) started hanging.

  The symptom is: I run some command with a lot of output (say a few
  hundreds of lines) in an ssh session, and the second the command
  completes, and the shell displays a new  prompt, the shell stops
  responding to keyboard input.

  At  the exact time of the hang (to the second) I always see these 3
  warnings in syslog:

  Apr 21 18:15:25 xx console-kit-daemon[3357]: GLib-CRITICAL: Source ID 469 was 
not found when attempting to remove it
  Apr 21 18:15:25 xx console-kit-daemon[3357]: GLib-CRITICAL: Source ID 86 was 
not found when attempting to remove it
  Apr 21 18:15:25 xx console-kit-daemon[3357]: GLib-CRITICAL: Source ID 86 was 
not found when attempting to remove it

  The Source ID numbers vary, but the warnings always come in triplets
  at the time of the hang.   I was able to reproduce this about 10 times
  today.  Every time the session hangs, these warnings appear in the log
  and vice versa: every time they appear in the log, I have a hanged
  remote session.

  A quote from an upstream (bugzilla.gnome.org) comment:

  https://bugzilla.gnome.org/show_bug.cgi?id=721369

  GLib recently started throwing a warning when g_source_remove()
  is passed garbage (as per warning). Your applications have probably been 
broken
  for a while, and there's no telling what could actually have happened in 
the
  past when g_source_remove() would happily close any random source because 
the
  programmer got the wrong argument to g_source_remove().

  So based on this I'm opening a bug against  consolekit for bad calls
  to g_source_remove() which seem to be related to the ssh hang.

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

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

[Touch-packages] [Bug 1371293] Re: console-kit-daemon[5037]: GLib-CRITICAL: Source ID 40 was not found when attempting to remove it

2016-05-11 Thread Laurent Bonnaud

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

** This bug is no longer a duplicate of bug 1313042
   console-kit-daemon Glib-CRITICAL warning
** This bug has been marked a duplicate of bug 1264368
   GLib-CRITICAL **: Source ID was not found when attempting to remove it - 
warning when leaving Network menu of g-c-c

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

Title:
  console-kit-daemon[5037]: GLib-CRITICAL: Source ID 40 was not found
  when attempting to remove it

Status in consolekit package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  In syslog there is critical error/s:

  Sep 18 21:15:38 hostname console-kit-daemon[5037]: GLib-CRITICAL: Source ID 
40 was not found when attempting to remove it
  Sep 18 21:15:38 hostname console-kit-daemon[5037]: GLib-CRITICAL: Source ID 
49 was not found when attempting to remove it

  apt-cache policy consolekit
  consolekit:
Installed: 0.4.6-5
Candidate: 0.4.6-5
Version table:
   *** 0.4.6-5 0
  500 http://archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
  100 /var/lib/dpkg/status

  lsb_release -rd
  Description:  Ubuntu Utopic Unicorn (development branch)
  Release:  14.10


  Thank You,
  Kind Regards,
  Martin

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

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

[Touch-packages] [Bug 1580521] [NEW] wget does not support link-scoped IPv6 literal addresses

2016-05-11 Thread Brian Candler

Public bug reported:

Inside an lxd container with default profile you get this error with
wget:

root@first:~# wget http://nsrc.org/
Error parsing proxy URL http://[fe80::1%eth0]:13128: Invalid IPv6 numeric 
address.

root@first:~# echo $http_proxy
http://[fe80::1%eth0]:13128

The underlying issue is that wget does not support IPv6 literals of the
form [address%interface] as used by lxd(*). You can demonstrate this
without lxd:

$ wget http://[fe80::1%eth0]/
http://[fe80::1%eth0]/: Invalid IPv6 numeric address.

$ http_proxy=http://[fe80::1%eth0]:13128 wget http://nsrc.org/
Error parsing proxy URL http://[fe80::1%eth0]:13128: Invalid IPv6 numeric 
address.


(*)
=== /etc/default/lxd ===

# Run a minimal HTTP PROXY server
LXD_IPV6_PROXY="true"

=== /usr/lib/lxd/lxd-bridge ===

[ "${HAS_IPV6}" = "true" ] && [ "${LXD_IPV6_PROXY}" = "true" ] && ip
addr add fe80::1/64 dev "${1}"

=== /usr/lib/lxd/profile-config ===

if [ "${LXD_IPV6_PROXY}" = "true" ]; then
lxc profile set default environment.http_proxy 
"http://[fe80::1%eth0]:13128"; --force-local || true
fi

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: wget 1.17.1-1ubuntu1
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: Wed May 11 10:29:40 2016
InstallationDate: Installed on 2016-05-06 (4 days ago)
InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
SourcePackage: wget
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  wget does not support link-scoped IPv6 literal addresses

Status in wget package in Ubuntu:
  New

Bug description:
  Inside an lxd container with default profile you get this error with
  wget:

  root@first:~# wget http://nsrc.org/
  Error parsing proxy URL http://[fe80::1%eth0]:13128: Invalid IPv6 numeric 
address.

  root@first:~# echo $http_proxy
  http://[fe80::1%eth0]:13128

  The underlying issue is that wget does not support IPv6 literals of
  the form [address%interface] as used by lxd(*). You can demonstrate
  this without lxd:

  $ wget http://[fe80::1%eth0]/
  http://[fe80::1%eth0]/: Invalid IPv6 numeric address.

  $ http_proxy=http://[fe80::1%eth0]:13128 wget http://nsrc.org/
  Error parsing proxy URL http://[fe80::1%eth0]:13128: Invalid IPv6 numeric 
address.

  
  (*)
  === /etc/default/lxd ===

  # Run a minimal HTTP PROXY server
  LXD_IPV6_PROXY="true"

  === /usr/lib/lxd/lxd-bridge ===

  [ "${HAS_IPV6}" = "true" ] && [ "${LXD_IPV6_PROXY}" = "true" ] &&
  ip addr add fe80::1/64 dev "${1}"

  === /usr/lib/lxd/profile-config ===

  if [ "${LXD_IPV6_PROXY}" = "true" ]; then
  lxc profile set default environment.http_proxy 
"http://[fe80::1%eth0]:13128"; --force-local || true
  fi

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: wget 1.17.1-1ubuntu1
  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: Wed May 11 10:29:40 2016
  InstallationDate: Installed on 2016-05-06 (4 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  SourcePackage: wget
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1580533] [NEW] Cycles through resolutions when switching multiple displays from mirrored configuration

2016-05-11 Thread Martin R Mortensen

Public bug reported:

When using the Settings / Displays applikation every time I try to
switch from mirrored between my internal LCD and the 2 external
monitors, the displays cycles through alot of different resolutions and
ends up with mirrored configuration again.

I also tried with xrandr, setting DP-3.3 right-of DP-3.2 triggers same
resolution cycling ending up with mirrored monitors again.

ubuntu 16.04, Lenovo P50.

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
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
 GCC version:  gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Wed May 11 12:16:27 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.4.0-22-generic, x86_64: installed
 nvidia-361, 361.42, 4.4.0-22-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 00 
[VGA controller])
   Subsystem: Lenovo Skylake Integrated Graphics [17aa:222e]
 NVIDIA Corporation GM107GLM [Quadro M1000M] [10de:13b1] (rev a2) (prog-if 00 
[VGA controller])
   Subsystem: Lenovo GM107GLM [Quadro M1000M] [17aa:222e]
InstallationDate: Installed on 2016-05-04 (6 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: LENOVO 20EQS1QJ00
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/08/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: N1EET47W (1.21 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20EQS1QJ00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET47W(1.21):bd03/08/2016:svnLENOVO:pn20EQS1QJ00:pvrThinkPadP50:rvnLENOVO:rn20EQS1QJ00:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20EQS1QJ00
dmi.product.version: ThinkPad P50
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Wed May 11 11:10:19 2016
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.3-1ubuntu2

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


** Tags: amd64 apport-bug ubuntu xenial

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

Title:
  Cycles through resolutions when switching multiple displays from
  mirrored configuration

Status in xorg package in Ubuntu:
  New

Bug description:
  When using the Settings / Displays applikation every time I try to
  switch from mirrored between my internal LCD and the 2 external
  monitors, the displays cycles through alot of different resolutions
  and ends up with mirrored configuration again.

  I also tried with xrandr, setting DP-3.3 right-of DP-3.2 triggers same
  resolution cycling ending up with mirrored monitors again.

  ubuntu 16.04, Lenovo P50.

  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
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.dri

[Touch-packages] [Bug 1580332] Re: [EasyNote_MX45, Analog Devices AD1986A, Green Headphone Out, Rear] No sound at all

** Description changed:

-  Sound not working
- Has already worked under ubuntu some times ago, then no speaker sound but 
still headphone after an upgrade, and now, no sound at all after the last 
upgrades (4.15 => 10.15 => 4.16).
+ Sound not working
+ Has already worked under ubuntu some times ago, then no speaker sound (same 
problem as: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1310622 
) but still headphone after an upgrade, and now, no sound at all after the last 
upgrades (4.15 => 10.15 => 4.16).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic i686
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/pcmC0D0c:   harmonie   1920 F...m pulseaudio
-  /dev/snd/pcmC0D0p:   harmonie   1920 F...m pulseaudio
-  /dev/snd/controlC0:  harmonie   1920 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/pcmC0D0c:   harmonie   1920 F...m pulseaudio
+  /dev/snd/pcmC0D0p:   harmonie   1920 F...m pulseaudio
+  /dev/snd/controlC0:  harmonie   1920 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue May 10 21:07:15 2016
  InstallationDate: Installed on 2014-04-19 (752 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release i386 
(20140416.2)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
  Symptom_Card: Audio interne - HDA Intel
  Symptom_DevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/pcmC0D0c:   harmonie   1920 F...m pulseaudio
-  /dev/snd/pcmC0D0p:   harmonie   1920 F...m pulseaudio
-  /dev/snd/controlC0:  gdm1120 F pulseaudio
-   harmonie   1920 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/pcmC0D0c:   harmonie   1920 F...m pulseaudio
+  /dev/snd/pcmC0D0p:   harmonie   1920 F...m pulseaudio
+  /dev/snd/controlC0:  gdm1120 F pulseaudio
+   harmonie   1920 F pulseaudio
  Symptom_Jack: Green Headphone Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [EasyNote_MX45, Analog Devices AD1986A, Green Headphone Out, Rear] No 
sound at all
  UpgradeStatus: Upgraded to xenial on 2016-05-07 (3 days ago)
  dmi.bios.date: 01/04/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: T12FvNC.302
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: EasyNote_MX45
  dmi.board.vendor: Packard Bell BV
  dmi.board.version: 1.0
  dmi.chassis.type: 10
  dmi.chassis.vendor: Packard Bell BV
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrT12FvNC.302:bd01/04/2007:svnPackardBellBV:pnEasyNote_MX45:pvrPB64E034A7:rvnPackardBellBV:rnEasyNote_MX45:rvr1.0:cvnPackardBellBV:ct10:cvr:
  dmi.product.name: EasyNote_MX45
  dmi.product.version: PB64E034A7
  dmi.sys.vendor: Packard Bell BV

** Description changed:

  Sound not working
- Has already worked under ubuntu some times ago, then no speaker sound (same 
problem as: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1310622 
) but still headphone after an upgrade, and now, no sound at all after the last 
upgrades (4.15 => 10.15 => 4.16).
+ Has already worked under ubuntu some times ago, then no speaker sound but 
still headphone after an upgrade (same problem as: 
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1310622 ), and now, 
no sound at all after the last upgrades (4.15 => 10.15 => 4.16).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic i686
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   harmonie   1920 F...m pulseaudio
   /dev/snd/pcmC0D0p:   harmonie   1920 F...m pulseaudio
   /dev/snd/controlC0:  harmonie   1920 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue May 10 21:07:15 2016
  InstallationDate: Installed on 2014-04-19 (752 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release i386 
(20140416.2)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
  Symptom_Card: Audio interne - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   harmonie   1920 F...m pulseaudio
   /dev/snd/pcmC0D0p:   harmonie   1920 F...m pulseaudio
   /dev/snd/controlC0:  gdm1120 F pulseaudio
    harmonie   1920 F pulseaudio
  Symptom_Jack: Green Headphone Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [EasyNote_MX45, Analog Devices AD1986A, Green Headphone Out, Rear] No 
sound at all
  UpgradeStatus: Upgraded to xenial on 2016-05-07 (3 days ago)

[Touch-packages] [Bug 1519120] Re: Xenial: VLAN interfaces don't work until after a reboot

2016-05-11 Thread SwaJime

This was working on 14.04.
Not working on 16.04.

root@acmu:~# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04 LTS"

root@acmu:~# apt-cache policy vlan
vlan:
  Installed: 1.9-3.2ubuntu1
  Candidate: 1.9-3.2ubuntu1
  Version table:
 *** 1.9-3.2ubuntu1 500
500 http://192.168.1.20/ubuntu xenial/main i386 Packages
500 file:/repo/debs i386/ Packages
100 /var/lib/dpkg/status

root@acmu:~# uname -a
Linux acmu 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:34:49 UTC 2016 i686 
i686 i686 GNU/Linux

root@acmu:~# cat /etc/network/interfaces | grep -A5 enp3s0.345
auto enp3s0.345
iface enp3s0.345 inet static
address 239.192.21.5
netmask 255.255.255.0
network 239.192.21.0
broadcast 239.192.21.255

root@acmu:~# ifup enp3s0.345
Cannot find device "enp3s0.345"
Failed to bring up enp3s0.345.

A reboot did not help.

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

Title:
  Xenial: VLAN interfaces don't work until after a reboot

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I tried to use the network manager UI to define a VLAN interface, and
  nothing happened. There are a few bugs here:

  (1) When creating a VLAN interface through the UI, the "vlan interface
  name" must be filled in. This should just default to ., rather than being a required field. (I typed in "vlan100"
  to get the "Save" button to activate.)

  (2) After creating my VLAN interface, nothing happened. No new
  interface appeared. I then realized that I had not installed the
  "vlan" package, and assumed that NetworkManager therefore could not
  complete configuration of the interface.

  (3) After installing the 'vlan' package (and then telling
  NetworkManager to disconnect and reconnect my Ethernet interface from
  the UI, just for good measure), still no VLAN interfaces were present
  on my system.

  I also tried editing the VLAN interface in the UI, and specifying
  "enp4s0f1.100", but still no VLAN interface came online.

  # apt-cache policy network-manager
  network-manager:
Installed: 1.0.4-0ubuntu6
Candidate: 1.0.4-0ubuntu6
Version table:
   *** 1.0.4-0ubuntu6 0
  500 http://172.16.42.88/ubuntu/ xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  # apt-cache policy vlan
  vlan:
Installed: 1.9-3.2ubuntu1
Candidate: 1.9-3.2ubuntu1
Version table:
   *** 1.9-3.2ubuntu1 0
  500 http://172.16.42.88/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/1519120/+subscriptions

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

[Touch-packages] [Bug 1580538] [NEW] Unskip test_text_field_evokes_osk_bug1545802

2016-05-11 Thread Christian Dywan

Public bug reported:

What it says on the tin.

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

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

Title:
  Unskip test_text_field_evokes_osk_bug1545802

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

Bug description:
  What it says on the tin.

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

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

[Touch-packages] [Bug 1580332] Re: [EasyNote_MX45, Analog Devices AD1986A, Green Headphone Out, Rear] No sound at all

Problem solved

Seeing the number of the sound card I found this thread:
http://ubuntuguide.net/fix-analog-devices-ad1986a-speakers-not-working-in-ubuntu-10-04

And doing the exact opposite:

Opening the file

sudo nano /etc/modprobe.d/alsa-base.conf

Finding the line and changing to:

# Keep snd-pcsp from being loaded as first soundcard
options snd-pcsp index=-2
#options snd-hda-intel model=laptop-eapd

Than reboot.

I suspect that change having been used to solve a precedent problem at
that time, but that the other bug corrections made it being the problem.

I hope it can helps some others

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

Title:
  [EasyNote_MX45, Analog Devices AD1986A, Green Headphone Out, Rear] No
  sound at all

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  No sound available after upgrade.
  Has already worked under ubuntu some time ago, then no speaker sound but 
still headphone after an upgrade (same problem as: 
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1310622 ), and now, 
no sound at all after the last upgrades (4.15 => 10.15 => 4.16).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic i686
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   harmonie   1920 F...m pulseaudio
   /dev/snd/pcmC0D0p:   harmonie   1920 F...m pulseaudio
   /dev/snd/controlC0:  harmonie   1920 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue May 10 21:07:15 2016
  InstallationDate: Installed on 2014-04-19 (752 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release i386 
(20140416.2)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
  Symptom_Card: Audio interne - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   harmonie   1920 F...m pulseaudio
   /dev/snd/pcmC0D0p:   harmonie   1920 F...m pulseaudio
   /dev/snd/controlC0:  gdm1120 F pulseaudio
    harmonie   1920 F pulseaudio
  Symptom_Jack: Green Headphone Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [EasyNote_MX45, Analog Devices AD1986A, Green Headphone Out, Rear] No 
sound at all
  UpgradeStatus: Upgraded to xenial on 2016-05-07 (3 days ago)
  dmi.bios.date: 01/04/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: T12FvNC.302
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: EasyNote_MX45
  dmi.board.vendor: Packard Bell BV
  dmi.board.version: 1.0
  dmi.chassis.type: 10
  dmi.chassis.vendor: Packard Bell BV
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrT12FvNC.302:bd01/04/2007:svnPackardBellBV:pnEasyNote_MX45:pvrPB64E034A7:rvnPackardBellBV:rnEasyNote_MX45:rvr1.0:cvnPackardBellBV:ct10:cvr:
  dmi.product.name: EasyNote_MX45
  dmi.product.version: PB64E034A7
  dmi.sys.vendor: Packard Bell BV

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

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

[Touch-packages] [Bug 1517257] Re: apport-retrace should install and use gdb for target release

I reverted http://bazaar.launchpad.net/~apport-
hackers/apport/trunk/revision/3076 in http://bazaar.launchpad.net
/~apport-hackers/apport/trunk/revision/3080.

This cannot work like this as we need a gdb command which  can actually
run on the host. This is not the case when processing crashes from
foreign architectures. This is already breaking with an i386 sandbox on
amd64:

$ file /tmp/si386/usr/bin/gdb
/tmp/si386/usr/bin/gdb: ELF 32-bit LSB executable, Intel 80386, version 1 
(SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 
2.6.32, BuildID[sha1]=4797df5acda65947a8d421d67e9bc772986ca5ba, stripped

$ ldd /tmp/si386/usr/bin/gdb
not a dynamic executable
$ /tmp/si386/usr/bin/gdb
bash: /tmp/si386/usr/bin/gdb: not found

This could be made to work with some multi-arch magic on the host, but
it will break completely when trying to retrace armhf or ppc reports.

So we'd need to download the apt indexes twice: once for the target arch
and downloading the debs/ddebs, and another time for downloading gdb and
gdb-multiarch for the host architecture. This is prohibitively expensive
when doing it every time, so we need to add a lot of local caching for
that. This is also a lot of work, I'm afraid.

** Changed in: apport
   Importance: Undecided => Wishlist

** Changed in: apport
   Status: Fix Released => Triaged

** Changed in: apport (Ubuntu)
   Status: Fix Committed => Triaged

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

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

Title:
  apport-retrace should install and use gdb for target release

Status in Apport:
  Triaged
Status in apport package in Ubuntu:
  Triaged

Bug description:
  apport-retrace will use the version of gdb installed on the system
  performing the retrace. This can cause issues retracing crash reports
  from releases that have a newer toolchain revision than the system
  performing the retrace. Subsequently, it would be better if apport-
  retrace were to install gdb into the sandbox being used for retracing
  and used that version of gdb for analyzing the core dump.

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

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

[Touch-packages] [Bug 1310622] Re: [EasyNote_MX45, Analog Devices AD1986A, Other Speaker, Internal] Playback problem

I had the same problem, and realised that it may be caused by a previous
try to solve a sound problem.

The solution would be:

1. Upgrade to the last Ubuntu version to date

2 edit the file (with admin rights):
/etc/modprobe.d/alsa-base.conf

Find the line:
# Keep snd-pcsp from being loaded as first soundcard
#options snd-pcsp index=-2
options snd-hda-intel model=laptop-eapd

And change to
# Keep snd-pcsp from being loaded as first soundcard
options snd-pcsp index=-2
#options snd-hda-intel model=laptop-eapd

Save the changes and reboot.
This solved the issue for me.

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

Title:
  [EasyNote_MX45, Analog Devices AD1986A, Other Speaker, Internal]
  Playback problem

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I can hear sound with the headphones but not with speakers. Actually I
  have to plug-in the headphone plug otherwise the speaker icon in the
  top changes between MUTE and ON constantly

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  horacio1853 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Apr 21 15:44:12 2014
  InstallationDate: Installed on 2014-04-21 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_Jack: Other Speaker, Internal
  Symptom_Type: None of the above
  Title: [EasyNote_MX45, Analog Devices AD1986A, Other Speaker, Internal] 
Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/11/2006
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: T12FvNC.203
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: EasyNote_MX45
  dmi.board.vendor: Packard Bell BV
  dmi.board.version: 1.0
  dmi.chassis.type: 10
  dmi.chassis.vendor: Packard Bell BV
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrT12FvNC.203:bd10/11/2006:svnPackardBellBV:pnEasyNote_MX45:pvrPB64H00506:rvnPackardBellBV:rnEasyNote_MX45:rvr1.0:cvnPackardBellBV:ct10:cvr:
  dmi.product.name: EasyNote_MX45
  dmi.product.version: PB64H00506
  dmi.sys.vendor: Packard Bell BV

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

-- 
Mailing list: https://launchpad.net/~touch-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

2016-05-11 Thread ch

** Attachment removed: "unity8.log"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1574777/+attachment/4660210/+files/unity8.log

-- 
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 1578190] Re: New text input visuals very heavy

** Branch linked: lp:~ubuntu-sdk-team/ubuntu-ui-
toolkit/dietTextFieldsTrunk

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

Title:
  New text input visuals very heavy

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  Since the UITK introduced the new text input focus ring, it also
  replaced the shaded Shape with a flat outline. That outline seems
  overly heavy (see attachment).

  The only visual spec of this that I saw (remarked as "old") is
  http://bit.ly/1TtDOqu ([1] says "spec is outdated", too).

  [1] https://sites.google.com/a/canonical.com/apps-and-platform-
  team/3-platform/toolkit/16-text-input

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qml-module-ubuntu-components 1.3.1960+16.04.20160428.1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  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: Unity
  Date: Wed May  4 14:23:21 2016
  SourcePackage: ubuntu-ui-toolkit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1254085] Re: ssh fails to connect to VPN host - hangs at 'expecting SSH2_MSG_KEX_ECDH_REPLY'

2016-05-11 Thread Ricardo Ferreira

Lowering MTU 1200 worked for me.

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

Title:
  ssh fails to connect to VPN host - hangs at 'expecting
  SSH2_MSG_KEX_ECDH_REPLY'

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  ssh -vvv  is failing for me where  is a VPN system.

  VPN is configured and connected via network-manager. Last messages
  from ssh (hangs forever):

  debug2: kex_parse_kexinit: none,z...@openssh.com
  debug2: kex_parse_kexinit: none,z...@openssh.com
  debug2: kex_parse_kexinit: 
  debug2: kex_parse_kexinit: 
  debug2: kex_parse_kexinit: first_kex_follows 0 
  debug2: kex_parse_kexinit: reserved 0 
  debug2: mac_setup: found hmac-md5
  debug1: kex: server->client aes128-ctr hmac-md5 none
  debug2: mac_setup: found hmac-md5
  debug1: kex: client->server aes128-ctr hmac-md5 none
  debug1: sending SSH2_MSG_KEX_ECDH_INIT
  debug1: expecting SSH2_MSG_KEX_ECDH_REPLY

  
  = Workaround =

  $ sudo apt-get install putty
  $ putty 

  This works perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: openssh-client 1:6.4p1-1
  ProcVersionSignature: Ubuntu 3.12.0-3.8-generic 3.12.0
  Uname: Linux 3.12.0-3-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.7-0ubuntu1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Fri Nov 22 15:37:18 2013
  InstallationDate: Installed on 2010-10-21 (1128 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  RelatedPackageVersions:
   ssh-askpass   1:1.2.4.1-9
   libpam-sshN/A
   keychain  2.7.1-1
   ssh-askpass-gnome 1:6.4p1-1
  SSHClientVersion: OpenSSH_6.4p1 Ubuntu-1, OpenSSL 1.0.1e 11 Feb 2013
  SourcePackage: openssh
  UpgradeStatus: Upgraded to trusty on 2013-11-01 (20 days ago)

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

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

[Touch-packages] [Bug 1580546] [NEW] ubuntu-bug behavior does not match documentation onhow to report a bug

2016-05-11 Thread Elyse Grasso

Public bug reported:

In particular, typing ubuntu-bug  in the search widget as
illustrated on the how to report a bug page opens Ubuntu Software
without any information about what to do next.

ubuntu-bug kernel (which seems to be suggested by the how to figure out
the relevant package info) just dies after providing useless messages.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apport 2.20.1-0ubuntu2
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
CrashReports: 664:108:116:11903:2016-05-07 00:23:37.423810907 -0500:2016-05-07 
00:23:37.423810907 -0500:/var/crash/_sbin_upstart.108.crash
CurrentDesktop: Unity
Date: Wed May 11 05:54:30 2016
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.apport:
 # set this to 0 to disable apport, or to 1 to enable it
 # you can temporarily override this with
 # sudo service apport start force_start=1
 enabled=0
mtime.conffile..etc.default.apport: 2016-04-28T21:07:24.472000

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

Title:
  ubuntu-bug behavior does not match documentation onhow to report a bug

Status in apport package in Ubuntu:
  New

Bug description:
  In particular, typing ubuntu-bug  in the search widget as
  illustrated on the how to report a bug page opens Ubuntu Software
  without any information about what to do next.

  ubuntu-bug kernel (which seems to be suggested by the how to figure
  out the relevant package info) just dies after providing useless
  messages.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2
  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
  CrashReports: 664:108:116:11903:2016-05-07 00:23:37.423810907 
-0500:2016-05-07 00:23:37.423810907 -0500:/var/crash/_sbin_upstart.108.crash
  CurrentDesktop: Unity
  Date: Wed May 11 05:54:30 2016
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2016-04-28T21:07:24.472000

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

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

[Touch-packages] [Bug 1580332] Re: [EasyNote_MX45, Analog Devices AD1986A, Green Headphone Out, Rear] No sound at all

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

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

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

** Converted to question:
   https://answers.launchpad.net/ubuntu/+source/pulseaudio/+question/293574

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

Title:
  [EasyNote_MX45, Analog Devices AD1986A, Green Headphone Out, Rear] No
  sound at all

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  No sound available after upgrade.
  Has already worked under ubuntu some time ago, then no speaker sound but 
still headphone after an upgrade (same problem as: 
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1310622 ), and now, 
no sound at all after the last upgrades (4.15 => 10.15 => 4.16).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic i686
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   harmonie   1920 F...m pulseaudio
   /dev/snd/pcmC0D0p:   harmonie   1920 F...m pulseaudio
   /dev/snd/controlC0:  harmonie   1920 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue May 10 21:07:15 2016
  InstallationDate: Installed on 2014-04-19 (752 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release i386 
(20140416.2)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
  Symptom_Card: Audio interne - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   harmonie   1920 F...m pulseaudio
   /dev/snd/pcmC0D0p:   harmonie   1920 F...m pulseaudio
   /dev/snd/controlC0:  gdm1120 F pulseaudio
    harmonie   1920 F pulseaudio
  Symptom_Jack: Green Headphone Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [EasyNote_MX45, Analog Devices AD1986A, Green Headphone Out, Rear] No 
sound at all
  UpgradeStatus: Upgraded to xenial on 2016-05-07 (3 days ago)
  dmi.bios.date: 01/04/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: T12FvNC.302
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: EasyNote_MX45
  dmi.board.vendor: Packard Bell BV
  dmi.board.version: 1.0
  dmi.chassis.type: 10
  dmi.chassis.vendor: Packard Bell BV
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrT12FvNC.302:bd01/04/2007:svnPackardBellBV:pnEasyNote_MX45:pvrPB64E034A7:rvnPackardBellBV:rnEasyNote_MX45:rvr1.0:cvnPackardBellBV:ct10:cvr:
  dmi.product.name: EasyNote_MX45
  dmi.product.version: PB64E034A7
  dmi.sys.vendor: Packard Bell BV

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

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

[Touch-packages] [Bug 1561350] Re: Bluetooth doesn't work

2016-05-11 Thread Vladimir Ustinov

Current version 16.04 now have support for this hardware.

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

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

Title:
  Bluetooth doesn't work

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  I can turn it on and off change visibility and so on. I can use any console 
tools for it - everything looks fine.
  But it looks like it is only visibility of working because it can’t find any 
devices nearby and can’t be found.

  I've check all related topics and try all possible solutions/advices -
  no result.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: bluetooth 5.35-0ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 24 12:11:10 2016
  InstallationDate: Installed on 2015-12-01 (113 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0489:e095 Foxconn / Hon Hai 
   Bus 001 Device 002: ID 04f2:b47f Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire ES1-331
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic.efi.signed 
root=UUID=82b73f79-8d4f-453e-b9ad-fc07955aaa21 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.13
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire ES1-331
  dmi.board.vendor: Acer
  dmi.board.version: V1.13
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.13
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.13:bd12/07/2015:svnAcer:pnAspireES1-331:pvrV1.13:rvnAcer:rnAspireES1-331:rvrV1.13:cvnAcer:ct10:cvrV1.13:
  dmi.product.name: Aspire ES1-331
  dmi.product.version: V1.13
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 70:77:81:2D:04:7E  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING 
RX bytes:700 acl:0 sco:0 events:51 errors:0
TX bytes:3477 acl:0 sco:0 commands:51 errors:0

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

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

[Touch-packages] [Bug 1580553] [NEW] Inactive screen on laptop turns back on immediately after blanking

2016-05-11 Thread Elyse Grasso

Public bug reported:

Inactive laptop screen fades to blank, then immediately brightens again
showing the login screen, and stays lit.

This happens whether the laptop if charging or running on battery.

The problem occurs with both the gnome screensaver package installed and
with xscreensaver.

Indicators in the status bar in addition to the default ones include 
Classic Menu indicator
Dropbox indicator
System Load indicator
(I have been running the same set of indicators on a different, 14.04, laptop 
without them interfering with screen blanking behavior)

Charging with the screen lit seems very slow and discharge seems fast,
but this is a new laptop that came with 16.04 installed, so I don't
really have a basis for comparison.

I have not installed TLP on this laptop.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apport 2.20.1-0ubuntu2
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
CrashReports: 664:108:116:11903:2016-05-07 00:23:37.423810907 -0500:2016-05-07 
00:23:37.423810907 -0500:/var/crash/_sbin_upstart.108.crash
CurrentDesktop: Unity
Date: Wed May 11 06:03:10 2016
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2016-04-28T21:07:24.472000

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


** Tags: amd64 kernel-bug xenial

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

Title:
  Inactive screen on laptop turns back on immediately after blanking

Status in linux package in Ubuntu:
  New

Bug description:
  Inactive laptop screen fades to blank, then immediately brightens
  again showing the login screen, and stays lit.

  This happens whether the laptop if charging or running on battery.

  The problem occurs with both the gnome screensaver package installed
  and with xscreensaver.

  Indicators in the status bar in addition to the default ones include 
  Classic Menu indicator
  Dropbox indicator
  System Load indicator
  (I have been running the same set of indicators on a different, 14.04, laptop 
without them interfering with screen blanking behavior)

  Charging with the screen lit seems very slow and discharge seems fast,
  but this is a new laptop that came with 16.04 installed, so I don't
  really have a basis for comparison.

  I have not installed TLP on this laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2
  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
  CrashReports: 664:108:116:11903:2016-05-07 00:23:37.423810907 
-0500:2016-05-07 00:23:37.423810907 -0500:/var/crash/_sbin_upstart.108.crash
  CurrentDesktop: Unity
  Date: Wed May 11 06:03:10 2016
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2016-04-28T21:07:24.472000

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

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

[Touch-packages] [Bug 1580553] Re: Inactive screen on laptop turns back on immediately after blanking

2016-05-11 Thread Elyse Grasso

ubuntu-bug and its documentation makes it very hard to post a bug that
is actually related to power management. I told it that it was an apport
bug in order to get into the system at all.

** Package changed: apport (Ubuntu) => linux-meta (Ubuntu)

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

Title:
  Inactive screen on laptop turns back on immediately after blanking

Status in linux package in Ubuntu:
  New

Bug description:
  Inactive laptop screen fades to blank, then immediately brightens
  again showing the login screen, and stays lit.

  This happens whether the laptop if charging or running on battery.

  The problem occurs with both the gnome screensaver package installed
  and with xscreensaver.

  Indicators in the status bar in addition to the default ones include 
  Classic Menu indicator
  Dropbox indicator
  System Load indicator
  (I have been running the same set of indicators on a different, 14.04, laptop 
without them interfering with screen blanking behavior)

  Charging with the screen lit seems very slow and discharge seems fast,
  but this is a new laptop that came with 16.04 installed, so I don't
  really have a basis for comparison.

  I have not installed TLP on this laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2
  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
  CrashReports: 664:108:116:11903:2016-05-07 00:23:37.423810907 
-0500:2016-05-07 00:23:37.423810907 -0500:/var/crash/_sbin_upstart.108.crash
  CurrentDesktop: Unity
  Date: Wed May 11 06:03:10 2016
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2016-04-28T21:07:24.472000

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

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

[Touch-packages] [Bug 1575354] Re: Connecting to VPN times out after 25 seconds if login credentials not entered

2016-05-11 Thread Viktor Pal

Will do that in the next days.

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

Title:
  Connecting to VPN times out after 25 seconds if login credentials not
  entered

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Connecting to OpenConnect VPN through the Gnome GUI fails because
  NetworkManager times out while requesting credentials through the GUI
  form in Ubuntu 16.04.

  It worked (is working on other computers I'm working on) fine from
  Ubuntu 12.04-15.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager-openconnect 1.0.2-1build1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Apr 26 22:06:41 2016
  SourcePackage: network-manager-openconnect
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-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] [NEW] Upgrade libseccomp from 2.2.3 ->2.3.1

You have been subscribed to a public bug:

== 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

** Affects: libseccomp (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-141261 severity-high 
targetmilestone-inin1610
-- 
Upgrade libseccomp from 2.2.3 ->2.3.1
https://bugs.launchpad.net/bugs/1580558
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to libseccomp in Ubuntu.

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

[Touch-packages] [Bug 1580558] [NEW] Upgrade libseccomp from 2.2.3 ->2.3.1

2016-05-11 Thread bugproxy

Public bug reported:

== 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

** Affects: libseccomp (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-141261 severity-high 
targetmilestone-inin1610

** Tags added: architecture-s39064 bugnameltc-141261 severity-high
targetmilestone-inin1610

** Changed in: ubuntu
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

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

-- 
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 libseccomp package in Ubuntu:
  New

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/+source/libseccomp/+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 1525390] Re: [drm:intel_pipe_update_end [i915]] ERROR Atomic update failure on pipe A

2016-05-11 Thread mjh

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

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

Title:
   [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on
  pipe A

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Dell 3552 Inspiron laptop, bought with Ubuntu 14.04LTS upgraded, to
  15.10.

  Every few minutes the following appears in the syslog:
  [ 6355.488381] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update 
failure on pipe A (start=1171 end=1172)

  Does not seem to be related to any specific user activity, though I note the 
Chrome 47 displays many graphical artifacts in images.
  Additionally, the below stack trace often appears:

  [ 1365.284232] perf interrupt took too long (2502 > 2500), lowering 
kernel.perf_event_max_sample_rate to 5
  [ 1599.998487] [ cut here ]
  [ 1599.998536] WARNING: CPU: 0 PID: 2333 at 
/build/linux-26_gwp/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:11102 
intel_check_page_flip+0xfc/0x110 [i915]()
  [ 1599.998539] Kicking stuck page flip: queued at 94224, now 94229
  [ 1599.998541] Modules linked in: ctr ccm ip6table_filter ip6_tables 
iptable_filter ip_tables x_tables pci_stub vboxpci(OE) vboxnetadp(OE) rfcomm 
vboxnetflt(OE) vboxdrv(OE) msr bnep binfmt_misc rtsx_usb_ms memstick 
snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic btusb 
uvcvideo dell_wmi btrtl snd_hda_intel sparse_keymap btbcm videobuf2_vmalloc 
btintel videobuf2_memops snd_hda_codec videobuf2_core bluetooth v4l2_common 
snd_hda_core snd_hwdep arc4 videodev media snd_pcm dell_laptop dcdbas 
nls_iso8859_1 rtl8723be snd_seq_midi snd_seq_midi_event intel_rapl snd_rawmidi 
dell_smm_hwmon btcoexist rtl8723_common intel_powerclamp rtl_pci coretemp 
rtlwifi kvm_intel mac80211 kvm punit_atom_debug cfg80211 snd_seq input_leds 
joydev serio_raw snd_seq_device snd_timer lpc_ich snd mei_txe mei
  [ 1599.998609]  shpchp soundcore iosf_mbi i2c_designware_platform mac_hid 
i2c_designware_core dell_rbtn synaptics_i2c parport_pc ppdev lp parport autofs4 
jitterentropy_rng drbg ansi_cprng algif_skcipher af_alg dm_crypt rtsx_usb_sdmmc 
rtsx_usb crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul 
glue_helper ablk_helper i915 cryptd psmouse i2c_algo_bit drm_kms_helper drm 
ahci libahci wmi sdhci_acpi video sdhci pinctrl_cherryview
  [ 1599.998649] CPU: 0 PID: 2333 Comm: Chrome_IOThread Tainted: G   OE 
  4.2.0-19-generic #23-Ubuntu
  [ 1599.998651] Hardware name: Dell Inc. Inspiron 15-3552/0CP33T, BIOS 3.0.3 
08/26/2015
  [ 1599.998654]   24a8568b 88017fc03ce8 
817e93f9
  [ 1599.998659]   88017fc03d40 88017fc03d28 
8107b3d6
  [ 1599.998663]  88017fc03d58 880035904800 8800e000 
8800359049a8
  [ 1599.998668] Call Trace:
  [ 1599.998670][] dump_stack+0x45/0x57
  [ 1599.998684]  [] warn_slowpath_common+0x86/0xc0
  [ 1599.998687]  [] warn_slowpath_fmt+0x55/0x70
  [ 1599.998714]  [] intel_check_page_flip+0xfc/0x110 [i915]
  [ 1599.998736]  [] 
valleyview_pipestat_irq_handler+0x1f6/0x200 [i915]
  [ 1599.998759]  [] cherryview_irq_handler+0x63/0x110 [i915]
  [ 1599.998765]  [] handle_irq_event_percpu+0x74/0x180
  [ 1599.998768]  [] handle_irq_event+0x49/0x70
  [ 1599.998772]  [] handle_edge_irq+0x81/0x150
  [ 1599.998777]  [] handle_irq+0x25/0x40
  [ 1599.998781]  [] do_IRQ+0x4f/0xe0
  [ 1599.998785]  [] common_interrupt+0x6b/0x6b
  [ 1599.998786]  
  [ 1599.998789] ---[ end trace c4f14dcdc80fdcfe ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Dec 11 21:17:25 2015
  DistUpgraded: 2015-10-29 20:07:04,539 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.10, 4.2.0-19-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:22b1] (rev 21) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:06ac]
  InstallationDate: Installed on 2015-05-12 (213 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. Inspiron 15-3552
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-19-generic.efi.signed 
root=/dev/mapper/ubuntu--15--vg-root ro quiet splash i8042.nopnp
  SourcePackage: xorg
  Symptom: display
  UdevLog: Error: [Errno 2] No such file or directo

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

2016-05-11 Thread Zed

notebook hp x360 13-4002dx
new install 16.04
same issue "Notebook doesn't suspend when lid is closed"
adding HandleLidSwitchDocked=suspend in /etc/systemd/logind.conf fix issue.

If need more info for making proper fix - ask

-- 
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:
  Incomplete

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 1574777] Re: tablet connected to monitor shows black screen - Idek Iiyama PL2409HD

2016-05-11 Thread ch

Sorry, I'd attached the wrong unity8.log. Now this one is the one I
described above.

Hmm, and why can you ignore that the mirserver logs the same wrong
information about the display for two different monitors?


** Attachment added: "unity8.log"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1574777/+attachment/4660584/+files/unity8.log

-- 
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 1576747] Re: Network manager unable to control wifi after suspend in 16.04

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => High

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

Title:
  Network manager unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-activating connection 'chiluks-5g 1'
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1688] device 
(wlp4s0): Activation: starting connection 'chiluks-5g 1' 
(8c69564c-5b6f-4ab4-8e6e-ee3157160892)
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1690] device 
(wlp4s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
  Apr 29 09:04:24 x1 NetworkManager[849]:   [14619

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

Those who state that "HandleLidSwitchDocked=suspend" fixes their issue,
could you undo that change and provide the "systemd-inhibit" "xrandr"
and "loginctl" commands output?

-- 
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:
  Incomplete

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 1537389] Re: The Desktop Never Loads and just stays on a black screen

2016-05-11 Thread Kevin DuBois

right, which is a hybris bug, so 'incomplete' (or making this bug a dup
of 1578461) seems appropriate

-- 
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 1547119] Re: Progress Bars are White On Orange

** Changed in: update-manager (Ubuntu)
   Importance: Undecided => Low

** No longer affects: transmissionbt-ppa (Ubuntu)

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

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

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

** Also affects: ubuntu-themes (Ubuntu)
   Importance: Undecided
   Status: New

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

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

** Changed in: update-manager (Ubuntu)
   Status: Confirmed => Invalid

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

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

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

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

** Changed in: hundredpapercuts
   Status: New => Confirmed

** Changed in: hundredpapercuts
   Importance: Undecided => Low

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

Title:
  Progress Bars are White On Orange

Status in One Hundred Papercuts:
  Confirmed
Status in Ubuntu theme:
  Confirmed
Status in transmission package in Ubuntu:
  Invalid
Status in ubuntu-themes package in Ubuntu:
  Confirmed
Status in update-manager package in Ubuntu:
  Invalid

Bug description:
  Take a look at this screenshot:
  http://neartalk.com/ss/2016-02-18_001_703x819.png

  Notice that the progress indicators are both white and orange. This
  doesn't look good to me, and suspect this is not intentional?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: update-manager 1:15.10.3
  ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1
  Uname: Linux 4.4.0-4-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Feb 18 11:19:44 2016
  GsettingsChanges:
   b'com.ubuntu.update-manager' b'show-details' b'true'
   b'com.ubuntu.update-manager' b'window-height' b'660'
   b'com.ubuntu.update-manager' b'first-run' b'false'
   b'com.ubuntu.update-manager' b'window-width' b'933'
   b'com.ubuntu.update-manager' b'launch-time' b'1455815689'
  InstallationDate: Installed on 2016-02-10 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  PackageArchitecture: all
  SourcePackage: update-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1574238] Re: Stand-by/sleep mode 16.04

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

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

Title:
  Stand-by/sleep mode 16.04

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Problems with Stand-by/sleep mode after upgrading to 16.04. Driver
  ventilation still running, but the screen stays black. No reaction at
  all.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  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: Sun Apr 24 13:46:01 2016
  DistUpgraded: 2016-04-22 21:07:47,908 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Kindprozess 
»./xorg_fix_proprietary.py« konnte nicht ausgeführt werden (No such file or 
directory) (8))
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.18, 4.2.0-35-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05ea]
  InstallationDate: Installed on 2015-06-04 (324 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. Inspiron 5537
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=7af49af0-d45a-4a2b-82e8-78cce2243823 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)
  dmi.bios.date: 11/12/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0RKNTK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A07
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd11/12/2013:svnDellInc.:pnInspiron5537:pvrA07:rvnDellInc.:rn0RKNTK:rvrA00:cvnDellInc.:ct8:cvrA07:
  dmi.product.name: Inspiron 5537
  dmi.product.version: A07
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Apr 24 13:05:15 2016
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5558 
   vendor CMN
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Touch-packages] [Bug 1575354] Re: Connecting to VPN times out after 25 seconds if login credentials not entered

2016-05-11 Thread Julien Olivier

Mike, here's what I get in /var/log/syslog after trying to connect to
the VPN. Could you tell me if this is the same bug or if I need to file
another one?

** Attachment added: "/var/log/syslog after trying to connect to VPN"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1575354/+attachment/4660586/+files/syslog

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

Title:
  Connecting to VPN times out after 25 seconds if login credentials not
  entered

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Connecting to OpenConnect VPN through the Gnome GUI fails because
  NetworkManager times out while requesting credentials through the GUI
  form in Ubuntu 16.04.

  It worked (is working on other computers I'm working on) fine from
  Ubuntu 12.04-15.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager-openconnect 1.0.2-1build1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Apr 26 22:06:41 2016
  SourcePackage: network-manager-openconnect
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1490956] Re: QOpenGL widget-based app crashing

2016-05-11 Thread Gerry Boland

I suspect https://github.com/libhybris/libhybris/issues/315 is exactly
this issue.

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

Title:
  QOpenGL widget-based app crashing

Status in qtubuntu:
  Triaged
Status in libhybris package in Ubuntu:
  New

Bug description:
  tsdgeos has this crash with a game of his:
  http://paste.ubuntu.com/12244384/

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

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

[Touch-packages] [Bug 1547374] Re: "Monospace Regular 8" became wider

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

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

Title:
  "Monospace Regular 8" became wider

Status in fontconfig package in Ubuntu:
  Confirmed

Bug description:
  I've been using gnome-terminal with "Monospace Regular 8" for years,
  which always had a 6x13 px font size (the same size as xterm, just
  nicer antialiasing).

  With yesterday's update in Xenial, it became wider: 7x13 px each cell
  (and less pleasing to my eyes).

  The neighbor sizes "Monospace Regular 7" is 5px wide, "Monospace
  Regular 9" is 7px wide just as "Monospace Regular 8", only taller. So
  it doesn't make sense for me for "Monospace Regular 8" to be 7px wide
  instead of 6px in between the two neighboring sizes as it used to be.

  (No clue which package is the culprit, sorry.)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: fontconfig 2.11.1-0ubuntu7
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 19 09:11:41 2016
  InstallationDate: Installed on 2012-05-30 (1359 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: fontconfig
  UpgradeStatus: Upgraded to xenial on 2016-02-13 (5 days ago)

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

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

[Touch-packages] [Bug 1578619] Re: [regression] Extra flickable margin added when using PullToRefresh

** Branch linked: lp:~tpeeters/ubuntu-ui-toolkit/refreshMargin

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

Title:
  [regression] Extra flickable margin added when using PullToRefresh

Status in Canonical System Image:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  The attached test works fine under OTA-10, but fails in rc-proposed.
  This is most likely caused by https://code.launchpad.net/~tpeeters
  /ubuntu-ui-toolkit/invisible-header-topmargin/+merge/290659 which also
  causes bug 1572525 and I asked to be reverted.

  To reproduce, run the attached test case with qmlscene:

  1) Wait for the window to be populated (network connectivity is needed)
  2) Swipe down, to trigger the pull to refresh action
  3) View automatically jumps to the second page
  4) navigate back to the first page
  5) watch the flickable topMargin: the pulltorefresh item is now visible

  If time you repeat steps 2-4, the topMargin increases.

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

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

[Touch-packages] [Bug 1578190] Re: New text input visuals very heavy

2016-05-11 Thread Timo Jyrinki

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

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

Title:
  New text input visuals very heavy

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  Since the UITK introduced the new text input focus ring, it also
  replaced the shaded Shape with a flat outline. That outline seems
  overly heavy (see attachment).

  The only visual spec of this that I saw (remarked as "old") is
  http://bit.ly/1TtDOqu ([1] says "spec is outdated", too).

  [1] https://sites.google.com/a/canonical.com/apps-and-platform-
  team/3-platform/toolkit/16-text-input

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qml-module-ubuntu-components 1.3.1960+16.04.20160428.1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  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: Unity
  Date: Wed May  4 14:23:21 2016
  SourcePackage: ubuntu-ui-toolkit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1389657] Re: Libpixman segfaults when searching

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

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

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

Title:
  Libpixman segfaults when searching

Status in pixman package in Ubuntu:
  Confirmed

Bug description:
  [ 2810.133252] pool[8519]: segfault at bc ip 7f966bdabb71 sp
  7f962bfed040 error 4 in libpixman-1.so.0.32.4[7f966bd55000+a3000]

  Compiz crashed and I saw the above line in the dmesg output.

  Happens EVERY time I pressed "d" on the ubuntu button for file search
  (dash, icon on top in the sidebar).

  Furthermore .xsession-errors has logged this as well:
  upstart: unity7 main process (1925) killed by SEGV signal
  upstart: unity7 main process ended, respawning

  Pretty serious I'd say ...

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

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

[Touch-packages] [Bug 1389657] Re: Libpixman segfaults when searching

2016-05-11 Thread photon

dmesg on a debian system:

[ 8507.445846] dibosys-disp-40[21440]: segfault at 7f4a67fff000 ip
7f4b01a4fa70 sp 7fff57fdb098 error 4 in
libpixman-1.so.0.33.6[7f4b019c1000+a]

..so the current libpixman version (0.33.6-1) seems to have the same
problem, triggered using a gtk3 webkit browser written in perl (when
running on xserver with 4k resolution, javascipt enabled and scrolling a
web page 1 pixel at a time).. [reproducible, crash after scrolling about
50 pixels]

same effect (segfault) occurs with version 0.32.6-3

serious indeed, affects all our appliances / customers...

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

Title:
  Libpixman segfaults when searching

Status in pixman package in Ubuntu:
  Confirmed

Bug description:
  [ 2810.133252] pool[8519]: segfault at bc ip 7f966bdabb71 sp
  7f962bfed040 error 4 in libpixman-1.so.0.32.4[7f966bd55000+a3000]

  Compiz crashed and I saw the above line in the dmesg output.

  Happens EVERY time I pressed "d" on the ubuntu button for file search
  (dash, icon on top in the sidebar).

  Furthermore .xsession-errors has logged this as well:
  upstart: unity7 main process (1925) killed by SEGV signal
  upstart: unity7 main process ended, respawning

  Pretty serious I'd say ...

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

-- 
Mailing list: https://launchpad.net/~touch-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] [NEW] python2.7 crashes with SegFault when running Zope

2016-05-11 Thread Ján Jockusch

Public bug reported:

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

** Affects: python2.7 (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "Script to reproduce the error on a fresh Ubuntu 16.04"
   
https://bugs.launchpad.net/bugs/1580577/+attachment/4660632/+files/testing_script.sh

-- 
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:
  New

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

[Touch-packages] [Bug 1286596] Re: mediascanner-service-2.0 crashed because could no longer create new inotify watches

2016-05-11 Thread Fabio

Bug name changed to avoid confusion, as this bug is automatically
suggested when reporting the bug with ubuntu-bug.

** Summary changed:

- mediascanner-service-2.0 crashed with SIGABRT in 
__gnu_cxx::__verbose_terminate_handler()
+ mediascanner-service-2.0 crashed because could no longer create new inotify 
watches

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

Title:
  mediascanner-service-2.0 crashed because could no longer create new
  inotify watches

Status in mediascanner2 package in Ubuntu:
  Fix Released

Bug description:
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04
  mediascenner2.0 0.99+14.04.20140220-0ubuntu1

  Actually, I don't know how to reproduce this crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: mediascanner2.0 0.99+14.04.20140220-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar  1 20:02:27 2014
  ExecutablePath: /usr/bin/mediascanner-service-2.0
  InstallationDate: Installed on 2014-01-29 (30 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140128)
  ProcCmdline: mediascanner-service-2.0
  Signal: 6
  SourcePackage: mediascanner2
  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
   mediascanner::SubtreeWatcher::addDir(std::string const&) ()
  Title: mediascanner-service-2.0 crashed with SIGABRT in 
__gnu_cxx::__verbose_terminate_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

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

-- 
Mailing list: https://launchpad.net/~touch-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

2016-05-11 Thread Ján Jockusch

Important additional information:

Stock pythons from python.org do not exhibit the problem.

Tested with:
- Python 2.7.9
- Python 2.7.10
- Python 2.7.11

-- 
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:
  New

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 1580558] Re: Upgrade libseccomp from 2.2.3 ->2.3.1

2016-05-11 Thread Frank Heimes

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

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

-- 
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:
  New
Status in libseccomp package in Ubuntu:
  New

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 1580558] Re: Upgrade libseccomp from 2.2.3 ->2.3.1

2016-05-11 Thread Frank Heimes

** Changed in: ubuntu-z-systems
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Changed in: ubuntu-z-systems
   Status: New => Triaged

-- 
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:
  New

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 1536353] Re: [regression] Printer drivers install is broken as lsb package is not available anymore

2016-05-11 Thread Arup

Suggestion from openprinting forums...

Firstly, install the package with dpkg -i , then change the dependency
on lsb to lsb-base by editing /var/lib/dpkg/status and finding the epson
package in that file. Then change the Depends: line to lsb-base so it
looks like

Depends: lsb-base

Then run apt-get install -f to configure the dirver properly.

The second thing is, because this isn't a real LSB system (or, seems so
to me) then you have to have a LSB compatible loader in /lib64 so we
need to symlink the standard link loader instead.

As root, you would

ln -s /lib64/ld-linux-x86-64.so.2 /lib64/ld-lsb-x86-64.so.3

This satisfies the loader for the printfilter.

After these steps, my networked XP-312 worked.

I suspect this to be the case for many of the LSB based Epson drivers on
Ubuntu 16.04 (maybe earlier versions of Ubuntu as well, actually).

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

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

Status in cups-filters package in Ubuntu:
  Confirmed
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Confirmed
Status in system-config-printer package in Ubuntu:
  Invalid

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

  lsb (9.20150826) unstable; urgency=low

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

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

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

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

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

  I see two possible solutions:

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

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

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

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

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

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

** Changed in: python2.7 (Ubuntu)
   Status: New => Confirmed

-- 
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 1559596] Re: arale capacitive button not disabled on music playback

2016-05-11 Thread Marko Šterman

Doesn't deactivate as in... when the screen is locked you can still
"press" it (it lights up normally ) and it will automatically wake up
the screen, unlock the phone and go to Today scope... without pressing
the Lock/Unlock button

as for your suggestion i don't have the device near me atm can test it
later

-- 
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:
  New
Status in unity-scope-mediascanner package in Ubuntu:
  New
Status in unity-scopes-shell package in Ubuntu:
  New

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 1551491] Re: Emoji skin tones are rendered as missing characters

2016-05-11 Thread Michael Sheldon

I've filed a Qt bug for this here:
https://bugreports.qt.io/browse/QTBUG-53302

Here's a bug that was fixed to provide support for Apple colour fonts,
but I believe that only works on Mac OS X with the native renderer:
https://bugreports.qt.io/browse/QTBUG-45514

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

Title:
  Emoji skin tones are rendered as missing characters

Status in Canonical System Image:
  Confirmed
Status in messaging-app package in Ubuntu:
  Confirmed
Status in ubuntu-keyboard package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu RTM:
  New

Bug description:
  U+1F3FB through U+1F3FF are not rendered in the messaging app.
  Instead the "empty rectangle" missing-character symbol is rendered.

  These characters are the "EMOJI MODIFIER FITZPATRICK TYPE" characters.
  They are meant to indicate skin tone of the preceding emoji.

  I know that on the messaging app, all emoji are currently rendered as
  black and white.  I assume that is a design choice.  In the case we
  given specific color information, we either could render the color as
  requested or ignore it.  But in neither case should we show the
  "missing-character" symbol.

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

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

[Touch-packages] [Bug 1579825] Re: IP Address not displayed for wifi access points

2016-05-11 Thread Jean-Baptiste Lallement

** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Committed

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

Title:
  IP Address not displayed for wifi access points

Status in Canonical System Image:
  Fix Committed
Status in indicator-network package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  latest rc-proposed build 319

  Open system settings
  expand the connected access point by pressing right arrow

  expected results:
  ip address is displayed

  actual results:
  ip address is not displayed, just a label "IP Address" with no value

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

-- 
Mailing list: https://launchpad.net/~touch-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

2016-05-11 Thread Neil Woolford

Ok.

Commented out the  HandleLidSwitchDocked=suspend line and restarted
systemd-logind.

Closed lid, waited a minute, the bug showed itself, the system did not
suspend.

neilw@NWPS-LAP:/etc/systemd$ systemd-inhibit
 Who: Unity (UID 1000/neilw, PID 1463/compiz)
What: sleep
 Why: Unity needs to lock the screen
Mode: delay

 Who: neilw (UID 1000/neilw, PID 1448/unity-settings-)
What: handle-power-key:handle-suspend-key:handle-hibernate-key
 Why: GNOME handling keypresses
Mode: block

 Who: neilw (UID 1000/neilw, PID 1448/unity-settings-)
What: sleep
 Why: GNOME needs to lock the screen
Mode: delay

 Who: Telepathy (UID 1000/neilw, PID 1729/mission-control)
What: shutdown:sleep
 Why: Disconnecting IM accounts before suspend/shutdown...
Mode: delay

 Who: NetworkManager (UID 0/root, PID 2218/NetworkManager)
What: sleep
 Why: NetworkManager needs to turn off networks
Mode: delay

5 inhibitors listed.

neilw@NWPS-LAP:/etc/systemd$ xrandr
Screen 0: minimum 320 x 200, current 1366 x 768, maximum 8192 x 8192
LVDS connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 
344mm x 194mm
   1366x768  60.07*+  40.04  
   1280x720  59.86  
   1152x768  59.78  
   1024x768  59.92  
   800x600   59.86  
   848x480   59.66  
   720x480   59.71  
   640x480   59.38  
HDMI-0 disconnected (normal left inverted right x axis y axis)
VGA-0 disconnected (normal left inverted right x axis y axis)

neilw@NWPS-LAP:/etc/systemd$ loginctl
   SESSIONUID USER SEAT
c2   1000 neilwseat0   

1 sessions listed.

-- 
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:
  Incomplete

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 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04

2016-05-11 Thread Neil Woolford

I've reinstated the workaround and run the requested commands again.

As far as I can see, the output of all three is exactly the same as in
the bug condition, apart from the items in the inhibitors list being
shown in a different order.

-- 
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:
  Incomplete

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 1580597] [NEW] /usr/bin/sudo:11:kill:main

2016-05-11 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding sudo.  This problem was most recently seen with version
1.8.16-0ubuntu2, the problem page at
https://errors.ubuntu.com/problem/df1e2e2bf23715911818cbc34bafb656d382ccdd
contains more details.

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


** Tags: xenial yakkety

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

Title:
  /usr/bin/sudo:11:kill:main

Status in sudo package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1580601] Re: __nih_abort_msg symbol cannot be read any more

Neither libnih nor glibc changed in yakkety, but what did change is that
gcc now applies the PIE option by default. Maybe libnih needs to be
adjusted for PIE on amd64, or this needs to be fixed in gcc, thus adding
a task for both for now.

** Tags removed: xenial
** Tags added: regression-releasease yakkety

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

Title:
  __nih_abort_msg symbol cannot be read any more

Status in gcc-5 package in Ubuntu:
  New
Status in libnih package in Ubuntu:
  New

Bug description:
  libnih has a global symbol __nih_abort_msg that contains the message
  of the last failed nih_assert() (similar to glibc's own __abort_msg
  and glib's __glib_assert_msg). Apport uses these to produce a more
  meaningful crash report than just "/bin/foo crashed with SIGABRT", as
  in these case the thing you actually want to see is the assertion
  message.

  This stopped working in yakkety/amd64. apport's
  report.test_add_gdb_info_abort_libnih() now fails:

  ERROR: test_add_gdb_info_abort_libnih (__main__.T)
  add_gdb_info() with libnih assertion
  --
  Traceback (most recent call last):
File "./test_report.py", line 886, in test_add_gdb_info_abort_libnih
  self.assertIn('Assertion failed in main: 1 < 0', pr['AssertionMessage'])
File "/usr/lib/python3.5/collections/__init__.py", line 985, in __getitem__
  raise KeyError(key)
  KeyError: 'AssertionMessage'

  This can be reproduced with the attached script which compiles a
  trivial nih_assert() C program, runs it, and runs gdb on the produced
  core dump. Up until xenial it looks like:

  $ ./nih-assert.sh 
  (null)::2: Assertion failed in main: 1 < 0
  Aborted (core dumped)
  [New LWP 9838]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `./nih-assert'.
  Program terminated with signal SIGABRT, Aborted.
  #0  0x7f28c070d418 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:54
  54../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
  $1 = 0x25400f0 ":2: Assertion failed in main: 1 < 0"

  But in yakkety/amd64 it now looks like

  $ ./nih-assert.sh 
  (null)::2: Assertion failed in main: 1 < 0
  Aborted (core dumped)
  [New LWP 10489]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `./nih-assert'.
  Program terminated with signal SIGABRT, Aborted.
  #0  0x7fd303865418 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:54
  54../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
  $1 = 0x869400f0 

  
  This can be reproduced easily in a schroot, you need to install "libnih-dev 
pkg-config gdb".

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libnih-dev 1.0.3-4.3ubuntu1
  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: i3
  Date: Wed May 11 15:13:46 2016
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu3
   libgcc1 1:6.0.1-0ubuntu1
   libnih1 1.0.3-4.3ubuntu1
  EcryptfsInUse: Yes
  SourcePackage: libnih
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1580601] [NEW] __nih_abort_msg symbol cannot be read any more

Public bug reported:

libnih has a global symbol __nih_abort_msg that contains the message of
the last failed nih_assert() (similar to glibc's own __abort_msg and
glib's __glib_assert_msg). Apport uses these to produce a more
meaningful crash report than just "/bin/foo crashed with SIGABRT", as in
these case the thing you actually want to see is the assertion message.

This stopped working in yakkety/amd64. apport's
report.test_add_gdb_info_abort_libnih() now fails:

ERROR: test_add_gdb_info_abort_libnih (__main__.T)
add_gdb_info() with libnih assertion
--
Traceback (most recent call last):
  File "./test_report.py", line 886, in test_add_gdb_info_abort_libnih
self.assertIn('Assertion failed in main: 1 < 0', pr['AssertionMessage'])
  File "/usr/lib/python3.5/collections/__init__.py", line 985, in __getitem__
raise KeyError(key)
KeyError: 'AssertionMessage'

This can be reproduced with the attached script which compiles a trivial
nih_assert() C program, runs it, and runs gdb on the produced core dump.
Up until xenial it looks like:

$ ./nih-assert.sh 
(null)::2: Assertion failed in main: 1 < 0
Aborted (core dumped)
[New LWP 9838]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `./nih-assert'.
Program terminated with signal SIGABRT, Aborted.
#0  0x7f28c070d418 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:54
54  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
$1 = 0x25400f0 ":2: Assertion failed in main: 1 < 0"

But in yakkety/amd64 it now looks like

$ ./nih-assert.sh 
(null)::2: Assertion failed in main: 1 < 0
Aborted (core dumped)
[New LWP 10489]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `./nih-assert'.
Program terminated with signal SIGABRT, Aborted.
#0  0x7fd303865418 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:54
54  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
$1 = 0x869400f0 


This can be reproduced easily in a schroot, you need to install "libnih-dev 
pkg-config gdb".

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libnih-dev 1.0.3-4.3ubuntu1
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: i3
Date: Wed May 11 15:13:46 2016
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu3
 libgcc1 1:6.0.1-0ubuntu1
 libnih1 1.0.3-4.3ubuntu1
EcryptfsInUse: Yes
SourcePackage: libnih
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gcc-5 (Ubuntu)
 Importance: Undecided
 Status: New

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


** Tags: amd64 apport-bug regression-releasease yakkety

** Attachment added: "reproducer"
   
https://bugs.launchpad.net/bugs/1580601/+attachment/4660648/+files/nih-assert.sh

** Also affects: gcc-5 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  __nih_abort_msg symbol cannot be read any more

Status in gcc-5 package in Ubuntu:
  New
Status in libnih package in Ubuntu:
  New

Bug description:
  libnih has a global symbol __nih_abort_msg that contains the message
  of the last failed nih_assert() (similar to glibc's own __abort_msg
  and glib's __glib_assert_msg). Apport uses these to produce a more
  meaningful crash report than just "/bin/foo crashed with SIGABRT", as
  in these case the thing you actually want to see is the assertion
  message.

  This stopped working in yakkety/amd64. apport's
  report.test_add_gdb_info_abort_libnih() now fails:

  ERROR: test_add_gdb_info_abort_libnih (__main__.T)
  add_gdb_info() with libnih assertion
  --
  Traceback (most recent call last):
File "./test_report.py", line 886, in test_add_gdb_info_abort_libnih
  self.assertIn('Assertion failed in main: 1 < 0', pr['AssertionMessage'])
File "/usr/lib/python3.5/collections/__init__.py", line 985, in __getitem__
  raise KeyError(key)
  KeyError: 'AssertionMessage'

  This can be reproduced with the attached script which compiles a
  trivial nih_assert() C program, runs it, and runs gdb on the produced
  core dump. Up until xenial it looks like:

  $ ./nih-assert.sh 
  (null)::2: Assertion failed in main: 1 < 0
  Aborted (core dumped)
  [New LWP 9838]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `./nih-assert'.
  Program terminated with signal SIGABRT, Aborted.
  #0

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

2016-05-11 Thread Karl Rinne

I have the Meizu mx4 near me: Start a video (Media Player) then lock the
screen (stops the video/sound as expected).

I see the following behaviour (I think it's consistent):
a) Pressing the capacitive button within a second or two after screen lock, the 
mx4 responds to the capacitive button and hops straight to the home screen.
b) If you wait longer than say 5 seconds or longer, the mx4 does not respond to 
the capacitive button, and can be unlocked as usual.

Hope this helps.

-- 
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:
  New
Status in unity-scope-mediascanner package in Ubuntu:
  New
Status in unity-scopes-shell package in Ubuntu:
  New

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 1559596] Re: arale capacitive button not disabled on music playback

2016-05-11 Thread Marko Šterman

not for me on RC proposed... it responds any at any time

-- 
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:
  New
Status in unity-scope-mediascanner package in Ubuntu:
  New
Status in unity-scopes-shell package in Ubuntu:
  New

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 1580616] [NEW] AMD GPUs not working

2016-05-11 Thread jacklondon

Public bug reported:

My AMD GPUs do not work or register

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.1:
 
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed May 11 06:47:04 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
InstallationDate: Installed on 2016-04-12 (28 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=1628c3f9-dc94-42dd-951b-971689ff1cb0 ro recovery nomodeset
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/01/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.20
dmi.board.name: H81 Pro BTC
dmi.board.vendor: ASRock
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.:bvrP2.20:bd03/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH81ProBTC:rvr: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.1
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 23:16:41 2016
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputTelink Wireless Receiver KEYBOARD, id 8
 inputTelink Wireless Receiver KEYBOARD, id 9
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.3-1ubuntu2.1

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


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

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

Title:
  AMD GPUs not working

Status in xorg package in Ubuntu:
  New

Bug description:
  My AMD GPUs do not work or register

  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.1:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed May 11 06:47:04 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  InstallationDate: Installed on 2016-04-12 (28 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=1628c3f9-dc94-42dd-951b-971689ff1cb0 ro recovery nomodeset
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.20
  dmi.board.name: H81 Pro BTC
  dmi.board.vendor: ASRock
  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.:bvrP2.20:bd03/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH81ProBTC:rv

[Touch-packages] [Bug 1579221] Re: Hotspot not working with NM 1.2

2016-05-11 Thread Pete Woods

In silo #19 we now have the following changes:
  * Fix limitations property (Lorn's patch)
  * Remember hotspot UUID (stop NM warning about changing UUID)
  * Wait for hotspot device to be ready, not just present (as per Alfonso's 
recommendation)
  * Don't create NM ipv4 settings with empty values (Tony's fix)

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

Title:
  Hotspot not working with NM 1.2

Status in Canonical System Image:
  In Progress
Status in indicator-network package in Ubuntu:
  In Progress

Bug description:
  While testing network-manager 1.1.93-0ubuntu1~vivid1 we noticed that
  hotspot no longer worked on arale or krillin ( it's not enabled on
  mako ).

  The first issue was that if no NM connection file yet existed for the
  hotspot, indicator-network would fail creating one due to a DBus
  error:

  void nmofono::HotspotManager::Priv::addConnection() Adding new hotspot 
connection
  Failed to add connection: "ipv4.dns: can't set property of type 'au' from 
value of type 'as'"

  This was due to indicator-network using the following code to set this
  setting:

  ipv4[QStringLiteral("dns")] = QVariant(QStringList());

  My guess is that NM's re-factoring of it's DBus code to use gdbus
  instead of dbus-glib, resulting in NM being a bit more strict in it's
  parameter checking.

  Removing this, and the same for the 'addresses' and 'routes' settings allows 
indicator-network to create hotspot connection files once again.
  See the associated branch for the update.

  If a connection file already exists, or one is created with the fix
  from the merge proposal, then the current problem is that when 'Start'
  is pressed, the UI displays a spinner which is never dismissed.

  Testing has shown that the hotspot is actually activated, can be seen
  from other devices and connected to.

  Testing has also shown that it's possible to activate the hotspot
  using nmcli directly, and the result is usable from other clients.

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

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

[Touch-packages] [Bug 1580616] Re: AMD GPUs not working

2016-05-11 Thread jacklondon

still nothing

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

Title:
  AMD GPUs not working

Status in xorg package in Ubuntu:
  New

Bug description:
  My AMD GPUs do not work or register

  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.1:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed May 11 06:47:04 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  InstallationDate: Installed on 2016-04-12 (28 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=1628c3f9-dc94-42dd-951b-971689ff1cb0 ro recovery nomodeset
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.20
  dmi.board.name: H81 Pro BTC
  dmi.board.vendor: ASRock
  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.:bvrP2.20:bd03/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH81ProBTC:rvr: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.1
  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 23:16:41 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputTelink Wireless Receiver KEYBOARD, id 8
   inputTelink Wireless Receiver KEYBOARD, id 9
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2.1

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

-- 
Mailing list: https://launchpad.net/~touch-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

2016-05-11 Thread Jim Hodapp

Interesting, so it's not consistent across multiple MX4s. What versions
of Ubuntu Touch are you both running? Will need to see how this behaves
on a freshly flashed MX4 with the same version.

-- 
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:
  New
Status in unity-scope-mediascanner package in Ubuntu:
  New
Status in unity-scopes-shell package in Ubuntu:
  New

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 1580627] [NEW] ComboButton is not propagating the click event

2016-05-11 Thread Renato Araujo Oliveira Filho

Public bug reported:

ListView delegate is not receiving the click event.

Check attached example.

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

** Attachment added: "combo.qml"
   https://bugs.launchpad.net/bugs/1580627/+attachment/4660689/+files/combo.qml

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

Title:
  ComboButton is not propagating the click event

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

Bug description:
  ListView delegate is not receiving the click event.

  Check attached example.

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

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

[Touch-packages] [Bug 1579221] Re: Hotspot not working with NM 1.2

2016-05-11 Thread Pete Woods

This fixes all the of issues I am *aware* of in indicator-network.
However when enabling hotspot on Krillin channel 'ubuntu-touch/rc-
proposed/bq-aquaris.en' r329 I seem to get kernel panics some of the
time. Additionally I also have seen a network-manager crash:

http://people.canonical.com/~pete/nm-debugging/

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

Title:
  Hotspot not working with NM 1.2

Status in Canonical System Image:
  In Progress
Status in indicator-network package in Ubuntu:
  In Progress

Bug description:
  While testing network-manager 1.1.93-0ubuntu1~vivid1 we noticed that
  hotspot no longer worked on arale or krillin ( it's not enabled on
  mako ).

  The first issue was that if no NM connection file yet existed for the
  hotspot, indicator-network would fail creating one due to a DBus
  error:

  void nmofono::HotspotManager::Priv::addConnection() Adding new hotspot 
connection
  Failed to add connection: "ipv4.dns: can't set property of type 'au' from 
value of type 'as'"

  This was due to indicator-network using the following code to set this
  setting:

  ipv4[QStringLiteral("dns")] = QVariant(QStringList());

  My guess is that NM's re-factoring of it's DBus code to use gdbus
  instead of dbus-glib, resulting in NM being a bit more strict in it's
  parameter checking.

  Removing this, and the same for the 'addresses' and 'routes' settings allows 
indicator-network to create hotspot connection files once again.
  See the associated branch for the update.

  If a connection file already exists, or one is created with the fix
  from the merge proposal, then the current problem is that when 'Start'
  is pressed, the UI displays a spinner which is never dismissed.

  Testing has shown that the hotspot is actually activated, can be seen
  from other devices and connected to.

  Testing has also shown that it's possible to activate the hotspot
  using nmcli directly, and the result is usable from other clients.

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

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

[Touch-packages] [Bug 1575690] Re: rabbitmq-server in lxc container running 14.04 fails to start

2016-05-11 Thread j^

** Changed in: lxc (Ubuntu)
   Status: New => Invalid

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

Title:
  rabbitmq-server in lxc container running 14.04 fails to start

Status in lxc package in Ubuntu:
  Invalid

Bug description:
  rabbitmq-server no longer starts inside an lxc container running 14.04
  after upgrading host to 16.04

  container config uses default ubuntu.common.conf configuration:

  # Common configuration
  lxc.include = /usr/share/lxc/config/ubuntu.common.conf

  # Container specific configuration
  lxc.rootfs = /var/lib/lxc/rabbitmq1404/rootfs
  lxc.mount = /var/lib/lxc/rabbitmq1404/fstab
  lxc.utsname = rabbitmq1404
  lxc.arch = amd64

  # Network configuration
  lxc.network.type = veth
  lxc.network.flags = up
  lxc.network.link = lxcbr0
  lxc.network.hwaddr = xxx

  
  rabbitmq error:

  BOOT FAILED
  ===

  Error description:
 {could_not_start,rabbit,
 {bad_return,
 {{rabbit,start,[normal,[]]},
  {'EXIT',
  {rabbit,failure_during_boot,
  {{shutdown,
   {failed_to_start_child,rabbit_memory_monitor,
   {noproc,
   {gen_server,call,
   [vm_memory_monitor,get_memory_limit,
infinity],
   {child,undefined,rabbit_memory_monitor_sup,
   {rabbit_restartable_sup,start_link,
   [rabbit_memory_monitor_sup,
{rabbit_memory_monitor,start_link,[]}]},
   transient,infinity,supervisor,
   [rabbit_restartable_sup]}}}

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

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

[Touch-packages] [Bug 981461] Re: Network interfaces are not correctly brought down on halt, disrupting Wake-on-LAN

2016-05-11 Thread proofNot

thanks to the solution proposed by @Robbie Williamson I was able to
start my ubuntu server by sending WOL packets

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

Title:
  Network interfaces are not correctly brought down on halt, disrupting
  Wake-on-LAN

Status in ifupdown package in Ubuntu:
  Triaged
Status in upstart package in Ubuntu:
  Confirmed
Status in ifupdown source package in Precise:
  Triaged

Bug description:
  I found the workaround (and proof) for this bug is posted here:
  
http://confoundedtech.blogspot.com/2011/06/enable-wol-on-ubuntu-hp-microserver.html

  The relevant info is below
  =
  To get WOL to work the ethernet interface must be properly brought down as 
part of the system shutdown. This should be performed as part of run levels rc0 
and rc6, noting that Linux typically has 7 different run levels (or operating 
modes):
  rc0.d - System Halted
  rc1.d - Single User Mode
  rc2.d - Single User Mode with Networking
  rc3.d - Multi-User Mode - boot up in text mode
  rc4.d - Not yet Defined
  rc5.d - Multi-User Mode - boot up in X Windows
  rc6.d - Shutdown & Reboot
  A simple script can be created to bring the ethernet interface down properly 
at shutdown:
  sudo vi /etc/rc6.d/wol_poweroff.sh

  
  It may contain:
  #!/bin/bash
  ifconfig eth0 down
  poweroff

  
  Change the script's permissions to make it executable:

  sudo chmod 755 /etc/rc6.d/wol_poweroff.sh

  
  Copy the script to work on system halt as well:

  sudo cp /etc/rc6.d/wol_poweroff.sh /etc/rc0.d/wol_poweroff.sh

  
  Change permissions to make it executable:

  sudo chmod 755 /etc/rc0.d/wol_poweroff.sh

  
  Job done. 

  
  To test power down the machine, sudo shutdown now or sudo poweroff , and use 
your favourite WOL tool to send a magic packet. Thanks to rockafeller and 
everyone else who have commented with various solutions.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: ifupdown 0.7~beta2ubuntu8
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  ApportVersion: 2.0.1-0ubuntu2
  Architecture: amd64
  Date: Sat Apr 14 05:12:38 2012
  ProcEnviron:
   TERM=xterm
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ifupdown
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1580401] Re: package openssh-server 1:7.2p2-4ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-05-11 Thread Robie Basak

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

Thank you for the crash report. I'll mark this as a duplicate as we can
treat it as a single issue.

** This bug has been marked a duplicate of bug 1579978
   upgrade to 1:7.2p2-4ubuntu1 fails on ubuntu server

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

Title:
  package openssh-server 1:7.2p2-4ubuntu1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openssh package in Ubuntu:
  New

Bug description:
  This is a crash report submitted from cli for bug 1579978

  ProblemType: Package
  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: Wed May 11 09:42:48 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2013-08-11 (1003 days ago)
  InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-05-05 (5 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-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

2016-05-11 Thread Robie Basak

I've not managed to reproduce this. I tried installing upstart-sysv on a
Wily cloud image and upgrading it to Xenial. This made the systemd
preinst fail (which may be a separate bug) but I didn't see any openssh
failure. I also tried installing upstart-sysv on a Vivid cloud image and
upgrading that to Wily and then to Xenial. This worked without problems.

Installing upstart-sysv does remove ubuntu-standard as you say, so I'm
not sure this is a supported path. So I'm marking Importance as Low on
the basis that it is at least an uncommon path that will not affect the
majority of users.

I'm not sure how this might make any further progress without steps to
reproduce.

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

-- 
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 1574347] Re: WiFi network list disappears from network manager applet

2016-05-11 Thread Cip Man

No package to test yet.
The good news is that a new source, namely 1.2.2, was just released upstream 
few hours ago: https://download.gnome.org/sources/NetworkManager/1.2/

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

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 1580637] [NEW] package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv

2016-05-11 Thread Szymon Lipiński

Public bug reported:

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)

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


** Tags: amd64 apport-package need-duplicate-check 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/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 1580434] Re: kernel 4.2.0-36 causes unity to break on 15.10

2016-05-11 Thread Brian Murray

** Tags added: wily

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

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

Title:
  kernel 4.2.0-36 causes unity to break on 15.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I run Ubuntu desktop 15.10 in a Oracle VirtualBox VM. After updating the 
kernel to 4.2.0-36 Unity stopped working (after the restart). The symptoms were:
  - The screen would not use the entire real estate in either the full screen 
or the windowed mode (of the VM)
  - On entering login information, only the desktop background would display 
without dash/launcher, files on desktop or any menu or keyboard action.
  - If you started / restarted unity from a shell (Ctrl + Shift + F1 or from a 
SSH session), the desktop files and mouse/keyboard actions would work, but 
still no dash/launcher.

  The problems went away after falling back to kernel 4.2.0-35.

  If additional information is required, please let me know I will try
  my best to get that.

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

-- 
Mailing list: https://launchpad.net/~touch-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

2016-05-11 Thread Karl Rinne

plain old 15.04 OTA-10.1. Note that my music player behaves as per
Marko's original description.

-- 
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:
  New
Status in unity-scope-mediascanner package in Ubuntu:
  New
Status in unity-scopes-shell package in Ubuntu:
  New

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 1565675] Re: MTP causes too many troubles

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

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

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

Title:
  MTP causes too many troubles

Status in Canonical System Image:
  Confirmed
Status in mtp package in Ubuntu:
  Confirmed

Bug description:
  MTP causes so many problems, it's really frustrating to use.

  * Every time I plug the phone to my laptop, I get hit by an error message on 
my laptop
  * Shotwell hangs forever trying to import images from the phone, sometimes it 
doesn't even try and just errors out.
  * When it's working, the connection drops frequently

  See attached screenshots

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

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

[Touch-packages] [Bug 1580643] Re: Impossible to move or resize windows in trackpad mode

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

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

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

Title:
  Impossible to move or resize windows in trackpad mode

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  I'm using an M10 connected to an external monitor via an HDMI cable.
  The tablet screen goes black and acts as a trackpad.

  I can hold down a finger and move it to move the mouse.
  I can hold down a finger, and move a second finger to scroll lists (Unity 
dash, switch between scopes, go through emails in Dekko).

  Holding down a finger and moving it, or holding down a finger and moving a 
second one doesn't do anything on window titlebars - both work on my Unity7 
Xenial machine and move the window.
  Resizing is also not possible regardless what I try.

  This is using rc-proposed r36.

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

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

[Touch-packages] [Bug 1580643] [NEW] Impossible to move or resize windows in trackpad mode

2016-05-11 Thread Christian Dywan

Public bug reported:

I'm using an M10 connected to an external monitor via an HDMI cable. The
tablet screen goes black and acts as a trackpad.

I can hold down a finger and move it to move the mouse.
I can hold down a finger, and move a second finger to scroll lists (Unity dash, 
switch between scopes, go through emails in Dekko).

Holding down a finger and moving it, or holding down a finger and moving a 
second one doesn't do anything on window titlebars - both work on my Unity7 
Xenial machine and move the window.
Resizing is also not possible regardless what I try.

This is using rc-proposed r36.

** Affects: unity8 (Ubuntu)
 Importance: Critical
 Status: Confirmed

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

Title:
  Impossible to move or resize windows in trackpad mode

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  I'm using an M10 connected to an external monitor via an HDMI cable.
  The tablet screen goes black and acts as a trackpad.

  I can hold down a finger and move it to move the mouse.
  I can hold down a finger, and move a second finger to scroll lists (Unity 
dash, switch between scopes, go through emails in Dekko).

  Holding down a finger and moving it, or holding down a finger and moving a 
second one doesn't do anything on window titlebars - both work on my Unity7 
Xenial machine and move the window.
  Resizing is also not possible regardless what I try.

  This is using rc-proposed r36.

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

-- 
Mailing list: https://launchpad.net/~touch-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

2016-05-11 Thread Pawel Stolowski

** Changed in: unity-scope-mediascanner (Ubuntu)
   Status: New => Invalid

** Changed in: unity-scopes-shell (Ubuntu)
   Status: New => Invalid

-- 
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:
  New
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 1580394] Re: Analog Loopback Static in Headphones while on Dell Latitude 3340 Battery Power

2016-05-11 Thread spm2011

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

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

Title:
  Analog Loopback Static in Headphones while on Dell Latitude 3340
  Battery Power

Status in ubuntu-mate:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have noticed that when I am on battery power on a Dell Latitude 3340
  laptop with headphones plugged in , and there is no audio playing on
  the computer, there is a consistent static sound that comes through
  the headphones at a constant volume that is not affected by changing
  the volume level. I think it may be picking up some kind of analog
  loopback signal because keyboard presses and disk activity seem to
  influence the noise. When I plug the power cable into the laptop , the
  static immediately goes away.

  I reported this earlier to the upstream Linux Kernel bug tracker, but
  it seems to be fixed in any distro running a 4.4 kernel or greater
  that I have tested , Except for Ubuntu MATE 16.04 LTS 64-bit. This
  make me think it is not a kernel level issue and is found somewhere
  either in the audio settings on Ubuntu MATE or a pulseaudio bug. I
  cannot reproduce it on any other 16.04 distro version, but it also
  affects all the 14.04.4 distros as well.

  Running amixer -c 1 set "Loopback Mixing" "Disabled" does not prevent
  the static.

  The BIOS Firmware version is up to date.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu-mate   1718 F pulseaudio
   /dev/snd/controlC0:  ubuntu-mate   1718 F pulseaudio
  CasperVersion: 1.376
  CurrentDesktop: MATE
  Date: Wed May 11 00:43:52 2016
  LiveMediaBuild: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd11/04/2015:svnDellInc.:pnLatitude3340:pvr00:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude 3340
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1580652] [NEW] Images repaint when the shell rotates

2016-05-11 Thread Pat McGowan

Public bug reported:

Most visible in the app, video and photo scopes for me.
Tested on proposed on MX4

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

Title:
  Images repaint when the shell rotates

Status in unity8 package in Ubuntu:
  New

Bug description:
  Most visible in the app, video and photo scopes for me.
  Tested on proposed on MX4

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

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

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

2016-05-11 Thread Joakim Koed

@seb128: Do you need more info? I don't know what to do next.

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

Title:
  Can't use networkmanager from lightdm

Status in network-manager package in Ubuntu:
  Incomplete

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

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

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

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

  Feel free to ask for more info.

  Edit:

  From syslog:

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

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

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

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

hum, could you get in the buggy state, run a "sleep 10; systemd-
inhibit", close the lid, wait until the 10s are over, open it back and
see what that listed? it could be that one of the processes delaying
suspend is

-- 
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:
  Incomplete

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 1580627] Re: ComboButton is not propagating the click event

** Branch linked: lp:~zsombi/ubuntu-ui-toolkit/fixComboButton

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

Title:
  ComboButton is not propagating the click event

Status in Canonical System Image:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  ListView delegate is not receiving the click event.

  Check attached example.

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

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

[Touch-packages] [Bug 1565567] Update Released

2016-05-11 Thread Chris J Arges

The verification of the Stable Release Update for sudo 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 sudo in Ubuntu.
https://bugs.launchpad.net/bugs/1565567

Title:
  segv in sudo_getgrgid

Status in sudo:
  Unknown
Status in sudo package in Ubuntu:
  Fix Released
Status in sudo source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  In certain environments, for example when using LDAP, users can end up
  in a group with no name. When that happens, sudo crashes when
  attempting to look up the group name for the debug log.

  Upstream has commited a simple fix for this issue, it has been
  commited to Yakkety, and uploaded to Xenial.

  [Test Case]

  I currently don't know an easy way to reproduce this, it is
  environment-specific. A package containing the fix was successfully
  tested in the problematic environment.

  [Regression Potential]

  A regression in the patch would prevent users from using sudo. The
  risk of regression is low since the patch only changes the debug log.


  Original report:

  If the user is in a group with no name (because libnss-db got removed
  and the group was defined there, for example...) then:

  the call to sudo_debug_printf in sudo_getgrgid
  (plugins/sudoers/pwutil.c, line 462) causes a SEGV when trying to get
  item->d.gr->gr_name (since item->d.gr is NULL).

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

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

[Touch-packages] [Bug 1580627] Re: ComboButton is not propagating the click event

2016-05-11 Thread Zsombor Egri

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Zsombor Egri (zsombi)

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => Critical

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => In Progress

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

Title:
  ComboButton is not propagating the click event

Status in Canonical System Image:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  ListView delegate is not receiving the click event.

  Check attached example.

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

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

[Touch-packages] [Bug 1565567] Re: segv in sudo_getgrgid