[Touch-packages] [Bug 1341681] Re: Autopilot tests should stop using deprecated emulators module

2015-03-19 Thread Launchpad Bug Tracker
This bug was fixed in the package unity8 - 8.02+15.04.20150318-0ubuntu1

---
unity8 (8.02+15.04.20150318-0ubuntu1) vivid; urgency=medium

  [ Albert Astals Cid ]
  * Add some context to tr calls (LP: #1431497)
  * Require binaries and .pc files we call from code
  * Test: More stubborn flick to the end

  [ Andrea Cimitan ]
  * Refactor PreviewOverlay to fix weird zoom out/in animations when
previewing images from the Previews

  [ CI Train Bot ]
  * Resync trunk.

  [ Charles Kerr ]
  * Re-enable a rotation lock test now that the bug that broke that test
has been fixed. (LP: #1410915)

  [ Daniel d'Andrada ]
  * Darkened area behind indicators menu should eat input until it fully
disappears (LP: #1417967)
  * DesktopStage - fix focus switch when user taps on window (LP:
#1431325)
  * Fix warnings when launching tutorial
  * Make MouseTouchAdaptor controllable from within QML
  * Make tst_Shell absorb tst_TabletShell

  [ Leo Arias ]
  * Changed the autopilot dependencies so they do not require qt4. (LP:
#1429158)
  * Drop the support for python2 in autopilot tests. (LP: #1429163)
  * Stop using the deprecated toolkit emulators namespace in autopilot
tests. (LP: #1341681)

  [ Michael Terry ]
  * Don't close wizard  edge tutorial when the unity8-dash closes (LP:
#1425484)
  * Don't let the wizard sit indefinitely, waiting for a wizard page to
finish preparing itself. (LP: #1425737)
  * Fix two broken qmluitest files by waiting for everything to settle
before starting the tests.
  * Only call unlockAllModems once the wizard is done. (LP: #1425161)
(LP: #1425161)
  * When we are locking the user out from too many login failures,
notice when time passes even if the device is suspended. (LP:
#1396817) (LP: #1396817)

  [ Michael Zanetti ]
  * Add a mouse area to the indicators panel so we can open them by
clicking. (LP: #1417650)
  * fix launcher not reacting to first click when revealed by mouse
hover, add tests
  * performance improvements (LP: #1430233, #1425087)

  [ Michał Sawicz ]
  * Remove the activity indicator from tests
  * Use targets instead of custom ld arguments for linking

  [ Mirco Müller ]
  * Updated the visuals of the SwipeToAct-widget for incoming-call snap-
decision notifications according to new design-spec.
  * Updated the visuals of the SwipeToAct-widget for incoming-call snap-
decision notifications according to new design-spec.
 -- CI Train Bot ci-train-...@canonical.com   Wed, 18 Mar 2015 10:19:06 +

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

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

Title:
  Autopilot tests should stop using deprecated emulators module

Status in Dialer app for Ubuntu Touch:
  In Progress
Status in Dropping Letters:
  New
Status in Music application for Ubuntu devices:
  Fix Released
Status in Notes App:
  New
Status in Ubuntu Reminders app:
  Fix Released
Status in Sudoku game for Ubuntu Touch:
  New
Status in Calculator application for Ubuntu devices:
  Fix Released
Status in Calendar application for Ubuntu devices:
  Fix Released
Status in Clock application for Ubuntu devices:
  Fix Released
Status in Document Viewer application for Ubuntu devices:
  New
Status in File Manager application for Ubuntu devices:
  Fix Released
Status in RSS Feed Reader application for Ubuntu devices:
  Incomplete
Status in Terminal application for Ubuntu devices:
  Fix Released
Status in Weather application for Ubuntu devices:
  Incomplete
Status in dialer-app package in Ubuntu:
  Fix Released
Status in reminders-app package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Autopilot tests should stop using deprecated emulators module. Instead
  the new custom_proxy_objects modules should be used and called
  directly.

  Please note until https://bugs.launchpad.net/ubuntu-ui-
  toolkit/+bug/1341679 is fixed, the deprecation warning will still
  appear.

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

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


[Touch-packages] [Bug 1425161] Re: [Wizard] SIM PIN page before language selection

2015-03-19 Thread Launchpad Bug Tracker
This bug was fixed in the package unity8 - 8.02+15.04.20150318-0ubuntu1

---
unity8 (8.02+15.04.20150318-0ubuntu1) vivid; urgency=medium

  [ Albert Astals Cid ]
  * Add some context to tr calls (LP: #1431497)
  * Require binaries and .pc files we call from code
  * Test: More stubborn flick to the end

  [ Andrea Cimitan ]
  * Refactor PreviewOverlay to fix weird zoom out/in animations when
previewing images from the Previews

  [ CI Train Bot ]
  * Resync trunk.

  [ Charles Kerr ]
  * Re-enable a rotation lock test now that the bug that broke that test
has been fixed. (LP: #1410915)

  [ Daniel d'Andrada ]
  * Darkened area behind indicators menu should eat input until it fully
disappears (LP: #1417967)
  * DesktopStage - fix focus switch when user taps on window (LP:
#1431325)
  * Fix warnings when launching tutorial
  * Make MouseTouchAdaptor controllable from within QML
  * Make tst_Shell absorb tst_TabletShell

  [ Leo Arias ]
  * Changed the autopilot dependencies so they do not require qt4. (LP:
#1429158)
  * Drop the support for python2 in autopilot tests. (LP: #1429163)
  * Stop using the deprecated toolkit emulators namespace in autopilot
tests. (LP: #1341681)

  [ Michael Terry ]
  * Don't close wizard  edge tutorial when the unity8-dash closes (LP:
#1425484)
  * Don't let the wizard sit indefinitely, waiting for a wizard page to
finish preparing itself. (LP: #1425737)
  * Fix two broken qmluitest files by waiting for everything to settle
before starting the tests.
  * Only call unlockAllModems once the wizard is done. (LP: #1425161)
(LP: #1425161)
  * When we are locking the user out from too many login failures,
notice when time passes even if the device is suspended. (LP:
#1396817) (LP: #1396817)

  [ Michael Zanetti ]
  * Add a mouse area to the indicators panel so we can open them by
clicking. (LP: #1417650)
  * fix launcher not reacting to first click when revealed by mouse
hover, add tests
  * performance improvements (LP: #1430233, #1425087)

  [ Michał Sawicz ]
  * Remove the activity indicator from tests
  * Use targets instead of custom ld arguments for linking

  [ Mirco Müller ]
  * Updated the visuals of the SwipeToAct-widget for incoming-call snap-
decision notifications according to new design-spec.
  * Updated the visuals of the SwipeToAct-widget for incoming-call snap-
decision notifications according to new design-spec.
 -- CI Train Bot ci-train-...@canonical.com   Wed, 18 Mar 2015 10:19:06 +

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

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

Title:
  [Wizard] SIM PIN page before language selection

Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Test case.
  - Flash the device with devel-proposed channel (Vivid).
  - Go to the wizard.

  Expected result.
  - Language selection is presented first.

  Actual result.
  - SIM PIN page is presented in English. Language selection should be first.

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

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

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


[Touch-packages] [Bug 1396817] Re: Device locked timer doesn't decrease if the screen is off

2015-03-19 Thread Launchpad Bug Tracker
This bug was fixed in the package unity8 - 8.02+15.04.20150318-0ubuntu1

---
unity8 (8.02+15.04.20150318-0ubuntu1) vivid; urgency=medium

  [ Albert Astals Cid ]
  * Add some context to tr calls (LP: #1431497)
  * Require binaries and .pc files we call from code
  * Test: More stubborn flick to the end

  [ Andrea Cimitan ]
  * Refactor PreviewOverlay to fix weird zoom out/in animations when
previewing images from the Previews

  [ CI Train Bot ]
  * Resync trunk.

  [ Charles Kerr ]
  * Re-enable a rotation lock test now that the bug that broke that test
has been fixed. (LP: #1410915)

  [ Daniel d'Andrada ]
  * Darkened area behind indicators menu should eat input until it fully
disappears (LP: #1417967)
  * DesktopStage - fix focus switch when user taps on window (LP:
#1431325)
  * Fix warnings when launching tutorial
  * Make MouseTouchAdaptor controllable from within QML
  * Make tst_Shell absorb tst_TabletShell

  [ Leo Arias ]
  * Changed the autopilot dependencies so they do not require qt4. (LP:
#1429158)
  * Drop the support for python2 in autopilot tests. (LP: #1429163)
  * Stop using the deprecated toolkit emulators namespace in autopilot
tests. (LP: #1341681)

  [ Michael Terry ]
  * Don't close wizard  edge tutorial when the unity8-dash closes (LP:
#1425484)
  * Don't let the wizard sit indefinitely, waiting for a wizard page to
finish preparing itself. (LP: #1425737)
  * Fix two broken qmluitest files by waiting for everything to settle
before starting the tests.
  * Only call unlockAllModems once the wizard is done. (LP: #1425161)
(LP: #1425161)
  * When we are locking the user out from too many login failures,
notice when time passes even if the device is suspended. (LP:
#1396817) (LP: #1396817)

  [ Michael Zanetti ]
  * Add a mouse area to the indicators panel so we can open them by
clicking. (LP: #1417650)
  * fix launcher not reacting to first click when revealed by mouse
hover, add tests
  * performance improvements (LP: #1430233, #1425087)

  [ Michał Sawicz ]
  * Remove the activity indicator from tests
  * Use targets instead of custom ld arguments for linking

  [ Mirco Müller ]
  * Updated the visuals of the SwipeToAct-widget for incoming-call snap-
decision notifications according to new design-spec.
  * Updated the visuals of the SwipeToAct-widget for incoming-call snap-
decision notifications according to new design-spec.
 -- CI Train Bot ci-train-...@canonical.com   Wed, 18 Mar 2015 10:19:06 +

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

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

Title:
  Device locked timer doesn't decrease if the screen is off

Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  I'm on RTM #9

  Way to reproduce:
  - Unplug phone from charger / PC
  - Insert 5 wrong PIN
  - The phone says the device is locked for 5 minutes
  - Turn off the screen
  - Go to drink a coffe
  - Return 5 minutes later
  - Turn on the screen

  What I expect:
  - I'm able to insert my pin and use my phone

  What happens:
  - The phone says the device is locked for 5 minutes

  After some tries, I'm pretty sure the timer goes down only if the
  screen is on

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

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


[Touch-packages] [Bug 1425484] Re: wizard aborts and goes directly to the dash

2015-03-19 Thread Launchpad Bug Tracker
This bug was fixed in the package unity8 - 8.02+15.04.20150318-0ubuntu1

---
unity8 (8.02+15.04.20150318-0ubuntu1) vivid; urgency=medium

  [ Albert Astals Cid ]
  * Add some context to tr calls (LP: #1431497)
  * Require binaries and .pc files we call from code
  * Test: More stubborn flick to the end

  [ Andrea Cimitan ]
  * Refactor PreviewOverlay to fix weird zoom out/in animations when
previewing images from the Previews

  [ CI Train Bot ]
  * Resync trunk.

  [ Charles Kerr ]
  * Re-enable a rotation lock test now that the bug that broke that test
has been fixed. (LP: #1410915)

  [ Daniel d'Andrada ]
  * Darkened area behind indicators menu should eat input until it fully
disappears (LP: #1417967)
  * DesktopStage - fix focus switch when user taps on window (LP:
#1431325)
  * Fix warnings when launching tutorial
  * Make MouseTouchAdaptor controllable from within QML
  * Make tst_Shell absorb tst_TabletShell

  [ Leo Arias ]
  * Changed the autopilot dependencies so they do not require qt4. (LP:
#1429158)
  * Drop the support for python2 in autopilot tests. (LP: #1429163)
  * Stop using the deprecated toolkit emulators namespace in autopilot
tests. (LP: #1341681)

  [ Michael Terry ]
  * Don't close wizard  edge tutorial when the unity8-dash closes (LP:
#1425484)
  * Don't let the wizard sit indefinitely, waiting for a wizard page to
finish preparing itself. (LP: #1425737)
  * Fix two broken qmluitest files by waiting for everything to settle
before starting the tests.
  * Only call unlockAllModems once the wizard is done. (LP: #1425161)
(LP: #1425161)
  * When we are locking the user out from too many login failures,
notice when time passes even if the device is suspended. (LP:
#1396817) (LP: #1396817)

  [ Michael Zanetti ]
  * Add a mouse area to the indicators panel so we can open them by
clicking. (LP: #1417650)
  * fix launcher not reacting to first click when revealed by mouse
hover, add tests
  * performance improvements (LP: #1430233, #1425087)

  [ Michał Sawicz ]
  * Remove the activity indicator from tests
  * Use targets instead of custom ld arguments for linking

  [ Mirco Müller ]
  * Updated the visuals of the SwipeToAct-widget for incoming-call snap-
decision notifications according to new design-spec.
  * Updated the visuals of the SwipeToAct-widget for incoming-call snap-
decision notifications according to new design-spec.
 -- CI Train Bot ci-train-...@canonical.com   Wed, 18 Mar 2015 10:19:06 +

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

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

Title:
  wizard aborts and goes directly to the dash

Status in the base for Ubuntu mobile products:
  In Progress
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  TEST CASE:
  1. Go to system-settings and do a factory reset
  2. After reboot in the wizard, dismiss the first SIM PIN dialog
  3. Select 'French' in the list of languages
  4. Tap on 'Continue'

  EXPECT RESULT
  The step 'device security' is displayed

  ACTUAL RESULT
  A blank screen is displayed (empty page with the default background) and 
after a few seconds the wizard stops and the dash loads. The edge intro is 
skipped.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.02+15.04.20150224-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: armhf
  Date: Wed Feb 25 11:41:16 2015
  InstallationDate: Installed on 2015-02-25 (0 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150225-020204)
  SourcePackage: unity8
  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/1425484/+subscriptions

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


[Touch-packages] [Bug 1425087] Re: Launcher re-ordering became laggy

2015-03-19 Thread Launchpad Bug Tracker
This bug was fixed in the package unity8 - 8.02+15.04.20150318-0ubuntu1

---
unity8 (8.02+15.04.20150318-0ubuntu1) vivid; urgency=medium

  [ Albert Astals Cid ]
  * Add some context to tr calls (LP: #1431497)
  * Require binaries and .pc files we call from code
  * Test: More stubborn flick to the end

  [ Andrea Cimitan ]
  * Refactor PreviewOverlay to fix weird zoom out/in animations when
previewing images from the Previews

  [ CI Train Bot ]
  * Resync trunk.

  [ Charles Kerr ]
  * Re-enable a rotation lock test now that the bug that broke that test
has been fixed. (LP: #1410915)

  [ Daniel d'Andrada ]
  * Darkened area behind indicators menu should eat input until it fully
disappears (LP: #1417967)
  * DesktopStage - fix focus switch when user taps on window (LP:
#1431325)
  * Fix warnings when launching tutorial
  * Make MouseTouchAdaptor controllable from within QML
  * Make tst_Shell absorb tst_TabletShell

  [ Leo Arias ]
  * Changed the autopilot dependencies so they do not require qt4. (LP:
#1429158)
  * Drop the support for python2 in autopilot tests. (LP: #1429163)
  * Stop using the deprecated toolkit emulators namespace in autopilot
tests. (LP: #1341681)

  [ Michael Terry ]
  * Don't close wizard  edge tutorial when the unity8-dash closes (LP:
#1425484)
  * Don't let the wizard sit indefinitely, waiting for a wizard page to
finish preparing itself. (LP: #1425737)
  * Fix two broken qmluitest files by waiting for everything to settle
before starting the tests.
  * Only call unlockAllModems once the wizard is done. (LP: #1425161)
(LP: #1425161)
  * When we are locking the user out from too many login failures,
notice when time passes even if the device is suspended. (LP:
#1396817) (LP: #1396817)

  [ Michael Zanetti ]
  * Add a mouse area to the indicators panel so we can open them by
clicking. (LP: #1417650)
  * fix launcher not reacting to first click when revealed by mouse
hover, add tests
  * performance improvements (LP: #1430233, #1425087)

  [ Michał Sawicz ]
  * Remove the activity indicator from tests
  * Use targets instead of custom ld arguments for linking

  [ Mirco Müller ]
  * Updated the visuals of the SwipeToAct-widget for incoming-call snap-
decision notifications according to new design-spec.
  * Updated the visuals of the SwipeToAct-widget for incoming-call snap-
decision notifications according to new design-spec.
 -- CI Train Bot ci-train-...@canonical.com   Wed, 18 Mar 2015 10:19:06 +

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

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

Title:
  Launcher re-ordering became laggy

Status in the base for Ubuntu mobile products:
  In Progress
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  image 121 vivid-proposed on krillin

  1. try to re-order the launcher icon order

  What happens:
  the icon does not get reordered instantly, rather they hang on screen for a 
bit. 

  attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.02+15.04.20150216.1-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: armhf
  Date: Tue Feb 24 18:53:38 2015
  InstallationDate: Installed on 2015-02-24 (0 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150224-020204)
  SourcePackage: unity8
  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/1425087/+subscriptions

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


[Touch-packages] [Bug 1423817] Re: Ubuntu Phone: No sound notifications

2015-03-19 Thread hutchy71
Same to me. No sound incoming message.

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

Title:
  Ubuntu Phone: No sound notifications

Status in indicator-sound package in Ubuntu:
  Invalid

Bug description:
  Hi!

  In the BQ Ubuntu Edition, when I receive a notification by Telegram or
  webapp, I don't get a sound notification, just a vibration.

  In the system settings is set all for a play sound.

  Thanks in advance!

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

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


[Touch-packages] [Bug 1410915] Re: com.ubuntu.touch.system rotation-lock can't be changed by the checkbox in indicators

2015-03-19 Thread Launchpad Bug Tracker
This bug was fixed in the package unity8 - 8.02+15.04.20150318-0ubuntu1

---
unity8 (8.02+15.04.20150318-0ubuntu1) vivid; urgency=medium

  [ Albert Astals Cid ]
  * Add some context to tr calls (LP: #1431497)
  * Require binaries and .pc files we call from code
  * Test: More stubborn flick to the end

  [ Andrea Cimitan ]
  * Refactor PreviewOverlay to fix weird zoom out/in animations when
previewing images from the Previews

  [ CI Train Bot ]
  * Resync trunk.

  [ Charles Kerr ]
  * Re-enable a rotation lock test now that the bug that broke that test
has been fixed. (LP: #1410915)

  [ Daniel d'Andrada ]
  * Darkened area behind indicators menu should eat input until it fully
disappears (LP: #1417967)
  * DesktopStage - fix focus switch when user taps on window (LP:
#1431325)
  * Fix warnings when launching tutorial
  * Make MouseTouchAdaptor controllable from within QML
  * Make tst_Shell absorb tst_TabletShell

  [ Leo Arias ]
  * Changed the autopilot dependencies so they do not require qt4. (LP:
#1429158)
  * Drop the support for python2 in autopilot tests. (LP: #1429163)
  * Stop using the deprecated toolkit emulators namespace in autopilot
tests. (LP: #1341681)

  [ Michael Terry ]
  * Don't close wizard  edge tutorial when the unity8-dash closes (LP:
#1425484)
  * Don't let the wizard sit indefinitely, waiting for a wizard page to
finish preparing itself. (LP: #1425737)
  * Fix two broken qmluitest files by waiting for everything to settle
before starting the tests.
  * Only call unlockAllModems once the wizard is done. (LP: #1425161)
(LP: #1425161)
  * When we are locking the user out from too many login failures,
notice when time passes even if the device is suspended. (LP:
#1396817) (LP: #1396817)

  [ Michael Zanetti ]
  * Add a mouse area to the indicators panel so we can open them by
clicking. (LP: #1417650)
  * fix launcher not reacting to first click when revealed by mouse
hover, add tests
  * performance improvements (LP: #1430233, #1425087)

  [ Michał Sawicz ]
  * Remove the activity indicator from tests
  * Use targets instead of custom ld arguments for linking

  [ Mirco Müller ]
  * Updated the visuals of the SwipeToAct-widget for incoming-call snap-
decision notifications according to new design-spec.
  * Updated the visuals of the SwipeToAct-widget for incoming-call snap-
decision notifications according to new design-spec.
 -- CI Train Bot ci-train-...@canonical.com   Wed, 18 Mar 2015 10:19:06 +

** Changed in: unity8 (Ubuntu)
   Status: New = 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/1410915

Title:
  com.ubuntu.touch.system rotation-lock can't be changed by the checkbox
  in indicators

Status in the base for Ubuntu mobile products:
  Fix Released
Status in indicator-display package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  When we turo on/off the checkbox for rotation lock in indicators. 
  The gsettings com.ubuntu.touch.system rotation-lock didn't change.

  How to reproduce: 
  1. open the Indicator Rotation page.
  2. click the checkbox to turn on/off the rotation lock.
  When doing 2. Use phablet-shell to go into the phone. And use gsettings get 
com.ubuntu.touch.system rotation-lock. It always print out false.

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

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


[Touch-packages] [Bug 1417650] Re: Pointer motion and crossing events are missing

2015-03-19 Thread Launchpad Bug Tracker
This bug was fixed in the package unity8 - 8.02+15.04.20150318-0ubuntu1

---
unity8 (8.02+15.04.20150318-0ubuntu1) vivid; urgency=medium

  [ Albert Astals Cid ]
  * Add some context to tr calls (LP: #1431497)
  * Require binaries and .pc files we call from code
  * Test: More stubborn flick to the end

  [ Andrea Cimitan ]
  * Refactor PreviewOverlay to fix weird zoom out/in animations when
previewing images from the Previews

  [ CI Train Bot ]
  * Resync trunk.

  [ Charles Kerr ]
  * Re-enable a rotation lock test now that the bug that broke that test
has been fixed. (LP: #1410915)

  [ Daniel d'Andrada ]
  * Darkened area behind indicators menu should eat input until it fully
disappears (LP: #1417967)
  * DesktopStage - fix focus switch when user taps on window (LP:
#1431325)
  * Fix warnings when launching tutorial
  * Make MouseTouchAdaptor controllable from within QML
  * Make tst_Shell absorb tst_TabletShell

  [ Leo Arias ]
  * Changed the autopilot dependencies so they do not require qt4. (LP:
#1429158)
  * Drop the support for python2 in autopilot tests. (LP: #1429163)
  * Stop using the deprecated toolkit emulators namespace in autopilot
tests. (LP: #1341681)

  [ Michael Terry ]
  * Don't close wizard  edge tutorial when the unity8-dash closes (LP:
#1425484)
  * Don't let the wizard sit indefinitely, waiting for a wizard page to
finish preparing itself. (LP: #1425737)
  * Fix two broken qmluitest files by waiting for everything to settle
before starting the tests.
  * Only call unlockAllModems once the wizard is done. (LP: #1425161)
(LP: #1425161)
  * When we are locking the user out from too many login failures,
notice when time passes even if the device is suspended. (LP:
#1396817) (LP: #1396817)

  [ Michael Zanetti ]
  * Add a mouse area to the indicators panel so we can open them by
clicking. (LP: #1417650)
  * fix launcher not reacting to first click when revealed by mouse
hover, add tests
  * performance improvements (LP: #1430233, #1425087)

  [ Michał Sawicz ]
  * Remove the activity indicator from tests
  * Use targets instead of custom ld arguments for linking

  [ Mirco Müller ]
  * Updated the visuals of the SwipeToAct-widget for incoming-call snap-
decision notifications according to new design-spec.
  * Updated the visuals of the SwipeToAct-widget for incoming-call snap-
decision notifications according to new design-spec.
 -- CI Train Bot ci-train-...@canonical.com   Wed, 18 Mar 2015 10:19:06 +

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

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

Title:
  Pointer motion and crossing events are missing

Status in Mir:
  Fix Released
Status in Qt integration with the Mir display server:
  In Progress
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Unity 8 doesn't seem to emit events for when the pointer enters or
  leaves a window, or when the pointer moves around inside a window. It
  does seem to emit the needed motion events when the mouse is dragged
  though.

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

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


[Touch-packages] [Bug 1417967] Re: Tablet: Dash flashes if double tapping outside open indicators

2015-03-19 Thread Launchpad Bug Tracker
This bug was fixed in the package unity8 - 8.02+15.04.20150318-0ubuntu1

---
unity8 (8.02+15.04.20150318-0ubuntu1) vivid; urgency=medium

  [ Albert Astals Cid ]
  * Add some context to tr calls (LP: #1431497)
  * Require binaries and .pc files we call from code
  * Test: More stubborn flick to the end

  [ Andrea Cimitan ]
  * Refactor PreviewOverlay to fix weird zoom out/in animations when
previewing images from the Previews

  [ CI Train Bot ]
  * Resync trunk.

  [ Charles Kerr ]
  * Re-enable a rotation lock test now that the bug that broke that test
has been fixed. (LP: #1410915)

  [ Daniel d'Andrada ]
  * Darkened area behind indicators menu should eat input until it fully
disappears (LP: #1417967)
  * DesktopStage - fix focus switch when user taps on window (LP:
#1431325)
  * Fix warnings when launching tutorial
  * Make MouseTouchAdaptor controllable from within QML
  * Make tst_Shell absorb tst_TabletShell

  [ Leo Arias ]
  * Changed the autopilot dependencies so they do not require qt4. (LP:
#1429158)
  * Drop the support for python2 in autopilot tests. (LP: #1429163)
  * Stop using the deprecated toolkit emulators namespace in autopilot
tests. (LP: #1341681)

  [ Michael Terry ]
  * Don't close wizard  edge tutorial when the unity8-dash closes (LP:
#1425484)
  * Don't let the wizard sit indefinitely, waiting for a wizard page to
finish preparing itself. (LP: #1425737)
  * Fix two broken qmluitest files by waiting for everything to settle
before starting the tests.
  * Only call unlockAllModems once the wizard is done. (LP: #1425161)
(LP: #1425161)
  * When we are locking the user out from too many login failures,
notice when time passes even if the device is suspended. (LP:
#1396817) (LP: #1396817)

  [ Michael Zanetti ]
  * Add a mouse area to the indicators panel so we can open them by
clicking. (LP: #1417650)
  * fix launcher not reacting to first click when revealed by mouse
hover, add tests
  * performance improvements (LP: #1430233, #1425087)

  [ Michał Sawicz ]
  * Remove the activity indicator from tests
  * Use targets instead of custom ld arguments for linking

  [ Mirco Müller ]
  * Updated the visuals of the SwipeToAct-widget for incoming-call snap-
decision notifications according to new design-spec.
  * Updated the visuals of the SwipeToAct-widget for incoming-call snap-
decision notifications according to new design-spec.
 -- CI Train Bot ci-train-...@canonical.com   Wed, 18 Mar 2015 10:19:06 +

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

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

Title:
  Tablet: Dash flashes if double tapping outside open indicators

Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  How to reproduce:
   * Be on tablet
   * Be in Dash with no app open
   * Open indicators
   * Double press very fast outside the indicators (over the greyed-out area)
   * See how the dash flashes to black for a split second

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

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


[Touch-packages] [Bug 1431497] Re: Add translator comments where applicable

2015-03-19 Thread Launchpad Bug Tracker
This bug was fixed in the package unity8 - 8.02+15.04.20150318-0ubuntu1

---
unity8 (8.02+15.04.20150318-0ubuntu1) vivid; urgency=medium

  [ Albert Astals Cid ]
  * Add some context to tr calls (LP: #1431497)
  * Require binaries and .pc files we call from code
  * Test: More stubborn flick to the end

  [ Andrea Cimitan ]
  * Refactor PreviewOverlay to fix weird zoom out/in animations when
previewing images from the Previews

  [ CI Train Bot ]
  * Resync trunk.

  [ Charles Kerr ]
  * Re-enable a rotation lock test now that the bug that broke that test
has been fixed. (LP: #1410915)

  [ Daniel d'Andrada ]
  * Darkened area behind indicators menu should eat input until it fully
disappears (LP: #1417967)
  * DesktopStage - fix focus switch when user taps on window (LP:
#1431325)
  * Fix warnings when launching tutorial
  * Make MouseTouchAdaptor controllable from within QML
  * Make tst_Shell absorb tst_TabletShell

  [ Leo Arias ]
  * Changed the autopilot dependencies so they do not require qt4. (LP:
#1429158)
  * Drop the support for python2 in autopilot tests. (LP: #1429163)
  * Stop using the deprecated toolkit emulators namespace in autopilot
tests. (LP: #1341681)

  [ Michael Terry ]
  * Don't close wizard  edge tutorial when the unity8-dash closes (LP:
#1425484)
  * Don't let the wizard sit indefinitely, waiting for a wizard page to
finish preparing itself. (LP: #1425737)
  * Fix two broken qmluitest files by waiting for everything to settle
before starting the tests.
  * Only call unlockAllModems once the wizard is done. (LP: #1425161)
(LP: #1425161)
  * When we are locking the user out from too many login failures,
notice when time passes even if the device is suspended. (LP:
#1396817) (LP: #1396817)

  [ Michael Zanetti ]
  * Add a mouse area to the indicators panel so we can open them by
clicking. (LP: #1417650)
  * fix launcher not reacting to first click when revealed by mouse
hover, add tests
  * performance improvements (LP: #1430233, #1425087)

  [ Michał Sawicz ]
  * Remove the activity indicator from tests
  * Use targets instead of custom ld arguments for linking

  [ Mirco Müller ]
  * Updated the visuals of the SwipeToAct-widget for incoming-call snap-
decision notifications according to new design-spec.
  * Updated the visuals of the SwipeToAct-widget for incoming-call snap-
decision notifications according to new design-spec.
 -- CI Train Bot ci-train-...@canonical.com   Wed, 18 Mar 2015 10:19:06 +

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

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

Title:
  Add translator comments where applicable

Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Could you add translator comments to the two following strings?
  Without context, translators can't know if they are verbs or nouns,
  resulting in possible translation errors.

  Lock
  qml/Components/Dialogs.qml:90 
  https://translations.launchpad.net/unity8/trunk/+pots/unity8/gd/10/+translate

  Shutdown
   qml/Components/Dialogs.qml:127 
  https://translations.launchpad.net/unity8/trunk/+pots/unity8/gd/16/+translate

  Thanks!

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

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


[Touch-packages] [Bug 1430233] Re: Launching/stopping an unpinned app has a 2s delay

2015-03-19 Thread Launchpad Bug Tracker
This bug was fixed in the package unity8 - 8.02+15.04.20150318-0ubuntu1

---
unity8 (8.02+15.04.20150318-0ubuntu1) vivid; urgency=medium

  [ Albert Astals Cid ]
  * Add some context to tr calls (LP: #1431497)
  * Require binaries and .pc files we call from code
  * Test: More stubborn flick to the end

  [ Andrea Cimitan ]
  * Refactor PreviewOverlay to fix weird zoom out/in animations when
previewing images from the Previews

  [ CI Train Bot ]
  * Resync trunk.

  [ Charles Kerr ]
  * Re-enable a rotation lock test now that the bug that broke that test
has been fixed. (LP: #1410915)

  [ Daniel d'Andrada ]
  * Darkened area behind indicators menu should eat input until it fully
disappears (LP: #1417967)
  * DesktopStage - fix focus switch when user taps on window (LP:
#1431325)
  * Fix warnings when launching tutorial
  * Make MouseTouchAdaptor controllable from within QML
  * Make tst_Shell absorb tst_TabletShell

  [ Leo Arias ]
  * Changed the autopilot dependencies so they do not require qt4. (LP:
#1429158)
  * Drop the support for python2 in autopilot tests. (LP: #1429163)
  * Stop using the deprecated toolkit emulators namespace in autopilot
tests. (LP: #1341681)

  [ Michael Terry ]
  * Don't close wizard  edge tutorial when the unity8-dash closes (LP:
#1425484)
  * Don't let the wizard sit indefinitely, waiting for a wizard page to
finish preparing itself. (LP: #1425737)
  * Fix two broken qmluitest files by waiting for everything to settle
before starting the tests.
  * Only call unlockAllModems once the wizard is done. (LP: #1425161)
(LP: #1425161)
  * When we are locking the user out from too many login failures,
notice when time passes even if the device is suspended. (LP:
#1396817) (LP: #1396817)

  [ Michael Zanetti ]
  * Add a mouse area to the indicators panel so we can open them by
clicking. (LP: #1417650)
  * fix launcher not reacting to first click when revealed by mouse
hover, add tests
  * performance improvements (LP: #1430233, #1425087)

  [ Michał Sawicz ]
  * Remove the activity indicator from tests
  * Use targets instead of custom ld arguments for linking

  [ Mirco Müller ]
  * Updated the visuals of the SwipeToAct-widget for incoming-call snap-
decision notifications according to new design-spec.
  * Updated the visuals of the SwipeToAct-widget for incoming-call snap-
decision notifications according to new design-spec.
 -- CI Train Bot ci-train-...@canonical.com   Wed, 18 Mar 2015 10:19:06 +

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

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

Title:
  Launching/stopping an unpinned app has a 2s delay

Status in the base for Ubuntu mobile products:
  New
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Steps:
  - start an app you have not pinned to launcher

  Expected:
  - splash screen shown immediately

  Current:
  - there's a 1-2s delay

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.02+15.04.20150302-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar 10 10:55:09 2015
  SourcePackage: unity8
  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/canonical-devices-system-image/+bug/1430233/+subscriptions

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


[Touch-packages] [Bug 1429158] Re: Autopilot tests depend on qt4

2015-03-19 Thread Launchpad Bug Tracker
This bug was fixed in the package unity8 - 8.02+15.04.20150318-0ubuntu1

---
unity8 (8.02+15.04.20150318-0ubuntu1) vivid; urgency=medium

  [ Albert Astals Cid ]
  * Add some context to tr calls (LP: #1431497)
  * Require binaries and .pc files we call from code
  * Test: More stubborn flick to the end

  [ Andrea Cimitan ]
  * Refactor PreviewOverlay to fix weird zoom out/in animations when
previewing images from the Previews

  [ CI Train Bot ]
  * Resync trunk.

  [ Charles Kerr ]
  * Re-enable a rotation lock test now that the bug that broke that test
has been fixed. (LP: #1410915)

  [ Daniel d'Andrada ]
  * Darkened area behind indicators menu should eat input until it fully
disappears (LP: #1417967)
  * DesktopStage - fix focus switch when user taps on window (LP:
#1431325)
  * Fix warnings when launching tutorial
  * Make MouseTouchAdaptor controllable from within QML
  * Make tst_Shell absorb tst_TabletShell

  [ Leo Arias ]
  * Changed the autopilot dependencies so they do not require qt4. (LP:
#1429158)
  * Drop the support for python2 in autopilot tests. (LP: #1429163)
  * Stop using the deprecated toolkit emulators namespace in autopilot
tests. (LP: #1341681)

  [ Michael Terry ]
  * Don't close wizard  edge tutorial when the unity8-dash closes (LP:
#1425484)
  * Don't let the wizard sit indefinitely, waiting for a wizard page to
finish preparing itself. (LP: #1425737)
  * Fix two broken qmluitest files by waiting for everything to settle
before starting the tests.
  * Only call unlockAllModems once the wizard is done. (LP: #1425161)
(LP: #1425161)
  * When we are locking the user out from too many login failures,
notice when time passes even if the device is suspended. (LP:
#1396817) (LP: #1396817)

  [ Michael Zanetti ]
  * Add a mouse area to the indicators panel so we can open them by
clicking. (LP: #1417650)
  * fix launcher not reacting to first click when revealed by mouse
hover, add tests
  * performance improvements (LP: #1430233, #1425087)

  [ Michał Sawicz ]
  * Remove the activity indicator from tests
  * Use targets instead of custom ld arguments for linking

  [ Mirco Müller ]
  * Updated the visuals of the SwipeToAct-widget for incoming-call snap-
decision notifications according to new design-spec.
  * Updated the visuals of the SwipeToAct-widget for incoming-call snap-
decision notifications according to new design-spec.
 -- CI Train Bot ci-train-...@canonical.com   Wed, 18 Mar 2015 10:19:06 +

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

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

Title:
  Autopilot tests depend on qt4

Status in address-book-app package in Ubuntu:
  New
Status in camera-app package in Ubuntu:
  New
Status in click-update-manager package in Ubuntu:
  New
Status in cordova-ubuntu package in Ubuntu:
  New
Status in gallery-app package in Ubuntu:
  New
Status in indicator-network package in Ubuntu:
  New
Status in mediaplayer-app package in Ubuntu:
  New
Status in notes-app package in Ubuntu:
  New
Status in ubuntu-html5-theme package in Ubuntu:
  New
Status in ubuntu-keyboard package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  New
Status in ubuntuone-credentials package in Ubuntu:
  Fix Released
Status in unity-scope-click package in Ubuntu:
  Fix Released
Status in unity-webapps-qml package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  When installing the autopilot tests, they bring qt4 dependencies that
  are unnecessary.

  The package with the autopilot tests depends on libautopilot-qt, which
  installs both autopilot-qt4 and autopilot-qt5.

  We can remove that dependency and add autopilot-qt5 and qttestability-
  autopilot instead.

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

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


[Touch-packages] [Bug 1429163] Re: Autopilot tests are compatible with py2

2015-03-19 Thread Launchpad Bug Tracker
This bug was fixed in the package unity8 - 8.02+15.04.20150318-0ubuntu1

---
unity8 (8.02+15.04.20150318-0ubuntu1) vivid; urgency=medium

  [ Albert Astals Cid ]
  * Add some context to tr calls (LP: #1431497)
  * Require binaries and .pc files we call from code
  * Test: More stubborn flick to the end

  [ Andrea Cimitan ]
  * Refactor PreviewOverlay to fix weird zoom out/in animations when
previewing images from the Previews

  [ CI Train Bot ]
  * Resync trunk.

  [ Charles Kerr ]
  * Re-enable a rotation lock test now that the bug that broke that test
has been fixed. (LP: #1410915)

  [ Daniel d'Andrada ]
  * Darkened area behind indicators menu should eat input until it fully
disappears (LP: #1417967)
  * DesktopStage - fix focus switch when user taps on window (LP:
#1431325)
  * Fix warnings when launching tutorial
  * Make MouseTouchAdaptor controllable from within QML
  * Make tst_Shell absorb tst_TabletShell

  [ Leo Arias ]
  * Changed the autopilot dependencies so they do not require qt4. (LP:
#1429158)
  * Drop the support for python2 in autopilot tests. (LP: #1429163)
  * Stop using the deprecated toolkit emulators namespace in autopilot
tests. (LP: #1341681)

  [ Michael Terry ]
  * Don't close wizard  edge tutorial when the unity8-dash closes (LP:
#1425484)
  * Don't let the wizard sit indefinitely, waiting for a wizard page to
finish preparing itself. (LP: #1425737)
  * Fix two broken qmluitest files by waiting for everything to settle
before starting the tests.
  * Only call unlockAllModems once the wizard is done. (LP: #1425161)
(LP: #1425161)
  * When we are locking the user out from too many login failures,
notice when time passes even if the device is suspended. (LP:
#1396817) (LP: #1396817)

  [ Michael Zanetti ]
  * Add a mouse area to the indicators panel so we can open them by
clicking. (LP: #1417650)
  * fix launcher not reacting to first click when revealed by mouse
hover, add tests
  * performance improvements (LP: #1430233, #1425087)

  [ Michał Sawicz ]
  * Remove the activity indicator from tests
  * Use targets instead of custom ld arguments for linking

  [ Mirco Müller ]
  * Updated the visuals of the SwipeToAct-widget for incoming-call snap-
decision notifications according to new design-spec.
  * Updated the visuals of the SwipeToAct-widget for incoming-call snap-
decision notifications according to new design-spec.
 -- CI Train Bot ci-train-...@canonical.com   Wed, 18 Mar 2015 10:19:06 +

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

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

Title:
  Autopilot tests are compatible with py2

Status in ubuntu-ui-toolkit package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  The autopilot suite of tests and helpers in the toolkit is compatible
  with py2.

  We should drop the py2 support to simplify the code and to avoid all
  the py2 requirements that get installed when we want to run any test.

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

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


[Touch-packages] [Bug 1425737] Re: Wizard can potentially wait forever on a buggy page

2015-03-19 Thread Launchpad Bug Tracker
This bug was fixed in the package unity8 - 8.02+15.04.20150318-0ubuntu1

---
unity8 (8.02+15.04.20150318-0ubuntu1) vivid; urgency=medium

  [ Albert Astals Cid ]
  * Add some context to tr calls (LP: #1431497)
  * Require binaries and .pc files we call from code
  * Test: More stubborn flick to the end

  [ Andrea Cimitan ]
  * Refactor PreviewOverlay to fix weird zoom out/in animations when
previewing images from the Previews

  [ CI Train Bot ]
  * Resync trunk.

  [ Charles Kerr ]
  * Re-enable a rotation lock test now that the bug that broke that test
has been fixed. (LP: #1410915)

  [ Daniel d'Andrada ]
  * Darkened area behind indicators menu should eat input until it fully
disappears (LP: #1417967)
  * DesktopStage - fix focus switch when user taps on window (LP:
#1431325)
  * Fix warnings when launching tutorial
  * Make MouseTouchAdaptor controllable from within QML
  * Make tst_Shell absorb tst_TabletShell

  [ Leo Arias ]
  * Changed the autopilot dependencies so they do not require qt4. (LP:
#1429158)
  * Drop the support for python2 in autopilot tests. (LP: #1429163)
  * Stop using the deprecated toolkit emulators namespace in autopilot
tests. (LP: #1341681)

  [ Michael Terry ]
  * Don't close wizard  edge tutorial when the unity8-dash closes (LP:
#1425484)
  * Don't let the wizard sit indefinitely, waiting for a wizard page to
finish preparing itself. (LP: #1425737)
  * Fix two broken qmluitest files by waiting for everything to settle
before starting the tests.
  * Only call unlockAllModems once the wizard is done. (LP: #1425161)
(LP: #1425161)
  * When we are locking the user out from too many login failures,
notice when time passes even if the device is suspended. (LP:
#1396817) (LP: #1396817)

  [ Michael Zanetti ]
  * Add a mouse area to the indicators panel so we can open them by
clicking. (LP: #1417650)
  * fix launcher not reacting to first click when revealed by mouse
hover, add tests
  * performance improvements (LP: #1430233, #1425087)

  [ Michał Sawicz ]
  * Remove the activity indicator from tests
  * Use targets instead of custom ld arguments for linking

  [ Mirco Müller ]
  * Updated the visuals of the SwipeToAct-widget for incoming-call snap-
decision notifications according to new design-spec.
  * Updated the visuals of the SwipeToAct-widget for incoming-call snap-
decision notifications according to new design-spec.
 -- CI Train Bot ci-train-...@canonical.com   Wed, 18 Mar 2015 10:19:06 +

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

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

Title:
  Wizard can potentially wait forever on a buggy page

Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  If a wizard page never reports that it's ready to answer the question
  should I skip this page?, the wizard will wait forever until it gets
  the answer.  Meanwhile, the user is presented with an empty page.

  We experienced this in vivid with ofono bug 1419675.  libqofono
  wouldn't report that SIM2 was done initializing.  So we'd just keep
  waiting.

  To reduce the severity of future similar bugs, the wizard should have
  a sensible timeout.  So at least the user can continue.

  == Original bug ==

  After selecting a language, sometimes I'm left with a blank page.  I
  never see the next screen, which lets me pick my password.

  When this happened, I was running krillin, on vivid image 122.  I had
  a SIM in slot 2, but none in slot 1.  I've NOT been able to reproduce
  with a SIM in slot 1 instead of slot 2, which seems relevant.

  After reproducing many times, it will sometimes stop happening.  But
  after an image flash, it is rather reliable for a while.

  I've looked into this a bit on the wizard side.  It turns out that
  libqofono is never replying that the second SIM slot is ready which
  means it has finished initializing it.

  Now, the wizard probably should timeout waiting for that to be true.
  But libqofono should also provide that info.

  current build number: 122
  device name: krillin
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-02-25 21:42:40
  version version: 122
  version ubuntu: 20150225
  version device: 20150210-95b6a9f
  version custom: 20150225

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

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


[Touch-packages] [Bug 1431325] Re: It takes two taps to switch focus between windows

2015-03-19 Thread Launchpad Bug Tracker
This bug was fixed in the package unity8 - 8.02+15.04.20150318-0ubuntu1

---
unity8 (8.02+15.04.20150318-0ubuntu1) vivid; urgency=medium

  [ Albert Astals Cid ]
  * Add some context to tr calls (LP: #1431497)
  * Require binaries and .pc files we call from code
  * Test: More stubborn flick to the end

  [ Andrea Cimitan ]
  * Refactor PreviewOverlay to fix weird zoom out/in animations when
previewing images from the Previews

  [ CI Train Bot ]
  * Resync trunk.

  [ Charles Kerr ]
  * Re-enable a rotation lock test now that the bug that broke that test
has been fixed. (LP: #1410915)

  [ Daniel d'Andrada ]
  * Darkened area behind indicators menu should eat input until it fully
disappears (LP: #1417967)
  * DesktopStage - fix focus switch when user taps on window (LP:
#1431325)
  * Fix warnings when launching tutorial
  * Make MouseTouchAdaptor controllable from within QML
  * Make tst_Shell absorb tst_TabletShell

  [ Leo Arias ]
  * Changed the autopilot dependencies so they do not require qt4. (LP:
#1429158)
  * Drop the support for python2 in autopilot tests. (LP: #1429163)
  * Stop using the deprecated toolkit emulators namespace in autopilot
tests. (LP: #1341681)

  [ Michael Terry ]
  * Don't close wizard  edge tutorial when the unity8-dash closes (LP:
#1425484)
  * Don't let the wizard sit indefinitely, waiting for a wizard page to
finish preparing itself. (LP: #1425737)
  * Fix two broken qmluitest files by waiting for everything to settle
before starting the tests.
  * Only call unlockAllModems once the wizard is done. (LP: #1425161)
(LP: #1425161)
  * When we are locking the user out from too many login failures,
notice when time passes even if the device is suspended. (LP:
#1396817) (LP: #1396817)

  [ Michael Zanetti ]
  * Add a mouse area to the indicators panel so we can open them by
clicking. (LP: #1417650)
  * fix launcher not reacting to first click when revealed by mouse
hover, add tests
  * performance improvements (LP: #1430233, #1425087)

  [ Michał Sawicz ]
  * Remove the activity indicator from tests
  * Use targets instead of custom ld arguments for linking

  [ Mirco Müller ]
  * Updated the visuals of the SwipeToAct-widget for incoming-call snap-
decision notifications according to new design-spec.
  * Updated the visuals of the SwipeToAct-widget for incoming-call snap-
decision notifications according to new design-spec.
 -- CI Train Bot ci-train-...@canonical.com   Wed, 18 Mar 2015 10:19:06 +

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

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

Title:
  It takes two taps to switch focus between windows

Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Preconditions:
   - Be in the desktop mode/stage
   - Have to apps, side-by-side, one of the focused

  Steps:
   - Tap the unfocused one

  Expected outcome:
   - The unfocused one gets active focus

  Actucal outcome:
   - All that is accomplished is removing active focus from the old one, so no 
window have active focus. It takes a second tap to finally give active focus to 
the new one

  Comments:
  If you press-and-drag the new window instead of tapping it, you're able to 
move it around as if you were dragging it from its tittle bar

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

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


[Touch-packages] [Bug 1427654] Re: FFE: switch system init to systemd [not touch] in 15.04

2015-03-19 Thread Didier Roche
As stated on the mailing list few months ago
(https://lists.ubuntu.com/archives/ubuntu-devel-
discuss/2014-December/015154.html), Ubuntu never offered a choice of
init system, and won't start doing that. systemd is mandatory to be the
supported ubuntu path. That's the reason why ubuntu-standard won't
depend on systemd|upstart.

Note that for some kernel reasons, the Touch image is still using
upstart, but that will change in the future.

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

Title:
  FFE: switch system init to systemd [not touch] in 15.04

Status in init-system-helpers package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in init-system-helpers source package in Vivid:
  Fix Released
Status in ubuntu-meta source package in Vivid:
  Fix Released

Bug description:
  As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411
  -systemd-migration we aimed for switching the system (not session)
  init from upstart to systemd this cycle. As this was by and large a
  1.2 man show, this took a little longer. One of the remaining blockers
  for switching the default was to fix NFS (bug 1312976) which is now
  ready to be uploaded. There is also juju (bug 1409639, landed upstream
  now) and maas (bug 1423613, scheduled), but for those we can work
  around missing systemd support by installing upstart on instances.

  We are a few days past feature freeze now, bug Steve and I discussed
  last week, and we still want to aim for switching the default in
  vivid. To be clear, this will affect Ubuntu desktop/server/cloud and
  the flavours like Kubuntu, but *NOT* ubuntu-touch. Migration to
  systemd is blocked on touch (too old kernels, some unported jobs), and
  was not scheduled for vivid. For that we need to ensure to keep
  upstart on Touch (there is a work item on the spec).

  I know from at least Kubuntu and Ubuntu GNOME that they are pushing
  for switching to systemd. We should get an ack from the others
  (Lubuntu/Xubuntu/MATE) before doing the switch; but quite a lot of
  vivid users are running systemd already, and I believe we shook out
  the worst bugs now.

  So if/once the release team generally agrees, these are the things
  which need to  happen before switching:

    * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) - DONE
    * Land NFS (bug 1312976) - DONE
    * Ensure Touch keeps upstart (bug 1428026) - DONE

  Operationally, the switch is merely to change s/upstart/systemd-sysv/
  in the seeds, i. e. flip the dependency in ubuntu-minimal. I did that
  in https://launchpad.net/~pitti/+archive/ubuntu/systemd, fixed
  ureadahead, and verified that upgrades from trusty and utopic cleanly
  upgrade to vivid+PPA with removing upstart and installing systemd-
  sysv.

  Around that time I will send a mail to ubuntu-devel-announce@ to warn
  about the impending switch, and give some pointers how to boot with
  upstart (from grub menu or reinstalling upstart), how to debug
  boot/shutdown issues, etc.

  Contingency plan: This will trigger wider testing, and most certainly
  uncover more integration issues. I'll try to keep up with them, but if
  we get to a point where we find that there are too many/too serious
  regressions, we can flip the seed back to upstart and get back to the
  situation today.

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

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


[Touch-packages] [Bug 1430817] Re: Systemd packages upgrade makes screen replaced by plymouth

2015-03-19 Thread grabaldam
*** This bug is a duplicate of bug 1431200 ***
https://bugs.launchpad.net/bugs/1431200

Problem happened again yesterday, mostly likely due to
systemd_219-4ubuntu6 update. Tip on comment #6 fixed it. Second time
happening in 7 days or so.

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

Title:
  Systemd packages upgrade makes screen replaced by plymouth

Status in sddm package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Two times already during systemd packages upgrade my screen has been
  replaced by plymouth. I'm not sure exactly what caused this problem
  but here is packages list from last upgrade when this happend:

  $ sudo apt full-upgrade
  Czytanie list pakietów... Gotowe
  Budowanie drzewa zależności   
  Odczyt informacji o stanie... Gotowe
  Obliczanie aktualizacji...Gotowe
  Następujące pakiety zostaną zaktualizowane:
libgudev-1.0-0 libpam-systemd libsystemd0 libsystemd0:i386 libudev1 
libudev1:i386 qml-module-qtquick-controls qml-module-qtquick-dialogs 
qml-module-qtquick-layouts
qml-module-qtquick-privatewidgets systemd systemd-sysv udev
  13 aktualizowanych, 0 nowo instalowanych, 0 usuwanych i 0 nieaktualizowanych.
  Konieczne pobranie 5138 kB archiwów.
  Po tej operacji zostanie zwolnione 27,6 kB miejsca na dysku.
  Kontynuować? [T/n] T
  Pobieranie:1 http://archive.ubuntu.com/ubuntu/ vivid/main libudev1 amd64 
219-4ubuntu5 [40,2 kB]
  Pobieranie:2 http://archive.ubuntu.com/ubuntu/ vivid/main libudev1 i386 
219-4ubuntu5 [43,7 kB]
  Pobieranie:3 http://archive.ubuntu.com/ubuntu/ vivid/main udev amd64 
219-4ubuntu5 [924 kB]
  Pobieranie:4 http://archive.ubuntu.com/ubuntu/ vivid/main systemd-sysv amd64 
219-4ubuntu5 [8710 B]
  Pobieranie:5 http://archive.ubuntu.com/ubuntu/ vivid/main libpam-systemd 
amd64 219-4ubuntu5 [108 kB]
  Pobieranie:6 http://archive.ubuntu.com/ubuntu/ vivid/main systemd amd64 
219-4ubuntu5 [3345 kB]
  Pobieranie:7 http://archive.ubuntu.com/ubuntu/ vivid/main libsystemd0 i386 
219-4ubuntu5 [80,9 kB]
  Pobieranie:8 http://archive.ubuntu.com/ubuntu/ vivid/main libsystemd0 amd64 
219-4ubuntu5 [73,1 kB]
  Pobieranie:9 http://archive.ubuntu.com/ubuntu/ vivid/main libgudev-1.0-0 
amd64 1:219-4ubuntu5 [14,4 kB]
  Pobieranie:10 http://archive.ubuntu.com/ubuntu/ vivid/universe 
qml-module-qtquick-controls amd64 5.4.0-1ubuntu2 [350 kB]
  Pobieranie:11 http://archive.ubuntu.com/ubuntu/ vivid/universe 
qml-module-qtquick-layouts amd64 5.4.0-1ubuntu2 [28,6 kB]
  Pobieranie:12 http://archive.ubuntu.com/ubuntu/ vivid/main 
qml-module-qtquick-privatewidgets amd64 5.4.0-1ubuntu2 [36,5 kB]
  Pobieranie:13 http://archive.ubuntu.com/ubuntu/ vivid/main 
qml-module-qtquick-dialogs amd64 5.4.0-1ubuntu2 [85,3 kB]
  Pobrano 5138 kB w 1s (2720 kB/s)  
  (Odczytywanie bazy danych ... 182170 plików i katalogów obecnie 
zainstalowanych.)
  Przygotowywanie do rozpakowania pakietu .../libudev1_219-4ubuntu5_i386.deb ...
  Dekonfigurowanie pakietu libudev1:amd64 (219-4ubuntu4) ...
  Rozpakowywanie pakietu libudev1:i386 (219-4ubuntu5) nad (219-4ubuntu4) ...
  Przygotowywanie do rozpakowania pakietu .../libudev1_219-4ubuntu5_amd64.deb 
...
  Rozpakowywanie pakietu libudev1:amd64 (219-4ubuntu5) nad (219-4ubuntu4) ...
  Konfigurowanie pakietu libudev1:amd64 (219-4ubuntu5) ...
  Konfigurowanie pakietu libudev1:i386 (219-4ubuntu5) ...
  Przetwarzanie wyzwalaczy pakietu libc-bin (2.19-15ubuntu2)...
  (Odczytywanie bazy danych ... 182170 plików i katalogów obecnie 
zainstalowanych.)
  Przygotowywanie do rozpakowania pakietu .../udev_219-4ubuntu5_amd64.deb ...
  Rozpakowywanie pakietu udev (219-4ubuntu5) nad (219-4ubuntu4) ...
  Przygotowywanie do rozpakowania pakietu 
.../systemd-sysv_219-4ubuntu5_amd64.deb ...
  Rozpakowywanie pakietu systemd-sysv (219-4ubuntu5) nad (219-4ubuntu4) ...
  Przygotowywanie do rozpakowania pakietu 
.../libpam-systemd_219-4ubuntu5_amd64.deb ...
  Rozpakowywanie pakietu libpam-systemd:amd64 (219-4ubuntu5) nad (219-4ubuntu4) 
...
  Przygotowywanie do rozpakowania pakietu .../systemd_219-4ubuntu5_amd64.deb ...
  Rozpakowywanie pakietu systemd (219-4ubuntu5) nad (219-4ubuntu4) ...
  Przygotowywanie do rozpakowania pakietu 
.../libsystemd0_219-4ubuntu5_amd64.deb ...
  Dekonfigurowanie pakietu libsystemd0:i386 (219-4ubuntu4) ...
  Rozpakowywanie pakietu libsystemd0:amd64 (219-4ubuntu5) nad (219-4ubuntu4) ...
  Przygotowywanie do rozpakowania pakietu .../libsystemd0_219-4ubuntu5_i386.deb 
...
  Rozpakowywanie pakietu libsystemd0:i386 (219-4ubuntu5) nad (219-4ubuntu4) ...
  Przygotowywanie do rozpakowania pakietu 
.../libgudev-1.0-0_1%3a219-4ubuntu5_amd64.deb ...
  Rozpakowywanie pakietu libgudev-1.0-0:amd64 (1:219-4ubuntu5) nad 
(1:219-4ubuntu4) ...
  Przygotowywanie do rozpakowania pakietu 
.../qml-module-qtquick-controls_5.4.0-1ubuntu2_amd64.deb ...
  Rozpakowywanie pakietu 

[Touch-packages] [Bug 1409209] Re: GRUB shows Ubuntu rather than flavor name

2015-03-19 Thread Ubuntu QA Website
This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1409209

** Tags added: iso-testing

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

Title:
  GRUB shows Ubuntu rather than flavor name

Status in lsb package in Ubuntu:
  Opinion

Bug description:
  I installed Lubuntu 15.04 Vervet (Live image 2015-01-09) as a Manual
  installation (choosing Something else...) to install the test
  Lubuntu alongside a machine that already has Ubuntu 14.04 LTS and
  Windows 7.

  After installation, Lubuntu was mistakenly listed as Ubuntu in the
  GRUB menu. The existing Ubuntu installation, which had formerly been
  labeled as Ubuntu was now (accurately) labeled as Ubuntu 14.04.

  To reproduce:

  Install Lubuntu alongside other existing operating systems using the
  Something else... option and configuring your partitions in the
  ubiquity installer.

  Expected result:

  Grub lists your new installation as Lubuntu and the other operating
  systems as their correct names.

  Actual result:

  Grub lists my new lubuntu installation as Ubuntu (only) and the
  other operating systems correctly (for me, Ubuntu 14.04.1 LTS and
  Windows 7).

  Hardware profile: https://gist.github.com/e4e4d9d3e41ccf5c27c7

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

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


[Touch-packages] [Bug 1431713] Re: After reboot root partition password prompt is displayed on laptop screen even when connected to external display

2015-03-19 Thread Timo Harmonen
** Package changed: systemd (Ubuntu) = linux (Ubuntu)

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

Title:
  After reboot root partition password prompt is displayed on laptop
  screen even when connected to external display

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Lenovo t440s with encrypted root partition, connected to Lenovo
  docking station and attached to DELL monitor. Restart the system
  laptop lid closed.

  Shutdown and restart: Boot time screen and encrypted partition
  password prompt are correctly shown on monitor.

  Reboot: Boot time screen and encrypted partition password prompt are
  shown on laptop screen, not on monitor. External display wakes up only
  when the login prompt is displayed.

  Attached shutdown.dmesg and reboot.dmesg respectively.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu5
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 13 09:36:46 2015
  InstallationDate: Installed on 2015-03-07 (5 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Alpha amd64 (20150304)
  MachineType: LENOVO 20AQ007SMS
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-9-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/10/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET71WW (2.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQ007SMS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 PRO
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET71WW(2.21):bd02/10/2014:svnLENOVO:pn20AQ007SMS:pvrThinkPadT440s:rvnLENOVO:rn20AQ007SMS:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20AQ007SMS
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1066404] Re: wireless connection drops

2015-03-19 Thread Christos
I have the same symptoms after an upgrade to version 14.04

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

Title:
  wireless connection drops

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 12.10 (fully updated) and the wireless connection
  keeps dropping.  It appears to be connected in Network Manager but I'm
  unable to reach any web pages or the admin page of my router.

  Clicking on the network manager icon and selecting my network re-
  establishes the connection which is fine for about half an hour then
  it drops again.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: network-manager 0.9.6.0-0ubuntu7
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  Date: Sat Oct 13 23:22:07 2012
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 
(20120302)
  IpRoute:
   default via 192.168.1.254 dev wlan0  proto static
   169.254.0.0/16 dev wlan0  scope link  metric 1000
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.65  metric 
9
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to quantal on 2012-10-12 (1 days ago)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH
   Wired connection 10e7ba644-1689-4f76-9e6c-89e9e8d12f9b   
802-3-ethernet1350158233   Sat 13 Oct 2012 20:57:13 BST   yes   
no /org/freedesktop/NetworkManager/Settings/1
   David and Emma's Home Network 9c41658a-d48f-48c0-87d3-bcbcbee8d9b8   
802-11-wireless   1350166935   Sat 13 Oct 2012 23:22:15 BST   yes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN
   running 0.9.6.0connected   enabled   enabled 
enabledenabled disabled

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

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


[Touch-packages] [Bug 1434006] Re: Information leak

2015-03-19 Thread Seth Arnold
You can configure this with /etc/pam.d/sshd -- simply remove the
pam_motd lines from your PAM sshd configuration and this information
will no longer be shown when users successfully authenticate. (Neither
sshd nor pam_motd.so care if your users are using bash or false or
nologin for their shell; they successfully authenticated, which is all
the pam_motd.so cares about.)

Thanks

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

Title:
  Information leak

Status in openssh package in Ubuntu:
  Invalid

Bug description:
  I have configured ssh server. I have added user with nologin shell,
  because he's use sftp client to transfer files, not to login to shell.
  But if that user try to login to shell server returns information
  about server:

  $ ssh u...@someserver.org
  user@someserver's password:
  Welcome to Ubuntu 14.04.2 LTS (GNU/Linux 3.13.0-45-generic x86_64)

   * Documentation:  https://help.ubuntu.com/

System information as of Thu Mar 19 11:16:13 CET 2015

System load:0.0 Processes:   131
Usage of /home: 52.4% of 295.16GB   Users logged in: 1
Memory usage:   11% IP address for eth0: xxx.x.xxx.xxx
Swap usage: 1%  IP address for eth1: xx.xx.xxx.xxx

Graph this data and manage this system at:
  https://landscape.canonical.com/

  10 packages can be updated.
  10 updates are security updates.

  Last login: Thu Mar 19 11:16:13 2015 from xx.xxx.xx.xx
  This account is currently not available.
  Connection to someserver.org closed.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: openssh-server 1:6.6p1-8
  ProcVersionSignature: Ubuntu 3.16.0-26.35-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-26-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 19 11:18:02 2015
  InstallationDate: Installed on 2014-04-19 (334 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
  SourcePackage: openssh
  UpgradeStatus: Upgraded to utopic on 2014-11-06 (133 days ago)
  upstart.ssh.override: manual

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

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


[Touch-packages] [Bug 1003950] Re: launcher does not show minimized update manager while clicked

2015-03-19 Thread Clay Spence
Here's another symptom, though it may well be unrelated. This bug
affects my work computer, on which I have ubuntu 14.04 LTS, 64-bit. On
that computer, when I use the workaround, i.e., quit software updater
and start it, a window appears for it and I can use it to update. But
the window can't be resized. The mouse pointer doesn't even change when
I pass it over the window's border.

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

Title:
  launcher does not show minimized update manager while clicked

Status in Compiz:
  New
Status in Accelerated Xorg driver for nVidia cards:
  New
Status in Unity:
  Fix Released
Status in Unity 5.0 series:
  Fix Released
Status in Unity 6.0 series:
  Fix Released
Status in binary-driver-fglrx package in Ubuntu:
  New
Status in intel-linux-graphics-installer package in Ubuntu:
  New
Status in unity package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  New
Status in binary-driver-fglrx source package in Precise:
  New
Status in intel-linux-graphics-installer source package in Precise:
  New
Status in unity source package in Precise:
  Fix Released
Status in update-manager source package in Precise:
  Confirmed
Status in xserver-xorg-video-nouveau source package in Precise:
  New
Status in binary-driver-fglrx source package in Quantal:
  Invalid
Status in intel-linux-graphics-installer source package in Quantal:
  Invalid
Status in unity source package in Quantal:
  Fix Released
Status in update-manager source package in Quantal:
  Won't Fix
Status in xserver-xorg-video-nouveau source package in Quantal:
  Invalid

Bug description:
  Found an easy way to reproduce it during brussels sprint:
  1. start deja-dup or update-manager
  2. kill -9 compiz; metacity
  3. compiz --replace

  
  ===

  Update manager is showing up in the dock but I can click on the icon
  all day and nothing happens. Similarly if I do Super-S or Super-W it
  doesn't show up anywhere.

  Even if I alt-tab to the application nothing shows up. This happens
  only when update manager runs on its own. If I kill it and then launch
  it myself it comes to the foreground just fine.

  I'm not 100% sure whether this is a unity, compiz, or update-manager
  bug but so far my bet is on unity.

  =Original Report=
  Bug #877444 is showing again in latest updates, please re-open it. This is 
the exact same problem.

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

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


[Touch-packages] [Bug 1431654] Re: lightdm (1.2.3-0ubuntu2.6) 100%/high cpu usage

2015-03-19 Thread paz
The bug fixed for me on  Linux paz 3.2.0-79-generic-pae #115-Ubuntu SMP Thu Mar 
12 14:33:25 UTC 2015 i686 i686 i386 GNU/Linux
Thank you very much!

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

Title:
  lightdm (1.2.3-0ubuntu2.6) 100%/high cpu usage

Status in lightdm package in Ubuntu:
  Fix Committed

Bug description:
  Since updating lightdm today, one core of my CPU is always maxed out
  at 100%.  I rolled back to version 1.2.3-0ubuntu2.5 and the issue
  stopped.  I tried this with 2 different kernels: 3.2.0-77-generic and
  3.2.0-79-generic and and version 1.2.3-0ubuntu2.6 of lightdm still
  caused 100% cpu usage.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: lightdm 1.2.3-0ubuntu2.6
  ProcVersionSignature: Ubuntu 3.2.0-77.114-generic 3.2.66
  Uname: Linux 3.2.0-77-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: amd64
  Date: Thu Mar 12 20:20:12 2015
  ExecutablePath: /usr/sbin/lightdm
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MarkForUpload: True
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1228575] Re: Slider's tooltip too small sometimes

2015-03-19 Thread Michal Predotka
Wanted to report a bug about this very problem but I see it's already
reported. I'm attaching my screenshot anyway.

** Attachment added: Screenshot at 22-13-39.png
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1228575/+attachment/4350339/+files/Screenshot%20at%2022-13-39.png

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

Title:
  Slider's tooltip too small sometimes

Status in RSS Feed Reader application for Ubuntu devices:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  I tried to reimplement Slider's formatValue function this way:

  function formatValue(v) {
  if (v  maximumValue / 3)
  return i18n.tr(Small)
  else if (v  maximumValue / 3 * 2)
  return i18n.tr(Midium)
  else return i18n.tr(Large)
  }

  Result: word Medium doesn't fit in tooltip.
  Solution: use something like 
  Math.max(STANDARD_WIDTH, innerLabel.contentWidth)

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

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


[Touch-packages] [Bug 1427785] Re: Duplicate processes started after Resume of amd64 bit

2015-03-19 Thread apjjr
Ok.  I have no idea what I'm looking for.  I see messages in a lot of
the upstart log files that look like errors. See below.

How am I supposed to know what package this 'bug' belongs to?  I'm not a linux 
systems guy.  How would I figure that out?  I'd be glad to classify this better 
if I knew how.
All I know is what I said in my first remark about this.
I've been using Ubuntu since 5.04 and have never seen duplicate processes get 
started like this before.  They just keep building up until I start to see 
performance degradation.  Then I reboot and all is well until they build up 
again.
Thanks for your help.

Here's part of the output of ps fax:
7011 ?Ss 0:00  \_ bash -c dbus-launch /usr/bin/docky /dev/null -
 7012 ?Sl 0:02  \_ mono /usr/lib/docky/Docky.exe
 6715 ?S  0:00 su apjjr - -c dbus-launch /usr/bin/docky /dev/null
 7016 ?Ss 0:00  \_ bash -c dbus-launch /usr/bin/docky /dev/null -
 7017 ?Sl 0:02  \_ mono /usr/lib/docky/Docky.exe
 6872 ?S  0:00 su apjjr - -c dbus-launch /usr/bin/docky /dev/null
 7019 ?Ss 0:00  \_ bash -c dbus-launch /usr/bin/docky /dev/null -
 7021 ?Sl 0:02  \_ mono /usr/lib/docky/Docky.exe
 6910 ?S  0:00 su apjjr - -c dbus-launch /usr/bin/docky /dev/null
 7022 ?Ss 0:00  \_ bash -c dbus-launch /usr/bin/docky /dev/null -
 7026 ?Sl 0:02  \_ mono /usr/lib/docky/Docky.exe

I wonder why so many instances of Docky?

I'd appreciate any help I can get.  If I need to reinstall because
somethngs gotten screwed up, I'll do that.

Following are the upstart log files I think are indicating some error:

cups.log
cupsd failed to create /var/run/cups/cups.sock, skipping automatic printer 
configuration
cupsd failed to create /var/run/cups/cups.sock, skipping automatic printer 
configuration

gpu-manager.log
/etc/modprobe.d is not a file
/etc/modprobe.d is not a file
/etc/modprobe.d is not a file
/etc/modprobe.d is not a file
update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
/etc/modprobe.d is not a file
/etc/modprobe.d is not a file
/etc/modprobe.d is not a file
/etc/modprobe.d is not a file
update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf

kmod.log
modprobe: FATAL: Module rtc not found.
modprobe: FATAL: Module rtc not found.

network-manager.log

(NetworkManager:861): GLib-WARNING **: GError set over the top of a previous 
GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before 
it's set.
The overwriting error message was: Key file does not have group 'connectivity'

(NetworkManager:879): GLib-WARNING **: GError set over the top of a previous 
GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before 
it's set.
The overwriting error message was: Key file does not have group 'connectivity'

ureadahead.log
ureadahead:/var/lib/NetworkManager/dhclient-wlan0.conf: No such file or 
directory
ureadahead:/var/lib/NetworkManager/dhclient-wlan0.conf: No such file or 
directory

ureadahead-other.log
ureadahead:/home/apjjr/.cache/upstart/im-config.log: No such file or directory
ureadahead:/home/apjjr/.cache/upstart/update-notifier-release.log: No such file 
or directory
ureadahead:/home/apjjr/.cache/upstart/gnome-keyring-ssh.log: No such file or 
directory
ureadahead:/home/apjjr/.cache/upstart/gnome-keyring-gpg.log: No such file or 
directory
ureadahead:/home/apjjr/.cache/upstart/ssh-agent.log: No such file or directory
ureadahead:/home/apjjr/.cache/upstart/unity7.log: No such file or directory
ureadahead:/home/apjjr/.cache/upstart/indicator-bluetooth.log: No such file or 
directory
ureadahead:/home/apjjr/.cache/upstart/indicator-datetime.log: No such file or 
directory
ureadahead:/home/apjjr/.local/share/gvfs-metadata/home-00b673f2.log: No such 
file or directory
ureadahead:/var/lib/ureadahead/boot.efi.pack: No such file or directory
ureadahead:/home/apjjr/.cache/upstart/im-config.log: No such file or directory
ureadahead:/home/apjjr/.cache/upstart/update-notifier-release.log: No such file 
or directory
ureadahead:/home/apjjr/.cache/upstart/gnome-keyring-ssh.log: No such file or 
directory
ureadahead:/home/apjjr/.cache/upstart/gnome-keyring-gpg.log: No such file or 
directory
ureadahead:/home/apjjr/.cache/upstart/ssh-agent.log: No such file or directory
ureadahead:/home/apjjr/.cache/upstart/unity7.log: No such file or directory
ureadahead:/home/apjjr/.cache/upstart/window-stack-bridge.log: No such file or 
directory
ureadahead:/home/apjjr/.cache/upstart/indicator-bluetooth.log: No such file or 
directory
ureadahead:/home/apjjr/.cache/upstart/indicator-datetime.log: No such file or 
directory
ureadahead:/home/apjjr/.local/share/gvfs-metadata/home-00b673f2.log: No such 
file or directory

wait-for-state-plymouth-shutdownlightdm.log
stop: Job has already been stopped: lightdm
stop: Job has already 

[Touch-packages] [Bug 1434143] Re: boot script should run aa-profile-hook in addition to aa-clickhook

2015-03-19 Thread Jamie Strandboge
** Changed in: apparmor (Ubuntu)
 Assignee: (unassigned) = Steve Beattie (sbeattie)

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

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

Title:
  boot script should run aa-profile-hook in addition to aa-clickhook

Status in Snappy Ubuntu:
  Triaged
Status in apparmor package in Ubuntu:
  In Progress

Bug description:
  Summary says it all. aa-profile-hook does the same sort of thing as
  aa-clickhook and is used on snappy.

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

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


[Touch-packages] [Bug 1396213] Re: LVM VG is not activated during system boot

2015-03-19 Thread MegaBrutal
With the knowledge that the hang is caused by snapshots, some googling has 
brought up some duplicates:
https://bugs.launchpad.net/lvm2/+bug/360237
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/995645

It seems the issue was hanging around since 2009 or earlier.

In Trusty (or probably even earlier distros) it was possible to work
around by setting a sufficiently long rootdelay, and eventually all the
LVs in all VGs came online. But since Utopic, initrd gives up
altogether. No matter how long my rootdelay is, my 2nd VG never gets
activated after the snapshot came online in the 1st VG.

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

Title:
  LVM VG is not activated during system boot

Status in One Hundred Papercuts:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  Hi all,

  I open this report based on the linked conversation I had on the linux-lvm 
mailing list, and the Ask Ubuntu question I posted regarding this case.
  https://www.redhat.com/archives/linux-lvm/2014-November/msg00023.html
  https://www.redhat.com/archives/linux-lvm/2014-November/msg00024.html
  
http://askubuntu.com/questions/542656/lvm-vg-is-not-activated-during-system-boot

  I have 2 VGs on my system, and for some reason, only one of them gets
  activated during the initrd boot sequence, which doesn't have my root
  LV, so my boot sequence halts with an initrd prompt.

  When I get to the initrd BusyBox prompt, I can see my LVs are inactive
  with lvm lvscan – then, lvm vgchange -ay brings them online. The
  boot sequence continues as I exit the BusyBox prompt. The expected
  behaviour would be that both VGs should activate automatically.

  On LVM mailing list, I've been advised it may be a problem with Ubuntu
  initrd scripts, hence I report this problem here. (I'm not sure if I'm
  reporting it to the correct place by assigning it to linux, but I
  didn't find a package directly related to the initrd only, so I
  assumed initrd scripts are maintained by the kernel team. If you think
  it's an error, and know the correct package, please reassign!) Our
  suspicion is, initrd prematurely issues vgchange -ay before all the
  PVs come online. This makes sense.

  I already tried to set the rootdelay kernel parameter to make initrd
  wait longer for the boot LV to come up, but it didn't work. Note
  however, it worked with previous kernel versions.

  The problem came up when I upgraded to Utopic, and got kernel 
vmlinuz-3.16.0-23-generic. When I boot with the old kernel from Trusty 
(vmlinuz-3.13.0-37-generic), it works fine.
  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.16.0-23-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC1D2p', '/dev/snd/pcmC1D1c', '/dev/snd/pcmC1D0c', 
'/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/timer'] failed with exit 
code 1:
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  Card1.Amixer.info: Error: [Errno 2] No such file or directory
  Card1.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=/dev/mapper/vmhost--vg-vmhost--swap0
  InstallationDate: Installed on 2013-12-06 (354 days ago)
  InstallationMedia: Ubuntu-Server 13.10 Saucy Salamander - Release amd64 
(20131016)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: WinFast 6150M2MA
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-23-generic 
root=/dev/mapper/hostname--vg-hostname--rootfs ro rootflags=subvol=@ 
rootdelay=300
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-23-generic N/A
   linux-backports-modules-3.16.0-23-generic  N/A
   linux-firmware 1.138
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  utopic utopic
  Uname: Linux 3.16.0-23-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: Upgraded to utopic on 2014-10-28 (28 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 01/19/2008
  dmi.bios.vendor: Phoenix 

[Touch-packages] [Bug 1433382] Re: [USB-Audio - SB X-Fi Surround 5.1 Pro, playback] Static, crackling sounds using module-loopback

2015-03-19 Thread Eric Peterson
Attached is the output of lsusb -

** Attachment added: lsusb.txt
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1433382/+attachment/4350374/+files/lsusb.txt

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

Title:
  [USB-Audio - SB X-Fi Surround 5.1 Pro, playback] Static, crackling
  sounds using module-loopback

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  I recently hooked up a SB X-Fi Surrount 5.1 Pro external sound card to
  my computer. It has a Line-In port which I wanted to use for playing
  audio from another computer. I enabled the loopback module like so:

 pactl load-module module-loopback

  And although I could then hear sound from Line-In, it was distorted by
  static, crackling sounds. I took the advice I found here:

 https://wiki.ubuntu.com/Audio/PositionReporting

  Making this change to /etc/pulse/default.pa:

 load-module module-udev-detect tsched=0

  After rebooting and again loading the loopback module, the playback
  was static-free. As instructed by the above webpage, I'm filing this
  bug to track the issue and suggested solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.2.0-77.114-generic 3.2.66
  Uname: Linux 3.2.0-77-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: amd64
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xfa62 irq 95'
 Mixer name : 'Realtek ALC898'
 Components : 'HDA:10ec0899,104384d8,0013'
 Controls  : 47
 Simple ctrls  : 23
  Card1.Amixer.info:
   Card hw:1 'Pro'/'Creative Technology Ltd SB X-Fi Surround 5.1 Pro at 
usb-:00:1d.0-1.3, high '
 Mixer name : 'USB Mixer'
 Components : 'USB041e:3237'
 Controls  : 0
 Simple ctrls  : 0
  Card1.Amixer.values:
   
  Card2.Amixer.info:
   Card hw:2 'NVidia'/'HDA NVidia at 0xfa08 irq 36'
 Mixer name : 'Nvidia GPU 16 HDMI/DP'
 Components : 'HDA:10de0016,10de0101,00100100'
 Controls  : 24
 Simple ctrls  : 4
  Date: Tue Mar 17 21:02:47 2015
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Pro successful
  Symptom_Card: GF114 HDMI Audio Controller - HDA NVidia
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Underruns, dropouts, or crackling sound
  Title: [USB-Audio - SB X-Fi Surround 5.1 Pro, playback] Underruns, dropouts 
or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/10/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79 PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1104:bd04/10/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79PRO:rvrRev1.xx: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/1433382/+subscriptions

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


[Touch-packages] [Bug 1434006] Re: Information leak

2015-03-19 Thread Seth Arnold
** Information type changed from Private Security to Public Security

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

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

Title:
  Information leak

Status in openssh package in Ubuntu:
  Invalid

Bug description:
  I have configured ssh server. I have added user with nologin shell,
  because he's use sftp client to transfer files, not to login to shell.
  But if that user try to login to shell server returns information
  about server:

  $ ssh u...@someserver.org
  user@someserver's password:
  Welcome to Ubuntu 14.04.2 LTS (GNU/Linux 3.13.0-45-generic x86_64)

   * Documentation:  https://help.ubuntu.com/

System information as of Thu Mar 19 11:16:13 CET 2015

System load:0.0 Processes:   131
Usage of /home: 52.4% of 295.16GB   Users logged in: 1
Memory usage:   11% IP address for eth0: xxx.x.xxx.xxx
Swap usage: 1%  IP address for eth1: xx.xx.xxx.xxx

Graph this data and manage this system at:
  https://landscape.canonical.com/

  10 packages can be updated.
  10 updates are security updates.

  Last login: Thu Mar 19 11:16:13 2015 from xx.xxx.xx.xx
  This account is currently not available.
  Connection to someserver.org closed.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: openssh-server 1:6.6p1-8
  ProcVersionSignature: Ubuntu 3.16.0-26.35-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-26-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 19 11:18:02 2015
  InstallationDate: Installed on 2014-04-19 (334 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
  SourcePackage: openssh
  UpgradeStatus: Upgraded to utopic on 2014-11-06 (133 days ago)
  upstart.ssh.override: manual

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

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


[Touch-packages] [Bug 1432829] Re: resolv.conf not updated correctly for interfaces configured in initramfs

2015-03-19 Thread Thomas Hood
** Summary changed:

- resolvconf not updated correctly for interfaces configured in initramfs
+ resolv.conf not updated correctly for interfaces configured in initramfs

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

Title:
  resolv.conf not updated correctly for interfaces configured in
  initramfs

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  maas images utilize cloud-initramfs-dyn-netconf . The way this works is 
basically:
   * /etc/network/interfaces in image is a link to 
../../run/network/dynamic-interfaces
   * kernel command line 'ip=' convince the initramfs to bring up networking 
using 'ipconfig'
     example: ip=maas-enlist:BOOTIF
   * ipconfig writes files in /run/net-*.conf for each interface it configures.
   * cloud-initramfs-dyn-netconf module writes /run/network/dyanmic-interfaces 
based on /run/net-*.conf files that 'ipconfig' creates.

  end result is that after the move to real root,
  /etc/network/interfaces should be a symlink to /run/ that ends up
  having something like this:

   | ## This file is generated by cloud-initramfs-dyn-netconf
   | auto lo
   | iface lo inet loopback
   | manual eth0
   | iface eth0 inet dhcp
   | dns-nameservers 192.168.64.3
   | dns-search maas

  resolvconf seems not to be working as well as it should be.  In vivid
  (now using systemd), I have only the resolvconf header in the file.

   in all other supported ubuntu releases, doing the above results in 
functional resolv.conf via resolv.conf. Seen here from trusty:
   | # Dynamic resolv.conf(5) file for glibc resolver(3) generated by 
resolvconf(8)
   | # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
   | nameserver 192.168.64.3

  Related Bugs:
   *  bug 1432821: something deleting /run/network after during boot

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: resolvconf 1.69ubuntu1.1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  Date: Mon Mar 16 20:42:24 2015
  PackageArchitecture: all
  ProcEnviron:
   TERM=vt102
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: resolvconf
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 995645] Re: udevd: timeout: killing 'watershed sh -c '/sbin/lvm vgscan; /sbin/lvm vgchange -a y''

2015-03-19 Thread MegaBrutal
*** This bug is a duplicate of bug 1396213 ***
https://bugs.launchpad.net/bugs/1396213

** This bug has been marked a duplicate of bug 1396213
   LVM VG is not activated during system boot

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

Title:
  udevd: timeout: killing 'watershed sh -c '/sbin/lvm vgscan; /sbin/lvm
  vgchange -a y''

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  Boot takes a long time during which the console reports:

  
  [  100.224928] device-mapper: table: 252:40: snapshot: Snapshot cow pairing 
for exception table handover failed
  udevd[617]: timeout: killing 'watershed sh -c '/sbin/lvm vgscan; /sbin/lvm 
vgchange -a y'' [1148]

  udevd[617]: 'watershed sh -c '/sbin/lvm vgscan; /sbin/lvm vgchange -a
  y'' [1148] terminated by signal 9 (Killed)

  Then the boot stalls waiting to mount /usr and I have to use M to
  manually recover.

  When I get into the recovery shell, a read from
  /dev/rootvol_tmp/ubuntu_usr returns 0 bytes and I have to run
  vgchange -a y before I can get a read from that LV to return data.
  At that point I can drop out of the recovery shell and boot will
  continue.

  I have the following LVs on this system:

  # lvs
LV   VG  Attr   LSize   Origin  Snap%  Move Log 
Copy%  Convert
videodatavol -wn-ao 698.19g 
  
video_tmpdatavol -wi-a- 233.32g 
  
apt_archives rootvol_tmp -wi-a-   1.00g 
  
home rootvol_tmp -wi-ao   1.78g 
  
lucidrootvol_tmp -wi-a-   3.00g 
  
lucid_root   rootvol_tmp swi-a-   1.00g ubuntu_root  34.70  
  
lucid_usrrootvol_tmp swi-a-   5.00g ubuntu_usr   42.22  
  
lucid_varrootvol_tmp swi-a-   4.00g ubuntu_var   39.57  
  
myth-0.24_root   rootvol_tmp swi-a-   1.00g ubuntu_root  34.66  
  
myth-0.24_usrrootvol_tmp swi-a-   5.00g ubuntu_usr   35.68  
  
natty_root   rootvol_tmp swi-a- 500.00m ubuntu_root  49.99  
  
natty_usrrootvol_tmp swi-a-   2.49g ubuntu_usr   58.34  
  
swap rootvol_tmp -wi-ao 512.00m 
  
ubuntu_root  rootvol_tmp owi-ao 500.00m 
  
ubuntu_root-20111213 rootvol_tmp swi-a- 500.00m ubuntu_root  70.96  
  
ubuntu_root-20120209 rootvol_tmp swi-a- 500.00m ubuntu_root  70.95  
  
ubuntu_root-20120214 rootvol_tmp swi-a- 500.00m ubuntu_root  70.94  
  
ubuntu_root-20120220 rootvol_tmp swi-a- 500.00m ubuntu_root  70.93  
  
ubuntu_root-20120313 rootvol_tmp swi-a- 500.00m ubuntu_root  70.93  
  
ubuntu_root-20120319 rootvol_tmp swi-a- 500.00m ubuntu_root  70.90  
  
ubuntu_root-20120412 rootvol_tmp swi-a- 500.00m ubuntu_root  50.03  
  
ubuntu_usr   rootvol_tmp owi-ao   2.49g 
  
ubuntu_usr-20111213  rootvol_tmp swi-a-   2.49g ubuntu_usr   69.04  
  
ubuntu_usr-20120209  rootvol_tmp swi-a-   2.49g ubuntu_usr   68.64  
  
ubuntu_usr-20120214  rootvol_tmp swi-a-   2.49g ubuntu_usr   67.79  
  
ubuntu_usr-20120220  rootvol_tmp swi-a-   2.49g ubuntu_usr   67.52  
  
ubuntu_usr-20120313  rootvol_tmp swi-a-   2.49g ubuntu_usr   67.41  
  
ubuntu_usr-20120319  rootvol_tmp swi-a-   2.49g ubuntu_usr   66.21  
  
ubuntu_usr-20120412  rootvol_tmp swi-a-   2.49g ubuntu_usr   65.69  
  
ubuntu_var   rootvol_tmp owi-ao   1.99g 
  

  That's probably more than most people, but certainly not enough to
  warrant an unbootable system I should not think.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: udev 175-0ubuntu9
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic i686
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: i386
  CurrentDmesg:
   [  237.755758] NFSD: starting 90-second grace period
   [  256.877022] SysRq : Changing Loglevel
   [  256.880020] Loglevel set to 8
  CustomUdevRuleFiles: 85-alsa.rules 85-ifupdown.rules 85-mdadm.rules 
41-mythtv-permissions.rules
  Date: Sun May  6 17:02:19 2012
  MachineType: To Be Filled By O.E.M. To Be Filled By 

[Touch-packages] [Bug 360237] Re: cannot boot root on lvm2 with (largish) snapshot

2015-03-19 Thread MegaBrutal
*** This bug is a duplicate of bug 1396213 ***
https://bugs.launchpad.net/bugs/1396213

** This bug is no longer a duplicate of bug 995645
   udevd: timeout: killing 'watershed sh -c '/sbin/lvm vgscan; /sbin/lvm 
vgchange -a y''
** This bug has been marked a duplicate of bug 1396213
   LVM VG is not activated during system boot

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

Title:
  cannot boot root on lvm2 with (largish) snapshot

Status in lvm2 - Logical Volume Manager:
  Invalid
Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  When running root-on-lvm2 with the root being part of a vg that
  contains snapshotted volume(s), booting may fail if the snapshot size
  (or fill rate) grows over a certain size.

  The kernel will only wait a certain amount of time until dropping to an 
initramfs-shell reporting 'Gave up waiting for root device' as the reason. The 
harddisk drive activity indicator will still show lots of disk access for some 
more time (minutes in out case). 
  'ps | grep lvm' reveals that 'lvchange -a y' is taking a long time to 
complete.
  Waiting for the disk activity to die down, and exiting the shell will allow 
the boot to resume normally.

  Can anybody explain *why* it could take that long - each and every time?
   DETAILS
  More specificly, my volume group contained an Intrepid root partition of 20Gb 
(15Gb filled). I created a snapshot of this (18Gb) in order to 'sandbox 
upgrade' to Jaunty beta. This I did. I was kind of surprised by the volume of 
changes on the snapshot: the snapshot was 53% full after upgrade (so about 9Gb 
of changed blocks vs. Intrepid). On reboot, I found out that the system would 
not reboot itself.

  I have spent a long time around various seemingly related bugs
  (#290153, #332270) for a cause until I found out the culprit myself. I
  have not been able to find any (lvm) documentation warning to the fact
  that lvm operations might take several minutes (?!) to complete on
  snapshotted volumes.

  At the very least this warrants a CAPITAL RED warning flag in the
  docs, IMHO: using large snapshots might render a system unbootable
  (remotely) with root on lvm. Manual intervention at console/serial is
  required!

  1. [untested] it doesn't matter whether the root volume is actually a 
snapshot or origin, as long as the volume group contains said snapshot (in my 
case, intrepid was on the origin and jaunty on tje snapshot; both systems 
failed boot with the same symptoms).
  2. [untested] if root volume is in a separate vg things might work ok 
(assuming activating several volume groups can be done in parallel)
  3. [partially tested: freshly snapshotted system booted ok] I suspect nothing 
is the matter with a snapshot sized 18Gb, unless it fills up ('exception 
blocks' get used). However there is not much use in a snapshot of 18Gb if you 
are only allowed to use small parts of it.
  4. [tested] as a side note, once booted, both systems were reasonably 
performant (at least in responsiveness)
  5. [tested] other volume groups in the same server did not suffer noticeable 
performance penalties even when the problematic one performed badly
  6. [tested] the performance was back to normal (acceptable), even though my 
40Gb Home lv still featured a (largely unaltered) snapshot of 5Gb/6% (in the 
_same_ volume group). This indicates that nothing special to be wrong/corrupted 
in the vg metadata.
  7. [tested] rebooting/shutting down seemed flawed when initiated from Jaunty 
(but it seems unrelated to me: Jaunty appears to use kexec for reboot, causing 
problems with my terminal display and harddisk spin-down as well)

  -- executed from the initramfs shell:
  /sbin/lvm vgchange -a n
  /sbin/lvm vgchange -a y # takes several minutes to complete (disk light on 
continuously)
  /sbin/lvm vgchange -a n
  /sbin/lvm vgchange -a y # again, same agony (continuous period of solid 
activity)

  /sbin/lvm lvremove vg/largish_snapshot

  /sbin/lvm vgchange -a n
  /sbin/lvm vgchange -a y # only takes seconds

  Of course I made a backup of the data in the snapshot that I actually
  wanted to keep :)

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

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


[Touch-packages] [Bug 1069218] Re: users.conf doesn't match users.c

2015-03-19 Thread Robert Ancell
Still working with 1.2.3-0ubuntu2.7

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

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

Title:
  users.conf doesn't match users.c

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Released
Status in Light Display Manager 1.8 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  Fix Committed
Status in lightdm source package in Trusty:
  Fix Released

Bug description:
  [Impact]
  The default users.conf provided by LightDM mentions a section [UserAccounts]. 
It should be [UserList].

  [Test Case]
  1. Check default installed users.conf
  Expected result:
  Should have a [UserList] section with all items available but disabled.
  Observed result:
  Have a [UserAccounts] section with all items available but disabled.

  [Regression Potential]
  Very low - just changing the default configuration file which has no active 
configuration items.

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

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


[Touch-packages] [Bug 1235915] Re: indicator-keyboard-service crashed with SIGSEGV in xkl_config_rec_get_full_from_server()

2015-03-19 Thread Robert Ancell
** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  indicator-keyboard-service crashed with SIGSEGV in
  xkl_config_rec_get_full_from_server()

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in Light Display Manager 1.4 series:
  Fix Committed
Status in Light Display Manager 1.8 series:
  Fix Committed
Status in indicator-keyboard package in Ubuntu:
  Invalid
Status in lightdm package in Ubuntu:
  Fix Released
Status in indicator-keyboard source package in Precise:
  New
Status in lightdm source package in Precise:
  Fix Committed

Bug description:
  The bug report details have been generated automatically. I'm not sure if 
this bug happens with lightdm or later on.
  The System Problem Detected dialogue box appears about 15 to 20 seconds 
after I've logged in (without me running any apps), so it could be that the 
crash occurs in the lightdm log-in screen but it just takes my system a while 
to collect the bug info?

  Everything appears to work normally after the System Problem
  Detected dialogue, so whatever is crashing seems to restart
  gracefully.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: indicator-keyboard 0.0.0+13.10.20131004-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Sat Oct  5 11:15:17 2013
  ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-keyboard-service
  InstallationDate: Installed on 2013-09-28 (7 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20130925.1)
  MarkForUpload: True
  ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-keyboard-service --use-gtk 
--use-bamf
  ProcEnviron:
   SHELL=/bin/false
   XDG_RUNTIME_DIR=set
   PATH=(custom, no user)
   LANGUAGE=en_GB
   LANG=en_GB.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fa5a9482616:mov0x18(%rdx),%rax
   PC (0x7fa5a9482616) ok
   source 0x18(%rdx) (0x0018) not located in a known VMA region (needed 
readable region)!
   destination %rax ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-keyboard
  StacktraceTop:
   ?? () from /usr/lib/libxklavier.so.16
   lightdm_get_layouts () from /usr/lib/liblightdm-gobject-1.so.0
   lightdm_get_layout () from /usr/lib/liblightdm-gobject-1.so.0
   ?? ()
   ?? ()
  Title: indicator-keyboard-service crashed with SIGSEGV in 
lightdm_get_layouts()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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


[Touch-packages] [Bug 1207935] Re: lightdm crashed with SIGSEGV in quit_timeout_cb()

2015-03-19 Thread Robert Ancell
** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  lightdm crashed with SIGSEGV in quit_timeout_cb()

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  Fix Committed

Bug description:
  ..

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: lightdm 1.7.8-0ubuntu1
  Uname: Linux 3.11.0-031100rc3-generic x86_64
  ApportVersion: 2.11-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Jul 31 00:29:44 2013
  ExecutablePath: /usr/sbin/lightdm
  InstallationDate: Installed on 2011-07-23 (738 days ago)
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110426)
  LightdmConfig:
   [SeatDefaults]
   greeter-session=unity-greeter
   user-session=ubuntu
   autologin-user=
  MarkForUpload: True
  ProcCmdline: lightdm
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x40e47d:  movl   $0x0,0x20(%rax)
   PC (0x0040e47d) ok
   source $0x0 ok
   destination 0x20(%rax) (0xaaca) not located in a known VMA 
region (needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: lightdm
  StacktraceTop:
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: lightdm crashed with SIGSEGV in g_main_context_dispatch()
  UpgradeStatus: Upgraded to saucy on 2013-07-10 (19 days ago)
  UserGroups:

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

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


[Touch-packages] [Bug 1378048] Re: Make music controls work in the sound indicator

2015-03-19 Thread Jim Hodapp
Plan is to work on underlying background playlist support this next
iteration, so this will be possible to re-enable in the next few weeks
or so.

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

Title:
  Make music controls work in the sound indicator

Status in the base for Ubuntu mobile products:
  Confirmed
Status in indicator-sound package in Ubuntu:
  Invalid
Status in media-hub package in Ubuntu:
  Confirmed

Bug description:
  Steps:
  1. Play an album in the music player
  2. Pull down sound indicator
  3. Click forward button

  Observed: the music does not advance
  Expected: the music advances

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

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


[Touch-packages] [Bug 1235915] Re: indicator-keyboard-service crashed with SIGSEGV in xkl_config_rec_get_full_from_server()

2015-03-19 Thread Robert Ancell
** Tags removed: verification-done

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

Title:
  indicator-keyboard-service crashed with SIGSEGV in
  xkl_config_rec_get_full_from_server()

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in Light Display Manager 1.4 series:
  Fix Committed
Status in Light Display Manager 1.8 series:
  Fix Committed
Status in indicator-keyboard package in Ubuntu:
  Invalid
Status in lightdm package in Ubuntu:
  Fix Released
Status in indicator-keyboard source package in Precise:
  New
Status in lightdm source package in Precise:
  Fix Committed

Bug description:
  The bug report details have been generated automatically. I'm not sure if 
this bug happens with lightdm or later on.
  The System Problem Detected dialogue box appears about 15 to 20 seconds 
after I've logged in (without me running any apps), so it could be that the 
crash occurs in the lightdm log-in screen but it just takes my system a while 
to collect the bug info?

  Everything appears to work normally after the System Problem
  Detected dialogue, so whatever is crashing seems to restart
  gracefully.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: indicator-keyboard 0.0.0+13.10.20131004-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Sat Oct  5 11:15:17 2013
  ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-keyboard-service
  InstallationDate: Installed on 2013-09-28 (7 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20130925.1)
  MarkForUpload: True
  ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-keyboard-service --use-gtk 
--use-bamf
  ProcEnviron:
   SHELL=/bin/false
   XDG_RUNTIME_DIR=set
   PATH=(custom, no user)
   LANGUAGE=en_GB
   LANG=en_GB.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fa5a9482616:mov0x18(%rdx),%rax
   PC (0x7fa5a9482616) ok
   source 0x18(%rdx) (0x0018) not located in a known VMA region (needed 
readable region)!
   destination %rax ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-keyboard
  StacktraceTop:
   ?? () from /usr/lib/libxklavier.so.16
   lightdm_get_layouts () from /usr/lib/liblightdm-gobject-1.so.0
   lightdm_get_layout () from /usr/lib/liblightdm-gobject-1.so.0
   ?? ()
   ?? ()
  Title: indicator-keyboard-service crashed with SIGSEGV in 
lightdm_get_layouts()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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


[Touch-packages] [Bug 1396213] Re: LVM VG is not activated during system boot

2015-03-19 Thread MegaBrutal
Got an interesting reply from the Red Hat LVM mailing list:
https://www.redhat.com/archives/linux-lvm/2015-March/msg00022.html

Haven't tested the suggestion yet.

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

Title:
  LVM VG is not activated during system boot

Status in One Hundred Papercuts:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  Hi all,

  I open this report based on the linked conversation I had on the linux-lvm 
mailing list, and the Ask Ubuntu question I posted regarding this case.
  https://www.redhat.com/archives/linux-lvm/2014-November/msg00023.html
  https://www.redhat.com/archives/linux-lvm/2014-November/msg00024.html
  
http://askubuntu.com/questions/542656/lvm-vg-is-not-activated-during-system-boot

  I have 2 VGs on my system, and for some reason, only one of them gets
  activated during the initrd boot sequence, which doesn't have my root
  LV, so my boot sequence halts with an initrd prompt.

  When I get to the initrd BusyBox prompt, I can see my LVs are inactive
  with lvm lvscan – then, lvm vgchange -ay brings them online. The
  boot sequence continues as I exit the BusyBox prompt. The expected
  behaviour would be that both VGs should activate automatically.

  On LVM mailing list, I've been advised it may be a problem with Ubuntu
  initrd scripts, hence I report this problem here. (I'm not sure if I'm
  reporting it to the correct place by assigning it to linux, but I
  didn't find a package directly related to the initrd only, so I
  assumed initrd scripts are maintained by the kernel team. If you think
  it's an error, and know the correct package, please reassign!) Our
  suspicion is, initrd prematurely issues vgchange -ay before all the
  PVs come online. This makes sense.

  I already tried to set the rootdelay kernel parameter to make initrd
  wait longer for the boot LV to come up, but it didn't work. Note
  however, it worked with previous kernel versions.

  The problem came up when I upgraded to Utopic, and got kernel 
vmlinuz-3.16.0-23-generic. When I boot with the old kernel from Trusty 
(vmlinuz-3.13.0-37-generic), it works fine.
  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.16.0-23-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC1D2p', '/dev/snd/pcmC1D1c', '/dev/snd/pcmC1D0c', 
'/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/timer'] failed with exit 
code 1:
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  Card1.Amixer.info: Error: [Errno 2] No such file or directory
  Card1.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=/dev/mapper/vmhost--vg-vmhost--swap0
  InstallationDate: Installed on 2013-12-06 (354 days ago)
  InstallationMedia: Ubuntu-Server 13.10 Saucy Salamander - Release amd64 
(20131016)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: WinFast 6150M2MA
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-23-generic 
root=/dev/mapper/hostname--vg-hostname--rootfs ro rootflags=subvol=@ 
rootdelay=300
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-23-generic N/A
   linux-backports-modules-3.16.0-23-generic  N/A
   linux-firmware 1.138
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  utopic utopic
  Uname: Linux 3.16.0-23-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: Upgraded to utopic on 2014-10-28 (28 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 01/19/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 686W1D28
  dmi.board.name: 6150M2MA
  dmi.board.vendor: WinFast
  dmi.board.version: FAB2.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: WinFast
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr686W1D28:bd01/19/2008:svnWinFast:pn6150M2MA:pvrFAB2.0:rvnWinFast:rn6150M2MA:rvrFAB2.0:cvnWinFast:ct3:cvr:
  dmi.product.name: 6150M2MA
  dmi.product.version: FAB2.0
  dmi.sys.vendor: WinFast
  ---
  

Re: [Touch-packages] [Bug 1405277] Re: screen flicker in ubuntu 14.04.1 and derivatives

2015-03-19 Thread hansie
kernel versions on 'Satelite A215-S4697' related 
 


 On Monday, March 9, 2015 12:12 PM, jwm hogenboom bandarsla...@yahoo.com 
wrote:
   

 1. i installed  a brandnew 'crucial ssd' on this 'toshiba satelite A215-S4697' 
- hoping that disk speed would solve the problem
2. first distro installed was 'zorin 9 lite'3. the original installation did 
not flicker: kernel 3.13.32 (??)4. the updated kernel version flickered badly: 
kernel 3.13.46
'zorin' is based on 'ubuntu 14.04 xfce'


 On Friday, February 27, 2015 2:01 PM, jwm hogenboom 
bandarsla...@yahoo.com wrote:
   

 1. the same still holds for all ubuntu 14.04.2 - and all of its derivatives2. 
the flickering does not exist in the very first - and original - kernel of 
ubuntu 14.043. the flickering does not exist in 'linux mint 17.0' - since 
'mint' does not change kernels, the way ubuntu does
 

 On Monday, February 23, 2015 5:20 PM, Christopher M. Penalver 
christopher.m.penal...@gmail.com wrote:
   

 hansie, this bug was reported a while ago and there hasn't been any
activity in it recently. We were wondering if this is still an issue? If
so, could you please test for this with the latest development release
of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
/daily-live/current/ .

If it remains an issue, could you please run the following command in
the development release from a Terminal as it will automatically gather
and attach updated debug information to this report:

apport-collect -p xorg 1405277

Please ensure you have xdiagnose installed, and that you click the Yes
button for attaching additional debugging information.

As well, given the information from the prior release is already
available, testing a release prior to the development one would not be
helpful.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

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

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

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1405277

Title:
  screen flicker in ubuntu 14.04.1 and derivatives

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  1. my screen flickers on all ubuntu 14.04.1 distro versions, linux
  mint 17.1 'cinamon', lxle 64 bit, guadalinex v9 32 bit, etc.

  2. it flickers on the mint 17.1 'cinamon' installation disk - but it
  is stable on mint 17.0 'mate' installed

  3. i can cure it by accesing the 'recovery section' of the 'multi-
  boot' system: but it is NOT 'persistent'

  4. how can i fix this, using the 'cli': to make the fix 'permanent'

  the laptop is an older 'toshiba - amd - athlon x2'

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

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

Title:
  screen flicker in ubuntu 14.04.1 and derivatives

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  1. my screen flickers on all ubuntu 14.04.1 distro versions, linux
  mint 17.1 'cinamon', lxle 64 bit, guadalinex v9 32 bit, etc.

  2. it flickers on the mint 17.1 'cinamon' installation disk - but it
  is stable on mint 17.0 'mate' installed

  3. i can cure it by accesing the 'recovery section' of the 'multi-
  boot' system: but it is NOT 'persistent'

  4. how can i fix this, using the 'cli': to make the fix 'permanent'

  the laptop is an older 'toshiba - amd - athlon x2'

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

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


[Touch-packages] [Bug 1427785] Re: Duplicate processes started after Resume of amd64 bit

2015-03-19 Thread apjjr
I just resumed from stand-by mode and counted 17 instances of dbus-
daemon running.  It's been in and out of suspend mode a few times today.

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

Title:
  Duplicate processes started after Resume of amd64 bit

Status in unity package in Ubuntu:
  New

Bug description:
  $ uname -a
  Linux ajsc855 3.13.0-46-generic #76-Ubuntu SMP Thu Feb 26 18:52:13 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux

  $ cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=14.04
  DISTRIB_CODENAME=trusty
  DISTRIB_DESCRIPTION=Ubuntu 14.04.2 LTS

  Toshiba Satellite C855,  4GB RAM, 720GB HD

  I typically run Thunderbird, Firefox, a terminal or two, Gthumb, Gimp,
  Qcad, Gedit, Libreoffice, Inkscape, Document Viewer and occasionally
  Virtualbox.

  I just noticed this a couple of weeks ago, so I am guessing a recent
  update started it.

  It seems to me that there are quite a few duplicate copies of some
  processes populating memory after suspending/resuming a session for a
  few days.  Namely, dbus-daemon, gvfsd and gconfd-2.  The more I
  suspend/resume the session, the more of these processes appear.  After
  a while they start using up a significant amount of memory and system
  response seems to slow down.

  Logging out and back in did not alleviate the problem. Rebooting did.
  But, I will have to reboot again in a week to free up the memory used
  by these duplicate processes.

  The example session used to get the following results was probably
  well over a week in use.

  Before rebooting:
  $ ps -ef prereboot.txt
  $ grep -i dbus-daemon prereboot.txt|wc -l
  40
  $ grep -i gvfsd prereboot.txt|wc -l
  78
  $ grep -i gconfd-2 prereboot.txt|wc -l
  37

  After rebooting:
  $ ps -ef postreboot.txt
  $ grep -i dbus-daemon postreboot.txt|wc -l
  4
  $ grep -i gvfsd postreboot.txt|wc -l
  5
  $ grep -i gconfd-2 postreboot.txt|wc -l
  1

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

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


[Touch-packages] [Bug 1433936] [NEW] Unity8 fails to start on latest image

2015-03-19 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

On latest image using krillin, unity8-dash never starts. Its on a
starting loop

** Affects: qtubuntu (Ubuntu)
 Importance: Critical
 Assignee: Michał Sawicz (saviq)
 Status: In Progress

-- 
Unity8 fails to start on latest image
https://bugs.launchpad.net/bugs/1433936
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to qtubuntu in Ubuntu.

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


[Touch-packages] [Bug 1428571] Re: Software Update - mysql-apt-config - can't continue

2015-03-19 Thread Lpu8er
Hi,

All of these are quick fixes for users. The real question is probably to
know if this issue is related to debconf or mysql-apt-config.

Goran : I had to do the same. But mysql-apt-config provides a way to
reset the mysql root password, in case of reinstall, which may be
useful.

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

Title:
  Software Update - mysql-apt-config - can't continue

Status in debconf package in Ubuntu:
  Confirmed

Bug description:
  Upon running software updater today, it's tried to update mysql-apt-
  config, and running that has popped up a debconf choice screen (see
  attached).

  However selecting any of the options, pressing the Forward button
  does absolutely nothing. Can't close the window, can't continue, it's
  just stuck like that.

  I bet if I restart the machine everything will end up in a broken
  state too! :D

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: debconf 1.5.53ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar  5 09:53:44 2015
  ExecutablePath: /usr/bin/debconf-communicate
  InstallationDate: Installed on 2013-07-31 (581 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  InterpreterPath: /usr/bin/perl
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_GB.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=set
   LANGUAGE=en_GB:en
  SourcePackage: debconf
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1433943] Re: Enable carddav OAuth2 scope ( https://www.googleapis.com/auth/carddav ) in Ubuntu Online Account (Vivid)

2015-03-19 Thread Alberto Mardegan
We will not enable this in the Google key shipped with the google.provider 
file, because that key should only be used for validating the account creation.
GNOME Evolution ships the google-contacts.service file which you seem to be 
using, so that could be a candidate for adding the permission. I've already 
enabled the CardDav access on the Google API console, so it's just a matter of 
modifying the google-contacts.service file and adding the additional scope 
there.

** Project changed: account-plugins = evolution-data-server (Ubuntu)

** Changed in: evolution-data-server (Ubuntu)
   Importance: Undecided = Medium

** Changed in: evolution-data-server (Ubuntu)
   Status: New = Confirmed

** Changed in: evolution-data-server (Ubuntu)
 Assignee: (unassigned) = Alberto Mardegan (mardy)

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

Title:
  Enable carddav OAuth2 scope ( https://www.googleapis.com/auth/carddav
  ) in Ubuntu Online Account (Vivid)

Status in evolution-data-server package in Ubuntu:
  Confirmed

Bug description:
  It seems Ubuntu does not enable CardDav scope
  (https://www.googleapis.com/auth/carddav) in online account. Ubuntu
  only enables Google Contacts API (Gdata)
  https://www.google.com/m8/feeds/  which is NOT same as CardDav. As a
  result when some application( ex. Syncevolution) tries to access it
  (through oauth2), it gives “authentication failed error”.

  For example, running following command:

  '''

  SYNCEVOLUTION_DEBUG=1 syncevolution --print-databases –daemon=no\

  loglevel=2 backend=carddav username=uoa:3,google-contacts\

  syncURL=https://www.googleapis.com/.well-known/carddav

  '''
  gives following error: 

  “PROPFIND: Neon error code 1: 403 Forbidden, must not retry”

  
  NOTE: It is required that that the scope for accessing CardDAV needs to be 
specified in the sources too. Having it only in the APIs Console is not enough. 
Otherwise Google rejects access to the CardDAV resources with a 401 AuthSub 
challenge.

  Discussion on Syncevolution Mailing List:
  https://lists.syncevolution.org/pipermail/syncevolution/2015-March/005119.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1433943/+subscriptions

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


[Touch-packages] [Bug 1396170] Re: [UbuntuShape] Add support for rectangle overlay

2015-03-19 Thread Pat McGowan
** Changed in: canonical-devices-system-image
   Status: In Progress = Fix Released

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

Title:
  [UbuntuShape] Add support for rectangle overlay

Status in the base for Ubuntu mobile products:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu RTM:
  New

Bug description:
  The Unity shell and other apps require a shaped rectangle overlay
  blended over an image. This is currently implement with a 2-pass
  solution that is neither efficient, nor flexible. It would be good to
  have that implemented efficiently in the toolkit.

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

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


[Touch-packages] [Bug 1362640] Re: Remove qtwebkit from touch image

2015-03-19 Thread Alberto Mardegan
Removing signon-ui. The fix will happen on the signon-plugin-oauth2
project.

** Changed in: signon-ui (Ubuntu)
   Status: Triaged = Invalid

** Changed in: signon-plugin-oauth2 (Ubuntu)
   Status: New = In Progress

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

Title:
  Remove qtwebkit from touch image

Status in the base for Ubuntu mobile products:
  In Progress
Status in Cordova Ubuntu:
  Fix Released
Status in Web Browser App:
  Triaged
Status in signon-plugin-oauth2 package in Ubuntu:
  In Progress
Status in signon-ui package in Ubuntu:
  Invalid
Status in ubuntu-html5-theme package in Ubuntu:
  In Progress
Status in ubuntu-touch-meta package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Triaged

Bug description:
  The argument to remove this is based on the following:

  The qtwebkit webview is deprecated for our sdk and we will not be supporting 
it long term
  We are supporting an Oxide/Chromium solution for the Ubuntu.Webview
  This was done largely for security reasons
  The qtwebkit package is large and we would like to reduce image and install 
size 
  We want to discourage app devs from using this api any longer, the review 
tools have indicated this for several months

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

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


[Touch-packages] [Bug 1433330] Re: Some protobuf Closure objects can access dead objects

2015-03-19 Thread Alexandros Frantzis
** Changed in: mir/0.12
   Status: Triaged = Fix Committed

** Changed in: mir/0.12
 Assignee: (unassigned) = Alberto Aguirre (albaguirre)

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

Title:
  Some protobuf Closure objects can access dead objects

Status in Mir:
  Fix Committed
Status in Mir 0.12 series:
  Fix Committed
Status in mir package in Ubuntu:
  Triaged

Bug description:
  ProtobufMessageProcessor::dispatch will create a protobuf closure
  object that references the ProtobufMessageProcessor this pointer.

  The closure/callback object may be invoked by a different thread (e.g.
  SessionMediator::exchange_buffer). Since there's no protection there
  can be a race between dropping a connection (which destroys the
  ProtoBufMessageProcessor) and the callback being invoked by a
  compositor thread.

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

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


[Touch-packages] [Bug 1430315] Re: DisplayConfigurationOutput.physical_size_mm is undefined/zero

2015-03-19 Thread Launchpad Bug Tracker
** Branch linked: lp:mir/0.12

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

Title:
  DisplayConfigurationOutput.physical_size_mm is undefined/zero

Status in Mir:
  Fix Committed
Status in Mir 0.12 series:
  Fix Committed
Status in mir package in Ubuntu:
  Triaged

Bug description:
  DisplayConfigurationOutput.physical_size_mm is currently (0,0) when
  run on devices, so qtmir has to resort to the android property
  ro.sf.lcd_density to get that info [1]

  [1] -
  https://code.launchpad.net/~dandrader/qtmir/QScreenPhysicalSize/+merge/252156

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

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


[Touch-packages] [Bug 1430315] Re: DisplayConfigurationOutput.physical_size_mm is undefined/zero

2015-03-19 Thread Alexandros Frantzis
** Changed in: mir/0.12
   Status: Triaged = Fix Committed

** Changed in: mir/0.12
 Assignee: (unassigned) = Kevin DuBois (kdub)

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

Title:
  DisplayConfigurationOutput.physical_size_mm is undefined/zero

Status in Mir:
  Fix Committed
Status in Mir 0.12 series:
  Fix Committed
Status in mir package in Ubuntu:
  Triaged

Bug description:
  DisplayConfigurationOutput.physical_size_mm is currently (0,0) when
  run on devices, so qtmir has to resort to the android property
  ro.sf.lcd_density to get that info [1]

  [1] -
  https://code.launchpad.net/~dandrader/qtmir/QScreenPhysicalSize/+merge/252156

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

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


[Touch-packages] [Bug 1424466] Re: Devel package not installable in 14.04.2 (mesa-lts-utopic

2015-03-19 Thread ADR
1) Run Ubuntu 14.04.2 LiveUSB
2) Try to install QtCreator
Result:
apt tells unmet dependencies

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

Title:
  Devel package not installable in 14.04.2 (mesa-lts-utopic

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Trusty:
  Fix Committed

Bug description:
  [Impact] 
   * Some -dev packages like ubuntu-sdk and libglew-dev cannot be installed 
when the lts-utopic stack is used.

  [Test Case]
   * Install the lts-utopic stack.
   * apt-get install ubuntu-sdk
   * Good: you get a whole list of packages to install.
   * Bad: apt-get install fails like pasted in the original bug report.
   * Also test the same without the lts-utopic stack, to make sure there are no 
regressions.

  [Regression Potential] 
   * Low, this has been done for precise before, and mesa packaging has to be 
updated for every LTS release. Unfortunately there are no alternatives. :(

  [Other Info]
   * There's probably an apt bug in here too. Nudging the resolver by 
specifying libgl1-mesa-dev-lts-utopic and libgles2-mesa-dev-lts-utopic works, 
but I didn't find a good way to express this in the depends, and that would 
have to be done for every package.

  [Original bug report]
  Not the first, likely not the last devel to not be installable in 14.04.2 or 
any mesa-lts-utopic install
  Another one is libglew-dev

   sudo apt-get install freeglut3-dev
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libcheese-gtk23 : Depends: libclutter-gtk-1.0-0 (= 0.91.8) but it is not 
going to be installed
     Depends: libcogl15 (= 1.15.8) but it is not going to be 
installed
   libcheese7 : Depends: libclutter-gst-2.0-0 (= 0.10.0) but it is not going 
to be installed
    Depends: gstreamer1.0-clutter but it is not going to be 
installed
   libclutter-1.0-0 : Depends: libcogl-pango15 (= 1.15.8) but it is not going 
to be installed
  Depends: libcogl15 (= 1.15.8) but it is not going to be 
installed

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: freeglut3-dev (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb 22 18:03:30 2015
  InstallationDate: Installed on 2015-02-08 (14 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 
(20150203.2)
  SourcePackage: freeglut
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1433633] Re: init --version does not work

2015-03-19 Thread Didier Roche
that's interesting:
$ ls -l /sbin/init
lrwxrwxrwx 1 root root 20 mars  11 11:22 /sbin/init - /lib/systemd/systemd
$ /sbin/init --help
init [OPTIONS...] {COMMAND}

Send control commands to the init daemon.
$ /lib/systemd/systemd --help
systemd [OPTIONS...]

Starts up and maintains the system or user services.

- seems help commands changes depending on systemd binary on user's
name.

@Robie: you can use systemctl --version in the interim term.


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

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

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

Title:
  init --version does not work

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  According to init(1), --version is expected to work. But instead I
  get:

  $ init --version
  init: unrecognized option '--version'

  As we switch from upstart to systemd, I wanted to check which I was
  running, and this seemed like an obvious way to do it.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd-sysv 219-4ubuntu5
  ProcVersionSignature: User Name 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  Date: Wed Mar 18 14:18:59 2015
  Ec2AMI: ami-0c76
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.medium
  Ec2Kernel: aki-0548
  Ec2Ramdisk: ari-0548
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1387219] Re: Mouse pointer disappears and cursor stops blinking

2015-03-19 Thread Andrei
So is anybody going to do something about this any time soon? Or do we
have to wait another 4 years for this to be fixed?

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

Title:
  Mouse pointer disappears and cursor stops blinking

Status in GtkSourceView Widget:
  Expired
Status in anjuta package in Ubuntu:
  Confirmed
Status in gedit package in Ubuntu:
  Confirmed
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  Open gedit.
  Notice the cursor is blinking.
  Type a few lines of text.
  Highilight some of the text.
  Press CTRLc to cut the text.
  Notice that the mouse ponter is invisible while hovering over the gedit 
window. Notice that the gedit cursor is no longer blinking.

  ***Workaround***
  sudo apt-get install ibus-gtk

   $ uname -a
  Linux XYZ 3.16.0-23-generic #31-Ubuntu SMP Tue Oct 21 17:56:17 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.10
  Release:  14.10
  Codename: utopic

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

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


[Touch-packages] [Bug 1417429] Re: back port signon-plugin-oauth2 Sina weibo fix to rtm

2015-03-19 Thread Launchpad Bug Tracker
This bug was fixed in the package signon-plugin-oauth2 -
0.20+15.04.20150317~rtm-0ubuntu1

---
signon-plugin-oauth2 (0.20+15.04.20150317~rtm-0ubuntu1) 14.09; urgency=medium

  [ Alberto Mardegan ]
  * OAuth2: implement a fallback mechanism when parsing replies (LP:
#1417429)
 -- CI Train Bot ci-train-...@canonical.com   Tue, 17 Mar 2015 09:54:51 +

** Changed in: signon-plugin-oauth2 (Ubuntu RTM)
   Status: New = Fix Released

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

Title:
  back port signon-plugin-oauth2 Sina weibo fix to rtm

Status in the base for Ubuntu mobile products:
  In Progress
Status in signon-plugin-oauth2 package in Ubuntu:
  In Progress
Status in signon-plugin-oauth2 package in Ubuntu RTM:
  Fix Released

Bug description:
  We have already createtd a  RTM (14.10) image for the developers
  contest in China. Due to some limitation of the Sina weibo API, it
  wrongly returns the message type (text/plain) which is incorrect for
  json content. Mardy has fixed the issue, and it is finally landed to
  vivid. The developers in China is recommended using rtm since it is
  more stable. The contest started Dec 18th last year, and it will be
  ended June this year. Sina weibo is an important social network
  service in China. Some developers may use it for their development for
  the competition.

  It is strongly recommended backporting the fix to rtm.

  This problem happens on RTM image of the phone. it seems that it is a
  similar bug report as

  https://bugs.launchpad.net/ubuntu/+source/signon-plugin-
  oauth2/+bug/1415376

  which was fixed for vivid. We need the fix for RTM 14.10 release.

  Thanks  best regards,
  XiaoGuo

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

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


[Touch-packages] [Bug 1413211] Re: [regression] mali, powervr locks up with around the introduction or removal of a third overlay

2015-03-19 Thread Launchpad Bug Tracker
** Branch linked: lp:mir/0.12

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

Title:
  [regression] mali, powervr locks up with around the introduction or
  removal of a third overlay

Status in Mir:
  Fix Committed
Status in Mir 0.12 series:
  Fix Committed
Status in mir package in Ubuntu:
  Triaged

Bug description:
  To reproduce:
  Run mir_demo_server with overlays enabled and 3 onscreen surfaces. It will 
lock up within a few iterations of introducing and removing the 3rd surface.

  Should not affect the current stack (as we always have = 2 surfaces)

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

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


[Touch-packages] [Bug 1413211] Re: [regression] mali, powervr locks up with around the introduction or removal of a third overlay

2015-03-19 Thread Alexandros Frantzis
** Changed in: mir/0.12
 Assignee: (unassigned) = Kevin DuBois (kdub)

** Changed in: mir/0.12
   Status: Triaged = Fix Committed

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

Title:
  [regression] mali, powervr locks up with around the introduction or
  removal of a third overlay

Status in Mir:
  Fix Committed
Status in Mir 0.12 series:
  Fix Committed
Status in mir package in Ubuntu:
  Triaged

Bug description:
  To reproduce:
  Run mir_demo_server with overlays enabled and 3 onscreen surfaces. It will 
lock up within a few iterations of introducing and removing the 3rd surface.

  Should not affect the current stack (as we always have = 2 surfaces)

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

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


[Touch-packages] [Bug 1418569] Re: mir_demo_server doesn't emit hover_exit events

2015-03-19 Thread Launchpad Bug Tracker
** Branch linked: lp:mir/0.12

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

Title:
  mir_demo_server doesn't emit hover_exit events

Status in Mir:
  Fix Committed
Status in Mir 0.12 series:
  Fix Committed
Status in mir package in Ubuntu:
  Triaged

Bug description:
  The demo server doesn't emit hover_exit events when the pointer leaves
  a surface. It only happens when you switch away from the VT it is
  running on.

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

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


[Touch-packages] [Bug 1430893] Re: [FFe] Install Fcitx for Chinese users

2015-03-19 Thread Iain Lane
Gunnar, the FFe for this wasn't approved so language-selector shouldn't
have been uploaded. We wanted to verify that the approach is sensible
first.

Seems that it luckily is, so retrospectively granted, but please be
aware in future.

** Changed in: ubuntu-meta (Ubuntu)
   Status: Confirmed = Fix Released

** Changed in: language-selector (Ubuntu)
   Status: Fix Committed = Fix Released

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

Title:
  [FFe] Install Fcitx for Chinese users

Status in im-config package in Ubuntu:
  Confirmed
Status in language-selector package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  There are currently two main supported input method frameworks
  available for CJK users: IBus (current default) and Fcitx. Both are
  mature projects, but Fcitx is better suited to Chinese users than IBus
  is, and is already the default in Ubuntu Kylin. IBus is increasingly
  moving in the direction of removing features upstream like tracking
  input state on a per-context basis. Also, the leading input method
  provider in China with more than 300 million users, Sogou, only
  supports Fcitx under Linux. Skinning support is non-existent in IBus.

  We've added support for Fcitx on the same level as IBus in Unity, so
  this FFe is a proposal to make Fcitx the default for Chinese locales
  this cycle, as a transition towards making Fcitx the default for all
  users next cycle. The changes should simply be seeding Fcitx and its
  related packages on the CD image, as well as possible changes to im-
  config. Those who have explicitly selected IBus as their chosen input
  method should be unaffected; these changes will only affect new users,
  and users who have never explicitly chosen an input method framework
  in their language settings.

  Also, this FFe propose to make language-selector to install more input
  method packages for Chinese users to their Fcitx equivalents
  (currently IBus) when adding/completing Chinese language support.

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

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


[Touch-packages] [Bug 1428402] Re: ProtobufResponder::send_response_result race

2015-03-19 Thread Alexandros Frantzis
** Changed in: mir/0.12
   Status: Triaged = Fix Committed

** Changed in: mir/0.12
 Assignee: (unassigned) = Alberto Aguirre (albaguirre)

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

Title:
  ProtobufResponder::send_response_result race

Status in Mir:
  Fix Committed
Status in Mir 0.12 series:
  Fix Committed
Status in mir package in Ubuntu:
  Triaged

Bug description:
  ProtobufResponder::send_response_result member must be protected as
  multiple threads call ProtobufResponder::send_response

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

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


[Touch-packages] [Bug 1278223] Re: Mouse Flickering after adding 3rd Monitor

2015-03-19 Thread Christopher M. Penalver
** Tags added: needs-apport-collect

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

Title:
  Mouse Flickering after adding 3rd Monitor

Status in xorg package in Ubuntu:
  Incomplete
Status in xorg package in Fedora:
  Unknown

Bug description:
  My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse
  flickers (or blinks) when the cursor is on monitors one or two, but
  not 3.

  Monitor 1: 1440 x 900 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor
  Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor

  Here's the video card that feeds my laptop's native monitor, monitor 2
  (hdmi).

  lspci | grep 'VGA\|Display'
  00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)
  00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)

  The 3rd Monitor is powered through a Display Link certified SIIG USB
  2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but
  it is a sticker on back of the device):

  lsusb -tv
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
  |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M

  dmesg
  [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee
  [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [1.688351] usb 2-1: Product: VGA Display Adapter
  [1.688353] usb 2-1: Manufacturer: DisplayLink
  [1.688356] usb 2-1: SerialNumber: 119785

  Additionally, unity-control-center crashes sometimes after I Restore
  previous settings, after selecting a resolution too high. This
  freezed my laptop, requiring a hard reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.1-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb  9 18:43:13 2014
  InstallationDate: Installed on 2014-02-02 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140202)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1430893] Re: [FFe] Install Fcitx for Chinese users

2015-03-19 Thread Gunnar Hjalmarsson
On 2015-03-19 10:42, Iain Lane wrote:
 Gunnar, the FFe for this wasn't approved so language-selector
 shouldn't have been uploaded.

Sorry Iain, forgot that.

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

Title:
  [FFe] Install Fcitx for Chinese users

Status in im-config package in Ubuntu:
  Fix Committed
Status in language-selector package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  There are currently two main supported input method frameworks
  available for CJK users: IBus (current default) and Fcitx. Both are
  mature projects, but Fcitx is better suited to Chinese users than IBus
  is, and is already the default in Ubuntu Kylin. IBus is increasingly
  moving in the direction of removing features upstream like tracking
  input state on a per-context basis. Also, the leading input method
  provider in China with more than 300 million users, Sogou, only
  supports Fcitx under Linux. Skinning support is non-existent in IBus.

  We've added support for Fcitx on the same level as IBus in Unity, so
  this FFe is a proposal to make Fcitx the default for Chinese locales
  this cycle, as a transition towards making Fcitx the default for all
  users next cycle. The changes should simply be seeding Fcitx and its
  related packages on the CD image, as well as possible changes to im-
  config. Those who have explicitly selected IBus as their chosen input
  method should be unaffected; these changes will only affect new users,
  and users who have never explicitly chosen an input method framework
  in their language settings.

  Also, this FFe propose to make language-selector to install more input
  method packages for Chinese users to their Fcitx equivalents
  (currently IBus) when adding/completing Chinese language support.

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

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


[Touch-packages] [Bug 1433858] Re: Mouse cursor flickering when using two graphics cards

2015-03-19 Thread Christopher M. Penalver
Jonathan Wang, thank you for reporting this and helping make Ubuntu
better. Could you please test http://cdimage.ubuntu.com/daily-
live/current/ and advise to the results?

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

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

** Description changed:

- See bug #1278223
+ Mouse cursor flickering when using two monitors.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-31.43~14.04.1-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  .tmp.unity.support.test.0:
-  
+ 
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Mar 18 22:40:10 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.3.10, 3.16.0-31-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7821]
-  Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850] 
[1002:6819] (prog-if 00 [VGA controller])
-Subsystem: ASUSTeK Computer Inc. Device [1043:042c]
+  Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7821]
+  Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850] 
[1002:6819] (prog-if 00 [VGA controller])
+    Subsystem: ASUSTeK Computer Inc. Device [1043:042c]
  InstallationDate: Installed on 2015-02-24 (22 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 
(20150218.1)
  MachineType: MSI MS-7821
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic 
root=UUID=cb3bd3ad-4c60-460e-8982-45ab28abdaf2 ro nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/10/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-G45 GAMING (MS-7821)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.5:bd11/10/2014:svnMSI:pnMS-7821:pvr1.0:rvnMSI:rnZ97-G45GAMING(MS-7821):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7821
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1~ubuntu2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Mar 18 14:17:36 2015
  xserver.configfile: default
  xserver.errors:
-  
+ 
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.16.0-1ubuntu1.2~trusty2
  xserver.video_driver: radeon

** Description changed:

- Mouse cursor flickering when using two monitors.
+ Mouse cursor flickering when using two graphics cards.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-31.43~14.04.1-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  .tmp.unity.support.test.0:
  
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Mar 18 22:40:10 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.3.10, 3.16.0-31-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7821]
   Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850] 
[1002:6819] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:042c]
  InstallationDate: Installed on 2015-02-24 (22 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 
(20150218.1)
  MachineType: MSI MS-7821
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic 
root=UUID=cb3bd3ad-4c60-460e-8982-45ab28abdaf2 ro nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw
  

[Touch-packages] [Bug 1433728] Re: white screen after boot

2015-03-19 Thread Didier Roche
If you are getting the same thing using upstart, I doubt this is a
systemd issue TBH (especially as we didn't get any update recently).

Can you go to a tty and attach hre the journal logs? (journalctl -b output)
also the ouptut of  sudo systemctl status -l ddms would helpful.

Thanks!


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

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

Title:
  white screen after boot

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Hi, i'm using Kubuntu 15.04 beta 1 on kernel: Linux kubuntu
  3.19.0-9-generic.

  Today after the last system upgrades when I start the PC, it will boot but 
after the kubuntu splash image, when it has to start sddm, it turns completely 
white... 
  Same thing if i use Upstart.

  I'm on a XPS15 laptop with NVidia 540m and Intel i7...

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

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


[Touch-packages] [Bug 1433936] Re: qtubuntu lacks a versioned dependency on platform-api

2015-03-19 Thread Michał Sawicz
** Also affects: qtubuntu (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  qtubuntu lacks a versioned dependency on platform-api

Status in platform-api package in Ubuntu:
  In Progress
Status in qtubuntu package in Ubuntu:
  In Progress

Bug description:
  On latest image using krillin, unity8-dash never starts. Its on a
  starting loop

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

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


[Touch-packages] [Bug 1433936] Re: qtubuntu lacks a versioned dependency on platform-api

2015-03-19 Thread Michał Sawicz
** Changed in: qtubuntu (Ubuntu)
   Status: New = In Progress

** Changed in: qtubuntu (Ubuntu)
   Importance: Undecided = High

** Changed in: qtubuntu (Ubuntu)
 Assignee: (unassigned) = Michał Sawicz (saviq)

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

Title:
  qtubuntu lacks a versioned dependency on platform-api

Status in platform-api package in Ubuntu:
  In Progress
Status in qtubuntu package in Ubuntu:
  In Progress

Bug description:
  On latest image using krillin, unity8-dash never starts. Its on a
  starting loop

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

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


[Touch-packages] [Bug 1433936] Re: qtubuntu lacks a versioned dependency on platform-api

2015-03-19 Thread Launchpad Bug Tracker
** Branch linked: lp:~saviq/platform-api/fix-symbols

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

Title:
  qtubuntu lacks a versioned dependency on platform-api

Status in platform-api package in Ubuntu:
  In Progress
Status in qtubuntu package in Ubuntu:
  In Progress

Bug description:
  On latest image using krillin, unity8-dash never starts. Its on a
  starting loop

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

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


[Touch-packages] [Bug 1240909] Re: [performance] Restore support for double-buffering by default

2015-03-19 Thread Alexandros Frantzis
** Changed in: mir/0.12
   Status: Triaged = Fix Committed

** Changed in: mir/0.12
 Assignee: (unassigned) = Daniel van Vugt (vanvugt)

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

Title:
  [performance] Restore support for double-buffering by default

Status in Mir:
  Fix Committed
Status in Mir 0.12 series:
  Fix Committed
Status in Mir 0.5 series:
  Won't Fix
Status in mir package in Ubuntu:
  Triaged

Bug description:
  We really should restore support for double-buffering where possible.
  Presently we're on triple-buffering all the time.

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

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


[Touch-packages] [Bug 1417581] Re: USC - mouse cursor on AMD graphics is drawing incorrectly

2015-03-19 Thread Alexandros Frantzis
** Changed in: mir/0.12
   Status: Triaged = Fix Committed

** Changed in: mir/0.12
 Assignee: (unassigned) = Andreas Pokorny (andreas-pokorny)

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

Title:
  USC - mouse cursor on AMD graphics is drawing incorrectly

Status in Mir:
  Fix Committed
Status in Mir 0.12 series:
  Fix Committed
Status in mesa package in Ubuntu:
  New
Status in mir package in Ubuntu:
  Triaged

Bug description:
  I've a Lenovo Flex 2 14D, which has an AMD APU.

  In Unity-System-Compositor, the mouse cursor does not draw correctly.

  See previous version of this bug for visuals:
  https://bugs.launchpad.net/mir/+bug/1391975

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

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


[Touch-packages] [Bug 1425307] Re: [regression] Exception when running phablet-screenshot (mako/vivid 110) [std::exception::what: Attempt to set swap interval on screencast is invalid]

2015-03-19 Thread Alexandros Frantzis
** Changed in: mir/0.12
Milestone: 0.12.1 = None

** Changed in: mir/0.12
 Assignee: (unassigned) = Robert Carr (robertcarr)

** Changed in: mir/0.12
   Status: Triaged = Fix Released

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

Title:
  [regression] Exception when running phablet-screenshot (mako/vivid
  110) [std::exception::what: Attempt to set swap interval on screencast
  is invalid]

Status in Mir:
  Fix Committed
Status in Mir 0.12 series:
  Fix Released
Status in mir package in Ubuntu:
  Triaged

Bug description:
  current build number: 110
  device name: mako
  channel: ubuntu-touch/vivid-proposed
  last update: 2015-02-24 22:35:35
  version version: 110
  version ubuntu: 20150224
  version device: 20150210
  version custom: 20150224

  rsalveti@evasys:~$ phablet-screenshot /tmp/foo.png
  I: Dumping fb0 ...
  [1424817826.846470] Loader: Loading modules from: 
/usr/lib/arm-linux-gnueabihf/mir/client-platform/
  [1424817826.847569] Loader: Loading module: 
/usr/lib/arm-linux-gnueabihf/mir/client-platform/mesa.so
  [1424817826.848393] Loader: Loading module: 
/usr/lib/arm-linux-gnueabihf/mir/client-platform/android.so
  [1424817826.849583] Loader: Loading module: 
/usr/lib/arm-linux-gnueabihf/mir/client-platform/dummy.so
  [1424817826.944654] ERROR mircommon: Caught exception at Mir/EGL driver 
boundary (in setSwapInterval): 
/build/buildd/mir-0.11.0+15.04.20150209.1/src/client/buffer_stream.cpp(283): 
Throw in function virtual void 
mir::client::BufferStream::request_and_wait_for_configure(MirSurfaceAttrib, int)
  Dynamic exception type: 
N5boost16exception_detail10clone_implINS0_19error_info_injectorISt11logic_error
  std::exception::what: Attempt to set swap interval on screencast is invalid

  3004 KB/s (3932160 bytes in 1.278s)
  I: Done

  phablet-tools - 1.1+15.04.20150218-0ubuntu1

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

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


[Touch-packages] [Bug 1430893] Re: [FFe] Install Fcitx for Chinese users

2015-03-19 Thread Aron Xu
The debdiff for setting fcitx as per locale default of zh_*, while
restoring ibus as default for everyone else.

** Patch added: im-config_0.27-1ubuntu8.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1430893/+attachment/4349739/+files/im-config_0.27-1ubuntu8.debdiff

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

Title:
  [FFe] Install Fcitx for Chinese users

Status in im-config package in Ubuntu:
  Confirmed
Status in language-selector package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  There are currently two main supported input method frameworks
  available for CJK users: IBus (current default) and Fcitx. Both are
  mature projects, but Fcitx is better suited to Chinese users than IBus
  is, and is already the default in Ubuntu Kylin. IBus is increasingly
  moving in the direction of removing features upstream like tracking
  input state on a per-context basis. Also, the leading input method
  provider in China with more than 300 million users, Sogou, only
  supports Fcitx under Linux. Skinning support is non-existent in IBus.

  We've added support for Fcitx on the same level as IBus in Unity, so
  this FFe is a proposal to make Fcitx the default for Chinese locales
  this cycle, as a transition towards making Fcitx the default for all
  users next cycle. The changes should simply be seeding Fcitx and its
  related packages on the CD image, as well as possible changes to im-
  config. Those who have explicitly selected IBus as their chosen input
  method should be unaffected; these changes will only affect new users,
  and users who have never explicitly chosen an input method framework
  in their language settings.

  Also, this FFe propose to make language-selector to install more input
  method packages for Chinese users to their Fcitx equivalents
  (currently IBus) when adding/completing Chinese language support.

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

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


[Touch-packages] [Bug 1300557] Re: Screen resolution no longer works

2015-03-19 Thread Christopher M. Penalver
Jeroen T. Vermeulen, could you please test the latest upstream kernel
available from the very top line at the top of the page (the release
names are irrelevant for testing, and please do not test the daily
folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will
allow additional upstream developers to examine the issue.

If the test did not allow you to test to the issue (ex. you couldn't boot into 
the OS) please make a comment in your report about this, and continue to test 
the next most recent kernel version until you can test to the issue. Once 
you've tested the upstream kernel, please comment on which kernel version 
specifically you tested. If this bug is fixed in the mainline kernel, please 
add the following tags by clicking on the yellow circle with a black pencil 
icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-3.XY-rcZ

Where XY and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-3.XY-rcZ

Once testing of the upstream kernel is complete, please mark this bug's
Status as Confirmed. Please let us know your results.

Thank you for your understanding.

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

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

Title:
  Screen resolution no longer works

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My display's native resolution is 2560×1440 pixels.  Prior to, I
  think, Saucy I could only reach this resolution by adding it using
  xrandr, and then calling xrandr on boot/login to select that
  resolution.  The Display preferences did not show any higher options
  than 1920×1200.

  In Saucy, the native resolution just worked, and I could stop using
  xrandr.  It also worked in Trusty in the alpha releases, up to (and I
  think including) beta-1.  But today (this is not an April's fool, is
  it?) I rebooted after an upgrade, and found myself back in 1920×1200.
  Again, the Display preferences list that resolution as the highest
  possible.  But this time, attempts to ‘xrandr --addmode’ my native
  resolution failed.

  The error message wasn't very helpful; I'll try to reproduce it later
  but it throws my display into yet a lower resolution that's hard to
  work with.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14-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: Tue Apr  1 09:59:00 2014
  DistUpgraded: 2014-01-22 17:01:10,909 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
  InstallationDate: Installed on 2013-08-03 (240 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic 
root=UUID=12085c8d-328f-4c75-a04c-184c592f61ee ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to trusty on 2014-01-22 (68 days ago)
  dmi.bios.date: 05/16/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-D3HP-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd05/16/2013:svnGigabyteTechnologyCo.,Ltd.:pnZ87-D3HP:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87-D3HP-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z87-D3HP
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1
  version.xserver-xorg-core: 

[Touch-packages] [Bug 1336713] Re: Nginx+PHP-FPM - Apache gets installed automatically on PHP update

2015-03-19 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Nginx+PHP-FPM - Apache gets installed automatically on PHP update

Status in apt package in Ubuntu:
  Confirmed
Status in php5 package in Ubuntu:
  Confirmed

Bug description:
  This was originally posted as a question. See: 
https://answers.launchpad.net/ubuntu/+source/php5/+question/250691
  ---

  My 14.04 machine that runs Nginx with PHP-FPM received updates for PHP
  and somehow Apache was automatically installed.

  Here is an excerpt from APT history log:
  Install: libapache2-mod-php5:amd64 (5.5.9+dfsg-1ubuntu4.1, automatic), 
libaprutil1-dbd-sqlite3:amd64 (1.5.3-1, automatic), libaprutil1-ldap:amd64 
(1.5.3-1, automatic), apache2-data:amd64 (2.4.7-1ubuntu4, automatic), 
apache2:amd64 (2.4.7-1ubuntu4, automatic), apache2-bin:amd64 (2.4.7-1ubuntu4, 
automatic)

  Looking at the dependencies for the php5 package I don't understand why this 
happened:
  Depends: libapache2-mod-php5 (= 5.5.9+dfsg-1ubuntu4.1) | 
libapache2-mod-php5filter (= 5.5.9+dfsg-1ubuntu4.1) | php5-cgi (= 
5.5.9+dfsg-1ubuntu4.1) | php5-fpm (= 5.5.9+dfsg-1ubuntu4.1), php5-common (= 
5.5.9+dfsg-1ubuntu4.1)

  With Nginx configured to listen on port 80, this unwanted Apache
  installation would interfere at startup (this exactly happened
  sometime ago on an older release). I don't think that this behaviour
  is correct.

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

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


[Touch-packages] [Bug 1336713] Re: Nginx+PHP-FPM - Apache gets installed automatically on PHP update

2015-03-19 Thread Hyacinth Stypuła
I've experienced this bug while upgrading through update-manager (Ubuntu
14.04.2 LTS), here goes the excerpt from APT history log:

Start-Date: 2015-03-19  10:35:14
Commandline: aptdaemon role='role-commit-packages' sender=':1.72'
Install: libapache2-mod-php5:amd64 (5.5.9+dfsg-1ubuntu4.7, automatic), 
apache2-data:amd64 (2.4.7-1ubuntu4.4, automatic), apache2:amd64 
(2.4.7-1ubuntu4.4, automatic), apache2-bin:amd64 (2.4.7-1ubuntu4.4, automatic)
Upgrade: php5-fpm:amd64 (5.5.9+dfsg-1ubuntu4.6, 5.5.9+dfsg-1ubuntu4.7), 
php5-common:amd64 (5.5.9+dfsg-1ubuntu4.6, 5.5.9+dfsg-1ubuntu4.7), 
php5-curl:amd64 (5.5.9+dfsg-1ubuntu4.6, 5.5.9+dfsg-1ubuntu4.7), 
php5-readline:amd64 (5.5.9+dfsg-1ubuntu4.6, 5.5.9+dfsg-1ubuntu4.7), php5:amd64 
(5.5.9+dfsg-1ubuntu4.6, 5.5.9+dfsg-1ubuntu4.7), libxfont1:amd64 
(1.4.7-1ubuntu0.1, 1.4.7-1ubuntu0.2), php5-cli:amd64 (5.5.9+dfsg-1ubuntu4.6, 
5.5.9+dfsg-1ubuntu4.7), php5-mysqlnd:amd64 (5.5.9+dfsg-1ubuntu4.6, 
5.5.9+dfsg-1ubuntu4.7), php5-gd:amd64 (5.5.9+dfsg-1ubuntu4.6, 
5.5.9+dfsg-1ubuntu4.7)
End-Date: 2015-03-19  10:37:05

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

Title:
  Nginx+PHP-FPM - Apache gets installed automatically on PHP update

Status in apt package in Ubuntu:
  Confirmed
Status in php5 package in Ubuntu:
  Confirmed

Bug description:
  This was originally posted as a question. See: 
https://answers.launchpad.net/ubuntu/+source/php5/+question/250691
  ---

  My 14.04 machine that runs Nginx with PHP-FPM received updates for PHP
  and somehow Apache was automatically installed.

  Here is an excerpt from APT history log:
  Install: libapache2-mod-php5:amd64 (5.5.9+dfsg-1ubuntu4.1, automatic), 
libaprutil1-dbd-sqlite3:amd64 (1.5.3-1, automatic), libaprutil1-ldap:amd64 
(1.5.3-1, automatic), apache2-data:amd64 (2.4.7-1ubuntu4, automatic), 
apache2:amd64 (2.4.7-1ubuntu4, automatic), apache2-bin:amd64 (2.4.7-1ubuntu4, 
automatic)

  Looking at the dependencies for the php5 package I don't understand why this 
happened:
  Depends: libapache2-mod-php5 (= 5.5.9+dfsg-1ubuntu4.1) | 
libapache2-mod-php5filter (= 5.5.9+dfsg-1ubuntu4.1) | php5-cgi (= 
5.5.9+dfsg-1ubuntu4.1) | php5-fpm (= 5.5.9+dfsg-1ubuntu4.1), php5-common (= 
5.5.9+dfsg-1ubuntu4.1)

  With Nginx configured to listen on port 80, this unwanted Apache
  installation would interfere at startup (this exactly happened
  sometime ago on an older release). I don't think that this behaviour
  is correct.

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

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


[Touch-packages] [Bug 1430233] Re: Launching/stopping an unpinned app has a 2s delay

2015-03-19 Thread Michał Sawicz
** Changed in: canonical-devices-system-image
   Status: New = Fix Released

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

Title:
  Launching/stopping an unpinned app has a 2s delay

Status in the base for Ubuntu mobile products:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Steps:
  - start an app you have not pinned to launcher

  Expected:
  - splash screen shown immediately

  Current:
  - there's a 1-2s delay

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.02+15.04.20150302-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar 10 10:55:09 2015
  SourcePackage: unity8
  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/canonical-devices-system-image/+bug/1430233/+subscriptions

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


[Touch-packages] [Bug 1417650] Re: Pointer motion and crossing events are missing

2015-03-19 Thread Michał Sawicz
** Changed in: qtmir
   Status: In Progress = Fix Released

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

Title:
  Pointer motion and crossing events are missing

Status in Mir:
  Fix Released
Status in Qt integration with the Mir display server:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Unity 8 doesn't seem to emit events for when the pointer enters or
  leaves a window, or when the pointer moves around inside a window. It
  does seem to emit the needed motion events when the mouse is dragged
  though.

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

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


[Touch-packages] [Bug 1425087] Re: Launcher re-ordering became laggy

2015-03-19 Thread Michał Sawicz
** Changed in: canonical-devices-system-image
   Status: In Progress = Fix Released

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

Title:
  Launcher re-ordering became laggy

Status in the base for Ubuntu mobile products:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  image 121 vivid-proposed on krillin

  1. try to re-order the launcher icon order

  What happens:
  the icon does not get reordered instantly, rather they hang on screen for a 
bit. 

  attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.02+15.04.20150216.1-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: armhf
  Date: Tue Feb 24 18:53:38 2015
  InstallationDate: Installed on 2015-02-24 (0 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150224-020204)
  SourcePackage: unity8
  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/1425087/+subscriptions

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


[Touch-packages] [Bug 1425484] Re: wizard aborts and goes directly to the dash

2015-03-19 Thread Michał Sawicz
** Changed in: canonical-devices-system-image
   Status: In Progress = Fix Released

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

Title:
  wizard aborts and goes directly to the dash

Status in the base for Ubuntu mobile products:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  TEST CASE:
  1. Go to system-settings and do a factory reset
  2. After reboot in the wizard, dismiss the first SIM PIN dialog
  3. Select 'French' in the list of languages
  4. Tap on 'Continue'

  EXPECT RESULT
  The step 'device security' is displayed

  ACTUAL RESULT
  A blank screen is displayed (empty page with the default background) and 
after a few seconds the wizard stops and the dash loads. The edge intro is 
skipped.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.02+15.04.20150224-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: armhf
  Date: Wed Feb 25 11:41:16 2015
  InstallationDate: Installed on 2015-02-25 (0 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150225-020204)
  SourcePackage: unity8
  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/1425484/+subscriptions

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


[Touch-packages] [Bug 1427976] Re: SessionMediator locks mutexes in one thread and unlocks them in another

2015-03-19 Thread Alexandros Frantzis
** Changed in: mir/0.12
   Status: Triaged = Fix Committed

** Changed in: mir/0.12
 Assignee: (unassigned) = Alberto Aguirre (albaguirre)

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

Title:
  SessionMediator locks mutexes in one thread and unlocks them in
  another

Status in Mir:
  Fix Committed
Status in Mir 0.12 series:
  Fix Committed
Status in mir package in Ubuntu:
  Triaged

Bug description:
  SessionMediator locks mutexes in one thread and unlocks them in
  another thread during create_surface or exchange_buffer. This can
  cause undefined behavior:

  http://www.cplusplus.com/reference/mutex/mutex/unlock/

  If the mutex is not currently locked by the calling thread, it causes
  undefined behavior.

  This may potentially be the root cause of  a hang (wait handle never
  signals) seen when creating/destroying menu surfaces while a parent
  does swap_buffers.

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

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


[Touch-packages] [Bug 1427976] Re: SessionMediator locks mutexes in one thread and unlocks them in another

2015-03-19 Thread Launchpad Bug Tracker
** Branch linked: lp:mir/0.12

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

Title:
  SessionMediator locks mutexes in one thread and unlocks them in
  another

Status in Mir:
  Fix Committed
Status in Mir 0.12 series:
  Fix Committed
Status in mir package in Ubuntu:
  Triaged

Bug description:
  SessionMediator locks mutexes in one thread and unlocks them in
  another thread during create_surface or exchange_buffer. This can
  cause undefined behavior:

  http://www.cplusplus.com/reference/mutex/mutex/unlock/

  If the mutex is not currently locked by the calling thread, it causes
  undefined behavior.

  This may potentially be the root cause of  a hang (wait handle never
  signals) seen when creating/destroying menu surfaces while a parent
  does swap_buffers.

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

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


[Touch-packages] [Bug 1430893] Re: [FFe] Install Fcitx for Chinese users

2015-03-19 Thread Aron Xu
Changes for im-config acked at #ubuntu-desktop.

** Changed in: im-config (Ubuntu)
   Status: Confirmed = Fix Committed

** Changed in: im-config (Ubuntu)
 Assignee: (unassigned) = Aron Xu (happyaron)

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

Title:
  [FFe] Install Fcitx for Chinese users

Status in im-config package in Ubuntu:
  Fix Committed
Status in language-selector package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  There are currently two main supported input method frameworks
  available for CJK users: IBus (current default) and Fcitx. Both are
  mature projects, but Fcitx is better suited to Chinese users than IBus
  is, and is already the default in Ubuntu Kylin. IBus is increasingly
  moving in the direction of removing features upstream like tracking
  input state on a per-context basis. Also, the leading input method
  provider in China with more than 300 million users, Sogou, only
  supports Fcitx under Linux. Skinning support is non-existent in IBus.

  We've added support for Fcitx on the same level as IBus in Unity, so
  this FFe is a proposal to make Fcitx the default for Chinese locales
  this cycle, as a transition towards making Fcitx the default for all
  users next cycle. The changes should simply be seeding Fcitx and its
  related packages on the CD image, as well as possible changes to im-
  config. Those who have explicitly selected IBus as their chosen input
  method should be unaffected; these changes will only affect new users,
  and users who have never explicitly chosen an input method framework
  in their language settings.

  Also, this FFe propose to make language-selector to install more input
  method packages for Chinese users to their Fcitx equivalents
  (currently IBus) when adding/completing Chinese language support.

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

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


[Touch-packages] [Bug 1430893] Re: [FFe] Install Fcitx for Chinese users

2015-03-19 Thread Aron Xu
The meta package itself is not related to pull in fcitx packages, but as
ibus-pinyin is removed from desktop-recommends (in 1.333), mark as Fix
Released.

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

Title:
  [FFe] Install Fcitx for Chinese users

Status in im-config package in Ubuntu:
  Fix Committed
Status in language-selector package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  There are currently two main supported input method frameworks
  available for CJK users: IBus (current default) and Fcitx. Both are
  mature projects, but Fcitx is better suited to Chinese users than IBus
  is, and is already the default in Ubuntu Kylin. IBus is increasingly
  moving in the direction of removing features upstream like tracking
  input state on a per-context basis. Also, the leading input method
  provider in China with more than 300 million users, Sogou, only
  supports Fcitx under Linux. Skinning support is non-existent in IBus.

  We've added support for Fcitx on the same level as IBus in Unity, so
  this FFe is a proposal to make Fcitx the default for Chinese locales
  this cycle, as a transition towards making Fcitx the default for all
  users next cycle. The changes should simply be seeding Fcitx and its
  related packages on the CD image, as well as possible changes to im-
  config. Those who have explicitly selected IBus as their chosen input
  method should be unaffected; these changes will only affect new users,
  and users who have never explicitly chosen an input method framework
  in their language settings.

  Also, this FFe propose to make language-selector to install more input
  method packages for Chinese users to their Fcitx equivalents
  (currently IBus) when adding/completing Chinese language support.

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

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


[Touch-packages] [Bug 1407723] Re: Text cursor/selection handles too small and confusing

2015-03-19 Thread Pat McGowan
** Changed in: canonical-devices-system-image
   Status: In Progress = Fix Released

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

Title:
  Text cursor/selection handles too small and confusing

Status in the base for Ubuntu mobile products:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu RTM:
  Confirmed

Bug description:
  It is still very difficult to reliably select text in text fields and
  areas, the handles are tiny and even if you manage to target them,
  you'll cover the text you operate on with your finger.

  It is also very difficult to distinguish between moving the cursor and
  selecting text.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: qtdeclarative5-ubuntu-ui-toolkit-plugin 
1.1.1364+15.04.20141209-0ubuntu2
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.15-0ubuntu3
  Architecture: armhf
  Date: Mon Jan  5 16:25:22 2015
  InstallationDate: Installed on 2014-12-18 (18 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20141218-020204)
  SourcePackage: ubuntu-ui-toolkit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1433936] Re: Unity8 fails to start on latest image

2015-03-19 Thread Michał Sawicz
** Changed in: unity8 (Ubuntu)
   Status: New = In Progress

** Changed in: unity8 (Ubuntu)
   Importance: Undecided = Critical

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) = Michał Sawicz (saviq)

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

Title:
  Unity8 fails to start on latest image

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  On latest image using krillin, unity8-dash never starts. Its on a
  starting loop

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

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


[Touch-packages] [Bug 1433936] [NEW] Unity8 fails to start on latest image

2015-03-19 Thread Omer Akram
Public bug reported:

On latest image using krillin, unity8-dash never starts. Its on a
starting loop

** Affects: unity8 (Ubuntu)
 Importance: Critical
 Assignee: Michał Sawicz (saviq)
 Status: In Progress

** Attachment added: unity8-dash.log
   
https://bugs.launchpad.net/bugs/1433936/+attachment/4349655/+files/unity8-dash.log

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

Title:
  Unity8 fails to start on latest image

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  On latest image using krillin, unity8-dash never starts. Its on a
  starting loop

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

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


[Touch-packages] [Bug 1433943] [NEW] Enable carddav OAuth2 scope ( https://www.googleapis.com/auth/carddav ) in Ubuntu Online Account (Vivid)

2015-03-19 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

It seems Ubuntu does not enable CardDav scope
(https://www.googleapis.com/auth/carddav) in online account. Ubuntu only
enables Google Contacts API (Gdata) https://www.google.com/m8/feeds/
which is NOT same as CardDav. As a result when some application( ex.
Syncevolution) tries to access it (through oauth2), it gives
“authentication failed error”.

For example, running following command:

'''

SYNCEVOLUTION_DEBUG=1 syncevolution --print-databases –daemon=no\

loglevel=2 backend=carddav username=uoa:3,google-contacts\

syncURL=https://www.googleapis.com/.well-known/carddav

'''
gives following error: 

“PROPFIND: Neon error code 1: 403 Forbidden, must not retry”


NOTE: It is required that that the scope for accessing CardDAV needs to be 
specified in the sources too. Having it only in the APIs Console is not enough. 
Otherwise Google rejects access to the CardDAV resources with a 401 AuthSub 
challenge.

Discussion on Syncevolution Mailing List:
https://lists.syncevolution.org/pipermail/syncevolution/2015-March/005119.html

** Affects: evolution-data-server (Ubuntu)
 Importance: Medium
 Assignee: Alberto Mardegan (mardy)
 Status: Confirmed


** Tags: vivid
-- 
Enable carddav OAuth2 scope ( https://www.googleapis.com/auth/carddav ) in 
Ubuntu Online Account (Vivid)
https://bugs.launchpad.net/bugs/1433943
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to evolution-data-server in Ubuntu.

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


[Touch-packages] [Bug 1433963] [NEW] toggling silent mode animation isn't smooth on arale

2015-03-19 Thread Wenfang Si
Public bug reported:

Release  Device Info:
phablet@ubuntu-phablet:~$ system-image-cli -i
current build number: 140
device name: m75
channel: ubuntu-touch/vivid-proposed
last update: 2015-03-19 10:22:28
version version: 140

Steps:
1. : Pull down the Sound indicator
2. : Tap on the Silent mode toggle

The actual result was : 
The animation toggling is a little un-smooth

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

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

Title:
  toggling silent mode animation isn't smooth on arale

Status in indicator-sound package in Ubuntu:
  New

Bug description:
  Release  Device Info:
  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 140
  device name: m75
  channel: ubuntu-touch/vivid-proposed
  last update: 2015-03-19 10:22:28
  version version: 140

  Steps:
  1. : Pull down the Sound indicator
  2. : Tap on the Silent mode toggle

  The actual result was : 
  The animation toggling is a little un-smooth

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

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


[Touch-packages] [Bug 1430893] Re: [FFe] Install Fcitx for Chinese users

2015-03-19 Thread Aron Xu
** Changed in: im-config (Ubuntu)
   Status: Fix Committed = Fix Released

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

Title:
  [FFe] Install Fcitx for Chinese users

Status in im-config package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  There are currently two main supported input method frameworks
  available for CJK users: IBus (current default) and Fcitx. Both are
  mature projects, but Fcitx is better suited to Chinese users than IBus
  is, and is already the default in Ubuntu Kylin. IBus is increasingly
  moving in the direction of removing features upstream like tracking
  input state on a per-context basis. Also, the leading input method
  provider in China with more than 300 million users, Sogou, only
  supports Fcitx under Linux. Skinning support is non-existent in IBus.

  We've added support for Fcitx on the same level as IBus in Unity, so
  this FFe is a proposal to make Fcitx the default for Chinese locales
  this cycle, as a transition towards making Fcitx the default for all
  users next cycle. The changes should simply be seeding Fcitx and its
  related packages on the CD image, as well as possible changes to im-
  config. Those who have explicitly selected IBus as their chosen input
  method should be unaffected; these changes will only affect new users,
  and users who have never explicitly chosen an input method framework
  in their language settings.

  Also, this FFe propose to make language-selector to install more input
  method packages for Chinese users to their Fcitx equivalents
  (currently IBus) when adding/completing Chinese language support.

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

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


[Touch-packages] [Bug 1432599] Re: Network-manager tries to manage virbr0, which it should not

2015-03-19 Thread Franck
Here is a bug report, related to the subject:
https://bugzilla.gnome.org/show_bug.cgi?id=731014

Notice vboxnet0 also appears in nm-applet, but is shown as Unmanaged,
unlike virbr0.

** Bug watch added: GNOME Bug Tracker #731014
   https://bugzilla.gnome.org/show_bug.cgi?id=731014

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

Title:
  Network-manager tries to manage virbr0, which it should not

Status in network-manager package in Ubuntu:
  New

Bug description:
  Since a recent upgrade in vivid, nm is trying to manage virbr0. This
  results in my main machine not getting a real IP address on eth0, and
  virtual machines not being able to use the network.

  This is probably related to
  https://bugzilla.redhat.com/show_bug.cgi?id=1166199

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 16 12:36:07 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-12-13 (92 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  IpRoute:
   default via 10.0.0.1 dev eth0  proto static  metric 1024
   10.0.0.0/24 dev eth0  proto kernel  scope link  src 10.0.0.75
   192.168.111.0/24 dev wlan0  proto kernel  scope link  src 192.168.111.8
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  http_proxy: http://localhost:8118/
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.
  no_proxy: localhost,127.0.0.0/8,::1

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

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


[Touch-packages] [Bug 1433945] [NEW] package lightdm 1.12.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2015-03-19 Thread ryzh
Public bug reported:

insserv: Starting smfpd depends on ondemand and therefore on system facility 
`$all' which can not be true!
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header
dpkg: ошибка при обработке пакета lightdm (--configure):
 подпроцесс установлен сценарий post-installation возвратил код ошибки 1

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: lightdm 1.12.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-31.43-generic 3.16.7-ckt5
Uname: Linux 3.16.0-31-generic x86_64
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
Date: Thu Mar 19 10:46:38 2015
DuplicateSignature: package:lightdm:1.12.3-0ubuntu1: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-03-06 (12 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
SourcePackage: lightdm
Title: package lightdm 1.12.3-0ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package package-from-proposed utopic

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

Title:
  package lightdm 1.12.3-0ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in lightdm package in Ubuntu:
  New

Bug description:
  insserv: Starting smfpd depends on ondemand and therefore on system facility 
`$all' which can not be true!
  insserv: exiting now without changing boot order!
  update-rc.d: error: insserv rejected the script header
  dpkg: ошибка при обработке пакета lightdm (--configure):
   подпроцесс установлен сценарий post-installation возвратил код ошибки 1

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: lightdm 1.12.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-31.43-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  Date: Thu Mar 19 10:46:38 2015
  DuplicateSignature: package:lightdm:1.12.3-0ubuntu1: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-03-06 (12 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  SourcePackage: lightdm
  Title: package lightdm 1.12.3-0ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1240909] Re: [performance] Restore support for double-buffering by default

2015-03-19 Thread Launchpad Bug Tracker
** Branch linked: lp:mir/0.12

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

Title:
  [performance] Restore support for double-buffering by default

Status in Mir:
  Fix Committed
Status in Mir 0.12 series:
  Fix Committed
Status in Mir 0.5 series:
  Won't Fix
Status in mir package in Ubuntu:
  Triaged

Bug description:
  We really should restore support for double-buffering where possible.
  Presently we're on triple-buffering all the time.

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

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


[Touch-packages] [Bug 1417581] Re: USC - mouse cursor on AMD graphics is drawing incorrectly

2015-03-19 Thread Launchpad Bug Tracker
** Branch linked: lp:mir/0.12

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

Title:
  USC - mouse cursor on AMD graphics is drawing incorrectly

Status in Mir:
  Fix Committed
Status in Mir 0.12 series:
  Fix Committed
Status in mesa package in Ubuntu:
  New
Status in mir package in Ubuntu:
  Triaged

Bug description:
  I've a Lenovo Flex 2 14D, which has an AMD APU.

  In Unity-System-Compositor, the mouse cursor does not draw correctly.

  See previous version of this bug for visuals:
  https://bugs.launchpad.net/mir/+bug/1391975

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

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


[Touch-packages] [Bug 1418569] Re: mir_demo_server doesn't emit hover_exit events

2015-03-19 Thread Alexandros Frantzis
** Changed in: mir/0.12
   Status: Triaged = Fix Committed

** Changed in: mir/0.12
 Assignee: (unassigned) = Robert Carr (robertcarr)

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

Title:
  mir_demo_server doesn't emit hover_exit events

Status in Mir:
  Fix Committed
Status in Mir 0.12 series:
  Fix Committed
Status in mir package in Ubuntu:
  Triaged

Bug description:
  The demo server doesn't emit hover_exit events when the pointer leaves
  a surface. It only happens when you switch away from the VT it is
  running on.

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

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


[Touch-packages] [Bug 1433330] Re: Some protobuf Closure objects can access dead objects

2015-03-19 Thread Launchpad Bug Tracker
** Branch linked: lp:mir/0.12

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

Title:
  Some protobuf Closure objects can access dead objects

Status in Mir:
  Fix Committed
Status in Mir 0.12 series:
  Fix Committed
Status in mir package in Ubuntu:
  Triaged

Bug description:
  ProtobufMessageProcessor::dispatch will create a protobuf closure
  object that references the ProtobufMessageProcessor this pointer.

  The closure/callback object may be invoked by a different thread (e.g.
  SessionMediator::exchange_buffer). Since there's no protection there
  can be a race between dropping a connection (which destroys the
  ProtoBufMessageProcessor) and the callback being invoked by a
  compositor thread.

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

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


[Touch-packages] [Bug 1362640] Re: Remove qtwebkit from touch image

2015-03-19 Thread Launchpad Bug Tracker
** Branch linked: lp:~mardy/signon-plugin-oauth2/lp1362640

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

Title:
  Remove qtwebkit from touch image

Status in the base for Ubuntu mobile products:
  In Progress
Status in Cordova Ubuntu:
  Fix Released
Status in Web Browser App:
  Triaged
Status in signon-plugin-oauth2 package in Ubuntu:
  In Progress
Status in signon-ui package in Ubuntu:
  Invalid
Status in ubuntu-html5-theme package in Ubuntu:
  In Progress
Status in ubuntu-touch-meta package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Triaged

Bug description:
  The argument to remove this is based on the following:

  The qtwebkit webview is deprecated for our sdk and we will not be supporting 
it long term
  We are supporting an Oxide/Chromium solution for the Ubuntu.Webview
  This was done largely for security reasons
  The qtwebkit package is large and we would like to reduce image and install 
size 
  We want to discourage app devs from using this api any longer, the review 
tools have indicated this for several months

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

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


[Touch-packages] [Bug 1433936] Re: Unity8 fails to start on latest image

2015-03-19 Thread Michał Sawicz
platform-api from silo 6 did not migrate in time, which meant we missed
a dependency. The next image will work fine and in the mean time we need
to refine our dependencies.

** Package changed: unity8 (Ubuntu) = qtmir (Ubuntu)

** Package changed: qtmir (Ubuntu) = qtubuntu (Ubuntu)

** Summary changed:

- Unity8 fails to start on latest image
+ qtubuntu lacks a versioned dependency on platform-api

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

** Package changed: qtubuntu (Ubuntu) = platform-api (Ubuntu)

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

Title:
  qtubuntu lacks a versioned dependency on platform-api

Status in platform-api package in Ubuntu:
  In Progress

Bug description:
  On latest image using krillin, unity8-dash never starts. Its on a
  starting loop

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

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


[Touch-packages] [Bug 1433945] Re: package lightdm 1.12.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2015-03-19 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package lightdm 1.12.3-0ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in lightdm package in Ubuntu:
  New

Bug description:
  insserv: Starting smfpd depends on ondemand and therefore on system facility 
`$all' which can not be true!
  insserv: exiting now without changing boot order!
  update-rc.d: error: insserv rejected the script header
  dpkg: ошибка при обработке пакета lightdm (--configure):
   подпроцесс установлен сценарий post-installation возвратил код ошибки 1

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: lightdm 1.12.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-31.43-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  Date: Thu Mar 19 10:46:38 2015
  DuplicateSignature: package:lightdm:1.12.3-0ubuntu1: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-03-06 (12 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  SourcePackage: lightdm
  Title: package lightdm 1.12.3-0ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1433936] Re: qtubuntu lacks a versioned dependency on platform-api

2015-03-19 Thread Michał Sawicz
debian/libubuntu-application-api2.symbols has:
u_application_instance_get_mir_connection@Base 2.8.0

Which should have been 2.9.0.

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

Title:
  qtubuntu lacks a versioned dependency on platform-api

Status in platform-api package in Ubuntu:
  In Progress

Bug description:
  On latest image using krillin, unity8-dash never starts. Its on a
  starting loop

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

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


Re: [Touch-packages] [Bug 1409209] Re: After installing Lubuntu from USB stick, GRUB mistakenly lists Lubuntu as Ubuntu

2015-03-19 Thread Istimsak
It would still be ideal to give the name of the ubuntu flavor installed.
The is the same and most applications from one DE will work on others. If
you are installing more one flavor of Ubuntu then this will be a problem.
For testers like us, this would make things easier. For a new user,
hopefully they don't install more than one flavor, should be fine with just
Ubuntu. To the developers, they are all the same.
On Mar 19, 2015 1:30 AM, Walter Lapchynski w...@ubuntu.com wrote:

 I don't disagree with you, but I'm saying that Ubuntu is a unique
 animal. Fedora, RHEL, and CentOS are all sort of separate bedfellows,
 much in the way that Debian, Ubuntu and Mint are. But none of the above
 *except* Ubuntu has all these different flavors. Still, Ubuntu is
 Ubuntu. Kubuntu is Ubuntu, Lubuntu is Ubuntu, Snappy Core is Ubuntu,
 etc. So it makes sense for lsb_release to show Ubuntu and not all these
 others more specific variations.

 The reason I mentioned the odd case of changing desktop environments is
 because it happens all the time. People who started out with Ubuntu come
 crawling over to #lubuntu for help because in their mind, they have
 Lubuntu. That's why I brought that up. It's important to consider such
 ideas holistically and make changes that work generally, especially when
 we're talking about something that ultimately affects every single
 flavor. For that matter, what other infrastructure is available to
 ensure that this is updated? I have no clue, so I'd be concerned about
 messing with it.

 All I'm saying is this is the way it's been for a long time. Maybe
 Kubuntu and Xubuntu do it differently, but that's not been my experience
 (see xubuntu-default-settings and kubuntu-settings). That is why it's
 Won't Fix. Maybe it would be better to call it an Opinion (done).

 I will say that it appears lsb_release gets its info from /etc/lsb-
 release so potentially this could be maintained separately. With that, I
 would talk to the GRUB team and see what they think about the
 implications of such a thing. Needless to say, since this is not a
 ubiquity bug, I'm refiling it against grub2.

 ** Changed in: ubiquity (Ubuntu)
Status: Won't Fix = Opinion

 ** Package changed: ubiquity (Ubuntu) = grub2 (Ubuntu)

 ** Summary changed:

 - After installing Lubuntu from USB stick, GRUB mistakenly lists Lubuntu
 as Ubuntu
 + GRUB shows Ubuntu rather than flavor name

 ** Changed in: grub2 (Ubuntu)
Importance: Undecided = Wishlist

 ** Package changed: grub2 (Ubuntu) = lsb (Ubuntu)

 --
 You received this bug notification because you are a member of Lubuntu
 Packages Team, which is subscribed to the bug report.
 https://bugs.launchpad.net/bugs/1409209

 Title:
   GRUB shows Ubuntu rather than flavor name

 Status in lsb package in Ubuntu:
   Opinion

 Bug description:
   I installed Lubuntu 15.04 Vervet (Live image 2015-01-09) as a Manual
   installation (choosing Something else...) to install the test
   Lubuntu alongside a machine that already has Ubuntu 14.04 LTS and
   Windows 7.

   After installation, Lubuntu was mistakenly listed as Ubuntu in the
   GRUB menu. The existing Ubuntu installation, which had formerly been
   labeled as Ubuntu was now (accurately) labeled as Ubuntu 14.04.

   To reproduce:

   Install Lubuntu alongside other existing operating systems using the
   Something else... option and configuring your partitions in the
   ubiquity installer.

   Expected result:

   Grub lists your new installation as Lubuntu and the other operating
   systems as their correct names.

   Actual result:

   Grub lists my new lubuntu installation as Ubuntu (only) and the
   other operating systems correctly (for me, Ubuntu 14.04.1 LTS and
   Windows 7).

   Hardware profile: https://gist.github.com/e4e4d9d3e41ccf5c27c7

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


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

Title:
  GRUB shows Ubuntu rather than flavor name

Status in lsb package in Ubuntu:
  Opinion

Bug description:
  I installed Lubuntu 15.04 Vervet (Live image 2015-01-09) as a Manual
  installation (choosing Something else...) to install the test
  Lubuntu alongside a machine that already has Ubuntu 14.04 LTS and
  Windows 7.

  After installation, Lubuntu was mistakenly listed as Ubuntu in the
  GRUB menu. The existing Ubuntu installation, which had formerly been
  labeled as Ubuntu was now (accurately) labeled as Ubuntu 14.04.

  To reproduce:

  Install Lubuntu alongside other existing operating systems using the
  Something else... option and configuring your partitions in the
  ubiquity installer.

  Expected result:

  Grub lists your new installation as Lubuntu and the other operating
  systems as their correct names.

  Actual result:

  Grub lists my new lubuntu installation 

[Touch-packages] [Bug 1430315] Re: DisplayConfigurationOutput.physical_size_mm is undefined/zero

2015-03-19 Thread Alexandros Frantzis
** Also affects: mir/0.12
   Importance: Undecided
   Status: New

** Changed in: mir/0.12
   Status: New = Triaged

** Changed in: mir/0.12
   Importance: Undecided = Medium

** Changed in: mir/0.12
Milestone: None = 0.12.1

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

Title:
  DisplayConfigurationOutput.physical_size_mm is undefined/zero

Status in Mir:
  Fix Committed
Status in Mir 0.12 series:
  Triaged
Status in mir package in Ubuntu:
  Triaged

Bug description:
  DisplayConfigurationOutput.physical_size_mm is currently (0,0) when
  run on devices, so qtmir has to resort to the android property
  ro.sf.lcd_density to get that info [1]

  [1] -
  https://code.launchpad.net/~dandrader/qtmir/QScreenPhysicalSize/+merge/252156

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

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


[Touch-packages] [Bug 1428402] Re: ProtobufResponder::send_response_result race

2015-03-19 Thread Launchpad Bug Tracker
** Branch linked: lp:mir/0.12

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

Title:
  ProtobufResponder::send_response_result race

Status in Mir:
  Fix Committed
Status in Mir 0.12 series:
  Fix Committed
Status in mir package in Ubuntu:
  Triaged

Bug description:
  ProtobufResponder::send_response_result member must be protected as
  multiple threads call ProtobufResponder::send_response

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

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


[Touch-packages] [Bug 1336713] Re: Nginx+PHP-FPM - Apache gets installed automatically on PHP update

2015-03-19 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Nginx+PHP-FPM - Apache gets installed automatically on PHP update

Status in apt package in Ubuntu:
  Confirmed
Status in php5 package in Ubuntu:
  Confirmed

Bug description:
  This was originally posted as a question. See: 
https://answers.launchpad.net/ubuntu/+source/php5/+question/250691
  ---

  My 14.04 machine that runs Nginx with PHP-FPM received updates for PHP
  and somehow Apache was automatically installed.

  Here is an excerpt from APT history log:
  Install: libapache2-mod-php5:amd64 (5.5.9+dfsg-1ubuntu4.1, automatic), 
libaprutil1-dbd-sqlite3:amd64 (1.5.3-1, automatic), libaprutil1-ldap:amd64 
(1.5.3-1, automatic), apache2-data:amd64 (2.4.7-1ubuntu4, automatic), 
apache2:amd64 (2.4.7-1ubuntu4, automatic), apache2-bin:amd64 (2.4.7-1ubuntu4, 
automatic)

  Looking at the dependencies for the php5 package I don't understand why this 
happened:
  Depends: libapache2-mod-php5 (= 5.5.9+dfsg-1ubuntu4.1) | 
libapache2-mod-php5filter (= 5.5.9+dfsg-1ubuntu4.1) | php5-cgi (= 
5.5.9+dfsg-1ubuntu4.1) | php5-fpm (= 5.5.9+dfsg-1ubuntu4.1), php5-common (= 
5.5.9+dfsg-1ubuntu4.1)

  With Nginx configured to listen on port 80, this unwanted Apache
  installation would interfere at startup (this exactly happened
  sometime ago on an older release). I don't think that this behaviour
  is correct.

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

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


[Touch-packages] [Bug 1433728] Re: white screen after boot

2015-03-19 Thread Didier Roche
Note that if you are using a virtualization system, you can have be hit
by bug #1433198. Upgrading to xorg-server 2:1.17.1-0ubuntu3 will fix it.
(It fixes some failed autopkgtests as well)

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

Title:
  white screen after boot

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Hi, i'm using Kubuntu 15.04 beta 1 on kernel: Linux kubuntu
  3.19.0-9-generic.

  Today after the last system upgrades when I start the PC, it will boot but 
after the kubuntu splash image, when it has to start sddm, it turns completely 
white... 
  Same thing if i use Upstart.

  I'm on a XPS15 laptop with NVidia 540m and Intel i7...

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

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


  1   2   3   4   >