date:20140910

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

Title:
  apt-get failing to show progress with yes command

Status in “apt” package in Ubuntu:
  Fix Released
Status in “apt” source package in Trusty:
  Fix Committed

Bug description:
  When running this command on Ubuntu 14.04 amd64 release:
  yes  | apt-get -y install tftpd-hpa
  It never finishes... Only shows black screen on the terminal.
  I know it's weird to use yes  for this command. However, just to show it 
does not make any sense the command can not be finished.
  This issue does not occur on Ubuntu 13.10, nor on Debian Sid.

  The following is some info about this system:
  ProblemType: Bug
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  Date: Thu May 29 15:06:52 2014
  Dependencies:
   dpkg 1.17.5ubuntu5.2
   gcc-4.8-base 4.8.2-19ubuntu1
   gcc-4.9-base 4.9-20140406-0ubuntu1
   gnupg 1.4.16-1ubuntu2
   gpgv 1.4.16-1ubuntu2
   libacl1 2.2.52-1
   libapt-pkg4.12 1.0.1ubuntu2
   libattr1 1:2.4.47-1ubuntu1
   libbz2-1.0 1.0.6-5
   libc6 2.19-0ubuntu6
   libgcc1 1:4.9-20140406-0ubuntu1
   liblzma5 5.1.1alpha+20120614-2ubuntu2
   libpcre3 1:8.31-2ubuntu2
   libreadline6 6.3-4ubuntu2
   libselinux1 2.2.2-1ubuntu0.1
   libstdc++6 4.8.2-19ubuntu1
   libtinfo5 5.9+20140118-1ubuntu1
   libusb-0.1-4 2:0.1.12-23.3ubuntu1
   multiarch-support 2.19-0ubuntu6
   readline-common 6.3-4ubuntu2
   tar 1.27.1-1
   ubuntu-keyring 2012.05.19
   zlib1g 1:1.2.8.dfsg-1ubuntu1
  DistroRelease: Ubuntu 14.04
  Package: apt 1.0.1ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  SourcePackage: apt
  Tags:  trusty
  Uname: Linux 3.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1365855] Re: 100% cpu in Xorg when xorg is started via lightdm

** Attachment added: lspci
   
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1365855/+attachment/4200324/+files/lspci.out

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

Title:
  100% cpu in Xorg when xorg is started via lightdm

Status in “lightdm” package in Ubuntu:
  Incomplete

Bug description:
  I see Xorg using 100% cpu when its running via lightdm.

  This is not the case if I start X via startx or when its run from lxdm or 
gdm. A strace from a VT shows constant activity (where gdm has only a select() 
waiting). Most notably this repeats:
  
  select(256, [0 1 3 5 13 24 25 26], NULL NULL {417 413000}) = 1 (in [0], left 
{417, 412998})
  read(0, 0x72bef74a0, 1024) = -1 (Bad file descriptor)
  
  (transcripted from the affected machine).

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

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

[Touch-packages] [Bug 1365855] Re: 100% cpu in Xorg when xorg is started via lightdm

** Attachment added: xorg
   
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1365855/+attachment/4200325/+files/Xorg.0.log

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

Title:
  100% cpu in Xorg when xorg is started via lightdm

Status in “lightdm” package in Ubuntu:
  Incomplete

Bug description:
  I see Xorg using 100% cpu when its running via lightdm.

  This is not the case if I start X via startx or when its run from lxdm or 
gdm. A strace from a VT shows constant activity (where gdm has only a select() 
waiting). Most notably this repeats:
  
  select(256, [0 1 3 5 13 24 25 26], NULL NULL {417 413000}) = 1 (in [0], left 
{417, 412998})
  read(0, 0x72bef74a0, 1024) = -1 (Bad file descriptor)
  
  (transcripted from the affected machine).

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

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

[Touch-packages] [Bug 1365855] Re: 100% cpu in Xorg when xorg is started via lightdm

** Attachment added: lightdm log
   
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1365855/+attachment/4200326/+files/lightdm.log

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

Title:
  100% cpu in Xorg when xorg is started via lightdm

Status in “lightdm” package in Ubuntu:
  Incomplete

Bug description:
  I see Xorg using 100% cpu when its running via lightdm.

  This is not the case if I start X via startx or when its run from lxdm or 
gdm. A strace from a VT shows constant activity (where gdm has only a select() 
waiting). Most notably this repeats:
  
  select(256, [0 1 3 5 13 24 25 26], NULL NULL {417 413000}) = 1 (in [0], left 
{417, 412998})
  read(0, 0x72bef74a0, 1024) = -1 (Bad file descriptor)
  
  (transcripted from the affected machine).

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

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

[Touch-packages] [Bug 1366805] Re: Can't log in to Unity8 in VirtualBox; Mir crashes with std::exception::what: Error opening DRM device

2014-09-10 Thread Daniel van Vugt

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

Duplicate of bug 1331980, which is arguably a duplicate of bug 1118903.

** This bug has been marked a duplicate of bug 1118903
   [enhancement] Mir lacks a software rendering backend

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

Title:
  Can't log in to Unity8 in VirtualBox; Mir crashes with
  std::exception::what: Error opening DRM device

Status in Mir:
  New
Status in “mir” package in Ubuntu:
  New

Bug description:
  When I try to login to Unity Next the system-compositor seems to crash
  immediately. I'm using Ubuntu Next on VirtualBox.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: ubuntu-desktop-mir (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
  Uname: Linux 3.16.0-14-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  Date: Mon Sep  8 15:10:15 2014
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2014-07-09 (61 days ago)
  InstallationMedia: Ubuntu-Desktop-Next 14.10 Utopic Unicorn - Alpha amd64 
(20140708)
  SourcePackage: unity-system-compositor
  SystemImageInfo:
   current build number: 0
   device name: 
   channel: daily
   last update: Unknown
  UnitySystemCompositorLog:
   Warning: ignoring unrecognised arguments:
   ERROR: 
/build/buildd/mir-0.7.0+14.10.20140829/src/platform/graphics/mesa/display_helpers.cpp(242):
 Throw in function int 
mir::graphics::mesa::helpers::DRMHelper::open_drm_device(const 
std::shared_ptrmir::udev::Context)
   Dynamic exception type: 
N5boost16exception_detail10clone_implINS0_19error_info_injectorISt13runtime_error
   std::exception::what: Error opening DRM device
   123, No medium found
  UnitySystemCompositorLogOld:
   Warning: ignoring unrecognised arguments:
   ERROR: 
/build/buildd/mir-0.7.0+14.10.20140829/src/platform/graphics/mesa/display_helpers.cpp(242):
 Throw in function int 
mir::graphics::mesa::helpers::DRMHelper::open_drm_device(const 
std::shared_ptrmir::udev::Context)
   Dynamic exception type: 
N5boost16exception_detail10clone_implINS0_19error_info_injectorISt13runtime_error
   std::exception::what: Error opening DRM device
   123, No medium found
  UpgradeStatus: No upgrade log present (probably fresh install)
  version.libdrm: libdrm2 2.4.56-1
  version.lightdm: lightdm 1.11.8-0ubuntu1
  version.mesa: libegl1-mesa-dev N/A

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

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

[Touch-packages] [Bug 1365855] Re: 100% cpu in Xorg when xorg is started via lightdm

Thanks, I attached the logs you requested. With 1.11.9-0ubuntu1 the
problem presists. I don't know when exactly it started but it happend
relatively recently. It might be a issue with the setup of X done by
lightdm, because when I launch my session via gdm I don't see this
problem.

Whats interessting is that lsof shows me that fd0 is connected as 0w to
/var/log/Xorg.0.log for both gdm/lightdm but the select() for lightdm
includes fd 0 in the select loop but for gdm it does not include it. And
lightdm has a slightly different set of options when it launches X -
i.e. -mir which is not set by gdm.

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

Title:
  100% cpu in Xorg when xorg is started via lightdm

Status in “lightdm” package in Ubuntu:
  Incomplete

Bug description:
  I see Xorg using 100% cpu when its running via lightdm.

  This is not the case if I start X via startx or when its run from lxdm or 
gdm. A strace from a VT shows constant activity (where gdm has only a select() 
waiting). Most notably this repeats:
  
  select(256, [0 1 3 5 13 24 25 26], NULL NULL {417 413000}) = 1 (in [0], left 
{417, 412998})
  read(0, 0x72bef74a0, 1024) = -1 (Bad file descriptor)
  
  (transcripted from the affected machine).

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

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

[Touch-packages] [Bug 1367623] Re: Titles should wrap in the notification menu/indicator

2014-09-10 Thread Sebastien Bacher

** Attachment added: everybody likes screenshots, right? ;-)
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1367623/+attachment/4200329/+files/unity8.png

** Description changed:

- Using rtm 26 on krillin, system updates are listing in the
- notification (indicator-message) menu, in french they show as
+ Using rtm 26 on krillin, system updates are listed in the notification
+ (indicator-message) menu, in french they show as
  
  Il existe une image d...
  hh:mm - day
  Appuyez pour ouvrir le gestionnaire
  de mise à jour du système
  
  There are a few issues there:
  - the first line/title is ellipsize but it has to, there is enough blank 
space on the right to add at least another 6 letters
  - the title doesn't have enough content to understand what the item is about
  
  Ideally that label would wrap so no content is lost, but it should at
  least use the space

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

Title:
  Titles should wrap in the notification menu/indicator

Status in “unity8” package in Ubuntu:
  New

Bug description:
  Using rtm 26 on krillin, system updates are listed in the
  notification (indicator-message) menu, in french they show as

  Il existe une image d...
  hh:mm - day
  Appuyez pour ouvrir le gestionnaire
  de mise à jour du système

  There are a few issues there:
  - the first line/title is ellipsize but it has to, there is enough blank 
space on the right to add at least another 6 letters
  - the title doesn't have enough content to understand what the item is about

  Ideally that label would wrap so no content is lost, but it should at
  least use the space

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

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

[Touch-packages] [Bug 1367623] [NEW] Titles should wrap in the notification menu/indicator

2014-09-10 Thread Sebastien Bacher

Public bug reported:

Using rtm 26 on krillin, system updates are listed in the notification
(indicator-message) menu, in french they show as

Il existe une image d...
hh:mm - day
Appuyez pour ouvrir le gestionnaire
de mise à jour du système

There are a few issues there:
- the first line/title is ellipsize but it has to, there is enough blank space 
on the right to add at least another 6 letters
- the title doesn't have enough content to understand what the item is about

Ideally that label would wrap so no content is lost, but it should at
least use the space

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

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

Title:
  Titles should wrap in the notification menu/indicator

Status in “unity8” package in Ubuntu:
  New

Bug description:
  Using rtm 26 on krillin, system updates are listed in the
  notification (indicator-message) menu, in french they show as

  Il existe une image d...
  hh:mm - day
  Appuyez pour ouvrir le gestionnaire
  de mise à jour du système

  There are a few issues there:
  - the first line/title is ellipsize but it has to, there is enough blank 
space on the right to add at least another 6 letters
  - the title doesn't have enough content to understand what the item is about

  Ideally that label would wrap so no content is lost, but it should at
  least use the space

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

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

[Touch-packages] [Bug 1328646] Re: Clock out of sync on resume from suspend

2014-09-10 Thread cm-t arudy

Hi,


Just to be sure: does the patch is now landing is an image (I am using mako as 
daily purpose, with channel devel on utopic image 203).

If it is suposing to be landed, then I can see this behavior's bug is
still here: always (and I mean always, everytime I need to check the
time) must open the clock apps after resuming the phone to be sure I
read the real time, not a cache'ed time that is not refreshed on the
lockscreen/time indicator.(if I get lost and it is not the same bug,
then tell me, I'll open a new one).

Libement

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

Title:
  Clock out of sync on resume from suspend

Status in The Date and Time Indicator:
  Invalid
Status in The Unity 8 shell:
  Fix Released
Status in “indicator-datetime” package in Ubuntu:
  Invalid
Status in “qmenumodel” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  Fix Released

Bug description:
  When the device is resumed by pressing the power button and the device
  is not connected over USB the clock is out of sync

  You need another system to compare the time to verify this bug report,
  and make sure both clocks are in sync.

  TEST CASE
  1. Unplug the device from its USB cable
  2. Press the power button to switch to suspend mode or wait until it goes to 
suspend
  3. Wait 2 or more minutes
  4. Press the power button again to resume the device
  5. Compare the time on the greeter and indicator with the time on the other 
system

  EXPECTED RESULT
  Clocks are in sync

  ACTUAL RESULT
  Time on the device is behind by several minutes. 

  The use case are people who use their device as a watch. You usually
  resume it, check the time, suspend it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity8 7.88+14.10.20140606-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.3-0ubuntu1
  Architecture: armhf
  Date: Tue Jun 10 19:11:42 2014
  InstallationDate: Installed on 2014-06-10 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140610)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1367623] Re: Titles should wrap in the notification menu/indicator

While I agree it elides too early, and that's a bug in settings
components, it's not clear that we'd want to wrap it to two lines.
Seeking design guidance.

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

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

** Changed in: ubuntu-system-settings (Ubuntu)
   Status: New = Confirmed

** Changed in: unity8 (Ubuntu)
   Status: New = Invalid

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

Title:
  Titles should wrap in the notification menu/indicator

Status in Ubuntu UX bugs:
  New
Status in “ubuntu-system-settings” package in Ubuntu:
  Confirmed
Status in “unity8” package in Ubuntu:
  Invalid

Bug description:
  Using rtm 26 on krillin, system updates are listed in the
  notification (indicator-message) menu, in french they show as

  Il existe une image d...
  hh:mm - day
  Appuyez pour ouvrir le gestionnaire
  de mise à jour du système

  There are a few issues there:
  - the first line/title is ellipsize but it has to, there is enough blank 
space on the right to add at least another 6 letters
  - the title doesn't have enough content to understand what the item is about

  Ideally that label would wrap so no content is lost, but it should at
  least use the space

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

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

[Touch-packages] [Bug 1367623] Re: Titles should wrap in the notification menu/indicator

Don't think unity8 can do anything here.

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

Title:
  Titles should wrap in the notification menu/indicator

Status in Ubuntu UX bugs:
  New
Status in “ubuntu-system-settings” package in Ubuntu:
  Confirmed
Status in “unity8” package in Ubuntu:
  Invalid

Bug description:
  Using rtm 26 on krillin, system updates are listed in the
  notification (indicator-message) menu, in french they show as

  Il existe une image d...
  hh:mm - day
  Appuyez pour ouvrir le gestionnaire
  de mise à jour du système

  There are a few issues there:
  - the first line/title is ellipsize but it has to, there is enough blank 
space on the right to add at least another 6 letters
  - the title doesn't have enough content to understand what the item is about

  Ideally that label would wrap so no content is lost, but it should at
  least use the space

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

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

[Touch-packages] [Bug 1328646] Re: Clock out of sync on resume from suspend

@cm-t, there is a new bug about this: bug #1365530

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

Title:
  Clock out of sync on resume from suspend

Status in The Date and Time Indicator:
  Invalid
Status in The Unity 8 shell:
  Fix Released
Status in “indicator-datetime” package in Ubuntu:
  Invalid
Status in “qmenumodel” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  Fix Released

Bug description:
  When the device is resumed by pressing the power button and the device
  is not connected over USB the clock is out of sync

  You need another system to compare the time to verify this bug report,
  and make sure both clocks are in sync.

  TEST CASE
  1. Unplug the device from its USB cable
  2. Press the power button to switch to suspend mode or wait until it goes to 
suspend
  3. Wait 2 or more minutes
  4. Press the power button again to resume the device
  5. Compare the time on the greeter and indicator with the time on the other 
system

  EXPECTED RESULT
  Clocks are in sync

  ACTUAL RESULT
  Time on the device is behind by several minutes. 

  The use case are people who use their device as a watch. You usually
  resume it, check the time, suspend it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity8 7.88+14.10.20140606-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.3-0ubuntu1
  Architecture: armhf
  Date: Tue Jun 10 19:11:42 2014
  InstallationDate: Installed on 2014-06-10 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140610)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1367551] Re: [MIR] capnproto

2014-09-10 Thread Matthias Klose

this is not a complete MIR. Please follow
https://wiki.ubuntu.com/MainInclusionProcess

at least a symbols file is missing

** Changed in: capnproto (Ubuntu)
   Status: New = Incomplete

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

Title:
  [MIR] capnproto

Status in “capnproto” package in Ubuntu:
  Incomplete

Bug description:
  Can we please include this in main? unity-scopes-api has a dependency
  on capnproto.

  Source and bug tracking for this are here:
  https://github.com/kentonv/capnproto

  There are no dependencies other than C++ 11 (gcc 4.7 or later work).

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

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

[Touch-packages] [Bug 1367623] Re: Titles should wrap in the notification menu/indicator

Components, of course...

** Package changed: ubuntu-system-settings (Ubuntu) = ubuntu-settings-
components (Ubuntu)

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

Title:
  Titles should wrap in the notification menu/indicator

Status in Ubuntu UX bugs:
  New
Status in “ubuntu-settings-components” package in Ubuntu:
  Confirmed
Status in “unity8” package in Ubuntu:
  Invalid

Bug description:
  Using rtm 26 on krillin, system updates are listed in the
  notification (indicator-message) menu, in french they show as

  Il existe une image d...
  hh:mm - day
  Appuyez pour ouvrir le gestionnaire
  de mise à jour du système

  There are a few issues there:
  - the first line/title is ellipsize but it has to, there is enough blank 
space on the right to add at least another 6 letters
  - the title doesn't have enough content to understand what the item is about

  Ideally that label would wrap so no content is lost, but it should at
  least use the space

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

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

[Touch-packages] [Bug 1367636] [NEW] Network connection breaks down regularly

2014-09-10 Thread Wolf Rogner

Public bug reported:

Using WiFi on all my notebooks the network connection terminates at
random (no signal, no connection).

Reconnecting to the AP does not work (connection efforts take
endlessly).

Disabling and Re-enabling Wireless Network works immediately.

This used to be an issue on a Macbook Pro Retina 15 at first, later the
MBPR13 had the same issue and finally my old HP 8510w does the same.

No regular events in the neighborhood (APs comming up or going down) or
in PC workload.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: network-manager 0.9.8.8-0ubuntu7
ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
Uname: Linux 3.13.0-36-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 2.14.1-0ubuntu3.4
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Sep 10 10:37:33 2014
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2013-05-17 (480 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64+mac (20130424)
IpRoute:
 default via 10.1.0.254 dev wlan0  proto static 
 10.0.0.0/8 dev wlan0  proto kernel  scope link  src 10.1.0.103  metric 9 
 192.168.97.0/24 dev vmnet8  proto kernel  scope link  src 192.168.97.1 
 192.168.204.0/24 dev vmnet1  proto kernel  scope link  src 192.168.204.1
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to trusty on 2014-04-20 (143 days ago)
nmcli-dev:
 DEVICE TYPE  STATE DBUS-PATH   
   
 wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   WIFI  
 WWAN-HARDWARE   WWAN  
 running 0.9.8.8connected   enabled   enabled 
enabledenabled enabled

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

Title:
  Network connection breaks down regularly

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

Bug description:
  Using WiFi on all my notebooks the network connection terminates at
  random (no signal, no connection).

  Reconnecting to the AP does not work (connection efforts take
  endlessly).

  Disabling and Re-enabling Wireless Network works immediately.

  This used to be an issue on a Macbook Pro Retina 15 at first, later
  the MBPR13 had the same issue and finally my old HP 8510w does the
  same.

  No regular events in the neighborhood (APs comming up or going down)
  or in PC workload.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Sep 10 10:37:33 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-05-17 (480 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64+mac 
(20130424)
  IpRoute:
   default via 10.1.0.254 dev wlan0  proto static 
   10.0.0.0/8 dev wlan0  proto kernel  scope link  src 10.1.0.103  metric 9 
   192.168.97.0/24 dev vmnet8  proto kernel  scope link  src 192.168.97.1 
   192.168.204.0/24 dev vmnet1  proto kernel  scope link  src 192.168.204.1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to trusty on 2014-04-20 (143 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled enabled

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

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

[Touch-packages] [Bug 1367551] Re: [MIR] capnproto

2014-09-10 Thread Michi Henning

I had a look at the requirements, but they don't mention anything about
a symbols file. What do I need to do here?

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

Title:
  [MIR] capnproto

Status in “capnproto” package in Ubuntu:
  Incomplete

Bug description:
  Can we please include this in main? unity-scopes-api has a dependency
  on capnproto.

  Source and bug tracking for this are here:
  https://github.com/kentonv/capnproto

  There are no dependencies other than C++ 11 (gcc 4.7 or later work).

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

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

[Touch-packages] [Bug 1360582] Re: Can't manually install clicks Signature verification error since #205

** Branch linked: lp:~mvo/phablet-tools/pkcon-allow-untrusted

** Changed in: phablet-tools (Ubuntu)
   Status: Confirmed = Fix Committed

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

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

Title:
  Can't manually install clicks Signature verification error since
  #205

Status in PackageKit:
  Confirmed
Status in “click” package in Ubuntu:
  Fix Released
Status in “phablet-tools” package in Ubuntu:
  Fix Committed
Status in “qtcreator-plugin-ubuntu” package in Ubuntu:
  Fix Released

Bug description:
  See mailing list thread at https://lists.launchpad.net/ubuntu-
  phone/msg09607.html

  Since image #205 I can't install click packages using click-buddy 
  pkcon install-local. Changed click-buddy to use  adb $ADBOPTS shell
  click install --user=$DEVICE_USER --allow-unauthenticated /tmp/$click
  which worked for me, but dunno if that's the right thing to do.

  alan@deep-thought:~/phablet/code/coreapps⟫ adb push 
com.ubuntu.music_1.3.597_all.click /tmp
  2560 KB/s (401406 bytes in 0.153s)

  alan@deep-thought:~/phablet/code/coreapps⟫ phablet-shell
  start: Job is already running: ssh
  /home/alan/.ssh/known_hosts updated.
  Original contents retained as /home/alan/.ssh/known_hosts.old
  9 KB/s (399 bytes in 0.040s)
  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 Aug 22 23:53:19 2014 from localhost.localdomain
  phablet@ubuntu-phablet:~$ pkcon install-local 
/tmp/com.ubuntu.music_1.3.597_all.click 
  Installing files  [=] 
  Finished  [=] 
  Installing files  [=] 
  Waiting for authentication[=] 
  Starting  [=] 
  Finished  [=] 
  Fatal error: /tmp/com.ubuntu.music_1.3.597_all.click failed to install.
  Cannot install /tmp/com.ubuntu.music_1.3.597_all.click: Signature 
verification error: debsig: Origin Signature check failed. This deb might not 
be signed.

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

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

[Touch-packages] [Bug 1332828] Re: Cannot upload photos to G+

2014-09-10 Thread David Barth

** Branch linked: lp:~dbarth/webapps-core/googleplus

** Branch unlinked: lp:~michael-sheldon/click-webapps/file-upload

** Changed in: webapps-core
   Status: Confirmed = In Progress

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

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

Title:
  Cannot upload photos to G+

Status in The Webapps-core project:
  In Progress
Status in “webbrowser-app” package in Ubuntu:
  Invalid

Bug description:
  I can upload photos to facebook and twitter but cannot upload to G+
  using image #91 on mako.

  I get an error.  Sorry, there aren't currently any apps installed
  that can provide this type of content.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: webbrowser-app 0.23+14.10.20140618.3-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.3-0ubuntu2
  Architecture: armhf
  Date: Sat Jun 21 15:28:24 2014
  InstallationDate: Installed on 2014-06-20 (1 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140620.1)
  SourcePackage: webbrowser-app
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/webapps-core/+bug/1332828/+subscriptions

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

[Touch-packages] [Bug 1184262] Re: times out too early, stuck in PrepareForSleep, causing network and other services to not resume

2014-09-10 Thread madmin314

** Information type changed from Public to Public Security

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

Title:
  times out too early, stuck in PrepareForSleep, causing network and
  other services to not resume

Status in “systemd” package in Ubuntu:
  Invalid
Status in “systemd-shim” package in Ubuntu:
  Fix Released
Status in “systemd” source package in Saucy:
  Invalid
Status in “systemd-shim” source package in Saucy:
  Fix Released
Status in “systemd” source package in Trusty:
  Invalid
Status in “systemd-shim” source package in Trusty:
  Fix Released

Bug description:
  After a suspend/resume, network-manager claimed that wireless was not
  available and would not let me reconnect to the wireless here.
  'iwlist wlan1 scan' would also not work; so thinking that it was a
  driver problem, I rebooted the system.  When it came back up, nm-
  applet in lightdm claimed that networking was disabled, and the option
  to enable it was greyed out.  It could also not be enabled by nmcli.
  I ended up stopping network-manager, bringing up the interface via
  /etc/network/interfaces, and logging in... at which point, restarting
  network-manager *did* let me enable networking from my logged-in
  session.

  So there are several problems here:
   - after a reboot, network-manager claimed networking was disabled.
   - nm-applet is not letting me enable networking from the lightdm session.
   - the networking was failing after a suspend/resume cycle, and could not be 
enabled even from inside the user session.

  The last issue probably *was* a kernel driver problem; but the first
  two issues are network-manager problems of some kind.

  SRU INFORMATION:
  
  Reproducer:
  - Force suspend to take very long by adding a sleep:
    echo -e '#!/bin/sh\nsleep 15\nexit 1' | sudo tee 
/usr/lib/pm-utils/sleep.d/00break
    (this will also make suspend fail, which eases testing)
  - Suspend from the menu or with
    sudo gdbus call -y -d org.freedesktop.login1 -o /org/freedesktop/login1 -m 
org.freedesktop.login1.Manager.Suspend true
  - With the 13.10 final version, systemd-shim will (often) time out, and the 
next Suspend call from above will fail with Operation already in progress and 
the network does not come back up. With the fixed version, network should be 
back up and the Suspend() call can be issued many times.

  Fix:
https://github.com/desrt/systemd-shim/commit/136ed1143077d13c2
https://github.com/desrt/systemd-shim/commit/16a7fdc0652ad78f4

  Regression potential: Errors in this code could potentially break
  suspend/shutdown completely, so for verification both of these
  functionalities ought to be tested on real hardware.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: network-manager 0.9.8.0-0ubuntu8
  ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3
  Uname: Linux 3.9.0-2-generic x86_64
  ApportVersion: 2.10.2-0ubuntu1
  Architecture: amd64
  Date: Sat May 25 21:38:31 2013
  InstallationDate: Installed on 2010-09-24 (974 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 
(20100816.1)
  IpRoute:
   default via 192.168.1.1 dev wlan1
   10.0.3.0/24 dev lxcbr0  proto kernel  scope link  src 10.0.3.1
   169.254.0.0/16 dev wlan1  scope link  metric 1000
   192.168.1.0/24 dev wlan1  proto kernel  scope link  src 192.168.1.106
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=false
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to saucy on 2013-05-06 (19 days ago)
  WifiSyslog:

  nmcli-con:
   Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9:
   ** (process:11977): WARNING **: Could not initialize NMClient 
/org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was 
not provided by any .service files
   Error: nmcli (0.9.8.0) and NetworkManager (unknown) versions don't match. 
Force execution using --nocheck, but the results are unpredictable.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN
   not running unknownunknown unknown   unknown 
unknownunknown unknown

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

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

[Touch-packages] [Bug 1363314] Re: App fails to launch on up-to-date utopic desktop

2014-09-10 Thread Thomas Strehl

** Changed in: thumbnailer
   Status: In Progress = Invalid

** Changed in: thumbnailer
 Assignee: Jussi Pakkanen (jpakkane) = (unassigned)

** Changed in: qtmultimedia-opensource-src (Ubuntu)
 Assignee: (unassigned) = Jim Hodapp (jhodapp)

** Changed in: thumbnailer
   Importance: Critical = Undecided

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

Title:
  App fails to launch on up-to-date utopic desktop

Status in Dropping Letters:
  Invalid
Status in Music application for Ubuntu devices:
  Invalid
Status in Thumbnail generator for all kinds of files:
  Invalid
Status in Clock application for Ubuntu devices:
  Invalid
Status in “qtmultimedia-opensource-src” package in Ubuntu:
  New
Status in “thumbnailer” package in Ubuntu:
  Fix Released

Bug description:
  Seems for a few days some of the core apps which use qtmultimedia now
  fail to start on the desktop with output like this:-

  ⟫ qmlscene music-app.qml
  unity::action::ActionManager::ActionManager(QObject*):
  Could not determine application identifier. HUD will not work 
properly.
  Provide your application identifier in $APP_ID environment variable.

  (qmlscene:25234): GLib-GObject-WARNING **: cannot register existing
  type 'GstFormat'

  (qmlscene:25234): GLib-CRITICAL **: g_once_init_leave: assertion
  'result != 0' failed

  (qmlscene:25234): GLib-GObject-WARNING **: cannot retrieve class for
  invalid (unclassed) type 'invalid'

  (qmlscene:25234): GLib-GObject-WARNING **: cannot register existing
  type 'GstQuery'

  (qmlscene:25234): GLib-CRITICAL **: g_once_init_leave: assertion
  'result != 0' failed

  (qmlscene:25234): GLib-GObject-WARNING **: cannot retrieve class for
  invalid (unclassed) type 'invalid'

  (qmlscene:25234): GLib-GObject-WARNING **: cannot register existing
  type 'GstObject'

  (qmlscene:25234): GLib-CRITICAL **: g_once_init_leave: assertion
  'result != 0' failed

  (qmlscene:25234): GLib-GObject-WARNING **: cannot retrieve class for
  invalid (unclassed) type 'invalid'

  
  Attached is the strace output as foo.txt

  A simple sample app which reproduces the issue can be seen at
  https://code.launchpad.net/~andrew-hayzen/+junk/test-mediaplayer-app

  Also affected include core apps which use Audio {} such as Clock and
  Dropping Letters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dropping-letters/+bug/1363314/+subscriptions

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

[Touch-packages] [Bug 1184262] Re: times out too early, stuck in PrepareForSleep, causing network and other services to not resume

2014-09-10 Thread Christopher M. Penalver

** Information type changed from Public Security to Public

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

Title:
  times out too early, stuck in PrepareForSleep, causing network and
  other services to not resume

Status in “systemd” package in Ubuntu:
  Invalid
Status in “systemd-shim” package in Ubuntu:
  Fix Released
Status in “systemd” source package in Saucy:
  Invalid
Status in “systemd-shim” source package in Saucy:
  Fix Released
Status in “systemd” source package in Trusty:
  Invalid
Status in “systemd-shim” source package in Trusty:
  Fix Released

Bug description:
  After a suspend/resume, network-manager claimed that wireless was not
  available and would not let me reconnect to the wireless here.
  'iwlist wlan1 scan' would also not work; so thinking that it was a
  driver problem, I rebooted the system.  When it came back up, nm-
  applet in lightdm claimed that networking was disabled, and the option
  to enable it was greyed out.  It could also not be enabled by nmcli.
  I ended up stopping network-manager, bringing up the interface via
  /etc/network/interfaces, and logging in... at which point, restarting
  network-manager *did* let me enable networking from my logged-in
  session.

  So there are several problems here:
   - after a reboot, network-manager claimed networking was disabled.
   - nm-applet is not letting me enable networking from the lightdm session.
   - the networking was failing after a suspend/resume cycle, and could not be 
enabled even from inside the user session.

  The last issue probably *was* a kernel driver problem; but the first
  two issues are network-manager problems of some kind.

  SRU INFORMATION:
  
  Reproducer:
  - Force suspend to take very long by adding a sleep:
    echo -e '#!/bin/sh\nsleep 15\nexit 1' | sudo tee 
/usr/lib/pm-utils/sleep.d/00break
    (this will also make suspend fail, which eases testing)
  - Suspend from the menu or with
    sudo gdbus call -y -d org.freedesktop.login1 -o /org/freedesktop/login1 -m 
org.freedesktop.login1.Manager.Suspend true
  - With the 13.10 final version, systemd-shim will (often) time out, and the 
next Suspend call from above will fail with Operation already in progress and 
the network does not come back up. With the fixed version, network should be 
back up and the Suspend() call can be issued many times.

  Fix:
https://github.com/desrt/systemd-shim/commit/136ed1143077d13c2
https://github.com/desrt/systemd-shim/commit/16a7fdc0652ad78f4

  Regression potential: Errors in this code could potentially break
  suspend/shutdown completely, so for verification both of these
  functionalities ought to be tested on real hardware.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: network-manager 0.9.8.0-0ubuntu8
  ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3
  Uname: Linux 3.9.0-2-generic x86_64
  ApportVersion: 2.10.2-0ubuntu1
  Architecture: amd64
  Date: Sat May 25 21:38:31 2013
  InstallationDate: Installed on 2010-09-24 (974 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 
(20100816.1)
  IpRoute:
   default via 192.168.1.1 dev wlan1
   10.0.3.0/24 dev lxcbr0  proto kernel  scope link  src 10.0.3.1
   169.254.0.0/16 dev wlan1  scope link  metric 1000
   192.168.1.0/24 dev wlan1  proto kernel  scope link  src 192.168.1.106
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=false
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to saucy on 2013-05-06 (19 days ago)
  WifiSyslog:

  nmcli-con:
   Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9:
   ** (process:11977): WARNING **: Could not initialize NMClient 
/org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was 
not provided by any .service files
   Error: nmcli (0.9.8.0) and NetworkManager (unknown) versions don't match. 
Force execution using --nocheck, but the results are unpredictable.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN
   not running unknownunknown unknown   unknown 
unknownunknown unknown

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

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

[Touch-packages] [Bug 1367683] [NEW] Allow disabling phone lock after enabling developer mode

2014-09-10 Thread Michael Zanetti

Public bug reported:

Using a dedicated device for developing on Ubuntu Touch which doesn't
ever leave the room and has no sensitive data on it, it would be great
to have a way of accessing adb but still not being required to enter the
device pin lock every time one wants to test something. This is really
just a waste of time not adding any value from a security point of view.
On such configuration's people will set the pin to something like 
anyways so I think we should spare them the effort of entering the
pinlock every time the Greeter is swiped away.

** Affects: lxc-android-config (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Allow disabling phone lock after enabling developer mode

Status in “lxc-android-config” package in Ubuntu:
  New

Bug description:
  Using a dedicated device for developing on Ubuntu Touch which doesn't
  ever leave the room and has no sensitive data on it, it would be great
  to have a way of accessing adb but still not being required to enter
  the device pin lock every time one wants to test something. This is
  really just a waste of time not adding any value from a security point
  of view. On such configuration's people will set the pin to something
  like  anyways so I think we should spare them the effort of
  entering the pinlock every time the Greeter is swiped away.

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

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

[Touch-packages] [Bug 1367028] Re: [MIR] system-image

2014-09-10 Thread Colin Watson

See bug 1349832 (especially https://bugs.launchpad.net/ubuntu/+source
/python-pip/+bug/1349832/comments/11).

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

Title:
  [MIR] system-image

Status in “system-image” package in Ubuntu:
  New

Bug description:
  Availability: universe

  Rationale: system-image is the client for image based upgrades.  It is
  a core component and thus seeded in Ubuntu Touch.

  Security: No known issues.

  QA: Well supported upstream and in Ubuntu.  Package has build-time
  unittests and DEP-8 tests.

  UI standards: n/a

  Dependencies: All non-main build- and run-time dependencies already or
  will soon have MIRs.

  Standards compliance: No known issues.

  Maintenance: No known issues.

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

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

[Touch-packages] [Bug 1367028] Re: [MIR] system-image

2014-09-10 Thread Matthias Klose

the blocker here is
https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1349832
the build dependencies on python-pip and python-virtualenv.

I'd like to delay that for 15.04 and try to find a solution for not
promoting these as well.

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

Title:
  [MIR] system-image

Status in “system-image” package in Ubuntu:
  New

Bug description:
  Availability: universe

  Rationale: system-image is the client for image based upgrades.  It is
  a core component and thus seeded in Ubuntu Touch.

  Security: No known issues.

  QA: Well supported upstream and in Ubuntu.  Package has build-time
  unittests and DEP-8 tests.

  UI standards: n/a

  Dependencies: All non-main build- and run-time dependencies already or
  will soon have MIRs.

  Standards compliance: No known issues.

  Maintenance: No known issues.

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

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

[Touch-packages] [Bug 1235567] Re: ibus-ui-gtk3 crashed with SIGABRT

2014-09-10 Thread Alberto Salvia Novella

@ Laura Czajkowski:

If in the future you see that a bug is affecting a particular release,
you only have to add its name to the tag list.

Thank you :-)

** Tags added: utopic

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

Title:
  ibus-ui-gtk3 crashed with SIGABRT

Status in IBus:
  New
Status in “ibus” package in Ubuntu:
  Confirmed

Bug description:
  Restarted system after installing updates was greeting me with that
  message

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: ibus 1.5.3-6ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Sat Oct  5 08:17:10 2013
  Disassembly: = 0x7f62f38f4f77:   Cannot access memory at address 
0x7f62f38f4f77
  ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3
  InstallationDate: Installed on 2013-06-12 (114 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: ibus-ui-gtk3 crashed with SIGABRT
  UpgradeStatus: Upgraded to saucy on 2013-08-11 (55 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1184262] Re: times out too early, stuck in PrepareForSleep, causing network and other services to not resume

2014-09-10 Thread Alberto Salvia Novella

@ madmin314:

If you are sure this is a security bug, please:

 1. Explain why do you think so.
 2. Mark it as Public Security again.

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

Title:
  times out too early, stuck in PrepareForSleep, causing network and
  other services to not resume

Status in “systemd” package in Ubuntu:
  Invalid
Status in “systemd-shim” package in Ubuntu:
  Fix Released
Status in “systemd” source package in Saucy:
  Invalid
Status in “systemd-shim” source package in Saucy:
  Fix Released
Status in “systemd” source package in Trusty:
  Invalid
Status in “systemd-shim” source package in Trusty:
  Fix Released

Bug description:
  After a suspend/resume, network-manager claimed that wireless was not
  available and would not let me reconnect to the wireless here.
  'iwlist wlan1 scan' would also not work; so thinking that it was a
  driver problem, I rebooted the system.  When it came back up, nm-
  applet in lightdm claimed that networking was disabled, and the option
  to enable it was greyed out.  It could also not be enabled by nmcli.
  I ended up stopping network-manager, bringing up the interface via
  /etc/network/interfaces, and logging in... at which point, restarting
  network-manager *did* let me enable networking from my logged-in
  session.

  So there are several problems here:
   - after a reboot, network-manager claimed networking was disabled.
   - nm-applet is not letting me enable networking from the lightdm session.
   - the networking was failing after a suspend/resume cycle, and could not be 
enabled even from inside the user session.

  The last issue probably *was* a kernel driver problem; but the first
  two issues are network-manager problems of some kind.

  SRU INFORMATION:
  
  Reproducer:
  - Force suspend to take very long by adding a sleep:
    echo -e '#!/bin/sh\nsleep 15\nexit 1' | sudo tee 
/usr/lib/pm-utils/sleep.d/00break
    (this will also make suspend fail, which eases testing)
  - Suspend from the menu or with
    sudo gdbus call -y -d org.freedesktop.login1 -o /org/freedesktop/login1 -m 
org.freedesktop.login1.Manager.Suspend true
  - With the 13.10 final version, systemd-shim will (often) time out, and the 
next Suspend call from above will fail with Operation already in progress and 
the network does not come back up. With the fixed version, network should be 
back up and the Suspend() call can be issued many times.

  Fix:
https://github.com/desrt/systemd-shim/commit/136ed1143077d13c2
https://github.com/desrt/systemd-shim/commit/16a7fdc0652ad78f4

  Regression potential: Errors in this code could potentially break
  suspend/shutdown completely, so for verification both of these
  functionalities ought to be tested on real hardware.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: network-manager 0.9.8.0-0ubuntu8
  ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3
  Uname: Linux 3.9.0-2-generic x86_64
  ApportVersion: 2.10.2-0ubuntu1
  Architecture: amd64
  Date: Sat May 25 21:38:31 2013
  InstallationDate: Installed on 2010-09-24 (974 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 
(20100816.1)
  IpRoute:
   default via 192.168.1.1 dev wlan1
   10.0.3.0/24 dev lxcbr0  proto kernel  scope link  src 10.0.3.1
   169.254.0.0/16 dev wlan1  scope link  metric 1000
   192.168.1.0/24 dev wlan1  proto kernel  scope link  src 192.168.1.106
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=false
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to saucy on 2013-05-06 (19 days ago)
  WifiSyslog:

  nmcli-con:
   Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9:
   ** (process:11977): WARNING **: Could not initialize NMClient 
/org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was 
not provided by any .service files
   Error: nmcli (0.9.8.0) and NetworkManager (unknown) versions don't match. 
Force execution using --nocheck, but the results are unpredictable.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN
   not running unknownunknown unknown   unknown 
unknownunknown unknown

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

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

[Touch-packages] [Bug 1362518] Re: Badge missing from System Settings icon when update is available

Ah missed the Dash part, indeed it's not there in the dash, it was
never confirmed that we want them in there.

** Changed in: unity8 (Ubuntu)
   Status: Triaged = Fix Released

** Changed in: unity8 (Ubuntu)
   Status: Fix Released = Triaged

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

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

** Summary changed:

- Badge missing from System Settings icon when update is available
+ Badge missing from System Settings icon on dash when update is available

** Description changed:

  Ubuntu 14.10 r203
  
  1. Wait until software updates are available.
- 2. Look at the System Settings icon, in the Dash or Launcher.
+ 2. Look at the System Settings icon in the Dash.
  
  What you see: It appears as normal.
  
  What you should see: Wherever the System Settings icon appears, it
  should have a badge with the number of updates available.
  https://wiki.ubuntu.com/SoftwareUpdates#Prompting

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

Title:
  Badge missing from System Settings icon on dash when update is
  available

Status in Ubuntu UX bugs:
  New
Status in “unity8” package in Ubuntu:
  New

Bug description:
  Ubuntu 14.10 r203

  1. Wait until software updates are available.
  2. Look at the System Settings icon in the Dash.

  What you see: It appears as normal.

  What you should see: Wherever the System Settings icon appears, it
  should have a badge with the number of updates available.
  https://wiki.ubuntu.com/SoftwareUpdates#Prompting

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

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

[Touch-packages] [Bug 1234616] Re: [Messaging menu] When the passcode is on/set I shouldn't be able to reply to text messages

2014-09-10 Thread Olga Kemmet

** Changed in: ubuntu-ux
 Assignee: Christina Li (christina-li) = Olga Kemmet (olga-kemmet)

** 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 messaging-app in Ubuntu.
https://bugs.launchpad.net/bugs/1234616

Title:
  [Messaging menu] When the passcode is on/set I shouldn't be able to
  reply to text messages

Status in The Messaging Menu:
  Opinion
Status in Messaging App:
  Opinion
Status in Ubuntu UX bugs:
  Fix Released
Status in The Unity 8 shell:
  Fix Released
Status in “messaging-app” package in Ubuntu:
  Opinion
Status in “unity8” package in Ubuntu:
  Fix Released

Bug description:
  Current situation:
  When the passcode is on/set, I shouldn't be able to reply to my text messages 
as my phone is considered lock.

  Steps to reproduce:
  1. Text message received
  2. Messaging menu via indicators
  3. Tap to expand a missed message
  4. Text box appeared, start typing message
  5. Send

  Desired solution:
  when the passcode is on/set, the user should only be able to view the missed 
messages. Tapping on a message should take me to the passcode screen and after 
keying the PIN, it should take the user directly to the messaging thread in the 
messaging app.

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

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

[Touch-packages] [Bug 1365336] Re: Lightdm update=No desktop

This bug was fixed in the package fglrx-installer-updates -
2:14.201-0ubuntu1

---
fglrx-installer-updates (2:14.201-0ubuntu1) utopic; urgency=medium

  * New upstream release.
  * debian/control.in, debian/com.ubuntu.amdcccle.pkexec.policy:
- Make amdcccle depend on polkit-1.
- Use pkexec for amdcccle when running Unity.
  * debian/dkms.conf.in:
- Drop all the patches.
  * debian/substvars:
- Add support for xorg-video-abi-18 (LP: #1359769).
  * debian/71-fglrx.rules:
- Tag the device for logind (LP: #1365336).
 -- Alberto Milone alberto.mil...@canonical.com   Tue, 09 Sep 2014 18:00:48 
+0200

** Changed in: fglrx-installer-updates (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 lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1365336

Title:
  Lightdm update=No desktop

Status in “fglrx-installer” package in Ubuntu:
  Fix Released
Status in “fglrx-installer-updates” package in Ubuntu:
  Fix Released
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-304” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  Fix Released
Status in “xserver-xorg-video-vesa” package in Ubuntu:
  Confirmed
Status in “xserver-xorg-video-vmware” package in Ubuntu:
  Confirmed

Bug description:
  Update to lightdm from 1.11.7-0ubuntu1 to 1.11.8-0ubuntu1 leaves me
  with no desktop on normal boot.

  Machine boots directly to tty1.

  Logged in at tty1 and then startx leads to a desktop that requires
  password to start properly and with themes unapplied.

  Password required to reboot machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: lightdm 1.11.8-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1
  Uname: Linux 3.16.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Sep  4 08:20:14 2014
  InstallationDate: Installed on 2014-07-17 (48 days ago)
  InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140717)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1237496] Re: signon-ui fails to start in Ubuntu Touch

2014-09-10 Thread David Barth

The problem has been fixed and signon-ui works properly with Mir on the
phone now.

** Changed in: signon-ui
   Status: Triaged = Fix Released

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

Title:
  signon-ui fails to start in Ubuntu Touch

Status in Online Accounts: Sign-on UI:
  Fix Released
Status in Unity Mir:
  Fix Released
Status in “unity-mir” package in Ubuntu:
  Fix Released

Bug description:
  Using Ubuntu Touch image 20131009.1, with Mir and write permissions.

  phablet@ubuntu-phablet:~$ export SSOUI_LOGGING_LEVEL=2
  phablet@ubuntu-phablet:~$  export SSOUI_DAEMON_TIMEOUT=3000
  phablet@ubuntu-phablet:~$ signon-ui 
  __pthread_gettid -2
  terminate called after throwing an instance of 'std::system_error'
what():  Operation not permitted
  Aborted (core dumped)

To manage notifications about this bug go to:
https://bugs.launchpad.net/signon-ui/+bug/1237496/+subscriptions

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

[Touch-packages] [Bug 1365336] Re: Lightdm update=No desktop

This bug was fixed in the package fglrx-installer - 2:14.201-0ubuntu1

---
fglrx-installer (2:14.201-0ubuntu1) utopic; urgency=medium

  * New upstream release.
  * debian/control.in, debian/com.ubuntu.amdcccle.pkexec.policy:
- Make amdcccle depend on polkit-1.
- Use pkexec for amdcccle when running Unity.
  * debian/dkms.conf.in:
- Drop all the patches.
  * debian/substvars:
- Add support for xorg-video-abi-18 (LP: #1359769).
  * debian/71-fglrx.rules:
- Tag the device for logind (LP: #1365336).
 -- Alberto Milone alberto.mil...@canonical.com   Tue, 09 Sep 2014 17:48:30 
+0200

** Changed in: fglrx-installer (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 lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1365336

Title:
  Lightdm update=No desktop

Status in “fglrx-installer” package in Ubuntu:
  Fix Released
Status in “fglrx-installer-updates” package in Ubuntu:
  Fix Released
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-304” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  Fix Released
Status in “xserver-xorg-video-vesa” package in Ubuntu:
  Confirmed
Status in “xserver-xorg-video-vmware” package in Ubuntu:
  Confirmed

Bug description:
  Update to lightdm from 1.11.7-0ubuntu1 to 1.11.8-0ubuntu1 leaves me
  with no desktop on normal boot.

  Machine boots directly to tty1.

  Logged in at tty1 and then startx leads to a desktop that requires
  password to start properly and with themes unapplied.

  Password required to reboot machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: lightdm 1.11.8-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1
  Uname: Linux 3.16.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Sep  4 08:20:14 2014
  InstallationDate: Installed on 2014-07-17 (48 days ago)
  InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140717)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1367696] [NEW] spinning Ubuntu logo on update boot feels cheesy

Public bug reported:

There is a large spinning Ubuntu logo during updates and a small spinning 
Ubuntu logo during the boot process.  I think there are two problems with this:
- whatever the progress indicator is should be consistent (not one large and 
one small), 
- more importantly, this progress indicator feels cheap and off brand to me.  
The desktop has the word Ubuntu with dots which change colour to indicate 
progress.  That feels classier to me. Is there a specific reason we have 
diverged from an existing (and excellent) solution?  Isn't this unnecessary 
divergence for the phone?

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


** Tags: avengers

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

Title:
  spinning Ubuntu logo on update  boot feels cheesy

Status in “unity8” package in Ubuntu:
  New

Bug description:
  There is a large spinning Ubuntu logo during updates and a small spinning 
Ubuntu logo during the boot process.  I think there are two problems with this:
  - whatever the progress indicator is should be consistent (not one large and 
one small), 
  - more importantly, this progress indicator feels cheap and off brand to me.  
The desktop has the word Ubuntu with dots which change colour to indicate 
progress.  That feels classier to me. Is there a specific reason we have 
diverged from an existing (and excellent) solution?  Isn't this unnecessary 
divergence for the phone?

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

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

[Touch-packages] [Bug 1367700] Re: text field for PIN code displays dots before typing

This is in reference to the PIN entry through the Settings menu, not the
PIN entry to unlock the phone.

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

Title:
  text field for PIN code displays dots before typing

Status in “unity8” package in Ubuntu:
  New

Bug description:
  When changing a PIN code (and perhaps when entering it for the first
  time), the text fields are pre-populated with 4 dots.  I suspect this
  is planned as a way to indicate that the user should type there
  (although I question whether that hint is necessary).  However, when
  you do type in that field, the dots stay the same.

  Expected behaviour:
  - I think the expected behavior is that the field is blank until you type, 
then dots appear according to the number of characters you type
  - (as a fallback, there could lighter ghost dots there that get replaced 
with darker dots as you type but this seems like a less desirable solution to 
me)

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

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

[Touch-packages] [Bug 1367700] [NEW] text field for PIN code displays dots before typing

Public bug reported:

When changing a PIN code (and perhaps when entering it for the first
time), the text fields are pre-populated with 4 dots.  I suspect this is
planned as a way to indicate that the user should type there (although I
question whether that hint is necessary).  However, when you do type in
that field, the dots stay the same.

Expected behaviour:
- I think the expected behavior is that the field is blank until you type, then 
dots appear according to the number of characters you type
- (as a fallback, there could lighter ghost dots there that get replaced with 
darker dots as you type but this seems like a less desirable solution to me)

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

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

Title:
  text field for PIN code displays dots before typing

Status in “unity8” package in Ubuntu:
  New

Bug description:
  When changing a PIN code (and perhaps when entering it for the first
  time), the text fields are pre-populated with 4 dots.  I suspect this
  is planned as a way to indicate that the user should type there
  (although I question whether that hint is necessary).  However, when
  you do type in that field, the dots stay the same.

  Expected behaviour:
  - I think the expected behavior is that the field is blank until you type, 
then dots appear according to the number of characters you type
  - (as a fallback, there could lighter ghost dots there that get replaced 
with darker dots as you type but this seems like a less desirable solution to 
me)

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

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

[Touch-packages] [Bug 1319726] Re: In pixman_region32_init_rect: Invalid rectangle passed

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

Title:
  In pixman_region32_init_rect: Invalid rectangle passed

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

Bug description:
  per***@A***oda:~$ /usr/lib/unity/unity-panel-service --lockscreen-mode
  *** BUG ***
  In pixman_region32_init_rect: Invalid rectangle passed
  Set a breakpoint on '_pixman_log_error' to debug

  *** BUG ***
  In pixman_region32_init_rect: Invalid rectangle passed
  Set a breakpoint on '_pixman_log_error' to debug

  *** BUG ***
  In pixman_region32_init_rect: Invalid rectangle passed
  Set a breakpoint on '_pixman_log_error' to debug

  *** BUG ***
  In pixman_region32_init_rect: Invalid rectangle passed
  Set a breakpoint on '_pixman_log_error' to debug

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-services 7.2.0+14.04.20140423-0ubuntu1.2 [modified: 
usr/lib/unity/unity-panel-service]
  ProcVersionSignature: Ubuntu 3.13.0-26.48-generic 3.13.11
  Uname: Linux 3.13.0-26-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu May 15 11:12:44 2014
  DistUpgraded: 2014-04-21 23:59:37,219 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 82G33/G31 Express Integrated Graphics Controller 
[8086:29c2] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Device [8086:5044]
  InstallationDate: Installed on 2013-02-15 (453 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-26-generic 
root=UUID=9e112b4e-2332-4bfd-850d-b576848ee2fa ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-04-21 (23 days ago)
  dmi.bios.date: 10/02/2007
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: DPP3510J.86A.0293.2007.1002.1519
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DG33BU
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAD79951-407
  dmi.chassis.type: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrDPP3510J.86A.0293.2007.1002.1519:bd10/02/2007:svn:pn:pvr:rvnIntelCorporation:rnDG33BU:rvrAAD79951-407:cvn:ct2:cvr:
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  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.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue May 13 13:05:53 2014
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputSleep Button KEYBOARD, id 7
   inputLogitech USB Optical Mouse MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   22235 
   vendor GSM
  xserver.version: 2:1.15.1-0ubuntu2

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

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

[Touch-packages] [Bug 1364647] Re: Alarm, Calls should always be played (also) in the speakerphone even when a bluetooth or wired headset is used

2014-09-10 Thread Treviño

** Tags added: rtm14

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

Title:
  Alarm, Calls should always be played (also) in the speakerphone even
  when a bluetooth or wired headset is used

Status in Dialer app for Ubuntu Touch:
  New
Status in Clock application for Ubuntu devices:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in “dialer-app” package in Ubuntu:
  New

Bug description:
  When a bluetooth or wired headset the phone embedded speakerphone
  should ring anyway as you probably won't wear an headset while
  sleeping, while you prefer keeping your headset connected all the
  times.

  -- SOLUTION --
  Calls and Alarms should *always* be played to the speaker phones.

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

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

[Touch-packages] [Bug 1367707] [NEW] poor text in prompt to user

Public bug reported:

Upon starting camera app, given message prompt of
com.ubuntu.camera_camera  com.ubuntu.camera_camera_3.0.0.387 wants to
access your current location

Expected behaviour? User friendly language and app name, not process
name.

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


** Tags: avengers

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

Title:
  poor text in prompt to user

Status in “camera-app” package in Ubuntu:
  New

Bug description:
  Upon starting camera app, given message prompt of
  com.ubuntu.camera_camera  com.ubuntu.camera_camera_3.0.0.387 wants to
  access your current location

  Expected behaviour? User friendly language and app name, not process
  name.

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

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

[Touch-packages] [Bug 1365769] Re: [G41MT-S2P, VIA VT2020, Pink Mic, Rear] No sound at all

2014-09-10 Thread Gideon Walker

I do not have the hda-jack-sense-test command.

I was not aware that I was overriding the pcm.default.  Is it worth
changing this to see if the bug goes away?  How would I do that?

Do I need to build my own version of the kernel to disable jack
detection?

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

Title:
  [G41MT-S2P, VIA VT2020, Pink Mic, Rear] No sound at all

Status in “alsa-driver” package in Ubuntu:
  Incomplete

Bug description:
  The problem is that the microphone is not detected after a reboot.  As
  a result, some applications cannot get sound from the microphone.

  The Input tab of the Sound window lists no device.

  I have a workround which is to disconnect and then connect the
  microphone after I have logged in.

  Interestingly, the audacity application can access the microphone when
  the system says that the device does not exist

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-67.101-generic 3.2.60
  Uname: Linux 3.2.0-67-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tim2060 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Sep  5 00:12:39 2014
  InstallationDate: Installed on 2011-07-29 (1133 days ago)
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tim2060 F pulseaudio
  Symptom_Jack: Pink Mic, Rear
  Symptom_Type: No sound at all
  Title: [G41MT-S2P, VIA VT2020, Pink Mic, Rear] No sound at all
  UpgradeStatus: Upgraded to trusty on 2014-08-15 (20 days ago)
  dmi.bios.date: 12/31/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F1
  dmi.board.name: G41MT-S2P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd12/31/2010:svnGigabyteTechnologyCo.,Ltd.:pnG41MT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41MT-S2P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: G41MT-S2P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1367700] Re: text field for PIN code displays dots before typing

2014-09-10 Thread Michael Zanetti

** Also affects: ubuntu-system-settings
   Importance: Undecided
   Status: New

** No longer affects: ubuntu-system-settings

** Package changed: unity8 (Ubuntu) = ubuntu-system-settings (Ubuntu)

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

Title:
  text field for PIN code displays dots before typing

Status in “ubuntu-system-settings” package in Ubuntu:
  New

Bug description:
  When changing a PIN code (and perhaps when entering it for the first
  time), the text fields are pre-populated with 4 dots.  I suspect this
  is planned as a way to indicate that the user should type there
  (although I question whether that hint is necessary).  However, when
  you do type in that field, the dots stay the same.

  Expected behaviour:
  - I think the expected behavior is that the field is blank until you type, 
then dots appear according to the number of characters you type
  - (as a fallback, there could lighter ghost dots there that get replaced 
with darker dots as you type but this seems like a less desirable solution to 
me)

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

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

[Touch-packages] [Bug 1367696] Re: spinning Ubuntu logo on update boot feels cheesy

** Package changed: unity8 (Ubuntu) = unity-system-compositor (Ubuntu)

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

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

Title:
  spinning Ubuntu logo on update  boot feels cheesy

Status in Ubuntu UX bugs:
  New
Status in “unity-system-compositor” package in Ubuntu:
  New

Bug description:
  There is a large spinning Ubuntu logo during updates and a small spinning 
Ubuntu logo during the boot process.  I think there are two problems with this:
  - whatever the progress indicator is should be consistent (not one large and 
one small), 
  - more importantly, this progress indicator feels cheap and off brand to me.  
The desktop has the word Ubuntu with dots which change colour to indicate 
progress.  That feels classier to me. Is there a specific reason we have 
diverged from an existing (and excellent) solution?  Isn't this unnecessary 
divergence for the phone?

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

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

[Touch-packages] [Bug 1366332] Re: Apt-get reports NO_PUBKEY gpg error for keys that are present in trusted.gpg

2014-09-10 Thread Timo Jyrinki

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

** This bug has been marked a duplicate of bug 1263540
   Apt-get reports NO_PUBKEY gpg error for keys that are present in trusted.gpg.

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

Title:
  Apt-get reports NO_PUBKEY gpg error for keys that are present in
  trusted.gpg

Status in “apt” package in Ubuntu:
  New

Bug description:
  Ubuntu 14.04
  apt 1.0.1ubuntu2.1

  'apt-get update' has started showing several warnings like the
  following, even though the keys are present:

  W: GPG error: http://extras.ubuntu.com trusty Release: The following 
signatures couldn't be verified because the public key is not available: 
NO_PUBKEY 16126D3A3E5C1192
  W: GPG error: http://archive.canonical.com trusty Release: The following 
signatures couldn't be verified because the public key is not available: 
NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  W: GPG error: http://qgis.org trusty InRelease: The following signatures 
couldn't be verified because the public key is not available: NO_PUBKEY 
030561BEDD45F6C3
  W: GPG error: http://dl.google.com stable Release: The following signatures 
couldn't be verified because the public key is not available: NO_PUBKEY 
A040830F7FAC5991
  W: GPG error: http://dl.google.com stable Release: The following signatures 
couldn't be verified because the public key is not available: NO_PUBKEY 
A040830F7FAC5991
  W: GPG error: http://archive.ubuntu.com trusty Release: The following 
signatures couldn't be verified because the public key is not available: 
NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  W: GPG error: http://archive.ubuntu.com trusty-updates Release: The following 
signatures couldn't be verified because the public key is not available: 
NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  W: GPG error: http://archive.ubuntu.com trusty-security Release: The 
following signatures couldn't be verified because the public key is not 
available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32

  sudo apt-key clean didn't help

  The only ultimate solution was to remove all the keys from
  /etc/apt/trusted.gpg.d and run

  sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys KEY

  for each key that was missing.


  Here is a reference bug for 13.10 
  https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1263540

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

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

[Touch-packages] [Bug 1367715] [NEW] [Greeter] on N10 left edge swipe unlocks Greeter, even with pin/password set

2014-09-10 Thread Gerry Boland

Public bug reported:

Steps to repro:
1. Set a PIN or password
2. Hit power to lock device
3. Hit power
4. at Greeter, do a left-edge swipe

It unlocks the device even though I never entered the PIN/password

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

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

Title:
  [Greeter] on N10 left edge swipe unlocks Greeter, even with
  pin/password set

Status in “unity8” package in Ubuntu:
  New

Bug description:
  Steps to repro:
  1. Set a PIN or password
  2. Hit power to lock device
  3. Hit power
  4. at Greeter, do a left-edge swipe

  It unlocks the device even though I never entered the PIN/password

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

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

[Touch-packages] [Bug 1367696] Re: spinning Ubuntu logo on update boot feels cheesy

2014-09-10 Thread John Lea

** Changed in: ubuntu-ux
 Assignee: (unassigned) = Jouni Helminen (jounihelminen)

** Changed in: ubuntu-ux
   Importance: Undecided = Medium

** Changed in: ubuntu-ux
   Status: New = Triaged

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

Title:
  spinning Ubuntu logo on update  boot feels cheesy

Status in Ubuntu UX bugs:
  Triaged
Status in “unity-system-compositor” package in Ubuntu:
  New

Bug description:
  There is a large spinning Ubuntu logo during updates and a small spinning 
Ubuntu logo during the boot process.  I think there are two problems with this:
  - whatever the progress indicator is should be consistent (not one large and 
one small), 
  - more importantly, this progress indicator feels cheap and off brand to me.  
The desktop has the word Ubuntu with dots which change colour to indicate 
progress.  That feels classier to me. Is there a specific reason we have 
diverged from an existing (and excellent) solution?  Isn't this unnecessary 
divergence for the phone?

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

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

[Touch-packages] [Bug 1365336] Re: Lightdm update=No desktop

2014-09-10 Thread Elfy

@Robert Ancell - thanks - synced and booted Xubuntu image in vbox

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

Title:
  Lightdm update=No desktop

Status in “fglrx-installer” package in Ubuntu:
  Fix Released
Status in “fglrx-installer-updates” package in Ubuntu:
  Fix Released
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-304” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  Fix Released
Status in “xserver-xorg-video-vesa” package in Ubuntu:
  Confirmed
Status in “xserver-xorg-video-vmware” package in Ubuntu:
  Confirmed

Bug description:
  Update to lightdm from 1.11.7-0ubuntu1 to 1.11.8-0ubuntu1 leaves me
  with no desktop on normal boot.

  Machine boots directly to tty1.

  Logged in at tty1 and then startx leads to a desktop that requires
  password to start properly and with themes unapplied.

  Password required to reboot machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: lightdm 1.11.8-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1
  Uname: Linux 3.16.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Sep  4 08:20:14 2014
  InstallationDate: Installed on 2014-07-17 (48 days ago)
  InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140717)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1363314] Re: App fails to launch on up-to-date utopic desktop

2014-09-10 Thread Thomas Strehl

** No longer affects: thumbnailer

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

Title:
  App fails to launch on up-to-date utopic desktop

Status in Dropping Letters:
  Invalid
Status in Music application for Ubuntu devices:
  Invalid
Status in Clock application for Ubuntu devices:
  Invalid
Status in “qtmultimedia-opensource-src” package in Ubuntu:
  New
Status in “thumbnailer” package in Ubuntu:
  Fix Released

Bug description:
  Seems for a few days some of the core apps which use qtmultimedia now
  fail to start on the desktop with output like this:-

  ⟫ qmlscene music-app.qml
  unity::action::ActionManager::ActionManager(QObject*):
  Could not determine application identifier. HUD will not work 
properly.
  Provide your application identifier in $APP_ID environment variable.

  (qmlscene:25234): GLib-GObject-WARNING **: cannot register existing
  type 'GstFormat'

  (qmlscene:25234): GLib-CRITICAL **: g_once_init_leave: assertion
  'result != 0' failed

  (qmlscene:25234): GLib-GObject-WARNING **: cannot retrieve class for
  invalid (unclassed) type 'invalid'

  (qmlscene:25234): GLib-GObject-WARNING **: cannot register existing
  type 'GstQuery'

  (qmlscene:25234): GLib-CRITICAL **: g_once_init_leave: assertion
  'result != 0' failed

  (qmlscene:25234): GLib-GObject-WARNING **: cannot retrieve class for
  invalid (unclassed) type 'invalid'

  (qmlscene:25234): GLib-GObject-WARNING **: cannot register existing
  type 'GstObject'

  (qmlscene:25234): GLib-CRITICAL **: g_once_init_leave: assertion
  'result != 0' failed

  (qmlscene:25234): GLib-GObject-WARNING **: cannot retrieve class for
  invalid (unclassed) type 'invalid'

  
  Attached is the strace output as foo.txt

  A simple sample app which reproduces the issue can be seen at
  https://code.launchpad.net/~andrew-hayzen/+junk/test-mediaplayer-app

  Also affected include core apps which use Audio {} such as Clock and
  Dropping Letters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dropping-letters/+bug/1363314/+subscriptions

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

[Touch-packages] [Bug 1342858] Re: old click packages are not always cleaned out

2014-09-10 Thread Colin Watson

** Changed in: click (Ubuntu)
 Assignee: (unassigned) = Colin Watson (cjwatson)

** Changed in: click (Ubuntu)
   Status: Triaged = In Progress

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

Title:
  old click packages are not always cleaned out

Status in “click” package in Ubuntu:
  In Progress

Bug description:
  /var/lib/apparmor/clicks still has a lot of symlinks pointing to
  security manifests for click packages that are no longer installed. I
  haven't verified this, but I think it might have something to do with
  preinstalled packages and system-image updates. Eg:

  $ ls -1 /var/lib/apparmor/clicks/*json | wc -l
  157

  $ click list | wc -l
  85

  $ sudo click list | wc -l
  19

  None of the symlinks in /var/lib/apparmor/clicks are dangling, so
  while this doesn't actively harm the system AFAICT, the 70+ additional
  and unneeded apparmor profiles means a slower first boot when policy
  regeneration is required.

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

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

[Touch-packages] [Bug 1339883] Re: unity8-dash on the phone has unreasonable CPU usage when system is idle with screen off

2014-09-10 Thread Michael Zanetti

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

** Changed in: qtmir
   Status: New = In Progress

** Changed in: qtmir
 Assignee: (unassigned) = Michael Zanetti (mzanetti)

** Branch linked: lp:~unity-team/qtmir/fix-some-lifecycle-bugs

** Branch linked: lp:~mzanetti/unity8/focus-first-if-running-at-startup

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

Title:
  unity8-dash on the phone has unreasonable CPU usage when system is
  idle with screen off

Status in Qt integration with the Mir display server:
  In Progress
Status in The Ubuntu Power Consumption Project:
  New
Status in “unity8” package in Ubuntu:
  In Progress

Bug description:
  I am attaching tty recordings of htop running on N4 with the latest
  image. This is with screen off, no apps running,  system has settled
  after boot. Three recordings of the major CPU usage offenders are
  included:

  unity8
  smartscopesproxy
  mpdecision (probably not directly related to unity8 but adding for 
completeness, please point me to a better place to report this if you know)

  To replay the tty recordings use ttyplay file.tty (from ubuntu
  package ttyrec)

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

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

[Touch-packages] [Bug 1362622] Re: When cancelling a purchase the progress bar doesn't disappear in the preview

2014-09-10 Thread Alejandro J. Cura

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

Title:
  When cancelling a purchase the progress bar doesn't disappear in the
  preview

Status in “unity8” package in Ubuntu:
  Fix Released

Bug description:
  A indeterminate progress bar is shown after pressing the button with
  the price in the preview, while the user waits for pay-ui to get open,
  but if the user cancels the purchase from the ui, when going back to
  the preview the progress bar stays there instead of showing the button
  again.

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

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

[Touch-packages] [Bug 1367696] Re: spinning Ubuntu logo on update boot feels frantic and not very classy

** Summary changed:

- spinning Ubuntu logo on update  boot feels cheesy
+ spinning Ubuntu logo on update  boot feels frantic and not very classy

** Description changed:

  There is a large spinning Ubuntu logo during updates and a small spinning 
Ubuntu logo during the boot process.  I think there are two problems with this:
- - whatever the progress indicator is should be consistent (not one large and 
one small), 
- - more importantly, this progress indicator feels cheap and off brand to me.  
The desktop has the word Ubuntu with dots which change colour to indicate 
progress.  That feels classier to me. Is there a specific reason we have 
diverged from an existing (and excellent) solution?  Isn't this unnecessary 
divergence for the phone?
+ - whatever the progress indicator is should be consistent (not one large and 
one small),
+ - more importantly, this progress indicator feels frantic, cheap and off 
brand to me.  The desktop has the word Ubuntu with dots which change colour to 
indicate progress.  That feels classier to me. Is there a specific reason we 
have diverged from an existing (and excellent) solution?  Isn't this 
unnecessary divergence for the phone?

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

Title:
  spinning Ubuntu logo on update  boot feels frantic and not very
  classy

Status in Ubuntu UX bugs:
  Triaged
Status in “unity-system-compositor” package in Ubuntu:
  New

Bug description:
  There is a large spinning Ubuntu logo during updates and a small spinning 
Ubuntu logo during the boot process.  I think there are two problems with this:
  - whatever the progress indicator is should be consistent (not one large and 
one small),
  - more importantly, this progress indicator feels frantic, cheap and off 
brand to me.  The desktop has the word Ubuntu with dots which change colour to 
indicate progress.  That feels classier to me. Is there a specific reason we 
have diverged from an existing (and excellent) solution?  Isn't this 
unnecessary divergence for the phone?

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

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

[Touch-packages] [Bug 1367521] Re: Some core/system apps do not start when launched from Apps scope

2014-09-10 Thread Alan Pope ʕ•͡ᴥ•ʔ

** Also affects: unity-scope-click (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: unity-scope-click (Ubuntu)
   Importance: Undecided = High

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

Title:
  Some core/system apps do not start when launched from Apps scope

Status in Gallery App:
  New
Status in Music application for Ubuntu devices:
  New
Status in “unity-scope-click” package in Ubuntu:
  Confirmed

Bug description:
  I have image #234 on a Nexus 4 and #231 on a Nexus 7 both with Gallery
  app v2.9.1.1049 installed and neither device can start the app. I only
  receive the following in the application's log:

  ** (process:24210): WARNING **: Unable to find keyfile for application
  'com.ubuntu.gallery_gallery_2.9.1.1049'

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

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

[Touch-packages] [Bug 1357548] Re: Empty PIN/password/passphrase field appears to contain 4 characters

2014-09-10 Thread Sebastien Bacher

that's a duplicate of bug #1352953, not sure if it should be marked this
way though since that one has design recommendations

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

Title:
  Empty PIN/password/passphrase field appears to contain 4 characters

Status in Ubuntu UI Toolkit:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in “ubuntu-ui-toolkit” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  New

Bug description:
  minor interrelated issues  probably needs design input
  1) visual inconsistency of the pin text box prompt shows 4 bullets implying 
needing 4 characters, but the passphrase is text box is empty
  2) selecting the pin text box prompt, the bullets remain, and don't respond 
to delete, they don't disappear once typing begins (i would think dissappear on 
text box selection)
  3) having a show password would be nice

  
  Desired resolution: Passcode/password fields should never contain bullets 
when you haven't entered anything in them.

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

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

[Touch-packages] [Bug 1367521] Re: Some core/system apps do not start when launched from Apps scope

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

** Changed in: unity-scope-click (Ubuntu)
   Status: New = Confirmed

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

Title:
  Some core/system apps do not start when launched from Apps scope

Status in Gallery App:
  New
Status in Music application for Ubuntu devices:
  New
Status in “unity-scope-click” package in Ubuntu:
  Confirmed

Bug description:
  I have image #234 on a Nexus 4 and #231 on a Nexus 7 both with Gallery
  app v2.9.1.1049 installed and neither device can start the app. I only
  receive the following in the application's log:

  ** (process:24210): WARNING **: Unable to find keyfile for application
  'com.ubuntu.gallery_gallery_2.9.1.1049'

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

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

[Touch-packages] [Bug 1367730] [NEW] container root directory has broken permissions with tight umask and --keep-data

2014-09-10 Thread Martin Pitt

Public bug reported:

While fixing autopkgtest for tight umasks
(http://bugs.debian.org/761049) I noticed that LXC fails under tight
umasks, too:

$ sudo -i
# umask 077
# lxc-start-ephemeral --keep-data -o adt-utopic
[... boots ... ]
adt-utopic-9x0b7tw_ login: ubuntu
Password:
Welcome to Ubuntu Utopic Unicorn (development branch) (GNU/Linux 
3.16.0-14-generic x86_64)

 * Documentation:  https://help.ubuntu.com/
Unable to cd to '/home/ubuntu'

then it fails and goes back to the login prompt. This is because of

$ sudo lxc-attach -n adt-utopic-9x0b7tw_
root@adt-utopic-9x0b7tw_:/# ls -ld /
drwx-- 1 root root 4096 Sep 10 14:23 /

apparently the container overlay root directory is created with the host
umask, and thus any non-root process in the container can't execute
anything due to / having 0700 permissions only.

This is with LXC 1.1.0~alpha1-0ubuntu4 under current Utopic.

** Affects: lxc (Ubuntu)
 Importance: Low
 Status: New

** Changed in: lxc (Ubuntu)
   Importance: Undecided = Low

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

Title:
  container root directory has broken permissions with tight umask and
  --keep-data

Status in “lxc” package in Ubuntu:
  New

Bug description:
  While fixing autopkgtest for tight umasks
  (http://bugs.debian.org/761049) I noticed that LXC fails under tight
  umasks, too:

  $ sudo -i
  # umask 077
  # lxc-start-ephemeral --keep-data -o adt-utopic
  [... boots ... ]
  adt-utopic-9x0b7tw_ login: ubuntu
  Password:
  Welcome to Ubuntu Utopic Unicorn (development branch) (GNU/Linux 
3.16.0-14-generic x86_64)

   * Documentation:  https://help.ubuntu.com/
  Unable to cd to '/home/ubuntu'

  then it fails and goes back to the login prompt. This is because of

  $ sudo lxc-attach -n adt-utopic-9x0b7tw_
  root@adt-utopic-9x0b7tw_:/# ls -ld /
  drwx-- 1 root root 4096 Sep 10 14:23 /

  apparently the container overlay root directory is created with the
  host umask, and thus any non-root process in the container can't
  execute anything due to / having 0700 permissions only.

  This is with LXC 1.1.0~alpha1-0ubuntu4 under current Utopic.

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

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

[Touch-packages] [Bug 1367728] Re: compiz crashed with SIGSEGV in FT_Load_Glyph()

2014-09-10 Thread Apport retracing service

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1199571, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: CoreDump.gz
   
https://bugs.launchpad.net/bugs/1367728/+attachment/4200542/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1367728/+attachment/4200544/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1367728/+attachment/4200545/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1367728/+attachment/4200546/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1367728/+attachment/4200547/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1367728/+attachment/4200548/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1367728/+attachment/4200549/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1199571
   Huge multi-threading violations in cairo

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  compiz crashed with SIGSEGV in FT_Load_Glyph()

Status in “unity” package in Ubuntu:
  New

Bug description:
  Crashed when opening the dash.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: unity 7.3.1+14.10.20140904-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
  Uname: Linux 3.16.0-14-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Sep  9 19:27:23 2014
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2012-07-31 (769 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  ProcCmdline: compiz
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=en_US
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fceeca5e9ac:testb  $0x1,(%rax)
   PC (0x7fceeca5e9ac) ok
   source $0x1 ok
   destination (%rax) (0x) not located in a known VMA region (needed 
writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
   FT_Load_Glyph () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
  Title: compiz crashed with SIGSEGV in FT_Load_Glyph()
  UpgradeStatus: Upgraded to utopic on 2014-08-02 (38 days ago)
  UserGroups: adm autopilot cdrom dip libvirtd lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1367732] [NEW] Screen blinks/flashes/flickers on boot, can't even login to shell

2014-09-10 Thread SWAPNANIL SAHA

Public bug reported:

Ubuntu 14.04; grub 2; lightdm; fglrx; gnome metacity
After booting, during the login prompt(but it does not appear), the screen goes 
black and reappears(gray color, blank), and this doesn't stop.
when booting in recovery mode, it doesn't happen.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: lightdm 1.10.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
Uname: Linux 3.13.0-35-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Sep 10 17:56:19 2014
InstallationDate: Installed on 2014-07-23 (48 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug third-party-packages trusty

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

Title:
  Screen blinks/flashes/flickers on boot, can't even login to shell

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  Ubuntu 14.04; grub 2; lightdm; fglrx; gnome metacity
  After booting, during the login prompt(but it does not appear), the screen 
goes black and reappears(gray color, blank), and this doesn't stop.
  when booting in recovery mode, it doesn't happen.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Sep 10 17:56:19 2014
  InstallationDate: Installed on 2014-07-23 (48 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1367730] Re: container root directory has broken permissions with tight umask and --keep-data

2014-09-10 Thread Martin Pitt

** Description changed:

  While fixing autopkgtest for tight umasks
  (http://bugs.debian.org/761049) I noticed that LXC fails under tight
  umasks, too:
  
  $ sudo -i
  # umask 077
  # lxc-start-ephemeral --keep-data -o adt-utopic
  [... boots ... ]
  adt-utopic-9x0b7tw_ login: ubuntu
- Password: 
+ Password:
  Welcome to Ubuntu Utopic Unicorn (development branch) (GNU/Linux 
3.16.0-14-generic x86_64)
  
-  * Documentation:  https://help.ubuntu.com/
+  * Documentation:  https://help.ubuntu.com/
  Unable to cd to '/home/ubuntu'
  
  then it fails and goes back to the login prompt. This is because of
  
  $ sudo lxc-attach -n adt-utopic-9x0b7tw_
  root@adt-utopic-9x0b7tw_:/# ls -ld /
  drwx-- 1 root root 4096 Sep 10 14:23 /
  
  apparently the container overlay root directory is created with the host
  umask, and thus any non-root process in the container can't execute
  anything due to / having 0700 permissions only.
+ 
+ This is with LXC 1.1.0~alpha1-0ubuntu4 under current Utopic.

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

Title:
  container root directory has broken permissions with tight umask and
  --keep-data

Status in “lxc” package in Ubuntu:
  New

Bug description:
  While fixing autopkgtest for tight umasks
  (http://bugs.debian.org/761049) I noticed that LXC fails under tight
  umasks, too:

  $ sudo -i
  # umask 077
  # lxc-start-ephemeral --keep-data -o adt-utopic
  [... boots ... ]
  adt-utopic-9x0b7tw_ login: ubuntu
  Password:
  Welcome to Ubuntu Utopic Unicorn (development branch) (GNU/Linux 
3.16.0-14-generic x86_64)

   * Documentation:  https://help.ubuntu.com/
  Unable to cd to '/home/ubuntu'

  then it fails and goes back to the login prompt. This is because of

  $ sudo lxc-attach -n adt-utopic-9x0b7tw_
  root@adt-utopic-9x0b7tw_:/# ls -ld /
  drwx-- 1 root root 4096 Sep 10 14:23 /

  apparently the container overlay root directory is created with the
  host umask, and thus any non-root process in the container can't
  execute anything due to / having 0700 permissions only.

  This is with LXC 1.1.0~alpha1-0ubuntu4 under current Utopic.

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

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

[Touch-packages] [Bug 1336675] Re: SIM unlock - UI hangs when user enters wrong PIN

2014-09-10 Thread Jussi Pakkanen

With system-image 27 this does not happen any more. Typing the wrong PIN
causes the dialog to come up again and then typing the right PIN unlocks
as expected.

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

** Changed in: unity8 (Ubuntu)
   Status: Triaged = Incomplete

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

Title:
  SIM unlock - UI hangs when user enters wrong PIN

Status in “indicator-network” package in Ubuntu:
  Incomplete
Status in “unity8” package in Ubuntu:
  Incomplete

Bug description:
  When the user wants to unlock his SIM card and enters a wrong PIN, the
  UI freezes completely on second attempt and a reboot is required.

  Test Case:
  1. Boot a SIM locked device
  2. Go to network indicator/sim unlock
  3. On the keypad enter a wrong PIN
  4. After the notification that unlock failed, enter the right PIN

  Actual Result
  While user is entering the PIN for the second time, the UI freezes and the 
phone must be rebooted.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: ubuntu-system-settings 0.3+14.10.20140626.1-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.3-0ubuntu2
  Architecture: armhf
  Date: Wed Jul  2 10:15:29 2014
  InstallationDate: Installed on 2014-07-02 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140702-020204)
  SourcePackage: ubuntu-system-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 986817] Re: UA-101 - UA-101, playback Pulseaudio fails to detect card

2014-09-10 Thread Raymond

seem bug if your card support 10 channels


lt-pulseaudio] alsa-util.c: Managed to open hw:2
I: [lt-pulseaudio] alsa-util.c: Disabling tsched mode since BATCH flag is set
D: [lt-pulseaudio] alsa-util.c: snd_pcm_hw_params_set_format(Signed 16 bit 
Little Endian) failed: Invalid argument
D: [lt-pulseaudio] alsa-util.c: snd_pcm_hw_params_set_format(Signed 16 bit Big 
Endian) failed: Invalid argument
D: [lt-pulseaudio] alsa-util.c: snd_pcm_hw_params_set_format(Float 32 bit 
Little Endian) failed: Invalid argument
D: [lt-pulseaudio] alsa-util.c: snd_pcm_hw_params_set_format(Float 32 bit Big 
Endian) failed: Invalid argument
D: [lt-pulseaudio] alsa-util.c: Maximum hw buffer size is 227 ms
D: [lt-pulseaudio] alsa-util.c: Set buffer size first (to 7680 samples), period 
size second (to 960 samples).
I: [lt-pulseaudio] alsa-util.c: Device hw:2 doesn't support 44100 Hz, changed 
to 96000 Hz.
I: [lt-pulseaudio] alsa-util.c: Device hw:2 doesn't support 4 channels, changed 
to 12.
I: [lt-pulseaudio] alsa-util.c: Device hw:2 doesn't support sample format 
s16le, changed to s32le.
D: [lt-pulseaudio] alsa-mixer.c: Channel map for mapping 'multichannel' 
permanently changed to 
'front-left,front-right,rear-left,rear-right,front-center,lfe,side-left,side-right,aux0,aux1,aux2,aux3'
D: [lt-pulseaudio] alsa-mixer.c: Profile input:multichannel supported.

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

Title:
   UA-101 - UA-101, playback  Pulseaudio fails to detect card

Status in PulseAudio sound server:
  Fix Released
Status in “pulseaudio” package in Ubuntu:
  Confirmed

Bug description:
  This bug has been created with apport-bug.

  After upgrade from 10.04, the UA-101 inputs and outputs seem unavailable in 
standard audio settings.
  Sound works with VLC when UA-101 is selected via ALSA.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: pulseaudio 1:1.1-0ubuntu15
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14
  Uname: Linux 3.2.0-23-generic-pae i686
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  michael   19895 F pulseaudio
   /dev/snd/controlC0:  michael   19895 F pulseaudio
   /dev/snd/pcmC0D0p:   michael   19895 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf6ff8000 irq 44'
 Mixer name : 'Realtek ALC883'
 Components : 'HDA:10ec0883,1043829f,0012'
 Controls  : 46
 Simple ctrls  : 22
  Card1.Amixer.info:
   Card hw:1 'UA101'/'EDIROL UA-101 (serial ZT82634), 192000 Hz at 
usb-:00:1a.7-3, high speed'
 Mixer name : ''
 Components : ''
 Controls  : 1
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'MIDI Input Mode',0
 Capabilities: enum
 Items: 'High Load' 'Light Load'
 Item0: 'Light Load'
  Card2.Amixer.info:
   Card hw:2 'CX8811'/'Conexant CX8811 at 0xfb00'
 Mixer name : 'CX88'
 Components : ''
 Controls  : 3
 Simple ctrls  : 2
  Date: Sun Apr 22 13:03:21 2012
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: CX23880/1/2/3 PCI Video and Audio Decoder [Audio Port] - 
Conexant CX8811
  Title: [UA-101 - UA-101, playback] Pulseaudio fails to detect card
  UpgradeStatus: Upgraded to precise on 2012-04-18 (3 days ago)
  dmi.bios.date: 10/14/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1201
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5K
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1201:bd10/14/2008:svnSystemmanufacturer:pnP5K:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5K
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1367028] Re: [MIR] system-image

2014-09-10 Thread Barry Warsaw

I have a branch that removes tox and its sub-dependencies as b-ds for
system-image.  I'll release it in a s-i 2.4 to come in the next few days
hopefully.

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

Title:
  [MIR] system-image

Status in “system-image” package in Ubuntu:
  New

Bug description:
  Availability: universe

  Rationale: system-image is the client for image based upgrades.  It is
  a core component and thus seeded in Ubuntu Touch.

  Security: No known issues.

  QA: Well supported upstream and in Ubuntu.  Package has build-time
  unittests and DEP-8 tests.

  UI standards: n/a

  Dependencies: All non-main build- and run-time dependencies already or
  will soon have MIRs.

  Standards compliance: No known issues.

  Maintenance: No known issues.

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

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

[Touch-packages] [Bug 1357548] Re: Empty PIN/password/passphrase field appears to contain 4 characters

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

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New = Confirmed

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

Title:
  Empty PIN/password/passphrase field appears to contain 4 characters

Status in Ubuntu UI Toolkit:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in “ubuntu-ui-toolkit” package in Ubuntu:
  Confirmed
Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  minor interrelated issues  probably needs design input
  1) visual inconsistency of the pin text box prompt shows 4 bullets implying 
needing 4 characters, but the passphrase is text box is empty
  2) selecting the pin text box prompt, the bullets remain, and don't respond 
to delete, they don't disappear once typing begins (i would think dissappear on 
text box selection)
  3) having a show password would be nice

  
  Desired resolution: Passcode/password fields should never contain bullets 
when you haven't entered anything in them.

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

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

[Touch-packages] [Bug 1357548] Re: Empty PIN/password/passphrase field appears to contain 4 characters

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

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

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

Title:
  Empty PIN/password/passphrase field appears to contain 4 characters

Status in Ubuntu UI Toolkit:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in “ubuntu-ui-toolkit” package in Ubuntu:
  Confirmed
Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  minor interrelated issues  probably needs design input
  1) visual inconsistency of the pin text box prompt shows 4 bullets implying 
needing 4 characters, but the passphrase is text box is empty
  2) selecting the pin text box prompt, the bullets remain, and don't respond 
to delete, they don't disappear once typing begins (i would think dissappear on 
text box selection)
  3) having a show password would be nice

  
  Desired resolution: Passcode/password fields should never contain bullets 
when you haven't entered anything in them.

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

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

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

I have introduced one big lock for ifupdown. The ifup, ifdown or ifquery
commands cannot be run simultaneously.

Since SEVERAL ifupdown pre/post scripts do need to make reentrant calls
do these commands I created on environment variable that disabled the
locking when reentrant calls are made to these scripts. This way sysv
and upstart networking scripts will never step into other's feet.

Attaching fix for ifupdown.

PS: This breaks even more ifenslave buggy behavior.. wait for next
comments.

** Patch added: trusty_ifupdown_0.7.47.2ubuntu4.2.debdiff

https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1337873/+attachment/4200562/+files/trusty_ifupdown_0.7.47.2ubuntu4.2.debdiff

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

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

Status in “ifupdown” package in Ubuntu:
In Progress
Status in “ifupdown” package in Debian:
New

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

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

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

to be explained

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

My setup:

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

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

Beginning:

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

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

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

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

OR only the script network-interface enabled:

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

Enabling bonding:

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

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

auto eth2
iface eth2 inet manual
bond-master bond0

auto bond0
iface bond0 inet static
bond-mode 1
bond-miimon 100
bond-primary eth1 eth2
address 192.168.169.1
netmask 255.255.255.0
broadcast 192.168.169.255
---

Having both scripts running does not make any difference since we
are missing bond-slaves keyword on slave interfaces, for ifenslave
to work, and they are set to manual.

Ifenslave code:

for slave in $BOND_SLAVES ; do
...
# Ensure $slave is down.
ip link set $slave down 2/dev/null
if ! sysfs_add slaves $slave 2/dev/null ; then
echo Failed to enslave $slave to $BOND_MASTER. Is $BOND_MASTER
ready and a bonding interface ? 2
else
# Bring up

[Touch-packages] [Bug 1295623] Re: Sometimes input breaks and only edges are responsive

2014-09-10 Thread Daniel d'Andrada

@Zanetti

 Here's a way to easily reproduce it with the dash to verify if this issue is 
 fixed:
 [...]

Thanks for that test case! Very useful.

That's another issue, which lp:~dandrader/qtmir/missingTouchEnd-
lp1295623  doesn't fix. I was hoping to deal with it in another bug
report but we can keep using this one since to the user it's hard to
distinguish between the two.

So, those are the problems:

1 - unity8 not receiving a touch end from Mir (or lower, like the evedev 
device) and thus having its mouse event emulation getting stuck
2 - A MirSurfaceItem inside unity8's QML scene not receiving a touch end, and 
thus leaving the mouse event emulation of the corresponding Qt client app stuck 
(like unity8-dash).

So lp:~dandrader/qtmir/missingTouchEnd-lp1295623 fixes item 1. Now I'm
working on a fix/workaround for item 2. Item 2 does look like a Qt bug
(although some might claim we're using its API wrongly). It happens when
you disable an Item while it's owning a touch point, which causes
QQuickWindow's event delivery to stop sending touch events for that Item
(which is ok). But it will never get further updates for that touch
point even when reenabled. Meaning it will never get a TouchEnd for that
touch. When you tap on it again it receives a whole new TouchBegin like
if the previous touch point, whose end is still pending, never existed.
So, when you disable an Item that owns a touch point I think
QQuickWindow should synthesize a TouchEnd for that disabled Item.

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

Title:
  Sometimes input breaks and only edges are responsive

Status in “unity8” package in Ubuntu:
  In Progress

Bug description:
  I had the music app (paused) open over night on my mako, waking up the
  device I found the application page showing me the one open app. The
  shell page itself is completely unresponsive, all side edge swipes
  seem to work fine though. I can switch to the music app when swiping
  from the right, bring up the launcher from the left and use the
  indicators from the top.

  When I am in the music app I can bring up the HUD from the bottom
  (trying to close the app, since the closing via the unresponsive shell
  does not work) but the HUD is completely unresponsive. Trying to close
  the HUD again via swiping down I see the indicators expand behind it
  and I am able to get input into the expanded indicators behind the
  HUD, but not the HUD itself.

  TEST CASE:
  1. tap and hold the dash (do not release)
  2. with the other hand, drag in the launcher and launch an app
  3. when the other app has started, release the first finger

  ACTUAL RESULT
  Dash mouse input will be broken. You cannot scroll the dash any more or tap 
entries. However, touch input still works as you can still activate the bottom 
edge.

  EXPECTED RESULT
  Dash is still responding to mouse input and touch input.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity8 7.84+14.04.20140319.1-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: armhf
  Date: Fri Mar 21 11:57:53 2014
  InstallationDate: Installed on 2014-03-20 (1 days ago)
  InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140320)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  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/1295623/+subscriptions

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

[Touch-packages] [Bug 1367749] [NEW] *#06# not showing IMEI on mako

2014-09-10 Thread Omer Akram

Public bug reported:

I dial *#06# the IMEI dialog appears but I don't see the IMEI. see
attached screenshot.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: telepathy-ofono 0.2+14.10.20140826.1-0ubuntu1
Uname: Linux 3.4.0-5-mako armv7l
ApportVersion: 2.14.7-0ubuntu2
Architecture: armhf
Date: Wed Sep 10 13:09:15 2014
InstallationDate: Installed on 2014-09-10 (0 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140910-020205)
SourcePackage: telepathy-ofono
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: telepathy-ofono (Ubuntu)
 Importance: Medium
 Assignee: Tiago Salem Herrmann (tiagosh)
 Status: New


** Tags: apport-bug armhf qa-touch utopic

** Attachment added: IMEI.png
   https://bugs.launchpad.net/bugs/1367749/+attachment/4200565/+files/IMEI.png

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

Title:
  *#06# not showing IMEI on mako

Status in “telepathy-ofono” package in Ubuntu:
  New

Bug description:
  I dial *#06# the IMEI dialog appears but I don't see the IMEI. see
  attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: telepathy-ofono 0.2+14.10.20140826.1-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: armhf
  Date: Wed Sep 10 13:09:15 2014
  InstallationDate: Installed on 2014-09-10 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140910-020205)
  SourcePackage: telepathy-ofono
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1367004] Re: [MIR] python-gnupg

2014-09-10 Thread Michael Terry

You gloss over the security issues in your MIR description.  The most
recent release fixed three CVEs...

Given such security sensitiveness of gnupg wrappers, can you explain why
it'd be worth having two python wrappers in main?  We already have
python-gpgme.  Do they offer different functionality?

** Changed in: python-gnupg (Ubuntu)
   Status: New = Incomplete

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

Title:
  [MIR] python-gnupg

Status in “python-gnupg” package in Ubuntu:
  Incomplete

Bug description:
  Availability: 
  % apt-cache show python-gnupg | grep -i section
  Section: universe/python

  Rationale:
  As shown here: 
http://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg 
python-gnupg is a run-time dependency of system-image, which is the system 
upgrader for, and seeded into Ubuntu Touch.

  Security, QA
  The package is well supported upstream, in Debian, and in Ubuntu.
  LP: #1283783 describes an upgrading bug, but I have not yet investigated it.

  UI standards: n/a

  Dependencies: None that aren't already in main.

  Standards compliance: No known issues.

  Maintenance: No known issues.

  This is the generally accepted best gnupg wrapper for Python.  It
  supports both Python 2 and 3.

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

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

[Touch-packages] [Bug 1367551] Re: [MIR] capnproto

2014-09-10 Thread Michael Terry

Symbols files help maintainers notice when the API changes and helps
other packages know which minimum version of a library they need to
depend on.

See https://wiki.debian.org/UsingSymbolsFiles

Note that a lack of a symbols file isn't a blocker, but they are super
encouraged.

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

Title:
  [MIR] capnproto

Status in “capnproto” package in Ubuntu:
  Incomplete

Bug description:
  Can we please include this in main? unity-scopes-api has a dependency
  on capnproto.

  Source and bug tracking for this are here:
  https://github.com/kentonv/capnproto

  There are no dependencies other than C++ 11 (gcc 4.7 or later work).

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

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

[Touch-packages] [Bug 1365646] Re: Top Crasher: /usr/sbin/system-image-dbus:RuntimeError:_download

2014-09-10 Thread Ken VanDine

The multiple dialogs getting opened was a bug I just fixed (or worked
around), landed in utopic-proposed last night.

In the UpdateManager code, it was getting onSystemUpdateDownloaded
signal multiple times, and each time opening a dialog.  The number of
times this signal was emitted seems to vary, I had times where it only
happened twice (1 too many) and other times where it was 5 or more
times.  In system-settings, it was creating a dialog each time the
signal was emitted.  It wasn't visual, and you could only notice it if
you hit not now.  If you choose to install the update, the view
changes so you never noticed the additional dialogs, then the device
rebooted.  What I did was to do a check, if there is a system update in
progress or awaiting confirmation from the user, it just does nothing on
the additional signals.

I'm not very familiar with the update code, could it be emitting that
signal for each update, not just system updates?

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

Title:
  Top Crasher: /usr/sbin/system-image-dbus:RuntimeError:_download

Status in Ubuntu system image (server/client/updater):
  In Progress
Status in “system-image” package in Ubuntu:
  Confirmed

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

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

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

[Touch-packages] [Bug 1349471] Re: See more/less sounds wrong

2014-09-10 Thread John Lea

** Changed in: ubuntu-ux
   Importance: Undecided = Medium

** Changed in: ubuntu-ux
   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/1349471

Title:
  See more/less sounds wrong

Status in Ubuntu UX bugs:
  Triaged
Status in “unity8” package in Ubuntu:
  Incomplete

Bug description:
  Collapsed/Expandable scopes show a label See more and expanded
  scopes accordingly See less. This sounds weird and should rather be
  Show more and Show less. The user is instructing the phone to show
  more entries, it's not that the phone sees them.

  I only really noticed with the german translation Mehr sehen which
  seems really uncommon in user interfaces, but after consulting with a
  native english speaker we seem to agree that the issue is the actual
  string, not the translation.

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

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

[Touch-packages] [Bug 1332306] Re: Hot-swapped SIMs should be detected and prompt user to reboot

2014-09-10 Thread Jussi Pakkanen

With krillin image 27 the Present signal is _not_ sent. I tested both
with gdbus and monitor-ofono. The status claims fix released, though,
so something is amiss.

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

Title:
  Hot-swapped SIMs should be detected and prompt user to reboot

Status in “indicator-network” package in Ubuntu:
  New
Status in “ofono” package in Ubuntu:
  Fix Released

Bug description:
  Our telephony stack doesn't support hot-swapping of SIM cards.  If a
  user hot-swaps a SIM, the telephony stack will become unusable.

  The telephony-service should detect when this happens and display a
  snap-decision informing the user that they need to restart their
  device.

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

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

[Touch-packages] [Bug 1340952] Re: Video and Music scopes should provide non-file:/// based URIs

2014-09-10 Thread Andrew Hayzen

Just as an FYI the music-app supports the protocol music:///path/to/file
which would resolve this issue for the music scope.

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

Title:
  Video and Music scopes should provide non-file:/// based URIs

Status in Media Player App:
  In Progress
Status in Unity Media Scanner Scope:
  Confirmed
Status in QML plugin for Scopes:
  Confirmed
Status in “url-dispatcher” package in Ubuntu:
  In Progress

Bug description:
  There are some mp4 videos found/indexed by mediascanner-service-2.0 from 
~/Pictures. The thumbnails of those are shown in the Video scope but can not be 
played. If the video is moved over to ~/Videos, the videos are played just fine.
  mako utopic r119

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

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

[Touch-packages] [Bug 1367715] Re: [Greeter] on N10 left edge swipe unlocks Greeter, even with pin/password set

2014-09-10 Thread kevin gunn

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

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

Title:
  [Greeter] on N10 left edge swipe unlocks Greeter, even with
  pin/password set

Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  Steps to repro:
  1. Set a PIN or password
  2. Hit power to lock device
  3. Hit power
  4. at Greeter, do a left-edge swipe

  It unlocks the device even though I never entered the PIN/password

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

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

[Touch-packages] [Bug 1349921] Re: Empty! message needs to be marked for translation

2014-09-10 Thread Víctor R . Ruiz

Any ETA?

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

Title:
  Empty! message needs to be marked for translation

Status in Ubuntu Translations:
  Invalid
Status in “unity8” package in Ubuntu:
  In Progress

Bug description:
  When an indicator has no content, there is an Empty! message shown
  that appears always in English.

  It seems to come from:
  
http://bazaar.launchpad.net/~unity-team/unity8/trunk/view/head:/qml/Panel/Indicators/DefaultIndicatorPage.qml#L200

  So to make it translatable it should simply be enclosed in i18n.tr()
  and the .pot template updated.

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

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

[Touch-packages] [Bug 1367756] Re: tracker-extract crashed with SIGABRT in g_malloc0()

2014-09-10 Thread Apport retracing service

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1364780, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: CoreDump.gz
   
https://bugs.launchpad.net/bugs/1367756/+attachment/4200579/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1367756/+attachment/4200581/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1367756/+attachment/4200582/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1367756/+attachment/4200583/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1367756/+attachment/4200584/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1367756/+attachment/4200585/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1367756/+attachment/4200586/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1364780

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  tracker-extract crashed with SIGABRT in g_malloc0()

Status in “tracker” package in Ubuntu:
  New

Bug description:
  It hapned on log in. The only problem I can see is weather applet not
  loading weather. Am running ubuntu gnome in virtual machine.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: tracker-extract 1.0.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-13.19-generic 3.16.1
  Uname: Linux 3.16.0-13-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Wed Sep 10 08:27:37 2014
  ExecutablePath: /usr/lib/tracker/tracker-extract
  InstallationDate: Installed on 2014-08-31 (10 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Alpha amd64 
(20140826)
  ProcCmdline: /usr/lib/tracker/tracker-extract
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: tracker
  StacktraceTop:
   g_malloc0 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_slice_free1 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_queue_pop_tail () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: tracker-extract crashed with SIGABRT in g_malloc0()
  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/ubuntu/+source/tracker/+bug/1367756/+subscriptions

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

[Touch-packages] [Bug 1367715] Re: [Greeter] on N10 left edge swipe unlocks Greeter, even with pin/password set

2014-09-10 Thread kevin gunn

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

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) = Michael Terry (mterry)

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

Title:
  [Greeter] on N10 left edge swipe unlocks Greeter, even with
  pin/password set

Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  Steps to repro:
  1. Set a PIN or password
  2. Hit power to lock device
  3. Hit power
  4. at Greeter, do a left-edge swipe

  It unlocks the device even though I never entered the PIN/password

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

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

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

Let's try everything again from the beggining but now with a fixed
ifupdown version (no race conditions between upstart and sysv scripts
). My interfaces file will be exactly the same as the one proposed for
ifenslave examples:

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

auto eth2
iface eth2 inet manual
bond-master bond0

auto bond0
iface bond0 inet static
bond-mode 1
bond-miimon 100
bond-primary eth1 eth2
 address 192.168.169.1
 netmask 255.255.255.0
 broadcast 192.168.169.255
 ---

We do have bond0 created but still no bonding configured:

---
root@provisioned:~# ifconfig bond0
bond0 Link encap:Ethernet  HWaddr 62:64:29:45:df:ef
  BROADCAST MASTER MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

root@provisioned:~# cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

Bonding Mode: load balancing (round-robin)
MII Status: down
MII Polling Interval (ms): 0
Up Delay (ms): 0
Down Delay (ms): 0
---

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

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

Status in “ifupdown” package in Ubuntu:
  In Progress
Status in “ifupdown” package in Debian:
  New

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

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

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

  to be explained

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

  #

   My setup:

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

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

   Beginning:

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

  auto lo
  iface lo inet loopback

  auto eth0
  iface eth0 inet dhcp

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

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

  OR only the script network-interface enabled:

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

   Enabling bonding:

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

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

  auto eth2
  iface eth2 inet manual
  bond-master bond0

  auto bond0
  iface bond0 inet static
  bond-mode 1
  bond-miimon 100
  bond-primary eth1 eth2
address 192.168.169.1
netmask 255.255.255.0
broadcast 192.168.169.255
  ---

  Having both scripts

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

And you can check that upstart got deadlocked:

---
root@provisioned:~# ps -ef | grep ifup
root   618 1  0 10:21 ?00:00:00 ifup --allow auto eth2
root   619 1  0 10:21 ?00:00:00 ifup --allow auto eth1
root   620 1  0 10:21 ?00:00:00 ifup --allow auto lo
root   621 1  0 10:21 ?00:00:00 ifup --allow auto eth0
root   726 1  0 10:21 ?00:00:00 ifup --allow auto bond0
root   739   733  0 10:21 ?00:00:00 ifup -a

root@provisioned:~# for i in `ps -ef | grep ifup | grep -v grep | awk '{print 
$2}'`; do echo $i; cat /proc/$i/environ; done
618
...UPSTART_INSTANCE=eth2...
...UPSTART_INSTANCE=eth1...
...UPSTART_INSTANCE=lo...
...UPSTART_INSTANCE=eth0...
...INSTANCE=UPSTART_JOB=networking...
---

As I said before, sysv scripts and upstart scripts were depending on
each other to run in parallel (unfortunately with race conditions)
to configure bonding. We can see here that one of upstart networking
processes (networking or network-instance) got the lock and is 
on an infinite loop waiting for other instance.. who is waiting for 
the lock.

---
root@provisioned:~# ps -ef | grep ifenslave
root   647   641  0 10:21 ?00:00:00 /bin/sh 
/etc/network/if-pre-up.d/ifenslave
---

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

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

Status in “ifupdown” package in Ubuntu:
  In Progress
Status in “ifupdown” package in Debian:
  New

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

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

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

  to be explained

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

  #

   My setup:

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

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

   Beginning:

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

  auto lo
  iface lo inet loopback

  auto eth0
  iface eth0 inet dhcp

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

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

  OR only the script network-interface enabled:

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

   Enabling bonding:

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

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

  auto eth2
  iface eth2 inet manual
  bond-master bond0

  auto bond0
  iface bond0 inet static
  bond-mode 1
  bond-miimon 100
  bond-primary eth1 eth2
address

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

YES!

---
root@provisioned:~# pstree -a
...
├─ifup --allow auto eth2
│   └─sh -c run-parts  /etc/network/if-pre-up.d
│   └─run-parts /etc/network/if-pre-up.d
│   └─ifenslave /etc/network/if-pre-up.d/ifenslave
│   └─sleep 0.1
---

One slave interface, eth2 in this case, got the ifupdown lock and is
running an infite loop waiting for the master bonding interface which
will never run without the lock.

Resuming:

So bonding had to have both networking scripts running (network-
interface and networking) to work AND having both scripts running 
would case race conditions sometime. Disabling one of the scripts
would also cause race condition if right triggers are set (like i
showed in this example). Fixing ifupdown race conditions led me to 
realize ifenslave is taking wrong decisions and can cause deadlocks.

Ifenslave must be fixed together...

* wait for next comments.

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

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

Status in “ifupdown” package in Ubuntu:
  In Progress
Status in “ifupdown” package in Debian:
  New

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

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

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

  to be explained

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

  #

   My setup:

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

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

   Beginning:

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

  auto lo
  iface lo inet loopback

  auto eth0
  iface eth0 inet dhcp

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

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

  OR only the script network-interface enabled:

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

   Enabling bonding:

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

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

  auto eth2
  iface eth2 inet manual
  bond-master bond0

  auto bond0
  iface bond0 inet static
  bond-mode 1
  bond-miimon 100
  bond-primary eth1 eth2
address 192.168.169.1
netmask 255.255.255.0
broadcast 192.168.169.255
  ---

  Having both scripts running does not make any difference since we
  are missing bond-slaves keyword on slave interfaces, for ifenslave
  to work, and they are set to manual.

  Ifenslave code:

  
  for slave in $BOND_SLAVES ; do
  ...
  # Ensure $slave is down.
  ip link set $slave down

[Touch-packages] [Bug 1341681] Re: Autopilot tests should stop using deprecated emulators module

2014-09-10 Thread Andrew Hayzen

** Changed in: music-app
   Status: Fix Committed = Fix Released

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

Title:
  Autopilot tests should stop using deprecated emulators module

Status in Dialer app for Ubuntu Touch:
  In Progress
Status in Dropping Letters:
  New
Status in Music application for Ubuntu devices:
  Fix Released
Status in Notes App:
  New
Status in Ubuntu Reminders app:
  Fix Released
Status in Sudoku game for Ubuntu Touch:
  New
Status in Calculator application for Ubuntu devices:
  Fix Committed
Status in Calendar application for Ubuntu devices:
  Fix Released
Status in Clock application for Ubuntu devices:
  Fix Released
Status in File Manager application for Ubuntu devices:
  New
Status in RSS Feed Reader application for Ubuntu devices:
  New
Status in Terminal application for Ubuntu devices:
  Fix Released
Status in Weather application for Ubuntu devices:
  New
Status in “dialer-app” package in Ubuntu:
  Fix Released

Bug description:
  Autopilot tests should stop using deprecated emulators module. Instead
  the new custom_proxy_objects modules should be used and called
  directly.

  Please note until https://bugs.launchpad.net/ubuntu-ui-
  toolkit/+bug/1341679 is fixed, the deprecation warning will still
  appear.

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

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

[Touch-packages] [Bug 1350281] Re: Download Complete snap-decision - improper use of the UbuntuShape

** Changed in: content-hub
   Status: In Progress = Fix Released

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

Title:
  Download Complete snap-decision - improper use of the UbuntuShape

Status in Content sharing/picking infrastructure and service:
  Fix Released
Status in “content-hub” package in Ubuntu:
  Fix Released

Bug description:
   The Download Complete snap-decision notification does not use the
  non-shaped-icon hint causing the symbolic save icon being masked
  with an UbuntuShape. This should not be the case.

To manage notifications about this bug go to:
https://bugs.launchpad.net/content-hub/+bug/1350281/+subscriptions

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

[Touch-packages] [Bug 1314367] Re: Flickering with Ubuntu 14.04 and nvidia card reappeared

2014-09-10 Thread Thomas Carlisle

I just loaded Ubuntu 14.04LTS 64-bit on a Dell D630 with an integrated
Nvidia Quadro NVS 135m display adapter, removed nouveau completely and
installed 340.32 from the Nvidia site (not the edgers PPA), andthe
flicker was present. A common suggestion is to disable dithering in
nvidia-settings, which did not help. The workaround posted by Alexander
Pavel above resolved this. I previously was running an Ubuntu 14.04LTS
64-bit build using the latest properietary driver that is native to
Ubuntu 14.4 (331.something) and did not have this issue.

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

Title:
  Flickering with Ubuntu 14.04 and nvidia card reappeared

Status in “xorg” package in Ubuntu:
  Confirmed

Bug description:
  As requested in Bug #1310633 I'm opening a new bug.

  With a previous version of Ubuntu I already had this flickering. With
  additional options for the kernel module I was able to fix the
  flickering.

  options nvidia NVreg_RegistryDwords=PerfLevelSrc=0x
  NVreg_Mobile=3 NVreg_ModifyDeviceFiles=0

  With version 14.04 and the nvidia-331 (331.38-0ubuntu7) driver the
  flickering reappeared although the line is still present in
  options.conf.

  Using modprobe --resolve-alias nvidia I found the correct driver
  module name which in my case is nvidia_331. Changing the module name
  in options.conf to nvidia_331 X doesn't start anymore. Removing the
  NVreg_ModifyDeviceFiles option X is starting again, but does not solve
  the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: Unity
  Date: Tue Apr 29 21:09:41 2014
  DistUpgraded: 2014-04-17 23:47:50,572 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed
   nvidia-331, 331.38, 3.13.0-24-generic, x86_64: installed
   vboxhost, 4.3.10, 3.13.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GT215GLM [Quadro FX 1800M] [10de:0cbc] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:1521]
  InstallationDate: Installed on 2012-11-17 (528 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  MachineType: Hewlett-Packard HP EliteBook 8540w
  PccardctlStatus:
   Socket 0:
 3.3V
16-bit
PC Card
 Subdevice 0 (function 0) bound to driver pata_pcmcia
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=c6af930a-63f1-4015-9c42-bdde793e3e5a ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2014-04-17 (11 days ago)
  dmi.bios.date: 09/13/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68CVD Ver. F.24
  dmi.board.name: 1521
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 32.35
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CVDVer.F.24:bd09/13/2013:svnHewlett-Packard:pnHPEliteBook8540w:pvr:rvnHewlett-Packard:rn1521:rvrKBCVersion32.35:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8540w
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  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
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Apr 29 21:06:04 2014
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.1-0ubuntu2

To manage notifications about this bug

[Touch-packages] [Bug 1321309] Re: [Indicators] Missed calendar or alarm events need to be properly indicated

2014-09-10 Thread Charles Kerr

I strongly agree that we need to denote missed alarms -- that
information should be prominent.

What's not clear to me is The Right Way to do this. We can't turn the
individual menuitems' icons red because they're removed from the menu
when the time has passed, since they're no longer upcoming events. We
also can't change the panel icon because there's no way to 'clear' the
warning to a normal state.

One thing we could do is to keep old alarms in the menu if (and only if)
they were missed. These menuitems' icons will change to red and can be
cleared by clicking on them. The indicator's main icon could be red if
there are any missed alarm menuitems in the indicator. This isn't a
perfect idea. While it does give the user needed information about
missed alarms, (1) it's a little clumsy and (2) what happens if we have
a handful of missed alarms? They will crowd out the upcoming alarms on
the menu.

Another option would be to leave a missed alarm message in the
Notification center... that raises interesting dependencies between the
indicators :)

This ticket still needs Design feedback.

** Changed in: indicator-datetime
 Assignee: Charles Kerr (charlesk) = James Mulholland 
(jamesjosephmulholland)

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

Title:
  [Indicators] Missed calendar or alarm events need to be properly
  indicated

Status in The Date and Time Indicator:
  Confirmed
Status in Clock application for Ubuntu devices:
  Triaged
Status in Themes for Ubuntu:
  New
Status in Ubuntu UX bugs:
  Fix Committed
Status in “indicator-datetime” package in Ubuntu:
  New
Status in “ubuntu-themes” package in Ubuntu:
  New

Bug description:
  Imagine a scenario where you have a calendar event or a clock alarm to
  go of at 10:00. If you get a call at the same time, then obviously the
  call gets the highest priority and the alarm or calendar audible
  notification is suppressed by the system. So a phone user can actually
  miss the event.

  This can be resolved by turning the alarm icon shown in the indicator
  to blue similar to messages to indicate that an alarm or event was
  missed by the user.

  ---

  Desired solution:

  The alarm icon turns its state to active like notification
  center/messages indicator as suggested in the bug description.

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

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

[Touch-packages] [Bug 1365987] Re: Clicking on 'Show Password' closes the keyboard

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

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

Title:
  Clicking on 'Show Password' closes the keyboard

Status in “ubuntu-ui-toolkit” package in Ubuntu:
  Invalid
Status in “unity8” package in Ubuntu:
  Fix Released

Bug description:
  When entering the wireless password:

  1. Click on the text field to reveal the keyboard
  2. Click on 'Show Password'

  The keyboard now closes

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-network 0.5.1+14.10.20140829~rtm-0ubuntu1 [origin: Ubuntu 
RTM]
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: armhf
  CrashDB: indicator_network
  Date: Fri Sep  5 12:25:28 2014
  InstallationDate: Installed on 2014-09-05 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140905-030204)
  SourcePackage: indicator-network
  ThirdParty: True
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1367551] Re: [MIR] capnproto

2014-09-10 Thread Michi Henning

Yes, I know what a symbols file is. But the requirements don't mention
one. So, what am I supposed to actually do? Build the library, run nm
over it and then post the symbols file here?

It's simply that I don't understand what I am expected to do.

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

Title:
  [MIR] capnproto

Status in “capnproto” package in Ubuntu:
  Incomplete

Bug description:
  Can we please include this in main? unity-scopes-api has a dependency
  on capnproto.

  Source and bug tracking for this are here:
  https://github.com/kentonv/capnproto

  There are no dependencies other than C++ 11 (gcc 4.7 or later work).

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

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

[Touch-packages] [Bug 1346838] Re: [Notification] an incoming call snap-decision notification does not use/display the secondary icon

** Changed in: telephony-service
   Status: In Progress = Fix Released

** Changed in: unity-notifications
   Status: Triaged = Won't Fix

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

Title:
  [Notification] an incoming call snap-decision notification does not
  use/display the secondary icon

Status in Telephony Service:
  Fix Released
Status in Ubuntu UX bugs:
  Fix Committed
Status in Server and client library for desktop notifications in Unity:
  Won't Fix
Status in The Unity 8 shell:
  Fix Released
Status in “telephony-service” package in Ubuntu:
  Fix Released
Status in “unity-notifications” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  Fix Released

Bug description:
  In the new notification UI design a secondary icon needs to be used in the 
top right corner. This icon helps to indicate what kind of notification is 
received.
  E.g. for messaging this icon can define weather user is receiving an SMS, or 
MMS with video, image or v-card. Please refer to the latest notification spec. 
  
https://docs.google.com/a/canonical.com/document/d/1ehZGFePGmy8pnyAGsgWYDeBgr45Cc8jE2mTb2Qz-oeM/edit#heading=h.ihcuz26wprxs

To manage notifications about this bug go to:
https://bugs.launchpad.net/telephony-service/+bug/1346838/+subscriptions

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

[Touch-packages] [Bug 1334855] Re: Can't use toolbar while notifications on screen

Only snap-decisions are meant to be dismissable via swipe. Who connected
this bug to branch lp:~macslow/unity8/swipe-dismiss-snap-decisions ?

I do not agree with the current state of solution. The design-document
explicitly states only snap-decision notifications to be dismissable
(via swipe).

Before proceeding with a fix for this I would like to get a clear
guideline from Design for this non-snap-decision case. Thus marked as
Opinion for the moment.

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

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

Title:
  Can't use toolbar while notifications on screen

Status in Ubuntu UX bugs:
  Fix Committed
Status in “unity8” package in Ubuntu:
  Opinion

Bug description:
  With notifications on the screen, they're overlayed on top of the top
  toolbar, as such I can't tap the back button.

  To replicate.
  Open system settings - accounts
  Sign in to twitter
  Wait while tweet notifications come in
  Navigate anywhere in system settings, such as updates.
  Note you can't go back while the notifications are on screen.

  See screenshot, back button obscured.

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

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

[Touch-packages] [Bug 1367551] Re: [MIR] capnproto

2014-09-10 Thread Michael Terry

See the How to manage the content of symbols files section of
https://wiki.debian.org/UsingSymbolsFiles on how to generate a starting
symbols file.

But basically yes, build the library then run a tool to generate the
symbols file.  Then please pass the patch to Debian because we don't
really want to maintain a symbols delta for long.

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

Title:
  [MIR] capnproto

Status in “capnproto” package in Ubuntu:
  Incomplete

Bug description:
  Can we please include this in main? unity-scopes-api has a dependency
  on capnproto.

  Source and bug tracking for this are here:
  https://github.com/kentonv/capnproto

  There are no dependencies other than C++ 11 (gcc 4.7 or later work).

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

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

[Touch-packages] [Bug 1365752] Re: ubuntu-desktop depends on iBus, which is totally broken

2014-09-10 Thread Daniele Varrazzo

The dependency is actually ubuntu-desktop - unity-control-center -
ibus.

** Package changed: ubuntu-meta (Ubuntu) = unity-control-center
(Ubuntu)

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

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

Title:
  ubuntu-desktop depends on iBus, which is totally broken

Status in “ubuntu-meta” package in Ubuntu:
  New
Status in “unity-control-center” package in Ubuntu:
  New

Bug description:
  Upgrading from Ubuntu 12.04 to 14.04 the package iBus has been
  installed in the system and activated by default. This has caused an
  amount of pain because it has completely broken the input method
  (symptoms: no en-uk keyboard available composite not working, backtick
  to be pressed twice). The problems are reported in a number of places;
  I've read somewhere I can't remember that Unity has some form of
  workaround against ibus but I don't use Unity (using Awesome on some
  systems, lubuntu on another one) and other windows managers are
  affected.

  Even disabling ibus (which has to be done via gnome-language-selector,
  instead of the keyboard panel in gnome-control-center, which is an
  usability problem that deserves its own bug report) the ibus processes
  keep on running. Probably this has no consequence but still there is
  no reason to have unwanted running processes. I have no idea where do
  these processes start, but I clearly have the idea that they shouldn't
  be running where not necessary.

  Uninstalling ibus is not straightforward because the ubuntu-desktop
  package depends on it. The dependency the core package ubuntu-desktop
  on ibus is excessive for a package that is 1) unneeded by many users
  and 2) broken for many users.

  The best solution to date is to:

  ibus exit
  sudo mv /usr/lib/ibus{,.bak}
  sudo mv /usr/bin/ibus{,.bak}

  Please remove the dependency of ubuntu-desktop on ibus and avoid
  installing it for european languages.

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

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

[Touch-packages] [Bug 1350544] Re: Some translations are not loaded

2014-09-10 Thread Charles Kerr

** Changed in: indicator-datetime
 Assignee: Charles Kerr (charlesk) = Lars Uebernickel (larsu)

** Changed in: indicator-datetime
   Status: In Progress = Fix Released

** Changed in: indicator-datetime (Ubuntu)
 Assignee: (unassigned) = Lars Uebernickel (larsu)

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

Title:
  Some translations are not loaded

Status in The Date and Time Indicator:
  Fix Released
Status in Ubuntu Translations:
  Incomplete
Status in “indicator-datetime” package in Ubuntu:
  Fix Released

Bug description:
  The translations for some messages don't seem to be loaded. E.g.
  Tomorrow always appears in English in the list of upcoming events
  when sliding down the indicator.

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

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

2014-09-10 Thread Lucio Torre

current build number: 234
device name: mako
channel: ubuntu-touch/devel-proposed
alias: ubuntu-touch/utopic-proposed
last update: 2014-09-09 17:45:46
version version: 234
version ubuntu: 20140909
version device: 20140903.1
version custom: mako-0.3a

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

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.

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 1153488] Re: Treats bluetooth input device batteries as batteries

2014-09-10 Thread Andrew Gee

Same problem as in #43 above - bluetooth device showing 0% battery in
all Trusty kernels since 3.13.0-24, which was the last one to work.

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

Title:
  Treats bluetooth input device batteries as batteries

Status in “gnome-power-manager” package in Ubuntu:
  Invalid
Status in “upower” package in Ubuntu:
  Fix Released
Status in “gnome-power-manager” source package in Precise:
  Invalid
Status in “upower” source package in Precise:
  Fix Released
Status in “gnome-power-manager” source package in Quantal:
  Invalid
Status in “upower” source package in Quantal:
  Confirmed
Status in “gnome-power-manager” source package in Raring:
  Invalid
Status in “upower” source package in Raring:
  Fix Released
Status in “gnome-power-manager” source package in Saucy:
  Invalid
Status in “upower” source package in Saucy:
  Fix Released

Bug description:
  [Impact]

   * There are many Bluetooth devices with battery information inside.
  When they are treated as system battery, it will make the system
  poweroff/suspend/hibernate when some Bluetooth device has critical low
  battery. It is a very annoying behavior for the users. Originally,
  there is no such Bluetooth battery information until Ubuntu 12.04
  brings linux-quantal-lts and linux-raring-lts, so those linux kernels
  also bring this issue.

  [Test Case]

   * Pair some Bluetooth devices, such as Apple Wireless Mouse or Apple 
Wireless Keyboard.
   * Click the power indicator and you can find Apple Wireless Mouse is listed 
as system battery, and there is no Apple Wireless Keyboard. If you open 
gnome-power-statistics, you can find the 'Supply' field of Apple Wireless Mouse 
is 'Yes' but it should not be.

  [Regression Potential]

   * There is no obvious regression as I know.

  [Other Info]

   * Most patches are from upstream, modified to fix the conflicts, and made by 
the same developer (i.e. fourdollars).
   * We need another patch from 
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d0a934b764c67b4bf626f5b7cf725a6e3066afd2
 to make Apple Wireless Keyboard showing.

  [Original Bug Description]

  This is a weird one... the system is an HP Pavilion 23 All In One and
  is powered by a large power supply brick.

  I currently have an Apple Magic Mouse connected via Bluetooth.  As
  soon as the mouse is connected, the Battery indicator shows up and
  clicking on that shows that the system is reading my mouse as a
  battery!

  See the attached screen shot for what I see in the Power status.

  Looking at hcitool:
  ubuntu@201206-11396:~$ hcitool dev
  Devices:
   hci0 9C:B7:0D:80:71:DB

  To make matters even more weird, I actually observed the battery
  indicator go from full to Critically Low and the system suspended
  itself.  Keep in mind, again, that this system has NO battery, it's
  reading my bluetooth mouse as a battery device.

  I disconnected the magic mouse and the battery indicator went to Empty
  Red outline and status showed Battery Disconnected.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.5.0-23-generic 3.5.0-23.35~precise1
  ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2
  Uname: Linux 3.5.0-23-generic x86_64
  NonfreeKernelModules: wl fglrx
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Generic [HD-Audio Generic], device 0: ALC269VC Analog [ALC269VC 
Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Generic [HD-Audio Generic], device 0: ALC269VC Analog [ALC269VC 
Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1726 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Generic'/'HD-Audio Generic at 0xfeb4 irq 16'
     Mixer name : 'Realtek ALC269VC'
     Components : 'HDA:10ec0269,103c2aee,00100202'
     Controls  : 21
     Simple ctrls  : 10
  Date: Mon Mar 11 03:54:36 2013
  HibernationDevice: RESUME=UUID=ccd7a21f-7a71-4fa5-b95d-e2898c3dae24
  InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 
(20130213)
  MachineType: Hewlett-Packard a654
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic 
root=UUID=e2a5f4ae-dfa2-40be-a6c5-3ddb85dcf68e ro quiet splash initcall_debug 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-23-generic N/A
   linux-backports-modules-3.5.0-23-generic  N/A
   linux-firmware1.79.1
  SourcePackage: linux

[Touch-packages] [Bug 1251597] Re: Scope header sometimes appears in the middle of the scope

2014-09-10 Thread Lucio Torre

** Attachment added: app-scope.png
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1251597/+attachment/4200630/+files/app-scope.png

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

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.

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 1251597] Re: Scope header sometimes appears in the middle of the scope