date:20150806

** Branch linked: lp:~dobey/unity-scope-click/enable-parallel

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

Title:
  Parallel builds not enabled in packaging

Status in unity-scope-click package in Ubuntu:
  In Progress

Bug description:
  comparing build times

  https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/landing-039/+sourcepub/5269586/+listing-
  archive-extra

  and

  https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/landing-039/+sourcepub/5269911/+listing-
  archive-extra

  shows that the building is reduced by 50% on nearly every
  architecture.  buildd resources are still a scarce resource for some
  architectures. So please enable parallel builds here and on other
  touch packages.

  if you need a sequential build, you can enforce it locally by

DEB_BUILD_OPTIONS=parallel=1 dpkg-buildpackge ...

  patch at

  https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/landing-039/+files/unity-scope-
  
click_0.1.1%2B15.10.20150724-0ubuntu2~ppa2_0.1.1%2B15.10.20150724-0ubuntu2~ppa3.diff.gz

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

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

[Touch-packages] [Bug 1478026] Re: Never loads click preview again if first tried offline

2015-08-06 Thread Rodney Dawes

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

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

Title:
  Never loads click preview again if first tried offline

Status in unity-scope-click package in Ubuntu:
  In Progress

Bug description:
  Using a bq 4.5 on rc-proposed r76
  - boot with flight mode enabled
  - hold a tap on an icon to see its click preview

  - you get an empty screen bouncing forever

  - go back to the apps view
  - turn off flight mode/enable some data connection
  - try to open a click preview view

  - you still get the empty screen and never ending bouncing

  
  the unity8-dash.log has those errors

  Caught an error from preview(): unity::scopes::TimeoutException:
  Request timed out after 500 milliseconds (endpoint =
  ipc:///run/user/32011/zmq/priv/clickscope, op = debug_mode)

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

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

[Touch-packages] [Bug 1482401] [NEW] Race condition when removing read sms's from the indicator menu

2015-08-06 Thread Tiago Salem Herrmann

Public bug reported:


If messaging-app acknowledges the message even before the indicator receives 
it, the message will never be automatically removed from messaging-menu, as the 
event in history service is already marked as read and messaging-app will never 
ask to acknowledge that message again.

** Affects: canonical-devices-system-image
 Importance: High
 Assignee: Bill Filler (bfiller)
 Status: Confirmed

** Affects: telephony-service (Ubuntu)
 Importance: High
 Assignee: Tiago Salem Herrmann (tiagosh)
 Status: Confirmed

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

Title:
  Race condition when removing read sms's from the indicator menu

Status in Canonical System Image:
  Confirmed
Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  
  If messaging-app acknowledges the message even before the indicator receives 
it, the message will never be automatically removed from messaging-menu, as the 
event in history service is already marked as read and messaging-app will never 
ask to acknowledge that message again.

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

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

[Touch-packages] [Bug 1482198] Re: tab becomes white after loading

2015-08-06 Thread Thibaut Brandscheid

I tried to reproduce the bug, but now the page is displayed correctly.

 when the web page becomes white, the chrome (top bar with address bar, back 
 and forward buttons) remains visible
Yes, the address bar was visible and the action menu was clickable.

 If so, what happens if you focus the address bar and press Return on the OSK 
 to load the page again?
I did try to find out how to reload a web page, but couldn't find the action 
(too hidden). Therefore I can't tell what would have happened.

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

Title:
  tab becomes white after loading

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Ubuntu Touch (15.04 r3) Meizu MX4

  When clicking at a link in the Telegram app, the web browser open - as
  expected - a new tab and starts loading the web page. While loading
  the web page is visible. When loading is done, the web page become
  white. I tried to zoom in or out in the page but the page stays white.

  web page: http://www.heroesfire.com/hots/guide/azmodan-lord-of-sin-173

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

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

[Touch-packages] [Bug 1481733] Re: Kernel panic when booting with initramfs-tools version 0.120ubuntu1 generated initramfs

2015-08-06 Thread Daniel Winzen

Ok, I attached an archive with both, the old and the new initrd and 
update-initrd logs for comparison. 
To minimize the size, I uninstalled the linux-image-extra-* and linux-firmware 
packages, but the issue is still the same.

** Attachment added: initrd.tar.gz
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1481733/+attachment/4440666/+files/initrd.tar.gz

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

Title:
  Kernel panic when booting with initramfs-tools version 0.120ubuntu1
  generated initramfs

Status in initramfs-tools package in Ubuntu:
  In Progress

Bug description:
  After updating initramfs-tools to version 0.120ubuntu1 the kernel
  stops with a kernel panic during boot.

  …
  Begin Running /scripts/local-bottom...
  Begin Running /scripts/init-bottom...
  done.
  /init: exec: line 372: switch_root: not found
  Kernel panic - not syncing: Attempted to kill init! exitcode=0x0200
  …

  For the rest of the backtrace, see the attached image.

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

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

[Touch-packages] [Bug 1482401] Re: Race condition when removing read sms's from the indicator menu

2015-08-06 Thread Bill Filler

The side effect of this bug is when you have a messaging thread open and
receive a message from that person, you should not see a notification
appear. Currently sometimes you do see the notification incorrectly, but
it's not consistent.

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

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

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

** Changed in: telephony-service (Ubuntu)
 Assignee: (unassigned) = Tiago Salem Herrmann (tiagosh)

** Changed in: telephony-service (Ubuntu)
   Importance: Undecided = High

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

** Changed in: telephony-service (Ubuntu)
   Status: New = Confirmed

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

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

Title:
  Race condition when removing read sms's from the indicator menu

Status in Canonical System Image:
  Confirmed
Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  
  If messaging-app acknowledges the message even before the indicator receives 
it, the message will never be automatically removed from messaging-menu, as the 
event in history service is already marked as read and messaging-app will never 
ask to acknowledge that message again.

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

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

[Touch-packages] [Bug 1169054] Re: Disabling then Re-Enabling login without password does remove user from nopasswdlogin group

2015-08-06 Thread Arthur Tan

I think this should be changed to Fix Released after your merge proposal
was approved? Thanks Eric.

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

Title:
  Disabling then Re-Enabling login without password does remove user
  from nopasswdlogin group

Status in accountsservice package in Ubuntu:
  Confirmed

Bug description:
  I am using 12.04.

  Under System Settings, User Accounts, Passwords, Action, changing to
  Login without a password works as expected. On the next login,
  LightDM will not prompt you for a password, You can just login by
  hitting Enter.

  But, re-enabling password, or changing a password for the same user
  does not change LightDM behavior. LightDM does not re-enable asking
  for password at login.

  I think the problem is re-enabling password under Systems Settings
  does not delete user from nopasswdlogin group. You have to delete it
  from the command line:

  sudo gpasswd -d username nopasswdlogin

  This problem is the same ones described here:

  http://ubuntuforums.org/showthread.php?p=11566335

  http://askubuntu.com/questions/211084/how-do-i-get-ubuntu-to-ask-me-
  for-at-password-at-login-again/281615#281615

  http://askubuntu.com/questions/100010/no-password-asked-at-login-
  screen-just-start-session-button-with-lightdm

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

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

[Touch-packages] [Bug 1478026] Re: Never loads click preview again if first tried offline

** Branch linked: lp:~dobey/unity-scope-click/avoid-isrefundable

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

Title:
  Never loads click preview again if first tried offline

Status in unity-scope-click package in Ubuntu:
  Confirmed

Bug description:
  Using a bq 4.5 on rc-proposed r76
  - boot with flight mode enabled
  - hold a tap on an icon to see its click preview

  - you get an empty screen bouncing forever

  - go back to the apps view
  - turn off flight mode/enable some data connection
  - try to open a click preview view

  - you still get the empty screen and never ending bouncing

  
  the unity8-dash.log has those errors

  Caught an error from preview(): unity::scopes::TimeoutException:
  Request timed out after 500 milliseconds (endpoint =
  ipc:///run/user/32011/zmq/priv/clickscope, op = debug_mode)

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

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

[Touch-packages] [Bug 1408159] Re: [messaging] Too easy to delete whole conversation history with a contact

2015-08-06 Thread Olga Kemmet

Updated bug description with a design resolution. Marking as Won't Fix
as described behaviour is intended.

** Description changed:

  Steps:
  * open messaging app
  * drag one of the items on the list to the right
  * tap on the trash icon
  
  Expected:
  * only today's messages are removed or at least there's a confirmation dialog
  
  Current:
  * whole history of messaging with a contact is removed
  
  The fact that conversations are separated by days suggests as if a
  single item was a conversation within that day. But in fact they're
  complete conversations just ordered by date (which is actually different
  than the phone log, which *is* split by date, and removing an item there
  only affects a day's events).
  
  I wonder if it would be better to indeed show multiple entries for a
  single contact, in each day a message was sent either way, this being a
  shortcut to a certain message when opening. It feels like this would be
  better in the long run (imagine many years of messaging history). That
  might deserve another bug though.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: messaging-app 0.1+15.04.20141210-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.15-0ubuntu3
  Architecture: armhf
  Date: Wed Jan  7 00:06:35 2015
  InstallationDate: Installed on 2014-12-17 (20 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20141217-020204)
  SourcePackage: messaging-app
  UpgradeStatus: No upgrade log present (probably fresh install)
+ 
+ --- UX comment  resolution 
+ 
+ There is an active action of 
+ 1. dragging the list item in the conversation overview to the right
+ 2. tapping the delete icon
+ 
+ This means that there is already a two step interaction in place before
+ the message is deleted, hence no additional confirmation dialog is
+ needed. This would place an unnecessary 3rd step in place.
+ 
+ It wouldn't make much sense to delete just today's messages, because you
+ are removing the whole conversation. The behaviour of removing the whole
+ message with a contact is intended.

** Changed in: ubuntu-ux
   Status: Triaged = Won't Fix

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

Title:
  [messaging] Too easy to delete whole conversation history with a
  contact

Status in Ubuntu UX:
  Won't Fix
Status in messaging-app package in Ubuntu:
  New

Bug description:
  Steps:
  * open messaging app
  * drag one of the items on the list to the right
  * tap on the trash icon

  Expected:
  * only today's messages are removed or at least there's a confirmation dialog

  Current:
  * whole history of messaging with a contact is removed

  The fact that conversations are separated by days suggests as if a
  single item was a conversation within that day. But in fact they're
  complete conversations just ordered by date (which is actually
  different than the phone log, which *is* split by date, and removing
  an item there only affects a day's events).

  I wonder if it would be better to indeed show multiple entries for a
  single contact, in each day a message was sent either way, this being
  a shortcut to a certain message when opening. It feels like this would
  be better in the long run (imagine many years of messaging history).
  That might deserve another bug though.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: messaging-app 0.1+15.04.20141210-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.15-0ubuntu3
  Architecture: armhf
  Date: Wed Jan  7 00:06:35 2015
  InstallationDate: Installed on 2014-12-17 (20 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20141217-020204)
  SourcePackage: messaging-app
  UpgradeStatus: No upgrade log present (probably fresh install)

  --- UX comment  resolution 

  There is an active action of 
  1. dragging the list item in the conversation overview to the right
  2. tapping the delete icon

  This means that there is already a two step interaction in place
  before the message is deleted, hence no additional confirmation dialog
  is needed. This would place an unnecessary 3rd step in place.

  It wouldn't make much sense to delete just today's messages, because
  you are removing the whole conversation. The behaviour of removing the
  whole message with a contact is intended.

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

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

[Touch-packages] [Bug 1478217] Re: can't pair bluetooth keyboard, phone doesn't show code.

2015-08-06 Thread Raymond

Same bug as described by Hugo, Aquaris E4.5 Ubuntu edition and Logik
bluetooth keyboard(LKBUBT13)

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

Title:
  can't pair bluetooth keyboard, phone doesn't show code.

Status in indicator-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  1) Device: Meizu MX4 Ubuntu Edition
   OS: Ubuntu 15.04 (r68) - armhf (20150724-020304)
  2) Bluez version 4.101-0ubuntu25
   indicator-bluetooth version 0.0.6+14.10.20141006-0ubuntu1

  3) When trying to connect a bluetooth keyboard (SilverCrest SBT 3.0 A1), 
pairing doesn't follow correct procedure.
  On other devices (Android 5.1.1 on Nexus 10; Ubuntu 15.04 on BTO laptop) a 6 
digit number is displayed, which needs to be typed on the Bluetooth keyboard, 
followed by pressing [Enter].

  4) On Ubuntu touch, a dialogue appears asking to enter a 4 digit PIN
  on the phone. Default is '' and at first the phone says the device
  is connected, but the phone does not respond to any input from the
  keyboard. After some time the phone indicates the device is not
  connected.

  All of this is similarly described in this askubuntu article:
  http://askubuntu.com/questions/625533/how-to-pair-external-bluetooth-
  keyboard-to-ubuntu-touch-bq-phone, which has not received any answers
  as of yet.

  I am willing to follow instructions and report back results. i have
  adb shell installed on my laptop, and Terminal app installed on the
  phone. Developer mode is on.

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

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

[Touch-packages] [Bug 1482148] Re: Unlock 2 SIMs with PIN enabled

2015-08-06 Thread Jonas G. Drange

Thank you for your report. The SIM unlock dialog after a reboot is
managed by indicator-network.

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

** No longer affects: ubuntu-system-settings (Ubuntu)

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

Title:
  Unlock 2 SIMs with PIN enabled

Status in indicator-network package in Ubuntu:
  New

Bug description:
  system-image-cli -i
  current build number: 165
  device name: krillin
  channel: ubuntu-touch/devel-proposed/krillin.en
  last update: 2015-08-05 08:22:08
  version version: 165
  version ubuntu: 20150802
  version device: 20150716-fb60d96
  version custom: 20150717-820-30-25-vivid

  reproduce steps:
  1.2 SIMs inserted with PIN lock enabled
  2.Boot phone and wait for PIN entry dialog
  3.Enter correct PIN for SIM1
  4.Enter correct PIN for SIM2
  5.unlock the  screen observe the status about the 2 SIMs card on the 
indicator bar

  expect result:
  2 SIMs card both unlocked and have service
  actual result:
  SIM1  was unlocked,while SIM2 not unlock after input the correct PIN.

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

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

[Touch-packages] [Bug 1267184] Re: [Apps Scope] apps that are being downloaded/installed are not shown differently from un-installed apps

2015-08-06 Thread Paty Davila

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

** Description changed:

  If a user chooses to install an app but doesn't stay on the app preview
  while it downloads and installs (or the device sleeps in the meantime),
  when they see the list of apps, the app that is being downloaded is
  still shown as un-installed, with no distinction made.
  
  This needs design input - some platforms show the app in the list of
  'installed apps' (eg iOS home screen) but have a progress bar or some
  other badge to show that it's not ready to run yet.
  
  This affects both unity8 and the scope because there will be additional
  state for the scope to send to the dash in the apps list results.
  
  -- UX Comment --
  
- This is part of a bigger redesign project (Scopes toolkit) and it can't
- be fixed as a single bug. The desired resolution and specs will be
- updated as soon as they are available.
+ The desired solution (although temporary) will be creating a new
+ category in the Apps scope to display all new/recently installed apps.
+ They can live there until the user launch them for the first time (or
+ move them to a user custom created section, once this functionality is
+ implemented). After this (ie. a week), they will appear on the 'All'
+ apps category displayed by alphabetical order.

** This bug has been marked a duplicate of bug 1388179
   [scopes] + [dash] After installing a new app, there's no obvious way to 
launch it

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

Title:
  [Apps Scope] apps that are being downloaded/installed are not shown
  differently from un-installed apps

Status in Ubuntu UX:
  In Progress
Status in unity-scope-click package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu RTM:
  Incomplete

Bug description:
  If a user chooses to install an app but doesn't stay on the app
  preview while it downloads and installs (or the device sleeps in the
  meantime), when they see the list of apps, the app that is being
  downloaded is still shown as un-installed, with no distinction made.

  This needs design input - some platforms show the app in the list of
  'installed apps' (eg iOS home screen) but have a progress bar or some
  other badge to show that it's not ready to run yet.

  This affects both unity8 and the scope because there will be
  additional state for the scope to send to the dash in the apps list
  results.

  -- UX Comment --

  The desired solution (although temporary) will be creating a new
  category in the Apps scope to display all new/recently installed apps.
  They can live there until the user launch them for the first time (or
  move them to a user custom created section, once this functionality is
  implemented). After this (ie. a week), they will appear on the 'All'
  apps category displayed by alphabetical order.

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

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

[Touch-packages] [Bug 1226962] Re: Hotkeys not functional in non-latin keyboard layout

2015-08-06 Thread Alberto Salvia Novella

** Summary changed:

- Hotkeys not functional in non-latin keyboard layout in 13.10, 14.04, 14.04.1, 
14.10, 15.04
+ Hotkeys not functional in non-latin keyboard layout

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

Title:
  Hotkeys not functional in non-latin keyboard layout

Status in aptana-studio-installer:
  New
Status in Default settings and artwork for Baltix OS:
  New
Status in LibreOffice Productivity Suite:
  Fix Released
Status in ibus:
  New
Status in Indicator keyboard:
  Fix Released
Status in Inkscape:
  New
Status in monodevelop:
  New
Status in mutter:
  Fix Released
Status in okular:
  New
Status in OpenOffice:
  New
Status in sigram:
  New
Status in Unity:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-terminal package in Ubuntu:
  Triaged
Status in openjdk-7 package in Ubuntu:
  Incomplete
Status in unity package in Ubuntu:
  Triaged
Status in unity-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-settings-daemon package in Fedora:
  Unknown
Status in gnome-shell package in Fedora:
  Unknown

Bug description:
  New keyboard layout changer in Ubuntu 13.10 introduce  old-new bug. Any 
system or application hotkey witch use char (for example: ctrl+alt+t for 
terminal or ctrl+t for new tab in browser) become unfunctional when selected 
non-latin keyboard layout.
  Hotkeys with F1-12, numbers and other non-character buttons works perfectly.

  Window manager hotkeys not affected by this bug. All hotkeys in system
  parameters-keyboard-hotkeys-windows works perfect with any keyboard
  layout.

  Workaround for some system hotkeys and two layouts (english and non-
  latin): rebind all hotkeys in your local layout. For example instead
  of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with
  english layout.  If you use english and two different non-latin
  layouts this workaround helps only with one of them.


  Dear Ubuntu users and developers! 
  Please include the following information to your comment about non-latin 
shortcuts problems:
  1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 
14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean 
installed
  2. What keyboard layout do you have
  3. What shortcut for keyboard layout switching do you use 
  4. On which session you have problems - that is one from Unity, GNOME Shell, 
GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz)
  5. With which program and its version and origin (Ubuntu repositories, PPA, 
non-deb binary package from some website) you have problems.

  By providing this information you can make bug-fixing much simpler and
  may be faster.

  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

To manage notifications about this bug go to:
https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+subscriptions

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

[Touch-packages] [Bug 1450894] Re: [Indicators] Messaging indicator does not indicate that there is a new message

2015-08-06 Thread Matthew Paul Thomas

So according to the usability test, 7/11 participants failed to
interpret the meaning of blue.

How many interpreted the meaning of green? Was it any better?

I'd be surprised if Michael quoted above, for example, would say: I
don't know why it would need to be blue ... but green, green makes sense
to me.

Or if Hansie would change his belief that The fact that it is present
indicates there is something there for me to do merely because it was
sometimes green rather than sometimes blue (if he even saw that happen).

If the logic is, the menu is where we list notifications, therefore the
indicator has to be there all the time, therefore we need to use visual
design to distinguish new messages received or not, then maybe the
premise is wrong.

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

Title:
  [Indicators] Messaging indicator does not indicate that there is a new
  message

Status in Canonical System Image:
  Fix Released
Status in Ubuntu theme:
  Fix Released
Status in Ubuntu UX:
  Fix Released
Status in indicator-messages package in Ubuntu:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  When you receive a message the indicator menu turns from opaque to
  full white to indicate that there is a new message. But this is not
  clear since all the other icons are white and you do not see any
  difference.

  This is very confuse to understand that the indicator is in a
  different state from the other indicators or if it needs attention.

  --DESIGN RESOLUTION---

  Please use the current ubuntu theme green to indicate that there is a
  new message - #3FB24F, the same green as we use for the battery icon
  in indicators.

  Change the LED light to green as well.

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

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

[Touch-packages] [Bug 1481834] Re: App background should be white by default, without texture

2015-08-06 Thread Jouni Helminen

** Attachment removed: dekko_phone1.jpg
   
https://bugs.launchpad.net/ubuntu-ux/+bug/1481834/+attachment/4440324/+files/dekko_phone1.jpg

** Attachment added: dekko_meizu.jpg
   
https://bugs.launchpad.net/ubuntu-ux/+bug/1481834/+attachment/4440325/+files/dekko_meizu.jpg

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

Title:
  App background should be white by default, without texture

Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  The background of apps should be white by default. When discussed with
  timp on IRC, it is currently defined at EDEDED - please change to
  FF.

  Tim also mentioned there is still some texture by default on app
  background - please remove this

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

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

[Touch-packages] [Bug 1473756] Re: New Upstream version 0.25

2015-08-06 Thread dino99

exiv2 (0.25-1ubuntu1) wily; urgency=medium

  * Temporarily drop the broken .symbols file. It was just introduced in
0.25.1, but needs to be adjusted for all architectures.

 -- Martin Pitt martin.p...@ubuntu.com  Wed, 05 Aug 2015 16:59:51
+0200

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

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

Title:
  New Upstream version 0.25

Status in exiv2 package in Ubuntu:
  Fix Released
Status in exiv2 package in Debian:
  Fix Released

Bug description:
  version 0.25 of exiv2 was released a few weeks ago.
  http://exiv2.org/whatsnew.html

  It contains a large collection of new features, new lenses and
  bugfixes across all areas ...

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

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

[Touch-packages] [Bug 1330939] Re: [sdk] Cards force background when summary is added

2015-08-06 Thread Magdalena Mirowicz

** Changed in: ubuntu-ux
 Assignee: Olga Kemmet (olga-kemmet) = Alex Milazzo (digitalalex)

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

Title:
  [scopes toolkit] Cards force background when summary is added

Status in The Savilerow project:
  Triaged
Status in Ubuntu UX:
  Triaged
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Using:
  {
  schema-version : 1,
  template : {
  category-layout : grid,
  card-size: large,
  overlay: false
  },
  components : {
  title : category,
  summary:summary,
  art : {
  field: art2,
  aspect-ratio: 1.4,
  fill-mode: fit
  }
  }
  }

  A white frame appears around the card. If the summary is remove, the
  white frame goes away. Checked with John Lea and this is not as
  intended by design

  --
  Solution

  Default background should be transparent

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

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

[Touch-packages] [Bug 1481671] Re: [mos] rsyslog periodically crashes with * glibc detected * rsyslogd: double free or corruption (fasttop) preventing log into the system

2015-08-06 Thread Andrey Bubyr

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

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

Title:
  [mos] rsyslog periodically crashes with *** glibc detected ***
  rsyslogd: double free or corruption (fasttop)  preventing log into the
  system

Status in Mirantis OpenStack:
  Incomplete
Status in rsyslog package in Ubuntu:
  New

Bug description:
  Rsyslog crashes every 10-14 days on MogoDB nodes with coredump in 
/var/log/messages:
  46Aug  4 15:01:56 node-115 rsyslogd: rsyslogd's groupid changed to 103
  46Aug  4 15:01:56 node-115 rsyslogd: rsyslogd's userid changed to 101
  6Aug  4 15:02:12 node-115 kernel: imklog 5.8.6, log source = /proc/kmsg 
started.
  46Aug  4 15:02:12 node-115 rsyslogd: [origin software=rsyslogd 
swVersion=5.8.6 x-pid=58757 x-info=http://www.
  rsyslog.com] start
  46Aug  4 15:02:12 node-115 rsyslogd: rsyslogd's groupid changed to 103
  46Aug  4 15:02:12 node-115 rsyslogd: rsyslogd's userid changed to 101
  6Aug  4 15:02:13 node-115 kernel: imklog 5.8.6, log source = /proc/kmsg 
started.
  46Aug  4 15:02:13 node-115 rsyslogd: [origin software=rsyslogd 
swVersion=5.8.6 x-pid=58773 x-info=http://www.
  rsyslog.com] start
  46Aug  4 15:02:13 node-115 rsyslogd: rsyslogd's groupid changed to 103
  46Aug  4 15:02:13 node-115 rsyslogd: rsyslogd's userid changed to 101
  6Aug  4 15:02:21 node-115 kernel: imklog 5.8.6, log source = /proc/kmsg 
started.
  46Aug  4 15:02:21 node-115 rsyslogd: [origin software=rsyslogd 
swVersion=5.8.6 x-pid=58788 x-info=http://www.
  rsyslog.com] start
  46Aug  4 15:02:21 node-115 rsyslogd: rsyslogd's groupid changed to 103
  46Aug  4 15:02:21 node-115 rsyslogd: rsyslogd's userid changed to 101
  *** glibc detected *** rsyslogd: double free or corruption (fasttop): 
0x7f5e88032100 ***
  === Backtrace: =
  /lib/x86_64-linux-gnu/libc.so.6(+0x7e846)[0x7f5ea2101846]
  rsyslogd[0x42ee36]
  rsyslogd[0x431697]
  rsyslogd[0x431ce7]
  rsyslogd(wtiWorker+0xc3)[0x42b513]
  rsyslogd[0x42a78a]
  /lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x7f5ea2855e9a]
  /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f5ea217731d]
  === Memory map: 
  0040-00456000 r-xp  08:03 8132346
/usr/sbin/rsyslogd
  00656000-00658000 r--p 00056000 08:03 8132346
/usr/sbin/rsyslogd
  00658000-0065e000 rw-p 00058000 08:03 8132346
/usr/sbin/rsyslogd
  0065e000-0065f000 rw-p  00:00 0
  00f18000-00f39000 rw-p  00:00 0  
[heap]
  00f39000-00f7b000 rw-p  00:00 0  
[heap]
  7f5e8400-7f5e8404 rw-p  00:00 0
  7f5e8404-7f5e8800 ---p  00:00 0
  7f5e8800-7f5e88043000 rw-p  00:00 0
  7f5e88043000-7f5e8c00 ---p  00:00 0
  7f5e8c00-7f5e8c1eb000 rw-p  00:00 0
  7f5e8c1eb000-7f5e9000 ---p  00:00 0
   ... memory map ... 
  Full memory map could be found in attached 'messages' log.
  When rsyslog crashes in this manner it is impossible to login into the 
system. Process /bin/login successfully authenticates user, but does not born 
shell process, constantly waiting for rsyslog reading login log message from 
Unix socket.

  Obviously Fuel master reports that node in 'False' state (because it
  becomes non-sshable too).

  Workaround: fully restart rsyslog after crash (service rsyslog
  restart) if some active login session is present or reboot the server
  if not.

  MOS 6.0, Ubuntu 12.04. Rsyslog v. 5.8.6 (from Fuel node repos).
  Rsyslog config files placed in rsyslog folder of attached archive.

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

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

[Touch-packages] [Bug 1450894] Re: [Indicators] Messaging indicator does not indicate that there is a new message

2015-08-06 Thread Matthieu James

Note that apart from the colour, the designs of the icons used for the two 
states of the indicator (no new message / new message) are different since the 
last update: outline / solid envelope.
This might help to differentiate the two states.

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

Title:
  [Indicators] Messaging indicator does not indicate that there is a new
  message

Status in Canonical System Image:
  Fix Released
Status in Ubuntu theme:
  Fix Released
Status in Ubuntu UX:
  Fix Released
Status in indicator-messages package in Ubuntu:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  When you receive a message the indicator menu turns from opaque to
  full white to indicate that there is a new message. But this is not
  clear since all the other icons are white and you do not see any
  difference.

  This is very confuse to understand that the indicator is in a
  different state from the other indicators or if it needs attention.

  --DESIGN RESOLUTION---

  Please use the current ubuntu theme green to indicate that there is a
  new message - #3FB24F, the same green as we use for the battery icon
  in indicators.

  Change the LED light to green as well.

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

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

[Touch-packages] [Bug 1330939] Re: [scopes toolkit] Cards force background when summary is added

2015-08-06 Thread Alex Milazzo

There is already a desired solution in the description. Not ideal but
for now is ok. This is part of a bigger redesign project (Scopes
toolkit) and it can't be fixed as a single bug.

** Changed in: ubuntu-ux
   Status: Triaged = Fix Committed

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

Title:
  [scopes toolkit] Cards force background when summary is added

Status in The Savilerow project:
  Triaged
Status in Ubuntu UX:
  Fix Committed
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Using:
  {
  schema-version : 1,
  template : {
  category-layout : grid,
  card-size: large,
  overlay: false
  },
  components : {
  title : category,
  summary:summary,
  art : {
  field: art2,
  aspect-ratio: 1.4,
  fill-mode: fit
  }
  }
  }

  A white frame appears around the card. If the summary is remove, the
  white frame goes away. Checked with John Lea and this is not as
  intended by design

  --
  Solution

  Default background should be transparent

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

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

[Touch-packages] [Bug 1481920] Re: gallery app opens empty

2015-08-06 Thread Víctor R . Ruiz

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

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

Title:
  gallery app opens empty

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

Bug description:
  Test case.
  - Flash the phone with latest image.
  - Open the gallery app.

  Expected result.
  - Gallery app opens and shows title, menus, etc.

  Actual result.
  - No UI is presented.

  current build number: 87
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en

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

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

[Touch-packages] [Bug 1330904] Re: carousel shadows do not resize

2015-08-06 Thread Andrea Cimitan

I am fixing this while fixing another bug...

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

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

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) = Andrea Cimitan (cimi)

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

Title:
  carousel shadows do not resize

Status in The Savilerow project:
  Invalid
Status in Unity 8:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  using the following schema to render a carousel category
  {
  schema-version: 1,
  template: {
  category-layout: carousel,
  card-size: small,
  overlay: true,
},
  components: {
  title : title2,
  art: {
  field: art2,
  aspect-ratio: 1,
  fill-mode: fit
  }
  }
  }

  Changing the aspect ratio from 1 to 1.5 resize the images but not the
  shade in the phone. This works fine in the fakenev tool.

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

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

[Touch-packages] [Bug 1350891] Re: [Scopes][UX] Suru Background should scroll

2015-08-06 Thread Andrea Cimitan

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

Title:
  [Scopes][UX] Suru Background should scroll

Status in Canonical System Image:
  Invalid
Status in Ubuntu Clock App:
  Incomplete
Status in Ubuntu UX:
  Fix Released
Status in unity8 package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu RTM:
  Invalid

Bug description:
  On the dash, the Suru paper folds stays fixed at the bottom, while it
  should rather scroll away.

  We should also 'tile' the background, so the paper fold is displayed
  again after scrolling a certain amount of vertical space.

  --

  Desired resolution:

  Background must be fixed

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

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

[Touch-packages] [Bug 1463606] Re: [dialer-app]+[address-book] back button

2015-08-06 Thread Olga Kemmet

Bug description contains desired solution, hence marking as Fix
Committed from design.

** Description changed:

  Step to replay:
  
  - Open the phone app;
  - Do a tap to the contacts icon in the top right corner;
  - Do research and choose a contact with multiple phone numbers;
  - Do a tap on one of the numbers - you return to the phone app and you are 
ready to be a call;
  - There is no direct way to return to the previous contact card opened (for 
example to change number if it is busy or to call alternative number) without 
repeating the search again.
  
  It would be useful to have a button to return to the phone app that
  makes return to the open contact to call a different number (or send an
  SMS / e-mail)
+ 
+ -- UX comment ---
+ 
+ The solution is as follows:
+ 1. open dialer
+ 2. tap on the contacts in the top right corner in the header
+ 3. find a contact and tap it to go into the contact card
+ 4. tap a number to call
+ 5. view returns to the dialer with the pre-populated number
+ 6. do not tap call!
+ 7. now tap again the contacts icon in the top right corner in the header
+ 8. view should show you the previously opened contacts card
+ 
+ Additional desired behaviours: 
+ If user taps the back button in the contact card, screen goes back to list of 
contacts. 
+ If user initiated a call, then tapping the back button from the calling 
screen goes back to the keypad (indicator bar turns green, to show user there 
is an active call happening). A tap on the contacts icon in the top right 
corner in the header from this view shows user the last opened contact card.

** Description changed:

  Step to replay:
  
  - Open the phone app;
  - Do a tap to the contacts icon in the top right corner;
  - Do research and choose a contact with multiple phone numbers;
  - Do a tap on one of the numbers - you return to the phone app and you are 
ready to be a call;
  - There is no direct way to return to the previous contact card opened (for 
example to change number if it is busy or to call alternative number) without 
repeating the search again.
  
  It would be useful to have a button to return to the phone app that
  makes return to the open contact to call a different number (or send an
  SMS / e-mail)
  
  -- UX comment ---
  
  The solution is as follows:
  1. open dialer
  2. tap on the contacts in the top right corner in the header
  3. find a contact and tap it to go into the contact card
  4. tap a number to call
  5. view returns to the dialer with the pre-populated number
  6. do not tap call!
  7. now tap again the contacts icon in the top right corner in the header
  8. view should show you the previously opened contacts card
  
- Additional desired behaviours: 
- If user taps the back button in the contact card, screen goes back to list of 
contacts. 
+ Additional desired behaviours:
+ If user taps the back button in the contact card, screen goes back to list of 
contacts.
  If user initiated a call, then tapping the back button from the calling 
screen goes back to the keypad (indicator bar turns green, to show user there 
is an active call happening). A tap on the contacts icon in the top right 
corner in the header from this view shows user the last opened contact card.
+ 
+ Please refer to this spec for the latest UX:
+ 
https://docs.google.com/document/d/1BRy9-DEXr3A1D7PHkJaXmjbe7xbRmxKkzANXuu-F6lc/edit

** Changed in: ubuntu-ux
   Status: Triaged = Fix Committed

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

Title:
  [dialer-app]+[address-book] back button

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  Fix Committed
Status in address-book-app package in Ubuntu:
  New
Status in dialer-app package in Ubuntu:
  New

Bug description:
  Step to replay:

  - Open the phone app;
  - Do a tap to the contacts icon in the top right corner;
  - Do research and choose a contact with multiple phone numbers;
  - Do a tap on one of the numbers - you return to the phone app and you are 
ready to be a call;
  - There is no direct way to return to the previous contact card opened (for 
example to change number if it is busy or to call alternative number) without 
repeating the search again.

  It would be useful to have a button to return to the phone app that
  makes return to the open contact to call a different number (or send
  an SMS / e-mail)

  -- UX comment ---

  The solution is as follows:
  1. open dialer
  2. tap on the contacts in the top right corner in the header
  3. find a contact and tap it to go into the contact card
  4. tap a number to call
  5. view returns to the dialer with the pre-populated number
  6. do not tap call!
  7. now tap again the contacts icon in the top right corner in the header
  8. view should show you the previously opened contacts card

  Additional desired behaviours:
  If

[Touch-packages] [Bug 1478075] Re: Sound indicator should only indicate ringtone volume

2015-08-06 Thread Matthew Paul Thomas

Per spec, if an app/game is playing sounds but not music, that is the
alert output role. As long as an alarm is not sounding, a phone call
is not in progress, and you're not playing music some other way, all
volume controls should adjust the volume of that app's sounds.
https://wiki.ubuntu.com/Sound#primary-output

In other words, if apps obey the media volume setting for things that
aren't music/video, that's probably a bug.

I just realized that when I added output roles to the spec, I updated
the design for the System Settings slider and the volume buttons, but I
neglected to update the design for the indicator slider to match. Spec
updated. https://wiki.ubuntu.com/Sound?action=diffrev2=148rev1=147
But that doesn't seem to be related to this bug report, and I still have
no reason to think that this bug report is valid.

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

Title:
  Sound indicator should only indicate ringtone volume

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  Incomplete
Status in indicator-sound package in Ubuntu:
  Incomplete

Bug description:
  On the phone, the volume indicator follows the current active stream
  volume (music, alarm etc.) to show and control via slider and/or
  volume buttons.

  The indicator icon and slider should only ever follow the ringtone
  volume. I'm not sure whether volume buttons should work for alarms.

  This is somewhat related to bug #1291458.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: indicator-sound 12.10.2+15.04.20150508-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ActionStates: ({'mediaplayer-app.desktop.greeter': (true, signature '', 
[{'running': false, 'state': 'Paused'}]), 'mute': (true, '', [false]), 
'phone-settings': (true, '', []), 'mic-volume': (true, '', [1.0]), 'scroll': 
(true, 'i', []), 'high-volume': (true, '', [false]), 
'play-playlist.mediaplayer-app.desktop': (true, 's', []), 'desktop-settings': 
(true, '', []), 'mediaplayer-app.desktop': (true, '', [{'running': false, 
'state': 'Paused'}]), 'play.mediaplayer-app.desktop': (true, '', 
['Paused']), 'volume': (true, 'i', [0.7414398193359375]), 
'next.mediaplayer-app.desktop': (true, '', []), 'indicator-shown': (true, '', 
[false]), 'root': (true, '', [{'title': 'Dźwięk', 'accessible-desc': 
'Głośność (74%)', 'icon': ('themed', ['audio-volume-high-panel', 
'audio-volume-high', 'audio-volume', 'audio']), 'visible': true}]), 
'silent-mode': (true, '', [false]), 'previous.mediaplayer-app.desktop': 
(true, '', [])},)
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: armhf
  Date: Fri Jul 24 18:07:15 2015
  InstallationDate: Installed on 2015-07-23 (1 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20150723-020304)
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1438254] Re: [address-book] No way to remove contact avatar

2015-08-06 Thread Olga Kemmet

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

Same bug as https://bugs.launchpad.net/ubuntu-ux/+bug/1438254
Marking as Won't Fix and as a duplicate

** Summary changed:

- No way to remove contact avatar
+ [address-book] No way to remove contact avatar

** Changed in: ubuntu-ux
   Status: Triaged = Won't Fix

** This bug has been marked a duplicate of bug 1471309
   [address book] Impossible to delete a photo of a contact

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

Title:
  [address-book] No way to remove contact avatar

Status in Ubuntu UX:
  Won't Fix
Status in address-book-app package in Ubuntu:
  Triaged

Bug description:
  I can add an avatar for a contact but I have not been able to find a
  way to remove that. Please implement a way to remove avatar for a
  contact.

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

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

[Touch-packages] [Bug 1481834] Re: App background should be white by default, without texture

2015-08-06 Thread Michal Predotka

Thank you for the answer.

On the image I see only the header background is #FF. The list items
background (most of the screen in this case) seems to be #FDFDFD.

I believe pure white (FF) as background colour is more tiring to
the eyes than what we have now as the default. Maybe consider going with
something in-between and make the text colour more black.

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

Title:
  App background should be white by default, without texture

Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  The background of apps should be white by default. When discussed with
  timp on IRC, it is currently defined at EDEDED - please change to
  FF.

  Tim also mentioned there is still some texture by default on app
  background - please remove this

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

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

[Touch-packages] [Bug 1330939] Re: [sdk] Cards force background when summary is added

2015-08-06 Thread Yuan-Chen Cheng

** Changed in: savilerow
   Status: New = Triaged

** Tags added: tracking

** Changed in: savilerow
   Importance: Undecided = Medium

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

Title:
  [sdk] Cards force background when summary is added

Status in The Savilerow project:
  Triaged
Status in Ubuntu UX:
  Triaged
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Using:
  {
  schema-version : 1,
  template : {
  category-layout : grid,
  card-size: large,
  overlay: false
  },
  components : {
  title : category,
  summary:summary,
  art : {
  field: art2,
  aspect-ratio: 1.4,
  fill-mode: fit
  }
  }
  }

  A white frame appears around the card. If the summary is remove, the
  white frame goes away. Checked with John Lea and this is not as
  intended by design

  --
  Solution

  Default background should be transparent

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

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

[Touch-packages] [Bug 1440608] Re: /etc/kernel/postinst.d/apt-auto-removal wants to remove all kernels except the latest one

2015-08-06 Thread Cavsfan

How can you run that when 
'''
/etc/kernel/postinst.d/apt-auto-removal 
'''
is automagically run at the end of  
'''
entering sudo apt-get purge 4 kernel modules. 
...
let alone when auto-remove is run.
'''
you will never get the chance.

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

Title:
  /etc/kernel/postinst.d/apt-auto-removal wants to remove all kernels
  except the latest one

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  After installing a 3rd kernel currently 3.19.0-12-generic, the
  /etc/apt/apt.conf.d/01autoremove-kernels file looks normal listing the
  3.19.0-11-generic and 3.19.0-12-generic with 3.19.0-10-generic listed
  to be autoremoved. But once autoremove is completed the machine
  requests to be rebooted and at that time the /etc/apt/apt.conf.d
  /01autoremove-kernels file lists the 3.19.0-12-generic and
  3.19.0-10-generic kernels. So upon rebooting the 3.19.0-11-generic is
  requested to be autoremoved leaving only one kernel the latest one
  3.19.0-12-generic.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: apt 1.0.9.7ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Apr  5 17:03:01 2015
  InstallationDate: Installed on 2015-04-02 (3 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 Vivid Vervet - Beta amd64 (20150401)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1309141] Re: Apt is missing tab complete on things like list search etc

2015-08-06 Thread Mathew Hodson

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

** Bug watch removed: alioth.debian.org/ #314652
   http://alioth.debian.org/support/tracker.php?aid=314652

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

Title:
  Apt is missing tab complete on things like list search etc

Status in One Hundred Papercuts:
  New
Status in apt package in Ubuntu:
  In Progress
Status in apt package in Debian:
  New

Bug description:
  Before I could do apt-gtab upgrtab and hit enter and be done

  With the new apt I can nolonger do this instead I have to type in apt
  search/list/update/upgrade/full-upgrade etc

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apt 1.0.1ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 17 19:30:35 2014
  InstallationDate: Installed on 2014-04-17 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1475205] Re: Random Chinese character missing with Ubuntu font

2015-08-06 Thread Jason Yen

@Ethan,

Please help to verify this fix with arale. Thanks.

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

Title:
  Random Chinese character missing with Ubuntu font

Status in Canonical System Image:
  In Progress
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in qtdeclarative-opensource-src package in Ubuntu:
  Invalid
Status in ubuntu-font-family-sources package in Ubuntu:
  Incomplete
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid

Bug description:
  After applied 50 GU setting in image, we started seeing randomly
  missing Chinese characters across scopes and apps header, not clipped
  at the begin or end of string, sometimes in the middle.

  STEPS:

  1. Switch display language to zh_CN in system settings
  2. Reboot the phone

  EXPECTED:

  I should see all header strings displayed properly.

  ACTUAL:

  Randomly missing character.

  VERSIONS:

  current build number: 51
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.zh-proposed
  last update: 2015-07-16 04:59:10
  version version: 51
  version ubuntu: 20150716
  version device: 20150709-8965e37
  version custom: 20150716-819-9-6

  -- update --
  The problem of missing characters can be reproduced even on a desktop, 
outside of the header, without importing Ubuntu.Components:

  import QtQuick 2.0
  Item {
  width: 800
  height: 600

  Text {
  anchors.centerIn: parent
  text: 系统设置 one two
  font.family: Ubuntu
  font.pixelSize: 69
  font.weight: Font.Light
  }
  }

  The problem only appears to occur with this specific combination of
  font family, pixelSize and weight. Tim Peeters reproduced the problem
  on vivid on a laptop without changing the default settings for the
  language (LANGUAGE=en_US).

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

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

[Touch-packages] [Bug 1481913] Re: UI volume warnings need revision

** Branch linked: lp:~unity-api-team/indicator-sound/lp-1481913-revised-
ui-volume-warnings

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

Title:
  UI volume warnings need revision

Status in Canonical System Image:
  Confirmed
Status in indicator-sound package in Ubuntu:
  Confirmed

Bug description:
  As raised in OEM bug #1474364 (the title there is poor), the warning
  scheme used by Ubuntu does not currently follow the letter of the EU
  regulations for mobile devices (it seems to follow the spirit).

  Design have now reviewed the regulations (bug #1480912), and propose:

  https://wiki.ubuntu.com/Sound#limits

  This is the diff:
  https://wiki.ubuntu.com/Sound?action=diffrev2=146rev1=145

  The UI notification scheme needs to be updated to match the new
  design.

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

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

[Touch-packages] [Bug 1473934] Re: ISST-LTE: pmac-fdisk doesn't work with mpath devices

2015-08-06 Thread bugproxy

--- Comment on attachment From ckuma...@in.ibm.com 2015-07-13 14:13 
EDT---


strace -e open fdisk -l
strace -e open fdisk -l /dev/mapper/mpath0

Both commands gives same results (reading only /dev/sdx and /dev/hdx)
and in unable to read multipath disk. And looking at code it seems it is
meant to be so.

root@dilllp1:/# ll /dev/mapper/
total 0
drwxr-xr-x  2 root root  400 Jul 12 21:03 ./
drwxr-xr-x 13 root root 6400 Jul 12 21:03 ../
crw---  1 root root  10, 236 Jul 12 20:46 control
lrwxrwxrwx  1 root root7 Jul 13 08:41 mpath0 - ../dm-0
brw---  1 root root 252,   6 Jul 12 20:46 mpath0-part1
brw---  1 root root 252,   7 Jul 12 20:46 mpath0-part2
brw---  1 root root 252,   8 Jul 12 20:46 mpath0-part3
lrwxrwxrwx  1 root root7 Jul 12 20:47 mpath1 - ../dm-1
brw---  1 root root 252,   9 Jul 12 20:46 mpath1-part1
brw---  1 root root 252,  11 Jul 12 20:46 mpath1-part2
lrwxrwxrwx  1 root root7 Jul 12 20:54 mpath2 - ../dm-2
brw-rw  1 root disk 252,  16 Jul 12 20:47 mpath2-part1
brw-rw  1 root disk 252,  17 Jul 12 20:47 mpath2-part2
lrwxrwxrwx  1 root root7 Jul 12 21:03 mpath3 - ../dm-3
brw-rw  1 root disk 252,  13 Jul 12 21:03 mpath3p1
brw-rw  1 root disk 252,  14 Jul 12 21:03 mpath3-part1
lrwxrwxrwx  1 root root7 Jul 12 20:52 mpath4 - ../dm-4
lrwxrwxrwx  1 root root7 Jul 12 20:47 mpath5 - ../dm-5
lrwxrwxrwx  1 root root8 Jul 12 20:47 mpath6 - ../dm-10
lrwxrwxrwx  1 root root8 Jul 12 21:03 mpath7 - ../dm-12
root@dilllp1:/# 
root@dilllp1:/# 
root@dilllp1:/# ls -l /dev/dm-0 
brw-rw 1 root disk 252, 0 Jul 13 08:41 /dev/dm-0
root@dilllp1:/# 


Looking at code : fdisk.c

---
void try(char *device)
{
disk_device = device;
if (!setjmp(listingbuf)) {
if ((fd = open(disk_device, type_open)) = 0) {
close(fd);
get_boot();
list_table();
if (partitions  4)
delete_partition(ext_index);
  } else {
/* Ignore other errors, since we try IDE
   and SCSI hard disks which may not be
   installed on the system. */
 if(errno == EACCES) {
fprintf(stderr, Cannot open %s\n, device);
exit(1);
 }
  }
}
}


void main(int argc, char **argv)
{
if (argc  3)
fatal(usage);
if (argc  1  *argv[1] == '-') {
switch (*(argv[1] + 1)) {
case 'v':
printf(fdisk v VERSION \n);
exit(0);
case 'l':
listing = 1;
type_open = O_RDONLY;
try(/dev/hda);
try(/dev/hdb);
try(/dev/hdc);
try(/dev/hdd);
try(/dev/sda);
try(/dev/sdb);
try(/dev/sdc);
try(/dev/sdd);
try(/dev/sde);
try(/dev/sdf);
try(/dev/sdg);
try(/dev/sdh);
exit(0);
case 's': {



** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin14043

** Attachment added: Strace Log
   https://bugs.launchpad.net/bugs/1473934/+attachment/4440834/+files/strace.log

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

Title:
  ISST-LTE: pmac-fdisk doesn't work with mpath devices

Status in mac-fdisk package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  Fix Released
Status in mac-fdisk source package in Trusty:
  Fix Released
Status in util-linux source package in Trusty:
  Fix Released
Status in mac-fdisk source package in Vivid:
  Fix Committed
Status in util-linux source package in Vivid:
  Fix Committed

Bug description:
  ---Problem Description---
  1. fdisk -l doesn't work with mpath device:

  % sudo fdisk -l /dev/mapper/mpath0
  The number of cylinders for this disk is set to 4252.
  This is larger than 1024, and may cause problems with:
  1) software that runs at boot time (e.g., LILO)
  2) booting and partitioning software form other OSs
 (e.g., DOS FDISK, OS/2 FDISK)

  Disk /dev/sda: 128 heads, 32 sectors, 4252 cylinders
  Units = cylinders of 4096 * 512 bytes

 Device Boot   BeginStart  End   Blocks   Id  System

[Touch-packages] [Bug 1482411] Re: Pulseaudio set Kodi sount to 1% each time I change video

2015-08-06 Thread Raymond

There is no hardware volume control when you use ac3 pass through SPDIF
the volume is controlled by your AC3 digital receiver 


index: 2
name: alsa_output.pci-_00_14.2.iec958-ac3-surround-51
driver: module-alsa-card.c
flags: HARDWARE DECIBEL_VOLUME LATENCY 
state: RUNNING
suspend cause: 
priority: 9958
volume: front-left: 65536 / 100% / 0,00 dB,   front-right: 65536 / 100% 
/ 0,00 dB,   rear-left: 65536 / 100% / 0,00 dB,   rear-right: 65536 / 100% / 
0,00 dB,   front-center: 65536 / 100% / 0,00 dB,   lfe: 65536 / 100% / 0,00 dB
balance 0,00
base volume: 65536 / 100% / 0,00 dB
volume steps: 65537
muted: no
current latency: 96,00 ms
max request: 54 KiB
max rewind: 0 KiB
monitor source: 4
sample spec: s16le 6ch 48000Hz
channel map: 
front-left,front-right,rear-left,rear-right,front-center,lfe
 Surround 5.1
used by: 1
linked by: 1
fixed latency: 96,00 ms
card: 2 alsa_card.pci-_00_14.2
module: 8
properties:
alsa.resolution_bits = 16
device.api = alsa
device.class = sound
alsa.class = generic
alsa.subclass = generic-mix
alsa.name = 
alsa.id = 
alsa.subdevice = 0
alsa.subdevice_name = 
alsa.device = 0
device.string = a52:0
device.buffering.buffer_size = 55296
device.buffering.fragment_size = 18432
device.access_mode = mmap
device.profile.name = iec958-ac3-surround-51
device.profile.description = Surround numérique 5.1 
(IEC958/AC3)
device.description = Audio interne Surround numérique 5.1 
(IEC958/AC3)
alsa.card = 0
alsa.card_name = HDA ATI SB
alsa.long_card_name = HDA ATI SB at 0xf9ff4000 irq 16
alsa.driver_name = snd_hda_intel
device.bus_path = pci-:00:14.2
sysfs.path = /devices/pci:00/:00:14.2/sound/card0
device.bus = pci
device.vendor.id = 1002
device.vendor.name = Advanced Micro Devices, Inc. [AMD/ATI]
device.product.id = 4383
device.product.name = SBx00 Azalia (Intel HDA)
device.form_factor = internal
module-udev-detect.discovered = 1
device.icon_name = audio-card-pci
4 source(s) available.


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

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

Title:
  Pulseaudio set Kodi sount to 1% each time I change video

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in kodi package in Ubuntu:
  New

Bug description:
  Hi,

  here is the bug :

  Each time Kodi change the video playing (like coming to next TV show
  episode), Pulseaudio set Kodi sound level to 1% and I need to go back
  to pavucontrol to upgrade to 100% each time !

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  kevin 10243 F pulseaudio
   /dev/snd/controlC1:  kevin 10243 F pulseaudio
   /dev/snd/pcmC0D1p:   kevin 10243 F...m pulseaudio
   /dev/snd/controlC0:  kevin 10243 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Aug  7 00:34:05 2015
  InstallationDate: Installed on 2015-07-14 (23 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Audio interne - HDA ATI SB
  Symptom_Jack: Grey SPDIF Out, Rear Panel
  Symptom_Type: Sound works for a while, then breaks
  Title: [System Product Name, VIA VT1708S, Grey SPDIF Out, Rear Panel] fails 
after a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0702
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A77TD PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias:

[Touch-packages] [Bug 1481804] Re: LightDM's guest-account script should disable screen lock universally for guest sessions

This bug was fixed in the package lightdm - 1.15.1-0ubuntu2

---
lightdm (1.15.1-0ubuntu2) wily; urgency=medium

  * debian/guest-session-auto.sh:
- Disable screenlocks for guest sessions on MATE, XFCE, Pantheon
  (LP: #1481804)
  * debian/control:
- Switch build-depends from transitional libgcrypt11-dev to libgcrypt20-dev

 -- Robert Ancell robert.anc...@canonical.com  Fri, 07 Aug 2015
12:50:38 +1200

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

Title:
  LightDM's guest-account script should disable screen lock universally
  for guest sessions

Status in lightdm package in Ubuntu:
  Fix Released

Bug description:
  Is it feasible to include in /usr/sbin/guest-account script some
  commands to disable screen lock for guest sessions? It should include
  several commands, depending on Ubuntu flavour. Examples:

  Ubuntu MATE (uses mate-screensaver)
  gsettings set org.mate.screensaver lock-enabled false

  Xubuntu and others (use light-locker)
  gsettings set apps.light-locker light-locker-enabled false
  gsettings set apps.light-locker late-locking false
  gsettings set apps.light-locker lock-on-lid false
  gsettings set apps.light-locker lock-on-suspend false

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

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

[Touch-packages] [Bug 1482411] Re: Pulseaudio set Kodi sount to 1% each time I change video

2015-08-06 Thread Raymond

you have to turn off IEC958 Default PCM if you are using AC3 passthrough
SPDIF

Simple mixer control 'IEC958 Default PCM',0
  Capabilities: pswitch pswitch-joined
  Playback channels: Mono
  Mono: Playback [on]

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

Title:
  Pulseaudio set Kodi sount to 1% each time I change video

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in kodi package in Ubuntu:
  New

Bug description:
  Hi,

  here is the bug :

  Each time Kodi change the video playing (like coming to next TV show
  episode), Pulseaudio set Kodi sound level to 1% and I need to go back
  to pavucontrol to upgrade to 100% each time !

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  kevin 10243 F pulseaudio
   /dev/snd/controlC1:  kevin 10243 F pulseaudio
   /dev/snd/pcmC0D1p:   kevin 10243 F...m pulseaudio
   /dev/snd/controlC0:  kevin 10243 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Aug  7 00:34:05 2015
  InstallationDate: Installed on 2015-07-14 (23 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Audio interne - HDA ATI SB
  Symptom_Jack: Grey SPDIF Out, Rear Panel
  Symptom_Type: Sound works for a while, then breaks
  Title: [System Product Name, VIA VT1708S, Grey SPDIF Out, Rear Panel] fails 
after a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0702
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A77TD PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0702:bd08/13/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A77TDPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1482504] [NEW] Putting and then getting dates in a document are altered by u1db

2015-08-06 Thread Didier Roche

Public bug reported:

When putting and getting a QML date in the u1db database, the resulting
strings are stored differently, even if you don't do any type
conversion.

The result is that the resulting date is shifted by the current
timezone, rendering an incorrect date.

Small example:

date is Sun Jul 5 17:20:46 2015 GMT+0200

This value is jsonified in var current = {title:First
element,date:2015-07-05T15:20:46.000Z}

console.log(Before save:  + JSON.stringify(tosave));
db.putDoc(tosave, current.billId);
var after = db.getDoc(current.billId.toString())
console.log(After save:  + JSON.stringify(afterSave));

log is:
qml: Before save: {title:First element,date:2015-07-05T15:20:46.000Z}
qml: After save: {date:2015-07-05T17:20:46,title:First element}

- Note that the date element has been altered and isn't returned in the
same format The date should be returned unalterned.

** Affects: u1db-qt
 Importance: Undecided
 Status: New

** Affects: u1db-qt (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: devexp

** Also affects: u1db-qt
   Importance: Undecided
   Status: New

** Tags added: devexp

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

Title:
  Putting and then getting dates in a document are altered by u1db

Status in U1DB Qt/ QML:
  New
Status in u1db-qt package in Ubuntu:
  New

Bug description:
  When putting and getting a QML date in the u1db database, the
  resulting strings are stored differently, even if you don't do any
  type conversion.

  The result is that the resulting date is shifted by the current
  timezone, rendering an incorrect date.

  Small example:

  date is Sun Jul 5 17:20:46 2015 GMT+0200

  This value is jsonified in var current = {title:First
  element,date:2015-07-05T15:20:46.000Z}

  console.log(Before save:  + JSON.stringify(tosave));
  db.putDoc(tosave, current.billId);
  var after = db.getDoc(current.billId.toString())
  console.log(After save:  + JSON.stringify(afterSave));

  log is:
  qml: Before save: {title:First element,date:2015-07-05T15:20:46.000Z}
  qml: After save: {date:2015-07-05T17:20:46,title:First element}

  - Note that the date element has been altered and isn't returned in
  the same format The date should be returned unalterned.

To manage notifications about this bug go to:
https://bugs.launchpad.net/u1db-qt/+bug/1482504/+subscriptions

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

[Touch-packages] [Bug 1455002] Re: Thinkpad x200t backlight settings

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

** Changed in: xorg (Ubuntu)
   Status: Incomplete = Expired

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

Title:
  Thinkpad x200t backlight settings

Status in xorg package in Ubuntu:
  Expired

Bug description:
  ubuntu 15.04 AMD64

  Howto reproduce this bug that did not exist up to ubuntu 14.10

  Set your required backlight power with the Fn-Keys and shutdown the
  machine. Now bootup again, the login screen and your desktop is on
  lowest backlight power that can be set, maybe you have to lower the
  light to see your display. You have to power the backlight up with the
  Fn-Keys after login., but this will not survive next shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.2-0ubuntu1
  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 14 11:00:23 2015
  DistUpgraded: 2015-04-25 23:23:28,368 DEBUG enabling apt cron job
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   tp-smapi, 0.41, 3.13.0-49-generic, x86_64: installed
   tp-smapi, 0.41, 3.16.0-34-generic, x86_64: installed
   tp-smapi, 0.41, 3.19.0-15-generic, x86_64: installed
   tp-smapi, 0.41, 3.19.0-16-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:20e4]
 Subsystem: Lenovo Device [17aa:20e4]
  InstallationDate: Installed on 2014-09-17 (238 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: LENOVO 7453WVK
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic 
root=UUID=dbb1913f-e1d6-42eb-b68f-221fd8326a6b ro quiet splash 
elevator=deadline vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to vivid on 2015-04-25 (18 days ago)
  dmi.bios.date: 11/16/2009
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7WET61WW (3.11 )
  dmi.board.name: 7453WVK
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7WET61WW(3.11):bd11/16/2009:svnLENOVO:pn7453WVK:pvrThinkPadX200T:rvnLENOVO:rn7453WVK:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 7453WVK
  dmi.product.version: ThinkPad X200T
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Thu May 14 10:56:56 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16401 
   vendor LEN
  xserver.version: 2:1.17.1-0ubuntu3

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

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

[Touch-packages] [Bug 1482503] [NEW] Putting and then getting dates in a document are altered by u1db

2015-08-06 Thread Didier Roche

Public bug reported:

When putting and getting a QML date in the u1db database, the resulting
strings are stored differently, even if you don't do any type
conversion.

The result is that the resulting date is shifted by the current
timezone, rendering an incorrect date.

Small example:

date is Sun Jul 5 17:20:46 2015 GMT+0200

This value is jsonified in var current = {title:First
element,date:2015-07-05T15:20:46.000Z}

console.log(Before save:  + JSON.stringify(tosave));
db.putDoc(tosave, current.billId);
var after = db.getDoc(current.billId.toString())
console.log(After save:  + JSON.stringify(afterSave));

log is:
qml: Before save: {title:First element,date:2015-07-05T15:20:46.000Z}
qml: After save: {date:2015-07-05T17:20:46,title:First element}

- Note that the date element has been altered and isn't returned in the
same format The date should be returned unalterned.

** Affects: u1db-qt (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Putting and then getting dates in a document are altered by u1db

Status in u1db-qt package in Ubuntu:
  New

Bug description:
  When putting and getting a QML date in the u1db database, the
  resulting strings are stored differently, even if you don't do any
  type conversion.

  The result is that the resulting date is shifted by the current
  timezone, rendering an incorrect date.

  Small example:

  date is Sun Jul 5 17:20:46 2015 GMT+0200

  This value is jsonified in var current = {title:First
  element,date:2015-07-05T15:20:46.000Z}

  console.log(Before save:  + JSON.stringify(tosave));
  db.putDoc(tosave, current.billId);
  var after = db.getDoc(current.billId.toString())
  console.log(After save:  + JSON.stringify(afterSave));

  log is:
  qml: Before save: {title:First element,date:2015-07-05T15:20:46.000Z}
  qml: After save: {date:2015-07-05T17:20:46,title:First element}

  - Note that the date element has been altered and isn't returned in
  the same format The date should be returned unalterned.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/u1db-qt/+bug/1482503/+subscriptions

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

[Touch-packages] [Bug 1479688] Re: ListItem does not swipe with custom MouseAreas

2015-08-06 Thread Zsombor Egri

So as of stakeholders meeting clarified, there should be no distinction
between touch and mouse handling. Whatever can be done with touch should
be doable with mouse. This policy stays the same, therefore the
implementation we have is right and will stay as is.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: In Progress = Fix Committed

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

Title:
ListItem does not swipe with custom MouseAreas

Status in Ubuntu UX:
Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
Fix Committed

Bug description:
Expected:
ListItem with user avatar an an image/attachment. I want to be able to detect
the click on the avatar or the image, so I need to place MouseAreas within the
list view. This used to work with the old ListViewItemWithActions.

Actual:
ListItem does not allow a swipe when it starts on one of those mouse areas.
Meaning, you have to look for free space where you can drag the item, which
is not intuitive and clearly a UX annoyance.

UX Fix:

When a mouse is plugged in, the leading and trailing actions should be
available in the contextual menu. Please look at

https://docs.google.com/document/d/1nFm8xiYhKXXuEO_IvMXoD0lASbYzYXva1BWMVanU3iw/edit#heading=h.y7e1o2x66nvr
pages 106-109.

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

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

[Touch-packages] [Bug 1468811] Re: headphone volume auto-set to loudest

2015-08-06 Thread Cédric Bellegarde

Happens again this morning, while switching tracks in music app

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

Title:
  headphone volume auto-set to loudest

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

Bug description:
  since OTA-4 i get the headphone volume randomly set to the highest
  setting. it can only be set when headphones are plugged in and
  playback has started, so I have no way of checking beforehand. (of
  course I can choose to keep headphones away from the ears.)

  
  this occurs both in the music app and in the podcast app podbird. also occurs 
sometimes during playback, when notification sound is played. 

  not a security issue, but rather a quite serious hearing health issue. 
  I'm on BQ Aquaris E4.5

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

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

[Touch-packages] [Bug 1372051] Re: ntp postinst user/group add commands are not idempotent

2015-08-06 Thread Robie Basak

Thanks Niklas, marking Invalid as advised.

** Changed in: ntp (Ubuntu)
   Status: Incomplete = Invalid

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

Title:
  ntp postinst user/group add commands are not idempotent

Status in ntp package in Ubuntu:
  Invalid

Bug description:
  At do release upgrade from 12.04.05 to 14.04.01, the ntp package failed:
  Errors were encountered while processing:
   ntp
  Error in function: 

  
  A fatal error occurred 

  Please report this as a bug and include the files 
  /var/log/dist-upgrade/main.log and /var/log/dist-upgrade/apt.log in 
  your report. The upgrade has aborted. 
  Your original sources.list was saved in 
  /etc/apt/sources.list.distUpgrade. 

  SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1)


  Could not install the upgrades

  The upgrade has aborted. Your system could be in an unusable state. A 
  recovery will run now (dpkg --configure -a). 

  Please report this bug in a browser at 
  http://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+filebug 
  and attach the files in /var/log/dist-upgrade/ to the bug report. 
  installArchives() failed 

  Setting up ntp (1:4.2.6.p5+dfsg-3ubuntu2) ...
  dpkg: error processing package ntp (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   ntp

  Upgrade complete

  The upgrade has completed but there were errors during the upgrade 
  process. 


  In /var/lib/dpkg/info/ntp.postinst the add group / adduser commands fail due 
to already existing group / user.
  Appended “ || /bin/true” to those lines, and “dpkg —configure ntp” succeeded.

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

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

[Touch-packages] [Bug 1482424] [NEW] /usr/lib/arm-linux-gnueabihf/thumbnailer/thumbnailer-service:11:construct:_S_construct:construct:push_back:unity::thumbnailer::service::DBusInterface::queueRequest

2015-08-06 Thread errors.ubuntu.com bug bridge

Public bug reported:

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

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


** Tags: vivid wily

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

Title:
  /usr/lib/arm-linux-gnueabihf/thumbnailer/thumbnailer-
  
service:11:construct:_S_construct:construct:push_back:unity::thumbnailer::service::DBusInterface::queueRequest

Status in thumbnailer package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1481804] Re: LightDM's guest-account script should disable screen lock universally for guest sessions

** Branch linked: lp:lightdm

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

Title:
  LightDM's guest-account script should disable screen lock universally
  for guest sessions

Status in lightdm package in Ubuntu:
  Fix Committed

Bug description:
  Is it feasible to include in /usr/sbin/guest-account script some
  commands to disable screen lock for guest sessions? It should include
  several commands, depending on Ubuntu flavour. Examples:

  Ubuntu MATE (uses mate-screensaver)
  gsettings set org.mate.screensaver lock-enabled false

  Xubuntu and others (use light-locker)
  gsettings set apps.light-locker light-locker-enabled false
  gsettings set apps.light-locker late-locking false
  gsettings set apps.light-locker lock-on-lid false
  gsettings set apps.light-locker lock-on-suspend false

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

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

[Touch-packages] [Bug 1471213] Re: [SKL] noise in unity dash, torcs

2015-08-06 Thread Adam Conrad

** Tags removed: verification-failed
** Tags added: verification-needed

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

Title:
  [SKL] noise in unity dash, torcs

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa-lts-vivid package in Ubuntu:
  Invalid
Status in mesa-lts-vivid source package in Trusty:
  Fix Committed
Status in mesa source package in Vivid:
  Fix Committed

Bug description:
  [Impact]
  Intel Skylake GPU's suffers from noise seen in transparent unity dialogs, 
also visible in torcs for instance

  Need to backport four patches from 10.6.0:

  commit c02c4b567ce001f6605c46e71e089692b837bf26
  Author: Neil Roberts n...@linux.intel.com
  Date:   Wed Mar 4 14:13:40 2015 +

  i965: Store the GPU revision number in brw_context

  commit bc4b18d2977a94a6fb513bf5955236a0e92298ca
  Author: Neil Roberts n...@linux.intel.com
  Date:   Thu Mar 19 18:18:49 2015 +

  i965: Refactor SIMD16-to-2xSIMD8 checks.

  commit 484f9f4fcd53fcaa768e63934a5f74346bfb46a9
  Author: Dave Airlie airl...@redhat.com
  Date:   Mon Mar 23 09:54:52 2015 +1000

  i965: define I915_PARAM_REVISION

  commit 706b916960c898cfc24110f14fa4def84caaba93
  Author: Kenneth Graunke kenn...@whitecape.org
  Date:   Wed Mar 4 12:53:45 2015 -0800

  i965/skl: Break down SIMD16 3-source instructions when required.

  [Test case]
  Run something like Torcs on Skylake.

  [Regression potential]
  Slim, this only affects i965 driver for Intel, and the actual fix 
(706b916960c89) only affects gen9.

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

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

[Touch-packages] [Bug 1479472] Re: package ntp 1:4.2.6.p5+dfsg-3ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2015-08-06 Thread Robie Basak

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

Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.

If indeed this is a local configuration problem, you can find pointers
to get help for this sort of problem here:
http://www.ubuntu.com/support/community

Or if you believe that this is really a bug, then you may find it
helpful to read How to report bugs effectively
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem,
explain why you believe this is a bug in Ubuntu rather than a problem
specific to your system, and then change the bug status back to New.

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

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

Title:
  package ntp 1:4.2.6.p5+dfsg-3ubuntu6 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in ntp package in Ubuntu:
  Incomplete

Bug description:
  I just setup a ntp server.

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: ntp 1:4.2.6.p5+dfsg-3ubuntu6
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  AptOrdering:
   vsftpd: Install
   ntp: Configure
   vsftpd: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Jul 29 11:47:52 2015
  DpkgHistoryLog:
   Start-Date: 2015-07-29  11:47:48
   Commandline: apt-get install vsftpd
   Install: vsftpd:amd64 (3.0.2-18ubuntu1)
  DuplicateSignature: package:ntp:1:4.2.6.p5+dfsg-3ubuntu6:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-05-04 (85 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.19.0-20-generic 
root=UUID=27b12a69-2da9-435b-953c-93b0523d7a2e ro quiet splash
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4
  SourcePackage: ntp
  Title: package ntp 1:4.2.6.p5+dfsg-3ubuntu6 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.ntp.conf: [modified]
  mtime.conffile..etc.ntp.conf: 2015-05-04T12:41:20.180252

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

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

[Touch-packages] [Bug 1481804] Re: LightDM's guest-account script should disable screen lock universally for guest sessions

2015-08-06 Thread Robert Ancell

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

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

** Changed in: lightdm
   Status: Triaged = Fix Committed

** Changed in: lightdm (Ubuntu)
   Importance: Undecided = Medium

** Changed in: lightdm
Milestone: None = 1.15.2

** No longer affects: lightdm

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

Title:
  LightDM's guest-account script should disable screen lock universally
  for guest sessions

Status in lightdm package in Ubuntu:
  Fix Committed

Bug description:
  Is it feasible to include in /usr/sbin/guest-account script some
  commands to disable screen lock for guest sessions? It should include
  several commands, depending on Ubuntu flavour. Examples:

  Ubuntu MATE (uses mate-screensaver)
  gsettings set org.mate.screensaver lock-enabled false

  Xubuntu and others (use light-locker)
  gsettings set apps.light-locker light-locker-enabled false
  gsettings set apps.light-locker late-locking false
  gsettings set apps.light-locker lock-on-lid false
  gsettings set apps.light-locker lock-on-suspend false

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

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

[Touch-packages] [Bug 1473562] Update Released

2015-08-06 Thread Brian Murray

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

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

Title:
  Too many crash files kill the device

Status in Canonical System Image:
  Fix Committed
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Vivid:
  Fix Released

Bug description:
  Tested on krillin.

  TEST CASE:
  1. adb shell to the phone and create a crash file
  $ sh -c 'kill -SEGV $$'
  2. Now create dozens
  $ for n in $(seq 50); do ln /var/crash/_bin_dash.32011.crash 
/var/crash/_bin_dash_${n}.32011.crash; done
  3. Remove any upload and uploaded files that have been created and reboot
  $ sudo rm /var/crash/*upload*  sudo reboot

  ACTUAL RESULT
  Lot of whoopsie-upload-all and apport processes are created on boot, consume 
all the resources of the system and make the phone unbootable or partially 
functional. OOM killer kills random system tasks such as upstart. Depending on 
the processes killed, the phone hangs on boot, reboots, dash doesn't come up...

  The number of crashes in this test is a bit excessive but we can
  imagine a scenario where a dozen of crash files are not uploaded
  because the phone is on cellular data, and uploads everything when it
  connects to wifi, disabling the user session.

  A way to recover is to go into recovery and clean /var/crash.

  EXPECTED RESULT
  crash uploads are serialized and can be uploaded only one at a time
  If system resources are already low, the crash file is not uploaded.

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

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

[Touch-packages] [Bug 1473562] Re: Too many crash files kill the device

This bug was fixed in the package apport - 2.17.2-0ubuntu1.2

---
apport (2.17.2-0ubuntu1.2) vivid-proposed; urgency=medium

  * apport-noui.upstart: Utilize watershed to only launch one instance of
whoopsie-upload-all at a time. (LP: #1473562)
  * apport-noui: Depend on watershed.

 -- Brian Murray br...@ubuntu.com  Fri, 24 Jul 2015 15:27:31 -0700

** Changed in: apport (Ubuntu Vivid)
   Status: Fix Committed = Fix Released

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

Title:
  Too many crash files kill the device

Status in Canonical System Image:
  Fix Committed
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Vivid:
  Fix Released

Bug description:
  Tested on krillin.

  TEST CASE:
  1. adb shell to the phone and create a crash file
  $ sh -c 'kill -SEGV $$'
  2. Now create dozens
  $ for n in $(seq 50); do ln /var/crash/_bin_dash.32011.crash 
/var/crash/_bin_dash_${n}.32011.crash; done
  3. Remove any upload and uploaded files that have been created and reboot
  $ sudo rm /var/crash/*upload*  sudo reboot

  ACTUAL RESULT
  Lot of whoopsie-upload-all and apport processes are created on boot, consume 
all the resources of the system and make the phone unbootable or partially 
functional. OOM killer kills random system tasks such as upstart. Depending on 
the processes killed, the phone hangs on boot, reboots, dash doesn't come up...

  The number of crashes in this test is a bit excessive but we can
  imagine a scenario where a dozen of crash files are not uploaded
  because the phone is on cellular data, and uploads everything when it
  connects to wifi, disabling the user session.

  A way to recover is to go into recovery and clean /var/crash.

  EXPECTED RESULT
  crash uploads are serialized and can be uploaded only one at a time
  If system resources are already low, the crash file is not uploaded.

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

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

[Touch-packages] [Bug 1473934] Comment bridged from LTC Bugzilla

2015-08-06 Thread bugproxy

--- Comment From pt...@cn.ibm.com 2015-08-07 01:39 EDT---
I can confirm that this bug has been fixed with the new packages. Thanks!

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

Title:
  ISST-LTE: pmac-fdisk doesn't work with mpath devices

Status in mac-fdisk package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  Fix Released
Status in mac-fdisk source package in Trusty:
  Fix Released
Status in util-linux source package in Trusty:
  Fix Released
Status in mac-fdisk source package in Vivid:
  Fix Committed
Status in util-linux source package in Vivid:
  Fix Committed

Bug description:
  ---Problem Description---
  1. fdisk -l doesn't work with mpath device:

  % sudo fdisk -l /dev/mapper/mpath0
  The number of cylinders for this disk is set to 4252.
  This is larger than 1024, and may cause problems with:
  1) software that runs at boot time (e.g., LILO)
  2) booting and partitioning software form other OSs
 (e.g., DOS FDISK, OS/2 FDISK)

  Disk /dev/sda: 128 heads, 32 sectors, 4252 cylinders
  Units = cylinders of 4096 * 512 bytes

 Device Boot   BeginStart  End   Blocks   Id  System
  /dev/sda111   135324277143551+  ee  Unknown
  Partition 1 does not end on cylinder boundary:
   phys=(1023, 254, 63) should be (1023, 127, 32)
  The number of cylinders for this disk is set to 4252.
  This is larger than 1024, and may cause problems with:
  1) software that runs at boot time (e.g., LILO)
  2) booting and partitioning software form other OSs
 (e.g., DOS FDISK, OS/2 FDISK)

  Disk /dev/sdb: 128 heads, 32 sectors, 4252 cylinders
  Units = cylinders of 4096 * 512 bytes

 Device Boot   BeginStart  End   Blocks   Id  System
  /dev/sdb111   2142992   83  Linux native
  The number of cylinders for this disk is set to 4252.
  This is larger than 1024, and may cause problems with:
  1) software that runs at boot time (e.g., LILO)
  2) booting and partitioning software form other OSs
 (e.g., DOS FDISK, OS/2 FDISK)
  Warning: invalid flag 6f00 of partition table 4 will be corrected by w(rite)

  Disk /dev/sdc: 128 heads, 32 sectors, 4252 cylinders
  Units = cylinders of 4096 * 512 bytes

 Device Boot   BeginStart  End   Blocks   Id  System
  The number of cylinders for this disk is set to 4252.
  This is larger than 1024, and may cause problems with:
  1) software that runs at boot time (e.g., LILO)
  2) booting and partitioning software form other OSs
 (e.g., DOS FDISK, OS/2 FDISK)
  Warning: invalid flag 6f00 of partition table 4 will be corrected by w(rite)

  Disk /dev/sdd: 128 heads, 32 sectors, 4252 cylinders
  Units = cylinders of 4096 * 512 bytes

 Device Boot   BeginStart  End   Blocks   Id  System
  The number of cylinders for this disk is set to 4252.
  This is larger than 1024, and may cause problems with:
  1) software that runs at boot time (e.g., LILO)
  2) booting and partitioning software form other OSs
 (e.g., DOS FDISK, OS/2 FDISK)
  Warning: invalid flag 6f00 of partition table 4 will be corrected by w(rite)

  Disk /dev/sde: 128 heads, 32 sectors, 4252 cylinders
  Units = cylinders of 4096 * 512 bytes

 Device Boot   BeginStart  End   Blocks   Id  System
  The number of cylinders for this disk is set to 4252.
  This is larger than 1024, and may cause problems with:
  1) software that runs at boot time (e.g., LILO)
  2) booting and partitioning software form other OSs
 (e.g., DOS FDISK, OS/2 FDISK)
  Warning: invalid flag 6f00 of partition table 4 will be corrected by w(rite)

  Disk /dev/sdf: 128 heads, 32 sectors, 4252 cylinders
  Units = cylinders of 4096 * 512 bytes

 Device Boot   BeginStart  End   Blocks   Id  System
  The number of cylinders for this disk is set to 4252.
  This is larger than 1024, and may cause problems with:
  1) software that runs at boot time (e.g., LILO)
  2) booting and partitioning software form other OSs
 (e.g., DOS FDISK, OS/2 FDISK)
  Warning: invalid flag 6f00 of partition table 4 will be corrected by w(rite)

  Disk /dev/sdg: 128 heads, 32 sectors, 4252 cylinders
  Units = cylinders of 4096 * 512 bytes

 Device Boot   BeginStart  End   Blocks   Id  System
  The number of cylinders for this disk is set to 4252.
  This is larger than 1024, and may cause problems with:
  1) software that runs at boot time (e.g., LILO)
  2) booting and partitioning software form other OSs
 (e.g., DOS FDISK, OS/2 FDISK)
  Warning: invalid flag 6f00 of partition table 4 will be corrected by w(rite)

  Disk /dev/sdh: 128 heads, 32 sectors, 4252 cylinders
  Units = cylinders of 4096 * 512 bytes

 Device Boot   BeginStart  End   Blocks   Id  System
  %  

  2. when trying to partition a mpath device with fdisk, it asks user to
  sed sectors and

[Touch-packages] [Bug 1482274] Re: GLibMainLoopTest.propagates_exception_from_server_action fails with GCC 5 in armhf

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

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

Title:
  GLibMainLoopTest.propagates_exception_from_server_action fails with
  GCC 5 in armhf

Status in Mir:
  Fix Committed
Status in Mir 0.15 series:
  Fix Committed
Status in mir package in Ubuntu:
  New

Bug description:
  Using -02 (which is turned on when building the mir packages or
  use_debflags=ON) with GCC 5 on armhf results in the following test
  failure:

  bin/mir_unit_tests 
--gtest_filter=GLibMainLoopTest.propagates_exception_from_server_action
  Running main() from main.cpp
  Note: Google Test filter = 
GLibMainLoopTest.propagates_exception_from_server_action
  [==] Running 1 test from 1 test case.
  [--] Global test environment set-up.
  [--] 1 test from GLibMainLoopTest
  [ RUN  ] GLibMainLoopTest.propagates_exception_from_server_action
  terminate called after throwing an instance of 'std::runtime_error'
what():  server action error
  /home/alberto/source/mir/0.15/tests/unit-tests/test_glib_main_loop.cpp:78: 
Failure
  Value of: result.succeeded()
Actual: false
  Expected: true
  [  FAILED  ] GLibMainLoopTest.propagates_exception_from_server_action (677 ms)
  [--] 1 test from GLibMainLoopTest (677 ms total)

  [--] Global test environment tear-down
  [==] 1 test from 1 test case ran. (679 ms total)
  [  PASSED  ] 0 tests.
  [  FAILED  ] 1 test, listed below:
  [  FAILED  ] GLibMainLoopTest.propagates_exception_from_server_action

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

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

[Touch-packages] [Bug 1479224] Re: The mesa-x11 driver is not packaged yet

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

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

Title:
  The mesa-x11 driver is not packaged yet

Status in Mir:
  Fix Committed
Status in Mir 0.15 series:
  Fix Committed
Status in mir package in Ubuntu:
  New

Bug description:
  The mesa-x11 driver is not packaged yet. No mention of it in debian/

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

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

[Touch-packages] [Bug 1482423] [NEW] /usr/sbin/NetworkManager:6:g_assertion_message:g_assertion_message_expr:nm_modem_ip4_pre_commit:ip4_config_merge_and_apply:nm_device_activate_ip4_config_commit

2015-08-06 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding network-manager.  This problem was most recently seen with
version 0.9.10.0-4ubuntu15.1.4, the problem page at
https://errors.ubuntu.com/problem/50d03f7339bd688901b30941272ea3768e10dcc3
contains more details.

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


** Tags: vivid

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

Title:
  
/usr/sbin/NetworkManager:6:g_assertion_message:g_assertion_message_expr:nm_modem_ip4_pre_commit:ip4_config_merge_and_apply:nm_device_activate_ip4_config_commit

Status in network-manager package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding network-manager.  This problem was most recently seen with
  version 0.9.10.0-4ubuntu15.1.4, the problem page at
  https://errors.ubuntu.com/problem/50d03f7339bd688901b30941272ea3768e10dcc3
  contains more details.

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

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

[Touch-packages] [Bug 1427311] Re: welcome wizard - no feedback that wifi connection succeeded

2015-08-06 Thread Andreea Pirvu

** Changed in: ubuntu-ux
   Status: Triaged = Fix Committed

** Description changed:

  Preconditions:
  Be in a environment where dozes of wifi access points are available, or at 
least where it has more APs than the wifi list can fit on the screen, so that 
it gets scrollable
  
  Steps:
  1 - boot phone into the Welcome Wizard
  2 - on the wifi connection page, scroll down to some access point and tap on 
it.
  3 - fill in the password in the dialog and tap on connect/ok
  
  Expected outcome:
  Dialog closes and you can see that you're now connected to that wifi AP you 
selected (e.g. you immediately see that the wifi you selected is now green with 
its checkbox ticked).
  
  Actual outcome:
  Dialog closes and you are brought back to the wifi selection list, where you 
cannot see the wifi AP you selected anywhere. You have to scroll the list all 
the way up to finally find your selected wifi there.
+ 
+  UX Design -
+ This bug is covered by the new OOBE design.
+ You can see the new spec here 
https://docs.google.com/a/canonical.com/document/d/1pZ-Ro--2eaRzjZKNRoYAeDvQHMkCuyvVuPFWFQfPW4s/edit?usp=sharing

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

Title:
  welcome wizard - no feedback that wifi connection succeeded

Status in Ubuntu UX:
  Fix Committed
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Preconditions:
  Be in a environment where dozes of wifi access points are available, or at 
least where it has more APs than the wifi list can fit on the screen, so that 
it gets scrollable

  Steps:
  1 - boot phone into the Welcome Wizard
  2 - on the wifi connection page, scroll down to some access point and tap on 
it.
  3 - fill in the password in the dialog and tap on connect/ok

  Expected outcome:
  Dialog closes and you can see that you're now connected to that wifi AP you 
selected (e.g. you immediately see that the wifi you selected is now green with 
its checkbox ticked).

  Actual outcome:
  Dialog closes and you are brought back to the wifi selection list, where you 
cannot see the wifi AP you selected anywhere. You have to scroll the list all 
the way up to finally find your selected wifi there.

   UX Design -
  This bug is covered by the new OOBE design.
  You can see the new spec here 
https://docs.google.com/a/canonical.com/document/d/1pZ-Ro--2eaRzjZKNRoYAeDvQHMkCuyvVuPFWFQfPW4s/edit?usp=sharing

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

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

[Touch-packages] [Bug 1481804] Re: LightDM's guest-account script should disable screen lock universally for guest sessions

** Branch linked: lp:ubuntu/wily-proposed/lightdm

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

Title:
  LightDM's guest-account script should disable screen lock universally
  for guest sessions

Status in lightdm package in Ubuntu:
  Fix Committed

Bug description:
  Is it feasible to include in /usr/sbin/guest-account script some
  commands to disable screen lock for guest sessions? It should include
  several commands, depending on Ubuntu flavour. Examples:

  Ubuntu MATE (uses mate-screensaver)
  gsettings set org.mate.screensaver lock-enabled false

  Xubuntu and others (use light-locker)
  gsettings set apps.light-locker light-locker-enabled false
  gsettings set apps.light-locker late-locking false
  gsettings set apps.light-locker lock-on-lid false
  gsettings set apps.light-locker lock-on-suspend false

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

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

[Touch-packages] [Bug 1471504] Re: X11 crashes when opening LibreOffice

apport information

** Tags added: apport-collected vivid

** Description changed:

- Ever since 14.04, X11 crashes when opening libreoffice, and the session
- is forced logged out.
+ Ever since 14.04, X11 crashes when opening libreoffice, and the session is 
forced logged out.
+ --- 
+ ApportVersion: 2.17.2-0ubuntu1
+ Architecture: amd64
+ CasperVersion: 1.360
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 15.04
+ LiveMediaBuild: Kubuntu 15.04 Vivid Vervet - Release amd64 (20150422)
+ Package: xorg 1:7.7+7ubuntu4
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
+ Tags:  vivid
+ Uname: Linux 3.19.0-15-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: Dependencies.txt
   
https://bugs.launchpad.net/bugs/1471504/+attachment/4440720/+files/Dependencies.txt

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

Title:
  X11 crashes when opening LibreOffice

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Ever since 14.04, X11 crashes when opening libreoffice, and the session is 
forced logged out.
  --- 
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.360
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 15.04
  LiveMediaBuild: Kubuntu 15.04 Vivid Vervet - Release amd64 (20150422)
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Tags:  vivid
  Uname: Linux 3.19.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1471504] JournalErrors.txt

apport information

** Attachment added: JournalErrors.txt
   
https://bugs.launchpad.net/bugs/1471504/+attachment/4440721/+files/JournalErrors.txt

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

Title:
  X11 crashes when opening LibreOffice

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Ever since 14.04, X11 crashes when opening libreoffice, and the session is 
forced logged out.
  --- 
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.360
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 15.04
  LiveMediaBuild: Kubuntu 15.04 Vivid Vervet - Release amd64 (20150422)
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Tags:  vivid
  Uname: Linux 3.19.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1471504] ProcEnviron.txt

apport information

** Attachment added: ProcEnviron.txt
   
https://bugs.launchpad.net/bugs/1471504/+attachment/4440722/+files/ProcEnviron.txt

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

Title:
  X11 crashes when opening LibreOffice

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Ever since 14.04, X11 crashes when opening libreoffice, and the session is 
forced logged out.
  --- 
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.360
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 15.04
  LiveMediaBuild: Kubuntu 15.04 Vivid Vervet - Release amd64 (20150422)
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Tags:  vivid
  Uname: Linux 3.19.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1482411] [NEW] Pulseaudio set Kodi sount to 1% each time I change video

2015-08-06 Thread PEIGNOT Kévin

Public bug reported:

Hi,

here is the bug :

Each time Kodi change the video playing (like coming to next TV show
episode), Pulseaudio set Kodi sound level to 1% and I need to go back to
pavucontrol to upgrade to 100% each time !

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
Uname: Linux 3.19.0-25-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  kevin 10243 F pulseaudio
 /dev/snd/controlC1:  kevin 10243 F pulseaudio
 /dev/snd/pcmC0D1p:   kevin 10243 F...m pulseaudio
 /dev/snd/controlC0:  kevin 10243 F pulseaudio
CurrentDesktop: Unity
Date: Fri Aug  7 00:34:05 2015
InstallationDate: Installed on 2015-07-14 (23 days ago)
InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Audio interne - HDA ATI SB
Symptom_Jack: Grey SPDIF Out, Rear Panel
Symptom_Type: Sound works for a while, then breaks
Title: [System Product Name, VIA VT1708S, Grey SPDIF Out, Rear Panel] fails 
after a while
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/13/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0702
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M4A77TD PRO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0702:bd08/13/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A77TDPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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

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


** Tags: amd64 apport-bug vivid

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

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

Title:
  Pulseaudio set Kodi sount to 1% each time I change video

Status in alsa-driver package in Ubuntu:
  New
Status in kodi package in Ubuntu:
  New

Bug description:
  Hi,

  here is the bug :

  Each time Kodi change the video playing (like coming to next TV show
  episode), Pulseaudio set Kodi sound level to 1% and I need to go back
  to pavucontrol to upgrade to 100% each time !

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  kevin 10243 F pulseaudio
   /dev/snd/controlC1:  kevin 10243 F pulseaudio
   /dev/snd/pcmC0D1p:   kevin 10243 F...m pulseaudio
   /dev/snd/controlC0:  kevin 10243 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Aug  7 00:34:05 2015
  InstallationDate: Installed on 2015-07-14 (23 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Audio interne - HDA ATI SB
  Symptom_Jack: Grey SPDIF Out, Rear Panel
  Symptom_Type: Sound works for a while, then breaks
  Title: [System Product Name, VIA VT1708S, Grey SPDIF Out, Rear Panel] fails 
after a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0702
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A77TD PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0702:bd08/13/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A77TDPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1471504] Re: X11 crashes when opening LibreOffice

so then why the need for apport to handle it then? Kind of makes the
whole bug reporting process useless, ya think? Besides Im getting a
sigsev trying it. everything seems to be sigsev. Its all related to
wiley, the bug is non-existant in tahir. So what to do about this mono
bug that creeped in?

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

Title:
  X11 crashes when opening LibreOffice

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Ever since 14.04, X11 crashes when opening libreoffice, and the session is 
forced logged out.
  --- 
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.360
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 15.04
  LiveMediaBuild: Kubuntu 15.04 Vivid Vervet - Release amd64 (20150422)
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Tags:  vivid
  Uname: Linux 3.19.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1435877] Re: [edge education] tutorial not adapted to desktop mode

2015-08-06 Thread Andreea Pirvu

** Changed in: ubuntu-ux
   Status: Triaged = In Progress

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

Title:
  [edge education] tutorial not adapted to desktop mode

Status in Ubuntu UX:
  In Progress
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  The first unity8 run shows you a tutorial explaining how the edges gestures 
work, that's also the case on the desktop-next iso, but some details don't fit 
well there
  - the switcher previews are not nicely scaled
  - the there are your software suggest that the dash is taking the screen, 
which is not the case
  - it might make sense to not restrict the explanations to be touch specific?

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

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

[Touch-packages] [Bug 1482427] [NEW] White Screen during WebApp session

2015-08-06 Thread Ilonka

Public bug reported:

Hello,
I recognize since a couple of weeks that sometimes in some WebApps appear 
white screens. 

This means: for example Google+ WebApp (this one from Oliver Grawert) is
open and suddenly the screen gets white and nothing works. Only reboot
of the App give the screen back. Sometimes then it's ok, other time
after a few minutes it happens again.

This issue I have in some WebApps: Facebook, Spiegel.de. Other WebApps
work without this issue.

I use a BQ4.5 
Ubuntu 15.04 (r24)

If you need further information please tell me.

Greeting and thanks in advance

Ilonka

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

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

Title:
  White Screen during WebApp session

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Hello,
  I recognize since a couple of weeks that sometimes in some WebApps appear 
white screens. 

  This means: for example Google+ WebApp (this one from Oliver Grawert)
  is open and suddenly the screen gets white and nothing works. Only
  reboot of the App give the screen back. Sometimes then it's ok, other
  time after a few minutes it happens again.

  This issue I have in some WebApps: Facebook, Spiegel.de. Other WebApps
  work without this issue.

  I use a BQ4.5 
  Ubuntu 15.04 (r24)

  If you need further information please tell me.

  Greeting and thanks in advance

  Ilonka

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

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

[Touch-packages] [Bug 1481784] Re: right click on touchpad doesn't work

Cool, thanks. Technically a two-finger click counts as gesture
recognition. So that's probably a separate task for each shell right
now.

** Changed in: mir
   Status: Incomplete = New

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

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

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

** Summary changed:

- right click on touchpad doesn't work
+ [enhancement] Support two-finger right click on clickpads

** Tags added: enhancement

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

Title:
  [enhancement] Support two-finger right click on clickpads

Status in Mir:
  Triaged
Status in mir package in Ubuntu:
  Triaged
Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Actual:
  Right clicking on a touchpad device produces a regular (left) click

  Expected: 
  The right click should behave the same as on X11, doing the same as a RMB 
click.

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

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

[Touch-packages] [Bug 1481784] Re: [enhancement] Support two-finger right click on clickpads

Although we may put common gesture recognition into Mir for all to use.
Maybe with libinput. Maybe further after that.

** Changed in: mir
   Importance: Undecided = Medium

** Changed in: mir (Ubuntu)
   Importance: Undecided = Medium

** Changed in: mir
   Status: New = Triaged

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

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

Title:
  [enhancement] Support two-finger right click on clickpads

Status in Mir:
  Triaged
Status in mir package in Ubuntu:
  Triaged
Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Actual:
  Right clicking on a touchpad device produces a regular (left) click

  Expected: 
  The right click should behave the same as on X11, doing the same as a RMB 
click.

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

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

[Touch-packages] [Bug 1474944] Re: Settings Display results from SCOPE is not translated

2015-08-06 Thread Yuan-Chen Cheng

** Changed in: savilerow
   Importance: Undecided = Medium

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

Title:
  Settings Display results from SCOPE is not translated

Status in Canonical System Image:
  Confirmed
Status in The Savilerow project:
  Triaged
Status in Ubuntu Translations:
  Fix Committed
Status in unity-scopes-api package in Ubuntu:
  Invalid
Status in unity-scopes-shell package in Ubuntu:
  Confirmed

Bug description:
  Since keyword support was added, agg scopes automatically get user
  settings to enable/disable child scopes.

  PROBLEM: Theses always display in English for me.

  I flashed with a --wipe:
  ubuntu-device-flash --wipe --channel=ubuntu-touch/rc-proposed/bq-aquaris.en

  On first boot welcome wizard I chose Spanish/Spain.

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 67
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-07-15 16:17:29
  version version: 67
  version ubuntu: 20150715
  version device: 20150529-8e13c5f
  version custom: 20150709-814-29-21-vivid

  See screenshot of Video agg.

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

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

[Touch-packages] [Bug 1480654] Re: [regression] Input focus delay after switching app back into focus since OTA5 (Mir 0.14)

It also feels like the Unity8 window switcher is getting in the way.
Particularly when switching into the web browser, it takes half a second
or so to finish the app switch after the animation apparently completes.
You can notice this just slightly as a flicker of shadow (from the app
switcher) appears on the right briefly, and sometimes the app surface
goes from slightly transformed (animation didn't end at the right spot)
to suddenly completely flat in that time. So it feels and looks like the
Unity8 app switcher is not finished doing it's thing for about half a
second after the animation apparently completes.

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

Title:
  [regression] Input focus delay after switching app back into focus
  since OTA5 (Mir 0.14)

Status in Mir:
  In Progress
Status in mir package in Ubuntu:
  Triaged
Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  i am not sure if it started with OTA4 or OTA5 but since one of the
  recent OTA upgrades my arale takes between half a second and one
  second before an app takes input again when one switches it from
  background back into focus. i'm talking about apps that were only
  sigstopped, not OOM killed here (i.e. no restart involved, just
  sigcont).

  this used to be instant before and gives a weird feeling of
  sluggishness.

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

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

[Touch-packages] [Bug 1461953] Re: scope settings of type list: layout of values unclear

2015-08-06 Thread Yuan-Chen Cheng

** Changed in: savilerow
   Status: New = Confirmed

** Changed in: savilerow
   Importance: Undecided = Medium

** Tags added: tracking

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

Title:
  scope settings of type list: layout of values unclear

Status in The Savilerow project:
  Confirmed
Status in unity8 package in Ubuntu:
  New

Bug description:
  Scope settings of type list puts list values on rows after displayName
  (the settings text).

  However, the value is flushed left and looks the same as the
  displayName (except for the chevron to expand/collapse the list).

  It not immediately clear that the value is associated with the
  displayName.

  The visual appearance needs to make it obvious that the values are
  subordinate to the displayName.

  see screenshot. Setting is Results per source:

  current build number: 230
  device name: krillin
  channel: ubuntu-touch/devel-proposed/ubuntu

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

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

[Touch-packages] [Bug 1428277] Re: Icon in notification center too small

** Changed in: ubuntu-ux
 Assignee: Paty Davila (dizzypaty) = Grazina (boroskograzina)

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

Title:
  Icon in notification center too small

Status in libqtelegram:
  Invalid
Status in Ubuntu UX:
  Triaged
Status in ubuntu-settings-components package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  See image attached. The tappable telegram icon is somewhat small and
  is not trivial to tap, or at least I'm not being able to tap it in a
  way it works in a single tap.

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

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

[Touch-packages] [Bug 1404824] Re: [Scopes] There is no way to uninstall a scope on ubuntu phone

2015-08-06 Thread Paty Davila

** Description changed:

  Currently, I only know that click unregister may help to remove an
  installed scope. May I know how I can remove an installed scope on the
  phone if a user does not like to have it in the phone?
  
- Relevant design:
+ -- UX Comment --
  
- https://sites.google.com/a/canonical.com/apps-and-platform-
- team/3-platform/4-dash-and-scopes
+ There are two possibilities for removing a scope from the phone:
+ 
+ 1 - Unfavourite a scope: 
+ If we access the 'Manage Dash' screen (via bottom edge gesture), you can tap 
on the star icon to remove any scope from the Dash (except the Apps Scope). 
After doing this, that scope will not be shonw as part of the Dash pagination. 
You can reverse the action by tapping on the star again.
+ 
+ 2 - Uninstall a scope:
+ If we go to the Ubunut Store (accessible from the Apps Scope or by tapping on 
the Store icon on the Manage Dash header) and we search for a specific scope 
(e.g.: Today Scope), we can tap on the 'Uninstall' button to uninstall it from 
the system. A confirmation dialog will prompt you and if you confirm, the scope 
will be uninstalled and therefore removed permantly from the Dash (pagination) 
and the Manage Dash screen. You can reverse this action by installing the scope 
again (same steps as any other app in the store).
+ 
+ However, we are working towards a entire redesign of Scopes and Dash,
+ therefore this is subject to change in the near future. The desired
+ solution and specs will be updated as soon as they are available.

** Changed in: ubuntu-ux
   Status: Triaged = 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/1404824

Title:
  [Scopes] There is no way to uninstall a scope on ubuntu phone

Status in Ubuntu UX:
  Invalid
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Currently, I only know that click unregister may help to remove an
  installed scope. May I know how I can remove an installed scope on the
  phone if a user does not like to have it in the phone?

  -- UX Comment --

  There are two possibilities for removing a scope from the phone:

  1 - Unfavourite a scope: 
  If we access the 'Manage Dash' screen (via bottom edge gesture), you can tap 
on the star icon to remove any scope from the Dash (except the Apps Scope). 
After doing this, that scope will not be shonw as part of the Dash pagination. 
You can reverse the action by tapping on the star again.

  2 - Uninstall a scope:
  If we go to the Ubunut Store (accessible from the Apps Scope or by tapping on 
the Store icon on the Manage Dash header) and we search for a specific scope 
(e.g.: Today Scope), we can tap on the 'Uninstall' button to uninstall it from 
the system. A confirmation dialog will prompt you and if you confirm, the scope 
will be uninstalled and therefore removed permantly from the Dash (pagination) 
and the Manage Dash screen. You can reverse this action by installing the scope 
again (same steps as any other app in the store).

  However, we are working towards a entire redesign of Scopes and Dash,
  therefore this is subject to change in the near future. The desired
  solution and specs will be updated as soon as they are available.

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

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

[Touch-packages] [Bug 1421623] Re: Welcome wizard claims GPS is less accurate than wifi based location

2015-08-06 Thread Ondrej Kubik

So is this it? Are we sticking to the version that Wifi based location is more 
accurate than GPS.
I strongly disagree to mark this as 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/1421623

Title:
  Welcome wizard claims GPS is less accurate than wifi based location

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  Invalid
Status in ubuntu-system-settings package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  First boot welcome wizard in location sections claims GPS is less accurate 
than network based location service from HERE.
  While this can be theoretically true in some insane corner case, in normal 
life GPS is far more accurate.

  To help form correct text here are main differences.

  GPS - more accurate, but slow to acquire fix, does not work indoors,
  drains battery more, no need for internet connection, does not send
  any data out.

  Network based location - almost instant to get coarse location, works
  indoors, accuracy depends on network coverage in the area, more power
  efficient, requires internet connection. To get location data about
  visible GSM network and wifi networks needs to be send to 3rd party
  server.

  tested on krillin vivid-proposed r107

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

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

[Touch-packages] [Bug 1471581] Re: [Notifications] Delete string in the messaging indicator is confusing

- Design comment -
  06/08/2015

There are new design for UX and visuals for notifications.
Document name Notification system UX spec  page (27)
https://docs.google.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit#

User can dismiss it by swiping either way: left to right or right to left.
User can swipe either way to unlock the screen, if she does, all notifications 
will disappear and be recorded in the notification centre.


** Description changed:

  Hello,
  I don't know is this right place for that bug, but I haven't found better. 
When we receive new SMS, e-mail or similar, we get information in notification 
bar. When we swipe that notify to right we get string 'Delete' and icon of 
trash. I thought that will permanently delete that sms/e-mail from system. But 
it's deleting it only from notify bar. It's little confusing. I think better 
will be 'dismiss', 'reject', 'disgard', 'hide' and change of icon. What do you 
think about that?
+ 
+ - Design comment -
+   06/08/2015
+ 
+ There are new design for UX and visuals for notifications.
+ Document name Notification system UX spec  page (27)
+ 
https://docs.google.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit#
+ 
+ User can dismiss it by swiping either way: left to right or right to left.
+ User can swipe either way to unlock the screen, if she does, all 
notifications will disappear and be recorded in the notification centre.

** Changed in: ubuntu-ux
   Status: Triaged = Fix Committed

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

Title:
  [Notifications] Delete string in the messaging indicator is
  confusing

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-settings-components package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Hello,
  I don't know is this right place for that bug, but I haven't found better. 
When we receive new SMS, e-mail or similar, we get information in notification 
bar. When we swipe that notify to right we get string 'Delete' and icon of 
trash. I thought that will permanently delete that sms/e-mail from system. But 
it's deleting it only from notify bar. It's little confusing. I think better 
will be 'dismiss', 'reject', 'disgard', 'hide' and change of icon. What do you 
think about that?

  - Design comment -
06/08/2015

  There are new design for UX and visuals for notifications.
  Document name Notification system UX spec  page (27)
  
https://docs.google.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit#

  User can dismiss it by swiping either way: left to right or right to left.
  User can swipe either way to unlock the screen, if she does, all 
notifications will disappear and be recorded in the notification centre.

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

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

[Touch-packages] [Bug 1471581] Re: [Notifications] Delete string in the messaging indicator is confusing

** Changed in: ubuntu-ux
   Status: Fix Committed = Won't Fix

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

Title:
  [Notifications] Delete string in the messaging indicator is
  confusing

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  Won't Fix
Status in ubuntu-settings-components package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Hello,
  I don't know is this right place for that bug, but I haven't found better. 
When we receive new SMS, e-mail or similar, we get information in notification 
bar. When we swipe that notify to right we get string 'Delete' and icon of 
trash. I thought that will permanently delete that sms/e-mail from system. But 
it's deleting it only from notify bar. It's little confusing. I think better 
will be 'dismiss', 'reject', 'disgard', 'hide' and change of icon. What do you 
think about that?

  - Design comment -
06/08/2015

  There are new design for UX and visuals for notifications.
  Document name Notification system UX spec  page (27)
  
https://docs.google.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit#

  User can dismiss it by swiping either way: left to right or right to left.
  User can swipe either way to unlock the screen, if she does, all 
notifications will disappear and be recorded in the notification centre.

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

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

[Touch-packages] [Bug 1428277] Re: Icon in notification center too small

** Changed in: ubuntu-ux
   Status: Fix Committed = Won't Fix

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

Title:
  Icon in notification center too small

Status in libqtelegram:
  Invalid
Status in Ubuntu UX:
  Won't Fix
Status in ubuntu-settings-components package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  See image attached. The tappable telegram icon is somewhat small and
  is not trivial to tap, or at least I'm not being able to tap it in a
  way it works in a single tap.

  - Design comment -
06/08/2015

  There are new design for UX and visuals for notifications.
  Document name Notification system UX spec  page ( 29 - 34)
  
https://docs.google.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit#
  When new design will be implemented we will do user testing to be sure what 
icons are tappable.

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

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

[Touch-packages] [Bug 1334916] Re: sshd-ConsoleKit integration patch causes abrupt termination of multichannel sessions

2015-08-06 Thread JanMalte

Is there any information needed to fix it?

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

Title:
  sshd-ConsoleKit integration patch causes abrupt termination of
  multichannel sessions

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  Attached to this report is a small app the reproduces the issue by creating 
multiple channels within one sessions. (I fist hit this issue using JSCH 
library)
  Following information is printed to stdout if sshd is launched with -d flags 
(I've modified the sshd code to print PIDs next to debug level):
  debug3(7526): monitor_read: checking request 156
  debug3(7526): mm_answer_consolekit_register entering
  debug1(7526): session_by_tty: session 0 tty /dev/pts/1
  debug1(7573): server_input_channel_req: channel 2 request pty-req reply 1
  debug1(7573): session_by_channel: session 2 channel 2
  debug1(7573): session_input_channel_req: session 2 req pty-req
  debug1(7573): Allocating pty.
  debug3(7573): mm_request_send entering: type 28
  debug3(7573): mm_pty_allocate: waiting for MONITOR_ANS_PTY
  debug3(7573): mm_request_receive_expect entering: type 29
  debug3(7573): mm_request_receive entering
  debug1(7526): Unable to open session: The name org.freedesktop.ConsoleKit was 
not provided by any .service files
  debug3(7526): mm_request_send entering: type 157
  debug3(7526): mm_request_receive entering
  debug3(7526): monitor_read: checking request 28
  debug3(7526): mm_answer_pty entering
  debug2(7526): session_new: allocate (allocated 2 max 10)
  debug3(7526): session_unused: session id 2 unused
  debug1(7526): session_new: session 2
  mm_request_receive_expect: read: rtype 157 != type 29

  From the log, it looks as if two processes use the same set of pipes
  to communicate to the monitor, one of them is sending
  MONITOR_REQ_CONSOLEKIT_REGISTER, while another  MONITOR_REQ_PTY, and
  because they use same set of pipes, and because both processes use
  same pipe FDs, monitor reply is sometimes delivered to the wrong
  process.

  I can reproduce the failure 90% of time using attached app, which expects 
first argument to be host name, second - login and the third - password, that 
are defaulted to ubuntu:ubuntu@localhost:
  $ ./ssh-multisession 
  Connecting to localhost...Done!
  Authenticating as ubuntu...Done.
  Starting channel 0
  Starting channel 1
  ssh_channel_request_pty()=-1: Socket error: disconnected
  Starting channel 2
  ssh_channel_open_session()=-1: Writing packet: error on socket (or connection 
closed): Operation now in progress
  Starting channel 3

  The same script works fine if sshd is compiled without consolekit.patch:
  ./ssh-multisession debian-host debian debian
  Connecting to 172.17.162.237...Done!
  Authenticating as debian...Done.
  Starting channel 0
  Starting channel 1
  Starting channel 2
  Starting channel 3
  Starting channel 4
  Starting channel 5
  Starting channel 6
  Starting channel 7
  Starting channel 8
  Starting channel 9

  P.S. To compile a test app one needs to have libssh-dev package
  installed on your system.

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

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

[Touch-packages] [Bug 1458509] Re: revoking the coupling of device remotely isn't reflected in inidcator-applet

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read How to report bugs effectively
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures

At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the 
problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
Thanks! 

** Changed in: indicator-bluetooth (Ubuntu)
   Importance: Undecided = Low

** Changed in: indicator-bluetooth (Ubuntu)
   Status: New = Incomplete

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

Title:
  revoking the coupling of device remotely isn't reflected in inidcator-
  applet

Status in indicator-bluetooth package in Ubuntu:
  Incomplete

Bug description:
  The device is still displayed as if it was coupled.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: indicator-bluetooth 0.0.6+14.10.20141006-0ubuntu1
  Uname: Linux 4.0.1-040001-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon May 25 11:51:19 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-04-02 (52 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-bluetooth
  SystemImageInfo:
   current build number: 0
   device name: 
   channel: daily
   last update: Unknown
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1385938] Re: bluetooth indicator has no option to enable file sharing

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

** Changed in: indicator-bluetooth (Ubuntu)
   Status: New = Confirmed

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

Title:
  bluetooth indicator has no option to enable file sharing

Status in Bluetooth Menu:
  New
Status in indicator-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  if you go to bluetooth settings via the bluetooth-indicator, you can
  pair with other devices such as phones, but there is no option to
  enable file sharing. When attempting to send a file with a paired
  device it silently fails. There is no prompt to confirm the file
  transfer.

  As it turns out you have to enable bluetooth filesharing in a separate
  menu Personal file sharing, wich is only available via the Dash.
  There you have the option to recieve files. This is totally not
  obvious and there should atleast be a link from the bluetooth
  indicator to this menu.

  This is on Ubuntu 14.04 LTS on two different laptops I have tried.

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

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

[Touch-packages] [Bug 1298374] Re: Bluetooth applet doesn't remember state

thanks, it's not a bug in the indicator but one in the bluez service,
see bug #446657

** Changed in: indicator-bluetooth (Ubuntu)
   Importance: Undecided = Low

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

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

Title:
  Bluetooth applet doesn't remember state

Status in indicator-bluetooth package in Ubuntu:
  Invalid

Bug description:
  If I disable bluetooth from the applet, reboot and then check the
  state, it is enabled.

  So the applet fails to make the change permanent, as you expect it to
  do.

  Other settings are usually permanent across reboots so I can't see why
  this settings shouldn't be. It saves battery to only turn it on if you
  need it on a laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-bluetooth 0.0.6+14.04.20140207-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
  Uname: Linux 3.13.0-19-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 27 14:04:54 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-03-26 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140325.1)
  SourcePackage: indicator-bluetooth
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.indicator-bluetooth.log: ** (unity-control-center:3393): WARNING **: 
Couldn't register with accessibility bus: Did not receive a reply. Possible 
causes include: the remote application did not send a reply, the message bus 
security policy blocked the reply, the reply timeout expired, or the network 
connection was broken.

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

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

[Touch-packages] [Bug 1328119] Re: [sdk] Scrollbars are too thin and transparent to be useful

2015-08-06 Thread Magdalena Mirowicz

** Changed in: ubuntu-ux
   Status: In Progress = Incomplete

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

Title:
  [sdk] Scrollbars are too thin and transparent to be useful

Status in Ubuntu UI Toolkit:
  Triaged
Status in Ubuntu UX:
  Incomplete
Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged

Bug description:
  Using the code from this branch 
https://code.launchpad.net/~kalikiana/ubuntu-ui-toolkit/interactiveThumb/+merge/218307
  which is practically being merged into trunk now.

  The scrollbars are too thin and too transparent. They blend with the
  background and with the content, and are too hard to see to be useful
  for anything.

  Please make them more noticeable.

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

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

[Touch-packages] [Bug 1278680] Re: indicator-bluetooth-service crashed with SIGSEGV in org_bluez_adapter_set_property()

seems like reports stopped in newer series, unsure why since the code
didn't change...

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

Title:
  indicator-bluetooth-service crashed with SIGSEGV in
  org_bluez_adapter_set_property()

Status in Bluetooth Menu:
  Confirmed
Status in indicator-bluetooth package in Ubuntu:
  Triaged

Bug description:
  My bluetooth device doesn't work at all.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: indicator-bluetooth 0.0.6+14.04.20140124-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: i386
  CurrentDesktop: Unity
  Date: Mon Feb 10 21:23:54 2014
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-bluetooth/indicator-bluetooth-service
  InstallationDate: Installed on 2013-06-04 (251 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 
(20120423)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-bluetooth/indicator-bluetooth-service
  SegvAnalysis:
   Segfault happened at: 0x8054fd8: mov(%ebx),%eax
   PC (0x08054fd8) ok
   source (%ebx) (0x) not located in a known VMA region (needed 
readable region)!
   destination %eax ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-bluetooth
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   g_cclosure_marshal_VOID__PARAM () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: indicator-bluetooth-service crashed with SIGSEGV in 
g_cclosure_marshal_VOID__PARAM()
  UpgradeStatus: Upgraded to trusty on 2014-01-07 (34 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  upstart.indicator-bluetooth.log: ** (process:2140): CRITICAL **: 
bluez.vala:184: GDBus.Error:org.freedesktop.DBus.Error.UnknownObject: Method 
GetProperties with signature  on interface org.bluez.Adapter doesn't exist

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

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

[Touch-packages] [Bug 1272686] Re: indicator-bluetooth-service crashed with SIGSEGV in org_bluez_adapter_set_property()

seems like reports stopped in newer series, unsure why since the code
didn't change...

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

Title:
  indicator-bluetooth-service crashed with SIGSEGV in
  org_bluez_adapter_set_property()

Status in indicator-bluetooth package in Ubuntu:
  Triaged

Bug description:
  After activating bluetooth.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: indicator-bluetooth 0.0.6+14.04.20140124-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-1.16-generic 3.13.0-rc7
  Uname: Linux 3.13.0-1-generic x86_64
  ApportVersion: 2.13.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jan 25 15:02:43 2014
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-bluetooth/indicator-bluetooth-service
  InstallationDate: Installed on 2013-12-10 (45 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64+mac (20131210)
  ProcCmdline: 
/usr/lib/x86_64-linux-gnu/indicator-bluetooth/indicator-bluetooth-service
  SegvAnalysis:
   Segfault happened at: 0x40d880:  mov(%rbx),%rdi
   PC (0x0040d880) ok
   source (%rbx) (0x) not located in a known VMA region (needed 
readable region)!
   destination %rdi ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-bluetooth
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: indicator-bluetooth-service crashed with SIGSEGV in g_closure_invoke()
  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/indicator-bluetooth/+bug/1272686/+subscriptions

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

[Touch-packages] [Bug 1479085] Re: package modemmanager 1.4.10-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100

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

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

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

Title:
  package modemmanager 1.4.10-1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 100

Status in modemmanager package in Ubuntu:
  Confirmed

Bug description:
  I had Ubuntu 15.04 and I updated my system through terminal. Right
  after finishing the upgrade I got this error.

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: modemmanager 1.4.10-1
  ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3
  Uname: Linux 4.1.0-2-generic x86_64
  ApportVersion: 2.18-0ubuntu5
  Architecture: amd64
  Date: Tue Jul 28 22:05:11 2015
  DuplicateSignature: package:modemmanager:1.4.10-1:subprocess installed 
post-installation script returned error exit status 100
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 100
  InstallationDate: Installed on 2015-05-20 (69 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.18.1ubuntu1
   apt  1.0.9.10ubuntu1
  SourcePackage: modemmanager
  Title: package modemmanager 1.4.10-1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 100
  UpgradeStatus: Upgraded to wily on 2015-07-28 (0 days ago)

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

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

[Touch-packages] [Bug 1482198] [NEW] tab becomes white after loading

2015-08-06 Thread Thibaut Brandscheid

Public bug reported:

Ubuntu Touch (15.04 r3) Meizu MX4

When clicking at a link in the Telegram app, the web browser open - as
expected - a new tab and starts loading the web page. While loading the
web page is visible. When loading is done, the web page become white. I
tried to zoom in or out in the page but the page stays white.

web page: http://www.heroesfire.com/hots/guide/azmodan-lord-of-sin-173

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

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

Title:
  tab becomes white after loading

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Ubuntu Touch (15.04 r3) Meizu MX4

  When clicking at a link in the Telegram app, the web browser open - as
  expected - a new tab and starts loading the web page. While loading
  the web page is visible. When loading is done, the web page become
  white. I tried to zoom in or out in the page but the page stays white.

  web page: http://www.heroesfire.com/hots/guide/azmodan-lord-of-sin-173

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

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

[Touch-packages] [Bug 1458235] Re: [scopes] Allow users to set arbitrary location for scopes.

2015-08-06 Thread Paty Davila

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

** Changed in: ubuntu-ux
   Status: Triaged = In Progress

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

Title:
  [scopes] Allow users to set arbitrary location for scopes.

Status in Ubuntu UX:
  In Progress
Status in unity-scopes-shell package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  New

Bug description:
  Currently I can't set my location manually for any scope. They get it
  somehow automatically, most of the time wrongly. It would be nice if a
  user could somehow select the location he/she wants.

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

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

[Touch-packages] [Bug 1481489] Re: Icons page in UI Toolkit gallery not resolution independent

2015-08-06 Thread Christian Dywan

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

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

Title:
  Icons page in UI Toolkit gallery not resolution independent

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

Bug description:
  What it says on the tin. The icons demo page in the UI toolkit gallery
  hard-codes 24 and doesn't use grid units.

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

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

[Touch-packages] [Bug 1475205] Re: Random Chinese character missing with Ubuntu font

2015-08-06 Thread Timo Jyrinki

adb push Main.qml /home/phablet
adb shell
qmlscene Main.qml 
--desktop_file_hint=/usr/share/applications/mediaplayer-app.desktop


** Attachment added: my combined test qml
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1475205/+attachment/4440445/+files/Main.qml

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

Title:
  Random Chinese character missing with Ubuntu font

Status in Canonical System Image:
  In Progress
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in qtdeclarative-opensource-src package in Ubuntu:
  Invalid
Status in ubuntu-font-family-sources package in Ubuntu:
  Incomplete
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid

Bug description:
  After applied 50 GU setting in image, we started seeing randomly
  missing Chinese characters across scopes and apps header, not clipped
  at the begin or end of string, sometimes in the middle.

  STEPS:

  1. Switch display language to zh_CN in system settings
  2. Reboot the phone

  EXPECTED:

  I should see all header strings displayed properly.

  ACTUAL:

  Randomly missing character.

  VERSIONS:

  current build number: 51
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.zh-proposed
  last update: 2015-07-16 04:59:10
  version version: 51
  version ubuntu: 20150716
  version device: 20150709-8965e37
  version custom: 20150716-819-9-6

  -- update --
  The problem of missing characters can be reproduced even on a desktop, 
outside of the header, without importing Ubuntu.Components:

  import QtQuick 2.0
  Item {
  width: 800
  height: 600

  Text {
  anchors.centerIn: parent
  text: 系统设置 one two
  font.family: Ubuntu
  font.pixelSize: 69
  font.weight: Font.Light
  }
  }

  The problem only appears to occur with this specific combination of
  font family, pixelSize and weight. Tim Peeters reproduced the problem
  on vivid on a laptop without changing the default settings for the
  language (LANGUAGE=en_US).

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

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

[Touch-packages] [Bug 1475205] Re: Random Chinese character missing with Ubuntu font

2015-08-06 Thread Timo Jyrinki

Could you please test on vivid+overlay with the silo 33
(https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/landing-033/). The debdiff is
http://paste.ubuntu.com/12013270/. For example: citrain device-upgrade
33  ubuntu

Check with dpkg -s libqt5core5a that the version is 5.4.1+dfsg-2ubuntu8

Please share your test results. On my mako I can't see a difference. The
example in comment #17 seems to always work my mako. But the test code
from comment #12 always tends to have one letter missing, with or
without the PPA.

So arale/krillin results would be welcome. I don't see regressions, so
if even one case is fixed with the updated qtbase I can land this, but I
can't see differences on my mako.

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

Title:
  Random Chinese character missing with Ubuntu font

Status in Canonical System Image:
  In Progress
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in qtdeclarative-opensource-src package in Ubuntu:
  Invalid
Status in ubuntu-font-family-sources package in Ubuntu:
  Incomplete
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid

Bug description:
  After applied 50 GU setting in image, we started seeing randomly
  missing Chinese characters across scopes and apps header, not clipped
  at the begin or end of string, sometimes in the middle.

  STEPS:

  1. Switch display language to zh_CN in system settings
  2. Reboot the phone

  EXPECTED:

  I should see all header strings displayed properly.

  ACTUAL:

  Randomly missing character.

  VERSIONS:

  current build number: 51
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.zh-proposed
  last update: 2015-07-16 04:59:10
  version version: 51
  version ubuntu: 20150716
  version device: 20150709-8965e37
  version custom: 20150716-819-9-6

  -- update --
  The problem of missing characters can be reproduced even on a desktop, 
outside of the header, without importing Ubuntu.Components:

  import QtQuick 2.0
  Item {
  width: 800
  height: 600

  Text {
  anchors.centerIn: parent
  text: 系统设置 one two
  font.family: Ubuntu
  font.pixelSize: 69
  font.weight: Font.Light
  }
  }

  The problem only appears to occur with this specific combination of
  font family, pixelSize and weight. Tim Peeters reproduced the problem
  on vivid on a laptop without changing the default settings for the
  language (LANGUAGE=en_US).

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

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

[Touch-packages] [Bug 1456349] Re: [notifications] Remove the files tab in the notification area

** Changed in: ubuntu-ux
 Assignee: Paty Davila (dizzypaty) = Grazina (boroskograzina)

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

Title:
  [notifications] Remove the files tab in the notification area

Status in Ubuntu UX:
  Triaged
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  The files tab in the notification is not so important as it is
  positioned. Using Ubuntu Phone now for several weeks I can just
  remeber to have used it once. COnsidering that it is positioned much
  to prominent - so remove it and make it an extra app or show this kind
  of notifications in the message part.

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

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

[Touch-packages] [Bug 1401491] Re: Bluetooth icon shows a little lock, and there's no indication of what it means

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

** This bug has been marked a duplicate of bug 1311211
   Bluetooth icon has a padlock emblem when paired with device

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

Title:
  Bluetooth icon shows a little lock, and there's no indication of what
  it means

Status in indicator-bluetooth package in Ubuntu:
  New

Bug description:
  All of a sudden the Bluetooth icon on the top right notification area shows a 
little lock icon (see screenshot).
  By clicking on the icon, there's no way to figure out what the icon means. 
  After turning bluetooth off and on, the lock icon disappeared.
  Then, no matter whether I turn bluetooth on or off, no matter whether visible 
or not, the lock icon never reappeared (the bluetooth icon, without a lock, 
greys out as expected when bluetooth is turned off).

  I thought the lock may mean that Receive Files via Bluetooth was
  turned off in Personal File Sharing settings (see also #958661: that
  setting should be in the Bluetooth settings), but even after enabling
  it, the lock was still showing up (until I turned off and on
  bluetooth). After disabling file reception again, the lock icon did
  not reappear.

  I suspect that the icon appeared because of an attempt to send a file to the 
computer which was rejected, because it appeared just after that but:
  1 - if that is the case, then an indication should be given, e.g. when 
rolling over the icon or when unfolding the submenu. You should ALWAYS be able 
to know what the  an icon means
  2 - if that is the case, there should be a way to dismiss the notice, other 
than turning off and on bluetooth
  3 - a toast (or whatever it is called) notification should also be shown at 
the moment the file is rejected

  If the lock is instead supposed to mean that file reception is turned
  off, or that visibility is turned off, then it's not working properly.
  If it means anything else, it is not working properly either, as I
  haven't changed any other setting when the lock disappeared.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Uname: Linux 3.13.0-40-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Dec 10 10:45:21 2014
  InstallationDate: Installed on 2013-10-11 (424 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Acer Aspire V3-571G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic.efi.signed 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to trusty on 2014-05-24 (199 days ago)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.07
  dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
  dmi.product.name: Aspire V3-571G
  dmi.product.version: V2.07
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: A4:17:31:0D:4A:70  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING PSCAN ISCAN 
RX bytes:819218 acl:1083 sco:0 events:198 errors:0
TX bytes:3969 acl:103 sco:0 commands:71 errors:0

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

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

[Touch-packages] [Bug 1458491] Re: indicator-bluetooth misses controls to enable file transfer

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

** Changed in: indicator-bluetooth (Ubuntu)
   Importance: Undecided = Low

** This bug has been marked a duplicate of bug 1385938
   bluetooth indicator has no option to enable file sharing

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

Title:
  indicator-bluetooth misses controls to enable file transfer

Status in indicator-bluetooth package in Ubuntu:
  New

Bug description:
  The default settings of `indicator-bluetooth` make file transfers fail
  without feedback (not too great, but not the issue here). One has to
  install `bluemon` and enable file transfer options like ~allow
  read/write and ~allow trusted devices. The user expects `indicator-
  bluetooth` to offer a sufficient set of options to transfer file which
  is a quite basic task for bluetooth connections. The options should be
  added to sufficient hints displayed in the application (e.g. a hint
  that the settings aren't implemented yet and that one needs to manage
  the device with `bluemon` like described above).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: indicator-bluetooth 0.0.6+14.10.20141006-0ubuntu1
  Uname: Linux 4.0.1-040001-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon May 25 10:54:04 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-04-02 (52 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-bluetooth
  SystemImageInfo:
   current build number: 0
   device name: 
   channel: daily
   last update: Unknown
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.indicator-bluetooth.log:
   (unity-control-center:7633): Bluetooth-WARNING **: Can't open the plugins 
dir: Fehler beim Öffnen des Ordners »/usr/lib/gnome-bluetooth/plugins«: Datei 
oder Verzeichnis nicht gefunden
   
   (unity-control-center:7633): Bluetooth-WARNING **: Could not open RFKILL 
control device, please verify your installation

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

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

[Touch-packages] [Bug 1311211] Re: Bluetooth icon has a padlock emblem when paired with device