[Touch-packages] [Bug 1502282] Re: "unknown" connectivity status problematic

[Kyle Nitzsche]

A problem is that the QueryMetadata.h file [1] and the public docs [2]
states that Unknown is one of the enum values. As such a scope dev needs
to handle the case.

Perhaps those texts should be modified to indicate "Unknown" will never
be the value, therefore sparing the dev the need to figure out how to
handle it.

[1]
\brief Indicates the internet connectivity status.

The `Unknown` enumerator indicates that set_internet_connectivity() has not 
yet been called,
hence the connectivity status is currently unknown.

[2]
https://developer.ubuntu.com/api/scopes/cpp/sdk-15.04.1/unity.scopes.QueryMetadata/

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

Title:
  "unknown" connectivity status problematic

Status in The Savilerow project:
  New
Status in unity-scopes-api package in Ubuntu:
  Incomplete
Status in unity-scopes-shell package in Ubuntu:
  Incomplete

Bug description:
  metadata provides a scope a network connectivity status enum with three 
possible states:
  * connected
  * disconnected
  * unknown

  Sometimes unknown is the current state. This is quite problematic
  because in general a scopes that queries the network (that is, most
  scopes) need to know whether there is network or is not network and
  depending on this either make the network queries or display an error
  message.

  A status of unknown connectivity leaves the scope with no valid option:
  * the scope could assume the network is down and provide the user an error 
message. But often the network is not actually down, so this interrupts the 
user's flow unnecessarily
  *  the scope could assume the network is up, but this is dangerous if it is 
not up

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

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

[Touch-packages] [Bug 1508357] [NEW] Tooltips have a black squares outside of its rounded corners

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Hover over any elements on a gtk apps making a tooltip appearing.

See that the tooltip is rectangular, containing rounded corner with a gradient.
However, the external part is just plain black and don't have transparency as 
expected.

** Affects: gtk+3.0 (Ubuntu)
 Importance: Medium
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: In Progress


** Tags: iso-testing
-- 
Tooltips have a black squares outside of its rounded corners
https://bugs.launchpad.net/bugs/1508357
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gtk+3.0 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 1508054] Re: [desktop] Crashes on startup

[Olivier Tilloy]

** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
   Status: New => In Progress

** Changed in: webbrowser-app (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
   Importance: Undecided => Critical

** Changed in: oxide
   Status: New => Invalid

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

Title:
  [desktop] Crashes on startup

Status in Oxide:
  Invalid
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  For a little while now on my development machine (which is a
  Frankenstein environment anyway), which is running wily+overlay,
  webbrowser-app has been crashing on startup.  The console output is
  below.  It looks like a permissions issue?  It may have started around
  the time that webbrowser-app got AppArmor support...

  I don't seem to have a file in /var/crash.  I don't seem to have *any*
  files in /var/crash...  But maybe this log is enough for now.

  
  (webbrowser-app:12313): dconf-CRITICAL **: unable to create file 
'/run/user/1001/dconf/user': Permission denied.  dconf will not work properly.

  (webbrowser-app:12313): dconf-CRITICAL **: unable to create file
  '/run/user/1001/dconf/user': Permission denied.  dconf will not work
  properly.

  (webbrowser-app:12313): dconf-CRITICAL **: unable to create file 
'/run/user/1001/dconf/user': Permission denied.  dconf will not work properly.
  org.gtk.vfs.MountTracker.listMountableInfo call failed: 
GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy 
prevents this sender from sending this message to this recipient; 
type="method_call", sender=":1.148" (uid=1001 pid=12313 comm="webbrowser-app ") 
interface="org.gtk.vfs.MountTracker" member="ListMountableInfo" error 
name="(unset)" requested_reply="0" destination=":1.9" (uid=1001 pid=3669 
comm="/usr/lib/gvfs/gvfsd ") (g-dbus-error-quark, 9)
  shm_open() failed: Permission denied
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/1.3/Sections.qml:96: 
TypeError: Cannot read property 'length' of undefined
  qml: Loaded 3 UA override(s) from 
file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Web/ua-overrides-desktop.js
  [1020/092321:ERROR:shared_memory_posix.cc(290)] Creating shared memory in 
/dev/shm/.org.chromium.Chromium.nxp9C4 failed: Permission denied
  [1020/092321:ERROR:webgraphicscontext3d_command_buffer_impl.cc(210)] 
CommandBufferProxy::Initialize failed.
  [1020/092321:ERROR:webgraphicscontext3d_command_buffer_impl.cc(229)] Failed 
to initialize command buffer.
  [1020/092321:ERROR:shared_memory_posix.cc(290)] Creating shared memory in 
/dev/shm/.org.chromium.Chromium.jaBUVR failed: Permission denied
  [1020/092321:ERROR:shared_memory_posix.cc(290)] Creating shared memory in 
/dev/shm/.org.chromium.Chromium.5McNeF failed: Permission denied
  [1020/092321:ERROR:webgraphicscontext3d_command_buffer_impl.cc(210)] 
CommandBufferProxy::Initialize failed.
  [1020/092321:ERROR:webgraphicscontext3d_command_buffer_impl.cc(229)] Failed 
to initialize command buffer.
  [1020/092321:ERROR:shared_memory_posix.cc(290)] Creating shared memory in 
/dev/shm/.org.chromium.Chromium.O6PKxs failed: Permission denied
  [1020/092321:ERROR:webgraphicscontext3d_command_buffer_impl.cc(210)] 
CommandBufferProxy::Initialize failed.
  [1020/092321:ERROR:webgraphicscontext3d_command_buffer_impl.cc(229)] Failed 
to initialize command buffer.
  [1020/092321:ERROR:shared_memory_posix.cc(290)] Creating shared memory in 
/dev/shm/.org.chromium.Chromium.qbYMQf failed: Permission denied
  [1020/092321:ERROR:webgraphicscontext3d_command_buffer_impl.cc(210)] 
CommandBufferProxy::Initialize failed.
  [1020/092321:ERROR:webgraphicscontext3d_command_buffer_impl.cc(229)] Failed 
to initialize command buffer.
  [1020/092321:ERROR:shared_memory_posix.cc(290)] Creating shared memory in 
/dev/shm/.org.chromium.Chromium.6o0292 failed: Permission denied
  [1020/092321:ERROR:webgraphicscontext3d_command_buffer_impl.cc(210)] 
CommandBufferProxy::Initialize failed.
  [1020/092321:ERROR:webgraphicscontext3d_command_buffer_impl.cc(229)] Failed 
to initialize command buffer.
  [1020/092321:FATAL:oxide_compositor.cc(185)] Check failed: 
num_failed_recreate_attempts_ <= 4 (5 vs. 4)
  Aborted

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

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

[Touch-packages] [Bug 1508357] Re: Tooltips have a black squares outside of its rounded corners

[Sebastien Bacher]

** Package changed: ubuntu => gtk+3.0 (Ubuntu)

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

Title:
  Tooltips have a black squares outside of its rounded corners

Status in gtk+3.0 package in Ubuntu:
  In Progress

Bug description:
  Hover over any elements on a gtk apps making a tooltip appearing.

  See that the tooltip is rectangular, containing rounded corner with a 
gradient.
  However, the external part is just plain black and don't have transparency as 
expected.

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

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

[Touch-packages] [Bug 1508337] Re: [devel-proposed] The mobile phone no response after top on Restart option.

[Pat McGowan]

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

** Summary changed:

- [devel-proposed] The mobile phone no response after top on Restart option.
+ Wily: The mobile phone no response after top on Restart option.

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

Title:
  Wily: The mobile phone no response after top on Restart option.

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

Bug description:
  ~$ system-image-cli -i
  current build number: 144
  device name: arale
  channel: ubuntu-touch/devel-proposed/meizu.en
  last update: 2015-10-21 02:58:07
  version version: 144
  version ubuntu: 20151020
  version device: 20151016-0b38025
  version custom: 20150925-900-8-47
  phablet@ubuntu-phablet:~$

  Reproduce steps:

  step 1:Long press off button.

  step 2:Top on Restart option.

  Actual result:
  The mobile phone no response after top on Restart.

  Expected result:

  Mobile phone reboot normally after top on Restart.

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

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

[Touch-packages] [Bug 1508054] Re: [desktop] Crashes on startup

[Launchpad Bug Tracker]

** Branch linked: lp:~osomon/apparmor-easyprof-ubuntu/webview-allow-dev-
shm

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

Title:
  [desktop] Crashes on startup

Status in Oxide:
  Invalid
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  For a little while now on my development machine (which is a
  Frankenstein environment anyway), which is running wily+overlay,
  webbrowser-app has been crashing on startup.  The console output is
  below.  It looks like a permissions issue?  It may have started around
  the time that webbrowser-app got AppArmor support...

  I don't seem to have a file in /var/crash.  I don't seem to have *any*
  files in /var/crash...  But maybe this log is enough for now.

  
  (webbrowser-app:12313): dconf-CRITICAL **: unable to create file 
'/run/user/1001/dconf/user': Permission denied.  dconf will not work properly.

  (webbrowser-app:12313): dconf-CRITICAL **: unable to create file
  '/run/user/1001/dconf/user': Permission denied.  dconf will not work
  properly.

  (webbrowser-app:12313): dconf-CRITICAL **: unable to create file 
'/run/user/1001/dconf/user': Permission denied.  dconf will not work properly.
  org.gtk.vfs.MountTracker.listMountableInfo call failed: 
GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy 
prevents this sender from sending this message to this recipient; 
type="method_call", sender=":1.148" (uid=1001 pid=12313 comm="webbrowser-app ") 
interface="org.gtk.vfs.MountTracker" member="ListMountableInfo" error 
name="(unset)" requested_reply="0" destination=":1.9" (uid=1001 pid=3669 
comm="/usr/lib/gvfs/gvfsd ") (g-dbus-error-quark, 9)
  shm_open() failed: Permission denied
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/1.3/Sections.qml:96: 
TypeError: Cannot read property 'length' of undefined
  qml: Loaded 3 UA override(s) from 
file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Web/ua-overrides-desktop.js
  [1020/092321:ERROR:shared_memory_posix.cc(290)] Creating shared memory in 
/dev/shm/.org.chromium.Chromium.nxp9C4 failed: Permission denied
  [1020/092321:ERROR:webgraphicscontext3d_command_buffer_impl.cc(210)] 
CommandBufferProxy::Initialize failed.
  [1020/092321:ERROR:webgraphicscontext3d_command_buffer_impl.cc(229)] Failed 
to initialize command buffer.
  [1020/092321:ERROR:shared_memory_posix.cc(290)] Creating shared memory in 
/dev/shm/.org.chromium.Chromium.jaBUVR failed: Permission denied
  [1020/092321:ERROR:shared_memory_posix.cc(290)] Creating shared memory in 
/dev/shm/.org.chromium.Chromium.5McNeF failed: Permission denied
  [1020/092321:ERROR:webgraphicscontext3d_command_buffer_impl.cc(210)] 
CommandBufferProxy::Initialize failed.
  [1020/092321:ERROR:webgraphicscontext3d_command_buffer_impl.cc(229)] Failed 
to initialize command buffer.
  [1020/092321:ERROR:shared_memory_posix.cc(290)] Creating shared memory in 
/dev/shm/.org.chromium.Chromium.O6PKxs failed: Permission denied
  [1020/092321:ERROR:webgraphicscontext3d_command_buffer_impl.cc(210)] 
CommandBufferProxy::Initialize failed.
  [1020/092321:ERROR:webgraphicscontext3d_command_buffer_impl.cc(229)] Failed 
to initialize command buffer.
  [1020/092321:ERROR:shared_memory_posix.cc(290)] Creating shared memory in 
/dev/shm/.org.chromium.Chromium.qbYMQf failed: Permission denied
  [1020/092321:ERROR:webgraphicscontext3d_command_buffer_impl.cc(210)] 
CommandBufferProxy::Initialize failed.
  [1020/092321:ERROR:webgraphicscontext3d_command_buffer_impl.cc(229)] Failed 
to initialize command buffer.
  [1020/092321:ERROR:shared_memory_posix.cc(290)] Creating shared memory in 
/dev/shm/.org.chromium.Chromium.6o0292 failed: Permission denied
  [1020/092321:ERROR:webgraphicscontext3d_command_buffer_impl.cc(210)] 
CommandBufferProxy::Initialize failed.
  [1020/092321:ERROR:webgraphicscontext3d_command_buffer_impl.cc(229)] Failed 
to initialize command buffer.
  [1020/092321:FATAL:oxide_compositor.cc(185)] Check failed: 
num_failed_recreate_attempts_ <= 4 (5 vs. 4)
  Aborted

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

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

[Touch-packages] [Bug 1508468] [NEW] Users are forced to wade through unknown networks to single out the network/s they have previously connected to in the past

[Greg Williams]

Public bug reported:

The summary pretty much tells the tale: users are forced to wade through
unknown networks to single out the network/s they have previously
connected to in the past.

I go to a location. Twenty some networks are available. Most of them
appear in the "More Networks" folder. Five networks appear outside the
"More Networks" folder. Despite the fact that I ONLY EVER connect maybe
two networks, other networks that I never ever connect to are always
displayed.

Why are networks that I have never connected to (and never will connect
to) ALWAYS displayed in the menu? Why aren't they confined to the "More
Networks" folder until connected to at least one time.

Previously, I proposed a solution: confine networks that have NEVER been
connected to in the "More Networks" folder. Once a connection has been
established, move it out of the "More Networks" folder.  I'm told most
users allow automatic wifi connections: so users only have to look ONE
TIME, the first time they connect to a foreign (never before seen)
network.

the current system presents two usability problems. If automatic
connection is turned on and more than one network has been connected to
in the past, the system does not know which network the user wants THIS
TIME. And yet the user has to wade through networks they have never
connected to and will never connect to to locate the networks they have
to connected to in the past (there has to be a better way to organize
this). Second, if the user does not allow automatic connections for
security/privacy/battery reasons, the user is forced to wade through
networks he/she has never connected to and will never connect every time
he/she wants to make a wifi connection.

Since my previous proposal was shot down, can ubuntu engineers please
come up with a solution to this usability problem (as Matthew Paul
Thomas has you are more capable of doing). Matthew Paul Thomas has
invalidated my "simple" solution that would inconvenience no one:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1425991

I'm told most users autoconnect. So they want to see the networks right
away, but this is nonsense. There are often so many networks, they HAVE
to look in "More Networks" anyways.

** Affects: indicator-network (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Users are forced to wade through unknown networks to single out the
  network/s they have previously connected to in the past

Status in indicator-network package in Ubuntu:
  New

Bug description:
  The summary pretty much tells the tale: users are forced to wade
  through unknown networks to single out the network/s they have
  previously connected to in the past.

  I go to a location. Twenty some networks are available. Most of them
  appear in the "More Networks" folder. Five networks appear outside the
  "More Networks" folder. Despite the fact that I ONLY EVER connect
  maybe two networks, other networks that I never ever connect to are
  always displayed.

  Why are networks that I have never connected to (and never will
  connect to) ALWAYS displayed in the menu? Why aren't they confined to
  the "More Networks" folder until connected to at least one time.

  Previously, I proposed a solution: confine networks that have NEVER
  been connected to in the "More Networks" folder. Once a connection has
  been established, move it out of the "More Networks" folder.  I'm told
  most users allow automatic wifi connections: so users only have to
  look ONE TIME, the first time they connect to a foreign (never before
  seen) network.

  the current system presents two usability problems. If automatic
  connection is turned on and more than one network has been connected
  to in the past, the system does not know which network the user wants
  THIS TIME. And yet the user has to wade through networks they have
  never connected to and will never connect to to locate the networks
  they have to connected to in the past (there has to be a better way to
  organize this). Second, if the user does not allow automatic
  connections for security/privacy/battery reasons, the user is forced
  to wade through networks he/she has never connected to and will never
  connect every time he/she wants to make a wifi connection.

  Since my previous proposal was shot down, can ubuntu engineers please
  come up with a solution to this usability problem (as Matthew Paul
  Thomas has you are more capable of doing). Matthew Paul Thomas has
  invalidated my "simple" solution that would inconvenience no one:
  https://bugs.launchpad.net/ubuntu/+source/indicator-
  network/+bug/1425991

  I'm told most users autoconnect. So they want to see the networks
  right away, but this is nonsense. There are often so many networks,
  they HAVE to look in "More 

[Touch-packages] [Bug 1337873] Re: Precise, Trusty, Utopic - ifupdown initialization problems caused by race condition

[Dariusz Gadomski]

Adding SRU proposal for wily.

** Description changed:

+ [Impact]
+ 
+  * A lack of proper synchronization in ifupdown causes a race condition
+ resulting in occasional incorrect network interface initialization (e.g.
+ in bonding case - wrong bonding settings, network unavailable because
+ slave<->master interfaces initialization order was wrong
+ 
+  * This is very annoying in case of large deployments (e.g. when
+ bringing up 1000 machines it is almost guaranteed that at least a few of
+ them will end up with network down).
+ 
+  * It has been fixed by introducing hierarchical and per-interface
+ locking mechanism ensuring the right order (along with the correct order
+ in the /e/n/interfaces file) of initialization
+ 
+ [Test Case]
+ 
+  1. Create a VM with bonding configured with at least 2 slave interfaces.
+  2. Reboot.
+  3. If all interfaces are up - go to 2.
+ 
+ [Regression Potential]
+ 
+  * This change has been introduced upstream in Debian.
+  * It does not require any config changes to existing installations.
+ 
+ [Other Info]
+  
+ Original bug description:
+ 
  * please consider my bonding examples are using eth1 and eth2 as slave
-  interfaces.
+  interfaces.
  
  ifupdown some race conditions explained bellow. ifenslave does not
  behave well with sysv networking and upstart network-interface scripts
  running together.
  
  
  case 1)
  (a) ifup eth0 (b) ifup -a for eth0
  -
  1-1. Lock ifstate.lock file.
-   1-1. Wait for locking ifstate.lock
-   file.
+   1-1. Wait for locking ifstate.lock
+   file.
  1-2. Read ifstate file to check
-  the target NIC.
+  the target NIC.
  1-3. close(=release) ifstate.lock
-  file.
+  file.
  1-4. Judge that the target NIC
-  isn't processed.
-   1-2. Read ifstate file to check
-the target NIC.
-   1-3. close(=release) ifstate.lock
-file.
-   1-4. Judge that the target NIC
-isn't processed.
+  isn't processed.
+   1-2. Read ifstate file to check
+    the target NIC.
+   1-3. close(=release) ifstate.lock
+    file.
+   1-4. Judge that the target NIC
+    isn't processed.
  2. Lock and update ifstate file.
-Release the lock.
-   2. Lock and update ifstate file.
-  Release the lock.
+    Release the lock.
+   2. Lock and update ifstate file.
+  Release the lock.
  !!!
  
  to be explained
  
  !!!
  case 2)
  (a) ifenslave of eth0  (b) ifenslave of eth0
  --
  3. Execute ifenslave of eth0.  3. Execute ifenslave of eth0.
  4. Link down the target NIC.
  5. Write NIC id to
-/sys/class/net/bond0/bonding
-/slaves then NIC gets up
-   4. Link down the target NIC.
-   5. Fails to write NIC id to
-  /sys/class/net/bond0/bonding/
-  slaves it is already written.
+    /sys/class/net/bond0/bonding
+    /slaves then NIC gets up
+   4. Link down the target NIC.
+   5. Fails to write NIC id to
+  /sys/class/net/bond0/bonding/
+  slaves it is already written.
  !!!
  
  #
  
   My setup:
  
  root@provisioned:~# cat /etc/modprobe.d/bonding.conf
  alias bond0 bonding options bonding mode=1 arp_interval=2000
  
  Both, /etc/init.d/networking and upstart network-interface begin
  enabled.
  
   Beginning:
  
  root@provisioned:~# cat /etc/network/interfaces
  # /etc/network/interfaces
  
  auto lo
  iface lo inet loopback
  
  auto eth0
  iface eth0 inet dhcp
  
  I'm able to boot with both scripts (networking and network-interface
- enabled) with no problem. I can also boot with only "networking" 
+ enabled) with no problem. I can also boot with only "networking"
  script enabled:
  
  ---
  root@provisioned:~# initctl list | grep network
  network-interface stop/waiting
  networking start/running
  ---
  
  OR only the script "network-interface" enabled:
  
  ---
  root@provisioned:~# initctl list | grep network
  network-interface (eth2) start/running
  

[Touch-packages] [Bug 1337873] Re: Precise, Trusty, Utopic - ifupdown initialization problems caused by race condition

[Dariusz Gadomski]

Adding SRU proposal for Vivid.

** Patch added: "vivid_ifupdown_0.7.48.1ubuntu11.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1337873/+attachment/4501798/+files/vivid_ifupdown_0.7.48.1ubuntu11.debdiff

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

Title:
  Precise, Trusty, Utopic - ifupdown initialization problems caused by
  race condition

Status in ifupdown package in Ubuntu:
  In Progress
Status in ifupdown source package in Precise:
  Confirmed
Status in ifupdown source package in Trusty:
  Confirmed
Status in ifupdown source package in Vivid:
  Confirmed
Status in ifupdown package in Debian:
  New

Bug description:
  [Impact]

   * A lack of proper synchronization in ifupdown causes a race
  condition resulting in occasional incorrect network interface
  initialization (e.g. in bonding case - wrong bonding settings, network
  unavailable because slave<->master interfaces initialization order was
  wrong

   * This is very annoying in case of large deployments (e.g. when
  bringing up 1000 machines it is almost guaranteed that at least a few
  of them will end up with network down).

   * It has been fixed by introducing hierarchical and per-interface
  locking mechanism ensuring the right order (along with the correct
  order in the /e/n/interfaces file) of initialization

  [Test Case]

   1. Create a VM with bonding configured with at least 2 slave interfaces.
   2. Reboot.
   3. If all interfaces are up - go to 2.

  [Regression Potential]

   * This change has been introduced upstream in Debian.
   * It does not require any config changes to existing installations.

  [Other Info]
   
  Original bug description:

  * please consider my bonding examples are using eth1 and eth2 as slave
   interfaces.

  ifupdown some race conditions explained bellow. ifenslave does not
  behave well with sysv networking and upstart network-interface scripts
  running together.

  
  case 1)
  (a) ifup eth0 (b) ifup -a for eth0
  -
  1-1. Lock ifstate.lock file.
    1-1. Wait for locking ifstate.lock
    file.
  1-2. Read ifstate file to check
   the target NIC.
  1-3. close(=release) ifstate.lock
   file.
  1-4. Judge that the target NIC
   isn't processed.
    1-2. Read ifstate file to check
     the target NIC.
    1-3. close(=release) ifstate.lock
     file.
    1-4. Judge that the target NIC
     isn't processed.
  2. Lock and update ifstate file.
     Release the lock.
    2. Lock and update ifstate file.
   Release the lock.
  !!!

  to be explained

  !!!
  case 2)
  (a) ifenslave of eth0  (b) ifenslave of eth0
  --
  3. Execute ifenslave of eth0.  3. Execute ifenslave of eth0.
  4. Link down the target NIC.
  5. Write NIC id to
     /sys/class/net/bond0/bonding
     /slaves then NIC gets up
    4. Link down the target NIC.
    5. Fails to write NIC id to
   /sys/class/net/bond0/bonding/
   slaves it is already written.
  !!!

  #

   My setup:

  root@provisioned:~# cat /etc/modprobe.d/bonding.conf
  alias bond0 bonding options bonding mode=1 arp_interval=2000

  Both, /etc/init.d/networking and upstart network-interface begin
  enabled.

   Beginning:

  root@provisioned:~# cat /etc/network/interfaces
  # /etc/network/interfaces

  auto lo
  iface lo inet loopback

  auto eth0
  iface eth0 inet dhcp

  I'm able to boot with both scripts (networking and network-interface
  enabled) with no problem. I can also boot with only "networking"
  script enabled:

  ---
  root@provisioned:~# initctl list | grep network
  network-interface stop/waiting
  networking start/running
  ---

  OR only the script "network-interface" enabled:

  ---
  root@provisioned:~# initctl list | grep network
  network-interface (eth2) start/running
  network-interface (lo) start/running
  network-interface (eth0) start/running
  network-interface (eth1) start/running
  ---

   Enabling bonding:

  Following ifenslave configuration example (/usr/share/doc/ifenslave/
  examples/two_hotplug_ethernet), my /etc/network/interfaces has to
  look like this:

  ---
  auto eth1
  iface eth1 inet manual
  bond-master bond0

  auto eth2
  iface eth2 inet manual
  bond-master 

[Touch-packages] [Bug 1337873] Re: Precise, Trusty, Utopic - ifupdown initialization problems caused by race condition

[Dariusz Gadomski]

Adding SRU proposal for Trusty (to make ifenslave compatible with
ifupdown changes).

** Patch added: "trusty_ifenslave_2.4ubuntu1.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1337873/+attachment/4501800/+files/trusty_ifenslave_2.4ubuntu1.2.debdiff

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

Title:
  Precise, Trusty, Utopic - ifupdown initialization problems caused by
  race condition

Status in ifupdown package in Ubuntu:
  In Progress
Status in ifupdown source package in Precise:
  Confirmed
Status in ifupdown source package in Trusty:
  Confirmed
Status in ifupdown source package in Vivid:
  Confirmed
Status in ifupdown package in Debian:
  New

Bug description:
  [Impact]

   * A lack of proper synchronization in ifupdown causes a race
  condition resulting in occasional incorrect network interface
  initialization (e.g. in bonding case - wrong bonding settings, network
  unavailable because slave<->master interfaces initialization order was
  wrong

   * This is very annoying in case of large deployments (e.g. when
  bringing up 1000 machines it is almost guaranteed that at least a few
  of them will end up with network down).

   * It has been fixed by introducing hierarchical and per-interface
  locking mechanism ensuring the right order (along with the correct
  order in the /e/n/interfaces file) of initialization

  [Test Case]

   1. Create a VM with bonding configured with at least 2 slave interfaces.
   2. Reboot.
   3. If all interfaces are up - go to 2.

  [Regression Potential]

   * This change has been introduced upstream in Debian.
   * It does not require any config changes to existing installations.

  [Other Info]
   
  Original bug description:

  * please consider my bonding examples are using eth1 and eth2 as slave
   interfaces.

  ifupdown some race conditions explained bellow. ifenslave does not
  behave well with sysv networking and upstart network-interface scripts
  running together.

  
  case 1)
  (a) ifup eth0 (b) ifup -a for eth0
  -
  1-1. Lock ifstate.lock file.
    1-1. Wait for locking ifstate.lock
    file.
  1-2. Read ifstate file to check
   the target NIC.
  1-3. close(=release) ifstate.lock
   file.
  1-4. Judge that the target NIC
   isn't processed.
    1-2. Read ifstate file to check
     the target NIC.
    1-3. close(=release) ifstate.lock
     file.
    1-4. Judge that the target NIC
     isn't processed.
  2. Lock and update ifstate file.
     Release the lock.
    2. Lock and update ifstate file.
   Release the lock.
  !!!

  to be explained

  !!!
  case 2)
  (a) ifenslave of eth0  (b) ifenslave of eth0
  --
  3. Execute ifenslave of eth0.  3. Execute ifenslave of eth0.
  4. Link down the target NIC.
  5. Write NIC id to
     /sys/class/net/bond0/bonding
     /slaves then NIC gets up
    4. Link down the target NIC.
    5. Fails to write NIC id to
   /sys/class/net/bond0/bonding/
   slaves it is already written.
  !!!

  #

   My setup:

  root@provisioned:~# cat /etc/modprobe.d/bonding.conf
  alias bond0 bonding options bonding mode=1 arp_interval=2000

  Both, /etc/init.d/networking and upstart network-interface begin
  enabled.

   Beginning:

  root@provisioned:~# cat /etc/network/interfaces
  # /etc/network/interfaces

  auto lo
  iface lo inet loopback

  auto eth0
  iface eth0 inet dhcp

  I'm able to boot with both scripts (networking and network-interface
  enabled) with no problem. I can also boot with only "networking"
  script enabled:

  ---
  root@provisioned:~# initctl list | grep network
  network-interface stop/waiting
  networking start/running
  ---

  OR only the script "network-interface" enabled:

  ---
  root@provisioned:~# initctl list | grep network
  network-interface (eth2) start/running
  network-interface (lo) start/running
  network-interface (eth0) start/running
  network-interface (eth1) start/running
  ---

   Enabling bonding:

  Following ifenslave configuration example (/usr/share/doc/ifenslave/
  examples/two_hotplug_ethernet), my /etc/network/interfaces has to
  look like this:

  ---
  auto eth1
  iface eth1 inet manual
  bond-master bond0

  auto 

[Touch-packages] [Bug 1337873] Re: Precise, Trusty, Utopic - ifupdown initialization problems caused by race condition

[Dariusz Gadomski]

Adding SRU proposal for Trusty.

** Patch added: "trusty_ifupdown_0.7.47.2ubuntu4.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1337873/+attachment/4501799/+files/trusty_ifupdown_0.7.47.2ubuntu4.2.debdiff

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

Title:
  Precise, Trusty, Utopic - ifupdown initialization problems caused by
  race condition

Status in ifupdown package in Ubuntu:
  In Progress
Status in ifupdown source package in Precise:
  Confirmed
Status in ifupdown source package in Trusty:
  Confirmed
Status in ifupdown source package in Vivid:
  Confirmed
Status in ifupdown package in Debian:
  New

Bug description:
  [Impact]

   * A lack of proper synchronization in ifupdown causes a race
  condition resulting in occasional incorrect network interface
  initialization (e.g. in bonding case - wrong bonding settings, network
  unavailable because slave<->master interfaces initialization order was
  wrong

   * This is very annoying in case of large deployments (e.g. when
  bringing up 1000 machines it is almost guaranteed that at least a few
  of them will end up with network down).

   * It has been fixed by introducing hierarchical and per-interface
  locking mechanism ensuring the right order (along with the correct
  order in the /e/n/interfaces file) of initialization

  [Test Case]

   1. Create a VM with bonding configured with at least 2 slave interfaces.
   2. Reboot.
   3. If all interfaces are up - go to 2.

  [Regression Potential]

   * This change has been introduced upstream in Debian.
   * It does not require any config changes to existing installations.

  [Other Info]
   
  Original bug description:

  * please consider my bonding examples are using eth1 and eth2 as slave
   interfaces.

  ifupdown some race conditions explained bellow. ifenslave does not
  behave well with sysv networking and upstart network-interface scripts
  running together.

  
  case 1)
  (a) ifup eth0 (b) ifup -a for eth0
  -
  1-1. Lock ifstate.lock file.
    1-1. Wait for locking ifstate.lock
    file.
  1-2. Read ifstate file to check
   the target NIC.
  1-3. close(=release) ifstate.lock
   file.
  1-4. Judge that the target NIC
   isn't processed.
    1-2. Read ifstate file to check
     the target NIC.
    1-3. close(=release) ifstate.lock
     file.
    1-4. Judge that the target NIC
     isn't processed.
  2. Lock and update ifstate file.
     Release the lock.
    2. Lock and update ifstate file.
   Release the lock.
  !!!

  to be explained

  !!!
  case 2)
  (a) ifenslave of eth0  (b) ifenslave of eth0
  --
  3. Execute ifenslave of eth0.  3. Execute ifenslave of eth0.
  4. Link down the target NIC.
  5. Write NIC id to
     /sys/class/net/bond0/bonding
     /slaves then NIC gets up
    4. Link down the target NIC.
    5. Fails to write NIC id to
   /sys/class/net/bond0/bonding/
   slaves it is already written.
  !!!

  #

   My setup:

  root@provisioned:~# cat /etc/modprobe.d/bonding.conf
  alias bond0 bonding options bonding mode=1 arp_interval=2000

  Both, /etc/init.d/networking and upstart network-interface begin
  enabled.

   Beginning:

  root@provisioned:~# cat /etc/network/interfaces
  # /etc/network/interfaces

  auto lo
  iface lo inet loopback

  auto eth0
  iface eth0 inet dhcp

  I'm able to boot with both scripts (networking and network-interface
  enabled) with no problem. I can also boot with only "networking"
  script enabled:

  ---
  root@provisioned:~# initctl list | grep network
  network-interface stop/waiting
  networking start/running
  ---

  OR only the script "network-interface" enabled:

  ---
  root@provisioned:~# initctl list | grep network
  network-interface (eth2) start/running
  network-interface (lo) start/running
  network-interface (eth0) start/running
  network-interface (eth1) start/running
  ---

   Enabling bonding:

  Following ifenslave configuration example (/usr/share/doc/ifenslave/
  examples/two_hotplug_ethernet), my /etc/network/interfaces has to
  look like this:

  ---
  auto eth1
  iface eth1 inet manual
  bond-master bond0

  auto eth2
  iface eth2 inet manual
  

[Touch-packages] [Bug 1508054] Re: [desktop] Crashes on startup

[Launchpad Bug Tracker]

** Branch linked: lp:~osomon/webbrowser-app/aa-profile-allow-dev-shm

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

Title:
  [desktop] Crashes on startup

Status in Oxide:
  Invalid
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Triaged
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  For a little while now on my development machine (which is a
  Frankenstein environment anyway), which is running wily+overlay,
  webbrowser-app has been crashing on startup.  The console output is
  below.  It looks like a permissions issue?  It may have started around
  the time that webbrowser-app got AppArmor support...

  I don't seem to have a file in /var/crash.  I don't seem to have *any*
  files in /var/crash...  But maybe this log is enough for now.

  
  (webbrowser-app:12313): dconf-CRITICAL **: unable to create file 
'/run/user/1001/dconf/user': Permission denied.  dconf will not work properly.

  (webbrowser-app:12313): dconf-CRITICAL **: unable to create file
  '/run/user/1001/dconf/user': Permission denied.  dconf will not work
  properly.

  (webbrowser-app:12313): dconf-CRITICAL **: unable to create file 
'/run/user/1001/dconf/user': Permission denied.  dconf will not work properly.
  org.gtk.vfs.MountTracker.listMountableInfo call failed: 
GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy 
prevents this sender from sending this message to this recipient; 
type="method_call", sender=":1.148" (uid=1001 pid=12313 comm="webbrowser-app ") 
interface="org.gtk.vfs.MountTracker" member="ListMountableInfo" error 
name="(unset)" requested_reply="0" destination=":1.9" (uid=1001 pid=3669 
comm="/usr/lib/gvfs/gvfsd ") (g-dbus-error-quark, 9)
  shm_open() failed: Permission denied
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/1.3/Sections.qml:96: 
TypeError: Cannot read property 'length' of undefined
  qml: Loaded 3 UA override(s) from 
file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Web/ua-overrides-desktop.js
  [1020/092321:ERROR:shared_memory_posix.cc(290)] Creating shared memory in 
/dev/shm/.org.chromium.Chromium.nxp9C4 failed: Permission denied
  [1020/092321:ERROR:webgraphicscontext3d_command_buffer_impl.cc(210)] 
CommandBufferProxy::Initialize failed.
  [1020/092321:ERROR:webgraphicscontext3d_command_buffer_impl.cc(229)] Failed 
to initialize command buffer.
  [1020/092321:ERROR:shared_memory_posix.cc(290)] Creating shared memory in 
/dev/shm/.org.chromium.Chromium.jaBUVR failed: Permission denied
  [1020/092321:ERROR:shared_memory_posix.cc(290)] Creating shared memory in 
/dev/shm/.org.chromium.Chromium.5McNeF failed: Permission denied
  [1020/092321:ERROR:webgraphicscontext3d_command_buffer_impl.cc(210)] 
CommandBufferProxy::Initialize failed.
  [1020/092321:ERROR:webgraphicscontext3d_command_buffer_impl.cc(229)] Failed 
to initialize command buffer.
  [1020/092321:ERROR:shared_memory_posix.cc(290)] Creating shared memory in 
/dev/shm/.org.chromium.Chromium.O6PKxs failed: Permission denied
  [1020/092321:ERROR:webgraphicscontext3d_command_buffer_impl.cc(210)] 
CommandBufferProxy::Initialize failed.
  [1020/092321:ERROR:webgraphicscontext3d_command_buffer_impl.cc(229)] Failed 
to initialize command buffer.
  [1020/092321:ERROR:shared_memory_posix.cc(290)] Creating shared memory in 
/dev/shm/.org.chromium.Chromium.qbYMQf failed: Permission denied
  [1020/092321:ERROR:webgraphicscontext3d_command_buffer_impl.cc(210)] 
CommandBufferProxy::Initialize failed.
  [1020/092321:ERROR:webgraphicscontext3d_command_buffer_impl.cc(229)] Failed 
to initialize command buffer.
  [1020/092321:ERROR:shared_memory_posix.cc(290)] Creating shared memory in 
/dev/shm/.org.chromium.Chromium.6o0292 failed: Permission denied
  [1020/092321:ERROR:webgraphicscontext3d_command_buffer_impl.cc(210)] 
CommandBufferProxy::Initialize failed.
  [1020/092321:ERROR:webgraphicscontext3d_command_buffer_impl.cc(229)] Failed 
to initialize command buffer.
  [1020/092321:FATAL:oxide_compositor.cc(185)] Check failed: 
num_failed_recreate_attempts_ <= 4 (5 vs. 4)
  Aborted

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

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

[Touch-packages] [Bug 1445436] Re: Segmentation faults in libapt-pkg.so.4.12.0

[Clement Lefebvre]

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

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

Title:
  Segmentation faults in libapt-pkg.so.4.12.0

Status in Linux Mint:
  Confirmed
Status in apt package in Ubuntu:
  Confirmed

Bug description:
  For no obvious reason whatsoever it is now completely impossible for
  me to use APT. Furthermore it is completely impossible for me to
  report a bug with apport.

  apport-gtk[4025]: segfault at aca04d24 ip b4b622f1 sp aebe7240 error 6 in 
libapt-pkg.so.4.12.0[b4a8c000+125000]
  apt-get[4087]: segfault at b58bed24 ip b768c2f1 sp bfc6d800 error 6 in 
libapt-pkg.so.4.12.0[b75b6000+125000]
  apt-cache[4827]: segfault at b58fbd24 ip b76c82f1 sp bfc7ece0 error 6 in 
libapt-pkg.so.4.12.0[b75f2000+125000]
  apport-gtk[4886]: segfault at ab92fd24 ip b4b8d2f1 sp b46d4240 error 6 in 
libapt-pkg.so.4.12.0[b4ab7000+125000]
  apt-get[4929]: segfault at b5953d24 ip b77212f1 sp bfb75f40 error 6 in 
libapt-pkg.so.4.12.0[b764b000+125000]
  apt-get[5110]: segfault at b58c9d24 ip b7697281 sp bf9cf750 error 6 in 
libapt-pkg.so.4.12.0[b75c1000+125000]
  apt-get[5258]: segfault at b58f0d24 ip b76bd281 sp bfa1fe40 error 6 in 
libapt-pkg.so.4.12.0[b75e7000+125000]
  apt-get[5381]: segfault at b58bad24 ip b7687281 sp bfdaf300 error 6 in 
libapt-pkg.so.4.12.0[b75b1000+125000]
  apt-get[5991]: segfault at b595ed24 ip b772c281 sp bff062a0 error 6 in 
libapt-pkg.so.4.12.0[b7656000+125000]
  apt-get[6104]: segfault at b5982d24 ip b7750281 sp bfdbeee0 error 6 in 
libapt-pkg.so.4.12.0[b767a000+125000]
  apt-get[6279]: segfault at b597dd24 ip b774b281 sp bfab9600 error 6 in 
libapt-pkg.so.4.12.0[b7675000+125000]
  apt-get[6814]: segfault at b58b4d24 ip b7682281 sp bfb1efe0 error 6 in 
libapt-pkg.so.4.12.0[b75ac000+125000]

  I have tried reinstalling libapt-
  pkg4.12_0.8.16~exp12ubuntu10.21_i386.deb but nothing changes.

  Last upgrade log:

  Start-Date: 2015-04-15  00:39:51
  Commandline: /usr/bin/apt-get dist-upgrade
  Upgrade: libsdl1.2debian:i386 (1.2.14-6.4ubuntu3, 1.2.14-6.4ubuntu3.1), 
libxfixes3:i386 (5.0-4ubuntu4.3, 5.0-4ubuntu4.4), libx11-data:i386 
(1.4.99.1-0ubuntu2.2, 1.4.99.1-0ubuntu2.3), libxi-dev:i386 
(1.7.1.901-1ubuntu1~precise2, 1.7.1.901-1ubuntu1~precise3), libxrender-dev:i386 
(0.9.6-2ubuntu0.1, 0.9.6-2ubuntu0.2), libx11-xcb1:i386 (1.4.99.1-0ubuntu2.2, 
1.4.99.1-0ubuntu2.3), x11proto-core-dev:i386 (7.0.22-1ubuntu0.1, 
7.0.22-1ubuntu0.2), libxext-dev:i386 (1.3.0-3ubuntu0.1, 1.3.0-3ubuntu0.2), 
xserver-xorg-video-vmware:i386 (12.0.1-1ubuntu1.1, 12.0.1-1ubuntu1.2), 
libxrender1:i386 (0.9.6-2ubuntu0.1, 0.9.6-2ubuntu0.2), libxrandr-dev:i386 
(1.3.2-2ubuntu0.2, 1.3.2-2ubuntu0.3), libx11-6:i386 (1.4.99.1-0ubuntu2.2, 
1.4.99.1-0ubuntu2.3), ntpdate:i386 (4.2.6.p3+dfsg-1ubuntu3.3, 
4.2.6.p3+dfsg-1ubuntu3.4), libx11-dev:i386 (1.4.99.1-0ubuntu2.2, 
1.4.99.1-0ubuntu2.3), libx11-doc:i386 (1.4.99.1-0ubuntu2.2, 
1.4.99.1-0ubuntu2.3), libxfixes-dev:i386 (5.0-4ubuntu4.3, 5.0-4ubuntu4.4), 
libxi6:i386 (1.7.1.9
 01-1ubuntu1~precise2, 1.7.1.901-1ubuntu1~precise3), libxp6:i386 
(1.0.1-2ubuntu0.12.04.1, 1.0.1-2ubuntu0.12.04.2), libxv1:i386 
(1.0.6-2ubuntu0.1, 1.0.6-2ubuntu0.2), libxext6:i386 (1.3.0-3ubuntu0.1, 
1.3.0-3ubuntu0.2), libxrandr2:i386 (1.3.2-2ubuntu0.2, 1.3.2-2ubuntu0.3)
  End-Date: 2015-04-15  00:40:43

  Clearing the entire archive including *.bin* files didn't work.
  http://askubuntu.com/a/14552/170177

  Increasing or disabling the cache limit made no difference.
  https://aziest.wordpress.com/2011/01/24/how-to-increase-your-apt-cache-limit/

  Still looking and will update.
  --- 
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: i386
  DistroRelease: Ubuntu 12.04
  MarkForUpload: True
  NonfreeKernelModules: nvidia
  Package: apt 0.8.16~exp12ubuntu10.23
  PackageArchitecture: i386
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12
  Tags:  precise package-from-proposed
  Uname: Linux 3.11.0-26-generic i686
  UpgradeStatus: Upgraded to precise on 2014-12-07 (130 days ago)
  UserGroups: adm admin audio cdrom debian-tor dialout dip fax floppy fuse lp 
lpadmin plugdev sambashare scanner tape video

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

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

[Touch-packages] [Bug 1507463] Re: OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13

[oleg]

I retested using lxc-1.1.4 from the lxc-stable ppa
(https://launchpad.net/~ubuntu-lxc/+archive/ubuntu/lxc-stable) which I
added to a fresh vm image from the daily-builds, https://cloud-
images.ubuntu.com/trusty/current.

"lxc-start -n trusty_overlay" fails as before, with the same error
message,

ERRORlxc_utils - utils.c:safe_mount:1641 - Permission denied - Failed to 
mount /home/ubuntu/test.txt onto 
/usr/lib/x86_64-linux-gnu/lxc/home/ubuntu/test.txt
ERRORlxc_conf - conf.c:mount_entry:1731 - Permission denied - failed to 
mount '/home/ubuntu/test.txt' on 
'/usr/lib/x86_64-linux-gnu/lxc/home/ubuntu/test.txt'
ERRORlxc_conf - conf.c:lxc_setup:3745 - failed to setup the mount entries 
for 'trusty_overlay'

Chris, it would be of interest to see whether you can reproduce the
underlying kernel bug using this script,

#!/bin/bash
fatal() { echo "error: $@"; exit 1; }

echo -e "testing for overlayfs kernel bug in kernels <= 3.17.";
echo -e "(This script does not work for the newer version of overlayfs in 
kernels 3.18+)";

mkdir test_dir|| fatal "mkdir test_dir";
sudo mount -t tmpfs none test_dir || fatal "mount tmpfs";
cd test_dir;
mkdir lowerdir upperdir overlayfs;
sudo mount -t overlayfs -o lowerdir=lowerdir,upperdir=upperdir none overlayfs 
|| fatal "mount overlayfs";

exec 6> file_tmpfs.txt;
exec 7> lowerdir/file_lowerdir.txt;
exec 8> upperdir/file_upperdir.txt;
exec 9> overlayfs/file_overlayfs.txt;

echo -e "\ncontents of /proc/$BASHPID/fd/ .  A broken symbolic link to 
file_overlayfs.txt indicates a kernel bug";
echo 
"";
file /proc/$BASHPID/fd/[6-9];

# cleanup
exec 9>&-;
exec 8>&-;
exec 7>&-;
exec 6>&-;
sudo umount overlayfs;
cd ..;
sudo umount test_dir && rmdir test_dir;
#--end of script

Running the script as root, sudo ./script, I get the following output,

  testing for overlayfs kernel bug in kernels <= 3.17.
  (This script does not work for the newer version of overlayfs in kernels 
3.18+)

  contents of /proc/1916/fd/ .  A broken symbolic link to file_overlayfs.txt 
indicates a kernel bug
  

  /proc/1916/fd/6: symbolic link to `/home/ubuntu/test_dir/file_tmpfs.txt' 
  /proc/1916/fd/7: symbolic link to 
`/home/ubuntu/test_dir/lowerdir/file_lowerdir.txt' 
  /proc/1916/fd/8: symbolic link to 
`/home/ubuntu/test_dir/upperdir/file_upperdir.txt' 
  /proc/1916/fd/9: broken symbolic link to `/file_overlayfs.txt'

It seems that the kernel bug is causing fd 9 to point to
/file_overlayfs.txt, when it should point to
/home/ubuntu/test_dir/overlayfs/file_overlayfs.txt .

The lxc commit which introduced safe_mount(), which passes fd's as
arguments to mount() is,

CVE-2015-1335: Protect container mounts against symlinks
https://github.com/lxc/lxc/commit/6de26af93d3dd87c8b21a42fdf20f30fa1c1948d

Here is the relevant part of the commit, which creates a file descriptor
and passes it to mount().

+   destfd = open_without_symlink(dest, rootfs);
+   if (destfd < 0) {
+   if (srcfd != -1)
+   close(srcfd);
+   return destfd;
+   }
+
+   ret = snprintf(destbuf, 50, "/proc/self/fd/%d", destfd);
+   if (ret < 0 || ret > 50) {
+   if (srcfd != -1)
+   close(srcfd);
+   close(destfd);
+   ERROR("Out of memory");
+   return -EINVAL;
+   }
+
+   ret = mount(mntsrc, destbuf, fstype, flags, data);


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

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

Title:
  OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13

Status in linux package in Ubuntu:
  Incomplete
Status in lxc package in Ubuntu:
  Incomplete

Bug description:
  I am running Ubuntu Trusty (3.13.0-65-generic #106-Ubuntu SMP Fri Oct
  2 22:08:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux).

  There are two issues in OverlayFS as follows:

   1. /proc//fdinfo/ reports wrong mnt_id (non-existent in
  /proc//mountinfo)

   2. /proc//fd/ shows incorrect path for the symlink target

  These issues were previously reported and patched for the Ubuntu Vivid
  kernel (3.19) in bug #1479468, but the patch was not applied to the
  3.13 kernel, possibly because it contains an older version of
  overlayfs.

  These issues are now adversely affecting some versions of lxc when
  used in conjunction with the 3.13 kernel, because lxc has recently
  been patched to pass /proc//fd/ to the mount syscall.  This
  change to lxc was made in response to cve-2015-1335; see bug #1476662.

  The kernel issues cause some overlayfs-backed containers to fail to
  start, with error message,

  strace: 

[Touch-packages] [Bug 1508309] Re: Every time i log into my computer the sound volume goes back to 100%!

[Sebastien Bacher]

** Package changed: unity-control-center (Ubuntu) => pulseaudio (Ubuntu)

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

Title:
  Every time i log into my computer the sound volume goes back to 100%!

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Every time i log into my computer the sound goes back to 100%, there
  has to be a way for ALSA or the controls or whatever to store the
  value i had before logging off!

  I tried a workaround that involved setting the values manually and
  storing them but it didnt work!! Every time i log into my computer the
  volume goes back up to 100%, its very frustrating.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity-control-center 15.04.0+15.04.20150410-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Oct 21 07:19:23 2015
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2014-11-09 (345 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: unity-control-center
  UpgradeStatus: Upgraded to vivid on 2015-04-28 (175 days ago)
  usr_lib_unity-control-center: deja-dup 32.0-0ubuntu5

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

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

[Touch-packages] [Bug 1508470] Re: sshd wont start for 15.10

[Thomas Schweikle]

The problem is related to ignoring "noauto" in fstab. The system tries
to mount a nonexisting fd using ufs and fails.

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

Title:
  sshd wont start for 15.10

Status in openssh package in Ubuntu:
  New

Bug description:
  After upgrading to the latest available packages for Ubuntu 15.10 sshd
  will not start any more. The system aquires an address, but it does
  not start sshd.

  Result: no remote access. On servers this might be fatal, since it
  might be a headless one and without sshd running access is not
  possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ssh (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27
  Uname: Linux 3.13.0-66-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.16
  Architecture: amd64
  Date: Wed Oct 21 15:41:42 2015
  InstallationDate: Installed on 2012-12-12 (1042 days ago)
  InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release 
amd64 (20120817.3)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: openssh
  UpgradeStatus: Upgraded to trusty on 2013-02-11 (981 days ago)

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

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

[Touch-packages] [Bug 1508485] Re: "QThread: Destroyed while thread is still running" printed on shutdown

[Gerry Boland]

DashCommunicator inherits QThread. From the QThread docs:

"Note that deleting a QThread object will not stop the execution of the
thread it manages. Deleting a running QThread (i.e. isFinished() returns
false) will probably result in a program crash. Wait for the finished()
signal before deleting the QThread."

So to fix this, need to refactor DashCommunicator a bit to only delete
the QThread after the thread's finished() signal has fired.

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

Title:
  "QThread: Destroyed while thread is still running" printed on shutdown

Status in unity8 package in Ubuntu:
  New

Bug description:
  Sending SIGTERM to unity8 causes this slightly concerning error
  message to be printed:

  QThread: Destroyed while thread is still running

  Going a quick dig, I see it came from DashCommunicator:

  (gdb) break src/corelib/thread/qthread.cpp:417
  Breakpoint 1 at 0x7fafce6bd935: file thread/qthread.cpp, line 417.
  (gdb) cont
  Continuing.
  ^C
  Program received signal SIGINT, Interrupt.
  0x7fafcddb98dd in poll () at ../sysdeps/unix/syscall-template.S:81
  81in ../sysdeps/unix/syscall-template.S
  (gdb) signal SIGTERM
  Continuing with signal SIGTERM.

  Breakpoint 1, QThread::~QThread (this=0x203d1f0, __in_chrg=) 
at thread/qthread.cpp:417
  417   thread/qthread.cpp: No such file or directory.
  (gdb) t
  [Current thread is 1 (Thread 0x7fafcfcaf800 (LWP 19100))]
  (gdb) info threads
Id   Target Id Frame 
23   Thread 0x7fafc178b700 (LWP 19101) "unity8" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
22   Thread 0x7fafc0f8a700 (LWP 19102) "unity8" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
21   Thread 0x7fafbbfff700 (LWP 19103) "MirServerThread" 0x7fafcddb98dd 
in poll () at ../sysdeps/unix/syscall-template.S:81
20   Thread 0x7fafbb7fe700 (LWP 19104) "RPC Thread" 0x7fafcddb98dd in 
poll () at ../sysdeps/unix/syscall-template.S:81
19   Thread 0x7fafb951d700 (LWP 19105) "MirServerThread" 
pthread_cond_wait@@GLIBC_2.3.2 ()
  at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
18   Thread 0x7fafb8ac0700 (LWP 19106) "Input dispatch" 0x7fafcddb98dd 
in poll () at ../sysdeps/unix/syscall-template.S:81
17   Thread 0x7fafaa0db700 (LWP 19107) "Mir/Snapshot" 
pthread_cond_wait@@GLIBC_2.3.2 ()
  at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
16   Thread 0x7fafa98da700 (LWP 19108) "Mir/IPC" 0x7fafcddc54f3 in 
epoll_wait () at ../sysdeps/unix/syscall-template.S:81
15   Thread 0x7fafa90d9700 (LWP 19109) "Mir/IPC" 0x7fafcddc54f3 in 
epoll_wait () at ../sysdeps/unix/syscall-template.S:81
14   Thread 0x7faf9db6d700 (LWP 19110) "QQmlThread" 0x7fafcddb98dd in 
poll () at ../sysdeps/unix/syscall-template.S:81
13   Thread 0x7faf8de65700 (LWP 19111) "gmain" 0x7fafcddb98dd in poll 
() at ../sysdeps/unix/syscall-template.S:81
12   Thread 0x7faf85664700 (LWP 19112) "gdbus" 0x7fafcbceea91 in 
g_variant_type_info_check (
  info=info@entry=0x7fafcbd504b0 , 
container_class=container_class@entry=0 '\000')
  at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gvarianttypeinfo.c:158
11   Thread 0x7faf8d3ff700 (LWP 19113) "dconf worker" 0x7fafcddb98dd in 
poll () at ../sysdeps/unix/syscall-template.S:81
10   Thread 0x7faf7eba6700 (LWP 19114) "dashCommunicato" 0x7fafcddb98dd 
in poll () at ../sysdeps/unix/syscall-template.S:81
9Thread 0x7faf73fff700 (LWP 19115) "unity8" 0x7fafcddc54f3 in 
epoll_wait () at ../sysdeps/unix/syscall-template.S:81
8Thread 0x7faf735f9700 (LWP 19118) "unity8" 
pthread_cond_wait@@GLIBC_2.3.2 ()
  at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
7Thread 0x7faf71dd9700 (LWP 19119) "Qt bearer threa" 0x7fafcddb98dd 
in poll () at ../sysdeps/unix/syscall-template.S:81
6Thread 0x7faf63fff700 (LWP 19121) "QQuickPixmapRea" 0x7fafcddb98dd 
in poll () at ../sysdeps/unix/syscall-template.S:81
5Thread 0x7faf615ad700 (LWP 19123) "Thread (pooled)" 
pthread_cond_wait@@GLIBC_2.3.2 ()
  at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
4Thread 0x7faf5ffa0700 (LWP 19124) "QThread" 0x7fafcddb98dd in poll 
() at ../sysdeps/unix/syscall-template.S:81
3Thread 0x7faf5f79f700 (LWP 19125) "QProcessManager" 0x7fafcddbb743 
in select () at ../sysdeps/unix/syscall-template.S:81
2Thread 0x7faf5ef5e700 (LWP 19135) "QSGRenderThread" 
pthread_cond_wait@@GLIBC_2.3.2 ()
  at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  * 1Thread 0x7fafcfcaf800 (LWP 19100) "unity8" QThread::~QThread 
(this=0x203d1f0, __in_chrg=)
  at thread/qthread.cpp:417

  
  (gdb) bt
  #0  0x7fafce6bd935 in QThread::~QThread() (this=0x203d1f0, 
__in_chrg=) at 

[Touch-packages] [Bug 1508309] [NEW] Every time i log into my computer the sound volume goes back to 100%!

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Every time i log into my computer the sound goes back to 100%, there has
to be a way for ALSA or the controls or whatever to store the value i
had before logging off!

I tried a workaround that involved setting the values manually and
storing them but it didnt work!! Every time i log into my computer the
volume goes back up to 100%, its very frustrating.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: unity-control-center 15.04.0+15.04.20150410-0ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
Uname: Linux 3.19.0-31-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.5
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Oct 21 07:19:23 2015
ExecutablePath: /usr/bin/unity-control-center
InstallationDate: Installed on 2014-11-09 (345 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
SourcePackage: unity-control-center
UpgradeStatus: Upgraded to vivid on 2015-04-28 (175 days ago)
usr_lib_unity-control-center: deja-dup 32.0-0ubuntu5

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


** Tags: amd64 apport-bug vivid
-- 
Every time i log into my computer the sound volume goes back to 100%!
https://bugs.launchpad.net/bugs/1508309
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to pulseaudio 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 1508470] [NEW] sshd wont start for 15.10

[Thomas Schweikle]

Public bug reported:

After upgrading to the latest available packages for Ubuntu 15.10 sshd
will not start any more. The system aquires an address, but it does not
start sshd.

Result: no remote access. On servers this might be fatal, since it might
be a headless one and without sshd running access is not possible.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ssh (not installed)
ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27
Uname: Linux 3.13.0-66-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.16
Architecture: amd64
Date: Wed Oct 21 15:41:42 2015
InstallationDate: Installed on 2012-12-12 (1042 days ago)
InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120817.3)
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: openssh
UpgradeStatus: Upgraded to trusty on 2013-02-11 (981 days ago)

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


** Tags: amd64 apport-bug trusty

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

Title:
  sshd wont start for 15.10

Status in openssh package in Ubuntu:
  New

Bug description:
  After upgrading to the latest available packages for Ubuntu 15.10 sshd
  will not start any more. The system aquires an address, but it does
  not start sshd.

  Result: no remote access. On servers this might be fatal, since it
  might be a headless one and without sshd running access is not
  possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ssh (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27
  Uname: Linux 3.13.0-66-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.16
  Architecture: amd64
  Date: Wed Oct 21 15:41:42 2015
  InstallationDate: Installed on 2012-12-12 (1042 days ago)
  InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release 
amd64 (20120817.3)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: openssh
  UpgradeStatus: Upgraded to trusty on 2013-02-11 (981 days ago)

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

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

[Touch-packages] [Bug 1508470] Re: sshd wont start for 15.10

[Thomas Schweikle]

PS: the bug is reported from a 14.04 system, for a 15.10 system. At the
moment of writing, the 15.10 system is not accessible any more, because
of sshd not running (or no open port for sshd. May be even a firewall
problem).

Seen it on:
- 15.04 -- current, stable
- 15.10 -- upcomming

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

Title:
  sshd wont start for 15.10

Status in openssh package in Ubuntu:
  New

Bug description:
  After upgrading to the latest available packages for Ubuntu 15.10 sshd
  will not start any more. The system aquires an address, but it does
  not start sshd.

  Result: no remote access. On servers this might be fatal, since it
  might be a headless one and without sshd running access is not
  possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ssh (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27
  Uname: Linux 3.13.0-66-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.16
  Architecture: amd64
  Date: Wed Oct 21 15:41:42 2015
  InstallationDate: Installed on 2012-12-12 (1042 days ago)
  InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release 
amd64 (20120817.3)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: openssh
  UpgradeStatus: Upgraded to trusty on 2013-02-11 (981 days ago)

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

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

[Touch-packages] [Bug 1508468] Re: Users are forced to wade through unknown networks to single out the network/s they have previously connected to in the past

[Greg Williams]

This would be a much more efficient and clean network-indicator design
arrangement:

Wi-Fi Networks
-currently connected network
Disconnect

-previously connected network
-previously connected network

More Networks
-never before connected network
-never before connected network
-never before connected network
-never before connected network
-never before connected network

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

Title:
  Users are forced to wade through unknown networks to single out the
  network/s they have previously connected to in the past

Status in indicator-network package in Ubuntu:
  New

Bug description:
  The summary pretty much tells the tale: users are forced to wade
  through unknown networks to single out the network/s they have
  previously connected to in the past.

  I go to a location. Twenty some networks are available. Most of them
  appear in the "More Networks" folder. Five networks appear outside the
  "More Networks" folder. Despite the fact that I ONLY EVER connect
  maybe two networks, other networks that I never ever connect to are
  always displayed.

  Why are networks that I have never connected to (and never will
  connect to) ALWAYS displayed in the menu? Why aren't they confined to
  the "More Networks" folder until connected to at least one time.

  Previously, I proposed a solution: confine networks that have NEVER
  been connected to in the "More Networks" folder. Once a connection has
  been established, move it out of the "More Networks" folder.  I'm told
  most users allow automatic wifi connections: so users only have to
  look ONE TIME, the first time they connect to a foreign (never before
  seen) network.

  the current system presents two usability problems. If automatic
  connection is turned on and more than one network has been connected
  to in the past, the system does not know which network the user wants
  THIS TIME. And yet the user has to wade through networks they have
  never connected to and will never connect to to locate the networks
  they have to connected to in the past (there has to be a better way to
  organize this). Second, if the user does not allow automatic
  connections for security/privacy/battery reasons, the user is forced
  to wade through networks he/she has never connected to and will never
  connect every time he/she wants to make a wifi connection.

  Since my previous proposal was shot down, can ubuntu engineers please
  come up with a solution to this usability problem (as Matthew Paul
  Thomas has you are more capable of doing). Matthew Paul Thomas has
  invalidated my "simple" solution that would inconvenience no one:
  https://bugs.launchpad.net/ubuntu/+source/indicator-
  network/+bug/1425991

  I'm told most users autoconnect. So they want to see the networks
  right away, but this is nonsense. There are often so many networks,
  they HAVE to look in "More Networks" anyways.

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

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

[Touch-packages] [Bug 1508357] Re: Tooltips have a black squares outside of its rounded corners

[Treviño]

This happens because unity (compiz) doesn't advertize to support
_GTK_FRAME_HINTS (as we don't), so gtk3 doesn't set up an rgba surface
for tooltips and other client-side decorated windows (such as the ones
with headerbar, to be fixed differently).

However in unity we do support rgba surfaces, and so to get proper
transparent corners we need to force this.

** Branch linked: lp:~3v1n0/gtk/unity-rgba-tooltips

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

Title:
  Tooltips have a black squares outside of its rounded corners

Status in gtk+3.0 package in Ubuntu:
  In Progress

Bug description:
  Hover over any elements on a gtk apps making a tooltip appearing.

  See that the tooltip is rectangular, containing rounded corner with a 
gradient.
  However, the external part is just plain black and don't have transparency as 
expected.

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

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

[Touch-packages] [Bug 1508485] [NEW] "QThread: Destroyed while thread is still running" printed on shutdown

[Gerry Boland]

Public bug reported:

Sending SIGTERM to unity8 causes this slightly concerning error message
to be printed:

QThread: Destroyed while thread is still running

Going a quick dig, I see it came from DashCommunicator:

(gdb) break src/corelib/thread/qthread.cpp:417
Breakpoint 1 at 0x7fafce6bd935: file thread/qthread.cpp, line 417.
(gdb) cont
Continuing.
^C
Program received signal SIGINT, Interrupt.
0x7fafcddb98dd in poll () at ../sysdeps/unix/syscall-template.S:81
81  in ../sysdeps/unix/syscall-template.S
(gdb) signal SIGTERM
Continuing with signal SIGTERM.

Breakpoint 1, QThread::~QThread (this=0x203d1f0, __in_chrg=) at 
thread/qthread.cpp:417
417 thread/qthread.cpp: No such file or directory.
(gdb) t
[Current thread is 1 (Thread 0x7fafcfcaf800 (LWP 19100))]
(gdb) info threads
  Id   Target Id Frame 
  23   Thread 0x7fafc178b700 (LWP 19101) "unity8" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  22   Thread 0x7fafc0f8a700 (LWP 19102) "unity8" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  21   Thread 0x7fafbbfff700 (LWP 19103) "MirServerThread" 0x7fafcddb98dd 
in poll () at ../sysdeps/unix/syscall-template.S:81
  20   Thread 0x7fafbb7fe700 (LWP 19104) "RPC Thread" 0x7fafcddb98dd in 
poll () at ../sysdeps/unix/syscall-template.S:81
  19   Thread 0x7fafb951d700 (LWP 19105) "MirServerThread" 
pthread_cond_wait@@GLIBC_2.3.2 ()
at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  18   Thread 0x7fafb8ac0700 (LWP 19106) "Input dispatch" 0x7fafcddb98dd in 
poll () at ../sysdeps/unix/syscall-template.S:81
  17   Thread 0x7fafaa0db700 (LWP 19107) "Mir/Snapshot" 
pthread_cond_wait@@GLIBC_2.3.2 ()
at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  16   Thread 0x7fafa98da700 (LWP 19108) "Mir/IPC" 0x7fafcddc54f3 in 
epoll_wait () at ../sysdeps/unix/syscall-template.S:81
  15   Thread 0x7fafa90d9700 (LWP 19109) "Mir/IPC" 0x7fafcddc54f3 in 
epoll_wait () at ../sysdeps/unix/syscall-template.S:81
  14   Thread 0x7faf9db6d700 (LWP 19110) "QQmlThread" 0x7fafcddb98dd in 
poll () at ../sysdeps/unix/syscall-template.S:81
  13   Thread 0x7faf8de65700 (LWP 19111) "gmain" 0x7fafcddb98dd in poll () 
at ../sysdeps/unix/syscall-template.S:81
  12   Thread 0x7faf85664700 (LWP 19112) "gdbus" 0x7fafcbceea91 in 
g_variant_type_info_check (
info=info@entry=0x7fafcbd504b0 , 
container_class=container_class@entry=0 '\000')
at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gvarianttypeinfo.c:158
  11   Thread 0x7faf8d3ff700 (LWP 19113) "dconf worker" 0x7fafcddb98dd in 
poll () at ../sysdeps/unix/syscall-template.S:81
  10   Thread 0x7faf7eba6700 (LWP 19114) "dashCommunicato" 0x7fafcddb98dd 
in poll () at ../sysdeps/unix/syscall-template.S:81
  9Thread 0x7faf73fff700 (LWP 19115) "unity8" 0x7fafcddc54f3 in 
epoll_wait () at ../sysdeps/unix/syscall-template.S:81
  8Thread 0x7faf735f9700 (LWP 19118) "unity8" 
pthread_cond_wait@@GLIBC_2.3.2 ()
at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  7Thread 0x7faf71dd9700 (LWP 19119) "Qt bearer threa" 0x7fafcddb98dd 
in poll () at ../sysdeps/unix/syscall-template.S:81
  6Thread 0x7faf63fff700 (LWP 19121) "QQuickPixmapRea" 0x7fafcddb98dd 
in poll () at ../sysdeps/unix/syscall-template.S:81
  5Thread 0x7faf615ad700 (LWP 19123) "Thread (pooled)" 
pthread_cond_wait@@GLIBC_2.3.2 ()
at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  4Thread 0x7faf5ffa0700 (LWP 19124) "QThread" 0x7fafcddb98dd in poll 
() at ../sysdeps/unix/syscall-template.S:81
  3Thread 0x7faf5f79f700 (LWP 19125) "QProcessManager" 0x7fafcddbb743 
in select () at ../sysdeps/unix/syscall-template.S:81
  2Thread 0x7faf5ef5e700 (LWP 19135) "QSGRenderThread" 
pthread_cond_wait@@GLIBC_2.3.2 ()
at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
* 1Thread 0x7fafcfcaf800 (LWP 19100) "unity8" QThread::~QThread 
(this=0x203d1f0, __in_chrg=)
at thread/qthread.cpp:417


(gdb) bt
#0  0x7fafce6bd935 in QThread::~QThread() (this=0x203d1f0, 
__in_chrg=) at thread/qthread.cpp:417
#1  0x7faf845e5ef2 in  () at 
/usr/lib/x86_64-linux-gnu/unity8/qml/Unity/DashCommunicator/libDashCommunicator-qml.so
#2  0x7fafce8d1d2b in QObjectPrivate::deleteChildren() 
(this=this@entry=0x2033f40) at kernel/qobject.cpp:1950
#3  0x7fafce8db620 in QObject::~QObject() (this=, 
__in_chrg=) at kernel/qobject.cpp:1030
#4  0x7fafcf5b52bd in QQuickItem::~QQuickItem() (this=0x2033f10, 
__in_chrg=) at items/qquickitem.cpp:2223
#5  0x7fafcf5cf7c6 in QQmlPrivate::QQmlElement::~QQmlElement() 
(this=0x2033f10, __in_chrg=)
at ../../include/QtQml/../../src/qml/qml/qqmlprivate.h:98
#6  0x7fafcf5cf7c6 in QQmlPrivate::QQmlElement::~QQmlElement() 
(this=0x2033f10, __in_chrg=)
at ../../include/QtQml/../../src/qml/qml/qqmlprivate.h:98
#7  0x7fafce8d1d2b in QObjectPrivate::deleteChildren() 

[Touch-packages] [Bug 1493552] Re: messaging-app crashes on startup sometimes

[Pat McGowan]

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

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

Title:
  messaging-app crashes on startup sometimes

Status in Canonical System Image:
  In Progress
Status in messaging-app package in Ubuntu:
  In Progress

Bug description:
  latest rc-proposed r105

  I launched messaging-app and see the Messages view is frozen only
  displaying phone numbers and no contact names. Turns out the app has
  crashed. The core file is attached.

  Here is a bt

  Thread 16 (Thread 0xa747f3d0 (LWP 4190)):
  #0  0xb646ae08 in 
QtVersit::QVersitReaderPrivate::parseVCard30Property(QtVersit::QVersitDocument::VersitType,
 QtVersit::LByteArray*, QtVersit::QVersitProperty*, QtVersit::LineReader*) ()
 from /usr/lib/arm-linux-gnueabihf/libQt5Versit.so.5
  #1  0xb646b4d0 in 
QtVersit::QVersitReaderPrivate::parseNextVersitProperty(QtVersit::QVersitDocument::VersitType,
 QtVersit::LineReader*) () from /usr/lib/arm-linux-gnueabihf/libQt5Versit.so.5
  #2  0xb646b8d0 in 
QtVersit::QVersitReaderPrivate::parseVersitDocument(QtVersit::LineReader*, 
QtVersit::QVersitDocument*) () from 
/usr/lib/arm-linux-gnueabihf/libQt5Versit.so.5
  #3  0xb646bc44 in QtVersit::QVersitReaderPrivate::read() ()
 from /usr/lib/arm-linux-gnueabihf/libQt5Versit.so.5
  #4  0xb6cbb496 in ?? () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
  #5  0xb6140490 in start_thread () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
  #6  0xb61e2c4c in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 15 (Thread 0xb6ff (LWP 4065)):
  #0  0xb61dc4e0 in poll () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0x in ?? ()
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 14 (Thread 0xa7e113d0 (LWP 4157)):
  #0  0xb42bffac in ?? ()
  #1  0xb42d5ee0 in ?? ()
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 13 (Thread 0xab5ae3d0 (LWP 4139)):
  ---Type  to continue, or q  to quit---
  #0  0xb61dc4e0 in poll () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0x in ?? ()
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 12 (Thread 0xa43023d0 (LWP 4191)):
  #0  0xb646ae08 in 
QtVersit::QVersitReaderPrivate::parseVCard30Property(QtVersit::QVersitDocument::VersitType,
 QtVersit::LByteArray*, QtVersit::QVersitProperty*, QtVersit::LineReader*) ()
 from /usr/lib/arm-linux-gnueabihf/libQt5Versit.so.5
  #1  0xb646b4d0 in 
QtVersit::QVersitReaderPrivate::parseNextVersitProperty(QtVersit::QVersitDocument::VersitType,
 QtVersit::LineReader*) () from /usr/lib/arm-linux-gnueabihf/libQt5Versit.so.5
  #2  0xb646b8d0 in 
QtVersit::QVersitReaderPrivate::parseVersitDocument(QtVersit::LineReader*, 
QtVersit::QVersitDocument*) () from 
/usr/lib/arm-linux-gnueabihf/libQt5Versit.so.5
  #3  0xb646bc44 in QtVersit::QVersitReaderPrivate::read() ()
 from /usr/lib/arm-linux-gnueabihf/libQt5Versit.so.5
  #4  0xb6cbb496 in ?? () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
  #5  0xb6140490 in start_thread () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
  #6  0xb61e2c4c in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 11 (Thread 0xabebe3d0 (LWP 4138)):
  #0  0xb61e3132 in epoll_wait () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0xb398528a in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
  #2  0xb3987262 in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
  #3  0xb39877c2 in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
  #4  0xb3970678 in core::dbus::Bus::run() () from 
/usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
  #5  0xb62ee2a0 in ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  #6  0xb6140490 in start_thread () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
  ---Type  to continue, or q  to quit---
  #7  0xb61e2c4c in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 10 (Thread 0xaccd33d0 (LWP 4108)):
  #0  0xb61e0620 in syscall () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0xadb6fc98 in ?? () from /usr/lib/arm-linux-gnueabihf/liblttng-ust.so.0
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 9 (Thread 0xb0e563d0 (LWP 4099)):
  #0  0xb61dc4e0 in poll () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0x in ?? ()
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 8 (Thread 0xad4d33d0 (LWP 4107)):
  #0  0xb61e0620 in syscall () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0xadb6fc98 in ?? () from /usr/lib/arm-linux-gnueabihf/liblttng-ust.so.0
  Backtrace stopped: previous 

[Touch-packages] [Bug 1503506] Re: [desktop] Dragging in Google Maps does not work

[Pat McGowan]

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

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

Title:
  [desktop] Dragging in Google Maps does not work

Status in Canonical System Image:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  1) Go to maps.google.com in a desktop browser session
  2) Try to drag the map with your mouse

  It does not drag, but I would expect it to.

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

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

[Touch-packages] [Bug 1483708] Re: Popovers became very narrow in UITK 1.3

[Pat McGowan]

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

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

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

Title:
  Popovers became very narrow in UITK 1.3

Status in Canonical System Image:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released

Bug description:
  I recently updated all the imports of Ubuntu.Components (and
  submodules) to 1.3 in webbrowser-app. One visible side-effect of that
  is that popovers have become much narrower than they used to be. The
  browser app uses popovers for context menus (triggered by a long press
  or a right click on e.g. a hyperlink) and for bookmark options when
  bookmarking a page.

  Bookmark options look okayish, but context menus are much too narrow,
  resulting in some entries not being entirely readable (see attached
  screenshot), especially in languages that are more verbose than
  English.

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

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

[Touch-packages] [Bug 1470730] Re: [HP EliteBook 840 G2, Realtek ALC3228, HP UltraSlim Dock 2013] Line in/Line out on docking station doesn't work

[val-s]

For reference, here's the output on the HP Elitebook 9480m. Not much
difference, except that things are on the Left side. Does that matter?

When should we expect this fix to be rolled in? (don't know how things
work). I tried retasking using hdjackretask, but I was unable to get any
sound out the speakers after selecting the Line Out, probably did
something wrong.


Docked, nothing plugged in:
-
Pin 0x12 (Internal Mic): present = No
Pin 0x13 (Not connected): present = No
Pin 0x14 (Internal Speaker): present = No
Pin 0x15 (Black Headphone, Left side): present = No
Pin 0x16 (Not connected): present = No
Pin 0x17 (Not connected): present = No
Pin 0x18 (Not connected): present = No
Pin 0x19 (Not connected): present = No
Pin 0x1a (Black Mic, Left side): present = No
Pin 0x1b (Not connected): present = No
Pin 0x1d (Not connected): present = No
Pin 0x1e (Not connected): present = No


Docked, plugged into mic:
-
Pin 0x12 (Internal Mic): present = No
Pin 0x13 (Not connected): present = No
Pin 0x14 (Internal Speaker): present = No
Pin 0x15 (Black Headphone, Left side): present = No
Pin 0x16 (Not connected): present = No
Pin 0x17 (Not connected): present = No
Pin 0x18 (Not connected): present = Yes
Pin 0x19 (Not connected): present = No
Pin 0x1a (Black Mic, Left side): present = No
Pin 0x1b (Not connected): present = No
Pin 0x1d (Not connected): present = No
Pin 0x1e (Not connected): present = No


Docked, headphone plugged into dock:
--
Pin 0x12 (Internal Mic): present = No
Pin 0x13 (Not connected): present = No
Pin 0x14 (Internal Speaker): present = No
Pin 0x15 (Black Headphone, Left side): present = No
Pin 0x16 (Not connected): present = No
Pin 0x17 (Not connected): present = No
Pin 0x18 (Not connected): present = No
Pin 0x19 (Not connected): present = No
Pin 0x1a (Black Mic, Left side): present = No
Pin 0x1b (Not connected): present = Yes
Pin 0x1d (Not connected): present = No
Pin 0x1e (Not connected): present = No

undocked:
-
Pin 0x12 (Internal Mic): present = No
Pin 0x13 (Not connected): present = No
Pin 0x14 (Internal Speaker): present = No
Pin 0x15 (Black Headphone, Left side): present = No
Pin 0x16 (Not connected): present = No
Pin 0x17 (Not connected): present = No
Pin 0x18 (Not connected): present = No
Pin 0x19 (Not connected): present = No
Pin 0x1a (Black Mic, Left side): present = No
Pin 0x1b (Not connected): present = No
Pin 0x1d (Not connected): present = No
Pin 0x1e (Not connected): present = No

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

Title:
  [HP EliteBook 840 G2, Realtek ALC3228, HP UltraSlim Dock 2013] Line
  in/Line out on docking station doesn't work

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  When I plug in external speakers to line in/line out combo on the
  laptop the internal speakers are turned off but when I plug the
  speakers into the docking station (HP UltraSlim Dock 2013 EURO,
  D9Y32AA) music keeps playing in the internal speakers. Similar
  behaviour (nothing happens) is experienced with microphone connected
  to line in on docking station.

  ### Expected behaviour
  Plugging in external speakers to docking station should turn off sound from 
laptop internal speakers.

  Plugging in microphone to line in on docking station should switch
  from "internal microphone" to "microphone" in Ubuntu sound settings.

  ### Current behaviour
  Sound keeps playing in internal speakers when plugging in external speakers 
to docking station.

  Plugging in microphone to line in on docking station, nothing happens.

  ### Hardware
  Laptop: HP EliteBook 840 G2
  Product number: H9W19EA#AK8

  Docking station: HP UltraSlim Dock 2013 EURO
  Product number: D9Y32AA

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  chol   2001 F pulseaudio
   /dev/snd/controlC0:  chol   2001 F pulseaudio
   /dev/snd/controlC1:  chol   2001 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jul  2 08:16:15 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-06-05 (26 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Right
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [HP EliteBook 840 G2, Realtek ALC3228, Black Headphone Out, Right] 
Playback problem
  UpgradeStatus: No upgrade log present 

[Touch-packages] [Bug 1447654] Re: installing policykit-1 hangs under systemd

[Bug Watch Updater]

** Changed in: policykit-1 (Debian)
   Status: Fix Committed => Fix Released

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

Title:
  installing policykit-1 hangs under systemd

Status in policykit-1 package in Ubuntu:
  Fix Released
Status in policykit-1-gnome package in Ubuntu:
  New
Status in policykit-1 source package in Vivid:
  Fix Committed
Status in policykit-1 package in Debian:
  Fix Released

Bug description:
  I've installed 15.04 using the current amd64 netboot.tar.gz (MD5 =
  6566065bf73a9c81feeddf5520dda122). It installs fine, but I'm getting
  errors installing packages (such as lubuntu-core).

  Last few lines from apt-get:
  Processing triggers for systemd (219-7ubuntu3) ...
  Error getting authority: Error initializing authority: Error calling 
StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached 
(g-io-error-quark, 24)
  Failed to execute operation: Connection timed out
  dpkg: error processing package systemd (--unpack):
   subprocess installed post-installation script returned error exit status 1
  Processing triggers for libglib2.0-0:amd64 (2.44.0-1ubuntu3) ...
  Processing triggers for shared-mime-info (1.3-1) ...
  Processing triggers for mime-support (3.58ubuntu1) ...
  Processing triggers for udev (219-7ubuntu3) ...
  Processing triggers for dbus (1.8.12-1ubuntu5) ...
  Errors were encountered while processing:
   systemd
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  I've done a second install using the server iso and lubuntu-core
  installs fine on that. The only thing different was my install media.

  SRU TEST CASE:
  - Boot a minimal VM and purge "apport policykit-1", or do the above netboot 
installation.
  - sudo apt-get install policykit-1 apport
  - The above hangs on the systemd triggers and eventually fails. It should 
succeed fine with this update.

  Regression potential: Very low: This update avoids that systemd tries
  to start up polkit while it's unpacked but not configured, which is
  exactly the case that can't work. If there's anything wrong with the
  postinst and the rm for the temporary masking symlink does not get run
  for some reason, the next reboot will clean it up anyway. So the fix
  is a no-change operation for anything but first install.

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

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

[Touch-packages] [Bug 1470730] Re: [HP EliteBook 840 G2, Realtek ALC3228, HP UltraSlim Dock 2013] Line in/Line out on docking station doesn't work

[Christoffer Holmstedt]

I no longer have access to the laptop and docking station that is
failing and can therefore not test it anymore. Thanks for the  help so
far, hope it gets solved for everyone else.

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

Title:
  [HP EliteBook 840 G2, Realtek ALC3228, HP UltraSlim Dock 2013] Line
  in/Line out on docking station doesn't work

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  When I plug in external speakers to line in/line out combo on the
  laptop the internal speakers are turned off but when I plug the
  speakers into the docking station (HP UltraSlim Dock 2013 EURO,
  D9Y32AA) music keeps playing in the internal speakers. Similar
  behaviour (nothing happens) is experienced with microphone connected
  to line in on docking station.

  ### Expected behaviour
  Plugging in external speakers to docking station should turn off sound from 
laptop internal speakers.

  Plugging in microphone to line in on docking station should switch
  from "internal microphone" to "microphone" in Ubuntu sound settings.

  ### Current behaviour
  Sound keeps playing in internal speakers when plugging in external speakers 
to docking station.

  Plugging in microphone to line in on docking station, nothing happens.

  ### Hardware
  Laptop: HP EliteBook 840 G2
  Product number: H9W19EA#AK8

  Docking station: HP UltraSlim Dock 2013 EURO
  Product number: D9Y32AA

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  chol   2001 F pulseaudio
   /dev/snd/controlC0:  chol   2001 F pulseaudio
   /dev/snd/controlC1:  chol   2001 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jul  2 08:16:15 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-06-05 (26 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Right
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [HP EliteBook 840 G2, Realtek ALC3228, Black Headphone Out, Right] 
Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/24/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M71 Ver. 01.04
  dmi.board.name: 2216
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 96.54
  dmi.chassis.asset.tag: 5CG5093YZ7
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM71Ver.01.04:bd02/24/2015:svnHewlett-Packard:pnHPEliteBook840G2:pvrA3009D410303:rvnHewlett-Packard:rn2216:rvrKBCVersion96.54:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 840 G2
  dmi.product.version: A3009D410303
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1508535] [NEW] Update Google account branding

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

The Google account icon in the Accounts page uses the old white-
lowercase-g-on-blue backing.  They updated their logo a while ago to use
a rainbow-uppercase-G.

We should update too.

(I'm sure this isn't the right component, just wasn't sure where to put
it.)

** Affects: ubuntu-system-settings-online-accounts (Ubuntu)
 Importance: Undecided
 Status: Confirmed

-- 
Update Google account branding
https://bugs.launchpad.net/bugs/1508535
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to ubuntu-system-settings-online-accounts 
in Ubuntu.

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

[Touch-packages] [Bug 1488170] Re: Bluetooth initiated after quitting airplane mode

[Pat McGowan]

** Description changed:

  This happens despite bluetooth not being enabled when entering airplane
  mode.
  
  On Aquaris E5 OTA-5.
+ 
+ Boot with bluetooth disabled
+ Turn on flight mode
+ turn off flight mode
+ Bluetooth gets enabled
+ 
+ See bug #1421249 for related symptoms

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

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

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

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

Title:
  Bluetooth initiated after quitting airplane mode

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in urfkill package in Ubuntu:
  Confirmed

Bug description:
  This happens despite bluetooth not being enabled when entering
  airplane mode.

  On Aquaris E5 OTA-5.

  Boot with bluetooth disabled
  Turn on flight mode
  turn off flight mode
  Bluetooth gets enabled

  See bug #1421249 for related symptoms

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

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

[Touch-packages] [Bug 1473890] Re: UITK API addition in Qt 5.5

[Christian Dywan]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Christian Dywan (kalikiana)

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Triaged => 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/1473890

Title:
  UITK API addition in Qt 5.5

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  There's a change in Qt 5.5 that affects API of UITK too:

  https://launchpadlibrarian.net/211518910/buildlog_ubuntu-wily-i386
  .ubuntu-ui-
  toolkit_1.3.1549%2B15.10.20150713.1-0ubuntu1_BUILDING.txt.gz

  ---

  https://wiki.ubuntu.com/Touch/QtTesting

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

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

[Touch-packages] [Bug 289592] Re: Unknown media types in /usr/share/mime/packages/kde.xml

[Ken Sharp]

** Tags added: i386 precise

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

Title:
  Unknown media types in /usr/share/mime/packages/kde.xml

Status in shared-mime-info:
  Confirmed
Status in kde4libs package in Ubuntu:
  Invalid
Status in shared-mime-info package in Ubuntu:
  Triaged
Status in kde4libs package in Debian:
  New
Status in shared-mime-info package in Debian:
  Confirmed

Bug description:
  Here is the problem:

  # update-mime-database /usr/share/mime
  [...]
  Unknown media type in type 'uri/mms'

  Unknown media type in type 'uri/mmst'

  Unknown media type in type 'uri/mmsu'

  Unknown media type in type 'uri/pnm'

  Unknown media type in type 'uri/rtspt'

  Unknown media type in type 'uri/rtspu'

  It seems to come from this file:
/usr/share/mime/packages/kde.xml

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

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

[Touch-packages] [Bug 1483586] Re: On demand cpufreq govneror causes large amounts of jitter

[Steve Langasek]

** Changed in: sysvinit (Ubuntu Trusty)
 Assignee: (unassigned) => Adam Conrad (adconrad)

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

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

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

Title:
  On demand cpufreq govneror causes large amounts of jitter

Status in sysvinit package in Ubuntu:
  Fix Released
Status in sysvinit source package in Trusty:
  Triaged
Status in sysvinit source package in Vivid:
  New

Bug description:
  == Comment: #0 - Anton Blanchard  - 2015-07-16 22:22:09 ==
  We are seeing large amounts of jitter caused by od_dbs_timer(). We should 
slow down the rate of updates and or turn this into a timer. Having a workqueue 
execute so often is very noticeable.

  # echo 1 >
  /sys/kernel/debug/tracing/events/workqueue/workqueue_execute_start/enable

  (wait a while)

  # cat /sys/kernel/debug/trace

 <...>-67605 [040]  849622.393576: workqueue_execute_start: 
work struct c007fba1ba20: function od_dbs_timer
 <...>-67605 [040]  849622.403574: workqueue_execute_start: 
work struct c007fba1ba20: function od_dbs_timer
 <...>-116685 [048]  849622.403575: workqueue_execute_start: 
work struct c007fbc1ba20: function od_dbs_timer
 <...>-116685 [048]  849622.413574: workqueue_execute_start: 
work struct c007fbc1ba20: function od_dbs_timer
 <...>-67605 [040]  849622.413575: workqueue_execute_start: 
work struct c007fba1ba20: function od_dbs_timer
 <...>-67605 [040]  849622.423575: workqueue_execute_start: 
work struct c007fba1ba20: function od_dbs_timer
 <...>-116685 [048]  849622.433574: workqueue_execute_start: 
work struct c007fbc1ba20: function od_dbs_timer
 <...>-67605 [040]  849622.433574: workqueue_execute_start: 
work struct c007fba1ba20: function od_dbs_timer
 <...>-116685 [048]  849622.443573: workqueue_execute_start: 
work struct c007fbc1ba20: function od_dbs_timer

  == Comment: #1 - Shilpasri G. Bhat  - 2015-07-22 
19:42:38 ==
  Hi Anton,

  We can set the governor's tunable 'sampling_down_factor' to decrease
  the rate of updates. When this tunable is set to a value greater than
  1, the sampling period of the governor is increased during the peak
  load to sampling_period times sampling_down_factor. This will reduce
  the jitter caused by od_dbs_timer() when the cpu is busy.

  I am currently running benchmarks to find out the optimal value for
  this tunable and will post them soon.

  Thanks and Regards,
  Shilpa

  == Comment: #2 - Anton Blanchard  - 2015-07-31 03:44:49 ==
  FYI We are also seeing high levels of CPU consumed by this on a LAMP workload:

   2.54%  kworker/0:0  [kernel.kallsyms] [k] osq_lock
  |   
  ---osq_lock
 |   
 |--99.83%-- mutex_optimistic_spin
 |  __mutex_lock_slowpath
 |  mutex_lock
 |  |  
 |  |--80.08%-- od_dbs_timer

  2.5% of total CPU time spent in the od_dbs_timer mutex.

  == Comment: #3 - Anton Blanchard  - 2015-07-31 06:00:45 ==
  Hitting this on a customer setup, raising priority

  == Comment: #4 - Shilpasri G. Bhat  - 2015-08-03 
06:47:40 ==
  I used `perf top` and `perf record` to observe the overhead caused by 
'osq_lock'.
  Both with ebizzy and SPECPower's ssjb workload I am able to see an overhead 
of 0.03% caused by 'osq_lock' with default governor settings. 
  With sampling_down_factor=100, (1second) I am able to see 0.00% of overhead 
by 'osq_lock'.

  So this might not be a good data point to showcase, but by reducing
  the  od_dbs_timer interrupts we are guaranteed to decrease the
  overhead caused by 'osq_lock'.

  == Comment: #5 - VAIDYANATHAN SRINIVASAN  - 2015-08-03 
09:09:09 ==
  Hi Anton,

  Thanks for opening the bz to track and fix this issue.  Shilpa is
  trying different workarounds.  Here is our plan:

  (1) Use sampling_down_factor and other tunables in current Ubuntu
  releases to workaround the issue or minimise the impact.

  (2) Redesign cpufreq subsystem on powerpc similar to intel pstate
  driver so that we can program timers and cancel them dynamically based
  on different utilization points.  Target Ubuntu 16.04 and then
  backport to 14.04.x and other distros.

  (3) Enhance design for (2) buy estimating core level utilization
  without running timers in each thread and then decide the target
  PState

  (4) Explore hardware assist so that we can avoid per-core estimation
  in software but 

[Touch-packages] [Bug 1486889] Re: no message about"not an emergency number "popup, when call a non-emergency number with no SIM card

[Pat McGowan]

see bug #1444883

** Changed in: canonical-devices-system-image
   Status: New => Won't Fix

** Changed in: dialer-app (Ubuntu)
   Status: New => Won't Fix

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

Title:
  no message about"not an emergency number "popup,when call a non-
  emergency number  with no SIM card

Status in Canonical System Image:
  Won't Fix
Status in dialer-app package in Ubuntu:
  Won't Fix

Bug description:
  system-image-cli -i
  current build number: 95
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-08-20 14:03:45
  version version: 95
  version ubuntu: 20150819
  version device: 20150818-0b38025
  version custom: 20150814-887-8-46

  reproduce steps:
  1.Setup:no SIM card inserted
  2. Lock device 
  3. Swipe away greeter and press Emergency call option 
  4. Enter a non-emergency number 
  5. Tap on the call button
  6.observe the result

  expect result:
  step 5, there will be a message display about "not an emergency number"
  actual result:
  no "not an emergency number" message display,while after a few seconds the 
call fail message display.

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

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

[Touch-packages] [Bug 1488588] Re: Terminal crashes on selecting text, takes Unity with it

[Pat McGowan]

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

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

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

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

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

Title:
  Terminal crashes on selecting text, takes Unity with it

Status in Canonical System Image:
  Confirmed
Status in Ubuntu Terminal App:
  Confirmed
Status in unity8 package in Ubuntu:
  New

Bug description:
  To reproduce:

  1. Open terminal
  2. Hold finger over screen until pop-up menu appears, select "Select" (or 
whatever it is in English, not copy or paste)
  3. Drag finger to select text
  4. Once again drag finger to select text
  5. Terminal disappears. After a bit, Unity restarts.

  I'm attaching the log that was generated /var/crash at the moment the
  crash occured.

  The terminal seems to continue working: the icon is still there with
  the little triangle next to it and it can be switched to/from using
  the app switcher, but it simply shows the app that's underneath it.

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

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

[Touch-packages] [Bug 1421249] Re: bluetooth can not be enabled sometimes (when booting with flight mode on being one case)

[Pat McGowan]

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

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

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

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

Title:
  bluetooth can not be enabled sometimes (when booting with flight mode
  on being one case)

Status in Canonical System Image:
  Confirmed
Status in lxc-android-config package in Ubuntu:
  Triaged
Status in urfkill package in Ubuntu:
  Triaged

Bug description:
  The bluetooth indicator and the bluetooth page in system settings
  sometimes won't turn on bluetooth until after a reboot. What I expect
  to happen is that if bluetooth is off in the indicator/system settings
  and I tap the switch, the switch will go green and in a moment the
  bluetooth indicator will show up and bluetooth is enabled. When
  bluetooth is on, I expect to go into the indicator/system settings and
  turn the switch off, the switch will go gray and the bluetooth
  indicator will hide and bluetooth is disabled. I expect this to work
  whenever I want while the phone is on.

  Sometimes, this does not work. For example, yesterday I disabled
  bluetooth at some point in the evening and later I went to sleep. When
  I woke up, I tried to turn it on via the indicator and also system
  settings and it wouldn't turn on. In the indicator, the switch moves
  to the green position briefly, then moves back to gray (the bluetooth
  indicator remains hidden and bluetooth is disabled). In system
  settings, the switch will stay green, but the bluetooth indicator
  remains hidden and bluetooth is disabled. If I leave system settings
  and come back, the the switch is now in the off position.

  /var/lib/urfkill/saved-states has:
  [BLUETOOTH]
  soft=false
  prev-soft=false

  bluetoothd is confirmed to be running before and after using the
  indicator and system settings when bluetooth cannot be enabled.

  Workaround: reboot the phone and bluetooth will be enabled.

  Note: this is not new behavior-- I'm only reporting it now (partly
  because I thought it was fixed for a while, but that might have been
  because I was rebooting a lot at the time)

  $ system-image-cli -i
  current build number: 194
  device name: mako
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2015-02-11 15:34:27
  version version: 194
  version ubuntu: 20150211.1
  version device: 20150116
  version custom: mako-1.1

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

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

[Touch-packages] [Bug 971864] Re: ValueError: could not convert string to float: k_latency=0.850

[Ivnitsky Andrey]

Gordon Mckeown (thefluffyone), thanks!

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

Title:
  ValueError: could not convert string to float: k_latency=0.850

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  
  /etc/cron.daily/apt:
  Traceback (most recent call last):
File "/usr/sbin/update-apt-xapian-index", line 101, in 
  if not indexer.setupIndexing(force=opts.force, system=opts.pkgfile is 
None):
File "/usr/lib/python2.7/dist-packages/axi/indexer.py", line 513, in 
setupIndexing
  addon.obj.init(dict(values=self.values), self.progress)
File "/usr/share/apt-xapian-index/plugins/cataloged_time.py", line 72, in 
init
  self._package_cataloged_time = 
cPickle.load(open(self._packages_cataloged_file))
  ValueError: could not convert string to float: k_latency=0.850

  This error is thrown from time to time from all versions of Ubuntu from 10.10 
on upward:
  Ubuntu 10.10
  Ubuntu 11.04
  Ubuntu 11.10
  Ubuntu 12.04

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: apt 0.8.16~exp5ubuntu13.2
  ProcVersionSignature: Ubuntu 3.0.0-17.30-virtual 3.0.22
  Uname: Linux 3.0.0-17-virtual x86_64
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Mon Apr  2 22:08:38 2012
  InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.2)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apt
  UpgradeStatus: Upgraded to oneiric on 2011-09-16 (199 days ago)

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

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

[Touch-packages] [Bug 1508163] Re: OTA7 can no-longer save image file without extension.

[Pat McGowan]

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

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

** This bug has been marked a duplicate of bug 1487090
   Download initiated from context menu’s saveLink/saveMedia doesn’t expose a 
mime type

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

Title:
  OTA7 can no-longer save image file without extension.

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

Bug description:
  Since the update on the 19th Oct when trying to save images from, for
  example web pages where the URL does not end in a traditional image
  extension, the error that "no application is able to handle a file of
  this type" is displayed.

  A simple example of this is any image on Google Plus which might have
  a url as follows:-

  https://lh3.googleusercontent.com/proxy/325yGX4c_mrw8lmANpU1tAsG-
  7XsdIq_9RBJCdRk-ODC3OYqqy-
  qAFHJeuXTo5gfdAU7XAnxaz2bEQEi7kmxSkRPGYb1l4H_6jy22vTHwp3oRIvAxlDzGXMJMSFi-
  CBavbU2=w595-h427-p

  Simply long press an image on Google Plus and select "save image" to
  see this message... this was working in OTA6.

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

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

[Touch-packages] [Bug 1483908] Re: Cannot copy text longer than TextEntry

[Launchpad Bug Tracker]

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

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

Title:
  Cannot copy text longer than TextEntry

Status in Canonical System Image:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  Go to a URL that is long, i.e.:
  
http://max-skizzen-blog.blogspot.de/2009/10/hessen-eine-geschichte-von-robert.html?m=1
  In the browser window, try to copy the URL string from the location bar. You 
will not succeed: There is no way to select and copy the full string. Blue 
markers will erratically appear, but cannot be moved to the beginning and end 
of the string, because the string does not scroll left or right while blue 
markers are present.
  This is akward and a very poor UX. Actually, it drives me mad.

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

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

[Touch-packages] [Bug 1389617] Re: [camera] + [gallery] Inconsistant dialogs between camera and gallery

[Launchpad Bug Tracker]

** Branch linked: lp:~seb128/gallery-app/delete-dialog-labels

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

Title:
  [camera] + [gallery] Inconsistant dialogs between camera and gallery

Status in Ubuntu UX:
  Fix Committed
Status in camera-app package in Ubuntu:
  Invalid
Status in gallery-app package in Ubuntu:
  In Progress

Bug description:
  Using rtm 142, camera and gallery have similar photo browsing views,
  yet their dialogs to delete photos has different label/buttons, it
  would be nice if those would be the same

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

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

[Touch-packages] [Bug 1486996] Re: [Dialer] [Address Book] “Call” icon does not actually place a call

[Pat McGowan]

I don't see this changing, although  i admit it has caught me a few times 
waiting for the call
fwiw its consistent across the apps

** Changed in: canonical-devices-system-image
   Status: New => Won't Fix

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

Title:
  [Dialer] [Address Book] “Call” icon does not actually place a call

Status in Canonical System Image:
  Won't Fix
Status in Ubuntu UX:
  Won't Fix
Status in address-book-app package in Ubuntu:
  Confirmed
Status in dialer-app package in Ubuntu:
  Confirmed

Bug description:
  Reproduce:
  Open address-book-app, choose contact. Press the phone-off-the-hook icon to 
place a call

  What happens:
  The dialer-app opens with a number pre-filled.

  What I expected would happen:
  I expected the call to be placed.

  Rationale:
  The phone-off-the-hook icon in dialer-app represents placing a call, but not 
in address-book-app. Why the inconsistency?

   UX comment --

  This is intended behaviour. Every single time users tap the `call`
  icon from an other app, the dialer is pre-populated with that number.
  A 2nd tap is required to finally place the call. This way we avoid
  e.g. a popup in the browser asking user if they really want to call
  that number.

  Please refer to the latest UX spec:
  https://docs.google.com/document/d/1BRy9
  -DEXr3A1D7PHkJaXmjbe7xbRmxKkzANXuu-F6lc/edit#heading=h.u6f263x6045p

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

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

[Touch-packages] [Bug 1389617] Re: [camera] + [gallery] Inconsistant dialogs between camera and gallery

[Sebastien Bacher]

** Changed in: gallery-app (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: gallery-app (Ubuntu)
   Status: Invalid => In Progress

** Changed in: camera-app (Ubuntu)
   Status: New => Invalid

** Changed in: camera-app (Ubuntu)
   Importance: Undecided => Low

** No longer affects: camera-app

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

Title:
  [camera] + [gallery] Inconsistant dialogs between camera and gallery

Status in Ubuntu UX:
  Fix Committed
Status in camera-app package in Ubuntu:
  Invalid
Status in gallery-app package in Ubuntu:
  In Progress

Bug description:
  Using rtm 142, camera and gallery have similar photo browsing views,
  yet their dialogs to delete photos has different label/buttons, it
  would be nice if those would be the same

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

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

[Touch-packages] [Bug 1502282] Re: "unknown" connectivity status problematic

[Tony Espy]

@Michi

Hmmm, I expected lp to auto-link "comment #7" to the comment in this
bug, but that apparently didn't work:

https://bugs.launchpad.net/ubuntu/+source/unity-scopes-
api/+bug/1502282/comments/7

*If* it's possible for the shell to return "unknown", then yes I think
the shell should be initializing the session per the example.  That
said, as I didn't write the code, and have zero direct experience with
QNetworkAccessManager.  I was just pointing out that this was suggested
as a way to prevent "unknown" from ever being returned.

Anyways, it seems like there's not really anything more that I can
contribute from a networking stack developer's perspective, so I'll
abstain from further comments for now...

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

Title:
  "unknown" connectivity status problematic

Status in The Savilerow project:
  New
Status in unity-scopes-api package in Ubuntu:
  Incomplete
Status in unity-scopes-shell package in Ubuntu:
  Incomplete

Bug description:
  metadata provides a scope a network connectivity status enum with three 
possible states:
  * connected
  * disconnected
  * unknown

  Sometimes unknown is the current state. This is quite problematic
  because in general a scopes that queries the network (that is, most
  scopes) need to know whether there is network or is not network and
  depending on this either make the network queries or display an error
  message.

  A status of unknown connectivity leaves the scope with no valid option:
  * the scope could assume the network is down and provide the user an error 
message. But often the network is not actually down, so this interrupts the 
user's flow unnecessarily
  *  the scope could assume the network is up, but this is dangerous if it is 
not up

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

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

[Touch-packages] [Bug 1507982] Re: [regression] OTA7 broke previously working app

[kevin gunn]

the good news is, the promise of ABI compatibility will be maintained
with libimrclient9, so a one time rebuild should fix it going fwd

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

Title:
  [regression] OTA7 broke previously working app

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Triaged
Status in Mir 0.16 series:
  Triaged
Status in Mir 0.17 series:
  Triaged
Status in mir package in Ubuntu:
  Triaged

Bug description:
  OTA7 broke previously working app
  after OTA7 update on Meizu MX4, glmark2 stopped working 
https://uappexplorer.com/app/glmark2.sturmflut
  system updates should not break apps

  
  ~/.cache/upstart$ cat application-click-glmark2.sturmflut_glmark2_0.4.1.log
  libust[24877/24879]: Error: Error opening shm /lttng-ust-wait-5-32011 (in 
get_wait_shm() at lttng-ust-comm.c:958)
  libust[24877/24879]: Error: Error opening shm /lttng-ust-wait-5-32011 (in 
get_wait_shm() at lttng-ust-comm.c:958)
  libust[24877/24878]: Error: Error opening shm /lttng-ust-wait-5 (in 
get_wait_shm() at lttng-ust-comm.c:958)
  libust[24877/24878]: Error: Error opening shm /lttng-ust-wait-5 (in 
get_wait_shm() at lttng-ust-comm.c:958)
  Error: Couldn't connect to the Mir display server
  Error: main: Could not initialize canvas
  [1445336019.182277]  MirConnectionAPI: Caught exception at client 
library boundary (in release): 
/build/buildd/mir-0.13.3+15.04.20150617/src/client/rpc/stream_socket_transport.cpp(168):
 Throw in function virtual void 
mir::client::rpc::StreamSocketTransport::send_message(const 
std::vector&, const std::vector&)
  Dynamic exception type: 
N5boost16exception_detail10clone_implINS0_19error_info_injectorIN3mir25socket_disconnected_errorE
  std::exception::what: Failed to send message to server: Broken pipe
  32, "Broken pipe"
  libust[24922/24923]: Error: Error opening shm /lttng-ust-wait-5 (in 
get_wait_shm() at lttng-ust-comm.c:958)
  libust[24922/24923]: Error: Error opening shm /lttng-ust-wait-5 (in 
get_wait_shm() at lttng-ust-comm.c:958)
  libust[24922/24924]: Error: Error opening shm /lttng-ust-wait-5-32011 (in 
get_wait_shm() at lttng-ust-comm.c:958)
  libust[24922/24924]: Error: Error opening shm /lttng-ust-wait-5-32011 (in 
get_wait_shm() at lttng-ust-comm.c:958)
  Error: Couldn't connect to the Mir display server
  Error: main: Could not initialize canvas
  [1445336029.784398]  MirConnectionAPI: Caught exception at client 
library boundary (in release): 
/build/buildd/mir-0.13.3+15.04.20150617/src/client/rpc/stream_socket_transport.cpp(168):
 Throw in function virtual void 
mir::client::rpc::StreamSocketTransport::send_message(const 
std::vector&, const std::vector&)
  Dynamic exception type: 
N5boost16exception_detail10clone_implINS0_19error_info_injectorIN3mir25socket_disconnected_errorE
  std::exception::what: Failed to send message to server: Broken pipe
  32, "Broken pipe"

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

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

[Touch-packages] [Bug 1273462] Re: Users can mistakenly run init.d scripts and cause problems if an equivalent upstart job already exists

[Mathew Hodson]

** No longer affects: mysql-5.5 (Ubuntu)

** No longer affects: mysql-5.5 (Ubuntu Trusty)

** No longer affects: mysql-5.5 (Ubuntu Utopic)

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

Title:
  Users can mistakenly run init.d scripts and cause problems if an
  equivalent upstart job already exists

Status in lsb package in Ubuntu:
  Fix Released
Status in upstart package in Ubuntu:
  Fix Released
Status in lsb source package in Trusty:
  Fix Committed
Status in upstart source package in Trusty:
  Won't Fix
Status in lsb source package in Utopic:
  Fix Released
Status in upstart source package in Utopic:
  Fix Released
Status in upstart package in Debian:
  New

Bug description:
  [ impact ]

  Previously, init.d scripts that were replaced by upstart jobs had
  "upstart-job" symlink as a redirect in-place, which directed users at
  using upstart commands. Despite the good intentions, that never
  actually taught people about the correct interfaces. Now with the
  advent of co-installability of multiple init systems, users may have
  systemd, upstart, and sysv-init all installed on users system and have
  init.d scripts / upstart jobs / systemd units all available. To avoid
  any doubt, we should support executing /etc/init.d/ scripts which may
  call into upstart, or into systemd, or actually execute the script in
  question depending on whether there is native configuration for that
  particular job and which init system we are running under.

  [ test case ]

  Invoking init.d script should invoke upstart commands, for example:

  $ /etc/init.d/ssh status
  ssh start/running, process 4620
  $ /etc/init.d/ssh stop
  stop: Rejected send message, 1 matched rules; type="method_call", 
sender=":1.2469694" (uid=1000 pid=3908 comm="stop ssh ") 
interface="com.ubuntu.Upstart0_6.Job" member="Stop" error name="(unset)" 
requested_reply="0" destination="com.ubuntu.Upstart" (uid=0 pid=1 
comm="/sbin/init")
  $ sudo /etc/init.d/ssh stop
  ssh stop/waiting
  $ sudo /etc/init.d/ssh start
  ssh start/running, process 5373
  $ sudo /etc/init.d/ssh restart
  ssh stop/waiting
  ssh start/running, process 5405

  Description:Ubuntu 13.10
  Release:13.10

  mysql-server-5.5:
    Installed: 5.5.35-0ubuntu0.13.10.1
    Candidate: 5.5.35-0ubuntu0.13.10.1
    Version table:
   *** 5.5.35-0ubuntu0.13.10.1 0
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu/ 
saucy-updates/main amd64 Packages
  500 http://security.ubuntu.com/ubuntu/ saucy-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.5.32-0ubuntu7 0
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu/ saucy/main amd64 
Packages

  In Ubuntu 13.10, the Upstart job and the init.d script do not work
  properly.  In previous versions, the init.d script was a symlink to
  the wrapper script around upstart (/lib/init/upstart-job).  This
  conflict means that if the server was started using the init.d script,
  upstart does not recognize that the server is running and will attempt
  to start a second instance of mysqld.

  Also problematic is that if the upstart job is started using the
  service or start commands, the init.d script's "stop" function runs a
  mysql shutdown, but upstart simply restarts mysqld (because it's
  marked respawn in the upstart config).

  Description: Ubuntu 14.04
  Release: 14.04
  mysql:   mysql-server-5.5.43-0ubuntu0.14.04.1
  The problem in some setup was that the upgrade von 12.04 to 14.04 requres the 
adjustment of the InnoDB log size. Therefore the start of MySQL via upstart 
failed directly while the one via init started successfully and then failed as 
below.
  r...@webserver01.kurt..ref:~# status mysql
  mysql start/running, process 5866
  r...@webserver01.kurt..ref:~# /etc/init.d/mysql stop
  * Stopping MySQL database server mysqld [ OK ]
  r...@webserver01.kurt..ref:~# status mysql
  mysql start/running, process 6101
  r...@webserver01.kurt..ref:~# /etc/init.d/mysql status
  * /usr/bin/mysqladmin Ver 8.42 Distrib 5.5.43, for debian-linux-gnu on x86_64
  Copyright (c) 2000, 2015, Oracle and/or its affiliates. All rights reserved.
  Oracle is a registered trademark of Oracle Corporation and/or its
  affiliates. Other names may be trademarks of their respective
  owners.
  Server version5.5.43-0ubuntu0.14.04.1-log
  Protocol version  10
  ConnectionLocalhost via UNIX socket
  UNIX socket   /var/run/mysqld/mysqld.sock
  Uptime:   7 sec
  Threads: 1 Questions: 108 Slow queries: 0 Opens: 48 Flush tables: 1 Open 
tables: 41 Queries per second avg: 15.428
  r...@webserver01.kurt..ref:~# stop mysql
  mysql stop/waiting
  r...@webserver01.kurt..ref:~# /etc/init.d/mysql status
  * MySQL is stopped.

  This is horrible. The "status" commands report the wrong status and the 
start/stop commands do not work. If our operators are not super careful, 

[Touch-packages] [Bug 1484300] Re: /usr/bin/dialer-app:11:QScopedLoopLevelCounter:QCoreApplication::notifyInternal:sendEvent:QCoreApplicationPrivate::sendPostedEvents:QCoreApplication::sendPostedEvent

[Gustavo Pichorim Boiko]

** Changed in: dialer-app (Ubuntu)
   Status: New => In Progress

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

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

Title:
  /usr/bin/dialer-
  
app:11:QScopedLoopLevelCounter:QCoreApplication::notifyInternal:sendEvent:QCoreApplicationPrivate::sendPostedEvents:QCoreApplication::sendPostedEvents

Status in Canonical System Image:
  In Progress
Status in dialer-app package in Ubuntu:
  In Progress

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

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

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

[Touch-packages] [Bug 1337873] Re: Precise, Trusty, Utopic - ifupdown initialization problems caused by race condition

[Dariusz Gadomski]

** Description changed:

  [Impact]
  
-  * A lack of proper synchronization in ifupdown causes a race condition
+  * Lack of proper synchronization in ifupdown causes a race condition
  resulting in occasional incorrect network interface initialization (e.g.
  in bonding case - wrong bonding settings, network unavailable because
  slave<->master interfaces initialization order was wrong
  
-  * This is very annoying in case of large deployments (e.g. when
+  * This is very annoying in case of large deployments (e.g. when
  bringing up 1000 machines it is almost guaranteed that at least a few of
  them will end up with network down).
  
-  * It has been fixed by introducing hierarchical and per-interface
+  * It has been fixed by introducing hierarchical and per-interface
  locking mechanism ensuring the right order (along with the correct order
  in the /e/n/interfaces file) of initialization
  
  [Test Case]
  
-  1. Create a VM with bonding configured with at least 2 slave interfaces.
-  2. Reboot.
-  3. If all interfaces are up - go to 2.
+  1. Create a VM with bonding configured with at least 2 slave interfaces.
+  2. Reboot.
+  3. If all interfaces are up - go to 2.
  
  [Regression Potential]
  
-  * This change has been introduced upstream in Debian.
-  * It does not require any config changes to existing installations.
+  * This change has been introduced upstream in Debian.
+  * It does not require any config changes to existing installations.
  
  [Other Info]
-  
+ 
  Original bug description:
  
  * please consider my bonding examples are using eth1 and eth2 as slave
   interfaces.
  
  ifupdown some race conditions explained bellow. ifenslave does not
  behave well with sysv networking and upstart network-interface scripts
  running together.
  
  
  case 1)
  (a) ifup eth0 (b) ifup -a for eth0
  -
  1-1. Lock ifstate.lock file.
    1-1. Wait for locking ifstate.lock
    file.
  1-2. Read ifstate file to check
   the target NIC.
  1-3. close(=release) ifstate.lock
   file.
  1-4. Judge that the target NIC
   isn't processed.
    1-2. Read ifstate file to check
     the target NIC.
    1-3. close(=release) ifstate.lock
     file.
    1-4. Judge that the target NIC
     isn't processed.
  2. Lock and update ifstate file.
     Release the lock.
    2. Lock and update ifstate file.
   Release the lock.
  !!!
  
  to be explained
  
  !!!
  case 2)
  (a) ifenslave of eth0  (b) ifenslave of eth0
  --
  3. Execute ifenslave of eth0.  3. Execute ifenslave of eth0.
  4. Link down the target NIC.
  5. Write NIC id to
     /sys/class/net/bond0/bonding
     /slaves then NIC gets up
    4. Link down the target NIC.
    5. Fails to write NIC id to
   /sys/class/net/bond0/bonding/
   slaves it is already written.
  !!!
  
  #
  
   My setup:
  
  root@provisioned:~# cat /etc/modprobe.d/bonding.conf
  alias bond0 bonding options bonding mode=1 arp_interval=2000
  
  Both, /etc/init.d/networking and upstart network-interface begin
  enabled.
  
   Beginning:
  
  root@provisioned:~# cat /etc/network/interfaces
  # /etc/network/interfaces
  
  auto lo
  iface lo inet loopback
  
  auto eth0
  iface eth0 inet dhcp
  
  I'm able to boot with both scripts (networking and network-interface
  enabled) with no problem. I can also boot with only "networking"
  script enabled:
  
  ---
  root@provisioned:~# initctl list | grep network
  network-interface stop/waiting
  networking start/running
  ---
  
  OR only the script "network-interface" enabled:
  
  ---
  root@provisioned:~# initctl list | grep network
  network-interface (eth2) start/running
  network-interface (lo) start/running
  network-interface (eth0) start/running
  network-interface (eth1) start/running
  ---
  
   Enabling bonding:
  
  Following ifenslave configuration example (/usr/share/doc/ifenslave/
  examples/two_hotplug_ethernet), my /etc/network/interfaces has to
  look like this:
  
  ---
  auto eth1
  iface eth1 inet manual
  bond-master bond0
  
  auto eth2
  iface eth2 inet manual
  bond-master bond0
  
  auto bond0
  iface bond0 inet static
  bond-mode 1
  bond-miimon 100
  bond-primary eth1 eth2
   address 192.168.169.1
   netmask 255.255.255.0
   broadcast 192.168.169.255
  ---
  
  Having both scripts running does 

[Touch-packages] [Bug 1508535] Re: Update Google account branding

[Sebastien Bacher]

** Package changed: ubuntu-system-settings (Ubuntu) => ubuntu-system-
settings-online-accounts (Ubuntu)

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

Title:
  Update Google account branding

Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Confirmed

Bug description:
  The Google account icon in the Accounts page uses the old white-
  lowercase-g-on-blue backing.  They updated their logo a while ago to
  use a rainbow-uppercase-G.

  We should update too.

  (I'm sure this isn't the right component, just wasn't sure where to
  put it.)

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

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

[Touch-packages] [Bug 1487530] Re: Confirmation missing for "SMS Received by Recipient(s)"

[Pat McGowan]

** Description changed:

  Confirmation missing for "SMS Received by Recipient(s)"
  Not possible to set this rule anywhere?
  
  (Aquaris E5 OTA-5)
+ 
+ Ofono supports requesting a delivery report with a third option on the
+ SendMessage method. When the report is received an IncomingStatusReport
+ signal is provided.
+ 
+ A setting in messaging app could be added to enable this.

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

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

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

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

** Description changed:

  Confirmation missing for "SMS Received by Recipient(s)"
  Not possible to set this rule anywhere?
  
  (Aquaris E5 OTA-5)
  
  Ofono supports requesting a delivery report with a third option on the
  SendMessage method. When the report is received an IncomingStatusReport
  signal is provided.
  
  A setting in messaging app could be added to enable this.
+ 
+ It seems not all carriers support this feature.

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

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

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

Title:
  Confirmation missing for "SMS Received by Recipient(s)"

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

Bug description:
  Confirmation missing for "SMS Received by Recipient(s)"
  Not possible to set this rule anywhere?

  (Aquaris E5 OTA-5)

  Ofono supports requesting a delivery report with a third option on the
  SendMessage method. When the report is received an
  IncomingStatusReport signal is provided.

  A setting in messaging app could be added to enable this.

  It seems not all carriers support this feature.

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

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

[Touch-packages] [Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices

[Jean-Baptiste Lallement]

I am still seeing this with latest rc-proposed build on arale:
current build number: 144
device name: arale
channel: ubuntu-touch/rc-proposed/meizu.en

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

Title:
  Access points' "PropertiesChanged" dbus signals freeze UI on mobile
  devices

Status in Canonical System Image:
  Fix Released
Status in indicator-network package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu RTM:
  Fix Released

Bug description:
  Krillin, rc-proposed, r83

  
  DESCRIPTION:
  I've been trying to track down the cause of the occasional UI freezes on my 
Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I 
get a burst of "PropertiesChanged" signals in dbus-monitor

  Here's a log of what's shown in dbus-monitor:
  http://pastebin.ubuntu.com/11992322/

  I'd guess the problem is in the code that actually catches the signals
  and acts accordingly.

  HOW TO REPRODUCE: 
  1) Move to a place where many wifi hotspots are available
  2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor"
  3) Use the device while keeping an eye on dbus-monitor output

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

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

[Touch-packages] [Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices

[Jean-Baptiste Lallement]

I am reopening this report given that previous fix didn't entirely fixed
the issue.

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

** Changed in: canonical-devices-system-image
Milestone: ww40-2015 => ww46-2015

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

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

Title:
  Access points' "PropertiesChanged" dbus signals freeze UI on mobile
  devices

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu RTM:
  Fix Released

Bug description:
  Krillin, rc-proposed, r83

  
  DESCRIPTION:
  I've been trying to track down the cause of the occasional UI freezes on my 
Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I 
get a burst of "PropertiesChanged" signals in dbus-monitor

  Here's a log of what's shown in dbus-monitor:
  http://pastebin.ubuntu.com/11992322/

  I'd guess the problem is in the code that actually catches the signals
  and acts accordingly.

  HOW TO REPRODUCE: 
  1) Move to a place where many wifi hotspots are available
  2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor"
  3) Use the device while keeping an eye on dbus-monitor output

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

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

[Touch-packages] [Bug 1488831] Re: booting with slimport connected to nexus4 seems to be an issue

[Michał Sawicz]

** No longer affects: unity8 (Ubuntu)

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

Title:
  booting with slimport connected to nexus4 seems to be an issue

Status in canonical-pocket-desktop:
  In Progress
Status in Mir:
  Invalid
Status in qtmir package in Ubuntu:
  In Progress

Bug description:
  nexus4 vivid+o + silo0
  when booting with the hdmi monitor already connected, it seems to cause some 
issue

  discovered after a couple of reboots
  - experienced that unity8 seemed to take no input or input not active or 
coordinates were off ?
  - when tapping on the greeter password text box sometimes the osk shows up 
but in a very slow fashion or takes 2 taps
  - sometimes the nexus goes out of landscape into portrait and subsequent 
screens are shifted 1/2 way off the screen

  i was ssh'd in, and top did not reveal any apport running.
  usc/unity8 appeared to be normally running, i was able to stop/start unity8

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1488831/+subscriptions

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

[Touch-packages] [Bug 1507463] Re: OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13

[Joseph Salisbury]

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

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

Title:
  OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13

Status in linux package in Ubuntu:
  Incomplete
Status in lxc package in Ubuntu:
  Incomplete

Bug description:
  I am running Ubuntu Trusty (3.13.0-65-generic #106-Ubuntu SMP Fri Oct
  2 22:08:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux).

  There are two issues in OverlayFS as follows:

   1. /proc//fdinfo/ reports wrong mnt_id (non-existent in
  /proc//mountinfo)

   2. /proc//fd/ shows incorrect path for the symlink target

  These issues were previously reported and patched for the Ubuntu Vivid
  kernel (3.19) in bug #1479468, but the patch was not applied to the
  3.13 kernel, possibly because it contains an older version of
  overlayfs.

  These issues are now adversely affecting some versions of lxc when
  used in conjunction with the 3.13 kernel, because lxc has recently
  been patched to pass /proc//fd/ to the mount syscall.  This
  change to lxc was made in response to cve-2015-1335; see bug #1476662.

  The kernel issues cause some overlayfs-backed containers to fail to
  start, with error message,

  strace: mount("/home/ubuntu/test.txt", "/proc/self/fd/16",
  0x7ffd4c3f7fdb, MS_BIND, NULL) = -1 EACCES (Permission denied)

  The mount fails because /proc/self/fd/16, which should point to a file
  in overlayfs, has an invalid value.

  The version of lxc in the trusty-updates repository, lxc-1.0.7-0ubuntu0.7,
  is not affected.  The following versions of lxc are affected:

  repository lxc version
  
  ppa:ubuntu-lxc/lxc-git-stable-1.0  1.0.7+stable~20151014-2143-0ubuntu1~trusty
  ppa:ubuntu-lxc/lxc-git-stable-1.1  1.1.3+stable~20151007-2301-0ubuntu1~trusty
  ppa:ubuntu-lxc/lxc-git-master  1.1.3+master~20151012-0541-0ubuntu1~trusty

  To reproduce the lxc failure-to-start issue:

  # Install the 3.13 kernel and also an affected version of lxc.
  lxc-create -t download -n trusty -- -d ubuntu -r trusty -a amd64;
  touch $HOME/test.txt;
  echo "lxc.mount.entry = $HOME/test.txt home/ubuntu/test.txt none 
bind,create=file 0 0" >> $HOME/.local/share/lxc/trusty/config;
  lxc-clone -s -B overlayfs trusty trusty_overlay;
  lxc-start -n trusty_overlay; # fails to start

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

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

[Touch-packages] [Bug 1488508] Re: Alarm volume set at zero and cannot be changed

[Pat McGowan]

Not enough info to take action

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

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

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

Title:
  Alarm volume set at zero and cannot be changed

Status in Canonical System Image:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Hi

  On a BQ Aquaris 5 with Ubuntu Touch 15.04 (r4), my alarm volume is
  somehow (not by me directly) set to nil; when the alarm goes off, the
  phone only vibrates; during, or after the event, I try to change the
  volume, without success.

  This seems to mimic the noise settings related to the phone ringing
  (which I had set to no volume, and vibrating).

  Best Regards,

  bburg11

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

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

[Touch-packages] [Bug 1508470] Re: sshd wont start for 15.10

[Robie Basak]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

You may find it helpful to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. Please can you
provide steps to reproduce the problem, and then change the bug status
back to New?

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

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

Title:
  sshd wont start for 15.10

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to the latest available packages for Ubuntu 15.10 sshd
  will not start any more. The system aquires an address, but it does
  not start sshd.

  Result: no remote access. On servers this might be fatal, since it
  might be a headless one and without sshd running access is not
  possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ssh (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27
  Uname: Linux 3.13.0-66-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.16
  Architecture: amd64
  Date: Wed Oct 21 15:41:42 2015
  InstallationDate: Installed on 2012-12-12 (1042 days ago)
  InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release 
amd64 (20120817.3)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: openssh
  UpgradeStatus: Upgraded to trusty on 2013-02-11 (981 days ago)

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

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

[Touch-packages] [Bug 1072518] Re: Restart networking crashes dbus and the desktop manager

[Mathew Hodson]

** No longer affects: dbus (Ubuntu)

** No longer affects: sysvinit (Ubuntu)

** No longer affects: upstart (Ubuntu)

** Project changed: dbus => ubuntu

** No longer affects: ubuntu

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

Title:
  Restart networking crashes dbus and the desktop manager

Status in ifupdown package in Ubuntu:
  Fix Released

Bug description:
  === WARNING ===

  Doing:

  sudo restart networking

  or

  sudo /etc/init.d/networking restart.

   WILL TEAR DOWN MOST OF YOUR DESKTOP =

  Networking is a generic job which brings up all networking interfaces
  in the right order at boot.

  It should never be stopped nor restarted.

  It is only stop at shutdown to correctly bring down all the networking
  interfaces in the right order again.

  === DO NOT RESTART NETWORKING ===

  If you want to reconfigure all networking interface you can use
  something like:

   ifdown eth0
   ifup eth0

  Or all interfaces with:

   ifdown -a --exclude=lo && ifup -a --exclude=lo

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

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

[Touch-packages] [Bug 1502883] Re: Impossible to pull to refresh scopes with Qt 5.5

[Timo Jyrinki]

This is indeed fixed with Qt 5.5.1 that is now in the 012 PPA.

** Changed in: qtdeclarative-opensource-src (Ubuntu)
   Status: New => Fix Committed

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

Title:
  Impossible to pull to refresh scopes with Qt 5.5

Status in qtdeclarative-opensource-src package in Ubuntu:
  Fix Committed
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  The pulling to refresh scopes does not work with Qt 5.5, since the
  amount of pixels that can be pulled down is only a few pixels, or at
  least severely less than with Qt 5.4 where the pulling gesture more or
  less follows finger.

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

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

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

[Touch-packages] [Bug 1508357] Re: Tooltips have a black squares outside of its rounded corners

[Treviño]

** No longer affects: compiz (Ubuntu)

** Package changed: gtk+3.0 (Ubuntu) => ubuntu

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

** Changed in: ubuntu
   Status: Confirmed => In Progress

** Changed in: ubuntu
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  Tooltips have a black squares outside of its rounded corners

Status in Ubuntu:
  In Progress

Bug description:
  Hover over any elements on a gtk apps making a tooltip appearing.

  See that the tooltip is rectangular, containing rounded corner with a 
gradient.
  However, the external part is just plain black and don't have transparency as 
expected.

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

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

[Touch-packages] [Bug 1508475] [NEW] Mouse wheel tilt not works; Bug #926917

[John Littleton]

Public bug reported:

https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-
evdev/+bug/926917

I can confirm this issue remains with Ubuntu 14.04.3 LTS.

Mouse is a Microsoft Wireless Laser Mouse 5000 v1.0

Running xev confirms mouse wheel tilt right and left (buttons 6,7) are
being remapped to mouse wheel scroll up and down (buttons 4,5).

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27
Uname: Linux 3.13.0-66-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.16
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed Oct 21 06:41:29 2015
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca]
InstallationDate: Installed on 2014-04-19 (549 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-66-generic 
root=UUID=ff8fdd6c-71d0-41e0-b390-c661e8526916 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/11/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0801
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8B75-V
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0801:bd10/11/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8B75-V:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu2intel1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu2intel1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.911-0intel1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Tue Oct 20 19:37:03 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   25252 
 vendor HSD
xserver.version: 2:1.15.1-0ubuntu2.7

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


** Tags: amd64 apport-bug compiz-0.9 third-party-packages trusty 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/1508475

Title:
  Mouse wheel tilt not works; Bug #926917

Status in xorg package in Ubuntu:
  New

Bug description:
  https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-
  evdev/+bug/926917

  I can confirm this issue remains with Ubuntu 14.04.3 LTS.

  Mouse is a Microsoft Wireless Laser Mouse 5000 v1.0

  Running xev confirms mouse wheel tilt right and left (buttons 6,7) are
  being remapped to mouse wheel scroll up and down (buttons 4,5).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27
  Uname: Linux 3.13.0-66-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.16
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Oct 21 06:41:29 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca]
  InstallationDate: 

[Touch-packages] [Bug 1447182] Re: u1db-qt FTBFS with Qt 5.5

[Timo Jyrinki]

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  u1db-qt FTBFS with Qt 5.5

Status in qtbase-opensource-src package in Ubuntu:
  Fix Committed
Status in u1db-qt package in Ubuntu:
  Invalid

Bug description:
  u1db-qt fails to build with Qt 5.5.

  Build log:

  https://launchpadlibrarian.net/204005182/buildlog_ubuntu-vivid-amd64
  .u1db-
  qt_0.1.5%2B15.04.20150327-0ubuntu2~vivid1~test1~qt550alpha1_BUILDING.txt.gz

  --
  documentation/CMakeFiles/doc.dir/build.make:60: recipe for target 
'documentation/overview.html' failed
  --

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

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

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

[Touch-packages] [Bug 1508054] Re: [desktop] Crashes on startup

[Jamie Strandboge]

09:09 < jdstrand> oSoMoN: we can't fix that in apparmor easyprof
09:10 < jdstrand> oSoMoN: not in a stable update. it will regenerate all 
  apparmor policy for webapps
09:10 < jdstrand> oSoMoN: which is a time consuming operation
09:10 < jdstrand> oSoMoN: it can be fixed in the 16.04 policy
09:10 < oSoMoN> jdstrand, how can we proceed then? other apps embedding a 
webview are going to hit the same issue, I’d think
09:10 < jdstrand> oSoMoN: it can be fixed in the 16.04 policy
09:11 < jdstrand> oSoMoN: the phone is fine
09:11 < oSoMoN> yes, the issue is desktop-specific
09:11 < jdstrand> oSoMoN: what other apps are you talking about?
09:11 < jdstrand> oSoMoN: personal will use the 16.04 policy, which can be fixed
09:12 < oSoMoN> jdstrand, I don’t have any specific example, I guess any app 
with a webview that runs confined, on desktop, will get the 
denials
09:12 < jdstrand> so, I think the path forward is fix webbrowser-app today (use 
  write_path) and then have the 16.04 policy fix this
09:12 < jdstrand> oSoMoN: yes, but those things don't run on the desktop today
09:12 < jdstrand> they will in personal
09:13 < jdstrand> but personal isn't until 16.04 or later

** Changed in: webbrowser-app (Ubuntu)
   Status: Invalid => In Progress

** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
   Importance: Critical => Low

** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
   Status: In Progress => Triaged

** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
 Assignee: Olivier Tilloy (osomon) => (unassigned)

** Tags added: application-confinement

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

Title:
  [desktop] Crashes on startup

Status in Oxide:
  Invalid
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Triaged
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  For a little while now on my development machine (which is a
  Frankenstein environment anyway), which is running wily+overlay,
  webbrowser-app has been crashing on startup.  The console output is
  below.  It looks like a permissions issue?  It may have started around
  the time that webbrowser-app got AppArmor support...

  I don't seem to have a file in /var/crash.  I don't seem to have *any*
  files in /var/crash...  But maybe this log is enough for now.

  
  (webbrowser-app:12313): dconf-CRITICAL **: unable to create file 
'/run/user/1001/dconf/user': Permission denied.  dconf will not work properly.

  (webbrowser-app:12313): dconf-CRITICAL **: unable to create file
  '/run/user/1001/dconf/user': Permission denied.  dconf will not work
  properly.

  (webbrowser-app:12313): dconf-CRITICAL **: unable to create file 
'/run/user/1001/dconf/user': Permission denied.  dconf will not work properly.
  org.gtk.vfs.MountTracker.listMountableInfo call failed: 
GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy 
prevents this sender from sending this message to this recipient; 
type="method_call", sender=":1.148" (uid=1001 pid=12313 comm="webbrowser-app ") 
interface="org.gtk.vfs.MountTracker" member="ListMountableInfo" error 
name="(unset)" requested_reply="0" destination=":1.9" (uid=1001 pid=3669 
comm="/usr/lib/gvfs/gvfsd ") (g-dbus-error-quark, 9)
  shm_open() failed: Permission denied
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/1.3/Sections.qml:96: 
TypeError: Cannot read property 'length' of undefined
  qml: Loaded 3 UA override(s) from 
file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Web/ua-overrides-desktop.js
  [1020/092321:ERROR:shared_memory_posix.cc(290)] Creating shared memory in 
/dev/shm/.org.chromium.Chromium.nxp9C4 failed: Permission denied
  [1020/092321:ERROR:webgraphicscontext3d_command_buffer_impl.cc(210)] 
CommandBufferProxy::Initialize failed.
  [1020/092321:ERROR:webgraphicscontext3d_command_buffer_impl.cc(229)] Failed 
to initialize command buffer.
  [1020/092321:ERROR:shared_memory_posix.cc(290)] Creating shared memory in 
/dev/shm/.org.chromium.Chromium.jaBUVR failed: Permission denied
  [1020/092321:ERROR:shared_memory_posix.cc(290)] Creating shared memory in 
/dev/shm/.org.chromium.Chromium.5McNeF failed: Permission denied
  [1020/092321:ERROR:webgraphicscontext3d_command_buffer_impl.cc(210)] 
CommandBufferProxy::Initialize failed.
  [1020/092321:ERROR:webgraphicscontext3d_command_buffer_impl.cc(229)] Failed 
to initialize command buffer.
  [1020/092321:ERROR:shared_memory_posix.cc(290)] Creating shared memory in 
/dev/shm/.org.chromium.Chromium.O6PKxs failed: Permission denied
  [1020/092321:ERROR:webgraphicscontext3d_command_buffer_impl.cc(210)] 
CommandBufferProxy::Initialize failed.
  [1020/092321:ERROR:webgraphicscontext3d_command_buffer_impl.cc(229)] Failed 
to initialize command buffer.
  

[Touch-packages] [Bug 1500918] Re: rc-proposed location is way out in comparison to ota6

[Alberto Mardegan]

Hi Dave, I wonder if you would be able to collect more logs?

Edit /etc/init/ubuntu-espoo-service.conf and 
/etc/init/ubuntu-location-service.override and change the start sequence to add 
some env vars:
export GLOG_v=200
export GLOG_logtostderr=1
before the exec. Reboot, and start the app. You should have some log files 
under /var/log/upstart/ubuntu-espoo-service.log and 
/var/log/upstart/ubuntu-location-service.log

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

Title:
  rc-proposed location is way out in comparison to ota6

Status in location-service package in Ubuntu:
  Confirmed

Bug description:
  DESCRIPTION:
  Ota 6 accurately positions me on the wednesfield road in rc-proposed it is 
positioning me in Mount Road this is approximately 11 miles across town.

  STEPS:
  1. install rc-proposed
  2. Open locations or pull down on the nearby scope

  EXPECTED:
  I expect rc-proposed to match ota6

  ACTUAL:
  The positioning is approximately 11 miles out

  https://goo.gl/maps/RZ5K3EzhG262

  VERSIONS:
  current build number: 525
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en-proposed
  last update: 2015-09-29 14:44:52
  version version: 525
  version ubuntu: 20150929
  version device: 20150821-736d127
  version custom: 20150925-901-35-40-vivid

  This equates to Image 135 on rc-proposed + custom tarball

  Also is the same on Arale with custom tarball and confirmed on:

  current build number: 124
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-09-29 15:20:36
  version version: 124
  version ubuntu: 20150929
  version device: 20150818-0b38025
  version custom: 20150814-887-8-46

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

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

[Touch-packages] [Bug 1484940] Re: gallery performs slower than similar apps on other platforms

[Pat McGowan]

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

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

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

Title:
  gallery performs slower than similar apps on other platforms

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

Bug description:
  This bug is a bit hard to phrase, because this is not an apples-to-
  apples comparison, except at the highest level.

  BQ report that customers are very unsatisfied with the performance of
  gallery. They are used to having a place which is a collection of
  photos on their phone.

  If they use the same hardware, and keep those photos in the equivalent
  app on android, performance is much better.

  I will attach in a comment a video demonstrating the problem

  Whilst the initial condition is not quite the same, I think the key
  usability concern is the scroll performance, and the heavy use of the
  spinner in place of an actual thumbnail.

  Obviously, there might be many reasons why 'things are slow', but it
  is a core comparison point between handsets to scroll a collection of
  the users photos, and this is a core function of gallery.

  It seems android can deliver this experience with almost no use of
  placeholders. Can Ubuntu?

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

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

[Touch-packages] [Bug 1497666] Re: No right channel sound on Creative Xtreme Audio (CA0106) in Ubuntu 14.04-15.10

[Raymond]

http://cgit.freedesktop.org/pulseaudio/pulseaudio/tree/src/modules/alsa
/alsa-mixer.c


seem pulseaudio only control left channel when it only use the virtual master 
playback volume control


in function element_set_volume, it check the element has left and right channel 


static int element_set_volume(pa_alsa_element *e, snd_mixer_t *m, const 
pa_channel_map *cm, pa_cvolume *v, bool deferred_volume, bool write_to_hw) {

snd_mixer_selem_id_t *sid;
pa_cvolume rv;
snd_mixer_elem_t *me;
snd_mixer_selem_channel_id_t c;
pa_channel_position_mask_t mask = 0;
unsigned k;

pa_assert(m);
pa_assert(e);
pa_assert(cm);
pa_assert(v);
pa_assert(pa_cvolume_compatible_with_channel_map(v, cm));

SELEM_INIT(sid, e->alsa_name);
if (!(me = snd_mixer_find_selem(m, sid))) {
pa_log_warn("Element %s seems to have disappeared.", e->alsa_name);
return -1;
}

pa_cvolume_mute(, cm->channels);

for (c = 0; c <= SND_MIXER_SCHN_LAST; c++) {
int r;
pa_volume_t f = PA_VOLUME_MUTED;
bool found = false;

for (k = 0; k < cm->channels; k++)
if (e->masks[c][e->n_channels-1] & 
PA_CHANNEL_POSITION_MASK(cm->map[k])) {
found = true;
if (v->values[k] > f)
f = v->values[k];
}

if (!found) {
/* Hmm, so this channel does not exist in the volume
 * struct, so let's bind it to the overall max of the
 * volume. */
f = pa_cvolume_max(v);
}

if (e->has_dB) {
long value = to_alsa_dB(f);
int rounding;

if (e->volume_limit >= 0 && value > (e->max_dB * 100))
value = e->max_dB * 100;

if (e->direction == PA_ALSA_DIRECTION_OUTPUT) {
/* If we call set_playback_volume() without checking first
 * if the channel is available, ALSA behaves very
 * strangely and doesn't fail the call */
if (snd_mixer_selem_has_playback_channel(me, c)) {


** Changed in: alsa-driver (Ubuntu)
   Status: New => Incomplete

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

Title:
  No right channel sound on Creative Xtreme Audio (CA0106)  in  Ubuntu
  14.04-15.10

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  After a fresh install of Ubuntu 14.04, 15.04, 15.10 and on the liveCD,
  There is no sound on right channel. But it works perfectly in Win
  7/10. It also worked perfectly on Ubuntu 12.04 My sound card is
  Creative Xtreme Audio (PCI CA0106).

  In the forum, many users also have experienced this bug with the
  incorrect default alsamixer settings.

  http://ubuntuforums.org/showthread.php?t=2217724

  Here are my alsa-info.sh results.

  http://www.alsa-
  project.org/db/?f=e3ae99437c3d283b35cac7c33ace996bedf43a16

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

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

[Touch-packages] [Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices

[Michael Terry]

I was about to do the same.  :)  I still see this issue, just reproduced
it in fact.  The patch that went in seems to sometimes improve things,
but overall this is very easily reproducable still.

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

Title:
  Access points' "PropertiesChanged" dbus signals freeze UI on mobile
  devices

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu RTM:
  Fix Released

Bug description:
  Krillin, rc-proposed, r83

  
  DESCRIPTION:
  I've been trying to track down the cause of the occasional UI freezes on my 
Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I 
get a burst of "PropertiesChanged" signals in dbus-monitor

  Here's a log of what's shown in dbus-monitor:
  http://pastebin.ubuntu.com/11992322/

  I'd guess the problem is in the code that actually catches the signals
  and acts accordingly.

  HOW TO REPRODUCE: 
  1) Move to a place where many wifi hotspots are available
  2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor"
  3) Use the device while keeping an eye on dbus-monitor output

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

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

[Touch-packages] [Bug 1490110] Re: package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100

[Serge Hallyn]

I still think the bug is actually not in lxc.   If I take a vivid cloud
image, manually install the wily lxc packages with dpkg, that works.
Then do-release-upgrade still fails.

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

Title:
  package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 100

Status in apport package in Ubuntu:
  Confirmed
Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  Error during do-releas-update -d from 15.04

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: lxc 1.1.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  Date: Sat Aug 29 10:13:04 2015
  DuplicateSignature: package:lxc:1.1.3-0ubuntu1:subprocess installed 
post-installation script returned error exit status 100
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 100
  InstallationDate: Installed on 2015-08-13 (15 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.1.0-3-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: lxc
  Title: package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 100
  UpgradeStatus: Upgraded to wily on 2015-08-29 (0 days ago)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

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

[Touch-packages] [Bug 1490110] Re: package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100

[Serge Hallyn]

Raising priority since as rbasak pointed out, all vivid cloud image
updates to wily will hit this.

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

Title:
  package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 100

Status in apport package in Ubuntu:
  Confirmed
Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  Error during do-releas-update -d from 15.04

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: lxc 1.1.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  Date: Sat Aug 29 10:13:04 2015
  DuplicateSignature: package:lxc:1.1.3-0ubuntu1:subprocess installed 
post-installation script returned error exit status 100
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 100
  InstallationDate: Installed on 2015-08-13 (15 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.1.0-3-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: lxc
  Title: package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 100
  UpgradeStatus: Upgraded to wily on 2015-08-29 (0 days ago)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

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

[Touch-packages] [Bug 1490110] Re: package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100

[Serge Hallyn]

SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1)
Error in sys.excepthook:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 102, in 
apport_excepthook
pr.add_proc_info(extraenv=['PYTHONPATH', 'PYTHONHOME'])
  File "/usr/lib/python3/dist-packages/apport/report.py", line 535, in 
add_proc_info
raise ValueError('%s does not exist' % self['ExecutablePath'])
ValueError: /usr/bin/python3.4 (deleted) does not exist


apport is trying to report on

root  2584  2583  0 16:54 pts/100:00:12 /usr/bin/python3 /tmp
/ubuntu-release-upgrader-_4pcnnvn/wily --mode=server
--frontend=DistUpgradeViewText --devel-release


but that python binary has been deleted:

sudo ls -l /proc/2584/exe
lrwxrwxrwx 1 root root 0 Oct 21 17:02 /proc/2584/exe -> /usr/bin/python3.4 
(deleted)


So at least there is an apport bug here that apport should know about deleted 
files.

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

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

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

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

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

Title:
  package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 100

Status in apport package in Ubuntu:
  Confirmed
Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  Error during do-releas-update -d from 15.04

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: lxc 1.1.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  Date: Sat Aug 29 10:13:04 2015
  DuplicateSignature: package:lxc:1.1.3-0ubuntu1:subprocess installed 
post-installation script returned error exit status 100
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 100
  InstallationDate: Installed on 2015-08-13 (15 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.1.0-3-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: lxc
  Title: package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 100
  UpgradeStatus: Upgraded to wily on 2015-08-29 (0 days ago)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

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

[Touch-packages] [Bug 995332] Re: Please enhance NetworkManager such that DNSSEC validation is done whenever possible

[Andreas Schildbach]

Does anyone have instructions for how to configure this by hand on a
desktop Ubuntu vivid or wily installation?

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

Title:
  Please enhance NetworkManager such that DNSSEC validation is done
  whenever possible

Status in dnsmasq package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Network Manager in Precise uses a local forwarding DNS server
  (dnsmasq).  This does not perform DNSSEC validation, although it is
  configured to proxy the DNSSEC validation result from the upstream
  server, for which the manpage mentions the following caveat:

  "You should only do this if you trust all the configured upstream
  nameservers and the network between you and them."

  Since not all networks or upstream DNS servers are trustworthy, the
  safest place to perform DNSSEC validation is on the client.  Using a
  local DNS server which cannot validate is a missed opportunity; by
  replacing dnsmasq with a more-capable DNS server (e.g. Unbound)
  security against DNS poisoning and MITM attacks could be improved.

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

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

[Touch-packages] [Bug 1508247] Re: Upgrade failed due to lxc

[Brian Murray]

** Summary changed:

- Upgrade failed due to presence of packages from PPAs
+ Upgrade failed due to lxc

** Package changed: ubuntu-release-upgrader (Ubuntu) => lxc (Ubuntu)

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

Title:
  Upgrade failed due to lxc

Status in lxc package in Ubuntu:
  New

Bug description:
  Upgrade failed due to juju-local and lxc being from PPA instead of
  stock vivid.  Claimed completed upgrade but otherwise did not actually
  upgrade to 15.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: ubuntu-release-upgrader-core 1:15.10.13
  ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  Date: Tue Oct 20 19:17:15 2015
  InstallationDate: Installed on 2015-08-27 (54 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to wily on 2015-10-20 (0 days ago)

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

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

[Touch-packages] [Bug 1483888] Re: Ringtone cannot be heard when jack/headphones plugged

[Pat McGowan]

Other phones seem to always ring through speakers unless silent mode is
on

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

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

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

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

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

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

Title:
  Ringtone cannot be heard when jack/headphones plugged

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  New
Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  Aquaris E5: Ringtone cannot be heard when jack/headphones are plugged.

  This I consider a bug, since user cannot depend on the such a device
  with hearing calls in the morning.

  Typical scenario: listening to music/watching movies during the night
  and falling asleep. It already happened several times to me that I did
  not get awakened by the phone in the morning, since headphones were
  plugged into the device and all the sounds could be heard only in
  headphones.

  (The equivalent for the alarm clock is bug 1364647.)

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

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

[Touch-packages] [Bug 1429887] Re: Sometimes need 3 power button presses to turn on screen

[Michael Terry]

I did some more testing, trying to reproduce this.  I did my usual "get
dbus-daemon to go crazy because I'm running through a bunch of wifi
networks" test in my neighborhood.

After getting my phone to be a bit overloaded, I still couldn't trigger
this bug even once.

But I did notice one oddity -- sometimes the phone screen wouldn't
finish fading in to full brightness.  It would then go to full
brightness if I touched the screen.

But that made me think that there is some mechanism/bug by which the
fade-in early-exits.  So what if this bug is an immediate early-exit to
the fade?  Then second press is actually accurately received as a turn-
off-screen-please request (which flashes the screen to full brightness
for a moment).  And the third is a normal turn-on-request.  Pure
conjecture without much evidence.  Just a thought.

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

Title:
  Sometimes need 3 power button presses to turn on screen

Status in Canonical System Image:
  Incomplete
Status in Unity System Compositor:
  New
Status in powerd package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  [filing here although may be other components]

  Mako running 211 from rtm
   I experienced these symptoms which have been previously mitigated in other 
scenarios.
  Last week while traveling and roaming this happened pretty much 100% of the 
time.
  This occurred in all areas (hotel, MWC, outside, etc)

  Press power button, no response
  Press button again, screen turns on for a few seconds then turns off
  Press button again, either phone resumes or more often the power dialog is 
shown

  When I returned back home the function was normal without reboot or
  other changes.

  The differences in environment:
  Roaming on foreign GSM network
  Lots of Wifi APs not connected

  Attached are some perhaps relevant logs, unfortunately the syslog
  rolled.

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

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

[Touch-packages] [Bug 1449539] Re: nearby scope intermittent.

[Pat McGowan]

Not sure if this will improve with planned enhacnements to how scopes
work with location service

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

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Alejandro J. Cura (alecu)

** Also affects: unity-scopes-shell (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  nearby scope intermittent.

Status in Canonical System Image:
  Confirmed
Status in unity-scopes-shell package in Ubuntu:
  New

Bug description:
  The nearby scope gets the location wrong (seems to use the city
  selected in the time settings). When Refreshing the scope the data is
  intermittent. Sometimes information is displayed sometimes its blank.

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

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

[Touch-packages] [Bug 1495943] Re: gvfs-trash doesn't add "trash::" attrs to file which is moved to Trash

[Monsta]

Ok, all good now :)

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

Title:
  gvfs-trash doesn't add "trash::" attrs to file which is moved to Trash

Status in GLib:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in gvfs package in Ubuntu:
  Fix Released
Status in glib2.0 package in Debian:
  Fix Released

Bug description:
  [System]

  Ubuntu MATE 15.10, fully updated.

  [Steps to reproduce]

  1. Create an empty file: touch ~/test
  2. Move it to trash: gvfs-trash ~/test
  3. Launch some file manager, browse Trash folder and try to restore the file. 
I've tested it with the following file managers: Caja, Nemo, Nautilus and 
Thunar.

  [Expected result]

  The file should be restored to its original location.

  [What happens instead]

  The file manager complains that it can't determine the original
  location of the file, and so doesn't restore it.

  [Details]

  When moving file to Trash, gvfs-trash does not add trash::orig-path
  and trash::deletion-date attributes to it. Without that the file
  manager can't determine the original location of the file, and hence
  can't restore it.

  You can check the file attributes by printing the moved file's info:
  gvfs-info trash:///test

  [Regression description]

  Restoring the files has been working fine in Ubuntu 14.04 and 15.04.
  This bug appeared only in 15.10, so it's a regression.

  You can see the gvfs-info output from 15.04 and 15.10 in the
  attachments below.

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

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

[Touch-packages] [Bug 1508247] [NEW] Upgrade failed due to lxc

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Upgrade failed due to juju-local and lxc being from PPA instead of stock
vivid.  Claimed completed upgrade but otherwise did not actually upgrade
to 15.10.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: ubuntu-release-upgrader-core 1:15.10.13
ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
Uname: Linux 3.19.0-30-generic x86_64
ApportVersion: 2.19.1-0ubuntu3
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: XFCE
Date: Tue Oct 20 19:17:15 2015
InstallationDate: Installed on 2015-08-27 (54 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: Upgraded to wily on 2015-10-20 (0 days ago)

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


** Tags: amd64 apport-bug dist-upgrade iso-testing wily
-- 
Upgrade failed due to lxc
https://bugs.launchpad.net/bugs/1508247
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to lxc 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 1483806] Re: addSource to a Playlist are ignored if it's not part of a player

[Pat McGowan]

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

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

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

Title:
  addSource to a Playlist are ignored if it's not part of a player

Status in Canonical System Image:
  Fix Committed
Status in qtmultimedia-opensource-src package in Ubuntu:
  Fix Committed

Bug description:
  I was doing

  audio.playlist = null;

  playlist.clear();
  // Look for newSource in newPlaylist
  for (var i in newPlaylist) {
  playlist.addSource(newPlaylist[i]);
  }
  audio.playlist = playlist;

  And the addSource didn't do anything, i've now moved the

  audio.playlist = playlist;

  before the addSource and it works.

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

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

[Touch-packages] [Bug 1490110] Re: package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100

[Serge Hallyn]

The original complaint appears to be:

dpkg: dependency problems prevent configuration of liblxc1:
 liblxc1 depends on libdbus-1-3 (>= 1.9.14); however:
  Version of libdbus-1-3:amd64 on system is 1.8.12-1ubuntu5.

The libdbus version being installed is higher than that.

Note that that dependency is automatically added (it's not in
debian/control).

We could require dbus upgrade to happen before lxc.

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

Title:
  package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 100

Status in apport package in Ubuntu:
  Confirmed
Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  Error during do-releas-update -d from 15.04

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: lxc 1.1.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  Date: Sat Aug 29 10:13:04 2015
  DuplicateSignature: package:lxc:1.1.3-0ubuntu1:subprocess installed 
post-installation script returned error exit status 100
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 100
  InstallationDate: Installed on 2015-08-13 (15 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.1.0-3-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: lxc
  Title: package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 100
  UpgradeStatus: Upgraded to wily on 2015-08-29 (0 days ago)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

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

[Touch-packages] [Bug 1375215] Re: System runs out of memory - white screens frequently seen in web renderers

[Ilonka]

After OTA7 I have still white screens in a WebApp. Mostly when enter App again 
coming from another App, but also during using the App.
I use a BQ4.5

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

Title:
  System runs out of memory - white screens frequently seen in web
  renderers

Status in Canonical System Image:
  Fix Released
Status in oxide-qt package in Ubuntu:
  Invalid
Status in webbrowser-app package in Ubuntu:
  Fix Committed

Bug description:
  [See latest comments for recent repro notes]

  krillin 14.09 #2 + all updates applied

  After running the system for a while (few minutes) the system runs out of 
memory and start killing processes.
  It is very visible with the webbrowser or webapps because it renders the page 
and displays a white page when oxide-render is killed. Although it is not 
specific to oxide, and any app are killed (address-book, system-settings, ...) 
You can clearly notice that other apps are being killed because when you switch 
to the app it's all blurry and take a while to reload, also it loses its state 
(for example, you lose the message you were writing in the messaging-app)

  There is no specific steps to reproduce. I have several scopes enabled
  (photos, nearby, news) You don't have to have tons of apps open to
  reproduce this. Launching the webbrowser or a webapps and navigating
  on the phone between the scopes and the open app seems enough for the
  system to start killing processes.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: liboxideqtcore0 1.2.0-0ubuntu1 [origin: Ubuntu RTM]
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: armhf
  Date: Mon Sep 29 12:51:34 2014
  InstallationDate: Installed on 2014-09-24 (5 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140924-030204)
  SourcePackage: oxide-qt
  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/1375215/+subscriptions

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

[Touch-packages] [Bug 1398614] Re: mediascanner-service-2.0 using large amounts of CPU

[Martyn Lloyd-Kelly]

Every time I plug in my external 1TB HDD this process consumes up to
101.8%(!) of my CPU and prevents me from doing anything on the computer
unless I physically turn off the HDD.  I thought that after its first
scan data is cached? Instead, the issue appears to be ongoing for me.
I'm currently using Ubuntu 14.10 LTS and I haven't purged the package
since I use the Ubuntu SDK and apparently the "mediascanner-service"
package is a dependency?  Absolutely abominable programming, whoever
released this into the wild needs to be spoken to, urgently.

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

Title:
  mediascanner-service-2.0 using large amounts of CPU

Status in mediascanner2 package in Ubuntu:
  Confirmed

Bug description:
  Each time I plug my external USB hard disk the mediascanner-service process 
is activ and is using large amount of CPU for long minutes without interruption.
  I have the same problem in utopic and vivid

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: mediascanner2.0 0.105+15.04.20141030.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Dec  3 00:29:43 2014
  InstallationDate: Installed on 2011-05-26 (1286 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  SourcePackage: mediascanner2
  UpgradeStatus: Upgraded to vivid on 2013-11-26 (371 days ago)

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

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

[Touch-packages] [Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices

[Launchpad Bug Tracker]

** Branch linked: lp:~phablet-team/network-manager/vivid-phone-overlay

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

Title:
  Access points' "PropertiesChanged" dbus signals freeze UI on mobile
  devices

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu RTM:
  Fix Released

Bug description:
  Krillin, rc-proposed, r83

  
  DESCRIPTION:
  I've been trying to track down the cause of the occasional UI freezes on my 
Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I 
get a burst of "PropertiesChanged" signals in dbus-monitor

  Here's a log of what's shown in dbus-monitor:
  http://pastebin.ubuntu.com/11992322/

  I'd guess the problem is in the code that actually catches the signals
  and acts accordingly.

  HOW TO REPRODUCE: 
  1) Move to a place where many wifi hotspots are available
  2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor"
  3) Use the device while keeping an eye on dbus-monitor output

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

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

[Touch-packages] [Bug 1508564] [NEW] cross binutils don't include the system search paths

[Matthias Klose]

Public bug reported:

e.g.

$ powerpc64le-linux-gnu-ld --verbose |grep SEARCH_DIR 
SEARCH_DIR("/usr/powerpc64le-linux-gnu/lib64le"); 
SEARCH_DIR("/usr/powerpc64le-linux-gnu/lib");

that should read (like in vivid):
$ powerpc64le-linux-gnu-ld --verbose |grep SEARCH_DIR
SEARCH_DIR("=/usr/powerpc64le-linux-gnu/lib64le"); 
SEARCH_DIR("=/usr/local/lib64le"); SEARCH_DIR("=/lib64le"); 
SEARCH_DIR("=/usr/lib64le"); SEARCH_DIR("=/usr/powerpc64le-linux-gnu/lib"); 
SEARCH_DIR("=/usr/local/lib/powerpc64le-linux-gnu"); 
SEARCH_DIR("=/usr/local/lib"); SEARCH_DIR("=/lib/powerpc64le-linux-gnu"); 
SEARCH_DIR("=/lib"); SEARCH_DIR("=/usr/lib/powerpc64le-linux-gnu"); 
SEARCH_DIR("=/usr/lib");

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

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

Title:
  cross binutils don't include the system search paths

Status in binutils package in Ubuntu:
  New

Bug description:
  e.g.

  $ powerpc64le-linux-gnu-ld --verbose |grep SEARCH_DIR 
  SEARCH_DIR("/usr/powerpc64le-linux-gnu/lib64le"); 
SEARCH_DIR("/usr/powerpc64le-linux-gnu/lib");

  that should read (like in vivid):
  $ powerpc64le-linux-gnu-ld --verbose |grep SEARCH_DIR
  SEARCH_DIR("=/usr/powerpc64le-linux-gnu/lib64le"); 
SEARCH_DIR("=/usr/local/lib64le"); SEARCH_DIR("=/lib64le"); 
SEARCH_DIR("=/usr/lib64le"); SEARCH_DIR("=/usr/powerpc64le-linux-gnu/lib"); 
SEARCH_DIR("=/usr/local/lib/powerpc64le-linux-gnu"); 
SEARCH_DIR("=/usr/local/lib"); SEARCH_DIR("=/lib/powerpc64le-linux-gnu"); 
SEARCH_DIR("=/lib"); SEARCH_DIR("=/usr/lib/powerpc64le-linux-gnu"); 
SEARCH_DIR("=/usr/lib");

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

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

[Touch-packages] [Bug 1508563] [NEW] Shutdown dialog appears on resume under high load

[Michael Terry]

Public bug reported:

This is very similar to old friends bug 1383277 and bug 1410830.

But we never fully vanquished the beast.  The dialog still appears on
resume in some situations where the system is very loaded.

I suspect what is happening is that we process the power-button-release
event so much later than the -press event because of the load.  And
think that the user has been holding it down this whole time.

But instead, we should compare event timestamps to determine that.
(Which I'm assuming we aren't doing because this bug exists.)

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

Title:
  Shutdown dialog appears on resume under high load

Status in unity8 package in Ubuntu:
  New

Bug description:
  This is very similar to old friends bug 1383277 and bug 1410830.

  But we never fully vanquished the beast.  The dialog still appears on
  resume in some situations where the system is very loaded.

  I suspect what is happening is that we process the power-button-
  release event so much later than the -press event because of the load.
  And think that the user has been holding it down this whole time.

  But instead, we should compare event timestamps to determine that.
  (Which I'm assuming we aren't doing because this bug exists.)

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

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

[Touch-packages] [Bug 1495943] Re: gvfs-trash doesn't add "trash::" attrs to file which is moved to Trash

[Bug Watch Updater]

** Changed in: glib2.0 (Debian)
   Status: Confirmed => Fix Released

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

Title:
  gvfs-trash doesn't add "trash::" attrs to file which is moved to Trash

Status in GLib:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in gvfs package in Ubuntu:
  Fix Released
Status in glib2.0 package in Debian:
  Fix Released

Bug description:
  [System]

  Ubuntu MATE 15.10, fully updated.

  [Steps to reproduce]

  1. Create an empty file: touch ~/test
  2. Move it to trash: gvfs-trash ~/test
  3. Launch some file manager, browse Trash folder and try to restore the file. 
I've tested it with the following file managers: Caja, Nemo, Nautilus and 
Thunar.

  [Expected result]

  The file should be restored to its original location.

  [What happens instead]

  The file manager complains that it can't determine the original
  location of the file, and so doesn't restore it.

  [Details]

  When moving file to Trash, gvfs-trash does not add trash::orig-path
  and trash::deletion-date attributes to it. Without that the file
  manager can't determine the original location of the file, and hence
  can't restore it.

  You can check the file attributes by printing the moved file's info:
  gvfs-info trash:///test

  [Regression description]

  Restoring the files has been working fine in Ubuntu 14.04 and 15.04.
  This bug appeared only in 15.10, so it's a regression.

  You can see the gvfs-info output from 15.04 and 15.10 in the
  attachments below.

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

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

[Touch-packages] [Bug 1447654] Re: installing policykit-1 hangs under systemd

[Acidburn_Zero]

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

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

Title:
  installing policykit-1 hangs under systemd

Status in policykit-1 package in Ubuntu:
  Fix Released
Status in policykit-1-gnome package in Ubuntu:
  New
Status in policykit-1 source package in Vivid:
  Fix Committed
Status in policykit-1 package in Debian:
  Fix Committed

Bug description:
  I've installed 15.04 using the current amd64 netboot.tar.gz (MD5 =
  6566065bf73a9c81feeddf5520dda122). It installs fine, but I'm getting
  errors installing packages (such as lubuntu-core).

  Last few lines from apt-get:
  Processing triggers for systemd (219-7ubuntu3) ...
  Error getting authority: Error initializing authority: Error calling 
StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached 
(g-io-error-quark, 24)
  Failed to execute operation: Connection timed out
  dpkg: error processing package systemd (--unpack):
   subprocess installed post-installation script returned error exit status 1
  Processing triggers for libglib2.0-0:amd64 (2.44.0-1ubuntu3) ...
  Processing triggers for shared-mime-info (1.3-1) ...
  Processing triggers for mime-support (3.58ubuntu1) ...
  Processing triggers for udev (219-7ubuntu3) ...
  Processing triggers for dbus (1.8.12-1ubuntu5) ...
  Errors were encountered while processing:
   systemd
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  I've done a second install using the server iso and lubuntu-core
  installs fine on that. The only thing different was my install media.

  SRU TEST CASE:
  - Boot a minimal VM and purge "apport policykit-1", or do the above netboot 
installation.
  - sudo apt-get install policykit-1 apport
  - The above hangs on the systemd triggers and eventually fails. It should 
succeed fine with this update.

  Regression potential: Very low: This update avoids that systemd tries
  to start up polkit while it's unpacked but not configured, which is
  exactly the case that can't work. If there's anything wrong with the
  postinst and the rm for the temporary masking symlink does not get run
  for some reason, the next reboot will clean it up anyway. So the fix
  is a no-change operation for anything but first install.

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

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

[Touch-packages] [Bug 1481876] Re: Add iw to touch images

[Pat McGowan]

added on 9/15

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

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

** Changed in: ubuntu-touch-meta (Ubuntu)
   Status: New => Fix Released

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

Title:
  Add iw to touch images

Status in Canonical System Image:
  Fix Released
Status in ubuntu-touch-meta package in Ubuntu:
  Fix Released

Bug description:
  Add the iw package to the seed.

  This package includes the iw command, which is the modern equivalent
  of iwconfig ( included in our images via the wireless-tools package ).
  It uses the nl80211 interface to query and configure wireless devices
  from the command-line, and therefore is an extremely useful tool for
  debugging customer issues.

  There are no external dependencies, and the package consumes 159kb.

  This is being reported against mako ( ubuntu-touch/rc-proposed/ubuntu,
  #202 ).

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

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

[Touch-packages] [Bug 1492161] Re: Messaging app sluggish after OTA-6

[Ari Börde Kröyer]

The description above quite accurately describes the behavior I am
experiencing on my handset (BQ 4.5), both before and after upgrading to
OTA-7. The only difference I experience is that the time before the
contact names are displayed can be twice what is mentioned on occasions.
(My address book has approximately 1000 entries.)

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

Title:
  Messaging app sluggish after OTA-6

Status in messaging-app package in Ubuntu:
  Confirmed

Bug description:
  Since OTA-6 on Bq Aquaris 4.5, the new messaging app is just
  unbearably slow. The app is very unresponsive and everything seems to
  take very long. Opening the app takes about 5 seconds, displaying
  contact names instead of numbers another 5 secs, opening a chat >=5
  secs, sending message after pressing button some 3 seconds etc.
  Sometimes the app sort of pauses while typing, then after a few
  seconds showing the characters that have been entered.

  Unfortunately, the latency in the app is so bad it is almost unusable.

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

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

[Touch-packages] [Bug 1490110] Re: package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100

[Serge Hallyn]

But even when pre-installing the newer dbus, it still fails with the
invoke-rc.d failure.

I can't explain that one, have no idea why it is trying to use the
/etc/init.d script.

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

Title:
  package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 100

Status in apport package in Ubuntu:
  Confirmed
Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  Error during do-releas-update -d from 15.04

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: lxc 1.1.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  Date: Sat Aug 29 10:13:04 2015
  DuplicateSignature: package:lxc:1.1.3-0ubuntu1:subprocess installed 
post-installation script returned error exit status 100
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 100
  InstallationDate: Installed on 2015-08-13 (15 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.1.0-3-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: lxc
  Title: package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 100
  UpgradeStatus: Upgraded to wily on 2015-08-29 (0 days ago)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

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

[Touch-packages] [Bug 1447605] Re: Video mode should not have an HDR setting

[Pat McGowan]

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

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

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

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

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

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

Title:
  Video mode should not have an HDR setting

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

Bug description:
  Version: ubuntu-touch/stable/bq-aquaris.en r21 krillin
  Version: ubuntu-touch/stable/bq-aquaris.en r21 vegeta
  Version: ubuntu-touch/devel-proposed/krillin.en r59 krillin

  Steps to reproduce:
   * open camera app
   * select video mode
   * swipe up from bottom edge
   * note settings available

  Expected results:
   - only settings relevant to video recording are displayed

  Actual results:
   - HDR is shown but isn't applicable to video mode

To manage notifications about this bug go to:
https://bugs.launchpad.net/camera-app/+bug/1447605/+subscriptions

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

[Touch-packages] [Bug 1508593] Re: [Hyper-V] x86/ioapic: Disable interrupts when re-routing legacy IRQs

[Joshua R. Poulson]

Argh, this should be in linux-kernel, not systemd.

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

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

** No longer affects: systemd (Ubuntu)

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

Title:
  [Hyper-V] x86/ioapic: Disable interrupts when re-routing legacy IRQs

Status in linux-kernel package in Ubuntu:
  New

Bug description:
  A sporadic hang with consequent crash is observed when booting Hyper-V
  Gen1 guests...

  Sauce request for upstream submission:

  https://lkml.org/lkml/2015/10/15/673

  From Vitaly Kuznetsov <> 
  Subject [PATCH] x86/ioapic: Disable interrupts when re-routing legacy IRQs 
  Date Thu, 15 Oct 2015 19:42:23 +0200 

  A sporadic hang with consequent crash is observed when booting Hyper-V Gen1
  guests:

   Call Trace:

[] ? trace_hardirqs_off+0xd/0x10
[] queue_work_on+0x46/0x90
[] ? add_interrupt_randomness+0x176/0x1d0
...

[] ? _raw_spin_unlock_irqrestore+0x3b/0x60
[] __irq_put_desc_unlock+0x1e/0x40
[] irq_modify_status+0xb5/0xd0
[] mp_register_handler+0x4b/0x70
[] mp_irqdomain_alloc+0x1ea/0x2a0
[] irq_domain_alloc_irqs_recursive+0x40/0xa0
[] __irq_domain_alloc_irqs+0x13c/0x2b0
[] alloc_isa_irq_from_domain.isra.1+0xc0/0xe0
[] mp_map_pin_to_irq+0x165/0x2d0
[] pin_2_irq+0x47/0x80
[] setup_IO_APIC+0xfe/0x802
...
[] ? rest_init+0x140/0x140
  The issue is easily reproducible with a simple instrumentation: if
  mdelay(10) is put between mp_setup_entry() and mp_register_handler() calls
  in mp_irqdomain_alloc() Hyper-V guest always fails to boot when re-routing
  IRQ0. The issue seems to be caused by the fact that we don't disable
  interrupts while doing IOPIC programming for legacy IRQs and IRQ0 actually
  happens. Decorate manipulations with legacy IRQs with local_irq_save()/
  local_irq_restore().

  Cc: Thomas Gleixner 
  Cc: Ingo Molnar 
  Cc: "H. Peter Anvin" 
  Cc: Jiang Liu 
  Cc: Yinghai Lu 
  Cc: K. Y. Srinivasan 
  Signed-off-by: Vitaly Kuznetsov 
  ---
  It may make sense to have interrupts disabled for non-legacy IRQs as well
  but I'm unaware of any bugs with them at this moment.
  ---
   arch/x86/kernel/apic/io_apic.c | 8 +++-
   1 file changed, 7 insertions(+), 1 deletion(-)
  diff --git a/arch/x86/kernel/apic/io_apic.c b/arch/x86/kernel/apic/io_apic.c
  index 5c60bb1..9aac777 100644
  --- a/arch/x86/kernel/apic/io_apic.c
  +++ b/arch/x86/kernel/apic/io_apic.c
  @@ -2907,6 +2907,7 @@ int mp_irqdomain_alloc(struct irq_domain *domain, 
unsigned int virq,
struct irq_data *irq_data;
struct mp_chip_data *data;
struct irq_alloc_info *info = arg;
  + unsigned long flags = 0;
   
if (!info || nr_irqs > 1)
return -EINVAL;
  @@ -2939,11 +2940,16 @@ int mp_irqdomain_alloc(struct irq_domain *domain, 
unsigned int virq,
   
cfg = irqd_cfg(irq_data);
add_pin_to_irq_node(data, ioapic_alloc_attr_node(info), ioapic, pin);
  +
  + if (virq < nr_legacy_irqs())
  + local_irq_save(flags);
if (info->ioapic_entry)
mp_setup_entry(cfg, data, info->ioapic_entry);
mp_register_handler(virq, data->trigger);
  - if (virq < nr_legacy_irqs())
  + if (virq < nr_legacy_irqs()) {
legacy_pic->mask(virq);
  + local_irq_restore(flags);
  + }
   
apic_printk(APIC_VERBOSE, KERN_DEBUG
"IOAPIC[%d]: Set routing entry (%d-%d -> 0x%x -> IRQ %d 
Mode:%i Active:%i Dest:%d)\n",
  -- 
  2.4.3

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

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

[Touch-packages] [Bug 1508593] [NEW] [Hyper-V] x86/ioapic: Disable interrupts when re-routing legacy IRQs

[Joshua R. Poulson]

Public bug reported:

A sporadic hang with consequent crash is observed when booting Hyper-V
Gen1 guests...

Sauce request for upstream submission:

https://lkml.org/lkml/2015/10/15/673

>From Vitaly Kuznetsov <> 
Subject [PATCH] x86/ioapic: Disable interrupts when re-routing legacy IRQs 
Date Thu, 15 Oct 2015 19:42:23 +0200 

A sporadic hang with consequent crash is observed when booting Hyper-V Gen1
guests:

 Call Trace:
  
  [] ? trace_hardirqs_off+0xd/0x10
  [] queue_work_on+0x46/0x90
  [] ? add_interrupt_randomness+0x176/0x1d0
  ...
  
  [] ? _raw_spin_unlock_irqrestore+0x3b/0x60
  [] __irq_put_desc_unlock+0x1e/0x40
  [] irq_modify_status+0xb5/0xd0
  [] mp_register_handler+0x4b/0x70
  [] mp_irqdomain_alloc+0x1ea/0x2a0
  [] irq_domain_alloc_irqs_recursive+0x40/0xa0
  [] __irq_domain_alloc_irqs+0x13c/0x2b0
  [] alloc_isa_irq_from_domain.isra.1+0xc0/0xe0
  [] mp_map_pin_to_irq+0x165/0x2d0
  [] pin_2_irq+0x47/0x80
  [] setup_IO_APIC+0xfe/0x802
  ...
  [] ? rest_init+0x140/0x140
The issue is easily reproducible with a simple instrumentation: if
mdelay(10) is put between mp_setup_entry() and mp_register_handler() calls
in mp_irqdomain_alloc() Hyper-V guest always fails to boot when re-routing
IRQ0. The issue seems to be caused by the fact that we don't disable
interrupts while doing IOPIC programming for legacy IRQs and IRQ0 actually
happens. Decorate manipulations with legacy IRQs with local_irq_save()/
local_irq_restore().

Cc: Thomas Gleixner 
Cc: Ingo Molnar 
Cc: "H. Peter Anvin" 
Cc: Jiang Liu 
Cc: Yinghai Lu 
Cc: K. Y. Srinivasan 
Signed-off-by: Vitaly Kuznetsov 
---
It may make sense to have interrupts disabled for non-legacy IRQs as well
but I'm unaware of any bugs with them at this moment.
---
 arch/x86/kernel/apic/io_apic.c | 8 +++-
 1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/arch/x86/kernel/apic/io_apic.c b/arch/x86/kernel/apic/io_apic.c
index 5c60bb1..9aac777 100644
--- a/arch/x86/kernel/apic/io_apic.c
+++ b/arch/x86/kernel/apic/io_apic.c
@@ -2907,6 +2907,7 @@ int mp_irqdomain_alloc(struct irq_domain *domain, 
unsigned int virq,
struct irq_data *irq_data;
struct mp_chip_data *data;
struct irq_alloc_info *info = arg;
+   unsigned long flags = 0;
 
if (!info || nr_irqs > 1)
return -EINVAL;
@@ -2939,11 +2940,16 @@ int mp_irqdomain_alloc(struct irq_domain *domain, 
unsigned int virq,
 
cfg = irqd_cfg(irq_data);
add_pin_to_irq_node(data, ioapic_alloc_attr_node(info), ioapic, pin);
+
+   if (virq < nr_legacy_irqs())
+   local_irq_save(flags);
if (info->ioapic_entry)
mp_setup_entry(cfg, data, info->ioapic_entry);
mp_register_handler(virq, data->trigger);
-   if (virq < nr_legacy_irqs())
+   if (virq < nr_legacy_irqs()) {
legacy_pic->mask(virq);
+   local_irq_restore(flags);
+   }
 
apic_printk(APIC_VERBOSE, KERN_DEBUG
"IOAPIC[%d]: Set routing entry (%d-%d -> 0x%x -> IRQ %d 
Mode:%i Active:%i Dest:%d)\n",
-- 
2.4.3

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

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

Title:
  [Hyper-V] x86/ioapic: Disable interrupts when re-routing legacy IRQs

Status in linux-kernel package in Ubuntu:
  New

Bug description:
  A sporadic hang with consequent crash is observed when booting Hyper-V
  Gen1 guests...

  Sauce request for upstream submission:

  https://lkml.org/lkml/2015/10/15/673

  From Vitaly Kuznetsov <> 
  Subject [PATCH] x86/ioapic: Disable interrupts when re-routing legacy IRQs 
  Date Thu, 15 Oct 2015 19:42:23 +0200 

  A sporadic hang with consequent crash is observed when booting Hyper-V Gen1
  guests:

   Call Trace:

[] ? trace_hardirqs_off+0xd/0x10
[] queue_work_on+0x46/0x90
[] ? add_interrupt_randomness+0x176/0x1d0
...

[] ? _raw_spin_unlock_irqrestore+0x3b/0x60
[] __irq_put_desc_unlock+0x1e/0x40
[] irq_modify_status+0xb5/0xd0
[] mp_register_handler+0x4b/0x70
[] mp_irqdomain_alloc+0x1ea/0x2a0
[] irq_domain_alloc_irqs_recursive+0x40/0xa0
[] __irq_domain_alloc_irqs+0x13c/0x2b0
[] alloc_isa_irq_from_domain.isra.1+0xc0/0xe0
[] mp_map_pin_to_irq+0x165/0x2d0
[] pin_2_irq+0x47/0x80
[] setup_IO_APIC+0xfe/0x802
...
[] ? rest_init+0x140/0x140
  The issue is easily reproducible with a simple instrumentation: if
  mdelay(10) is put between mp_setup_entry() and mp_register_handler() calls
  in mp_irqdomain_alloc() Hyper-V guest always fails to boot when re-routing
  IRQ0. The issue seems to be caused by the fact that we don't disable
  interrupts while doing IOPIC programming for 

[Touch-packages] [Bug 1315434] Re: Mouse with no time remaining estimate showing in preference to battery being charged

[Don McCants]

Found specifics around the new issue and a temporary fix.

The last patch/update from Elementary changed the referred file name to :
95-upower-csr.rule

Where it had previously been:
95-upower-csr.rules

Traditional .rules files are named with an "s" on the end. So any edits
made as indicated in this thread did not work. Making changes to the
.rule file followed by a restart fixed the issue.

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

Title:
  Mouse with no time remaining estimate showing in preference to battery
  being charged

Status in indicator-power package in Ubuntu:
  In Progress

Bug description:
  When my laptop battery is in a charging state, but is not fully
  charged, I expect it to be displayed in preference to my mouse, which
  has no time remaining estimate.

  The spec here:

  https://wiki.ubuntu.com/Power

  says:

  "If anything is discharging, the menu title should represent the
  component (not battery, but component) that is estimated to lose power
  first. For example, if your notebook battery is estimated to discharge
  in 1 hour 47 minutes, and your wireless mouse battery is estimated to
  discharge in 27 minutes, the menu title should represent the mouse. "

  but there doesn't seem to be any guideline to what happens when a
  battery is being charged.

  I suggest the time remaining to charge a battery should be displayed
  in preference to the power level in a wireless mouse.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-power 12.10.6+14.04.20140411-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May  2 11:50:36 2014
  InstallationDate: Installed on 2013-11-26 (156 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: indicator-power
  UpgradeStatus: Upgraded to trusty on 2014-01-17 (104 days ago)

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

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

[Touch-packages] [Bug 1508607] [NEW] Build with multiarch support

[Robert Ancell]

Public bug reported:

Build with multiarch support

** Affects: gupnp (Ubuntu)
 Importance: Medium
 Status: Triaged


** Tags: multiarch

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

Title:
  Build with multiarch support

Status in gupnp package in Ubuntu:
  Triaged

Bug description:
  Build with multiarch support

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

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

[Touch-packages] [Bug 1508605] [NEW] Build with multiarch support

[Robert Ancell]

Public bug reported:

Build with multiarch support

** Affects: libzeitgeist (Ubuntu)
 Importance: Medium
 Status: Triaged


** Tags: multiarch

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

Title:
  Build with multiarch support

Status in libzeitgeist package in Ubuntu:
  Triaged

Bug description:
  Build with multiarch support

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

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

[Touch-packages] [Bug 1508577] Re: [wily] installing juju-local on ARM64 failed. broken apt dependency

[Curtis Hovey]

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

** Changed in: juju-core
   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/1508577

Title:
  [wily] installing juju-local on ARM64 failed. broken apt dependency

Status in juju-core:
  Invalid
Status in lxc package in Ubuntu:
  New

Bug description:
  Installing juju-local on ARM64 fails due to broken dependency.
  running apt-get install -f does not solve this.

  Setting up lxc (1.1.4-0ubuntu1) ...
  Job for lxc-net.service failed because the control process exited with error 
code. See "systemctl status lxc-net.service" and "journalctl -xe" for details.
  invoke-rc.d: initscript lxc-net, action "start" failed.
  dpkg: error processing package lxc (--configure):
   subprocess installed post-installation script returned error exit status 1
  dpkg: dependency problems prevent configuration of lxc-templates:
   lxc-templates depends on lxc (>= 0.8.0~rc1-4ubuntu43); however:
    Package lxc is not configured yet.

  dpkg: error processing package lxc-templates (--configure):
   dependency problems - leaving unconfigured
  Setting up lxcfs (0.10-0ubuntu2) ...
  update-alternatives: using /usr/lib/juju-1.24.6/bin/juju to provide 
/usr/bin/juju (juju) in auto mode
  Setting up rsyslog-gnutls (8.12.0-1ubuntu2) ...
  dpkg: dependency problems prevent configuration of juju-local:
   juju-local depends on lxc (>= 1.0.0~alpha1-0ubuntu14); however:
    Package lxc is not configured yet.
   juju-local depends on lxc-templates; however:
    Package lxc-templates is not configured yet.

  dpkg: error processing package juju-local (--configure):
   dependency problems - leaving unconfigured

  ubuntu@machine:~$ sudo apt-get install -f
  sudo: unable to resolve host bandera
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
    libdw1 libelf1 libunwind8
  Use 'apt-get autoremove' to remove them.
  0 upgraded, 0 newly installed, 0 to remove and 8 not upgraded.
  3 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  perl: warning: Setting locale failed.
  perl: warning: Please check that your locale settings:
   LANGUAGE = (unset),
   LC_ALL = (unset),
   LANG = "en_US.UTF-8"
  are supported and installed on your system.
  perl: warning: Falling back to the standard locale ("C").
  Setting up lxc (1.1.4-0ubuntu1) ...
  Job for lxc-net.service failed because the control process exited with error 
code. See "systemctl status lxc-net.service" and "journalctl -xe" for details.
  invoke-rc.d: initscript lxc-net, action "start" failed.
  dpkg: error processing package lxc (--configure):
   subprocess installed post-installation script returned error exit status 1
  dpkg: dependency problems prevent configuration of lxc-templates:
   lxc-templates depends on lxc (>= 0.8.0~rc1-4ubuntu43); however:
    Package lxc is not configured yet.

  dpkg: error processing package lxc-templates (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of juju-local:
   juju-local depends on lxc (>= 1.0.0~alpha1-0ubuntu14); however:
    Package lxc is not configured yet.
   juju-local depends on lxc-templates; however:
    Package lxc-templates is not configured yet.

  dpkg: error processing package juju-local (--configure):
   dependency problems - leaving unconfigured
  Errors were encountered while processing:
   lxc
   lxc-templates
   juju-local
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  ubuntu@machine:~$

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1508577/+subscriptions

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

[Touch-packages] [Bug 1479305] Re: BQ E4.5 (r24): Gallery app is showing thumbnails of viedeos without any indication of content

[Pat McGowan]

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

** No longer affects: thumbnailer (Ubuntu)

** No longer affects: thumbnailer (Ubuntu RTM)

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

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

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

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

** Summary changed:

- BQ E4.5 (r24): Gallery app is showing thumbnails of viedeos without any 
indication of content
+ BQ E4.5 (r24): Gallery app is showing thumbnails of videos without any 
indication of content

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

Title:
  BQ E4.5 (r24): Gallery app is showing thumbnails of videos without any
  indication of content

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  New
Status in gallery-app package in Ubuntu:
  Confirmed
Status in gstreamer1.0 package in Ubuntu:
  Confirmed
Status in gallery-app package in Ubuntu RTM:
  New

Bug description:
  The Gallery-->Photos is showing for videos no indication about the
  content. It could present, for example, at least the date and time
  from the filename of the video. Without this it is impossible to pick-
  up the desired video. See attachment.

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

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

[Touch-packages] [Bug 1508592] [NEW] Build with multiarch support

[Robert Ancell]

Public bug reported:

Build with multiarch support

** Affects: evolution-data-server (Ubuntu)
 Importance: Medium
 Status: Triaged


** Tags: multiarch

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

Title:
  Build with multiarch support

Status in evolution-data-server package in Ubuntu:
  Triaged

Bug description:
  Build with multiarch support

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

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

[Touch-packages] [Bug 1447376] Re: obexd fails to stop

[Pat McGowan]

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

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

Title:
  obexd fails to stop

Status in Canonical System Image:
  Fix Released
Status in ubuntu-touch-session package in Ubuntu:
  Fix Released

Bug description:
  Current obexd job fails to stop/restart, as the upstart job is
  expecting daemon instead of fork.

  This affect the shutdown process.

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

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

[Touch-packages] [Bug 1508573] Re: X11 keeps booting in failsafe mode due to xorg.conf having the nvidia set as primary GPU.

[Omega-xis]

also see:
http://ubuntuforums.org/showthread.php?t=2297755

every reboot results in having the following contents in
/etc/X11/xorg.conf

Section "ServerLayout"
Identifier "layout"
Screen 0 "nvidia"
Inactive "intel"
EndSection

the intel section also displays "none" as acceleration method.

** Also affects: xserver-xorg-video-intel (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  X11 keeps booting in failsafe mode due to xorg.conf having the nvidia
  set as primary GPU.

Status in bumblebee package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  removing the nvidia-driver and /etc/X11/xorg.conf and manually
  launching lightdm from the command-line solves it.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: bumblebee 3.2.1-9
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Oct 21 20:56:04 2015
  InstallationDate: Installed on 2014-11-08 (347 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcEnviron:
   LANGUAGE=nl_NL
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  SourcePackage: bumblebee
  UpgradeStatus: Upgraded to wily on 2015-10-19 (2 days ago)
  mtime.conffile..etc.bumblebee.xorg.conf.nouveau: 2015-10-21T20:48:11.549384
  mtime.conffile..etc.bumblebee.xorg.conf.nvidia: 2015-10-21T20:48:51.188097

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

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

[Touch-packages] [Bug 1508573] [NEW] X11 keeps booting in failsafe mode due to xorg.conf having the nvidia set as primary GPU.

[Omega-xis]

Public bug reported:

removing the nvidia-driver and /etc/X11/xorg.conf and manually launching
lightdm from the command-line solves it.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: bumblebee 3.2.1-9
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
ApportVersion: 2.19.1-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Oct 21 20:56:04 2015
InstallationDate: Installed on 2014-11-08 (347 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
ProcEnviron:
 LANGUAGE=nl_NL
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
SourcePackage: bumblebee
UpgradeStatus: Upgraded to wily on 2015-10-19 (2 days ago)
mtime.conffile..etc.bumblebee.xorg.conf.nouveau: 2015-10-21T20:48:11.549384
mtime.conffile..etc.bumblebee.xorg.conf.nvidia: 2015-10-21T20:48:51.188097

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

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

** Affects: xserver-xorg-video-intel (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug wily

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

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

Title:
  X11 keeps booting in failsafe mode due to xorg.conf having the nvidia
  set as primary GPU.

Status in bumblebee package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  removing the nvidia-driver and /etc/X11/xorg.conf and manually
  launching lightdm from the command-line solves it.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: bumblebee 3.2.1-9
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Oct 21 20:56:04 2015
  InstallationDate: Installed on 2014-11-08 (347 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcEnviron:
   LANGUAGE=nl_NL
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  SourcePackage: bumblebee
  UpgradeStatus: Upgraded to wily on 2015-10-19 (2 days ago)
  mtime.conffile..etc.bumblebee.xorg.conf.nouveau: 2015-10-21T20:48:11.549384
  mtime.conffile..etc.bumblebee.xorg.conf.nvidia: 2015-10-21T20:48:51.188097

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

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