[Touch-packages] [Bug 1382595] Re: [TOPBLOCKER] /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service:indicator-network-service: pthread_mutex_lock.c:80: __pthread_mutex_lock: Asser

[Antti Kaijanmäki]

Looking at the stacktrace, the assertion error happens inside dbus-cpp
worker thread that has called core::dbus::Bus::run().

Some quick googling:
http://stackoverflow.com/questions/1105745/pthread-mutex-assertion-error

** Also affects: dbus-cpp
   Importance: Undecided
   Status: New

** Changed in: dbus-cpp
   Status: New => Confirmed

** Also affects: dbus-cpp (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: dbus-cpp (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Changed in: dbus-cpp (Ubuntu)
   Status: New => Confirmed

** Changed in: dbus-cpp (Ubuntu RTM)
   Status: New => Confirmed

** Changed in: dbus-cpp (Ubuntu)
   Importance: Undecided => Critical

** Changed in: dbus-cpp (Ubuntu RTM)
   Importance: Undecided => Critical

** Changed in: dbus-cpp (Ubuntu)
 Assignee: (unassigned) => Thomas Voß (thomas-voss)

** Changed in: dbus-cpp (Ubuntu RTM)
 Assignee: (unassigned) => Thomas Voß (thomas-voss)

** Changed in: indicator-network (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  [TOPBLOCKER] /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-
  network-service:indicator-network-service: pthread_mutex_lock.c:80:
  __pthread_mutex_lock: Assertion `mutex->__data.__owner == 0' failed.

Status in DBus C++:
  Confirmed
Status in “dbus-cpp” package in Ubuntu:
  Confirmed
Status in “indicator-network” package in Ubuntu:
  Invalid
Status in “dbus-cpp” package in Ubuntu RTM:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding indicator-network.  This problem was most recently seen with
  version 0.5.1+14.10.20141015-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/ecc14b5d54f3e0a0f1720cad0c623f81c8a16988
  contains more details.

  steps to reproduce: (need to trigger race condition)
  1. pull down network indicator
  2. toggle flight mode on and off quickly a few times
  3. click sim card 1 and 2
  4. toggle flight mode
  5. swipe up close indicators
  6. repeat steps 1-5 until crash occurs

  expected results:
  no crash happens

  actual results:
  Bluetooth indicator blinks (appear and disappear) in indicator bar at top of 
screen, and network indicator crashes. 

  additional info:
  eventually the bluetooth indicator appears stable in the indicators at the 
top of the screen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus-cpp/+bug/1382595/+subscriptions

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

[Touch-packages] [Bug 1384502] Re: fstab entry for nfs /home fails to mount on boot

[Steve Langasek]

Confirmed.  The issue here is that as an NFS mount not mounted under
/usr or /var, mountall implicitly treats this as 'nobootwait'.  It's
debatable whether this should be done, but the other issue is that
filesystems being marked 'nobootwait' doesn't just prevent them from
blocking the boot, it also prevents them from being waited for at all -
if they become available while mountall is running it will mount them,
but otherwise mountall will exit without caring that there are still
filesystems that could possibly come online later and need mounted.

This is definitely a bug in mountall.

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

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

Title:
  fstab entry for nfs /home fails to mount on boot

Status in “mountall” package in Ubuntu:
  Triaged

Bug description:
  i'm uncertain exactly when this issue started as we use cfengine
  (verifies all expected mounts in place, manually mounts those that are
  not).  from a note i have i believe it goes back as far as lucid.

  the symptom is that an /etc/fstab entry for an nfs-mounted /home is
  not mounted during the system boot. once the system is network-
  accessible, manually running `mount -tnfs -av` as root (or using
  cfengine or any number of other solutions) is sufficient.

  per lp#836533 i added "--verbose" to /etc/init/mountall.conf and will attach 
the resulting /var/log/upstart/mountall.log and /etc/network/interfaces. the 
smoking gun appears to be:
  mount.nfs: Failed to resolve server nfs-home: Temporary failure in name 
resolution

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: mountall 2.53
  ProcVersionSignature: Ubuntu 3.13.0-38.65.lp1383921-generic 3.13.11.8
  Uname: Linux 3.13.0-38.65-generic x86_64
  .run.mount.utab:
   
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  Date: Wed Oct 22 16:35:47 2014
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-38.65-generic 
root=/dev/md0 ro consoleblank=0 console=tty0 console=ttyS2,115200n8 nomdmonddf 
nomdmonisw bootdegraded=true
  SourcePackage: mountall
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1384394] Re: /etc/network/interfaces: "dns-nameservers" entries for bridge "br*" interfaces are ignored i.e. they are not listed in "/etc/resolv.conf" when invoking "ifup" comman

[Steve Langasek]

/etc/resolvconf/interface-order is only supposed to determine the order
in which interfaces are preferred as sources of DNS configuration, it
should certainly not cause the DNS servers for an interface to be
ignored completely.  Please attach your full /etc/network/interfaces, as
well as the contents of the /run/resolvconf directory (in particular,
the /run/resolvconf/interface subdirectory).

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

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

Title:
  /etc/network/interfaces: "dns-nameservers" entries for bridge "br*"
  interfaces are ignored i.e. they are not listed in "/etc/resolv.conf"
  when invoking "ifup" command

Status in “resolvconf” package in Ubuntu:
  Incomplete

Bug description:
  lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  apt-cache policy resolvconf
  resolvconf:
Installed: 1.69ubuntu1.1
Candidate: 1.69ubuntu1.1
Version table:
   *** 1.69ubuntu1.1 0
  500 http://ch.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.69ubuntu1 0
  500 http://ch.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  DESCRIPTION:
  network-manager: My "eth0" and "wlan0" cards are managed by the 
network-manager and this works fine.

  /etc/network/interfaces: My 2 bridges "br0" and "br1" are managed in 
"/etc/network/interfaces" as follows:
  ...
  iface br0 inet static
   address 192.168.10.1
   netmask 255.255.255.0
   dns-nameservers 192.168.10.2
   bridge_ports none
   bridge_stp off
   bridge_fd 0
   bridge_maxwait 0

  iface br1 inet static
   address 192.168.0.1
   netmask 255.255.255.0
   dns-nameservers 192.168.0.2
   bridge_ports none
   bridge_stp off
   bridge_fd 0
   bridge_maxwait 0
  ...

  When I now bring up the bridge interfaces using:
  sudo ifup br0 br1
  Then they show up fine in "ifconfig".
  BUT "dns-nameservers 192.168.10.2" and "dns-nameservers 192.168.0.2" DO NOT 
show up in "/etc/resolv.conf"

  WORKAROUND: Until this has been fixed the following workaround works fine for 
me:
  sudo vi /etc/resolvconf/interface-order
  #Add the following entry (this entry can be put on any line BUT it has to 
come before the last entry "*"):
  ...
  br*
  ...
  *

  PS: Based on the workaround in "/etc/resolvconf/interface-order" I
  think the issue is in package "resolvconf" otherwise I would have
  reported the error against the "ifupdown scripts".

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

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

[Touch-packages] [Bug 751939] Re: Wired-only machine has empty volcano icon

[Rolf Leggewie]

ping Barry

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

Title:
  Wired-only machine has empty volcano icon

Status in “network-manager” package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: network-manager

  I just upgraded my maverick desktop machine to natty.  This machine
  only has a wired connection, no wireless.  I'm used to seeing the
  up/down arrows for the nm icon in the menu bar, but now all I see is
  the empty volcano (or fan, or pie slice :) icon.  When I select Edit
  Connections, I do see just the Auto Ethernet wired connection I
  expect.

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

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

[Touch-packages] [Bug 913839] Re: tether over bluetooth - regression in precise

[Rolf Leggewie]

** Tags added: regression-release

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

Title:
  tether over bluetooth - regression in precise

Status in “network-manager” package in Ubuntu:
  Confirmed
Status in “network-manager” package in Fedora:
  Unknown

Bug description:
  I've had dial-up networking via bluetooth working between my CR-48 and
  Blackberry 9800 for several months.

  Recent Precise update (sometime around the last couple of weeks of
  2011) appear to have broken the ability to tether over bluetooth in
  this manner.  I have completely removed the bluetooth connection and
  re-paired the devices from scratch, but it does not work.

  Other bluetooth functionality appears to work fine.  i.e. I can send
  files from the laptop to the phone without issue.

  Here's what I see in syslog:

  Jan  9 09:02:28 chrombuntu NetworkManager[516]:  Activation 
(CC:55:AD:DF:60:A9) starting connection 'AT&T MEdia Net (phones)'
  Jan  9 09:02:28 chrombuntu NetworkManager[516]:  (CC:55:AD:DF:60:A9): 
device state change: disconnected -> prepare (reason 'none') [30 40 0]
  Jan  9 09:02:28 chrombuntu NetworkManager[516]:  Activation 
(CC:55:AD:DF:60:A9) Stage 1 of 5 (Device Prepare) scheduled...
  Jan  9 09:02:28 chrombuntu NetworkManager[516]:  Activation 
(CC:55:AD:DF:60:A9) Stage 1 of 5 (Device Prepare) started...
  Jan  9 09:02:28 chrombuntu NetworkManager[516]:  Activation 
(CC:55:AD:DF:60:A9) Stage 2 of 5 (Device Configure) scheduled...
  Jan  9 09:02:28 chrombuntu NetworkManager[516]:  Activation 
(CC:55:AD:DF:60:A9) Stage 1 of 5 (Device Prepare) complete.
  Jan  9 09:02:28 chrombuntu NetworkManager[516]:  Activation 
(CC:55:AD:DF:60:A9) Stage 2 of 5 (Device Configure) starting...
  Jan  9 09:02:28 chrombuntu NetworkManager[516]:  (CC:55:AD:DF:60:A9): 
device state change: prepare -> config (reason 'none') [40 50 0]
  Jan  9 09:02:28 chrombuntu NetworkManager[516]:  Activation 
(CC:55:AD:DF:60:A9) Stage 2 of 5 (Device Configure) complete.
  Jan  9 09:02:48 chrombuntu NetworkManager[516]:  Error connecting with 
bluez: Did not receive a reply. Possible causes include: the remote application 
did not send a reply, the message bus security policy blocked the reply, the 
reply timeout expired, or the network connection was broken.
  Jan  9 09:02:48 chrombuntu NetworkManager[516]:  (CC:55:AD:DF:60:A9): 
device state change: config -> failed (reason 'bluetooth-failed') [50 120 44]
  Jan  9 09:02:48 chrombuntu NetworkManager[516]:  Activation 
(CC:55:AD:DF:60:A9) failed.
  Jan  9 09:02:48 chrombuntu NetworkManager[516]:  (CC:55:AD:DF:60:A9): 
device state change: failed -> disconnected (reason 'none') [120 30 0]
  Jan  9 09:02:48 chrombuntu NetworkManager[516]:  (CC:55:AD:DF:60:A9): 
deactivating device (reason 'none') [0]
  Jan  9 09:02:48 chrombuntu NetworkManager[516]: nm_system_iface_flush_routes: 
assertion `ifindex > 0' failed
  Jan  9 09:02:48 chrombuntu NetworkManager[516]: 
nm_system_iface_flush_addresses: assertion `ifindex > 0' failed
  Jan  9 09:03:11 chrombuntu bluetoothd[1268]: Connection refused (111)

  dmesg is devoid of any errors during the attempt to connect.  The only
  messages I see related to the device is:

  [ 6567.470098] Bluetooth: TIOCGSERIAL is not supported

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: network-manager 0.9.2.0+git201112151936.6b31828-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-8.14-generic 3.2.0
  Uname: Linux 3.2.0-8-generic x86_64
  ApportVersion: 1.90-0ubuntu1
  Architecture: amd64
  Date: Mon Jan  9 09:09:39 2012
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64+mac (20110913)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.206  
metric 2
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile
   
   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0  
   CC:55:AD:DF:60:A9 bluetooth disconnected  
/org/freedesktop/NetworkManager/Devices/3
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.3.0connected   enabled   enabled 
enabledenabled enabled

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

--

[Touch-packages] [Bug 1165789] Re: Wifi indicator shows "disconnected" in between "connecting" and "connected" (raring regression)

[Rolf Leggewie]

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

** Tags added: trusty

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

Title:
  Wifi indicator shows "disconnected" in between "connecting" and
  "connected" (raring regression)

Status in “network-manager” package in Ubuntu:
  Confirmed

Bug description:
  In quantal, the network-manager indicator progressed straight from
  "connecting" (pulsing/rippling wifi symbol) to "connected" (static
  wifi signal level indicator) when successfully connected.

  In raring, it shows the "disconnected" (outlined empty lack of wifi
  symbol) symbol for a half-second or so between "connecting" and
  "connected", provoking a moment's concern of "What? My wifi connection
  failed?" until the user learns to tolerate this quirk.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: network-manager 0.9.8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic x86_64
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Sun Apr  7 16:45:16 2013
  EcryptfsInUse: Yes
  IpRoute:
   default via 192.168.42.129 dev usb0  proto static 
   169.254.0.0/16 dev usb0  scope link  metric 1000 
   192.168.42.0/24 dev usb0  proto kernel  scope link  src 192.168.42.195  
metric 1
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to raring on 2013-03-16 (21 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   usb0   802-3-ethernetconnected 
/org/freedesktop/NetworkManager/Devices/2  
   wlan0  802-11-wireless   unavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.0connected   enabled   enabled 
disabled   enabled disabled

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

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

[Touch-packages] [Bug 1384538] Re: bash-completion stopped working (regression)

[Rolf Leggewie]

** Tags added: regression-release

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

Title:
  bash-completion stopped working (regression)

Status in “network-manager” package in Ubuntu:
  New

Bug description:
  I'm quite sure that at least until precise "sudo service netwTAB"
  would complete to either "sudo service networking" or "sudo service
  network-manager".  The latter is no longer there in trusty. Please
  bring it back.

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

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

[Touch-packages] [Bug 1384327] Re: lxc-attach --clear-env results in a limited $PATH in the container

[Serge Hallyn]

Looks like the value actually comes straight from a #define in the glibc
source code.

As such, I think it would be pretty reasonable to change lxc to always
use its own path.

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

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

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

Title:
  lxc-attach --clear-env results in a limited $PATH in the container

Status in “lxc” package in Ubuntu:
  Triaged

Bug description:
  Here is the problem in more details:

   # Clearing the env
   $ printf 'echo $PATH\n' | sudo lxc-attach --clear-env -n p1
   /bin:/usr/bin

   # Keeping the env
   $ printf 'echo $PATH\n' | sudo lxc-attach --keep-env -n p1
   /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

  While keeping the env seems like a good workaround it cause other
  undesirable effects like preserving $HOME that doesn't (always) exist
  in the container.

  Additional information:

  $ apt-cache policy lxc
  lxc:
Installed: 1.0.6-0ubuntu0.1
Candidate: 1.0.6-0ubuntu0.1
Version table:
   *** 1.0.6-0ubuntu0.1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.0.5-0ubuntu0.1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
   1.0.3-0ubuntu3 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  Both host and container are:

  $ lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

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

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

[Touch-packages] [Bug 1384538] [NEW] bash-completion stopped working (regression)

[Rolf Leggewie]

Public bug reported:

I'm quite sure that at least until precise "sudo service netwTAB" would
complete to either "sudo service networking" or "sudo service network-
manager".  The latter is no longer there in trusty. Please bring it
back.

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


** Tags: trusty

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

Title:
  bash-completion stopped working (regression)

Status in “network-manager” package in Ubuntu:
  New

Bug description:
  I'm quite sure that at least until precise "sudo service netwTAB"
  would complete to either "sudo service networking" or "sudo service
  network-manager".  The latter is no longer there in trusty. Please
  bring it back.

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

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

[Touch-packages] [Bug 913839] Re: tether over bluetooth - regression in precise

[Rolf Leggewie]

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

** Tags added: saucy

** Also affects: network-manager (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=1054212
   Importance: Unknown
   Status: Unknown

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

Title:
  tether over bluetooth - regression in precise

Status in “network-manager” package in Ubuntu:
  Confirmed
Status in “network-manager” package in Fedora:
  Unknown

Bug description:
  I've had dial-up networking via bluetooth working between my CR-48 and
  Blackberry 9800 for several months.

  Recent Precise update (sometime around the last couple of weeks of
  2011) appear to have broken the ability to tether over bluetooth in
  this manner.  I have completely removed the bluetooth connection and
  re-paired the devices from scratch, but it does not work.

  Other bluetooth functionality appears to work fine.  i.e. I can send
  files from the laptop to the phone without issue.

  Here's what I see in syslog:

  Jan  9 09:02:28 chrombuntu NetworkManager[516]:  Activation 
(CC:55:AD:DF:60:A9) starting connection 'AT&T MEdia Net (phones)'
  Jan  9 09:02:28 chrombuntu NetworkManager[516]:  (CC:55:AD:DF:60:A9): 
device state change: disconnected -> prepare (reason 'none') [30 40 0]
  Jan  9 09:02:28 chrombuntu NetworkManager[516]:  Activation 
(CC:55:AD:DF:60:A9) Stage 1 of 5 (Device Prepare) scheduled...
  Jan  9 09:02:28 chrombuntu NetworkManager[516]:  Activation 
(CC:55:AD:DF:60:A9) Stage 1 of 5 (Device Prepare) started...
  Jan  9 09:02:28 chrombuntu NetworkManager[516]:  Activation 
(CC:55:AD:DF:60:A9) Stage 2 of 5 (Device Configure) scheduled...
  Jan  9 09:02:28 chrombuntu NetworkManager[516]:  Activation 
(CC:55:AD:DF:60:A9) Stage 1 of 5 (Device Prepare) complete.
  Jan  9 09:02:28 chrombuntu NetworkManager[516]:  Activation 
(CC:55:AD:DF:60:A9) Stage 2 of 5 (Device Configure) starting...
  Jan  9 09:02:28 chrombuntu NetworkManager[516]:  (CC:55:AD:DF:60:A9): 
device state change: prepare -> config (reason 'none') [40 50 0]
  Jan  9 09:02:28 chrombuntu NetworkManager[516]:  Activation 
(CC:55:AD:DF:60:A9) Stage 2 of 5 (Device Configure) complete.
  Jan  9 09:02:48 chrombuntu NetworkManager[516]:  Error connecting with 
bluez: Did not receive a reply. Possible causes include: the remote application 
did not send a reply, the message bus security policy blocked the reply, the 
reply timeout expired, or the network connection was broken.
  Jan  9 09:02:48 chrombuntu NetworkManager[516]:  (CC:55:AD:DF:60:A9): 
device state change: config -> failed (reason 'bluetooth-failed') [50 120 44]
  Jan  9 09:02:48 chrombuntu NetworkManager[516]:  Activation 
(CC:55:AD:DF:60:A9) failed.
  Jan  9 09:02:48 chrombuntu NetworkManager[516]:  (CC:55:AD:DF:60:A9): 
device state change: failed -> disconnected (reason 'none') [120 30 0]
  Jan  9 09:02:48 chrombuntu NetworkManager[516]:  (CC:55:AD:DF:60:A9): 
deactivating device (reason 'none') [0]
  Jan  9 09:02:48 chrombuntu NetworkManager[516]: nm_system_iface_flush_routes: 
assertion `ifindex > 0' failed
  Jan  9 09:02:48 chrombuntu NetworkManager[516]: 
nm_system_iface_flush_addresses: assertion `ifindex > 0' failed
  Jan  9 09:03:11 chrombuntu bluetoothd[1268]: Connection refused (111)

  dmesg is devoid of any errors during the attempt to connect.  The only
  messages I see related to the device is:

  [ 6567.470098] Bluetooth: TIOCGSERIAL is not supported

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: network-manager 0.9.2.0+git201112151936.6b31828-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-8.14-generic 3.2.0
  Uname: Linux 3.2.0-8-generic x86_64
  ApportVersion: 1.90-0ubuntu1
  Architecture: amd64
  Date: Mon Jan  9 09:09:39 2012
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64+mac (20110913)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.206  
metric 2
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile
   
   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0  
   CC:55:AD:DF:60:A9 bluetooth disconnected  
/org/freedesktop/NetworkManager/Devices/3
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.3.0connec

[Touch-packages] [Bug 1229256] Re: network-manager does not recognize bluetooth PAN interfaces (bnep0)

[Rolf Leggewie]

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

** This bug has been marked a duplicate of bug 913839
   tether over bluetooth - regression in precise

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

Title:
  network-manager does not recognize bluetooth PAN interfaces (bnep0)

Status in “network-manager” package in Ubuntu:
  Triaged

Bug description:
  When bluetooth network is created by bluez, it creates bnep0 network
  interface.

  That interface is ignored by Network Manager (no auto dhcp, not in the
  list, not in the creation options). Interfaces can be configurated
  manually (sudo dhclient bnep0), but NM ignores it completely.

  Steps to reproduce:

  1) Pair xubuntu with android device (in my case Samsung S3)
  2) Initiate network access (network access point) on that device

  Expected behavior:
  NM or silently initialize interface, or just show it as option to initialize 
network

  Actual behavior:
  complete ignorance.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: network-manager 0.9.8.0-0ubuntu20
  ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
  Uname: Linux 3.11.0-8-generic i686
  ApportVersion: 2.12.4-0ubuntu1
  Architecture: i386
  Date: Mon Sep 23 19:45:32 2013
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-07-19 (65 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1)
  IpRoute:
   default via 192.168.44.1 dev bnep0 
   192.168.44.0/24 dev bnep0  proto kernel  scope link  src 192.168.44.217
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to saucy on 2013-09-08 (15 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   disconnected  
/org/freedesktop/NetworkManager/Devices/1  
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.0disconnectedenabled   enabled 
enabledenabled enabled

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

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

[Touch-packages] [Bug 294190] Re: spews logs with "supplicant connection state change"

[Rolf Leggewie]

I believe this is fixed at least in trusty, isn't it?

** Changed in: network-manager (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  spews logs with "supplicant connection state change"

Status in NetworkManager:
  Confirmed
Status in Linux WPA/WPA2/IEEE 802.1X Supplicant:
  Won't Fix
Status in “network-manager” package in Ubuntu:
  Incomplete
Status in “wpasupplicant” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: network-manager

  NetworkManager completely clogs up all the system logs with messages
  like this:

  Nov  5 01:36:32 inspiron NetworkManager:   (eth1): supplicant 
connection state change: 7 -> 0
  Nov  5 01:36:32 inspiron NetworkManager:   (eth1): supplicant 
connection state change: 0 -> 2
  Nov  5 01:36:33 inspiron NetworkManager:   (eth1): supplicant 
connection state change: 2 -> 3
  Nov  5 01:36:33 inspiron NetworkManager:   (eth1): supplicant 
connection state change: 3 -> 4
  Nov  5 01:36:33 inspiron NetworkManager:   (eth1): supplicant 
connection state change: 4 -> 5
  Nov  5 01:36:33 inspiron NetworkManager:   (eth1): supplicant 
connection state change: 5 -> 6
  Nov  5 01:36:33 inspiron NetworkManager:   (eth1): supplicant 
connection state change: 6 -> 7
  Nov  5 01:38:32 inspiron NetworkManager:   (eth1): supplicant 
connection state change: 7 -> 0
  Nov  5 01:38:32 inspiron NetworkManager:   (eth1): supplicant 
connection state change: 0 -> 2
  Nov  5 01:38:33 inspiron NetworkManager:   (eth1): supplicant 
connection state change: 2 -> 3
  Nov  5 01:38:33 inspiron NetworkManager:   (eth1): supplicant 
connection state change: 3 -> 4
  Nov  5 01:38:33 inspiron NetworkManager:   (eth1): supplicant 
connection state change: 4 -> 5
  Nov  5 01:38:33 inspiron NetworkManager:   (eth1): supplicant 
connection state change: 5 -> 6
  Nov  5 01:38:33 inspiron NetworkManager:   (eth1): supplicant 
connection state change: 6 -> 7
  Nov  5 01:40:32 inspiron NetworkManager:   (eth1): supplicant 
connection state change: 7 -> 0
  Nov  5 01:40:32 inspiron NetworkManager:   (eth1): supplicant 
connection state change: 0 -> 2
  Nov  5 01:40:33 inspiron NetworkManager:   (eth1): supplicant 
connection state change: 2 -> 3
  Nov  5 01:40:33 inspiron NetworkManager:   (eth1): supplicant 
connection state change: 3 -> 4
  Nov  5 01:40:33 inspiron NetworkManager:   (eth1): supplicant 
connection state change: 4 -> 5
  Nov  5 01:40:33 inspiron NetworkManager:   (eth1): supplicant 
connection state change: 5 -> 6
  Nov  5 01:40:33 inspiron NetworkManager:   (eth1): supplicant 
connection state change: 6 -> 7
  Nov  5 01:42:35 inspiron NetworkManager:   (eth1): supplicant 
connection state change: 7 -> 0
  Nov  5 01:42:35 inspiron NetworkManager:   (eth1): supplicant 
connection state change: 0 -> 2
  Nov  5 01:42:36 inspiron NetworkManager:   (eth1): supplicant 
connection state change: 2 -> 3
  Nov  5 01:42:36 inspiron NetworkManager:   (eth1): supplicant 
connection state change: 3 -> 4
  Nov  5 01:42:36 inspiron NetworkManager:   (eth1): supplicant 
connection state change: 4 -> 5
  Nov  5 01:42:36 inspiron NetworkManager:   (eth1): supplicant 
connection state change: 5 -> 6
  Nov  5 01:42:36 inspiron NetworkManager:   (eth1): supplicant 
connection state change: 6 -> 7
  Nov  5 01:44:32 inspiron NetworkManager:   (eth1): supplicant 
connection state change: 7 -> 0
  Nov  5 01:44:32 inspiron NetworkManager:   (eth1): supplicant 
connection state change: 0 -> 2
  Nov  5 01:44:33 inspiron NetworkManager:   (eth1): supplicant 
connection state change: 2 -> 3
  Nov  5 01:44:33 inspiron NetworkManager:   (eth1): supplicant 
connection state change: 3 -> 4
  Nov  5 01:44:33 inspiron NetworkManager:   (eth1): supplicant 
connection state change: 4 -> 5
  Nov  5 01:44:33 inspiron NetworkManager:   (eth1): supplicant 
connection state change: 5 -> 6
  Nov  5 01:44:33 inspiron NetworkManager:   (eth1): supplicant 
connection state change: 6 -> 7
  Nov  5 01:46:32 inspiron NetworkManager:   (eth1): supplicant 
connection state change: 7 -> 0
  Nov  5 01:46:32 inspiron NetworkManager:   (eth1): supplicant 
connection state change: 0 -> 2
  Nov  5 01:46:33 inspiron NetworkManager:   (eth1): supplicant 
connection state change: 2 -> 3
  Nov  5 01:46:34 inspiron NetworkManager:   (eth1): supplicant 
connection state change: 3 -> 4
  Nov  5 01:46:34 inspiron NetworkManager:   (eth1): supplicant 
connection state change: 4 -> 5

  If this stuff really needs to be logged for some reason, can't it be
  directed to its own file?  It makes the logs really difficult to read
  and wastes disk space.

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

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

[Touch-packages] [Bug 1384522] [NEW] libOpenVG.so.1 missing in /usr/lib/*-linux-*/

[Sergio Benjamim]

Public bug reported:

Hi, it seems libOpenVG.so.1 is missing in  /usr/lib/*-linux-*/, there is
only the libOpenVG.so. I had trouble with this symlink:

dpkg-shlibdeps: error: couldn't find library libOpenVG.so.1 needed by 
debian/retroarch/usr/bin/retroarch (ELF format: 'elf32-littlearm-hfabi'; RPATH: 
'')
dpkg-shlibdeps: warning: package could avoid a useless dependency if 
debian/retroarch/usr/bin/retroarch was not linked against libEGL.so.1 (it uses 
none of the library's symbols)

I created the symlink for *.so.1, it worked for me.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: libopenvg1-mesa-dev 10.1.3-0ubuntu0.1
Uname: Linux 3.16.4-031604-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
Date: Thu Oct 23 00:23:12 2014
InstallationDate: Installed on 2014-05-26 (150 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: mesa (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug trusty

** Description changed:

- Hi, it seems libOpenVG.so.1 is missing in  /usr/lib/arm-linux-gnuabihf/,
- there is only the libOpenVG.so. I had trouble with this symlink:
+ Hi, it seems libOpenVG.so.1 is missing in  /usr/lib/*-linux-*/, there is
+ only the libOpenVG.so. I had trouble with this symlink:
  
  dpkg-shlibdeps: error: couldn't find library libOpenVG.so.1 needed by 
debian/retroarch/usr/bin/retroarch (ELF format: 'elf32-littlearm-hfabi'; RPATH: 
'')
- dpkg-shlibdeps: warning: package could avoid a useless dependency if 
debian/retroarch/usr/bin/retroarch was not linked against libEGL.so.1 (it uses 
none of the library's symbols) 
+ dpkg-shlibdeps: warning: package could avoid a useless dependency if 
debian/retroarch/usr/bin/retroarch was not linked against libEGL.so.1 (it uses 
none of the library's symbols)
  
  I created the symlink for *.so.1, it worked for me.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libopenvg1-mesa-dev 10.1.3-0ubuntu0.1
  Uname: Linux 3.16.4-031604-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  Date: Thu Oct 23 00:23:12 2014
  InstallationDate: Installed on 2014-05-26 (150 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  libOpenVG.so.1 missing in /usr/lib/*-linux-*/

Status in “mesa” package in Ubuntu:
  Confirmed

Bug description:
  Hi, it seems libOpenVG.so.1 is missing in  /usr/lib/*-linux-*/, there
  is only the libOpenVG.so. I had trouble with this symlink:

  dpkg-shlibdeps: error: couldn't find library libOpenVG.so.1 needed by 
debian/retroarch/usr/bin/retroarch (ELF format: 'elf32-littlearm-hfabi'; RPATH: 
'')
  dpkg-shlibdeps: warning: package could avoid a useless dependency if 
debian/retroarch/usr/bin/retroarch was not linked against libEGL.so.1 (it uses 
none of the library's symbols)

  I created the symlink for *.so.1, it worked for me.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libopenvg1-mesa-dev 10.1.3-0ubuntu0.1
  Uname: Linux 3.16.4-031604-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  Date: Thu Oct 23 00:23:12 2014
  InstallationDate: Installed on 2014-05-26 (150 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1384522] Re: libOpenVG.so.1 missing in /usr/lib/*-linux-*/

[Launchpad Bug Tracker]

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

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

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

Title:
  libOpenVG.so.1 missing in /usr/lib/*-linux-*/

Status in “mesa” package in Ubuntu:
  Confirmed

Bug description:
  Hi, it seems libOpenVG.so.1 is missing in  /usr/lib/*-linux-*/, there
  is only the libOpenVG.so. I had trouble with this symlink:

  dpkg-shlibdeps: error: couldn't find library libOpenVG.so.1 needed by 
debian/retroarch/usr/bin/retroarch (ELF format: 'elf32-littlearm-hfabi'; RPATH: 
'')
  dpkg-shlibdeps: warning: package could avoid a useless dependency if 
debian/retroarch/usr/bin/retroarch was not linked against libEGL.so.1 (it uses 
none of the library's symbols)

  I created the symlink for *.so.1, it worked for me.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libopenvg1-mesa-dev 10.1.3-0ubuntu0.1
  Uname: Linux 3.16.4-031604-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  Date: Thu Oct 23 00:23:12 2014
  InstallationDate: Installed on 2014-05-26 (150 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1377813] Re: tzdata SRU to 2014f because of law changes in Russia

[Launchpad Bug Tracker]

This bug was fixed in the package tzdata - 2014i-0ubuntu0.14.04

---
tzdata (2014i-0ubuntu0.14.04) trusty; urgency=critical

  * New upstream release with zone changes in 4 days for Belarus.
 -- Adam ConradWed, 22 Oct 2014 17:22:43 -0600

** Changed in: tzdata (Ubuntu Trusty)
   Status: Confirmed => Fix Released

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

Title:
  tzdata SRU to 2014f because of law changes in Russia

Status in “tzdata” package in Ubuntu:
  Fix Released
Status in “tzdata” source package in Lucid:
  Fix Released
Status in “tzdata” source package in Precise:
  Fix Released
Status in “tzdata” source package in Trusty:
  Fix Released
Status in “tzdata” package in Debian:
  Fix Released

Bug description:
  Tzdata in 12.04 (Precise) and 14.04 (Trusty) needs to be updated to
  version 2014f or newer.

  Timezone assignment in Russia has changed in 2014-07-01. The changes
  are published in Olson 2014f. Timezone changes will take effect in
  2014-10-26. Please release package updates before this date.

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

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

[Touch-packages] [Bug 1377813] Re: tzdata SRU to 2014f because of law changes in Russia

[Launchpad Bug Tracker]

This bug was fixed in the package tzdata - 2014i-0ubuntu0.14.04

---
tzdata (2014i-0ubuntu0.14.04) trusty; urgency=critical

  * New upstream release with zone changes in 4 days for Belarus.
 -- Adam ConradWed, 22 Oct 2014 17:22:43 -0600

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

Title:
  tzdata SRU to 2014f because of law changes in Russia

Status in “tzdata” package in Ubuntu:
  Fix Released
Status in “tzdata” source package in Lucid:
  Fix Released
Status in “tzdata” source package in Precise:
  Fix Released
Status in “tzdata” source package in Trusty:
  Fix Released
Status in “tzdata” package in Debian:
  Fix Released

Bug description:
  Tzdata in 12.04 (Precise) and 14.04 (Trusty) needs to be updated to
  version 2014f or newer.

  Timezone assignment in Russia has changed in 2014-07-01. The changes
  are published in Olson 2014f. Timezone changes will take effect in
  2014-10-26. Please release package updates before this date.

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

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

[Touch-packages] [Bug 1377813] Re: tzdata SRU to 2014f because of law changes in Russia

[Launchpad Bug Tracker]

This bug was fixed in the package tzdata - 2014i-0ubuntu0.10.04

---
tzdata (2014i-0ubuntu0.10.04) lucid; urgency=critical

  * New upstream release with zone changes in 4 days for Belarus.
 -- Adam ConradWed, 22 Oct 2014 17:22:43 -0600

** Changed in: tzdata (Ubuntu Precise)
   Status: Confirmed => Fix Released

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

Title:
  tzdata SRU to 2014f because of law changes in Russia

Status in “tzdata” package in Ubuntu:
  Fix Released
Status in “tzdata” source package in Lucid:
  Fix Released
Status in “tzdata” source package in Precise:
  Fix Released
Status in “tzdata” source package in Trusty:
  Fix Released
Status in “tzdata” package in Debian:
  Fix Released

Bug description:
  Tzdata in 12.04 (Precise) and 14.04 (Trusty) needs to be updated to
  version 2014f or newer.

  Timezone assignment in Russia has changed in 2014-07-01. The changes
  are published in Olson 2014f. Timezone changes will take effect in
  2014-10-26. Please release package updates before this date.

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

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

[Touch-packages] [Bug 1377813] Re: tzdata SRU to 2014f because of law changes in Russia

[Launchpad Bug Tracker]

This bug was fixed in the package tzdata - 2014i-0ubuntu0.12.04

---
tzdata (2014i-0ubuntu0.12.04) precise; urgency=critical

  * New upstream release with zone changes in 4 days for Belarus.
 -- Adam ConradWed, 22 Oct 2014 17:22:43 -0600

** Changed in: tzdata (Ubuntu Trusty)
   Status: Confirmed => Fix Released

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

Title:
  tzdata SRU to 2014f because of law changes in Russia

Status in “tzdata” package in Ubuntu:
  Fix Released
Status in “tzdata” source package in Lucid:
  Fix Released
Status in “tzdata” source package in Precise:
  Fix Released
Status in “tzdata” source package in Trusty:
  Fix Released
Status in “tzdata” package in Debian:
  Fix Released

Bug description:
  Tzdata in 12.04 (Precise) and 14.04 (Trusty) needs to be updated to
  version 2014f or newer.

  Timezone assignment in Russia has changed in 2014-07-01. The changes
  are published in Olson 2014f. Timezone changes will take effect in
  2014-10-26. Please release package updates before this date.

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

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

[Touch-packages] [Bug 1377813] Re: tzdata SRU to 2014f because of law changes in Russia

[Launchpad Bug Tracker]

This bug was fixed in the package tzdata - 2014i-0ubuntu0.12.04

---
tzdata (2014i-0ubuntu0.12.04) precise; urgency=critical

  * New upstream release with zone changes in 4 days for Belarus.
 -- Adam ConradWed, 22 Oct 2014 17:22:43 -0600

** Changed in: tzdata (Ubuntu Precise)
   Status: Confirmed => Fix Released

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

Title:
  tzdata SRU to 2014f because of law changes in Russia

Status in “tzdata” package in Ubuntu:
  Fix Released
Status in “tzdata” source package in Lucid:
  Fix Released
Status in “tzdata” source package in Precise:
  Fix Released
Status in “tzdata” source package in Trusty:
  Fix Released
Status in “tzdata” package in Debian:
  Fix Released

Bug description:
  Tzdata in 12.04 (Precise) and 14.04 (Trusty) needs to be updated to
  version 2014f or newer.

  Timezone assignment in Russia has changed in 2014-07-01. The changes
  are published in Olson 2014f. Timezone changes will take effect in
  2014-10-26. Please release package updates before this date.

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

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

[Touch-packages] [Bug 1377813] Re: tzdata SRU to 2014f because of law changes in Russia

[Launchpad Bug Tracker]

This bug was fixed in the package tzdata - 2014i-0ubuntu0.10.04

---
tzdata (2014i-0ubuntu0.10.04) lucid; urgency=critical

  * New upstream release with zone changes in 4 days for Belarus.
 -- Adam ConradWed, 22 Oct 2014 17:22:43 -0600

** Changed in: tzdata (Ubuntu Lucid)
   Status: Confirmed => Fix Released

** Changed in: tzdata (Ubuntu Lucid)
   Status: Confirmed => Fix Released

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

Title:
  tzdata SRU to 2014f because of law changes in Russia

Status in “tzdata” package in Ubuntu:
  Fix Released
Status in “tzdata” source package in Lucid:
  Fix Released
Status in “tzdata” source package in Precise:
  Fix Released
Status in “tzdata” source package in Trusty:
  Fix Released
Status in “tzdata” package in Debian:
  Fix Released

Bug description:
  Tzdata in 12.04 (Precise) and 14.04 (Trusty) needs to be updated to
  version 2014f or newer.

  Timezone assignment in Russia has changed in 2014-07-01. The changes
  are published in Olson 2014f. Timezone changes will take effect in
  2014-10-26. Please release package updates before this date.

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

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

[Touch-packages] [Bug 1341685] Re: When unconstrained, udm sometimes downloads files to wrong location

[Loïc Minier]

Testsuite now passes on above branch; would like to get a build of it.

** Changed in: ubuntu-download-manager
 Assignee: (unassigned) => Loïc Minier (lool)

** Changed in: ubuntu-download-manager
   Status: New => In Progress

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

** Changed in: ubuntu-download-manager (Ubuntu)
   Importance: Undecided => Critical

** Changed in: ubuntu-download-manager (Ubuntu)
   Status: New => In Progress

** Also affects: ubuntu-download-manager (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-download-manager (Ubuntu RTM)
   Importance: Undecided => Critical

** Changed in: ubuntu-download-manager (Ubuntu RTM)
   Status: New => In Progress

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

Title:
  When unconstrained, udm sometimes downloads files to wrong location

Status in Ubuntu Download Manager:
  In Progress
Status in “ubuntu-download-manager” package in Ubuntu:
  In Progress
Status in “ubuntu-download-manager” package in Ubuntu RTM:
  In Progress

Bug description:
  I'm working on making the s-i tests more robust and I've run into an
  odd situation, where udm sometimes stores its downloaded files using
  an incorrect path, and not the one that s-i (which is unconstrained)
  requests.  This only appears to happen when the full s-i test suite is
  run.  When run in isolation, the test succeeds.

  Here's a log of the createDownloadGroup call I'm making:

  createDownloadGroup:
  [Record(url='https://localhost:8943/gpg/blacklist.tar.xz',
  destination='/tmp/tmpe7mo8qm9/ubuntu/cache/keyring.tar.xz',
  checksum=''),
  Record(url='https://localhost:8943/gpg/blacklist.tar.xz.asc',
  destination='/tmp/tmpe7mo8qm9/ubuntu/cache/keyring.tar.xz.asc',
  checksum='')]

  url is the source url, destination is the local path to save the file
  in.  This call produces incorrect destination paths in the 'finished'
  signal:

  FINISHED: dbus.Array([dbus.String('/home/barry/.local/share/ubuntu-
  download-manager//usr/lib/telepathy/mission-
  control-5/Downloads/blacklist (20).tar.xz'),
  dbus.String('/home/barry/.local/share/ubuntu-download-
  manager//usr/lib/telepathy/mission-control-5/Downloads/blacklist
  (20).tar.xz.asc')], signature=dbus.Signature('s'))

  Notice the very strange directory udm chooses which is definitely not
  the path requested, and in fact doesn't exist.  This matches the
  observed behavior that after a succesful group download completion
  (i.e. no errors occur), I assert that the requested destination path
  exists, and in the failing test it does not.

  I suspect some state is not getting reset in udm.

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

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

[Touch-packages] [Bug 1383060] Re: Window controls became invisible

[Vadim Peretokin]

This happened again.

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

Title:
  Window controls became invisible

Status in “unity” package in Ubuntu:
  New

Bug description:
  The window controls suddenly became invisible. They still acted as
  they should.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.2+14.04.20140714-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.5
  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: Mon Oct 20 09:49:16 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:198f]
   Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] [1002:6601] 
(rev ff) (prog-if ff)
  InstallationDate: Installed on 2014-06-26 (115 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP ZBook 14
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-37-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/29/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.11
  dmi.board.name: 198F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.54
  dmi.chassis.asset.tag: CNU424B3ZZ
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.11:bd04/29/2014:svnHewlett-Packard:pnHPZBook14:pvrA3009DD10303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.54:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ZBook 14
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.54-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.2-0intel1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.2-0intel1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
  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: Thu Oct 16 07:30:35 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors: Screen 1 deleted because of no matching config section.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2.1
  xserver.video_driver: fglrx

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

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

[Touch-packages] [Bug 787451] Re: pcscd spams to syslog and kern.log after enabling smartcard reader in VMWare Workstation

[pkrishn6]

As you previously mentioned, Killing pcscd or using the virtual smart
card is definitely an option but neither is hollistic since a user might
want to share one of the physical smart cards between the guest and host
but might want to passthrough another smart card reader.

We rely on  pcscd for our virtual smart card backend.

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

Title:
  pcscd spams to syslog and kern.log after enabling smartcard reader in
  VMWare Workstation

Status in “pcsc-lite” package in Ubuntu:
  Confirmed

Bug description:
  Info:
  Ubuntu 11.04 amd64

  pcscd:
    Installed: 1.7.0-2ubuntu2
    Candidate: 1.7.0-2ubuntu2
    Version table:
   *** 1.7.0-2ubuntu2 0
  500 http://ru.archive.ubuntu.com/ubuntu/ natty/universe amd64 Packages
  100 /var/lib/dpkg/status

  libccid:
    Installed: 1.4.2-2
    Candidate: 1.4.2-2
    Version table:
   *** 1.4.2-2 0
  500 http://ru.archive.ubuntu.com/ubuntu/ natty/universe amd64 Packages
  100 /var/lib/dpkg/status

  libpcsclite1:
    Installed: 1.7.0-2ubuntu2
    Candidate: 1.7.0-2ubuntu2
    Version table:
   *** 1.7.0-2ubuntu2 0
  500 http://ru.archive.ubuntu.com/ubuntu/ natty/main amd64 Packages
  100 /var/lib/dpkg/status

   pcscd --version
  pcsc-lite version 1.7.0.
  Copyright (C) 1999-2002 by David Corcoran .
  Copyright (C) 2001-2010 by Ludovic Rousseau .
  Copyright (C) 2003-2004 by Damien Sauveron .
  Report bugs to .
  Enabled features: Linux x86_64-pc-linux-gnu serial usb libudev 
usbdropdir=/usr/lib/pcsc/drivers ipcdir=/var/run/pcscd 
configdir=/etc/reader.conf.d

  smart card is JCOP 31.

  VMWare Workstation version is 7.1.4 build-385536

  Steps for bug reproducing:
  1) Launch VMWare OS. In my case this is Windows 7 but I guess it doesn't 
matter.

  2) Connect SmartCard reader to VMWare OS.  Reader's model is SCM
  SCR3110. This is supported by libccid 1.4.2.

  3) At this moment, syslog is spamed by pcscd process. The following strings 
can be found in syslog:
  May 24 13:10:02 computer-name pcscd: ccid_usb.c:618:WriteUSB() write failed 
(8/2): -1 Device or resource busy
  May 24 13:10:02 computer-name pcscd: ifdwrapper.c:346:IFDStatusICC() Card not 
transacted: 612
  May 24 13:10:02 computer-name pcscd: 
eventhandler.c:303:EHStatusHandlerThread() Error communicating to: SCM SCR 3310 
[CCID Interface] (21120818206778) 00 00
  May 24 13:10:02 computer-name pcscd: ccid_usb.c:618:WriteUSB() write failed 
(8/2): -1 Device or resource busy
  May 24 13:10:02 computer-name pcscd: ifdwrapper.c:346:IFDStatusICC() Card not 
transacted: 612
  May 24 13:10:02 computer-name pcscd: 
eventhandler.c:303:EHStatusHandlerThread() Error communicating to: SCM SCR 3310 
[CCID Interface] (21120818206778) 00 00
  May 24 13:10:02 computer-name pcscd: ccid_usb.c:618:WriteUSB() write failed 
(8/2): -1 Device or resource busy
  May 24 13:10:02 computer-name pcscd: ifdwrapper.c:346:IFDStatusICC() Card not 
transacted: 612
  May 24 13:10:02 computer-name pcscd: 
eventhandler.c:303:EHStatusHandlerThread() Error communicating to: SCM SCR 3310 
[CCID Interface] (21120818206778) 00 00
  May 24 13:10:02 computer-name pcscd: ccid_usb.c:618:WriteUSB() write failed 
(8/2): -1 Device or resource busy
  May 24 13:10:02 computer-name pcscd: ifdwrapper.c:346:IFDStatusICC() Card not 
transacted: 612
  May 24 13:10:02 computer-name pcscd: 
eventhandler.c:303:EHStatusHandlerThread() Error communicating to: SCM SCR 3310 
[CCID Interface] (21120818206778) 00 00
  May 24 13:10:02 computer-name pcscd: ccid_usb.c:618:WriteUSB() write failed 
(8/2): -1 Device or resource busy
  

  4) The log size rapidly increases. It takes several minutes to reach
  20 Gb.

  5) After disconnecting smartcard reader, the following string can be found in 
syslog:
  ...
  May 24 13:12:41 computer-name kernel: [75680.065939] usb 8-2: usbfs: process 
2956 (pcscd) did not claim interface 0 before use
  May 24 13:12:41 computer-name kernel: [75680.065996] usb 8-2: usbfs: process 
2956 (pcscd) did not claim interface 0 before use
  May 24 13:12:41 computer-name kernel: [75680.066000] usb 8-2: usbfs: process 
2956 (pcscd) did not claim interface 0 before use
  May 24 13:12:41 computer-name kernel: [75680.066057] usb 8-2: usbfs: process 
2956 (pcscd) did not claim interface 0 before use
  May 24 13:12:41 computer-name kernel: [75680.066211] usb 8-2: usbfs: process 
2956 (pcscd) did not claim interface 0 before use

  Also this messages are written in kern.log

  6) The problem is solved by restarting of computer.

  I cannot attach syslog and kern.log due to huge size.

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

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

[Touch-packages] [Bug 787451] Re: pcscd spams to syslog and kern.log after enabling smartcard reader in VMWare Workstation

[pkrishn6]

Ludovic Rousseau,

Hello. I am a VMware USb developer and I am trying to deal with this
issue. What we when an user wants to connect a physical device to the
guest aka passthrogh is to knock off the current driver loaded for the
device and claim the interfaces. While this approach works if a kernel
driver is loaded against the device, it does not if pcscd/libccid is the
driver.

I do not get an error from usbfs but my demsg buffer is filled with vmx-
tried to use interface 0 before claiming.

Any suggestions how else we could address this problem?

I do not have examples of knocking off other user space drivers working
well., since other USB device (mass storage, audio, video) use kernel
drivers.

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

Title:
  pcscd spams to syslog and kern.log after enabling smartcard reader in
  VMWare Workstation

Status in “pcsc-lite” package in Ubuntu:
  Confirmed

Bug description:
  Info:
  Ubuntu 11.04 amd64

  pcscd:
    Installed: 1.7.0-2ubuntu2
    Candidate: 1.7.0-2ubuntu2
    Version table:
   *** 1.7.0-2ubuntu2 0
  500 http://ru.archive.ubuntu.com/ubuntu/ natty/universe amd64 Packages
  100 /var/lib/dpkg/status

  libccid:
    Installed: 1.4.2-2
    Candidate: 1.4.2-2
    Version table:
   *** 1.4.2-2 0
  500 http://ru.archive.ubuntu.com/ubuntu/ natty/universe amd64 Packages
  100 /var/lib/dpkg/status

  libpcsclite1:
    Installed: 1.7.0-2ubuntu2
    Candidate: 1.7.0-2ubuntu2
    Version table:
   *** 1.7.0-2ubuntu2 0
  500 http://ru.archive.ubuntu.com/ubuntu/ natty/main amd64 Packages
  100 /var/lib/dpkg/status

   pcscd --version
  pcsc-lite version 1.7.0.
  Copyright (C) 1999-2002 by David Corcoran .
  Copyright (C) 2001-2010 by Ludovic Rousseau .
  Copyright (C) 2003-2004 by Damien Sauveron .
  Report bugs to .
  Enabled features: Linux x86_64-pc-linux-gnu serial usb libudev 
usbdropdir=/usr/lib/pcsc/drivers ipcdir=/var/run/pcscd 
configdir=/etc/reader.conf.d

  smart card is JCOP 31.

  VMWare Workstation version is 7.1.4 build-385536

  Steps for bug reproducing:
  1) Launch VMWare OS. In my case this is Windows 7 but I guess it doesn't 
matter.

  2) Connect SmartCard reader to VMWare OS.  Reader's model is SCM
  SCR3110. This is supported by libccid 1.4.2.

  3) At this moment, syslog is spamed by pcscd process. The following strings 
can be found in syslog:
  May 24 13:10:02 computer-name pcscd: ccid_usb.c:618:WriteUSB() write failed 
(8/2): -1 Device or resource busy
  May 24 13:10:02 computer-name pcscd: ifdwrapper.c:346:IFDStatusICC() Card not 
transacted: 612
  May 24 13:10:02 computer-name pcscd: 
eventhandler.c:303:EHStatusHandlerThread() Error communicating to: SCM SCR 3310 
[CCID Interface] (21120818206778) 00 00
  May 24 13:10:02 computer-name pcscd: ccid_usb.c:618:WriteUSB() write failed 
(8/2): -1 Device or resource busy
  May 24 13:10:02 computer-name pcscd: ifdwrapper.c:346:IFDStatusICC() Card not 
transacted: 612
  May 24 13:10:02 computer-name pcscd: 
eventhandler.c:303:EHStatusHandlerThread() Error communicating to: SCM SCR 3310 
[CCID Interface] (21120818206778) 00 00
  May 24 13:10:02 computer-name pcscd: ccid_usb.c:618:WriteUSB() write failed 
(8/2): -1 Device or resource busy
  May 24 13:10:02 computer-name pcscd: ifdwrapper.c:346:IFDStatusICC() Card not 
transacted: 612
  May 24 13:10:02 computer-name pcscd: 
eventhandler.c:303:EHStatusHandlerThread() Error communicating to: SCM SCR 3310 
[CCID Interface] (21120818206778) 00 00
  May 24 13:10:02 computer-name pcscd: ccid_usb.c:618:WriteUSB() write failed 
(8/2): -1 Device or resource busy
  May 24 13:10:02 computer-name pcscd: ifdwrapper.c:346:IFDStatusICC() Card not 
transacted: 612
  May 24 13:10:02 computer-name pcscd: 
eventhandler.c:303:EHStatusHandlerThread() Error communicating to: SCM SCR 3310 
[CCID Interface] (21120818206778) 00 00
  May 24 13:10:02 computer-name pcscd: ccid_usb.c:618:WriteUSB() write failed 
(8/2): -1 Device or resource busy
  

  4) The log size rapidly increases. It takes several minutes to reach
  20 Gb.

  5) After disconnecting smartcard reader, the following string can be found in 
syslog:
  ...
  May 24 13:12:41 computer-name kernel: [75680.065939] usb 8-2: usbfs: process 
2956 (pcscd) did not claim interface 0 before use
  May 24 13:12:41 computer-name kernel: [75680.065996] usb 8-2: usbfs: process 
2956 (pcscd) did not claim interface 0 before use
  May 24 13:12:41 computer-name kernel: [75680.066000] usb 8-2: usbfs: process 
2956 (pcscd) did not claim interface 0 before use
  May 24 13:12:41 computer-name kernel: [75680.066057] usb 8-2: usbfs: process 
2956 (pcscd) did not claim interface 0 before use
  May 24 13:12:41 computer-name kernel: [75680.066211] usb 8-2: usbfs: process 
2956 (pcscd) did not claim interface 0 before use

  Also this messages are written in ke

[Touch-packages] [Bug 1384416] Re: coreutils 'info command' broken

[Bug Watch Updater]

** Changed in: coreutils
   Status: Unknown => Confirmed

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

Title:
  coreutils 'info command' broken

Status in The Gnu Core Utilities:
  Confirmed
Status in “coreutils” package in Ubuntu:
  Triaged

Bug description:
  Try the following on Ubuntu (or one of its flavors) and tell me what
  you see:

  $ info coreutils 'cat invocation'

  Should give you the *detailed* cat manual. However,  you will in fact
  land on "2.14 'coreutils' Multi-call binary" in the documentation. Now
  idea yet how to fix this.

  Great job. Seems the bug they reported on Debian mailing list on 9/11
  (2014)

  https://www.mail-archive.com/debian-bugs-
  d...@lists.debian.org/msg1256146.html

  ... has now made its way into the Ubuntu version of coreutils as well.

  By the way,  isn't that a great comment again??

  "though downstream 8.23 could be tweaked to avoid this issue."

  Cool. They've broken something that worked perfectly _for years_ and
  all the user gets is "yeah, 8.23 'could be tweaked'". If only he had
  said _how_ to tweak it!! But apparently the commenter was way too lazy
  to write one more line.

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

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

[Touch-packages] [Bug 1383994] Re: OpenVPN connections with supplied server certificate don't use it by default

[Mike]

** Description changed:

- I am on Xubuntu 14.04 with the most recent version of network-manager
- (up-to-date with apt-get).
+ I am on Xubuntu 14.04 with network-manager 0.9.8.8 (the most recent
+ version of network-manager, using apt-get).
  
  I added a TCP OpenVPN connection from a config file with a server
  certificate file specified. Today, when looking through my syslog, I
  found the following:
  
    Oct 21 11:20:38 xubuntu-MacAir NetworkManager[14273]:  VPN connection 
'USA-New York-TCP' (Connect) reply received.
    Oct 21 11:20:38 xubuntu-MacAir nm-openvpn[30726]: OpenVPN 2.3.2 
x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [eurephia] [MH] 
[IPv6] built on Feb  4 2014
    Oct 21 11:20:38 xubuntu-MacAir nm-openvpn[30726]: WARNING: No server 
certificate verification method has been enabled.  See 
http://openvpn.net/howto.html#mitm for more info.
  
  The certificate was listed in the main tabs of the network-manager's VPN
  config window, confirming that network-manager recognized its presence
  in the config file. Upon entering the "Advanced" window, I found that
  network-manager was not even attempting to use the certificate. I simply
  checked the relevant box, and everything now seems to be working fine.
  
  I feel that this is a bug, especially because the user is not notified
  of the warning. I'm reasonably experienced with manual configs, but I
  wrongly assumed that adding a server certificate was sufficient to have
  it actually used. There must be many users that don't know what a syslog
  is, and many more that made the same false assumption I did and never
  ventured into their logs to observe OpenVPN.
  
  I suggest that the user get an explicit warning through network-manager
  in this case, or that the server certificate be used by default if
  supplied by the user.

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

Title:
  OpenVPN connections with supplied server certificate don't use it by
  default

Status in “network-manager” package in Ubuntu:
  New

Bug description:
  I am on Xubuntu 14.04 with network-manager 0.9.8.8 (the most recent
  version of network-manager, using apt-get).

  I added a TCP OpenVPN connection from a config file with a server
  certificate file specified. Today, when looking through my syslog, I
  found the following:

    Oct 21 11:20:38 xubuntu-MacAir NetworkManager[14273]:  VPN connection 
'USA-New York-TCP' (Connect) reply received.
    Oct 21 11:20:38 xubuntu-MacAir nm-openvpn[30726]: OpenVPN 2.3.2 
x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [eurephia] [MH] 
[IPv6] built on Feb  4 2014
    Oct 21 11:20:38 xubuntu-MacAir nm-openvpn[30726]: WARNING: No server 
certificate verification method has been enabled.  See 
http://openvpn.net/howto.html#mitm for more info.

  The certificate was listed in the main tabs of the network-manager's
  VPN config window, confirming that network-manager recognized its
  presence in the config file. Upon entering the "Advanced" window, I
  found that network-manager was not even attempting to use the
  certificate. I simply checked the relevant box, and everything now
  seems to be working fine.

  I feel that this is a bug, especially because the user is not notified
  of the warning. I'm reasonably experienced with manual configs, but I
  wrongly assumed that adding a server certificate was sufficient to
  have it actually used. There must be many users that don't know what a
  syslog is, and many more that made the same false assumption I did and
  never ventured into their logs to observe OpenVPN.

  I suggest that the user get an explicit warning through network-
  manager in this case, or that the server certificate be used by
  default if supplied by the user.

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

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

[Touch-packages] [Bug 1384502] Re: fstab entry for nfs /home fails to mount on boot

[andrew bezella]

`mountall --verbose` log w/ip addr in fstab

** Attachment added: "mountall.log.ipaddr"
   
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1384502/+attachment/4242077/+files/mountall.log.ipaddr

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

Title:
  fstab entry for nfs /home fails to mount on boot

Status in “mountall” package in Ubuntu:
  New

Bug description:
  i'm uncertain exactly when this issue started as we use cfengine
  (verifies all expected mounts in place, manually mounts those that are
  not).  from a note i have i believe it goes back as far as lucid.

  the symptom is that an /etc/fstab entry for an nfs-mounted /home is
  not mounted during the system boot. once the system is network-
  accessible, manually running `mount -tnfs -av` as root (or using
  cfengine or any number of other solutions) is sufficient.

  per lp#836533 i added "--verbose" to /etc/init/mountall.conf and will attach 
the resulting /var/log/upstart/mountall.log and /etc/network/interfaces. the 
smoking gun appears to be:
  mount.nfs: Failed to resolve server nfs-home: Temporary failure in name 
resolution

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: mountall 2.53
  ProcVersionSignature: Ubuntu 3.13.0-38.65.lp1383921-generic 3.13.11.8
  Uname: Linux 3.13.0-38.65-generic x86_64
  .run.mount.utab:
   
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  Date: Wed Oct 22 16:35:47 2014
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-38.65-generic 
root=/dev/md0 ro consoleblank=0 console=tty0 console=ttyS2,115200n8 nomdmonddf 
nomdmonisw bootdegraded=true
  SourcePackage: mountall
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1384502] Re: fstab entry for nfs /home fails to mount on boot

[andrew bezella]

** Attachment added: ".var.log.upstart.mountall.log"
   
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1384502/+attachment/4242076/+files/.var.log.upstart.mountall.log

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

Title:
  fstab entry for nfs /home fails to mount on boot

Status in “mountall” package in Ubuntu:
  New

Bug description:
  i'm uncertain exactly when this issue started as we use cfengine
  (verifies all expected mounts in place, manually mounts those that are
  not).  from a note i have i believe it goes back as far as lucid.

  the symptom is that an /etc/fstab entry for an nfs-mounted /home is
  not mounted during the system boot. once the system is network-
  accessible, manually running `mount -tnfs -av` as root (or using
  cfengine or any number of other solutions) is sufficient.

  per lp#836533 i added "--verbose" to /etc/init/mountall.conf and will attach 
the resulting /var/log/upstart/mountall.log and /etc/network/interfaces. the 
smoking gun appears to be:
  mount.nfs: Failed to resolve server nfs-home: Temporary failure in name 
resolution

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: mountall 2.53
  ProcVersionSignature: Ubuntu 3.13.0-38.65.lp1383921-generic 3.13.11.8
  Uname: Linux 3.13.0-38.65-generic x86_64
  .run.mount.utab:
   
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  Date: Wed Oct 22 16:35:47 2014
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-38.65-generic 
root=/dev/md0 ro consoleblank=0 console=tty0 console=ttyS2,115200n8 nomdmonddf 
nomdmonisw bootdegraded=true
  SourcePackage: mountall
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1384502] Re: fstab entry for nfs /home fails to mount on boot

[andrew bezella]

** Attachment added: ".etc.network.interfaces"
   
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1384502/+attachment/4242075/+files/.etc.network.interfaces

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

Title:
  fstab entry for nfs /home fails to mount on boot

Status in “mountall” package in Ubuntu:
  New

Bug description:
  i'm uncertain exactly when this issue started as we use cfengine
  (verifies all expected mounts in place, manually mounts those that are
  not).  from a note i have i believe it goes back as far as lucid.

  the symptom is that an /etc/fstab entry for an nfs-mounted /home is
  not mounted during the system boot. once the system is network-
  accessible, manually running `mount -tnfs -av` as root (or using
  cfengine or any number of other solutions) is sufficient.

  per lp#836533 i added "--verbose" to /etc/init/mountall.conf and will attach 
the resulting /var/log/upstart/mountall.log and /etc/network/interfaces. the 
smoking gun appears to be:
  mount.nfs: Failed to resolve server nfs-home: Temporary failure in name 
resolution

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: mountall 2.53
  ProcVersionSignature: Ubuntu 3.13.0-38.65.lp1383921-generic 3.13.11.8
  Uname: Linux 3.13.0-38.65-generic x86_64
  .run.mount.utab:
   
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  Date: Wed Oct 22 16:35:47 2014
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-38.65-generic 
root=/dev/md0 ro consoleblank=0 console=tty0 console=ttyS2,115200n8 nomdmonddf 
nomdmonisw bootdegraded=true
  SourcePackage: mountall
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1384502] Re: fstab entry for nfs /home fails to mount on boot

[andrew bezella]

i also attempted a boot w/the nfs server's ip address instead of
hostname (although technically i guess "nfs-home" is an alias).  no
change, /home was still not mounted automatically on boot by mountall.

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

Title:
  fstab entry for nfs /home fails to mount on boot

Status in “mountall” package in Ubuntu:
  New

Bug description:
  i'm uncertain exactly when this issue started as we use cfengine
  (verifies all expected mounts in place, manually mounts those that are
  not).  from a note i have i believe it goes back as far as lucid.

  the symptom is that an /etc/fstab entry for an nfs-mounted /home is
  not mounted during the system boot. once the system is network-
  accessible, manually running `mount -tnfs -av` as root (or using
  cfengine or any number of other solutions) is sufficient.

  per lp#836533 i added "--verbose" to /etc/init/mountall.conf and will attach 
the resulting /var/log/upstart/mountall.log and /etc/network/interfaces. the 
smoking gun appears to be:
  mount.nfs: Failed to resolve server nfs-home: Temporary failure in name 
resolution

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: mountall 2.53
  ProcVersionSignature: Ubuntu 3.13.0-38.65.lp1383921-generic 3.13.11.8
  Uname: Linux 3.13.0-38.65-generic x86_64
  .run.mount.utab:
   
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  Date: Wed Oct 22 16:35:47 2014
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-38.65-generic 
root=/dev/md0 ro consoleblank=0 console=tty0 console=ttyS2,115200n8 nomdmonddf 
nomdmonisw bootdegraded=true
  SourcePackage: mountall
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1384502] [NEW] fstab entry for nfs /home fails to mount on boot

[andrew bezella]

Public bug reported:

i'm uncertain exactly when this issue started as we use cfengine
(verifies all expected mounts in place, manually mounts those that are
not).  from a note i have i believe it goes back as far as lucid.

the symptom is that an /etc/fstab entry for an nfs-mounted /home is not
mounted during the system boot. once the system is network-accessible,
manually running `mount -tnfs -av` as root (or using cfengine or any
number of other solutions) is sufficient.

per lp#836533 i added "--verbose" to /etc/init/mountall.conf and will attach 
the resulting /var/log/upstart/mountall.log and /etc/network/interfaces. the 
smoking gun appears to be:
mount.nfs: Failed to resolve server nfs-home: Temporary failure in name 
resolution

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: mountall 2.53
ProcVersionSignature: Ubuntu 3.13.0-38.65.lp1383921-generic 3.13.11.8
Uname: Linux 3.13.0-38.65-generic x86_64
.run.mount.utab:
 
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
Date: Wed Oct 22 16:35:47 2014
ProcEnviron:
 TERM=rxvt-unicode-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/usr/bin/zsh
ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-38.65-generic root=/dev/md0 
ro consoleblank=0 console=tty0 console=ttyS2,115200n8 nomdmonddf nomdmonisw 
bootdegraded=true
SourcePackage: mountall
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  fstab entry for nfs /home fails to mount on boot

Status in “mountall” package in Ubuntu:
  New

Bug description:
  i'm uncertain exactly when this issue started as we use cfengine
  (verifies all expected mounts in place, manually mounts those that are
  not).  from a note i have i believe it goes back as far as lucid.

  the symptom is that an /etc/fstab entry for an nfs-mounted /home is
  not mounted during the system boot. once the system is network-
  accessible, manually running `mount -tnfs -av` as root (or using
  cfengine or any number of other solutions) is sufficient.

  per lp#836533 i added "--verbose" to /etc/init/mountall.conf and will attach 
the resulting /var/log/upstart/mountall.log and /etc/network/interfaces. the 
smoking gun appears to be:
  mount.nfs: Failed to resolve server nfs-home: Temporary failure in name 
resolution

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: mountall 2.53
  ProcVersionSignature: Ubuntu 3.13.0-38.65.lp1383921-generic 3.13.11.8
  Uname: Linux 3.13.0-38.65-generic x86_64
  .run.mount.utab:
   
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  Date: Wed Oct 22 16:35:47 2014
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-38.65-generic 
root=/dev/md0 ro consoleblank=0 console=tty0 console=ttyS2,115200n8 nomdmonddf 
nomdmonisw bootdegraded=true
  SourcePackage: mountall
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1371834] Re: Chrome causes segfault in i965_dri.so

[Tito]

I can confirm this very annoying bug with i915 driver (on Lenovo x220).

It creates all sorts of graphical difficulties in Chromium (no vsync, no
interpolation of fullscreen videos, and of course no WebGL)

 LIBGL_DRI3_DISABLE=1 is a good fix.

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

Title:
  Chrome causes segfault in i965_dri.so

Status in Chromium Browser:
  Unknown
Status in “mesa” package in Ubuntu:
  Confirmed
Status in Debian GNU/Linux:
  New

Bug description:
  Running chrome 38.0.2125.66-1 on Ubuntu 14.10, on Lenovo X230

  When I start a new instance of chrome, it cannot enable WebGL. I have
  reported that bug separately to chrome at
  https://code.google.com/p/chromium/issues/detail?id=416207

  I suspect the cause of the bug is in mesa, as dmesg contains evidence
  of a segfault:

  [31979.398090] chrome[24013]: segfault at 20 ip 7fbbd5ca5d83 sp 
7fffd7669ab0 error 4 in i965_dri.so[7fbbd59c4000+50a000]
  [31979.585606] chrome[24104]: segfault at 20 ip 7f7550c26d83 sp 
7fff970b4630 error 4 in i965_dri.so[7f7550945000+50a000]
  [31979.737378] chrome[24117]: segfault at 20 ip 7ffd06e45d83 sp 
7fffc989f440 error 4 in i965_dri.so[7ffd06b64000+50a000]

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: libgl1-mesa-dri 10.2.6-1ubuntu3
  ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2
  Uname: Linux 3.16.0-16-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Sep 20 11:17:41 2014
  DistUpgraded: 2014-09-02 14:59:08,481 DEBUG failed to SystemUnLock() (E:Not 
locked)
  DistroCodename: utopic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21fa]
  MachineType: LENOVO 23301B9
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-16-generic 
root=/dev/mapper/hostname--vg-root ro splash quiet crashkernel=384M-:128M 
crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: Upgraded to utopic on 2014-09-02 (17 days ago)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 23301B9
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn23301B9:pvrThinkPadX230:rvnLENOVO:rn23301B9:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 23301B9
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.6-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.6-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Fri Sep 19 15:45:16 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4204 
   vendor AUO
  xserver.version: 2:1.16.0-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1371834/+subscriptions

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

[Touch-packages] [Bug 1384503] [NEW] rsync fails on large files with compression

[Joe Harrington]

Public bug reported:

Copying large (>10GB) files with rsync -z (compression) leads to a long
hang and eventual error after transferring part of the file.  The error
is consistent.  The file copies at normal speed until it reaches its
maximum size (1.4 GB out of 20 GB for one, 6.9 GB out of 29 GB for
another).  Then nothing happens for a while (many minutes).  Finally,
there is an error:

[]
jh/.VirtualBox/win7/win7.vbox
jh/.VirtualBox/win7/win7.vbox-prev
jh/.VirtualBox/win7/win7.vdi
rsync: [sender] write error: Broken pipe (32)
rsync error: error in rsync protocol data stream (code 12) at io.c(837) 
[sender=3.1.0]

In this case, 6.9 GB of 29 GB transferred.  Without -z, it works.

See the following upstream report, with a comment at the end from the
rsync maintainer:

https://bugzilla.samba.org/show_bug.cgi?id=10372

According to this report, version 3.1.0 (included in 14.04) uses a
different compression package from prior versions.  Prior versions did
not have this problem for me using the same command on the same systems.
Both hosts ran Ubuntu 11.10 at the time, and all run 14.04 now, in each
case with all updates applied, Intel hardware.  Network connection
between them is gigabit ethernet through one switch.  A shell ssh
between them in a terminal works and stays up during the failure, so it
is not a network issue.  There are no relevant entries in syslog on
either machine.  There is sufficient capacity on the receiving disk.
All filesystems are ext4.

rsync command:

/usr/bin/rsync -aHSxvz --delete --stats --exclude=lost+found
--exclude=.gvfs --exclude=/nonlaptop /home/
backup.host.edu:/bu/host/home/

(yes, I changed the machine names)

Current release (both hosts):

Description:Ubuntu 14.04.1 LTS
Release:14.04

Current package (both hosts):

rsync:
  Installed: 3.1.0-2ubuntu0.1
  Candidate: 3.1.0-2ubuntu0.1
  Version table:
 *** 3.1.0-2ubuntu0.1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
100 /var/lib/dpkg/status
 3.1.0-2 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

Thanks,

--jh--

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

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

Title:
  rsync fails on large files with compression

Status in “rsync” package in Ubuntu:
  New

Bug description:
  Copying large (>10GB) files with rsync -z (compression) leads to a
  long hang and eventual error after transferring part of the file.  The
  error is consistent.  The file copies at normal speed until it reaches
  its maximum size (1.4 GB out of 20 GB for one, 6.9 GB out of 29 GB for
  another).  Then nothing happens for a while (many minutes).  Finally,
  there is an error:

  []
  jh/.VirtualBox/win7/win7.vbox
  jh/.VirtualBox/win7/win7.vbox-prev
  jh/.VirtualBox/win7/win7.vdi
  rsync: [sender] write error: Broken pipe (32)
  rsync error: error in rsync protocol data stream (code 12) at io.c(837) 
[sender=3.1.0]

  In this case, 6.9 GB of 29 GB transferred.  Without -z, it works.

  See the following upstream report, with a comment at the end from the
  rsync maintainer:

  https://bugzilla.samba.org/show_bug.cgi?id=10372

  According to this report, version 3.1.0 (included in 14.04) uses a
  different compression package from prior versions.  Prior versions did
  not have this problem for me using the same command on the same
  systems. Both hosts ran Ubuntu 11.10 at the time, and all run 14.04
  now, in each case with all updates applied, Intel hardware.  Network
  connection between them is gigabit ethernet through one switch.  A
  shell ssh between them in a terminal works and stays up during the
  failure, so it is not a network issue.  There are no relevant entries
  in syslog on either machine.  There is sufficient capacity on the
  receiving disk.  All filesystems are ext4.

  rsync command:

  /usr/bin/rsync -aHSxvz --delete --stats --exclude=lost+found
  --exclude=.gvfs --exclude=/nonlaptop /home/
  backup.host.edu:/bu/host/home/

  (yes, I changed the machine names)

  Current release (both hosts):

  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  Current package (both hosts):

  rsync:
Installed: 3.1.0-2ubuntu0.1
Candidate: 3.1.0-2ubuntu0.1
Version table:
   *** 3.1.0-2ubuntu0.1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.1.0-2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  Thanks,

  --jh--

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

-- 
Mailin

[Touch-packages] [Bug 1384374] Re: Dash pauses/stutters during scope switching left/right

[Michał Sawicz]

This happens especially on boot, when moving between scopes causes other
scopes to load their content. Creation of the delegates seems to cause
the UI thread to block.

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

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

Title:
  Dash pauses/stutters during scope switching left/right

Status in “unity8” package in Ubuntu:
  Triaged

Bug description:
  Dash pauses/stutters during scope switching left/right.

  Watching the log:   tail -f ~/.cache/upstart/unity8-dash.log

  I can see error messages flood out whenever the dash pauses/stutters
  during left/right swipes:

  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property "height"

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

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

[Touch-packages] [Bug 1378805] Re: denial for creating /run/user/32011/scopes/leaf-net/

[Marcus Tomlinson]

** Branch linked: lp:unity-scopes-api/staging

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

Title:
  denial for creating /run/user/32011/scopes/leaf-net/

Status in “unity-scopes-api” package in Ubuntu:
  Fix Committed

Bug description:
  I feel like this bug is known and I thought there was a bug for this,
  but I can't seem to find it now so filing a new one

  Most scopes are seeing:
  apparmor="DENIED" operation="mkdir" 
profile="com.ubuntu.scopes.youtube_youtube_1.0.13" 
name="/run/user/32011/scopes/leaf-net/" pid=NNN comm="scoperunner" 
requested_mask="c" denied_mask="c" fsuid=32011 ouid=32011

  Scopes aren't allowed to create /run/user/32011/scopes/leaf-net/ (they
  are allowed to create their own scopes directory under it). This was
  mentioned in https://bugs.launchpad.net/unity-scopes-
  api/+bug/1356409/comments/3 and it was mentioned that this branch may
  fix it: https://code.launchpad.net/~michihenning/unity-scopes-api
  /test-before-mkdir/+merge/231110. However, the problem seems to be
  that nothing is creating that directory at all before the scopes try
  to create it for themselves. Pete said in the above comment "I think
  the runtime should probably not be trying to create this while inside
  confinement, as it will always fail." -- that is precisely the
  problem. Something unconfined outside of the scopes themselves needs
  to create it.

  Marking rtm14 and Critical-- it is causing a lot of noise in the logs
  and presumably scopes aren't able to function correctly. Please adjust
  as needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1378805/+subscriptions

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

[Touch-packages] [Bug 1376416] Re: apparmor denial for yelp

[Marcus Tomlinson]

** Branch linked: lp:unity-scopes-api/staging

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

Title:
  apparmor denial for yelp

Status in “unity-scopes-api” package in Ubuntu:
  Fix Committed

Bug description:
  In a recent test run, the following denial was observed:
  Oct  1 18:13:05 ubuntu-phablet kernel: [  130.968843] 
(3)[6618:com.ubuntu.yelp]type=1400 audit(1412187185.260:127): apparmor="DENIED" 
operation="mkdir" profile="com.ubuntu.yelp_yelp_1.0.26" 
name="/home/phablet/.local/share/unity-scopes/com.ubuntu.yelp_yelp/" pid=6618 
comm="com.ubuntu.yelp" requested_mask="c" denied_mask="c" fsuid=32011 ouid=32011

  Yelp is using the wrong directory. It is using:
  @{HOME}/.local/share/unity-scopes/@{APP_PKGNAME}_@{APP_APPNAME}

  but apparmor policy says to use:
  @{HOME}/.local/share/unity-scopes/leaf-net/@{APP_PKGNAME}

  Note: this is a different bug than the one dealing with
  XDG_RUNTIME_DIR paths, where we do use @{APP_APPNAME}.

  Adding rtm14 tag with High priority since this seems to affect scopes
  in the store. Please readjust as necessary.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1376416/+subscriptions

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

[Touch-packages] [Bug 1361221] Re: Manage Dash does not notice when the phone comes online

[Marcus Tomlinson]

** Branch linked: lp:unity-scopes-api/staging

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

Title:
  Manage Dash does not notice when the phone comes online

Status in “unity-scope-scopes” package in Ubuntu:
  Invalid
Status in “unity-scopes-api” package in Ubuntu:
  In Progress
Status in “unity-scopes-shell” package in Ubuntu:
  In Progress

Bug description:
  Steps:
  1. Start the phone with no Internet (i.e. no wireless or 2g/3g/4g)
  2. From the Dash, swipe from the bottom to get to Manage Dash
  3. Click "All"
  4. Note there are no internet based scopes available (which makes sense since 
you are not online)
  5. Click Done to go back to the dash
  6. Use the network indicator to get online
  7. After getting online, go back to Manage Dash

  Observed:
  The online scopes are still hidden

  Expected:
  After getting online you can see the online scopes

  Note that after a reboot and being online, the online scopes are
  visible

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-scopes/+bug/1361221/+subscriptions

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

[Touch-packages] [Bug 1356699] Re: Replace "InvalidateResults" dbus-send with "list updated" pub/sub mechanism

[Marcus Tomlinson]

** Branch linked: lp:unity-scopes-api/staging

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

Title:
  Replace "InvalidateResults" dbus-send with "list updated" pub/sub
  mechanism

Status in “unity-scopes-api” package in Ubuntu:
  In Progress
Status in “unity-scopes-shell” package in Ubuntu:
  In Progress

Bug description:
  The dbus "InvalidateResults" message was intended to be a temporary
  solution until we implemented a proper "list updated" pub/sub
  mechanism. Now that we have one, we should replace the dbus-send call
  in SSRegistryObject with publisher_->send_message() as done in
  RegistryObject.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1356699/+subscriptions

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

[Touch-packages] [Bug 1326086] Re: Make window menu always visible

[Launchpad Bug Tracker]

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

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

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

Title:
  Make window menu always visible

Status in Unity:
  New
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  Please make the window menu at the top of the screen always visible
  (instead of auto-hide).

  This would allow for quicker workflow: Instead of having to move the
  cursor to the top and then search for the desired menu (e.g. "File" or
  "Edit"), you could directly head for the desired menu. Furthermore it
  would make Ubuntu/Unity easier to use for new users.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140416-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  CasperVersion: 1.340
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Jun  3 17:16:38 2014
  LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1384419] Re: com.canonical.UnityGreeter.HideGreeter defeats password requirement

[Michael Terry]

You can only call that DBus method if you are unconfined and inside the
user session already.  So I don't *think* this is an issue.  But Seth,
please correct me if I'm wrong.

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

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Seth Arnold (seth-arnold)

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

Title:
  com.canonical.UnityGreeter.HideGreeter defeats password requirement

Status in “unity8” package in Ubuntu:
  Incomplete

Bug description:
  I have enabled developer mode in my phone(s). I'm required to have a
  password to enable developer mode. However, it's still possible to
  call com.canonical.UnityGreeter.HideGreete via adb to unlock without
  the password. This to me seems to defeat the purpose of the
  requirement of the password.

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

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

[Touch-packages] [Bug 1384416] Re: coreutils 'info command' broken

[A. Eibach]

OK, this one-liner has to do the trick for me, until this is fixed
downstream:

#!/bin/bash
[[ $1 == "" ]] || info Coreutils "$1 invocation"

Wish this could be made an alias, but this is impossible since the
variable is _inside_ instead of at EOL

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

Title:
  coreutils 'info command' broken

Status in The Gnu Core Utilities:
  Unknown
Status in “coreutils” package in Ubuntu:
  Triaged

Bug description:
  Try the following on Ubuntu (or one of its flavors) and tell me what
  you see:

  $ info coreutils 'cat invocation'

  Should give you the *detailed* cat manual. However,  you will in fact
  land on "2.14 'coreutils' Multi-call binary" in the documentation. Now
  idea yet how to fix this.

  Great job. Seems the bug they reported on Debian mailing list on 9/11
  (2014)

  https://www.mail-archive.com/debian-bugs-
  d...@lists.debian.org/msg1256146.html

  ... has now made its way into the Ubuntu version of coreutils as well.

  By the way,  isn't that a great comment again??

  "though downstream 8.23 could be tweaked to avoid this issue."

  Cool. They've broken something that worked perfectly _for years_ and
  all the user gets is "yeah, 8.23 'could be tweaked'". If only he had
  said _how_ to tweak it!! But apparently the commenter was way too lazy
  to write one more line.

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

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

[Touch-packages] [Bug 1379152] Re: Needs building dependency on libmtdev-dev (or making QPlatformSupport public)

[Timo Jyrinki]

I don't think this B) option has any impact other than the 80kB library
appearing on rootfs and the need to add the build dependency in affected
packages. This is already done in the Qt 5.3.2 landing PPA.

The mtdev is only used if evdev input driver is in use, ie. this can
improve multi touch on desktop but does not affect the phone.

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

Title:
  Needs building dependency on libmtdev-dev (or making QPlatformSupport
  public)

Status in Application menu for Qt5:
  New
Status in Qt integration with the Mir display server:
  New
Status in QT Ubuntu:
  New
Status in “appmenu-qt5” package in Ubuntu:
  New
Status in “maliit-framework” package in Ubuntu:
  New
Status in “qtmir” package in Ubuntu:
  In Progress
Status in “qtubuntu” package in Ubuntu:
  New
Status in Debian GNU/Linux:
  Won't Fix
Status in “qtmir” package in Ubuntu RTM:
  In Progress

Bug description:
  Because of packaging changes in Qt Base in Qt 5.3.2, packages using
  qplatformsupport from private headers will need to add an additional
  dependency to compile against it.

  From Debian bug report:
  ---
  This comes from QPlatformSupport stuff which creates a static library that 
needs this linking.

  It also happens that QPlatformSupport is private stuff, so there is really no 
way to solve this but either stop using private stuff or helping upstream to 
make QPlatformSupport public (which would be really helpful). This will in turn 
mean that it will become a dynamic lib and this bug can be fixed.
  ---

  So:
  A) someone works in qtbase upstream to make the QPlatformSupport public, or
  B) workaround with adding libmtdev-dev build dependencies

  This bug refers more to the B) option to get Qt 5.3.2 packages move
  forward.

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1379152/+subscriptions

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

[Touch-packages] [Bug 1383357] Re: enabling flight mode shows airplane + 2g icon

[Alexander Sack]

used ota-1 tag assuming that its just UI problem. If thats not case,
please drop that tag again.

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

Title:
  enabling flight mode shows airplane + 2g icon

Status in “indicator-network” package in Ubuntu:
  Confirmed
Status in “network-manager” package in Ubuntu:
  New

Bug description:
  I see this when I toggle the indicator in the indicator-network.logs

  void core::dbus::Property::handle_changed(const
  core::dbus::types::Variant&) [with PropertyType =
  org::freedesktop::URfkill::Interface::Killswitch::Property::State]:
  org.freedesktop.DBus.Error.UnknownMethod: Method "Get" with signature
  "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist

  There is nothing crashing according to /var/crash

  
  Modem seems to be offline:
  phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-modems 
  [ /ril_1 ]
  Features = 
  Manufacturer = Fake Manufacturer
  Lockdown = 0
  Powered = 1
  Online = 0
  Interfaces = org.ofono.CallVolume org.ofono.VoiceCallManager 
org.ofono.NetworkTime 
  Serial = 354142060406982
  Type = hardware
  Emergency = 0
  Revision = MOLY.WR8.W1315.MD.WG.MP.V37.P5, 2014/05/15 11:49
  Model = Fake Modem Model
  [ org.ofono.CallVolume ]
  SpeakerVolume = 0
  Muted = 0
  MicrophoneVolume = 0
  [ org.ofono.VoiceCallManager ]
  EmergencyNumbers = 08 000 999 110 112 911 118 119 
  [ org.ofono.NetworkTime ]

  [ /ril_0 ]
  Features = 
  Manufacturer = Fake Manufacturer
  Lockdown = 0
  Powered = 1
  Online = 0
  Interfaces = org.ofono.CallVolume org.ofono.VoiceCallManager 
org.ofono.NetworkTime 
  Serial = 354142060126986
  Type = hardware
  Emergency = 0
  Revision = MOLY.WR8.W1315.MD.WG.MP.V37.P5, 2014/05/15 11:49
  Model = Fake Modem Model
  [ org.ofono.CallVolume ]
  SpeakerVolume = 0
  Muted = 0
  MicrophoneVolume = 0
  [ org.ofono.VoiceCallManager ]
  EmergencyNumbers = 112 911 
  [ org.ofono.NetworkTime ]

  
  phablet@ubuntu-phablet:~$ /usr/share/urfkill/scripts/flight-mode 
  flight-mode is: 1

  phablet@ubuntu-phablet:~$ /usr/share/urfkill/scripts/enumerate 
  /org/freedesktop/URfkill/devices/0
  Printing props for unspecialized device: /org/freedesktop/URfkill/devices/0
  Printing props for Kernel device: /org/freedesktop/URfkill/devices/0
  type: 2
  hard: 0
  index: 0
  urftype: org.freedesktop.URfkill.Device.Kernel
  name: hci0
  platform: 0
  soft: 1

  /org/freedesktop/URfkill/devices/200
  Printing props for unspecialized device: /org/freedesktop/URfkill/devices/200
  Printing props for Hybris device: /org/freedesktop/URfkill/devices/200
  type: 1
  index: 200
  urftype: org.freedesktop.URfkill.Device.Hybris
  name: hybris_wifi
  platform: 0
  soft: 1

  /org/freedesktop/URfkill/devices/100
  Printing props for unspecialized device: /org/freedesktop/URfkill/devices/100
  Printing props for Ofono device: /org/freedesktop/URfkill/devices/100
  type: 5
  index: 100
  urftype: org.freedesktop.URfkill.Device.Ofono
  name: Fake Manufacturer Fake Modem Model
  platform: 0
  soft: 1

  /org/freedesktop/URfkill/devices/101
  Printing props for unspecialized device: /org/freedesktop/URfkill/devices/101
  Printing props for Ofono device: /org/freedesktop/URfkill/devices/101
  type: 5
  index: 101
  urftype: org.freedesktop.URfkill.Device.Ofono
  name: Fake Manufacturer Fake Modem Model
  platform: 0
  soft: 1

  
  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 117
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2014-10-19 08:18:48
  version version: 117
  version ubuntu: 20141019
  version device: 20141015-32e0f27
  version custom: 1413412663

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

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

[Touch-packages] [Bug 1383357] Re: enabling flight mode shows airplane + 2g icon

[Alexander Sack]

tvoss asked to have this also tracked on network-manager...

** Also affects: network-manager (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: ota-1

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

Title:
  enabling flight mode shows airplane + 2g icon

Status in “indicator-network” package in Ubuntu:
  Confirmed
Status in “network-manager” package in Ubuntu:
  New

Bug description:
  I see this when I toggle the indicator in the indicator-network.logs

  void core::dbus::Property::handle_changed(const
  core::dbus::types::Variant&) [with PropertyType =
  org::freedesktop::URfkill::Interface::Killswitch::Property::State]:
  org.freedesktop.DBus.Error.UnknownMethod: Method "Get" with signature
  "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist

  There is nothing crashing according to /var/crash

  
  Modem seems to be offline:
  phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-modems 
  [ /ril_1 ]
  Features = 
  Manufacturer = Fake Manufacturer
  Lockdown = 0
  Powered = 1
  Online = 0
  Interfaces = org.ofono.CallVolume org.ofono.VoiceCallManager 
org.ofono.NetworkTime 
  Serial = 354142060406982
  Type = hardware
  Emergency = 0
  Revision = MOLY.WR8.W1315.MD.WG.MP.V37.P5, 2014/05/15 11:49
  Model = Fake Modem Model
  [ org.ofono.CallVolume ]
  SpeakerVolume = 0
  Muted = 0
  MicrophoneVolume = 0
  [ org.ofono.VoiceCallManager ]
  EmergencyNumbers = 08 000 999 110 112 911 118 119 
  [ org.ofono.NetworkTime ]

  [ /ril_0 ]
  Features = 
  Manufacturer = Fake Manufacturer
  Lockdown = 0
  Powered = 1
  Online = 0
  Interfaces = org.ofono.CallVolume org.ofono.VoiceCallManager 
org.ofono.NetworkTime 
  Serial = 354142060126986
  Type = hardware
  Emergency = 0
  Revision = MOLY.WR8.W1315.MD.WG.MP.V37.P5, 2014/05/15 11:49
  Model = Fake Modem Model
  [ org.ofono.CallVolume ]
  SpeakerVolume = 0
  Muted = 0
  MicrophoneVolume = 0
  [ org.ofono.VoiceCallManager ]
  EmergencyNumbers = 112 911 
  [ org.ofono.NetworkTime ]

  
  phablet@ubuntu-phablet:~$ /usr/share/urfkill/scripts/flight-mode 
  flight-mode is: 1

  phablet@ubuntu-phablet:~$ /usr/share/urfkill/scripts/enumerate 
  /org/freedesktop/URfkill/devices/0
  Printing props for unspecialized device: /org/freedesktop/URfkill/devices/0
  Printing props for Kernel device: /org/freedesktop/URfkill/devices/0
  type: 2
  hard: 0
  index: 0
  urftype: org.freedesktop.URfkill.Device.Kernel
  name: hci0
  platform: 0
  soft: 1

  /org/freedesktop/URfkill/devices/200
  Printing props for unspecialized device: /org/freedesktop/URfkill/devices/200
  Printing props for Hybris device: /org/freedesktop/URfkill/devices/200
  type: 1
  index: 200
  urftype: org.freedesktop.URfkill.Device.Hybris
  name: hybris_wifi
  platform: 0
  soft: 1

  /org/freedesktop/URfkill/devices/100
  Printing props for unspecialized device: /org/freedesktop/URfkill/devices/100
  Printing props for Ofono device: /org/freedesktop/URfkill/devices/100
  type: 5
  index: 100
  urftype: org.freedesktop.URfkill.Device.Ofono
  name: Fake Manufacturer Fake Modem Model
  platform: 0
  soft: 1

  /org/freedesktop/URfkill/devices/101
  Printing props for unspecialized device: /org/freedesktop/URfkill/devices/101
  Printing props for Ofono device: /org/freedesktop/URfkill/devices/101
  type: 5
  index: 101
  urftype: org.freedesktop.URfkill.Device.Ofono
  name: Fake Manufacturer Fake Modem Model
  platform: 0
  soft: 1

  
  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 117
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2014-10-19 08:18:48
  version version: 117
  version ubuntu: 20141019
  version device: 20141015-32e0f27
  version custom: 1413412663

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

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

[Touch-packages] [Bug 1383479] Re: Remove autopilot from touch images

[Olli Ries]

** Changed in: autopilot (Ubuntu RTM)
   Importance: Critical => High

** Changed in: dbus-property-service (Ubuntu)
   Importance: Critical => High

** Changed in: dbus-property-service (Ubuntu RTM)
   Importance: Critical => High

** Changed in: ubuntu-touch-meta (Ubuntu RTM)
   Importance: Critical => High

** Changed in: ubuntu-touch-meta (Ubuntu)
   Importance: Critical => High

** Changed in: autopilot (Ubuntu)
   Importance: Critical => High

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

Title:
  Remove autopilot from touch images

Status in “autopilot” package in Ubuntu:
  Confirmed
Status in “dbus-property-service” package in Ubuntu:
  Confirmed
Status in “ubuntu-touch-meta” package in Ubuntu:
  Confirmed
Status in “autopilot” package in Ubuntu RTM:
  Confirmed
Status in “dbus-property-service” package in Ubuntu RTM:
  Confirmed
Status in “ubuntu-touch-meta” package in Ubuntu RTM:
  Confirmed

Bug description:
  Autopilot should be removed from the image. We intend to ship a
  consumer image, testing and debugging packages such as autopilot
  should not be needed.

  The ramfications affect app developers and CI who depend and assume
  autopilot exists on the image. To fix this, CI will migrate to adt-
  run. In the interim, autopilot will be added as a dependency so the
  current CI setup continues to run properly.

  phablet-test-run will also migrate to a wrapper for adt-run so users
  who have not already switched will have a seamless experience.

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

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

[Touch-packages] [Bug 1383724] Re: In the welcome wizard enable location but not here services and in here maps app you get no location

[Alexander Sack]

we have other bugs track that normal GPS doesn't work. once those are
fixed this won't be that critical.

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

Title:
  In the welcome wizard enable location but not here services and in
  here maps app you get no location

Status in “location-service” package in Ubuntu:
  New

Bug description:
  STEPS:
  1. Flash a fresh image
  2. Complete the welcome wizard enable location but leave the here tos 
unchecked
  3. Complete the edges demo
  4. Open here webapp

  EXPECTED:
  I expect to get a location of some sort as location is enabled

  ACTUAL:
  No location is given at all.

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

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

[Touch-packages] [Bug 1383724] Re: In the welcome wizard enable location but not here services and in here maps app you get no location

[Olli Ries]

** Tags removed: rtm14

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

Title:
  In the welcome wizard enable location but not here services and in
  here maps app you get no location

Status in “location-service” package in Ubuntu:
  New

Bug description:
  STEPS:
  1. Flash a fresh image
  2. Complete the welcome wizard enable location but leave the here tos 
unchecked
  3. Complete the edges demo
  4. Open here webapp

  EXPECTED:
  I expect to get a location of some sort as location is enabled

  ACTUAL:
  No location is given at all.

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

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

[Touch-packages] [Bug 1003854] Re: Database upgrade/migration fails with nested db directories (lucid to precise)

[Ryan Tandy]

Fixed in Debian in 2.4.40-1.

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

Title:
  Database upgrade/migration fails with nested db directories (lucid to
  precise)

Status in “openldap” package in Ubuntu:
  Confirmed
Status in “openldap” source package in Precise:
  Confirmed
Status in “openldap” package in Debian:
  Fix Released

Bug description:
  Hi,

  I've just performed an upgrade of our LDAP server on Ubuntu 10.04.4
  LTS to Ubuntu 12.04 (I acknowledge this upgrade path is not officially
  supported yet).

  The incompatible database upgrading process in the preinst/postinst
  files failed in the following scenario.

  We have two suffixes/databases at the following paths:-

   * /var/lib/ldap
   * /var/lib/ldap/accesslog

  The preinst database dumping part of the process worked just fine and
  created the appropriate LDIF files under
  /var/backup/slapd-2.4.21-0ubuntu5.7, however the restore failed
  stating:-

  """
    Loading from /var/backups/slapd-2.4.21-0ubuntu5.7:
    - directory dc=REDACTEDs,dc=co,dc=uk... failed.

  Loading the database from the LDIF dump failed with the following
  error while running slapadd:
  4fbdfebf olcDbDirectory: value #0: invalid path: No such file or directory
  4fbdfebf config error processing olcDatabase={2}hdb,cn=config: 
olcDbDirectory: value #0: invalid path: No such file or directory
  slapadd: bad configuration directory!
  """

  This is because when move_incompatible_databases_away() runs it finds
  the main database first (/var/lib/ldap) and moves all top level
  entries (find -mindepth 1 -maxdepth 1 ...) into the backup directory
  and this includes the accesslog subdirectory which then no longer
  exists. When slapadd runs it checks config specifying that directory
  and bails with the above error given it is indeed missing.

  I've tested a tentative fix and that's to patch the two find commands
  (one in is_empty_dir() one in move_old_database_away to also specify
  -type f so that the directory structure is preserved when moving the
  old database away (accesslog will be backed up separately when its
  suffx is iterated over in move_incompatible_databases_away()).

  The simple and very tentative patch for this is:-

  """
  # diff -u slapd.scripts-common.old slapd.scripts-common
  --- slapd.scripts-common.old  2012-05-24 10:33:01.746206585 +0100
  +++ slapd.scripts-common  2012-05-24 10:33:23.967902747 +0100
  @@ -391,7 +391,7 @@
     echo -n "  - directory $suffix... " >&2
     mkdir -p "$backupdir"
     find "$databasedir" -mindepth 1 -maxdepth 1\
  - -exec mv {} "$backupdir" \;
  + -type f -exec mv {} "$backupdir" \;
     echo done. >&2
    else
     cat >&2 /dev/null`
    if [ -n "$output" ]; then
     return 1
    else
  """

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

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

[Touch-packages] [Bug 964497] Re: GIF loader uses about 280M of VmRSS for a 200Kb GIF

[Bug Watch Updater]

** Changed in: gdk-pixbuf
   Status: New => Fix Released

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

Title:
  GIF loader uses about 280M of VmRSS for a 200Kb GIF

Status in pixbuf library for gtk+:
  Fix Released
Status in “gdk-pixbuf” package in Ubuntu:
  New

Bug description:
  https://bugzilla.gnome.org/show_bug.cgi?id=585425

  Patch reduced memory usage from 892MiB to 30MiB on amd64 - may it will
  be useful?

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdk-pixbuf/+bug/964497/+subscriptions

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

[Touch-packages] [Bug 1382595] Re: [TOPBLOCKER] /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service:indicator-network-service: pthread_mutex_lock.c:80: __pthread_mutex_lock: Asser

[Alexander Sack]

** Summary changed:

- 
/usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service:indicator-network-service:
 pthread_mutex_lock.c:80: __pthread_mutex_lock: Assertion 
`mutex->__data.__owner == 0' failed.
+ [TOPBLOCKER] 
/usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service:indicator-network-service:
 pthread_mutex_lock.c:80: __pthread_mutex_lock: Assertion 
`mutex->__data.__owner == 0' failed.

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

Title:
  [TOPBLOCKER] /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-
  network-service:indicator-network-service: pthread_mutex_lock.c:80:
  __pthread_mutex_lock: Assertion `mutex->__data.__owner == 0' failed.

Status in “indicator-network” package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding indicator-network.  This problem was most recently seen with
  version 0.5.1+14.10.20141015-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/ecc14b5d54f3e0a0f1720cad0c623f81c8a16988
  contains more details.

  steps to reproduce: (need to trigger race condition)
  1. pull down network indicator
  2. toggle flight mode on and off quickly a few times
  3. click sim card 1 and 2
  4. toggle flight mode
  5. swipe up close indicators
  6. repeat steps 1-5 until crash occurs

  expected results:
  no crash happens

  actual results:
  Bluetooth indicator blinks (appear and disappear) in indicator bar at top of 
screen, and network indicator crashes. 

  additional info:
  eventually the bluetooth indicator appears stable in the indicators at the 
top of the screen.

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

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

[Touch-packages] [Bug 1384416] Re: coreutils 'info command' broken

[A. Eibach]

Your bypass did not work at all, but thanks to the debbug entry you
linked, I got two working variants now:

(fully compatible, anywhere)

$ info '(coreutils) cat invocation'

(note: might not work everywhere)

$ info Coreutils 'cat invocation'

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

Title:
  coreutils 'info command' broken

Status in The Gnu Core Utilities:
  Unknown
Status in “coreutils” package in Ubuntu:
  Triaged

Bug description:
  Try the following on Ubuntu (or one of its flavors) and tell me what
  you see:

  $ info coreutils 'cat invocation'

  Should give you the *detailed* cat manual. However,  you will in fact
  land on "2.14 'coreutils' Multi-call binary" in the documentation. Now
  idea yet how to fix this.

  Great job. Seems the bug they reported on Debian mailing list on 9/11
  (2014)

  https://www.mail-archive.com/debian-bugs-
  d...@lists.debian.org/msg1256146.html

  ... has now made its way into the Ubuntu version of coreutils as well.

  By the way,  isn't that a great comment again??

  "though downstream 8.23 could be tweaked to avoid this issue."

  Cool. They've broken something that worked perfectly _for years_ and
  all the user gets is "yeah, 8.23 'could be tweaked'". If only he had
  said _how_ to tweak it!! But apparently the commenter was way too lazy
  to write one more line.

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

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

[Touch-packages] [Bug 1374419] Re: [TOPBLOCKER] Threading issue with the MenuModel Updates

[Alexander Sack]

** Summary changed:

- Threading issue with the MenuModel Updates
+ [TOPBLOCKER] Threading issue with the MenuModel Updates

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

Title:
  [TOPBLOCKER] Threading issue with the MenuModel Updates

Status in “indicator-network” package in Ubuntu:
  In Progress
Status in “ubuntu-system-settings” package in Ubuntu:
  Invalid

Bug description:
  This and other "corruptions" in the i-network menus is caused by a
  race condition in the i-network-service GMainLoop synchronization.

  ===
  Some access points in indicator-network show twice, when they should be 
merged into a single entry given that security and SSID are the same.

  See attached screenshot.

  For example, "Instant Staff" should only show once, not greyed out.
  There are not multiple APs with different security settings to justify
  two different entries.

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

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

[Touch-packages] [Bug 1382501] Re: Android GPS HAL should only be started/stopped at most once

[Pat McGowan]

** Tags added: touch-2014-10-30

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

Title:
  Android GPS HAL should only be started/stopped at most once

Status in “location-service” package in Ubuntu:
  In Progress

Bug description:
  Some Android GPS HAL implementations seem to have an issue with multiple 
start/stop attempts if they are already running/stopped. The subsequent 
behavior is undefined and results in bugs that are difficult to 
track/identify/trace back to 
  the misbehaving HAL. With that, the gps provider implementation should ensure 
correct behavior.

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

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

[Touch-packages] [Bug 1380736] Re: showing notification right after boot causes unity8 crash

[Olli Ries]

** Changed in: qtubuntu-media (Ubuntu)
   Importance: Critical => High

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

Title:
  showing notification right after boot causes unity8 crash

Status in Network Menu:
  Invalid
Status in “dbus-cpp” package in Ubuntu:
  Invalid
Status in “media-hub” package in Ubuntu:
  Invalid
Status in “qtubuntu-media” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  Invalid
Status in “qtubuntu-media” package in Ubuntu RTM:
  Fix Released

Bug description:
  STEPS:
  1. Install a new image (Apparently it works with just re-running the wizard)
  2. While the dash is empty drag down the network indicator
  3. Click on the first unlock sim button
  4. Type in the unlock code and hit the tick
  5. System locks up

  EXPECTED:
  I expect the lock you unlock the sim and change back to the indicator

  ACTUAL:
  The system hard locks nothing works.  In the end you are forced to hard 
shutdown the phone by pressing and holding the power button till the phone 
powers down.

  Booting the Phone back up after this and everthing works as expected.
  Also waiting on the dash to fully load and fill with apps and then unlocking 
works.

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

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

[Touch-packages] [Bug 1381069] Re: We should hide the player controls in the sound indicator until the music player is fixed to work with them

[Olli Ries]

** Changed in: indicator-sound (Ubuntu)
   Status: In Progress => Invalid

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

Title:
  We should hide the player controls in the sound indicator until the
  music player is fixed to work with them

Status in “indicator-sound” package in Ubuntu:
  Invalid
Status in “media-hub” package in Ubuntu:
  Fix Released

Bug description:
  see these two bugs:
  https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1378048
   
https://bugs.launchpad.net/ubuntu/+source/unity-scope-mediascanner/+bug/1361232

  Essentially, the music player does not work with the sound menu, and
  the fix is involved. Until the default experience works, I suggest
  that we do not show these controls.

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

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

[Touch-packages] [Bug 1382039] Re: [TOPBLOCKER] Apps scope empty on boot

[Alexander Sack]

** Summary changed:

- Apps scope empty on boot
+ [TOPBLOCKER] Apps scope empty on boot

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

Title:
  [TOPBLOCKER] Apps scope empty on boot

Status in “unity-scope-click” package in Ubuntu:
  New
Status in “unity-scopes-api” package in Ubuntu:
  New
Status in “unity-scopes-shell” package in Ubuntu:
  Confirmed
Status in “unity8” package in Ubuntu:
  Triaged

Bug description:
  Several people reported today that the apps scope came up empty on
  boot. A pull-to-refresh makes results come in again.

  Note: it seems the problem is more likely to happen if you wait for at
  least 1 minute after reboot, and then unlock your device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1382039/+subscriptions

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

[Touch-packages] [Bug 1364466] Re: /usr/bin/mediascanner-service-2.0:*** Error in `mediascanner-service-2.0': double free or corruption (fasttop): ADDR ***

[Pat McGowan]

Thomas can we get a read on who can debug this as its seems ownerless

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

** Changed in: mediascanner2 (Ubuntu)
 Assignee: (unassigned) => Thomas Strehl (strehl-t)

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

Title:
  /usr/bin/mediascanner-service-2.0:*** Error in `mediascanner-
  service-2.0': double free or corruption (fasttop): ADDR ***

Status in “gstreamer” package in Ubuntu:
  Confirmed
Status in “mediascanner2” package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding mediascanner2.  This problem was most recently seen with
  version 0.104+14.10.20140825-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/354f10fdaba609ee33dd0a2868637ec79c590b56
  and
  https://errors.ubuntu.com/problem/01fcf2789e27c0abf6922c68c02a408b907fab83
  contains more details.

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

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

[Touch-packages] [Bug 1379836] Re: dialer and messaging app show unlocked pin as locked

[Olli Ries]

** Changed in: telepathy-ofono (Ubuntu)
   Importance: Critical => High

** Changed in: telepathy-ofono
   Importance: Critical => High

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

Title:
  dialer and messaging app show unlocked pin as locked

Status in Telepathy Ofono:
  In Progress
Status in “indicator-network” package in Ubuntu:
  Invalid
Status in “telepathy-ofono” package in Ubuntu:
  In Progress
Status in “telepathy-ofono” package in Ubuntu RTM:
  Fix Released

Bug description:
  Ubuntu System Settings and ofono say it's unlocked but trying to use
  the dialer and messaging app is blocked by thinking the PIN is locked.

  $ system-image-cli -i
  current build number: 81
  device name: mako
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2014-10-10 15:33:48
  version version: 81
  version ubuntu: 20141010.1
  version device: 20140929.1
  version custom: mako-0.7

  $ phablet-shell 
  /home/sergiusens/.ssh/known_hosts updated.
  Original contents retained as /home/sergiusens/.ssh/known_hosts.old
  Warning: Permanently added '[localhost]:' (RSA) to the list of known 
hosts.
  Welcome to Ubuntu Utopic Unicorn (development branch) (GNU/Linux 3.4.0-5-mako 
armv7l)

   * Documentation:  https://help.ubuntu.com/
  Last login: Fri Oct 10 15:37:40 2014 from localhost.localdomain
  phablet@ubuntu-phablet:~$ lis^C
  phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-modems 
  [ /ril_0 ]
  Features = gprs ussd net sms rat sim 
  Model = Fake Modem Model
  Powered = 1
  Emergency = 0
  Online = 1
  Interfaces = org.ofono.ConnectionManager org.ofono.CallBarring 
org.ofono.CallSettings org.ofono.SupplementaryServices 
org.ofono.NetworkRegistration org.ofono.CallForwarding org.ofono.SmartMessaging 
org.ofono.PushNotification org.ofono.MessageManager org.ofono.NetworkTime 
org.ofono.MessageWaiting org.ofono.RadioSettings org.ofono.SimManager 
org.ofono.CallVolume org.ofono.VoiceCallManager 
  Revision = M9615A-CEFWMAZM-2.0.1701.03
  Type = hardware
  Manufacturer = Fake Manufacturer
  Serial = 355136052657866
  Lockdown = 0
  [ org.ofono.ConnectionManager ]
  Bearer = hspa
  RoamingAllowed = 0
  Suspended = 0
  Powered = 1
  Attached = 1
  [ org.ofono.CallBarring ]
  VoiceIncoming = disabled
  VoiceOutgoing = disabled
  [ org.ofono.CallSettings ]
  CallingLineRestriction = off
  HideCallerId = default
  ConnectedLinePresentation = unknown
  ConnectedLineRestriction = unknown
  CallingLinePresentation = enabled
  CallingNamePresentation = unknown
  CalledLinePresentation = disabled
  VoiceCallWaiting = enabled
  [ org.ofono.SupplementaryServices ]
  State = idle
  [ org.ofono.NetworkRegistration ]
  Mode = auto
  Name = Personal
  LocationAreaCode = 394
  Status = registered
  CellId = 14122637
  MobileCountryCode = 722
  Technology = umts
  Strength = 61
  MobileNetworkCode = 34
  [ org.ofono.CallForwarding ]
  VoiceNotReachable = +541151009255
  VoiceNoReplyTimeout = 25
  VoiceUnconditional = 
  VoiceNoReply = +541151009255
  ForwardingFlagOnSim = 0
  VoiceBusy = +541151009255
  [ org.ofono.SmartMessaging ]
  [ org.ofono.PushNotification ]
  [ org.ofono.MessageManager ]
  Alphabet = default
  UseDeliveryReports = 0
  ServiceCenterAddress = +541151740055
  Bearer = cs-preferred
  [ org.ofono.NetworkTime ]
  [ org.ofono.MessageWaiting ]
  VoicemailWaiting = 0
  VoicemailMailboxNumber = *555
  VoicemailMessageCount = 0
  [ org.ofono.RadioSettings ]
  TechnologyPreference = umts
  ModemTechnologies = gsm umts 
  FastDormancy = 0
  [ org.ofono.SimManager ]
  CardIdentifier = 89543421113404033941
  ServiceNumbers = [Llam. a su Cargo] = '11' [Club Personal] = 
'*2582' [Personal] = '+810' [At. Clientes] = '*111' 
  Retries = 
  FixedDialing = 0
  SubscriberIdentity = 722341240403394
  MobileCountryCode = 722
  BarredDialing = 0
  PinRequired = none
  LockedPins = 
  SubscriberNumbers = 
  Present = 1
  PreferredLanguages = es en pt it 
  MobileNetworkCode = 34
  [ org.ofono.CallVolume ]
  MicrophoneVolume = 0
  Muted = 1
  SpeakerVolume = 0
  [ org.ofono.VoiceCallManager ]
  EmergencyNumbers = 112 911

To manage notifications about this bug go to:
https://bugs.launchpad.net/telepathy-ofono/+bug/1379836/+subscriptions

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

[Touch-packages] [Bug 1378377] Re: /usr/bin/mediascanner-service-2.0:*** Error in `mediascanner-service-2.0': corrupted double-linked list: ADDR ***

[Olli Ries]

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

** Tags removed: rtm14

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

Title:
  /usr/bin/mediascanner-service-2.0:*** Error in `mediascanner-
  service-2.0': corrupted double-linked list: ADDR ***

Status in “mediascanner2” package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding mediascanner2.  This problem was most recently seen with
  version 0.105+14.10.20141001.1-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/01fcf2789e27c0abf6922c68c02a408b907fab83
  contains more details.

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

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

[Touch-packages] [Bug 1378043] Re: [TOPBLOCKER] Phone is getting locked during a call

[Alexander Sack]

** Summary changed:

- Phone is getting locked during a call
+ [TOPBLOCKER] Phone is getting locked during a call

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

Title:
  [TOPBLOCKER] Phone is getting locked during a call

Status in Dialer app for Ubuntu Touch:
  Invalid
Status in “powerd” package in Ubuntu:
  In Progress

Bug description:
  The phone is getting lock during a call.

  How to reproduce
  

  1 - Open dialer app
  2 - Type a number
  3 - Click to call
  4 - Cover the proximity sensor
  5 - Uncover the proximity sensor

  Expected
  

  The phone shows the active call information

  Current results
  ===

  The phone get locked and you need to type your password to unlock it

  
  OBS:

  If you wait the call complete for about 3~ secs everything works nice.

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

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

[Touch-packages] [Bug 1376495] Re: autopilot3 run camera_app.tests.test_zoom.TestCameraZoom.test_slider_zoom_out crashes camera-app

[Olli Ries]

** Changed in: camera-app (Ubuntu)
   Importance: Critical => High

** Changed in: camera-app
   Importance: Critical => High

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

Title:
  autopilot3 run
  camera_app.tests.test_zoom.TestCameraZoom.test_slider_zoom_out crashes
  camera-app

Status in Camera App:
  In Progress
Status in “camera-app” package in Ubuntu:
  In Progress

Bug description:
  Summary:
  autopilot3 run camera_app.tests.test_zoom.TestCameraZoom.test_slider_zoom_out 
crashes camera-app

  steps:
  1. phablet-click-test-setup -s $ANDROID_SERIAL
  2. phablet-config -s $ANDROID_SERIAL autopilot --dbus-probe enable
  3. adb -s $ANDROID_SERIAL shell
  4. cd autopilot 
  5. autopilot3 run 
camera_app.tests.test_zoom.TestCameraZoom.test_slider_zoom_out -
  6. ls /var/crash

  expected results:
  test passes without crashing camera app

  actual results:
  test crashes camera app

  base: system-image.ubuntu.com
  http_port: 80
  https_port: 443
  channel: ubuntu-touch/devel-proposed
  device: mako
  build_number: 263
  channel_target: ubuntu-touch/utopic-proposed
  version_detail: ubuntu=20140930,device=20140929.1,custom=mako-0.6,version=263

  com.ubuntu.camera   3.0.0.387

To manage notifications about this bug go to:
https://bugs.launchpad.net/camera-app/+bug/1376495/+subscriptions

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

[Touch-packages] [Bug 1378012] Re: [krillin only] screen goes black immediately when pressing the Call button in dialer

[Olli Ries]

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

** Changed in: powerd
   Importance: Critical => High

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

Title:
  [krillin only] screen goes black immediately when pressing the Call
  button in dialer

Status in PowerD:
  In Progress
Status in “powerd” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu RTM:
  New

Bug description:
  latest rtm image 84 on krillin
  Have seen this problem for quite a while, but it is intermittent. Does not 
happen all the time, but I can get it to happen at least a few times per day

  Steps to reproduce:
  - open dialer
  - type a number using the keypad
  - press the call button

  Expected results:
  - screen stays on, live call view is made visible

  Actual results:
  - the screen goes immediately black
  - pressing the power button shows the greeter/lockscreen as the call is not 
active yet
  - the call continues to ring but you can't interact with it until you unlock 
the screen

  This is causing Autopilot failures as well for the dialer as sometimes
  the screen goes black and can't be interacted with until unlocked.

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

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

[Touch-packages] [Bug 1236290] Re: [gesture recognition] Implement improved edge gesture detection to reduce false positives and pass non-edge gestures through to the focused app

[Pat McGowan]

** Tags removed: ota-1

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

Title:
  [gesture recognition] Implement improved edge gesture detection to
  reduce false positives and pass non-edge gestures through to the
  focused app

Status in Ubuntu UX bugs:
  Fix Committed
Status in “unity8” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu RTM:
  In Progress

Bug description:
  (from section "3.1 Edge drag gestures" in the "Unity Gesture UI
  Guidelines" doc https://docs.google.com/a/canonical.com/document/d
  /1WJF8YdphrorvHiB5FFVxsitL5Pz-tpZ5-kmtzoD3tFc/edit )

  These are Unity level gestures that allow the user to reveal and
  interact with shell elements like the Launcher.  To reduce the number
  of false positives, edge drag gestures are only triggered when a user
  drags their finger over the edge of the screen and the drag does not
  have following charastics:

  - If the initial velocity is zero or close to zero an edge gesture is
  not triggered.  The gesture is passed through to the app.  This is
  because the intended gesture is probably a tap or a hold

  - If the initial velocity is high an edge gesture is not triggered.
  The gesture is passed through to the app.  This is because the
  intended gesture is probably a flick

  - If the initial direction is not close to perpendicular to the edge
  an edge gesture is not triggered.  This is because the intended
  gesture may be a vertical drag.

  - If at the gesture’s initiation the user has more than one finger
  touching the screen an edge gesture is not triggered.  This is because
  the intended gesture may be a pinch, spread or rotate.

  ---
  Desired resolution:

  - Implement the heuristics defined above for detecting edge gestures
  to reduce the incidence of false positives.

  - The exact values for these heuristics should be easily modifiable so
  that we can experiment with different values to find the optimal
  values.

  - Gestures performed on the edge of the screen when are no longer
  detected as edge gestures due to the above heuristics should be passed
  through to the currently focused app.

  Note: The solution must fix the problem described in bug 1350881

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

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

[Touch-packages] [Bug 1384394] Re: /etc/network/interfaces: "dns-nameservers" entries for bridge "br*" interfaces are ignored i.e. they are not listed in "/etc/resolv.conf" when invoking "ifup" comman

[Thaddäus Tintenfisch]

** Package changed: xubuntu-meta (Ubuntu) => resolvconf (Ubuntu)

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

Title:
  /etc/network/interfaces: "dns-nameservers" entries for bridge "br*"
  interfaces are ignored i.e. they are not listed in "/etc/resolv.conf"
  when invoking "ifup" command

Status in “resolvconf” package in Ubuntu:
  New

Bug description:
  lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  apt-cache policy resolvconf
  resolvconf:
Installed: 1.69ubuntu1.1
Candidate: 1.69ubuntu1.1
Version table:
   *** 1.69ubuntu1.1 0
  500 http://ch.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.69ubuntu1 0
  500 http://ch.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  DESCRIPTION:
  network-manager: My "eth0" and "wlan0" cards are managed by the 
network-manager and this works fine.

  /etc/network/interfaces: My 2 bridges "br0" and "br1" are managed in 
"/etc/network/interfaces" as follows:
  ...
  iface br0 inet static
   address 192.168.10.1
   netmask 255.255.255.0
   dns-nameservers 192.168.10.2
   bridge_ports none
   bridge_stp off
   bridge_fd 0
   bridge_maxwait 0

  iface br1 inet static
   address 192.168.0.1
   netmask 255.255.255.0
   dns-nameservers 192.168.0.2
   bridge_ports none
   bridge_stp off
   bridge_fd 0
   bridge_maxwait 0
  ...

  When I now bring up the bridge interfaces using:
  sudo ifup br0 br1
  Then they show up fine in "ifconfig".
  BUT "dns-nameservers 192.168.10.2" and "dns-nameservers 192.168.0.2" DO NOT 
show up in "/etc/resolv.conf"

  WORKAROUND: Until this has been fixed the following workaround works fine for 
me:
  sudo vi /etc/resolvconf/interface-order
  #Add the following entry (this entry can be put on any line BUT it has to 
come before the last entry "*"):
  ...
  br*
  ...
  *

  PS: Based on the workaround in "/etc/resolvconf/interface-order" I
  think the issue is in package "resolvconf" otherwise I would have
  reported the error against the "ifupdown scripts".

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

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

[Touch-packages] [Bug 1384477] [NEW] install fails: "insserv: ssh: Permission denied"

[Geoff Jacobsen]

Public bug reported:

Setting up openssh-server (1:6.6p1-8) ...
insserv: ssh: Permission denied
update-rc.d: error: insserv rejected the script header
dpkg: error processing package openssh-server (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 openssh-server
E: Sub-process /usr/bin/dpkg returned an error code (1)

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

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

Title:
  install fails: "insserv: ssh: Permission denied"

Status in “openssh” package in Ubuntu:
  New

Bug description:
  Setting up openssh-server (1:6.6p1-8) ...
  insserv: ssh: Permission denied
  update-rc.d: error: insserv rejected the script header
  dpkg: error processing package openssh-server (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   openssh-server
  E: Sub-process /usr/bin/dpkg returned an error code (1)

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

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

[Touch-packages] [Bug 1373404] Re: [notification] No warning of high volume level

[Pat McGowan]

** Changed in: indicator-sound
   Importance: Critical => High

** Changed in: ubuntu-system-settings (Ubuntu)
   Importance: Critical => High

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

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

Title:
  [notification] No warning of high volume level

Status in Sound Menu:
  In Progress
Status in Ubuntu UX bugs:
  Fix Committed
Status in “indicator-sound” package in Ubuntu:
  In Progress
Status in “pulseaudio” package in Ubuntu:
  Invalid
Status in “ubuntu-system-settings” package in Ubuntu:
  In Progress
Status in “unity-notifications” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  In Progress
Status in “indicator-sound” package in Ubuntu RTM:
  Fix Released
Status in “unity-notifications” package in Ubuntu RTM:
  Fix Released
Status in “unity8” package in Ubuntu RTM:
  Fix Released

Bug description:
  The EU has a legal requirement for personal music players to prevent hearing 
damage.
  http://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32009D0490&rid=1
  

  Desired resolution:

  - For RTM the design spec'ed in the following section of the Sound
  wiki page should be implemented
  
https://wiki.ubuntu.com/Sound#Warnings_.28note:_This_section_should_be_implemented_for_RTM.29

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-sound/+bug/1373404/+subscriptions

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

[Touch-packages] [Bug 1344386] Re: Do.exe crashed with SIGABRT in __GI_raise()

[Launchpad Bug Tracker]

** Branch linked: lp:debian/gnome-do

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

Title:
  Do.exe crashed with SIGABRT in __GI_raise()

Status in Do:
  New
Status in “glib2.0” package in Ubuntu:
  Invalid
Status in “gnome-do” package in Ubuntu:
  Fix Released

Bug description:
  Do.exe crashed with SIGABRT in __GI_raise()

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: gnome-do 0.9-1build1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jul 18 17:47:01 2014
  ExecutablePath: /usr/lib/gnome-do/Do.exe
  InstallationDate: Installed on 2014-05-16 (63 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  InterpreterPath: /usr/bin/mono-sgen
  ProcCmdline: /usr/bin/cli /usr/lib/gnome-do/Do.exe
  Signal: 6
  SourcePackage: gnome-do
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
   __GI_abort () at abort.c:89
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
   ?? ()
  Title: Do.exe crashed with SIGABRT in __GI_raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1358384] Re: MP4s won't play without a reboot of the phone

[James Henstridge]

** Package changed: mediascanner (Ubuntu) => mediascanner2 (Ubuntu)

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

Title:
  MP4s won't play without a reboot of the phone

Status in “mediascanner2” package in Ubuntu:
  New

Bug description:
  this is krillin r197

  Steps:
  1. Have an mp4 file
  2. Plug your phone into your computer
  3. In nautilus, drill down into the Videos folder
  4. Copy the video over
  5. Go to the video scope, note that the video is not there
  6. go to file manager, click on the file, note that the video does not play
  7. Reboot the phone

  Observed:
  The video is now in the scope and plays

  Expected:
  The video works without rebooting the phone

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

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

[Touch-packages] [Bug 1373404] Re: [notification] No warning of high volume level

[Olli Ries]

** Changed in: indicator-sound (Ubuntu)
   Importance: Critical => High

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

Title:
  [notification] No warning of high volume level

Status in Sound Menu:
  In Progress
Status in Ubuntu UX bugs:
  Fix Committed
Status in “indicator-sound” package in Ubuntu:
  In Progress
Status in “pulseaudio” package in Ubuntu:
  Invalid
Status in “ubuntu-system-settings” package in Ubuntu:
  In Progress
Status in “unity-notifications” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  In Progress
Status in “indicator-sound” package in Ubuntu RTM:
  Fix Released
Status in “unity-notifications” package in Ubuntu RTM:
  Fix Released
Status in “unity8” package in Ubuntu RTM:
  Fix Released

Bug description:
  The EU has a legal requirement for personal music players to prevent hearing 
damage.
  http://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32009D0490&rid=1
  

  Desired resolution:

  - For RTM the design spec'ed in the following section of the Sound
  wiki page should be implemented
  
https://wiki.ubuntu.com/Sound#Warnings_.28note:_This_section_should_be_implemented_for_RTM.29

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-sound/+bug/1373404/+subscriptions

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

[Touch-packages] [Bug 1374481] Re: Nearby and News scope do not load on reboot

[Olli Ries]

** Changed in: unity-scopes-shell (Ubuntu RTM)
   Importance: Undecided => Critical

** Changed in: unity-scopes-shell (Ubuntu)
   Importance: Critical => High

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

Title:
  Nearby and News scope do not load on reboot

Status in The Savilerow project:
  Invalid
Status in “unity-scopes-api” package in Ubuntu:
  Invalid
Status in “unity-scopes-shell” package in Ubuntu:
  In Progress
Status in “unity-scopes-shell” package in Ubuntu RTM:
  New

Bug description:
  reporduce:
  1- favourite nearby and/or news
  2- reboot the phone
  3 - unlock and swipe to nearby/news

  result:
  Scope is blank, not even departments are loaded in nearby

  expected result:
  scope load, to see what they look like, search for something and then cancel 
search. This triggers a refresh and the scopes then load ok.

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

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

[Touch-packages] [Bug 1384394] [NEW] /etc/network/interfaces: "dns-nameservers" entries for bridge "br*" interfaces are ignored i.e. they are not listed in "/etc/resolv.conf" when invoking "ifup" comm

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

lsb_release -rd
Description:Ubuntu 14.04.1 LTS
Release:14.04

apt-cache policy resolvconf
resolvconf:
  Installed: 1.69ubuntu1.1
  Candidate: 1.69ubuntu1.1
  Version table:
 *** 1.69ubuntu1.1 0
500 http://ch.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1.69ubuntu1 0
500 http://ch.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

DESCRIPTION:
network-manager: My "eth0" and "wlan0" cards are managed by the network-manager 
and this works fine.

/etc/network/interfaces: My 2 bridges "br0" and "br1" are managed in 
"/etc/network/interfaces" as follows:
...
iface br0 inet static
 address 192.168.10.1
 netmask 255.255.255.0
 dns-nameservers 192.168.10.2
 bridge_ports none
 bridge_stp off
 bridge_fd 0
 bridge_maxwait 0

iface br1 inet static
 address 192.168.0.1
 netmask 255.255.255.0
 dns-nameservers 192.168.0.2
 bridge_ports none
 bridge_stp off
 bridge_fd 0
 bridge_maxwait 0
...

When I now bring up the bridge interfaces using:
sudo ifup br0 br1
Then they show up fine in "ifconfig".
BUT "dns-nameservers 192.168.10.2" and "dns-nameservers 192.168.0.2" DO NOT 
show up in "/etc/resolv.conf"

WORKAROUND: Until this has been fixed the following workaround works fine for 
me:
sudo vi /etc/resolvconf/interface-order
#Add the following entry (this entry can be put on any line BUT it has to come 
before the last entry "*"):
...
br*
...
*

PS: Based on the workaround in "/etc/resolvconf/interface-order" I think
the issue is in package "resolvconf" otherwise I would have reported the
error against the "ifupdown scripts".

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

-- 
/etc/network/interfaces: "dns-nameservers" entries for bridge "br*" interfaces 
are ignored i.e. they are not listed in "/etc/resolv.conf" when invoking "ifup" 
command
https://bugs.launchpad.net/bugs/1384394
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to resolvconf 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 1370240] Re: Clicking a snap decision button makes the foreground application inactive

[Olli Ries]

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

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

Title:
  Clicking a snap decision button makes the foreground application
  inactive

Status in “unity8” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu RTM:
  Fix Released

Bug description:
  Steps to reproduce:

  1) open an application
  2) trigger a snap decision (by receiving a call or something like that)
  3) click the snap decision buttons

  Expected behavior:
  - the foreground application might temporarily switch to active=false while 
the snap decision is visible or during the interaction with the actions, but 
should be set back to active=true

  What happens:
  - when clicking the snap decision action the application active property is 
set to false and kept like that.

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

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

[Touch-packages] [Bug 1366777] Re: qmlscene crashed while running music-app autopilot tests

[James Henstridge]

** Project changed: mediascanner => mediascanner2

** Package changed: mediascanner (Ubuntu) => mediascanner2 (Ubuntu)

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

Title:
  qmlscene crashed while running music-app autopilot tests

Status in Media Scanner v2:
  Confirmed
Status in Music application for Ubuntu devices:
  Fix Released
Status in “mediascanner2” package in Ubuntu:
  Confirmed

Bug description:
  music-app tests could not succeed due to qmlscene crash

  
http://ci.ubuntu.com/smokeng/utopic/touch/mako/222:20140904.1:20140903.1/10220/music_app/

  _StringException: Binary content:
FailedTestScreenshot (image/png)

  /var/log/syslog: {{{Sep  5 00:59:45 ubuntu-phablet kernel: [   86.241416] 
input: autopilot-finger as /devices/virtual/input/input6}}}
  Application Log (com.ubuntu.music_music_1.3.611): {{{
  /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene: unrecognized option '--url='
  /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene: invalid option -- 'I'
  Testability driver loaded. Wire protocol version is "1.4".
  Could not create thumbnailer:  Unknown error when checking cache access: Is a 
directory
  Failed to register thumbnailer image provider: Unknown error when checking 
cache access: Is a directory
  terminate called after throwing an instance of 'std::runtime_error'
what():  Tried to open a db with an unsupported schema version.
  }}}

  test-log: {{{
  00:59:45.372 WARNING testcase:115 - No tracing available - install the 
python-autopilot-trace package!
  00:59:45.627 WARNING testcase:162 - Process manager backend unavailable, 
application snapshot support disabled.
  00:59:45.691 INFO logging:45 - str: Set the value of an initctl environment 
variable. Arguments ('/home/phablet/autopilot/fakeenv/tmp8mgdb_gk',).
  Keyword arguments: {}.
  00:59:45.712 DEBUG __init__:174 - Patched home to fake home directory 
/home/phablet/autopilot/fakeenv/tmp8mgdb_gk
  00:59:45.713 DEBUG __init__:178 - Creating music library for click test
  00:59:45.714 DEBUG __init__:179 - Home set to 
/home/phablet/autopilot/fakeenv/tmp8mgdb_gk
  00:59:45.714 DEBUG __init__:181 - Music path set to 
/home/phablet/autopilot/fakeenv/tmp8mgdb_gk/Music
  00:59:45.715 DEBUG __init__:186 - Mediascanner path set to 
/home/phablet/autopilot/fakeenv/tmp8mgdb_gk/.cache/mediascanner-2.0
  00:59:45.716 DEBUG __init__:192 - Content dir set to 
/home/phablet/autopilot/music_app/content
  00:59:45.819 DEBUG __init__:201 - Music copied, files ['1.ogg', '2.ogg', 
'3.mp3']
  00:59:45.820 DEBUG __init__:214 - Patching fake mediascanner database in 
/home/phablet/autopilot/fakeenv/tmp8mgdb_gk/.cache/mediascanner-2.0
  00:59:45.820 DEBUG __init__:217 - Mediascanner database files 
['mediastore.sql', 'mediastore.db']
  00:59:45.904 DEBUG __init__:207 - Mediascanner database copied, files 
['mediastore.sql', 'mediastore.db']
  00:59:45.906 INFO logging:45 - TestMainWindow: launch_test_click. Arguments 
(). Keyword arguments: {}.
  00:59:45.907 INFO _launcher:280 - Attempting to launch click application 
'(default)' from click package  'com.ubuntu.music' and URIs ''
  00:59:46.691 INFO _launcher:120 - Attempting to launch application 
'com.ubuntu.music_music_1.3.611' with URIs '' via upstart-app-launch
  01:00:13.601 ERROR proxies:410 - Introspect error on 
:1.96:/com/canonical/Autopilot/Introspection: dbus.exceptions.DBusException:
  org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout 
by message bus)
  01:00:13.602 DEBUG proxies:413 - Executing introspect queue due to error
  01:00:36.491 ERROR _launcher:206 - Timed out waiting for Application with 
app_id 'com.ubuntu.music_music_1.3.611' to stop.
  01:00:36.498 INFO logging:45 - str: Set the value of an initctl environment 
variable. Arguments ('/home/phablet',). Keyword arguments: {}.
  }}}

  Traceback (most recent call last):
File "/home/phablet/autopilot/music_app/tests/test_music.py", line 26, in 
setUp
  super(TestMainWindow, self).setUp()
File "/home/phablet/autopilot/music_app/tests/__init__.py", line 255, in 
setUp
  self.app = MusicApp(launcher_method())
File "/usr/lib/python3/dist-packages/autopilot/logging.py", line 46, in 
inner
  return f(instance, *args, **kwargs)
File "/home/phablet/autopilot/music_app/tests/__init__.py", line 92, in 
launch_test_click
  emulator_base=ubuntuuitoolkit.UbuntuUIToolkitCustomProxyObjectBase)
File "/usr/lib/python3/dist-packages/autopilot/testcase.py", line 310, in 
launch_click_package
  return launcher.launch(package_id, app_name, app_uris)
File "/usr/lib/python3/dist-packages/autopilot/application/_launcher.py", 
line 283, in launch
  return super().launch(app_id, app_uris)
File "/usr/lib/python3/dist-packages/autopilot/application/_launcher.py", 
line 146, in launch
  pid=pid
File "/usr/lib/python3/dist-packages

[Touch-packages] [Bug 1372973] Re: [Call]There should be a audible feedback(e.g beep) when the caller hangs up first

[Olli Ries]

** Changed in: dialer-app
   Importance: Critical => High

** Changed in: telephony-service
   Importance: Critical => High

** Changed in: dialer-app (Ubuntu)
   Importance: Critical => High

** Changed in: telephony-service (Ubuntu)
   Importance: Critical => High

** Changed in: telephony-service (Ubuntu RTM)
   Importance: Critical => High

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

Title:
  [Call]There should be a audible feedback(e.g beep) when the caller
  hangs up first

Status in Dialer app for Ubuntu Touch:
  Invalid
Status in Telephony Service:
  In Progress
Status in Ubuntu UX bugs:
  Fix Committed
Status in “dialer-app” package in Ubuntu:
  Invalid
Status in “telephony-service” package in Ubuntu:
  New
Status in “telephony-service” package in Ubuntu RTM:
  New

Bug description:
  [Procedures]
  1.there is a voice call
  2.the other party hangs up first
  3.the conversation view exit automatically

  [Expect results]
  There should be a audible feedback (e.g beeps) when the conversation view 
exit automatically

  [Actual results]
  Nothing

  [Reproduce]
  Always

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

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

[Touch-packages] [Bug 1368670] Re: [Dash] Simplify 'Manage Dash' area

[Olli Ries]

** Tags removed: touch-2014-10-23

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

Title:
  [Dash] Simplify 'Manage Dash' area

Status in Ubuntu UX bugs:
  Fix Committed
Status in “unity-scopes-shell” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  In Progress
Status in “unity-scopes-shell” package in Ubuntu RTM:
  In Progress
Status in “unity8” package in Ubuntu RTM:
  In Progress

Bug description:
  UX Testing Report: "Replace the current bottom edge screens with the
  simpler "Complete list of Scopes" design."

  New Manage Dash design can be found here:
  
https://sites.google.com/a/canonical.com/unity-8-dash-rtm-1/scope-structure-navigation/my-feeds-structure

  Additional UX Testing Report findings addressed by the redesign:

  "Poor discoverability and comprehension of scopes - The use of
  labelings that do not include the word 'scope'/'scopes'"

  "Lack of visual distinctions between apps and scopes in the 'manage
  dash' screen"

  "Undefined relationship between apps and scopes"

  "Search function does not help the discovery of scopes"

  "No dedicated place for adding scopes on the dash"

  "Poor memorability in locating the' manage dash' screen again"

  "The impact of making a scope favourite is unclear"

  "Lack of indication of the nature of the scopes under 'all' tab on
  'manage dash'"

  "Navigation between manage dash and apps scope was difficult"

  "Expect to see categorises instead of content"


  ---
  [EDIT]
  Please refer to the "Dash & Feeds RTM usability fix" for this bug:
  
https://docs.google.com/a/canonical.com/document/d/1LsjdqKDVcFN8Zxb_Oe-Zk1X_DiqviXr8D7-ELt2LEFI/edit?usp=sharing

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

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

[Touch-packages] [Bug 1368492] Re: crash opening image file

[Olli Ries]

** Changed in: ubuntu-ui-toolkit
   Importance: Critical => High

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

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

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

Title:
  crash opening image file

Status in Ubuntu UI Toolkit:
  In Progress
Status in “gallery-app” package in Ubuntu:
  Fix Released
Status in “thumbnailer” package in Ubuntu:
  Invalid
Status in “ubuntu-ui-toolkit” package in Ubuntu:
  In Progress
Status in “gallery-app” package in Ubuntu RTM:
  Fix Released
Status in “ubuntu-ui-toolkit” package in Ubuntu RTM:
  Fix Released

Bug description:
  krillin image 25
  libthumbailer version 1.2+14.10.20140814-0ubuntu1

  - take a picture with the camera
  - open the gallery app
  - click on the thumbnail of the photo just taken
  - boom, crash happens

  Here is the stack trace. Core file and picture used are attached

  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
  Core was generated by `./gallery-app'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0xb5b2201c in std::string::assign(std::string const&) ()
 from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  (gdb) bt
  #0  0xb5b2201c in std::string::assign(std::string const&) ()
 from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  #1  0xacebe712 in ?? () from /usr/lib/arm-linux-gnueabihf/libthumbnailer.so.0
  #2  0xacebec62 in ?? () from /usr/lib/arm-linux-gnueabihf/libthumbnailer.so.0
  #3  0xacebff34 in Thumbnailer::get_thumbnail(std::string const&, 
ThumbnailSize, ThumbnailPolicy) () from 
/usr/lib/arm-linux-gnueabihf/libthumbnailer.so.0
  #4  0xacec00ae in Thumbnailer::get_thumbnail(std::string const&, 
ThumbnailSize)
  () from /usr/lib/arm-linux-gnueabihf/libthumbnailer.so.0
  #5  0xacf7b70e in ThumbnailGenerator::requestImage(QString const&, QSize*, 
QSize const&) ()
 from 
/usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/libUbuntuComponents.so
  #6  0xb640acfa in ?? () from /usr/lib/arm-linux-gnueabihf/libQt5Quick.so.5
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

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

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

[Touch-packages] [Bug 1368856] Re: [Indicators] Update indicators to match the latest design

[Olli Ries]

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

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

Title:
  [Indicators] Update indicators to match the latest design

Status in Ubuntu UX bugs:
  Fix Committed
Status in “unity8” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu RTM:
  Fix Released

Bug description:
  There is a new indicators design that improves and fixes many of the
  usability issues in the current design.

  New design fixes following issues:
  1. Too small target size for reliably making selection -> false positives
  2. Current design doesn’t support overflow. Or inactive items so that their 
menu could be accessed.
  3. Movement overload when item changes while going down.
  4. Tabs. Deprecated component and poor navigation.
  5. Invisible locking line in mid point of the screen.

  Specification can be found here:
  
https://docs.google.com/a/canonical.com/document/d/1jHIGzAzf7kFELgOiU9J0Hd9mOa3NzTsnEglLmx_qEfk/edit

  There is also a prototype of the new design:
  It can be found here: lp:~willow-team/willow/Indicators-Bens-idea/

  There is also a screencast video of the prototype in action here:
  
https://docs.google.com/a/canonical.com/file/d/0B8eY_FZZ1z7IN0ZaazhwOUhjdnc/edit

  Implementing this would be one way of fixing bug 1285951, bug 1352784,
  and bug 1370799.

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

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

[Touch-packages] [Bug 1368808] Re: [camera]+[gallery] Accessing photo roll could be more discoverable

[Olli Ries]

** Changed in: camera-app
   Importance: Critical => High

** Changed in: camera-app (Ubuntu RTM)
   Importance: Critical => High

** Changed in: camera-app (Ubuntu)
   Importance: Critical => High

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

Title:
  [camera]+[gallery] Accessing photo roll could be more discoverable

Status in Camera App:
  In Progress
Status in Ubuntu UX bugs:
  Fix Committed
Status in “camera-app” package in Ubuntu:
  In Progress
Status in “camera-app” package in Ubuntu RTM:
  In Progress

Bug description:
  "Some participants tried locate a picture icon option on the camera to
  link them to the photo they just had taken.  Not finding it, they left
  the camera and looked for the photo somewhere else, in the gallery. "

  Investigate visual aides to help users understand how to access photo
  roll

To manage notifications about this bug go to:
https://bugs.launchpad.net/camera-app/+bug/1368808/+subscriptions

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

[Touch-packages] [Bug 1342151] Re: [Indicators] Silent mode control in the indicator

[Olli Ries]

** Changed in: ubuntu-ux
   Status: Fix Committed => Fix Released

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

Title:
  [Indicators] Silent mode control in the indicator

Status in Ubuntu UX bugs:
  Fix Released
Status in “indicator-sound” package in Ubuntu:
  Fix Released
Status in “indicator-sound” package in Ubuntu RTM:
  Fix Released

Bug description:
  Should the indicator expose the control for silent mode for easy
  access?

  Implementing in settings now but would like to leverage a common
  implementation

  --

  I've attached a wireframe which shows an additional setting in the
  sound indicator for turning on and off silent mode.

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

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

[Touch-packages] [Bug 1358343] Re: TOPBLOCKER too easy to answer a call by accident

[Alexander Sack]

** Summary changed:

- [notifications] too easy to answer a call by accident
+ TOPBLOCKER too easy to answer a call by accident

** Summary changed:

- TOPBLOCKER too easy to answer a call by accident
+ [TOPBLOCKER] too easy to answer a call by accident

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

Title:
  [TOPBLOCKER] too easy to answer a call by accident

Status in Telephony Service:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in “dialer-app” package in Ubuntu:
  Confirmed
Status in “telephony-service” package in Ubuntu:
  New
Status in “unity-notifications” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  In Progress

Bug description:
  If you put the phone in your pocket with locked screen and you receive
  a call is too easy to answer or reject that by mistake. Or pressing
  the screen while trying to get the phone or the call can be answered
  without you noticed by your pocket.

To manage notifications about this bug go to:
https://bugs.launchpad.net/telephony-service/+bug/1358343/+subscriptions

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

[Touch-packages] [Bug 1342151] Re: [Indicators] Silent mode control in the indicator

[Victor Tuson Palau]

** Changed in: ubuntu-ux
   Status: Confirmed => Fix Committed

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

Title:
  [Indicators] Silent mode control in the indicator

Status in Ubuntu UX bugs:
  Fix Released
Status in “indicator-sound” package in Ubuntu:
  Fix Released
Status in “indicator-sound” package in Ubuntu RTM:
  Fix Released

Bug description:
  Should the indicator expose the control for silent mode for easy
  access?

  Implementing in settings now but would like to leverage a common
  implementation

  --

  I've attached a wireframe which shows an additional setting in the
  sound indicator for turning on and off silent mode.

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

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

[Touch-packages] [Bug 1330770] Re: click packages rely upon tls for integrity and authenticity

[Victor Tuson Palau]

** Tags removed: touch-2014-10-23
** Tags added: ota-1

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

Title:
  click packages rely upon tls for integrity and authenticity

Status in Click Package metadata search service:
  Fix Released
Status in Online service used by software center:
  Fix Released
Status in Click Packages Scope for Unity:
  Fix Committed
Status in “click” package in Ubuntu:
  Fix Released
Status in “ubuntu-system-settings” package in Ubuntu:
  In Progress
Status in “unity-scope-click” package in Ubuntu:
  Fix Released

Bug description:
  Hello, I just completed a quick review of the click source and the
  unity-scope-click source and behaviours, and found some opportunities
  for improvement.

  Debian, and Ubuntu, rely upon signed repository files with
  cryptographic hashes of packages to provide both integrity and
  authenticity checks for the packages hosted on that repository.

  The click framework and the unity-scope-click discovery and
  installation tool do not use signed repository files, nor do they have
  signatures of any sort on downloaded packages. The only integrity and
  authenticity checks are provided by the use of HTTPS.  The click
  verify command will check files within the archive against MD5sums
  stored inside the archive but the click verify command is not used
  during package installation. (This is suitable for validating
  integrity against accidental changes only.)

  While it appears that unity-scope-click properly uses HTTPS to
  download package metadata and packages, HTTPS alone is insufficient
  for our needs:

  - Someone in a position to create new certificates at any of several
  hundred certificate authorities could create certificates purporting
  to be our update servers. This actual problem has been discovered in
  the wild with several certificate authorities issuing wild-card
  certificates or even certificates with signing authority.

  - X.509 is extremely complicated; TLS is extremely complicated. Flaws
  in both are inevitable.

  - HTTPS prevents the use of caching.

  - HTTPS only 'works' for data-in-motion; it is useless for data-at-
  rest integrity and authenticity checks.

  I have not yet reviewed the tools that application authors will use to
  upload their packages to our distribution servers but note in passing
  that most of these issues are also issues for adding packages to our
  update servers -- packages in flight within our network can be
  corrupted for many reasons, packages on disk can be corrupted for many
  reasons. A signature mechanism can protect against internal network
  faults, storage faults, and provide assurance months or years later
  that an uploaded package was uploaded by someone in control of a
  corresponding private key.

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/click-package-index/+bug/1330770/+subscriptions

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

[Touch-packages] [Bug 1191934] Re: orientation wrong in playback for recorded videos

[Olli Ries]

is that fixed released in its entirety in krillin?

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

Title:
  orientation wrong in playback for recorded videos

Status in Media Hub:
  Fix Committed
Status in QT Ubuntu Media:
  New
Status in Thumbnail generator for all kinds of files:
  In Progress
Status in “qtubuntu-camera” package in Ubuntu:
  Fix Released
Status in “thumbnailer” package in Ubuntu:
  New
Status in “media-hub” package in Ubuntu RTM:
  Fix Released
Status in “qtubuntu-media” package in Ubuntu RTM:
  Fix Released
Status in “qtvideo-node” package in Ubuntu RTM:
  Fix Released

Bug description:
  saucy-15 + updates
  Galaxy Nexus
  camera-app 2.9.1daily13.06.17-0ubuntu1
  gallery-app 0.0.67daily13.06.17-0ubuntu1

  If you record a video in portrait orientation in the camera, it should
  be played back in same orientation in gallery but it is not. It's
  incorrectly displayed in landscape mode rotated 90 degrees to the
  left. See attached images.

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

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

[Touch-packages] [Bug 1381570] Re: libuuid1 uses chsh in postinst which breaks upgrades

[Michael Vogt]

** Changed in: util-linux (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  libuuid1 uses chsh in postinst which breaks upgrades

Status in “util-linux” package in Ubuntu:
  Fix Released

Bug description:
  Older systems that have the libuuid user with a interactive shell
  (/bin/sh) will fail spectacularly during a trusty->utopic upgrade
  because chsh will ask for a password and hang and if the user enters a
  password it will fail with a postinst failure really deep in the
  stack.

  This is debian bug https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=764244

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

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

[Touch-packages] [Bug 1191934] Re: orientation wrong in playback for recorded videos

[Olli Ries]

** Changed in: qtubuntu-media
   Importance: Critical => High

** Changed in: media-hub
   Importance: Critical => High

** Changed in: qtubuntu-camera (Ubuntu)
   Importance: Critical => High

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

Title:
  orientation wrong in playback for recorded videos

Status in Media Hub:
  Fix Committed
Status in QT Ubuntu Media:
  New
Status in Thumbnail generator for all kinds of files:
  In Progress
Status in “qtubuntu-camera” package in Ubuntu:
  Fix Released
Status in “thumbnailer” package in Ubuntu:
  New
Status in “media-hub” package in Ubuntu RTM:
  Fix Released
Status in “qtubuntu-media” package in Ubuntu RTM:
  Fix Released
Status in “qtvideo-node” package in Ubuntu RTM:
  Fix Released

Bug description:
  saucy-15 + updates
  Galaxy Nexus
  camera-app 2.9.1daily13.06.17-0ubuntu1
  gallery-app 0.0.67daily13.06.17-0ubuntu1

  If you record a video in portrait orientation in the camera, it should
  be played back in same orientation in gallery but it is not. It's
  incorrectly displayed in landscape mode rotated 90 degrees to the
  left. See attached images.

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

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

[Touch-packages] [Bug 1191934] Re: orientation wrong in playback for recorded videos

[Victor Tuson Palau]

** Changed in: qtubuntu-camera (Ubuntu)
   Importance: High => Critical

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

Title:
  orientation wrong in playback for recorded videos

Status in Media Hub:
  Fix Committed
Status in QT Ubuntu Media:
  New
Status in Thumbnail generator for all kinds of files:
  In Progress
Status in “qtubuntu-camera” package in Ubuntu:
  Fix Released
Status in “thumbnailer” package in Ubuntu:
  New
Status in “media-hub” package in Ubuntu RTM:
  Fix Released
Status in “qtubuntu-media” package in Ubuntu RTM:
  Fix Released
Status in “qtvideo-node” package in Ubuntu RTM:
  Fix Released

Bug description:
  saucy-15 + updates
  Galaxy Nexus
  camera-app 2.9.1daily13.06.17-0ubuntu1
  gallery-app 0.0.67daily13.06.17-0ubuntu1

  If you record a video in portrait orientation in the camera, it should
  be played back in same orientation in gallery but it is not. It's
  incorrectly displayed in landscape mode rotated 90 degrees to the
  left. See attached images.

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

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

[Touch-packages] [Bug 1379152] Re: Needs building dependency on libmtdev-dev (or making QPlatformSupport public)

[Michał Sawicz]

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

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

** Changed in: qtmir (Ubuntu)
 Assignee: (unassigned) => Timo Jyrinki (timo-jyrinki)

** Changed in: qtmir (Ubuntu RTM)
 Assignee: (unassigned) => Timo Jyrinki (timo-jyrinki)

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

Title:
  Needs building dependency on libmtdev-dev (or making QPlatformSupport
  public)

Status in Application menu for Qt5:
  New
Status in Qt integration with the Mir display server:
  New
Status in QT Ubuntu:
  New
Status in “appmenu-qt5” package in Ubuntu:
  New
Status in “maliit-framework” package in Ubuntu:
  New
Status in “qtmir” package in Ubuntu:
  In Progress
Status in “qtubuntu” package in Ubuntu:
  New
Status in Debian GNU/Linux:
  Won't Fix
Status in “qtmir” package in Ubuntu RTM:
  In Progress

Bug description:
  Because of packaging changes in Qt Base in Qt 5.3.2, packages using
  qplatformsupport from private headers will need to add an additional
  dependency to compile against it.

  From Debian bug report:
  ---
  This comes from QPlatformSupport stuff which creates a static library that 
needs this linking.

  It also happens that QPlatformSupport is private stuff, so there is really no 
way to solve this but either stop using private stuff or helping upstream to 
make QPlatformSupport public (which would be really helpful). This will in turn 
mean that it will become a dynamic lib and this bug can be fixed.
  ---

  So:
  A) someone works in qtbase upstream to make the QPlatformSupport public, or
  B) workaround with adding libmtdev-dev build dependencies

  This bug refers more to the B) option to get Qt 5.3.2 packages move
  forward.

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1379152/+subscriptions

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

[Touch-packages] [Bug 1348557] Re: Make scrolling speed resolution independent

[Zsombor Egri]

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: Incomplete => Confirmed

** Changed in: qtdeclarative-opensource-src (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  Make scrolling speed resolution independent

Status in QT Ubuntu:
  Invalid
Status in Ubuntu UI Toolkit:
  Confirmed
Status in “qtbase-opensource-src” package in Ubuntu:
  Confirmed
Status in “qtdeclarative-opensource-src” package in Ubuntu:
  Confirmed
Status in “unity8” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu RTM:
  In Progress

Bug description:
  Following https://bugreports.qt-project.org/browse/QTBUG-35608 the
  default speed of scrollable components (components inheriting from
  flickable basically) is not resolution independent. The result is that
  scrolling speed on our high dpi touch screens is slow.

  We could workaround this in the SDK until the bug is fixed upstream (I
  bet it won't happen in time for our releases), by simply adding
  components named as Flickable, Listview, Gridview etc etc in the
  Ubuntu.Components, where each of them sets the speed to be resolution
  independent following our GU guidelines

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

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

[Touch-packages] [Bug 1384441] Re: [dash] Some results should not be interactive

[Olli Ries]

** Tags added: touch-2014-10-30

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

Title:
  [dash] Some results should not be interactive

Status in “unity-scope-mediascanner” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu RTM:
  In Progress

Bug description:
  Steps:
  * go to music scope
  * tap on an artist
  * tap on the top result

  Expected:
  * nothing

  Current:
  * dash refreshes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-mediascanner/+bug/1384441/+subscriptions

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

[Touch-packages] [Bug 1381067] Re: left-edge drag over greeter results in jumpy launcher

[Michał Sawicz]

Pat, it's only visible on devel-proposed now, but is a problem that
would be introduced by landing lp:~dandrader/unity8/touchOwnership in
RTM.

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

Title:
  left-edge drag over greeter results in jumpy launcher

Status in “unity8” package in Ubuntu:
  In Progress

Bug description:
  unity8 version 8.00+14.10.20141013.2-0ubuntu1

  Performing a left-edge drag over the greeter results in a jumpy
  launcher. It jumps back and forth a couple of times before finally
  moving rightwards to follow the gesture

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

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

[Touch-packages] [Bug 1372940] Re: Page header disappearing after uninstalling an app

[Michał Sawicz]

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

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

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

Title:
  Page header disappearing after uninstalling an app

Status in “unity8” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu RTM:
  In Progress

Bug description:
  In about half of the times, when I uninstall an app from the dash, the
  page header disappears.

  * Longpress an installed app
  * click the uninstall button
  * confirm uninstallation
  => dash will return to the main scope view (exiting previews) and header is 
gone.

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

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

[Touch-packages] [Bug 1348557] Re: Make scrolling speed resolution independent

[Michał Sawicz]

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

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

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

** Changed in: unity8 (Ubuntu RTM)
 Assignee: (unassigned) => Andrea Cimitan (cimi)

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

Title:
  Make scrolling speed resolution independent

Status in QT Ubuntu:
  Invalid
Status in Ubuntu UI Toolkit:
  Confirmed
Status in “qtbase-opensource-src” package in Ubuntu:
  Confirmed
Status in “qtdeclarative-opensource-src” package in Ubuntu:
  Confirmed
Status in “unity8” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu RTM:
  In Progress

Bug description:
  Following https://bugreports.qt-project.org/browse/QTBUG-35608 the
  default speed of scrollable components (components inheriting from
  flickable basically) is not resolution independent. The result is that
  scrolling speed on our high dpi touch screens is slow.

  We could workaround this in the SDK until the bug is fixed upstream (I
  bet it won't happen in time for our releases), by simply adding
  components named as Flickable, Listview, Gridview etc etc in the
  Ubuntu.Components, where each of them sets the speed to be resolution
  independent following our GU guidelines

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

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

[Touch-packages] [Bug 1251597] Re: Scope header sometimes appears in the middle of the scope

[Michał Sawicz]

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

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

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

Title:
  Scope header sometimes appears in the middle of the scope

Status in “unity8” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu RTM:
  In Progress

Bug description:
  I see this sometimes when switching from an app back to the
  applications scope. Not seen it in other scopes, but I don't use the
  others as much.

  The "Applications" header sometimes appears in the middle of the
  icons, over the top of them.

  See screenshot.

  This seems to happen most often if you (un)install an app in the
  store, meaning that when you go back to Apps from the store the list
  refreshes.

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

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

[Touch-packages] [Bug 1381067] Re: left-edge drag over greeter results in jumpy launcher

[Pat McGowan]

This looks fixed already? cannot reproduce

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

Title:
  left-edge drag over greeter results in jumpy launcher

Status in “unity8” package in Ubuntu:
  In Progress

Bug description:
  unity8 version 8.00+14.10.20141013.2-0ubuntu1

  Performing a left-edge drag over the greeter results in a jumpy
  launcher. It jumps back and forth a couple of times before finally
  moving rightwards to follow the gesture

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

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

[Touch-packages] [Bug 1384416] Re: coreutils 'info command' broken

[C de-Avillez]

Thank you for opening this bug and helping make Ubuntu, and free
software, better.

The Debian bug I linked to has more information, and is the core bug for
this issue. Right now, for Ubuntu (and Debian) 'info " will work, and can be used as a bypass.

I am not sure how to interpret the rest of your comments, so I will
refrain from doing so.

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

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

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

Title:
  coreutils 'info command' broken

Status in The Gnu Core Utilities:
  Unknown
Status in “coreutils” package in Ubuntu:
  Triaged

Bug description:
  Try the following on Ubuntu (or one of its flavors) and tell me what
  you see:

  $ info coreutils 'cat invocation'

  Should give you the *detailed* cat manual. However,  you will in fact
  land on "2.14 'coreutils' Multi-call binary" in the documentation. Now
  idea yet how to fix this.

  Great job. Seems the bug they reported on Debian mailing list on 9/11
  (2014)

  https://www.mail-archive.com/debian-bugs-
  d...@lists.debian.org/msg1256146.html

  ... has now made its way into the Ubuntu version of coreutils as well.

  By the way,  isn't that a great comment again??

  "though downstream 8.23 could be tweaked to avoid this issue."

  Cool. They've broken something that worked perfectly _for years_ and
  all the user gets is "yeah, 8.23 'could be tweaked'". If only he had
  said _how_ to tweak it!! But apparently the commenter was way too lazy
  to write one more line.

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

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

[Touch-packages] [Bug 1378218] Re: Calling back from notification center opens an emergency-mode dialer

[Olli Ries]

** Tags added: rtm14 touch-2014-10-30

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

Title:
  Calling back from notification center opens an emergency-mode dialer

Status in “unity8” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu RTM:
  In Progress

Bug description:
  This is extracted out of bug #1367916:

  Steps to reproduce:
  1) make sure you have a passcode lock setup on phone
  2) make sure you have indicator allows to show on lock screen (default)
  3) lock the phone
  4) call the phone and hang up before answering it, then wait till phone turns 
off after 1 minute
  5) turn on screen but don't unlock
  6) pull down the messaging menu, and click on the Missed Call to expand it, 
then tap in right corner to launch the app

  Expected Results:
  The passcode unlock screen should be shown

  Actual Results:
  The dialer gets launched in step 6 and is visible but it's in Emergency 
calling mode (because the phone is locked) so the call can't be made. The 
correct thing to do in both cases is to display the passcode unlock screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity8 8.00+14.10.20141006-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu3
  Architecture: armhf
  Date: Tue Oct  7 09:39:25 2014
  InstallationDate: Installed on 2014-10-07 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141007-020205)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1372940] Re: Page header disappearing after uninstalling an app

[Pat McGowan]

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

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

** Tags added: touch-2014-10-30

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

Title:
  Page header disappearing after uninstalling an app

Status in “unity8” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu RTM:
  New

Bug description:
  In about half of the times, when I uninstall an app from the dash, the
  page header disappears.

  * Longpress an installed app
  * click the uninstall button
  * confirm uninstallation
  => dash will return to the main scope view (exiting previews) and header is 
gone.

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

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

[Touch-packages] [Bug 1378218] Re: Calling back from notification center opens an emergency-mode dialer

[Victor Tuson Palau]

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

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

Title:
  Calling back from notification center opens an emergency-mode dialer

Status in “unity8” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu RTM:
  In Progress

Bug description:
  This is extracted out of bug #1367916:

  Steps to reproduce:
  1) make sure you have a passcode lock setup on phone
  2) make sure you have indicator allows to show on lock screen (default)
  3) lock the phone
  4) call the phone and hang up before answering it, then wait till phone turns 
off after 1 minute
  5) turn on screen but don't unlock
  6) pull down the messaging menu, and click on the Missed Call to expand it, 
then tap in right corner to launch the app

  Expected Results:
  The passcode unlock screen should be shown

  Actual Results:
  The dialer gets launched in step 6 and is visible but it's in Emergency 
calling mode (because the phone is locked) so the call can't be made. The 
correct thing to do in both cases is to display the passcode unlock screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity8 8.00+14.10.20141006-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu3
  Architecture: armhf
  Date: Tue Oct  7 09:39:25 2014
  InstallationDate: Installed on 2014-10-07 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141007-020205)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1337613] Re: ubuntu-location-service crash

[Manuel de la Peña]

I have been looking into the issue and when gdb attached I get the
following:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb4aff3c0 (LWP 9459)]
0xb6c2d7c2 in pthread_mutex_lock () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
(gdb) bt
#0  0xb6c2d7c2 in pthread_mutex_lock () from 
/lib/arm-linux-gnueabihf/libpthread.so.0
#1  0xb6c83eb8 in __gthread_mutex_lock (__mutex=) at 
/usr/include/arm-linux-gnueabihf/c++/4.9/bits/gthr-default.h:748
#2  std::mutex::lock (this=) at /usr/include/c++/4.9/mutex:135
#3  0xb6c890e2 in lock_guard (__m=..., this=) at 
/usr/include/c++/4.9/mutex:377
#4  core::Signal::operator() (this=0x18d3050, args#0=) at 
/usr/include/core/signal.h:134
#5  0xb6c80d92 in operator= (rhs=@0xb4afe998: true, this=0x18d3028) at 
/usr/include/core/property.h:82
#6  detail::CachedRadioCell::on_network_registration_property_changed 
(this=0x18d2f90, tuple=...)
at 
/build/buildd/location-service-2.1+14.10.20141013/src/location_service/com/ubuntu/location/connectivity/cached_radio_cell.cpp:495
#7  0xb6ca4d48 in 
core::dbus::Signal >::operator() (
this=0x18d29b8, msg=...) at /usr/include/core/dbus/impl/signal.h:343
#8  0xb6e23546 in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
#9  0xb6e19d54 in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
#10 0xb6e18572 in 
core::dbus::Bus::handle_message(std::shared_ptr const&) () 
from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
#11 0xb6e1860e in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
#12 0xb6a242e2 in dbus_connection_dispatch () from 
/lib/arm-linux-gnueabihf/libdbus-1.so.3
#13 0xb6e309c8 in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
#14 0xb6e2e4d8 in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
#15 0xb6e2e7b6 in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
#16 0xb6e17958 in core::dbus::Bus::run() () from 
/usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
#17 0xb6bf4360 in ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
#18 0xb6c2bf98 in start_thread () from /lib/arm-linux-gnueabihf/libpthread.so.0
#19 0xb6ae722c in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)


The/A way to reproduce it is to start the location service and turn on and off 
the aerplane mode (with a sim that needs to be unlocked). 

** Changed in: location-service (Ubuntu)
   Status: New => Confirmed

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

Title:
  ubuntu-location-service crash

Status in “location-service” package in Ubuntu:
  Confirmed
Status in “unity8-desktop-session” package in Ubuntu:
  New

Bug description:
  Hallo
  Testing unity8-MIR image ubuntu-desktop-next in dmesg there was this repeated 
a bunch of times:

  [   13.446215] init: ubuntu-location-service main process (682) killed by 
SEGV signal
  [   13.446228] init: ubuntu-location-service main process ended, respawning
  [   13.454540] init: ubuntu-location-service main process (817) killed by 
SEGV signal
  [   13.454551] init: ubuntu-location-service main process ended, respawning

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: ubuntu-location-service-bin 1.0.0+14.10.20140630-0ubuntu1
  ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0
  Uname: Linux 3.15.0-6-generic x86_64
  ApportVersion: 2.14.3-0ubuntu2
  Architecture: amd64
  Date: Fri Jul  4 00:44:15 2014
  InstallationDate: Installed on 2014-07-03 (0 days ago)
  InstallationMedia: Ubuntu-Desktop-Next 14.10 "Utopic Unicorn" - Alpha amd64 
(20140703)
  SourcePackage: location-service
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1348557] Re: Make scrolling speed resolution independent

[Alexander Sack]

general comment: please try to submit bugs for product team landing
request with many incomplete tasks etc. in future.

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

Title:
  Make scrolling speed resolution independent

Status in QT Ubuntu:
  Invalid
Status in Ubuntu UI Toolkit:
  Confirmed
Status in “qtbase-opensource-src” package in Ubuntu:
  Incomplete
Status in “qtdeclarative-opensource-src” package in Ubuntu:
  Incomplete
Status in “unity8” package in Ubuntu:
  Fix Released

Bug description:
  Following https://bugreports.qt-project.org/browse/QTBUG-35608 the
  default speed of scrollable components (components inheriting from
  flickable basically) is not resolution independent. The result is that
  scrolling speed on our high dpi touch screens is slow.

  We could workaround this in the SDK until the bug is fixed upstream (I
  bet it won't happen in time for our releases), by simply adding
  components named as Flickable, Listview, Gridview etc etc in the
  Ubuntu.Components, where each of them sets the speed to be resolution
  independent following our GU guidelines

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

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