date:20150325

I ran some Autopilot testing last night and continuing a bit now . The
two new patches do not fix the AP problems. As examples:

- Archive image (#145):
* UITK: 1-2 AP failures
* webbrowser-app: 1-2 AP failures
* calculator: 0 AP failures
* ubuntu-system-settings: 0 AP failures

- Image (#147) added with silo 018 (qtbase DBus patches)
* UITK: 7-8 failures (similar to earlier #145 + previous qtbase DBus fix build)
* webbrowser-app: 5-7 failures
* calculator: 2 failures
* ubuntu-system-settings: 16 AP failures (only 1 run done)

Details at
http://people.canonical.com/~tjyrinki/qt5/fail/qtbase_ubuntu5/

Even if the qtbase patches themselves would be correct and functioning
well and they just happen to make Autopilot break, we can't let
Autopilot regress so badly. Either there should be something more done
to Qt or an Autopilot landing fixing the issues should be put to the
same silo.

As for libusermetrics, the diff for its landing in #106 is at
http://launchpadlibrarian.net/198152771/libusermetrics_1.1.1%2B14.10.20141020-0ubuntu1_1.1.1%2B15.04.20150219-0ubuntu1.diff.gz

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

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: In Progress = Incomplete

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

Title:
  unity8 sometimes hangs on boot

Status in autopilot package in Ubuntu:
  New
Status in libusermetrics package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  The following gdbus call is failing with a Error: Timeout was
  reached message:

  gdbus call --session --dest com.canonical.UnityGreeter --object-path /
  --method org.freedesktop.DBus.Properties.Get
  com.canonical.UnityGreeter IsActive

  
  This is being seen on krillin devices starting with image 106 from 
ubuntu-touch/devel-proposed. It doesn't happen every time, so far today, I've 
seen it 3 times from about 12 tests. On the most recent failure, I grabbed a 
console and tried repeatedly to run the command from the shell, even after 2 
hours the timeout was still being returned (after about 28 seconds).

  A copy of ~/.cache/upstart/unity8.log is here:
  http://paste.ubuntu.com/10179482/

  I have 3 test cases where the problem was observed:
  http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-qtchooser/1/console
  
http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-gsettings-ubuntu-touch-schemas/1/console
  http://d-jenkins.ubuntu-ci:8080/job/fjg-boottest/3/console

  In all cases, the test is using adt-run (from autopkgtest) to drive a
  test on the phone device. adt-run uses the above gdbus call to
  determine if the desktop is active. In all the examples, the device
  was freshly flashed.

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

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

[Touch-packages] [Bug 349469] Re: debconf: DbDriver config: /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

2015-03-25 Thread Herminio

It crashed my update of 15.04 MATE.

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

Title:
  debconf: DbDriver config: /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

Status in Ambasa Operating System:
  New
Status in Debconf:
  New
Status in aptdaemon package in Ubuntu:
  Confirmed
Status in debconf package in Ubuntu:
  Triaged

Bug description:
  Upgrading packages that use debconf sometimes fail with the following
  error:

  debconf: DbDriver config: /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

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

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

[Touch-packages] [Bug 1436006] Re: Screenshots do not properly use the current date

2015-03-25 Thread handsome_feng

** Branch linked: lp:~feng-kylin/unity8/fixlp1436006

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

Title:
  Screenshots do not properly use the current date

Status in The Unity 8 shell:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  It seems we try to name the screenshots using a suffix similar to the camera 
like mmdd-secsorsomething but the month portion is incorrect. For example 
on 3/24 I got
  screenshot20150124_120119280.png
  screenshot20153124_123111200.png
  screenshot20153124_123154122.png

  so the year and day are correct but not the month which seems random.

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

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

[Touch-packages] [Bug 1436006] Re: Screenshots do not properly use the current date

2015-03-25 Thread Michał Sawicz

** No longer affects: unity8

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

Title:
  Screenshots do not properly use the current date

Status in unity8 package in Ubuntu:
  New

Bug description:
  It seems we try to name the screenshots using a suffix similar to the camera 
like mmdd-secsorsomething but the month portion is incorrect. For example 
on 3/24 I got
  screenshot20150124_120119280.png
  screenshot20153124_123111200.png
  screenshot20153124_123154122.png

  so the year and day are correct but not the month which seems random.

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

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

[Touch-packages] [Bug 1436198] [NEW] System shutdown even I click on cancel button in the shutdown popup - GUI error

2015-03-25 Thread Balasubramanian Kandasamy

Public bug reported:

When I click on cancel or X button in the shutdown screen, the system
shutdown. There is no option to cancel the system shutdown.

ProblemType: Bug
DistroRelease: Ubuntu 14.04

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

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

Title:
  System shutdown even I click on cancel button in the shutdown popup -
  GUI error

Status in unity package in Ubuntu:
  New

Bug description:
  When I click on cancel or X button in the shutdown screen, the system
  shutdown. There is no option to cancel the system shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04

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

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

[Touch-packages] [Bug 1436198] Re: System shutdown even I click on cancel button in the shutdown popup - GUI error

2015-03-25 Thread Balasubramanian Kandasamy

** Package changed: unity (Ubuntu) = compiz (Ubuntu)

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

Title:
  System shutdown even I click on cancel button in the shutdown popup -
  GUI error

Status in compiz package in Ubuntu:
  New

Bug description:
  When I click on cancel or X button in the shutdown screen, the system
  shutdown. There is no option to cancel the system shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04

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

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

[Touch-packages] [Bug 1274167] Re: Webkit broken on PowerPC - JSC::LLInt::CLoop

2015-03-25 Thread Adam Smith

Another debian bug on this - https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=771841

** Bug watch added: Debian Bug tracker #771841
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771841

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

Title:
  Webkit broken on PowerPC - JSC::LLInt::CLoop

Status in The WebKit Open Source Project:
  Unknown
Status in qtwebkit-opensource-src package in Ubuntu:
  Fix Released
Status in qtwebkit-source package in Ubuntu:
  Confirmed
Status in webkitgtk package in Ubuntu:
  Confirmed
Status in qtwebkit package in Debian:
  Fix Released
Status in webkitgtk package in Debian:
  New

Bug description:
  Midori crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: midori 0.4.3+dfsg-0.1
  Uname: Linux 3.13.0_A-EON_AmigaOne_X1000_Nemo ppc64
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: powerpc
  CrashCounter: 1
  CurrentDesktop: LXDE
  Date: Wed Jan 29 16:58:54 2014
  ExecutablePath: /usr/bin/midori
  ProcCmdline: midori
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: midori
  StacktraceTop:
   JSC::LLInt::CLoop::execute(JSC::ExecState*, void*, bool) () from 
/usr/lib/powerpc-linux-gnu/libjavascriptcoregtk-1.0.so.0
   callToJavaScript () from 
/usr/lib/powerpc-linux-gnu/libjavascriptcoregtk-1.0.so.0
   JSC::JITCode::execute(JSC::VM*, JSC::ProtoCallFrame*, JSC::Register*) () 
from /usr/lib/powerpc-linux-gnu/libjavascriptcoregtk-1.0.so.0
   JSC::Interpreter::execute(JSC::ProgramExecutable*, JSC::ExecState*, 
JSC::JSObject*) () from /usr/lib/powerpc-linux-gnu/libjavascriptcoregtk-1.0.so.0
   JSC::evaluate(JSC::ExecState*, JSC::SourceCode const, JSC::JSValue, 
JSC::JSValue*) () from /usr/lib/powerpc-linux-gnu/libjavascriptcoregtk-1.0.so.0
  Title: midori crashed with SIGSEGV in JSC::LLInt::CLoop::execute()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video

To manage notifications about this bug go to:
https://bugs.launchpad.net/webkit-open-source/+bug/1274167/+subscriptions

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

[Touch-packages] [Bug 1412367] Re: Show SSS results as they arrive

2015-03-25 Thread Marcus Tomlinson

** Branch unlinked: lp:~marcustomlinson/net-cpp/on_data_handler

** Branch unlinked: lp:~marcustomlinson/unity-scopes-api/lp-1412367

** Branch linked: lp:~thomas-voss/net-cpp/add-streaming

** Description changed:

  (This is a regression of Bug #1359177)
  
  Now that unity-scopes-api has switched to using net-cpp in place of
  QNetwork (Bug #1409995), we are back to waiting on all results to be
  returned from the SSS before displaying them in a smart scope (This is a
  limitation on net-cpp at the moment).
- 
- net-cpp is in the process of being updated to allow us to process
- chunked data responses from a server (lp:~marcustomlinson/net-
- cpp/on_data_handler) but unfortunately this change breaks the net-cpp
- ABI, so we are unable to land such a change at this time.
- 
- This should be dealt with as soon as we are able to handle an ABI
- breaking update.

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

Title:
  Show SSS results as they arrive

Status in net-cpp package in Ubuntu:
  In Progress
Status in unity-scopes-api package in Ubuntu:
  In Progress

Bug description:
  (This is a regression of Bug #1359177)

  Now that unity-scopes-api has switched to using net-cpp in place of
  QNetwork (Bug #1409995), we are back to waiting on all results to be
  returned from the SSS before displaying them in a smart scope (This is
  a limitation on net-cpp at the moment).

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

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

[Touch-packages] [Bug 1436211] [NEW] Remove GTK3 from phone images

Public bug reported:

This is a wishlist bug to eventually remove GTK3 from Ubuntu Phone
images to save some space.

-- gnome-control-center-signon --
Since libaccount-plugin-1.0-0 is included on Ubuntu Phone images, would it be 
possible to refactor it so that it would not depend on GTK3 bringing it on the 
images?

-- address-book-service --
address-book-service depends on evolution-data-server, which depends on GTK3. 
evolution-data-server further depends on libgweather-3-6 and libgcr-ui-3-1 
which both directly depend on GTK3 too.

Would it be possible to work with libfolks-eds25 and other libraries
alone? Or would it be possible to modify evolution-data-server building
to not depend on GTK3 since we're not using the toolkit anyway?

-- themes (unity-asset-pool, adwaita-icon-theme...) --

humanity-icon-theme, ubuntu-mono and unity-asset-pool depend on adwaita-
icon-theme. adwaita-icon-theme directly depends on GTK3.

-- ubuntu-system-settings --

ubuntu-system-settings depends on libtimezonemap1 which directly depends
on GTK3. Maybe the library could be made not to depend on GTK3?

** Affects: address-book-service (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: gnome-control-center-signon (Ubuntu)
 Importance: Undecided
 Status: New

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

** Affects: ubuntu-touch-meta (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: unity-asset-pool (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: ubuntu-touch-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: address-book-service (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  This is a wishlist bug to eventually remove GTK3 from Ubuntu Phone
  images to save some space.
  
- Since libaccount-plugin-1.0-0 is included on Ubuntu Phone images, would
- it be possible to refactor it so that it would not depend on GTK3
- bringing it on the images?
+ -- gnome-control-center-signon --
+ Since libaccount-plugin-1.0-0 is included on Ubuntu Phone images, would it be 
possible to refactor it so that it would not depend on GTK3 bringing it on the 
images?
+ 
+ -- address-book-service --
+ address-book-service depends on evolution-data-server, which depends on GTK3. 
evolution-data-server further depends on libgweather-3-6 and libgcr-ui-3-1 
which both directly depend on GTK3 too.
+ 
+ Would it be possible to work with libfolks-eds25 and other libraries
+ alone? Or would it be possible to modify evolution-data-server building
+ to not depend on GTK3 since we're not using the toolkit anyway?

** Changed in: ubuntu-touch-meta (Ubuntu)
   Status: New = Invalid

** Also affects: unity-asset-pool (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  This is a wishlist bug to eventually remove GTK3 from Ubuntu Phone
  images to save some space.
  
  -- gnome-control-center-signon --
  Since libaccount-plugin-1.0-0 is included on Ubuntu Phone images, would it be 
possible to refactor it so that it would not depend on GTK3 bringing it on the 
images?
  
  -- address-book-service --
  address-book-service depends on evolution-data-server, which depends on GTK3. 
evolution-data-server further depends on libgweather-3-6 and libgcr-ui-3-1 
which both directly depend on GTK3 too.
  
  Would it be possible to work with libfolks-eds25 and other libraries
  alone? Or would it be possible to modify evolution-data-server building
  to not depend on GTK3 since we're not using the toolkit anyway?
+ 
+ -- themes (unity-asset-pool) --
+ 
+ humanity-icon-theme, ubuntu-mono and unity-asset-pool depend on adwaita-
+ icon-theme. adwaita-icon-theme directly depends on GTK3.

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

** Description changed:

  This is a wishlist bug to eventually remove GTK3 from Ubuntu Phone
  images to save some space.
  
  -- gnome-control-center-signon --
  Since libaccount-plugin-1.0-0 is included on Ubuntu Phone images, would it be 
possible to refactor it so that it would not depend on GTK3 bringing it on the 
images?
  
  -- address-book-service --
  address-book-service depends on evolution-data-server, which depends on GTK3. 
evolution-data-server further depends on libgweather-3-6 and libgcr-ui-3-1 
which both directly depend on GTK3 too.
  
  Would it be possible to work with libfolks-eds25 and other libraries
  alone? Or would it be possible to modify evolution-data-server building
  to not depend on GTK3 since we're not using the toolkit anyway?
  
- -- themes (unity-asset-pool) --
+ -- themes (unity-asset-pool, adwaita-icon-theme...) --
  
  humanity-icon-theme, ubuntu-mono and unity-asset-pool depend on adwaita-
  icon-theme. adwaita-icon-theme directly depends on GTK3.
+ 
+ -- ubuntu-system-settings --
+ 
+ ubuntu-system-settings depends on libtimezonemap1 which

[Touch-packages] [Bug 1241986] Re: Cannot connect to WPA/WPA2, EAP-PEAP, MSCHAPV2 network

2015-03-25 Thread Sergi

I've tried making a config file but it didn't work. 
I hope this will be fixed/added soon becasue 9/10 of the time im in a building 
with peap. And in my opinion a smartphone is kind of useless without internet.

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

Title:
  Cannot connect to WPA/WPA2, EAP-PEAP, MSCHAPV2 network

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu for Phones final image on mako I can see a network but
  cannot connect because I never get prompted for the username/password.

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

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

[Touch-packages] [Bug 1435984] Re: SRU: apt-transport-https segfaults when downloading from SBT repository

2015-03-25 Thread Michael Vogt

** Also affects: apt (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

Title:
  SRU: apt-transport-https segfaults when downloading from SBT
  repository

Status in apt package in Ubuntu:
  New
Status in apt source package in Trusty:
  New

Bug description:
  [Impact]

  apt-transport-https crashes whenever any repository's Owner is NULL.

  This leaves the user unable to get any upgrades as long as the
  problematic repository is present in sources.list or sources.list.d
  directory.

  
  [Test Case]

  1. echo deb https://dl.bintray.com/sbt/debian / | sudo tee -a 
/etc/apt/sources.list.d/sbt.list
  2. sudo apt-get update
  3. sudo apt-get install sbt

  Expected result:
  The package gets installed/updated.

  Actual result:
  E: Method https has died unexpectedly!
  E: Sub-process https received a segmentation fault.

  [Regression Potential]

  The patch that was uploaded to both Debian and Ubuntu Vivid is rather
  simple, therefore the regression potential is really low.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apt 1.0.1ubuntu2.6
  ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15
  Uname: Linux 3.13.0-46-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Mar 24 18:15:25 2015
  InstallationDate: Installed on 2014-08-04 (232 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1436203] [NEW] [Dash] unity8-dash crashed with SIGABRT in QMessageLogger::fatal()

2015-03-25 Thread Alberto Mardegan

Public bug reported:

Testing unity8 on a Lenovo IdeaPad s10-3t. The welcome wizard completed 
successfully. Unity8 loads, the indicators are visible and working.
However, nothing else works: the scope shell doesn't load, only the splash 
screen is shown with the progress indicator spinning, and you can see that 
periodically it's restarted. Upstart logs for unity8-shell show an infinite 
loop of these:

==
Loading module: 'libubuntu_application_api_desktop_mirclient.so.2.9.0'
[1427269742.137055] Loader: Loading modules from: 
/usr/lib/i386-linux-gnu/mir/client-platform/
[1427269742.137918] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/client-platform/dummy.so
[1427269742.139587] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/client-platform/mesa.so.2
[1427269742.140657] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/client-platform/mesa.so
QSocketNotifier: Can only be used with threads started with QThread
QSocketNotifier: Can only be used with threads started with QThread
QObject::startTimer: Timers can only be used with threads started with QThread
QIBusPlatformInputContext: invalid bus.
file:///usr/share/unity8/Dash/Dash.qml:245: ReferenceError: scopeStyle is not 
defined
UbuntuWindow - regular geometry
file:///usr/share/unity8/Dash/Dash.qml:245: ReferenceError: scopeStyle is not 
defined
ASSERT: eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE in file 
../../../src/ubuntumirclient/glcontext.cpp, line 70
Loading module: 'libubuntu_application_api_desktop_mirclient.so.2.9.0'
[1427269746.575630] Loader: Loading modules from: 
/usr/lib/i386-linux-gnu/mir/client-platform/
[1427269746.576432] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/client-platform/dummy.so
...
==

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: unity8 8.02+15.04.20150318-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
Uname: Linux 3.13.0-45-generic i686
ApportVersion: 2.16.2-0ubuntu4
Architecture: i386
Date: Tue Mar 24 17:31:02 2015
ExecutablePath: /usr/bin/unity8-dash
InstallationDate: Installed on 2012-10-07 (898 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release i386 
(20120817.3)
ProcCmdline: unity8-dash 
--desktop_file_hint=/usr/share/applications/unity8-dash.desktop
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: unity8
StacktraceTop:
 QMessageLogger::fatal(char const*, ...) const () from 
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
 qt_assert(char const*, char const*, int) () from 
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
 ?? () from 
/usr/lib/i386-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
 ?? () from 
/usr/lib/i386-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
 QOpenGLContext::destroy() () from /usr/lib/i386-linux-gnu/sse2/libQt5Gui.so.5
Title: unity8-dash crashed with SIGABRT in QMessageLogger::fatal()
UpgradeStatus: Upgraded to vivid on 2015-01-31 (52 days ago)
UserGroups: adm lpadmin nopasswdlogin sambashare sudo

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


** Tags: apport-crash i386 need-i386-retrace vivid

** Information type changed from Private to Public

** Summary changed:

- [Dash] unity8-dash crashed with SIGABRT in QMessageLogger::fatail()
+ [Dash] unity8-dash crashed with SIGABRT in QMessageLogger::fatal()

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

Title:
  [Dash] unity8-dash crashed with SIGABRT in QMessageLogger::fatal()

Status in unity8 package in Ubuntu:
  New

Bug description:
  Testing unity8 on a Lenovo IdeaPad s10-3t. The welcome wizard completed 
successfully. Unity8 loads, the indicators are visible and working.
  However, nothing else works: the scope shell doesn't load, only the splash 
screen is shown with the progress indicator spinning, and you can see that 
periodically it's restarted. Upstart logs for unity8-shell show an infinite 
loop of these:

  ==
  Loading module: 'libubuntu_application_api_desktop_mirclient.so.2.9.0'
  [1427269742.137055] Loader: Loading modules from: 
/usr/lib/i386-linux-gnu/mir/client-platform/
  [1427269742.137918] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/client-platform/dummy.so
  [1427269742.139587] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/client-platform/mesa.so.2
  [1427269742.140657] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/client-platform/mesa.so
  QSocketNotifier: Can only be used with threads started with QThread
  QSocketNotifier: Can only be used with threads started with QThread
  QObject::startTimer: Timers can only be used with threads started with QThread
  QIBusPlatformInputContext: invalid bus.
  file:///usr/share/unity8/Dash/Dash.qml:245: ReferenceError: scopeStyle is not 
defined
  UbuntuWindow - regular

[Touch-packages] [Bug 1432843] Re: Lubuntu failed to boot

2015-03-25 Thread Henk Terhell

I tried version 20150324.1 of i386 last night and again this failed to install. 
I was able to install amd64 version of 20150324 on another PC but after 
installation loading takes  2 minutes until login menu appears. In recovery 
mode it shows: a start up job is running for dev-disk.

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

Title:
  Lubuntu failed to boot

Status in X.Org X server:
  New
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  The daily build of Lubuntu 20150316 failed to boot into the live
  session, and fails to install. During the boot session, the Lubuntu
  splash screen appears indicating that Lubuntu was loading. What
  follows next was a blank screen.

  Unfortunately, I cannot sumit the exact version of syslinux since the
  daily build could not boot into an interactive session.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: syslinux 3:6.03~pre18+dfsg-1ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic i686
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: i386
  Date: Mon Mar 16 17:19:35 2015
  Dependencies:
   gcc-5-base 5-20150228-1ubuntu1
   libc6 2.19-15ubuntu2
   libgcc1 1:5-20150228-1ubuntu1
   mtools 4.0.18-2
   multiarch-support 2.19-15ubuntu2
  InstallationDate: Installed on 2015-03-05 (11 days ago)
  InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha i386 (20150303)
  SourcePackage: syslinux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1432843/+subscriptions

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

[Touch-packages] [Bug 1434447] Re: apport reports are not complete for filing bugs against linux-lts-utopic kernel

2015-03-25 Thread Ara Pulido

** Also affects: apport (Ubuntu Utopic)
   Importance: Undecided
   Status: New

** Also affects: apport (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

Title:
  apport reports are not complete for filing bugs against linux-lts-
  utopic kernel

Status in apport package in Ubuntu:
  New
Status in apport source package in Trusty:
  New
Status in apport source package in Utopic:
  New

Bug description:
  When filing a bug with ubuntu-bug linux command on 14.04.2, it won't collect 
extra reports for attachment.
  Only Dependencies.txt and ProcEnviron.txt will be attached to the report. 
(See bug 1434442)

  
  Similar bugs: bug 1352829, bug 1229611

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apport 2.14.1-0ubuntu3.7
  ProcVersionSignature: Ubuntu 3.16.0-31.43~14.04.1-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 20 04:36:34 2015
  InstallationDate: Installed on 2015-03-20 (0 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 
(20150218.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1416424] Re: Wifi list is empty

2015-03-25 Thread Sebastien Bacher

is that still an issue?

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

Title:
  Wifi list is empty

Status in indicator-network package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Invalid

Bug description:
  On recent vivid-proposed builds for mako (e.g. r83), the Wifi list in
  the network indicator as well as in the system settings is empty, even
  when the phone has automatically connected to a saved network.

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 84
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-01-30 14:45:36
  version version: 84
  version ubuntu: 20150130
  version device: 20150129
  version custom: 20150130

  Systems Effected:
  Mako
  Flo
  Manta

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

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

[Touch-packages] [Bug 1436215] Re: Separate GTK2 dependency from libqt5gui5

2015-03-25 Thread Dmitry Shachnev

+1, I had it in my todo list as well.

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

Title:
  Separate GTK2 dependency from libqt5gui5

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  Doing this would save at least 5MB of space on Ubuntu Phone images in
  case nothing else depends on GTK2. Obviously also desktop users using
  only Qt applications would not need to install GTK2.

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

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

[Touch-packages] [Bug 1436192] Re: Dragging objects in a nested server or a client stutters slightly

2015-03-25 Thread Daniel van Vugt

** Branch linked: lp:~vanvugt/mir/59Hz

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

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

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

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

Title:
  Dragging objects in a nested server or a client stutters slightly

Status in Mir:
  In Progress
Status in mir package in Ubuntu:
  Triaged

Bug description:
  Dragging objects in a nested server or a client stutters slightly. You
  can see this in the new mir_demo_client_eglsquare, or when dragging
  windows in a nested server.

  This is due to the 55Hz input resampling rate. Every 12th frame or so
  is skipped (5 frames per second on a 60Hz display).

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

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

[Touch-packages] [Bug 1380982] Re: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message()

2015-03-25 Thread James

ubuntu studio 15.04 
updated from 14.10

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

Title:
  ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message()

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  Error popped up after login

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: ibus 1.5.8-2ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
  Uname: Linux 3.16.0-22-generic x86_64
  ApportVersion: 2.14.7-0ubuntu6
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Tue Oct 14 11:37:21 2014
  ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3
  InstallationDate: Installed on 2014-03-06 (221 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140304)
  ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? ()
  Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: Upgraded to utopic on 2014-09-10 (34 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1436203] ThreadStacktrace.txt

2015-03-25 Thread Apport retracing service

** Attachment added: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1436203/+attachment/4355323/+files/ThreadStacktrace.txt

** Attachment removed: CoreDump.gz
   
https://bugs.launchpad.net/bugs/1436203/+attachment/4355293/+files/CoreDump.gz

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

** Summary changed:

- [Dash] unity8-dash crashed with SIGABRT in QMessageLogger::fatal()
+ [Dash] unity8-dash crashed with SIGABRT in qt_message_fatal()

** Tags removed: need-i386-retrace

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

Title:
  [Dash] unity8-dash crashed with SIGABRT in qt_message_fatal()

Status in unity8 package in Ubuntu:
  New

Bug description:
  Testing unity8 on a Lenovo IdeaPad s10-3t. The welcome wizard completed 
successfully. Unity8 loads, the indicators are visible and working.
  However, nothing else works: the scope shell doesn't load, only the splash 
screen is shown with the progress indicator spinning, and you can see that 
periodically it's restarted. Upstart logs for unity8-shell show an infinite 
loop of these:

  ==
  Loading module: 'libubuntu_application_api_desktop_mirclient.so.2.9.0'
  [1427269742.137055] Loader: Loading modules from: 
/usr/lib/i386-linux-gnu/mir/client-platform/
  [1427269742.137918] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/client-platform/dummy.so
  [1427269742.139587] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/client-platform/mesa.so.2
  [1427269742.140657] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/client-platform/mesa.so
  QSocketNotifier: Can only be used with threads started with QThread
  QSocketNotifier: Can only be used with threads started with QThread
  QObject::startTimer: Timers can only be used with threads started with QThread
  QIBusPlatformInputContext: invalid bus.
  file:///usr/share/unity8/Dash/Dash.qml:245: ReferenceError: scopeStyle is not 
defined
  UbuntuWindow - regular geometry
  file:///usr/share/unity8/Dash/Dash.qml:245: ReferenceError: scopeStyle is not 
defined
  ASSERT: eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE in file 
../../../src/ubuntumirclient/glcontext.cpp, line 70
  Loading module: 'libubuntu_application_api_desktop_mirclient.so.2.9.0'
  [1427269746.575630] Loader: Loading modules from: 
/usr/lib/i386-linux-gnu/mir/client-platform/
  [1427269746.576432] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/client-platform/dummy.so
  ...
  ==

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.02+15.04.20150318-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic i686
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: i386
  Date: Tue Mar 24 17:31:02 2015
  ExecutablePath: /usr/bin/unity8-dash
  InstallationDate: Installed on 2012-10-07 (898 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release i386 
(20120817.3)
  ProcCmdline: unity8-dash 
--desktop_file_hint=/usr/share/applications/unity8-dash.desktop
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: unity8
  StacktraceTop:
   QMessageLogger::fatal(char const*, ...) const () from 
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
   qt_assert(char const*, char const*, int) () from 
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
   ?? () from 
/usr/lib/i386-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
   ?? () from 
/usr/lib/i386-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
   QOpenGLContext::destroy() () from /usr/lib/i386-linux-gnu/sse2/libQt5Gui.so.5
  Title: unity8-dash crashed with SIGABRT in QMessageLogger::fatal()
  UpgradeStatus: Upgraded to vivid on 2015-01-31 (52 days ago)
  UserGroups: adm lpadmin nopasswdlogin sambashare sudo

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

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

[Touch-packages] [Bug 1436203]

2015-03-25 Thread Apport retracing service

StacktraceTop:
 qt_message_fatal (context=..., message=...) at global/qlogging.cpp:1415
 QMessageLogger::fatal (this=0xbfaedd48, msg=0xb6535b14 ASSERT: \%s\ in file 
%s, line %d) at global/qlogging.cpp:636
 qt_assert (assertion=0xb3b5e698 eglDestroyContext(mEglDisplay, mEglContext) 
== EGL_TRUE, file=0xb3b5e66c ../../../src/ubuntumirclient/glcontext.cpp, 
line=70) at global/qglobal.cpp:2868
 UbuntuOpenGLContext::~UbuntuOpenGLContext (this=0x9ea5fb8, 
__in_chrg=optimized out) at ../../../src/ubuntumirclient/glcontext.cpp:70
 UbuntuOpenGLContext::~UbuntuOpenGLContext (this=0x9ea5fb8, 
__in_chrg=optimized out) at ../../../src/ubuntumirclient/glcontext.cpp:71

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

Title:
  [Dash] unity8-dash crashed with SIGABRT in qt_message_fatal()

Status in unity8 package in Ubuntu:
  New

Bug description:
  Testing unity8 on a Lenovo IdeaPad s10-3t. The welcome wizard completed 
successfully. Unity8 loads, the indicators are visible and working.
  However, nothing else works: the scope shell doesn't load, only the splash 
screen is shown with the progress indicator spinning, and you can see that 
periodically it's restarted. Upstart logs for unity8-shell show an infinite 
loop of these:

  ==
  Loading module: 'libubuntu_application_api_desktop_mirclient.so.2.9.0'
  [1427269742.137055] Loader: Loading modules from: 
/usr/lib/i386-linux-gnu/mir/client-platform/
  [1427269742.137918] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/client-platform/dummy.so
  [1427269742.139587] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/client-platform/mesa.so.2
  [1427269742.140657] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/client-platform/mesa.so
  QSocketNotifier: Can only be used with threads started with QThread
  QSocketNotifier: Can only be used with threads started with QThread
  QObject::startTimer: Timers can only be used with threads started with QThread
  QIBusPlatformInputContext: invalid bus.
  file:///usr/share/unity8/Dash/Dash.qml:245: ReferenceError: scopeStyle is not 
defined
  UbuntuWindow - regular geometry
  file:///usr/share/unity8/Dash/Dash.qml:245: ReferenceError: scopeStyle is not 
defined
  ASSERT: eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE in file 
../../../src/ubuntumirclient/glcontext.cpp, line 70
  Loading module: 'libubuntu_application_api_desktop_mirclient.so.2.9.0'
  [1427269746.575630] Loader: Loading modules from: 
/usr/lib/i386-linux-gnu/mir/client-platform/
  [1427269746.576432] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/client-platform/dummy.so
  ...
  ==

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.02+15.04.20150318-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic i686
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: i386
  Date: Tue Mar 24 17:31:02 2015
  ExecutablePath: /usr/bin/unity8-dash
  InstallationDate: Installed on 2012-10-07 (898 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release i386 
(20120817.3)
  ProcCmdline: unity8-dash 
--desktop_file_hint=/usr/share/applications/unity8-dash.desktop
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: unity8
  StacktraceTop:
   QMessageLogger::fatal(char const*, ...) const () from 
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
   qt_assert(char const*, char const*, int) () from 
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
   ?? () from 
/usr/lib/i386-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
   ?? () from 
/usr/lib/i386-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
   QOpenGLContext::destroy() () from /usr/lib/i386-linux-gnu/sse2/libQt5Gui.so.5
  Title: unity8-dash crashed with SIGABRT in QMessageLogger::fatal()
  UpgradeStatus: Upgraded to vivid on 2015-01-31 (52 days ago)
  UserGroups: adm lpadmin nopasswdlogin sambashare sudo

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

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

[Touch-packages] [Bug 1436203] Stacktrace.txt

2015-03-25 Thread Apport retracing service

** Attachment added: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1436203/+attachment/4355322/+files/Stacktrace.txt

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

Title:
  [Dash] unity8-dash crashed with SIGABRT in qt_message_fatal()

Status in unity8 package in Ubuntu:
  New

Bug description:
  Testing unity8 on a Lenovo IdeaPad s10-3t. The welcome wizard completed 
successfully. Unity8 loads, the indicators are visible and working.
  However, nothing else works: the scope shell doesn't load, only the splash 
screen is shown with the progress indicator spinning, and you can see that 
periodically it's restarted. Upstart logs for unity8-shell show an infinite 
loop of these:

  ==
  Loading module: 'libubuntu_application_api_desktop_mirclient.so.2.9.0'
  [1427269742.137055] Loader: Loading modules from: 
/usr/lib/i386-linux-gnu/mir/client-platform/
  [1427269742.137918] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/client-platform/dummy.so
  [1427269742.139587] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/client-platform/mesa.so.2
  [1427269742.140657] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/client-platform/mesa.so
  QSocketNotifier: Can only be used with threads started with QThread
  QSocketNotifier: Can only be used with threads started with QThread
  QObject::startTimer: Timers can only be used with threads started with QThread
  QIBusPlatformInputContext: invalid bus.
  file:///usr/share/unity8/Dash/Dash.qml:245: ReferenceError: scopeStyle is not 
defined
  UbuntuWindow - regular geometry
  file:///usr/share/unity8/Dash/Dash.qml:245: ReferenceError: scopeStyle is not 
defined
  ASSERT: eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE in file 
../../../src/ubuntumirclient/glcontext.cpp, line 70
  Loading module: 'libubuntu_application_api_desktop_mirclient.so.2.9.0'
  [1427269746.575630] Loader: Loading modules from: 
/usr/lib/i386-linux-gnu/mir/client-platform/
  [1427269746.576432] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/client-platform/dummy.so
  ...
  ==

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.02+15.04.20150318-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic i686
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: i386
  Date: Tue Mar 24 17:31:02 2015
  ExecutablePath: /usr/bin/unity8-dash
  InstallationDate: Installed on 2012-10-07 (898 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release i386 
(20120817.3)
  ProcCmdline: unity8-dash 
--desktop_file_hint=/usr/share/applications/unity8-dash.desktop
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: unity8
  StacktraceTop:
   QMessageLogger::fatal(char const*, ...) const () from 
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
   qt_assert(char const*, char const*, int) () from 
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
   ?? () from 
/usr/lib/i386-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
   ?? () from 
/usr/lib/i386-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
   QOpenGLContext::destroy() () from /usr/lib/i386-linux-gnu/sse2/libQt5Gui.so.5
  Title: unity8-dash crashed with SIGABRT in QMessageLogger::fatal()
  UpgradeStatus: Upgraded to vivid on 2015-01-31 (52 days ago)
  UserGroups: adm lpadmin nopasswdlogin sambashare sudo

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

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

[Touch-packages] [Bug 1430828] Re: scopes dont load pictures

2015-03-25 Thread Albert Astals Cid

I can confirm that todays images from ubuntu-rtm/14.09-proposed  (257
for Krillin and 215 for Mako) contain the maybe fix.

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

Title:
  scopes dont load pictures

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

Bug description:
  The phone (krillin) is clearly connected and you can retrive text data
  but pictures do not updated see, attached pictures.

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

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

[Touch-packages] [Bug 1436215] [NEW] Separate GTK2 dependency from libqt5gui5

Public bug reported:

Doing this would save at least 5MB of space on Ubuntu Phone images in
case nothing else depends on GTK2. Obviously also desktop users using
only Qt applications would not need to install GTK2.

** Affects: qtbase-opensource-src (Ubuntu)
 Importance: Wishlist
 Status: New

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

Title:
  Separate GTK2 dependency from libqt5gui5

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  Doing this would save at least 5MB of space on Ubuntu Phone images in
  case nothing else depends on GTK2. Obviously also desktop users using
  only Qt applications would not need to install GTK2.

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

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

[Touch-packages] [Bug 1436235] [NEW] It should be possible to click on the contact URL and have a web page open

2015-03-25 Thread Jon The Nice Guy Spriggs

Public bug reported:

I've found an issue in a click package, and I want to report it to the
publisher/creator. I find the package name, scroll down to Contact and
press on the URL. No response. I long press, trying to provoke a copy
action. No response.

Ideally, this should either be a hyperlink or if not, something which is
copy-and-paste-able.

This is with the BQ Ubuntu Phone, running 14.10 (OS Build 20) Ubuntu
Image Part: 20150312

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

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

Title:
  It should be possible to click on the contact URL and have a web page
  open

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

Bug description:
  I've found an issue in a click package, and I want to report it to the
  publisher/creator. I find the package name, scroll down to Contact
  and press on the URL. No response. I long press, trying to provoke a
  copy action. No response.

  Ideally, this should either be a hyperlink or if not, something which
  is copy-and-paste-able.

  This is with the BQ Ubuntu Phone, running 14.10 (OS Build 20) Ubuntu
  Image Part: 20150312

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

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

[Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock

2015-03-25 Thread Daniel Halvorsen

@Andrea is This fixed included for 15.04 as well?

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

Title:
  After locking screen there is no input field to type password for
  unlock

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  *** IMPORTANT **

  *** The fix is not included in TRUSTY. Will be included with next SRU.
  ***

  If you can reproduce this bug please be sure to provide the following info:
  1. Do you use a multi-head setup? If yes, using just one monitor fixes the 
issue?
  2. Can you reproduce all the time?
  3. Do you use ldap? If yes, using gnome-screensaver fix the issue (see 
comment #115) can you still reproduce that?
  4. Please consider posting /var/log/auth.log (at least part of it, should not 
contain sensitive information)
  5. Please specify the unity version
  *** END IMPORTANT **

  Sometimes (but not always) after locking the screen there is the
  situation not having any input field where I can type the password to
  unlock the session again. The shaded gray area simply does not have
  the input field. I can't do anything, I have to switch to text console
  and stop/start lightdm service to cure the problem loosing all of my
  session :(

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140416-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Apr 22 22:17:57 2014
  InstallationDate: Installed on 2012-03-03 (780 days ago)
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago)

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

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

[Touch-packages] [Bug 1434151] Re: [system-settings] the user should not need to sign into Ubuntu One in order to update core apps

2015-03-25 Thread Sebastien Bacher

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

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

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

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

Title:
  [system-settings] the user should not need to sign into Ubuntu One in
  order to update core apps

Status in Ubuntu UX bugs:
  Triaged
Status in ubuntu-download-manager package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  New

Bug description:
  Apps that come pre-installed with Ubuntu Touch should not require the
  user to create an UbuntuOne account in order to receive updates to
  those apps.

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

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

[Touch-packages] [Bug 1426467] Re: Indicator can fail to display panel icon

2015-03-25 Thread Jonathan Cave

ubuntu-touch/vivid-proposed arale r148

Inserted a SIM and rebooted after flash of the above. After boot network
indicator showed a wifi connection, but no cellular connection. On the
menu the cellular showed Offline. Examing ofono list-modems showed
ril_0 as online.

Issued a restart network-indicator and the state then showed the
cellular connection correctly.

** Attachment added: indicator-network.log

https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1426467/+attachment/4355397/+files/indicator-network.log

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

Title:
Indicator can fail to display panel icon

Status in the base for Ubuntu mobile products:
Confirmed
Status in indicator-network package in Ubuntu:
Confirmed

Bug description:
current build number: 122
device name: krillin
channel: ubuntu-touch/devel-proposed

It's possible for the device to boot in such a manner that the
network-indicator doesn't display an icon on the top panel ( see
attached screenshot ).

This bug was discovered while testing an ofono vivid silo. The
associated ofono merge request is:

https://code.launchpad.net/~phablet-
team/ofono/ww10-update/+merge/250665

The version of ofono in the silo (ubuntu-013) is:

1.12.bzr6888+15.04.20150224-0ubuntu1

This version of ofono fixes a couple of bugs, the most important being
a regression on krillin where the 2nd SIM isn't always recognized on
boot.

My testing was performed using two SIMs, with the 2nd SIM being PIN-
locked.

In the case of the missing icon, no PIN unlock screen was displayed
after booting.

I checked using 'ps' and an indicator-network process is running,
however when I checked /home/phablet/.cache/upstart, there only
indicator-network log files I see are the saved .gz files. There's no
unzipped/current indicator-network.log. The .gz log file with the
most recent timestamp shows a single log message:

phablet@ubuntu-phablet:~/.cache/upstart$ less indicator-network.log.1.gz
void core::dbus::PropertyT::handle_changed(const
core::dbus::types::Variant) [with PropertyType =
org::freedesktop::URfkill::Interface::Killswitch::Property::State]:
org.freedesktop.DBus.Error.UnknownMethod: Method Get with signature ss on
interface org.freedesktop.DBus.Properties doesn't exist

I checked and urfkilld is running on the system.

I also verified that there were no crash files present on the system.

I also checked and there was nothing relevant in syslog.

This bug is hard to reproduce as well. I've hit it 4 or 5 times out
of a total of maybe 45-50 reboots.

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

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

[Touch-packages] [Bug 1314653] Re: sysvinit: default cpufreq governor to powersave for intel-pstate driver

This bug was fixed in the package sysvinit - 2.88dsf-41ubuntu6.1

---
sysvinit (2.88dsf-41ubuntu6.1) trusty; urgency=low

  [Colin King]
  * debian/src/initscripts/etc/init.d/ondemand: Add powersave as a final
resort powersaving governor. If intel_pstate is enabled (which is
possible on the utopic-hwe kernel) this is the only one available
(LP: #1314653)
 -- Stefan Bader stefan.ba...@canonical.com   Fri, 13 Mar 2015 16:02:15 +0100

** Changed in: sysvinit (Ubuntu Trusty)
   Status: Fix Committed = Fix Released

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

Title:
  sysvinit: default cpufreq governor to powersave for intel-pstate
  driver

Status in sysvinit package in Ubuntu:
  Fix Released
Status in sysvinit source package in Trusty:
  Fix Released
Status in sysvinit source package in Utopic:
  Fix Released

Bug description:
  When defaulting to the intel-pstate driver, there are only a couple of
  cpufreq governors available, none of which are handled in the
  /etc/init.d/ondemand script.

  Since this driver is meant to be used for power saving, it seems wrong
  to leave the system in the kernel default configured performance
  governor after boot, so I think it is pertinent to set this to
  powersave if it is the only suitable non-power hungry governor
  available.

  How to reproduce:

  1. enable the intel_pstate driver on a recent Intel machine
  (Sandybridge or above)

  edit /etc/default/grub, modify the following:

  GRUB_CMDLINE_LINUX_DEFAULT=quiet splash intel_pstate=enable

  and run:

  sudo update-grub

  and reboot.

  2. login

  3. wait at least 60 seconds for /etc/init.d/ondemand to complete

  check out the default cpufreq governor, you will see it is still set
  to the boot default of performance:

  cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor

  With the attached fix the system will boot into a less aggressive
  cpufreq governor.

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

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

[Touch-packages] [Bug 1431058] Re: Stable Release Update to provide possiblity of automatically reporting crashes

This bug was fixed in the package apport - 2.14.1-0ubuntu3.8

---
apport (2.14.1-0ubuntu3.8) trusty-proposed; urgency=medium

  * Backport changes from 14.10 to ensure that automatic crash reporting
works. (LP: #1431058)
- Refactor whoopsie-upload-all to behave more reliably in case of
  overlapping crash processing.
- debian/apport-noui.upstart: refactor to make this an 'instance' job for
  each incoming .crash file, and drop the racy handling of non-root .crash
  files (as well as the unnecessary 'env MATCH' line).
- debian/apport-noui.upstart: remove early exit
- debian/apport-noui.dirs: create /var/lib/apport
- apport-noui: make the package installation automatically enable
  autosubmission, and update the package description accordingly.
 -- Brian Murray br...@ubuntu.com   Thu, 12 Mar 2015 15:58:32 -0700

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

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

Title:
  Stable Release Update to provide possiblity of automatically reporting
  crashes

Status in apport package in Ubuntu:
  Invalid
Status in apport source package in Trusty:
  Fix Released

Bug description:
  [Test Case]
  ---
  1) Install apport-noui
  2) Verify /var/lib/apport/autoreport is created
  3) sleep 1000 
  4) pkill -11 sleep
  5) observe /var/crash/_bin_sleep.crash file
  6) wait a wee bit
  7) observe /var/crash/_bin_sleep.upload and .uploaded are created

  The version of apport in Ubuntu 14.04 is missing a few changes that
  would allow users to install apport-noui and allow crash reports to be
  submitted automatically from systems with it installed. The changes
  are the following:

    * debian/apport-noui.upstart: remove early exit (LP: #1235436)
    * debian/apport-noui.dirs: create /var/lib/apport (LP: #1235436)
    * data/whoopsie-upload-all: backport utopic version of it
    * apport-noui: make the package installation automatically enable
  autosubmission, and update the package description accordingly.
  LP: #1351137.

  The changes to whoopsie-upload-all can be found in this revision
  (http://bazaar.launchpad.net/~ubuntu-core-
  dev/ubuntu/vivid/apport/ubuntu/revision/2351) and they were fixing LP:
  #1354318.  It would be useful if users of 14.04 could install apport-
  noui and have crash reports automatically submitted for them.

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

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

[Touch-packages] [Bug 1431058] Update Released

2015-03-25 Thread Adam Conrad

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

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

Title:
  Stable Release Update to provide possiblity of automatically reporting
  crashes

Status in apport package in Ubuntu:
  Invalid
Status in apport source package in Trusty:
  Fix Released

Bug description:
  [Test Case]
  ---
  1) Install apport-noui
  2) Verify /var/lib/apport/autoreport is created
  3) sleep 1000 
  4) pkill -11 sleep
  5) observe /var/crash/_bin_sleep.crash file
  6) wait a wee bit
  7) observe /var/crash/_bin_sleep.upload and .uploaded are created

  The version of apport in Ubuntu 14.04 is missing a few changes that
  would allow users to install apport-noui and allow crash reports to be
  submitted automatically from systems with it installed. The changes
  are the following:

    * debian/apport-noui.upstart: remove early exit (LP: #1235436)
    * debian/apport-noui.dirs: create /var/lib/apport (LP: #1235436)
    * data/whoopsie-upload-all: backport utopic version of it
    * apport-noui: make the package installation automatically enable
  autosubmission, and update the package description accordingly.
  LP: #1351137.

  The changes to whoopsie-upload-all can be found in this revision
  (http://bazaar.launchpad.net/~ubuntu-core-
  dev/ubuntu/vivid/apport/ubuntu/revision/2351) and they were fixing LP:
  #1354318.  It would be useful if users of 14.04 could install apport-
  noui and have crash reports automatically submitted for them.

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

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

[Touch-packages] [Bug 1047517] Re: compiz crashed with SIGSEGV in g_mount_spec_to_dbus_with_path() ... from unity::IconLoader::Impl::IconLoaderTask::LoaderJobFunc()

2015-03-25 Thread Andrea Azzarone

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

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

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

Title:
  compiz crashed with SIGSEGV in g_mount_spec_to_dbus_with_path() ...
  from unity::IconLoader::Impl::IconLoaderTask::LoaderJobFunc()

Status in Unity:
  Confirmed
Status in Unity 7.2 series:
  Confirmed
Status in glib2.0 package in Ubuntu:
  Confirmed
Status in gvfs package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Unity crashed when i was trying the Preview.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: unity 6.4.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
  Uname: Linux 3.5.0-13-generic i686
  ApportVersion: 2.5.1-0ubuntu7
  Architecture: i386
  CrashCounter: 1
  Date: Fri Sep  7 18:49:48 2012
  ExecutablePath: /usr/bin/compiz
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 
(20120423)
  ProcCmdline: compiz
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0xb0d448c2 g_mount_spec_to_dbus_with_path+50:
mov0x4(%eax),%ebp
   PC (0xb0d448c2) ok
   source 0x4(%eax) (0x0005) not located in a known VMA region (needed 
readable region)!
   destination %ebp ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   g_mount_spec_to_dbus_with_path () from 
/usr/lib/i386-linux-gnu/gvfs/libgvfscommon.so
   ?? () from /usr/lib/i386-linux-gnu/gio/modules/libgvfsdbus.so
   ?? () from /usr/lib/i386-linux-gnu/gio/modules/libgvfsdbus.so
   ?? () from /usr/lib/i386-linux-gnu/gio/modules/libgvfsdbus.so
   ?? () from /usr/lib/i386-linux-gnu/gio/modules/libgvfsdbus.so
  Title: compiz crashed with SIGSEGV in g_mount_spec_to_dbus_with_path()
  UpgradeStatus: Upgraded to quantal on 2012-09-07 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1436252] [NEW] Behaves inconsistently when you unplug headphones

2015-03-25 Thread Jarno Suni

Public bug reported:

In the beginning headphones are plugged in, and Auto-Mute Mode set Disabled 
in alsamixer.
Start pulseaudio.
Then unplug headphones. Speakers are muted.
Then plug headphones in. Speakers are muted.
Then unplug headphones. Speaker volume is unmuted.

I expect Speaker levels and muted/unmuted state of Speakers in alsamixer
stay intact when you plug headphones in or out. And concerning the Auto-
Mute Mode Disabled, Speakers should not get effectively muted when
headphones are plugged in.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: pulseaudio 1:4.0-0ubuntu11.1
ProcVersionSignature: Ubuntu 3.13.0-48.80-lowlatency 3.13.11-ckt16
Uname: Linux 3.13.0-48-lowlatency x86_64
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jarnos 2255 F panel-12-mixer
  jarnos 8103 F alsamixer
  jarnos 8313 F pulseaudio
CurrentDesktop: XFCE
Date: Wed Mar 25 11:59:07 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-09-21 (185 days ago)
InstallationMedia: Ubuntu-Studio 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.1)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/26/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.6.6
dmi.board.name: 0RF703
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex 745
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug trusty

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

Title:
  Behaves inconsistently when you unplug headphones

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  In the beginning headphones are plugged in, and Auto-Mute Mode set 
Disabled in alsamixer.
  Start pulseaudio.
  Then unplug headphones. Speakers are muted.
  Then plug headphones in. Speakers are muted.
  Then unplug headphones. Speaker volume is unmuted.

  I expect Speaker levels and muted/unmuted state of Speakers in
  alsamixer stay intact when you plug headphones in or out. And
  concerning the Auto-Mute Mode Disabled, Speakers should not get
  effectively muted when headphones are plugged in.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11.1
  ProcVersionSignature: Ubuntu 3.13.0-48.80-lowlatency 3.13.11-ckt16
  Uname: Linux 3.13.0-48-lowlatency x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jarnos 2255 F panel-12-mixer
jarnos 8103 F alsamixer
jarnos 8313 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Mar 25 11:59:07 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-21 (185 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.1)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.6.6
  dmi.board.name: 0RF703
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 745
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1436215] Re: Separate GTK2 dependency from libqt5gui5

** Bug watch added: Debian Bug tracker #781148
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781148

** Also affects: qtbase-opensource-src (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781148
   Importance: Unknown
   Status: Unknown

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

Title:
  Separate GTK2 dependency from libqt5gui5

Status in qtbase-opensource-src package in Ubuntu:
  New
Status in qtbase-opensource-src package in Debian:
  Unknown

Bug description:
  Doing this would save at least 5MB of space on Ubuntu Phone images in
  case nothing else depends on GTK2. Obviously also desktop users using
  only Qt applications would not need to install GTK2.

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

-- 
Mailing list: https://launchpad.net/~touch-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] Re: toggling silent mode animation isn't smooth on arale

2015-03-25 Thread Wenfang Si

it looks good with revision147.

** Changed in: indicator-sound (Ubuntu)
   Status: New = Invalid

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

Title:
  toggling silent mode animation isn't smooth on arale

Status in indicator-sound package in Ubuntu:
  Invalid

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 1435035] [NEW] No CopyPaste for wifi key possible .

You have been subscribed to a public bug:

Ubuntu 14.10 (r20)

There is no chance to paste a long wpa key in the passphrase textfield for a 
new AP.
Thats bad if you have a long passphrase like 63 signs.

If it has sth. to do with security, fine. But then remove the Show Key
Option too;-)

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

-- 
No CopyPaste for wifi key possible .
https://bugs.launchpad.net/bugs/1435035
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to indicator-network 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 1314653] Update Released

2015-03-25 Thread Adam Conrad

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

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

Title:
  sysvinit: default cpufreq governor to powersave for intel-pstate
  driver

Status in sysvinit package in Ubuntu:
  Fix Released
Status in sysvinit source package in Trusty:
  Fix Released
Status in sysvinit source package in Utopic:
  Fix Released

Bug description:
  When defaulting to the intel-pstate driver, there are only a couple of
  cpufreq governors available, none of which are handled in the
  /etc/init.d/ondemand script.

  Since this driver is meant to be used for power saving, it seems wrong
  to leave the system in the kernel default configured performance
  governor after boot, so I think it is pertinent to set this to
  powersave if it is the only suitable non-power hungry governor
  available.

  How to reproduce:

  1. enable the intel_pstate driver on a recent Intel machine
  (Sandybridge or above)

  edit /etc/default/grub, modify the following:

  GRUB_CMDLINE_LINUX_DEFAULT=quiet splash intel_pstate=enable

  and run:

  sudo update-grub

  and reboot.

  2. login

  3. wait at least 60 seconds for /etc/init.d/ondemand to complete

  check out the default cpufreq governor, you will see it is still set
  to the boot default of performance:

  cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor

  With the attached fix the system will boot into a less aggressive
  cpufreq governor.

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

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

[Touch-packages] [Bug 1435311] Re: fcitx (the framework) should be seeded in desktop

Correction #3: I meant debian/control, of course.

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

Title:
  fcitx (the framework) should be seeded in desktop

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  As a result of bug #1430893, check-language-support now pulls fcitx IM
  support for Chinese instead of IBus ditto. However, this is true only
  if the fcitx package is installed.

  Consider these steps:

  * Plain English install - fcitx not installed

  * Install a Chinese language using Language Support, and find that
1. No IM support gets installed and
2. fcitx is not available as an IM framework option.

  I think it would make more sense to have the fcitx package installed
  for all users.

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

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

[Touch-packages] [Bug 1425114] Re: Please build documentation package for QtOrganizer

** Changed in: qtpim-opensource-src (Ubuntu)
   Status: Triaged = In Progress

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

Title:
  Please build documentation package for QtOrganizer

Status in qtpim-opensource-src package in Ubuntu:
  In Progress

Bug description:
  We're providing QtOrganizer as part of the set of libraries from the
  SDK, and we're making its API documentation available online. However,
  these documents are being generated and maintained manually, which is
  not scalable and often causes them to be out-of-date and misleading to
  app developers.

  In order to enable automatic publishing of docs, just as the other APIs, we 
would need documentation packages to be created for:
  - qtpim5-doc
  - qtpim5-doc-html

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

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

[Touch-packages] [Bug 1436252] Re: Behaves inconsistently when you unplug headphones

2015-03-25 Thread Jarno Suni

** Attachment added: pulseverbose.log
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1436252/+attachment/4355406/+files/pulseverbose.log

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

Title:
  Behaves inconsistently when you unplug headphones

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  In the beginning headphones are plugged in, and Auto-Mute Mode set 
Disabled in alsamixer.
  Start pulseaudio.
  Then unplug headphones. Speakers are muted.
  Then plug headphones in. Speakers are muted.
  Then unplug headphones. Speaker volume is unmuted.

  I expect Speaker levels and muted/unmuted state of Speakers in
  alsamixer stay intact when you plug headphones in or out. And
  concerning the Auto-Mute Mode Disabled, Speakers should not get
  effectively muted when headphones are plugged in.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11.1
  ProcVersionSignature: Ubuntu 3.13.0-48.80-lowlatency 3.13.11-ckt16
  Uname: Linux 3.13.0-48-lowlatency x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jarnos 2255 F panel-12-mixer
jarnos 8103 F alsamixer
jarnos 8313 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Mar 25 11:59:07 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-21 (185 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.1)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.6.6
  dmi.board.name: 0RF703
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 745
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1435311] Re: fcitx (the framework) should be seeded in desktop

It wouldn't automatically make it default, but it would make it
available and possible to switch to from gnome-language-selector after
having installed a Chinese language.

The language packs are auto built AFAIK, and I don't know how easy it is
to fiddle with debian/config for only a few of them.

Also, pkg_depends tests whether fcitx is installed, but I suppose this
could be changed to test for fcitx-bin.

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

Title:
  fcitx (the framework) should be seeded in desktop

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  As a result of bug #1430893, check-language-support now pulls fcitx IM
  support for Chinese instead of IBus ditto. However, this is true only
  if the fcitx package is installed.

  Consider these steps:

  * Plain English install - fcitx not installed

  * Install a Chinese language using Language Support, and find that
1. No IM support gets installed and
2. fcitx is not available as an IM framework option.

  I think it would make more sense to have the fcitx package installed
  for all users.

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

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

[Touch-packages] [Bug 1435311] Re: fcitx (the framework) should be seeded in desktop

Another problem: gnome-language-selector uses check-language-support to
first list the packages to be installed, and then installs them. It
means that l-s wouldn't pull the fcitx IM stuff according to pkg_depends
when a Chinese language is installed, but only next time gnome-language-
selector is started.

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

Title:
  fcitx (the framework) should be seeded in desktop

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  As a result of bug #1430893, check-language-support now pulls fcitx IM
  support for Chinese instead of IBus ditto. However, this is true only
  if the fcitx package is installed.

  Consider these steps:

  * Plain English install - fcitx not installed

  * Install a Chinese language using Language Support, and find that
1. No IM support gets installed and
2. fcitx is not available as an IM framework option.

  I think it would make more sense to have the fcitx package installed
  for all users.

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

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

[Touch-packages] [Bug 1363214] Re: [System Settings] [design] allow Passcodes of variable length instead of just 4 digits

2015-03-25 Thread Matthew Paul Thomas

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

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

Title:
  [System Settings] [design] allow Passcodes of variable length instead
  of just 4 digits

Status in Ubuntu UX bugs:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Currently when setting a Passcode on the device, it must be 4 digits.
  This is artificially limiting. Other platforms (eg Android) allow
  longer Passcodes. It has always been my understanding that we should
  support Swipe, Passphrase and Passcode where Passphrase and Passcode
  can be arbitrarily long.

  However, once longer Passcodes are supported, we will have to add an
  Enter key. Right now, the lockscreen checks the Passcode once 4 digits
  are added so that you don't have to press Enter. I guess this was done
  for usability, but would be a security issue because an attacker can
  easily determine the Passcode length, which makes it easier to for an
  attacker to guess the Passcode. Eg, if I have a 5 digit Passcode set,
  then an attacker need only type '1' and know that the Passcode is
  only five characters. Now, a Passcode isn't strong to begin with and
  an automated attack could rather quickly brute force Passcodes, but we
  shouldn't make it easier for someone manually trying to guess the
  Passcode.

  The passphrase lockscreen prompt correctly allows variable length
  passphrases and requires you to press Enter.

  I suggest moving the 'X' up t the left of '0' and an Enter symbol to
  the rigth of '0'.

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

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

[Touch-packages] [Bug 957922] Re: Thunderbird's messaging menu highlight helps some people but not many

2015-03-25 Thread Matthew Paul Thomas

** Changed in: ayatana-design
   Status: In Progress = Confirmed

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

Title:
  Thunderbird's messaging menu highlight helps some people but not many

Status in Ayatana Design:
  Confirmed
Status in The Messaging Menu:
  Invalid
Status in indicator-messages package in Ubuntu:
  Invalid
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  By default, when new emails arrive in Thunderbird, they *sometimes* highlight 
the messaging menu. As described by Chris Coulson, a message highlights the 
menu if:
  - The message is sent with high-priority OR
  - The message is flagged (by a filter) OR
  - The message is addressed directly to the recipient (eg, not CC) AND the 
message is not low prioirty AND the message wasn't automated AND the message is 
not from a mailing list.

  This is good behavior for some people, but not for others, e.g. ViViD:
  In my personal case, no message received through Thunderbird lacks
  importance. Since I hide the launcher by default, many mails go
  unnoticed for a time and I find myself randomly mousing over the
  launcher to check mails.

  To suit more people, Thunderbird should contain a setting for which
  messages highlight the messaging menu. One option should be to
  highlight messages if they are from one of your contacts.

  This setting needs design, and then proposing (and maybe implementing)
  upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/957922/+subscriptions

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

[Touch-packages] [Bug 1435311] Re: fcitx (the framework) should be seeded in desktop

Maybe a language-selector hack? If the user requests the installation of
some Chinese language, install fcitx-bin (if not already installed)
before calling check-language-support.

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

Title:
  fcitx (the framework) should be seeded in desktop

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  As a result of bug #1430893, check-language-support now pulls fcitx IM
  support for Chinese instead of IBus ditto. However, this is true only
  if the fcitx package is installed.

  Consider these steps:

  * Plain English install - fcitx not installed

  * Install a Chinese language using Language Support, and find that
1. No IM support gets installed and
2. fcitx is not available as an IM framework option.

  I think it would make more sense to have the fcitx package installed
  for all users.

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

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

[Touch-packages] [Bug 1424121] Re: Spotify apparmor=DENIED operation=ptrace

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

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

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

Title:
  Spotify  apparmor=DENIED operation=ptrace

Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  Syslog repeat

  kernel: [  701.861498] type=1400
  audit(1424523171.731:872):apparmor=DENIEDoperation=ptrace
  profile=/optspotify/spotify-client/spotify pid=2670
  comm=Chrome_IOThread requested_mask=trace denied_mask=trace
  peer=/opt/spotify/spotify-client spotify

  This happens when you remove the indicator and modified spotify
  apparmor:

  http://www.webupd8.org/2014/03/how-to-disable-spotify-tray.html

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apparmor 2.8.95~2430-0ubuntu5.1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 21 00:55:29 2015
  InstallationDate: Installed on 2015-02-20 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  ProcEnviron:
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=es_CL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed 
root=UUID=2ff057ee-3a8a-4dd6-97f1-f1b31b832062 ro quiet splash vt.handoff=7
  SourcePackage: apparmor
  Syslog:
   Feb 20 18:45:04 aventino dbus[515]: [system] AppArmor D-Bus mediation is 
enabled
   Feb 20 23:55:55 aventino dbus[661]: apparmor=DENIED 
operation=dbus_method_call  bus=system path=/org/freedesktop/DBus 
interface=org.freedesktop.DBus member=Hello mask=send 
name=org.freedesktop.DBus pid=30179 
profile=/opt/spotify/spotify-client/spotify peer_profile=unconfined
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1435759] Re: Does not produce -doc package

** Changed in: qtfeedback-opensource-src (Ubuntu)
   Status: Triaged = In Progress

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

Title:
  Does not produce -doc package

Status in qtfeedback-opensource-src package in Ubuntu:
  In Progress

Bug description:
  It looks like this should be relatively easy to implement.

  Running the following in the source tree seems to work:

   - qmake; make docs
   - then install the contents of doc/qtfeedback/ into qtfeedback5-doc (or 
whatever else the naming scheme is).

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

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

[Touch-packages] [Bug 1373598] Re: apt-get update fails, hash sum mismatches (trusty)

2015-03-25 Thread mpcore

Same Issue here with http://de.archive.ubuntu.com  . Additionally,  I
also see GPG error for the  Ubuntu Archive Automatic Signing Key. No
problems with other mirrors.

apt-get update
Ign http://de.archive.ubuntu.com trusty InRelease
Ign http://de.archive.ubuntu.com trusty-security InRelease
Ign http://de.archive.ubuntu.com trusty-updates InRelease  
Ign http://de.archive.ubuntu.com trusty-proposed InRelease
Ign http://de.archive.ubuntu.com trusty-backports InRelease
Hit http://de.archive.ubuntu.com trusty Release.gpg
Hit http://de.archive.ubuntu.com trusty-security Release.gpg
Get:1 http://de.archive.ubuntu.com trusty-updates Release.gpg [933 B]
(...)
Get:12 http://de.archive.ubuntu.com trusty-backports/main amd64 Packages [5,536 
B]
Get:13 http://de.archive.ubuntu.com trusty-backports/restricted amd64 Packages 
[28 B]
Get:14 http://de.archive.ubuntu.com trusty-backports/universe amd64 Packages 
[26.2 kB]
Get:15 http://de.archive.ubuntu.com trusty-backports/multiverse amd64 Packages 
[1,245 B]
Get:16 http://de.archive.ubuntu.com trusty-backports/main i386 Packages [5,550 
B]
Get:17 http://de.archive.ubuntu.com trusty-backports/restricted i386 Packages 
[28 B]
Get:18 http://de.archive.ubuntu.com trusty-backports/universe i386 Packages 
[26.3 kB]
Get:19 http://de.archive.ubuntu.com trusty-backports/multiverse i386 Packages 
[1,249 B]
Get:20 http://de.archive.ubuntu.com trusty-backports/main Translation-en [3,233 
B]
Get:21 http://de.archive.ubuntu.com trusty-backports/multiverse Translation-en 
[776 B]
Get:22 http://de.archive.ubuntu.com trusty-backports/restricted Translation-en 
[14 B]
Get:23 http://de.archive.ubuntu.com trusty-backports/universe Translation-en 
[24.3 kB]
Get:24 http://de.archive.ubuntu.com trusty-proposed/main amd64 Packages [148 kB]
Get:25 http://de.archive.ubuntu.com trusty-proposed/restricted amd64 Packages 
[28 B]
Hit http://de.archive.ubuntu.com trusty-proposed/universe amd64 Packages
Get:26 http://de.archive.ubuntu.com trusty-proposed/multiverse amd64 Packages 
[1,134 B]
Get:27 http://de.archive.ubuntu.com trusty-proposed/main i386 Packages [145 kB]
Get:28 http://de.archive.ubuntu.com trusty-proposed/restricted i386 Packages 
[28 B]
Get:29 http://de.archive.ubuntu.com trusty-proposed/multiverse i386 Packages 
[1,133 B]
Fetched 1,226 kB in 53s (22.9 kB/s)
W: GPG error: http://de.archive.ubuntu.com trusty-proposed Release: The 
following signatures were invalid: BADSIG 40976EAF437D05B5 Ubuntu Archive 
Automatic Signing Key ftpmas...@ubuntu.com
W: Failed to fetch 
http://de.archive.ubuntu.com/ubuntu/dists/trusty-updates/main/binary-amd64/Packages
  Hash Sum mismatch

W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/trusty-
updates/main/binary-i386/Packages  Hash Sum mismatch

E: Some index files failed to download. They have been ignored, or old
ones used instead.


# VS.: #


(...)
Get:53 http://de2.archive.ubuntu.com trusty-backports/main Translation-en 
[3,233 B]
Get:54 http://de2.archive.ubuntu.com trusty-backports/multiverse Translation-en 
[776 B]
Get:55 http://de2.archive.ubuntu.com trusty-backports/restricted Translation-en 
[14 B]
Get:56 http://de2.archive.ubuntu.com trusty-backports/universe Translation-en 
[24.3 kB]
(...)
Fetched 22.8 MB in 12s (1,810 kB/s)
Reading package lists... Done


If I remember correctly,  http://de.archive.ubuntu.com  never worked for 
trusty...

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

Title:
  apt-get update fails, hash sum mismatches (trusty)

Status in apt package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed

Bug description:
  1. Release: 
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  2.  not a package. The whole distro is broken.

  3. I always expect apt-get update to work, at least with Ubuntu's own
  repositories.

  4. apt-get update failed, and later apt-get dist upgrade

  
  It started with this when doing a normal apt-get update

  W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/trusty-
  updates/main/source/Sources  Hash Sum mismatch

  W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/trusty-
  updates/main/binary-amd64/Packages  Hash Sum mismatch

  W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/trusty-
  updates/universe/binary-i386/Packages  Hash Sum mismatch

  E: Some index files failed to download. They have been ignored, or old
  ones used instead.

  
  When doing a dist-upgrade, I then got this:
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-3.13.0-36-generic with 1.
  run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
  Failed to process /etc/kernel/postinst.d at 
/var/lib/dpkg/info/linux-image-extra-3.13.0-36-generic.postinst line 1025.
  No apport report

[Touch-packages] [Bug 1435685] Re: [Asus X751MD] Double mouse cursor

2015-03-25 Thread Christopher M. Penalver

lecolo:
my laptop is this one...

Just to advise, your laptop model is already in the Bug Description.

There was mouse-bug using normal free driver, for intel HD (Intel
Pentium Quad Core N3540 Bay Trail-M (2.16 GHz, 4 cœurs, TDP 7.5W)
Choosing the verified Nvidia driver in the (x)ubuntu repository : no
bug.

Ok. Does the issue occur in http://cdimage.ubuntu.com/daily-
live/current/ ?

I didn't try the unverified more recent Nvidia one.

It's not necessary to test this, as we've already narrowed down where
the issue is.

Also, this report is scoped to the double mouse cursor issue, not how your 
touchpad doesn't work. If you have an issue with your touchpad, it would help 
immensely if you filed a new report via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to the new report.

** Summary changed:

- double mouse cursor, 64bit, fresh install
+ [Asus X751MD] Double mouse cursor

** Description changed:

- see here 
- https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1393169
- and
- http://forum.ubuntu-fr.org/viewtopic.php?id=1761131
+ I have a double mouse cursor.
  
- may apeared after resizing folder on Xubuntu?
+ WORKAROUND: Installed nvidia driver from Ubuntu repository.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7
  Uname: Linux 3.16.0-33-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Mar 24 07:51:42 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
-  Intel Corporation ValleyView Gen7 [8086:0f31] (rev 0e) (prog-if 00 [VGA 
controller])
-Subsystem: ASUSTeK Computer Inc. Device [1043:16dd]
+  Intel Corporation ValleyView Gen7 [8086:0f31] (rev 0e) (prog-if 00 [VGA 
controller])
+    Subsystem: ASUSTeK Computer Inc. Device [1043:16dd]
  InstallationDate: Installed on 2015-03-22 (1 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS Trusty Tahr - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. X751MD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic.efi.signed 
root=UUID=e919445c-9bea-469f-a036-22c3f5fb6dbb ro splash quiet
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X751MD.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X751MD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX751MD.208:bd02/06/2015:svnASUSTeKCOMPUTERINC.:pnX751MD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX751MD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X751MD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  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: Tue Mar 24 07:49:15 2015
  xserver.configfile: default
  xserver.errors:
-  Failed to load module nvidia (module does not exist, 0)
-  Failed to load module nvidia (module does not exist, 0)
-  NOUVEAU(G0): [XvMC] Failed to initialize extension.
+  Failed to load module nvidia (module does not exist, 0)
+  Failed to load module nvidia (module does not exist, 0)
+  NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
-  product id5928 
-  vendor CMN
+  product id5928
+  vendor CMN
  xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

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

Title:
  [Asus X751MD] Double mouse cursor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I have a double mouse cursor.

  WORKAROUND: Installed nvidia driver from Ubuntu repository.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7
  Uname: Linux 3.16.0-33-generic x86_64

[Touch-packages] [Bug 1433232] Re: compiz crashed with SIGSEGV in strlen()

2015-03-25 Thread Andrea Azzarone

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

** Information type changed from Private to Public

** This bug has been marked a duplicate of bug 1047517
   compiz crashed with SIGSEGV in g_mount_spec_to_dbus_with_path() ... from 
unity::IconLoader::Impl::IconLoaderTask::LoaderJobFunc()

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

Title:
  compiz crashed with SIGSEGV in strlen()

Status in Unity:
  New
Status in unity package in Ubuntu:
  New

Bug description:
  crashed unity while trying to open/work with filezilla - please let me
  know if you need anymore details/help debugging

  thank you,

  darran

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.1+15.04.20150227-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Tue Mar 17 12:23:30 2015
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2012-09-16 (911 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120905.2)
  ProcCmdline: compiz
  SegvAnalysis:
   Segfault happened at: 0x7fd178ab52aa strlen+42:movdqu (%rax),%xmm12
   PC (0x7fd178ab52aa) ok
   source (%rax) (0x0241) not located in a known VMA region (needed 
readable region)!
   destination %xmm12 ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   strlen () at ../sysdeps/x86_64/strlen.S:106
   g_variant_new_bytestring () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_mount_spec_to_dbus_with_path () from 
/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so
   ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
   ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
  Title: compiz crashed with SIGSEGV in strlen()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom debian-tor dip libvirtd lpadmin plugdev 
sambashare sudo

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

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

[Touch-packages] [Bug 1435035] Re: No CopyPaste for wifi key possible .

2015-03-25 Thread Sebastien Bacher

that entry is provided by the indicator backend

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

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

Title:
  No CopyPaste for wifi key possible .

Status in indicator-network package in Ubuntu:
  New

Bug description:
  Ubuntu 14.10 (r20)

  There is no chance to paste a long wpa key in the passphrase textfield for a 
new AP.
  Thats bad if you have a long passphrase like 63 signs.

  If it has sth. to do with security, fine. But then remove the Show Key
  Option too;-)

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

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

[Touch-packages] [Bug 1436328] Re: FFe apport-kde qt5 port

2015-03-25 Thread Jonathan Riddell

good with me but should get apport maintainers ack

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

Title:
  FFe apport-kde qt5 port

Status in apport package in Ubuntu:
  New

Bug description:
  https://code.launchpad.net/~kubuntu-packagers/apport/qt5/+merge/254082

  integrating the qt5 port would allow kubuntu to attempt dropping
  python-kde4  from the ISO reducing the oversizing quite a bit

  test by Jonathan Riddell and me and works very well.

  functionally nothing changed as far as the UI is concerned and under
  the hood all the happened was an almost straight qt4-qt5 port along
  with replacing now obsolete kde dependencies with their qt5
  counterpart

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

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

[Touch-packages] [Bug 1436328] [NEW] FFe apport-kde qt5 port

2015-03-25 Thread Harald Sitter

Public bug reported:

https://code.launchpad.net/~kubuntu-packagers/apport/qt5/+merge/254082

integrating the qt5 port would allow kubuntu to attempt dropping python-
kde4  from the ISO reducing the oversizing quite a bit

test by Jonathan Riddell and me and works very well.

functionally nothing changed as far as the UI is concerned and under the
hood all the happened was an almost straight qt4-qt5 port along with
replacing now obsolete kde dependencies with their qt5 counterpart

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

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

Title:
  FFe apport-kde qt5 port

Status in apport package in Ubuntu:
  New

Bug description:
  https://code.launchpad.net/~kubuntu-packagers/apport/qt5/+merge/254082

  integrating the qt5 port would allow kubuntu to attempt dropping
  python-kde4  from the ISO reducing the oversizing quite a bit

  test by Jonathan Riddell and me and works very well.

  functionally nothing changed as far as the UI is concerned and under
  the hood all the happened was an almost straight qt4-qt5 port along
  with replacing now obsolete kde dependencies with their qt5
  counterpart

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

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

[Touch-packages] [Bug 1436312] Re: Uppercase URL causes web search

** Branch linked: lp:~osomon/webbrowser-app/rewrite-uppercase-scheme

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

Title:
  Uppercase URL causes web search

Status in Web Browser App:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Using krilin build 20.

  In the browser, I enter the URL HTTP://www.ubuntu.com.

  Expected behaviour: fixes case, takes me to Ubuntu website.

  Actual behaviour: does a Google search for HTTP://www.ubuntu.com.

  Impact: it's awkward to scan QR codes that give me URLs in all caps,
  which is how I discovered the issue.

  Workaround: edit the HTTP to http manually. But after the Google
  search, editing the URL is awkward because the URL changes to one
  suitable for the Google search.

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

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

[Touch-packages] [Bug 1436312] Re: Uppercase URL causes web search

2015-03-25 Thread Olivier Tilloy

** Changed in: webbrowser-app
 Assignee: (unassigned) = Olivier Tilloy (osomon)

** Changed in: webbrowser-app (Ubuntu)
 Assignee: (unassigned) = Olivier Tilloy (osomon)

** Changed in: webbrowser-app
   Status: Confirmed = In Progress

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

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

Title:
  Uppercase URL causes web search

Status in Web Browser App:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Using krilin build 20.

  In the browser, I enter the URL HTTP://www.ubuntu.com.

  Expected behaviour: fixes case, takes me to Ubuntu website.

  Actual behaviour: does a Google search for HTTP://www.ubuntu.com.

  Impact: it's awkward to scan QR codes that give me URLs in all caps,
  which is how I discovered the issue.

  Workaround: edit the HTTP to http manually. But after the Google
  search, editing the URL is awkward because the URL changes to one
  suitable for the Google search.

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

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

[Touch-packages] [Bug 1436235] Re: It should be possible to click on the contact URL and have a web page open

2015-03-25 Thread Alejandro J. Cura

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

Thanks for the bug report, I'm marking this as a duplicate of an
existing one.

** This bug has been marked a duplicate of bug 1350993
   Support link should be clickable, app preview shows mailto links with 
mailto text

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

Title:
  It should be possible to click on the contact URL and have a web page
  open

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

Bug description:
  I've found an issue in a click package, and I want to report it to the
  publisher/creator. I find the package name, scroll down to Contact
  and press on the URL. No response. I long press, trying to provoke a
  copy action. No response.

  Ideally, this should either be a hyperlink or if not, something which
  is copy-and-paste-able.

  This is with the BQ Ubuntu Phone, running 14.10 (OS Build 20) Ubuntu
  Image Part: 20150312

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

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

[Touch-packages] [Bug 1350993] Re: Support link should be clickable, app preview shows mailto links with mailto text

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

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

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

Title:
  Support link should be clickable, app preview shows mailto links with
  mailto text

Status in Ubuntu UX bugs:
  Triaged
Status in unity-scope-click package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  When uploading an app to the store we're given a field to put a
  support link in. It's recommended to put an http or mailto link in. I
  have put mailto: links in mine. With the latest click scope I now see
  some details about the app, and the support link actually says
  mailto:a...@popey.com; when it probably should be clickable whether
  it's a mailto link or an http* link.

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

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

[Touch-packages] [Bug 1425991] Re: Networks I have never connected to should be confined to the More Networks folder

as Shahbaz points out, most of the time, Ubuntu will connect
automatically to one of the networks you have connected to before. So
most of the time, if you open the menu to connect to a Wi-Fi network, it
is to connect to a network that you have *not* connected to before. It
would be counterproductive, then, to show by default only networks that
you *have* connected to before.

No, this is not accurate.
1) there are lots of users who do not want networks connecting automatically, 
so they manually select the network they want.
2) even if Ubuntu is set to automatically connect to networks, if there are 
more than one network in range that a user regularly connects to, he/she HAS to 
manually select the network because Ubuntu does not know which network to 
automatically connect to. Except the way Ubuntu currently works, the user is 
forced to wade through unknown networks to single out the network/s they have 
previously connected to in the past.
3) there are other reasons to access the network-indicator besides connecting 
to a network. And having NEVER-USED, NEVER-WILL-USE networks taking up space in 
the drop-down is not a smart design choice
4) there is no good reason NOT to confine networks you have never connected to 
the More networks folder or an Unknown networks folder. Demarcating 
networks like this makes it easier on the user because it helps identify to the 
user which networks they have and have-not connected to in the past. And it 
allows simplified presentation of the network-indicator menu; it also aides 
user memory of what networks they have connected to in the past without forcing 
them to visit the Edit Connections section of the network-indicator menu. 
Networks are already demarcated into the More networks folder. But there is 
little logic to why they are put in the folder. Add some logic and 
understanding to the placement of networks in this folder, logic that the User 
immediately understands.

Where you have previously connected to more than one of the networks
in range, the menu prioritizes showing these ones, ahead of showing
networks that you have not connected to before. After that, it
prioritizes the strongest other networks, minimizing the probability
that the network you want isn't at the top level.
https://wiki.ubuntu.com/Networking#wi-fi-menu

No, this is untrue. I regularly have to fish out the network I want at
the bottom of the network-indicator dropdown list because other networks
are placed above it in the list (networks I have never connected to and
never will connect to).

for example, you may not remember whether you used the Wi-Fi the last
time you were at this particular cafe/airport/etc, so you may not
remember whether the network is known or not. And having two lists of
networks, separated by other functional items, would be rather
inelegant.

What? You do not understand what I am reporting as the bug. If you fix
the bug I am reporting, the user would immediately know whether he/she
used the network in the past because Ubuntu would display it in the
network-indicator dropdown. The network was connected to before, so it
would show up in the network-indicator list. If the network has NEVER
been connected to before, it will only show in the More networks
folder or the Unknown networks folder.

Having networks list in the network-indicator list that the user will
NEVER connect to and has NEVER connected to in the past is what is
inelegant and screws with the user's memory. In my proposal, the user
does not have to remember whether the network is known or not. Ubuntu
tells the user the network is known (or connected to before) because it
is not listing it in the Unknown networks folder.

Let me restate what you need to do to fix this problem: Networks that
have never been connected to in the past should not directly display in
the network-indicator drop-down. Instead, they should be confined to a
folder that says Unknown Networks. If a connection has been made to
the network in the past, then the network should directly display in the
network-indicator drop-down.

Part of adapting the phone Wi-Fi settings to the PC will, I hope, be
introducing the ability to arrange previous networks in order of
preference. Once that is done, I don't think there will be any point in
also letting you confine/blacklist networks.

This bug reports the inelegant and inefficient organziation and handling
of wifi networks that currently exists in Ubuntu. It should be fixed as
soon as possible. Currently, every time a user wants to connect to a
network, he/she has to hunt through a list of networks that perpetually
show but that the user will NEVER EVER connect to. What sense does this
make to force this on Ubuntu users? Every user on earth will immediately
understand to look in the More Networks folder or a folder called
Unknown Networks for networks that they have not connected to in the
past. And then once the user has connected to a network that network
will display in the

[Touch-packages] [Bug 1406034] Re: XPS 15 9530, Realtek ALC3661, Black Headphone Out, Left Background noise

2015-03-25 Thread Raymond

seem xps 15  9530 specs and quick startup guide does not mention that
the combo jack can be used as mic jack, why do driver create headphone
mic ?

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

Title:
   XPS 15 9530, Realtek ALC3661, Black Headphone Out, Left  Background
  noise

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When listening with headphones or a headset, there's a constant
  background noise with a hiss i the left ear and 'electronic warbling'
  in the rigt ear.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dave   2547 F pulseaudio
   /dev/snd/controlC0:  dave   2547 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Dec 28 00:52:28 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-11-30 (392 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: High background noise, or volume is too low
  Title: [XPS 15 9530, Realtek ALC3661, Black Headphone Out, Left] Background 
noise or low volume
  UpgradeStatus: Upgraded to utopic on 2014-12-21 (6 days ago)
  dmi.bios.date: 09/17/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: XPS 15 9530
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd09/17/2013:svnDellInc.:pnXPS159530:pvrA00:rvnDellInc.:rnXPS159530:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: XPS 15 9530
  dmi.product.version: A00
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1436351] [NEW] icon does not change in silent mode

2015-03-25 Thread Jamie Strandboge

Public bug reported:

If I pull down on the indicator-network and check 'Silent Mode', the
icon does not change.

$ system-image-cli -i
current build number: 214
device name: mako
channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
last update: 2015-03-11 22:07:13
version version: 214
version ubuntu: 20150312
version device: 20150116
version custom: mako-1.1

Bug 1367818 seems related, but is marked Fix Released.

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

** Description changed:

  If I pull down on the indicator-network and check 'Silent Mode', the
  icon does not change.
  
  $ system-image-cli -i
  current build number: 214
  device name: mako
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2015-03-11 22:07:13
  version version: 214
  version ubuntu: 20150312
  version device: 20150116
  version custom: mako-1.1
  
- Bug 139 and bug 1367818 seem related, but are marked Fix Released.
+ Bug 1367818 seems related, but is marked Fix Released.

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

Title:
  icon does not change in silent mode

Status in indicator-sound package in Ubuntu:
  New

Bug description:
  If I pull down on the indicator-network and check 'Silent Mode', the
  icon does not change.

  $ system-image-cli -i
  current build number: 214
  device name: mako
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2015-03-11 22:07:13
  version version: 214
  version ubuntu: 20150312
  version device: 20150116
  version custom: mako-1.1

  Bug 1367818 seems related, but is marked Fix Released.

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

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

[Touch-packages] [Bug 1286596] Re: mediascanner-service-2.0 crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()

2015-03-25 Thread Christopher

Occurred again in 15.04 (Unity).

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

Title:
  mediascanner-service-2.0 crashed with SIGABRT in
  __gnu_cxx::__verbose_terminate_handler()

Status in mediascanner2 package in Ubuntu:
  Fix Released

Bug description:
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04
  mediascenner2.0 0.99+14.04.20140220-0ubuntu1

  Actually, I don't know how to reproduce this crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: mediascanner2.0 0.99+14.04.20140220-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar  1 20:02:27 2014
  ExecutablePath: /usr/bin/mediascanner-service-2.0
  InstallationDate: Installed on 2014-01-29 (30 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140128)
  ProcCmdline: mediascanner-service-2.0
  Signal: 6
  SourcePackage: mediascanner2
  StacktraceTop:
   __gnu_cxx::__verbose_terminate_handler() () from 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   mediascanner::SubtreeWatcher::addDir(std::string const) ()
  Title: mediascanner-service-2.0 crashed with SIGABRT in 
__gnu_cxx::__verbose_terminate_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1320461] Re: keybindings do not work when opening multiple files

I can confirm this issue (the forgetting of an unbind) in version 2.2.6.
It is no longer present in 2.4.0, which was recently released.  It is,
however, not an easy patch to backport.  So with a little patience...
you will be freed from this annoyance in a next version of Ubuntu.

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

Title:
  keybindings do not work when opening multiple files

Status in nano package in Ubuntu:
  New

Bug description:
  I think I have found a bug. At least weird behaviour.

  I set my ~/.nanorc to unbind ^J  main because I
  find it very annoying when it mangles my text when I
  accidentally press Ctrl+Enter.  

  
  This setup works well for me when I use nano to open  
  
  one file, i.e. nano foo.tex. However, when I open two files,
  i.e. nano foo.tex bar.tex, it works for the first file only.
  That is, when I quit the first instance with Ctrl+X and when nano 
  
  has loaded the second file, my nanorc does not seem to be 
  
  respected anymore. I can press Ctrl+Enter and it mangles my text.
  I hope you find this useful and are able to reproduce this issue. 
  

  
  nano --version
  
   GNU nano version 2.2.6 (compiled 14:12:08, Oct  1 2012)  
  
   (C) 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007,
  
   2008, 2009 Free Software Foundation, Inc.
  
   E-mail: n...@nano-editor.org   Web: http://www.nano-editor.org/  
  
   Compiled options: --disable-wrapping-as-root --enable-color --enable-extra 
--en
  able-multibuffer --enable-nanorc --enable-utf8

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: nano 2.2.6-1ubuntu1
  Uname: Linux 3.14.0-031400rc4-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Sat May 17 12:21:54 2014
  InstallationDate: Installed on 2014-01-22 (114 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release amd64 
(20131017)
  MarkForUpload: True
  SourcePackage: nano
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.nanorc: [modified]
  mtime.conffile..etc.nanorc: 2014-02-26T11:29:03.194042

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

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

[Touch-packages] [Bug 264144] Re: NetworkManager VPN configuration export does not work

2015-03-25 Thread fenixk19

Confirming the issue on Ubuntu 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/264144

Title:
  NetworkManager VPN configuration export does not work

Status in NetworkManager:
  Invalid
Status in Network management framework (OpenVPN plugin):
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in network-manager-openvpn package in Ubuntu:
  Fix Released
Status in network-manager-pptp package in Ubuntu:
  Triaged

Bug description:
  Intrepid,
  network-manager: 0.7~~svn20080818t061112+eni0-0ubuntu1

  Subject says it. To reproduce:
  1. Configure VPN connection
  2. Try to Export it to a file

  As a result I got cryptic error message dialog:
  ===
  Cannot export VPN connection

  The VPN connection 'vpn_test' could not be exported to vpn_test
  (pptp).conf.

  Error: unknown error.
  ===

  Expected behavior:
  Configuration saved to a file.

  =
  WORKAROUND
  The configuration is saved in a file in 
/etc/NetworkManager/system-connections/
  that has the same name as the connection.
  This file can be examined with a text editor and/or copied around to other 
machines.
  source: 
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/264144/comments/27
  WORKAROUND
  =

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

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

[Touch-packages] [Bug 1434142] Re: in developer mode, there should be a shutdown option to boot into the bootloader

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

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

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

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

Title:
  in developer mode, there should be a shutdown option to boot into the
  bootloader

Status in Ubuntu UX bugs:
  Triaged
Status in unity8 package in Ubuntu:
  New

Bug description:
  when pressing the power button in Ubuntu Touch, the user has the
  option to Cancel, Power Off, or Reboot. If the user has enabled
  Developer Mode, then there should be an option to boot into
  recover/bootloader

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

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

[Touch-packages] [Bug 1268097] Re: Can't set user-supplied ring tone

** Changed in: ubuntu-ux
 Assignee: (unassigned) = Matthew Paul Thomas (mpt)

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

** Summary changed:

- Can't set user-supplied ring tone
+ [System settings] Can't set user-supplied ring tone

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

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

Title:
  [System settings] Can't set user-supplied ring tone

Status in Ubuntu UX bugs:
  Triaged
Status in content-hub package in Ubuntu:
  Triaged
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  AFAICS I can't set a custom ring tone without using a writable image.
  (http://askubuntu.com/questions/372759/ringtones-in-ubuntu-touch)

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

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

[Touch-packages] [Bug 1436162] Re: [pulsesink] abort at pthread_mutex_unlock(m-mutex) == 0' failed at pulsecore/mutex-posix.c:118, function pa_mutex_unlock() with libc 2.21

2015-03-25 Thread Ricardo Salveti

So this issue is a combination of the following patches:
https://sourceware.org/git/?p=glibc.git;a=commit;h=47c5adebd2c864a098c3af66e61e1147dc3cf0b4
https://sourceware.org/git/?p=glibc.git;a=commit;h=03d41216fe09fc71a2750946af8fe2892bf4feb5

Basically the main problem is that futex_atomic_cmpxchg_inatomic got
disabled, even though we have that well supported in our kernels.

I just did another build (in canonical-arm-dev) including the patch bellow, and 
with that I'm unable to reproduce this bug:
Index: glibc-2.21/sysdeps/unix/sysv/linux/arm/kernel-features.h
===
--- glibc-2.21.orig/sysdeps/unix/sysv/linux/arm/kernel-features.h
+++ glibc-2.21/sysdeps/unix/sysv/linux/arm/kernel-features.h
@@ -37,8 +37,10 @@
 /* The ARM kernel before 3.14.3 may or may not support
futex_atomic_cmpxchg_inatomic, depending on kernel
configuration.  */
+/*
 #if __LINUX_KERNEL_VERSION  0x030E03
 # undef __ASSUME_FUTEX_LOCK_PI
 # undef __ASSUME_REQUEUE_PI
 # undef __ASSUME_SET_ROBUST_LIST
 #endif
+*/

** Changed in: gst-plugins-good1.0 (Ubuntu)
   Status: Confirmed = Invalid

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed = Invalid

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

Title:
  [pulsesink] abort at pthread_mutex_unlock(m-mutex) == 0' failed at
  pulsecore/mutex-posix.c:118, function pa_mutex_unlock() with libc 2.21

Status in glibc package in Ubuntu:
  Confirmed
Status in gst-plugins-good1.0 package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  current build number: 146
  device name: m75
  channel: ubuntu-touch/vivid-proposed
  last update: 2015-03-24 13:57:03
  version version: 146

  After libc 2.21 landed, pulsesink fails constantly when pausing or
  seeking the active pipeline.

  Abort message:
  Assertion 'pthread_mutex_unlock(m-mutex) == 0' failed at 
pulsecore/mutex-posix.c:118, function pa_mutex_unlock(). Aborting.

  This is basically happens when it tries to unlock a mutex that is
  already unlocked.

  This issue doesn't happen with libc 2.19.

  To reproduce the issue:
  GST_DEBUG=*pulse*:5 gst-launch-1.0 playbin uri=file:///tmp/foobar.mp3

  Then when playing, just hit control+c, which will then pause the
  pipeline, causing the crash. The crash happens with most of the times
  you pause or seek the pipeline.

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

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

[Touch-packages] [Bug 1425991] Re: Networks I have never connected to should be confined to an Unknown Networks folder

** Description changed:

  When a user clicks the network manager indicator, a dropdown appears and
  lists wifi networks. This menu should NOT display networks that the user
  has never connected to. Networks the user has never connected to should
- only display in the More networks folder. At a mininum, the user
- should be given the ability to confine unwanted networks in the More
- networks folder.
+ only display in a folder called Unknown Networks. At a mininum, the
+ user should be given the ability to prevent networks from cluttering up
+ the indicator menu.
  
  It is an unproductive design choice to force users to have to wade
  through networks they have never connected to (networks they will never
- connect to) in their menu. Numerous reasons exist why a user will not
- use the Auto-Connect setting for wireless networks. So it makes sense
- and is more efficient to have the menu only display the networks the
- user makes active use of and no more.
+ connect to) in their menu. Even if a user makes use of the Auto-Connect
+ setting for wireless networks, only displaying known networks in the
+ indicator dropdown allows a visual reference of available networks the
+ user can connect to. If the user is interested in connecting to an
+ unknown (or never before connected-to network), the user can explore a
+ folder that contains such networks. It makes sense and is more efficient
+ to have the menu only display the networks the user makes active use of
+ and no more.
  
  When I click on the Network Manager Indicator and select Edit
  Connections and then look under the Wifi heading, only a couple
  networks appear. So why do 5 or more networks (networks I have never
  connected to, networks I never will connect to) perpetually show in the
  Network Indicator menu? They should not be displayed like they are. They
- should be confined to the More networks folder. Alternatively, there
- should be a way to manually confine/sandbox unwanted networks to this
- folder so they no longer display in the dropdown menu.
+ should be confined to a folder called Unknown Networks.
  
  In the interest of providing a visual example of what I am talking about, 
here is a picture of some networks I would like to hide/remove from my Network 
Indicator menu.
  http://a.pomf.se/fdqlnn.png

** Description changed:

  When a user clicks the network manager indicator, a dropdown appears and
  lists wifi networks. This menu should NOT display networks that the user
  has never connected to. Networks the user has never connected to should
  only display in a folder called Unknown Networks. At a mininum, the
  user should be given the ability to prevent networks from cluttering up
  the indicator menu.
  
  It is an unproductive design choice to force users to have to wade
  through networks they have never connected to (networks they will never
  connect to) in their menu. Even if a user makes use of the Auto-Connect
  setting for wireless networks, only displaying known networks in the
  indicator dropdown allows a visual reference of available networks the
- user can connect to. If the user is interested in connecting to an
- unknown (or never before connected-to network), the user can explore a
- folder that contains such networks. It makes sense and is more efficient
- to have the menu only display the networks the user makes active use of
- and no more.
+ user can connect to. If the user is in the vicinity of a free network or
+ at a friend's house and has the password to a network he/she has never
+ connected to before, this network would be unknown (because it has never
+ been connected to before). So the user would browse the Unknown
+ Networks folder to identify the SSID. Once connected to, from then on
+ the network would directly display in the Network-Indicator dropdown
+ list. It makes sense and is more efficient to have the menu only display
+ the networks the user makes active use of and no more.
  
  When I click on the Network Manager Indicator and select Edit
  Connections and then look under the Wifi heading, only a couple
  networks appear. So why do 5 or more networks (networks I have never
  connected to, networks I never will connect to) perpetually show in the
  Network Indicator menu? They should not be displayed like they are. They
  should be confined to a folder called Unknown Networks.
  
  In the interest of providing a visual example of what I am talking about, 
here is a picture of some networks I would like to hide/remove from my Network 
Indicator menu.
  http://a.pomf.se/fdqlnn.png

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

Title:
  Networks I have never connected to should be confined to an Unknown
  Networks folder

Status in indicator-network package in Ubuntu:
  New

Bug description:
  When a user clicks the network manager indicator, a

[Touch-packages] [Bug 1286276] Re: Lock screen whines that No data sources available on first use

2015-03-25 Thread Alan Bell

I did waste 10 minutes or so eagerly hunting around for data sources to
enable due to this message. It sounds like a call to action, you should
totally enable some data sources to see awesome stuff here but it
isn't. It should say nothing, or something that gives you a clue as to
what you are expected to do about it.

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

Title:
  Lock screen whines that No data sources available on first use

Status in libusermetrics package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 14.04 r188, Ubuntu 14.10 r203

  1. Flash the phone.
  2. Lock the phone.
  3. Wake up the phone.

  What you see: No data sources available

  What you should see: Something less miserable.

  As someone who's just started using the phone, I probably have no idea
  that the lock screen tries to show me statistics of my usage or
  whatever. And even if I do know, I probably don't care. Why, then, is
  the phone complaining to me about its failure? What am I supposed to
  do about it?

  A simple solution would be to show no text at all in this situation.

  This is not a duplicate of bug 1339002, because stats on the welcome
  screen are on by default. However, fixing that bug might fix this bug
  too.

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

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

[Touch-packages] [Bug 1425991] Re: Networks I have never connected to should be confined to an Unknown Networks folder

@ James Anslow, no because it's not signal strength that defines the
significance of the network to the user. The user is making connection
decisions based on the identity of the network. Even in a context where
a user is trying to select between several free networks, signal
strength may or may not be an important consideration. Personally, I
value my appraisal of the trust worthiness of the network over signal
strength.

And signal strength is a non-factor in a trusted context, for example
your home. The neighbors may be blasting their WAP at max strength and
you have reduced your WAP's strength because you are in a small
apartment or something. So your network would appear at the bottom of
the list, being crowded out by the stronger signals. Yet you have never
connected to your neighbors' networks and you likely never will. So why
should these networks display perpetually in a regular-use area of
your menu?

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

Title:
  Networks I have never connected to should be confined to an Unknown
  Networks folder

Status in indicator-network package in Ubuntu:
  New

Bug description:
  When a user clicks the network manager indicator, a dropdown appears
  and lists wifi networks. This menu should NOT display networks that
  the user has never connected to. Networks the user has never connected
  to should only display in a folder called Unknown Networks. At a
  mininum, the user should be given the ability to prevent networks from
  cluttering up the indicator menu.

  It is an unproductive design choice to force users to have to wade
  through networks they have never connected to (networks they will
  never connect to) in their menu. Even if a user makes use of the Auto-
  Connect setting for wireless networks, only displaying known networks
  in the indicator dropdown allows a visual reference of available
  networks the user can connect to. If the user is in the vicinity of a
  free network or at a friend's house and has the password to a network
  he/she has never connected to before, this network would be unknown
  (because it has never been connected to before). So the user would
  browse the Unknown Networks folder to identify the SSID. Once
  connected to, from then on the network would directly display in the
  Network-Indicator dropdown list. It makes sense and is more efficient
  to have the menu only display the networks the user makes active use
  of and no more.

  When I click on the Network Manager Indicator and select Edit
  Connections and then look under the Wifi heading, only a couple
  networks appear. So why do 5 or more networks (networks I have never
  connected to, networks I never will connect to) perpetually show in
  the Network Indicator menu? They should not be displayed like they
  are. They should be confined to a folder called Unknown Networks.

  In the interest of providing a visual example of what I am talking about, 
here is a picture of some networks I would like to hide/remove from my Network 
Indicator menu.
  http://a.pomf.se/fdqlnn.png

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

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

[Touch-packages] [Bug 1426559] Re: [Shell] Bring the HUD back to Unity 8

** Changed in: ubuntu-ux
 Assignee: Magdalena Mirowicz (magdalena-mirowicz) = (unassigned)

** Changed in: ubuntu-ux
 Assignee: (unassigned) = Benjamin Keyser (bjkeyser)

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

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

Title:
  [Shell] Bring the HUD back to Unity 8

Status in Ubuntu UX bugs:
  Triaged
Status in unity8 package in Ubuntu:
  New

Bug description:
  One of the most innovative, useful, and wildly popular features
  introduced into Unity 7 was the HUD. Unity 8 currently does not have
  it.

  When Unity 8 was started, we had a way of accessing the HUD with a
  long-swipe from the bottom edge. However, the API to use it was late
  in being added to the SDK, and changed in incompatible ways after it
  was available, and as a result only a few apps (including one of my
  own) had taken advantage of it. Moreover user testing showed that the
  swipe-up activation was not easily discover-able by users.

  When the toolbar/header was redesigned and the bottom-edge gesture
  given to app developers, the way of accessing the HUD was removed, and
  the API was removed before the first supported API freeze.

  Before switching to Unity 8 on the desktop we will need to re-
  introduce the HUD into Unity, to avoid a feature regression that many
  have come to expect and appreciate. Moreover, we should re-introduce
  it on the phone so that apps can once again start taking advantage of
  it, so we can learn how to provide new use cases and user interactions
  for phone/tablet apps.

  In order to match, as much as possible, the Unity 7 way of accessing
  the HUD, my recommendation would be to implement it like an Indicator,
  but always on the far left of the panel. Then it would be touch-
  accessible with a swipe down from the top, or switchable from within
  the drop-down of another indicator, placing it at the same screen
  position as it is on the Unity 7 desktop. Placing the window title or
  simple Menu in that location of the panel (or switching between
  them, depending on available space) would aid in discovery of the
  feature.

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

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

[Touch-packages] [Bug 1361131] Re: constantly flashing bright green while typing

If the trailing-whitespace highlighting annoys you, you can edit
/usr/share/nano/sh.nanorc and remove or comment out the line that says:
color ,green [[:space:]]+$.  Problem solved.  (You will then probably
want to do the same for the other *.nanorc files there.)

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

Title:
  constantly flashing bright green while typing

Status in nano package in Ubuntu:
  New

Bug description:
  While editing a shell script (.sh file) nano colours trailing spaces
  bright green.

  It also considers spaces that have just been typed to be trailing
  spaces.

  This results in constant flashing bright green while typing, which is
  both distracting and annoying.

  It's at its most ridiculous when typing comments (for which trailing
  whitespace is obviously completely irrelevant), but is also irritating
  any time you happen to look at what you're typing. Which for me is, as
  it happens, all the time.

  Ideal solution: only display trailing whitespace if the user is not,
  you know, still typing on that line, with the cursor right there.

  Easy solution: just shut up about the damn spaces already.

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

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

[Touch-packages] [Bug 1425991] Re: Networks I have never connected to should be confined to an Unknown Networks folder

2015-03-25 Thread James Anslow

Wouldn't it make more sense to simply organise network names by the
access points' signal strength, descending?

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

Title:
  Networks I have never connected to should be confined to an Unknown
  Networks folder

Status in indicator-network package in Ubuntu:
  New

Bug description:
  When a user clicks the network manager indicator, a dropdown appears
  and lists wifi networks. This menu should NOT display networks that
  the user has never connected to. Networks the user has never connected
  to should only display in a folder called Unknown Networks. At a
  mininum, the user should be given the ability to prevent networks from
  cluttering up the indicator menu.

  It is an unproductive design choice to force users to have to wade
  through networks they have never connected to (networks they will
  never connect to) in their menu. Even if a user makes use of the Auto-
  Connect setting for wireless networks, only displaying known networks
  in the indicator dropdown allows a visual reference of available
  networks the user can connect to. If the user is in the vicinity of a
  free network or at a friend's house and has the password to a network
  he/she has never connected to before, this network would be unknown
  (because it has never been connected to before). So the user would
  browse the Unknown Networks folder to identify the SSID. Once
  connected to, from then on the network would directly display in the
  Network-Indicator dropdown list. It makes sense and is more efficient
  to have the menu only display the networks the user makes active use
  of and no more.

  When I click on the Network Manager Indicator and select Edit
  Connections and then look under the Wifi heading, only a couple
  networks appear. So why do 5 or more networks (networks I have never
  connected to, networks I never will connect to) perpetually show in
  the Network Indicator menu? They should not be displayed like they
  are. They should be confined to a folder called Unknown Networks.

  In the interest of providing a visual example of what I am talking about, 
here is a picture of some networks I would like to hide/remove from my Network 
Indicator menu.
  http://a.pomf.se/fdqlnn.png

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

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

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

All the failure traces seem to be stating that autopilot wouldn't be
able to launch the application. In case of eg address-book-app once a
test fails, all subsequent tests fail too. In case of eg UITK, it's just
that random tests fail.

Here's a simplified test case:

while [ 1 ] ; do phablet-test-run
ubuntuuitoolkit.tests.custom_proxy_objects.test_header.SectionsTestCase.test_select_sections_with_sections_disabled
; done

When the failure happens, the application seems to start fine, but
autopilot thinks it did not. After waiting for some while (~38 seconds
as opposed to ~6 seconds on successful run) it errors out.

Without silo 018 the above test case never fails.

** Attachment added: testfail.txt
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1421009/+attachment/4355569/+files/testfail.txt

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

Title:
  unity8 sometimes hangs on boot

Status in autopilot package in Ubuntu:
  New
Status in libusermetrics package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  The following gdbus call is failing with a Error: Timeout was
  reached message:

  gdbus call --session --dest com.canonical.UnityGreeter --object-path /
  --method org.freedesktop.DBus.Properties.Get
  com.canonical.UnityGreeter IsActive

  
  This is being seen on krillin devices starting with image 106 from 
ubuntu-touch/devel-proposed. It doesn't happen every time, so far today, I've 
seen it 3 times from about 12 tests. On the most recent failure, I grabbed a 
console and tried repeatedly to run the command from the shell, even after 2 
hours the timeout was still being returned (after about 28 seconds).

  A copy of ~/.cache/upstart/unity8.log is here:
  http://paste.ubuntu.com/10179482/

  I have 3 test cases where the problem was observed:
  http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-qtchooser/1/console
  
http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-gsettings-ubuntu-touch-schemas/1/console
  http://d-jenkins.ubuntu-ci:8080/job/fjg-boottest/3/console

  In all cases, the test is using adt-run (from autopkgtest) to drive a
  test on the phone device. adt-run uses the above gdbus call to
  determine if the desktop is active. In all the examples, the device
  was freshly flashed.

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

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

[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot

** Description changed:

  The following gdbus call is failing with a Error: Timeout was reached
  message:
  
  gdbus call --session --dest com.canonical.UnityGreeter --object-path /
  --method org.freedesktop.DBus.Properties.Get com.canonical.UnityGreeter
  IsActive
  
- 
- This is being seen on krillin devices starting with image 106 from 
ubuntu-touch/devel-proposed. It doesn't happen every time, so far today, I've 
seen it 3 times from about 12 tests. On the most recent failure, I grabbed a 
console and tried repeatedly to run the command from the shell, even after 2 
hours the timeout was still being returned (after about 28 seconds).
+ This is being seen on krillin devices starting with image 106 from
+ ubuntu-touch/devel-proposed. It doesn't happen every time, so far today,
+ I've seen it 3 times from about 12 tests. On the most recent failure, I
+ grabbed a console and tried repeatedly to run the command from the
+ shell, even after 2 hours the timeout was still being returned (after
+ about 28 seconds).
  
  A copy of ~/.cache/upstart/unity8.log is here:
  http://paste.ubuntu.com/10179482/
  
  I have 3 test cases where the problem was observed:
  http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-qtchooser/1/console
  
http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-gsettings-ubuntu-touch-schemas/1/console
  http://d-jenkins.ubuntu-ci:8080/job/fjg-boottest/3/console
  
  In all cases, the test is using adt-run (from autopkgtest) to drive a
  test on the phone device. adt-run uses the above gdbus call to determine
  if the desktop is active. In all the examples, the device was freshly
  flashed.
+ 
+ Update 2015-03-25: the qtbase dbus update in silo 018 seems to address
+ the boot issue, but causes autopilot to have problems seeing an
+ application start, randomly

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

Title:
  unity8 sometimes hangs on boot

Status in autopilot package in Ubuntu:
  New
Status in libusermetrics package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  The following gdbus call is failing with a Error: Timeout was
  reached message:

  gdbus call --session --dest com.canonical.UnityGreeter --object-path /
  --method org.freedesktop.DBus.Properties.Get
  com.canonical.UnityGreeter IsActive

  This is being seen on krillin devices starting with image 106 from
  ubuntu-touch/devel-proposed. It doesn't happen every time, so far
  today, I've seen it 3 times from about 12 tests. On the most recent
  failure, I grabbed a console and tried repeatedly to run the command
  from the shell, even after 2 hours the timeout was still being
  returned (after about 28 seconds).

  A copy of ~/.cache/upstart/unity8.log is here:
  http://paste.ubuntu.com/10179482/

  I have 3 test cases where the problem was observed:
  http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-qtchooser/1/console
  
http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-gsettings-ubuntu-touch-schemas/1/console
  http://d-jenkins.ubuntu-ci:8080/job/fjg-boottest/3/console

  In all cases, the test is using adt-run (from autopkgtest) to drive a
  test on the phone device. adt-run uses the above gdbus call to
  determine if the desktop is active. In all the examples, the device
  was freshly flashed.

  Update 2015-03-25: the qtbase dbus update in silo 018 seems to address
  the boot issue, but causes autopilot to have problems seeing an
  application start, randomly

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

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

[Touch-packages] [Bug 1410113] Re: [krillin] Data connection doesn't switch from Wifi to Cellular

2015-03-25 Thread Jean-Baptiste Lallement

** Summary changed:

- [krillin] Data connection doesn't switch from Wifi to Cellular (3G/4G)
+ [krillin] Data connection doesn't switch from Wifi to Cellular

** Description changed:

  Conditions to reproduce are not clear.
- *Sometimes* when going out of Wifi range, data doesn't switch to 3G/4G. I 
waited 45min and the connection never established. When I'm back within Wifi 
range, the device reconnects to the AP and data is working.
+ *Sometimes* when going out of Wifi range, data doesn't switch to 3G. I waited 
45min and the connection never established. When I'm back within Wifi range, 
the device reconnects to the AP and data is working.
  
  I didn't play with airplane mode.
  
  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: network-manager 0.9.8.8-0ubuntu33
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Tue Jan 13 09:34:02 2015
  IfupdownConfig:
-  # interfaces(5) file used by ifup(8) and ifdown(8)
-  # Include files from /etc/network/interfaces.d:
-  source-directory /etc/network/interfaces.d
+  # interfaces(5) file used by ifup(8) and ifdown(8)
+  # Include files from /etc/network/interfaces.d:
+  source-directory /etc/network/interfaces.d
  InstallationDate: Installed on 2015-01-12 (1 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20150112-030205)
  IpRoute:
-  default via 192.168.1.254 dev wlan0  proto static 
-  192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.16  metric 
9
+  default via 192.168.1.254 dev wlan0  proto static
+  192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.16  metric 
9
  NetworkManager.state:
-  [main]
-  NetworkingEnabled=true
-  WirelessEnabled=true
-  WWANEnabled=true
-  WimaxEnabled=true
+  [main]
+  NetworkingEnabled=true
+  WirelessEnabled=true
+  WWANEnabled=true
+  WimaxEnabled=true
  PciNetwork:
-  
+ 
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.dbus.1.system.d.org.freedesktop.NetworkManager.conf: 
2014-12-18T18:05:17
  nmcli-dev:
-  DEVICE TYPE  STATE DBUS-PATH 
 
-  /ril_0 gsm   connected 
/org/freedesktop/NetworkManager/Devices/2  
-  /ril_1 gsm   disconnected  
/org/freedesktop/NetworkManager/Devices/1  
-  wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
+  DEVICE TYPE  STATE DBUS-PATH
+  /ril_0 gsm   connected 
/org/freedesktop/NetworkManager/Devices/2
+  /ril_1 gsm   disconnected  
/org/freedesktop/NetworkManager/Devices/1
+  wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
-  RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
-  running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled
+  RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN
+  running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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

Title:
  [krillin] Data connection doesn't switch from Wifi to Cellular

Status in the base for Ubuntu mobile products:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  Conditions to reproduce are not clear.
  *Sometimes* when going out of Wifi range, data doesn't switch to 3G. I waited 
45min and the connection never established. When I'm back within Wifi range, 
the device reconnects to the AP and data is working.

  I didn't play with airplane mode.

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: network-manager 0.9.8.8-0ubuntu33
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Tue Jan 13 09:34:02 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  InstallationDate: Installed on 2015-01-12 (1 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20150112-030205)
  IpRoute:
   default via 192.168.1.254 dev wlan0  proto static
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.16  metric 
9
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  PciNetwork:

  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

[Touch-packages] [Bug 1363214] Re: [System Settings] [design] allow Passcodes of variable length instead of just 4 digits

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

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

Title:
  [System Settings] [design] allow Passcodes of variable length instead
  of just 4 digits

Status in Ubuntu UX bugs:
  Triaged
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Currently when setting a Passcode on the device, it must be 4 digits.
  This is artificially limiting. Other platforms (eg Android) allow
  longer Passcodes. It has always been my understanding that we should
  support Swipe, Passphrase and Passcode where Passphrase and Passcode
  can be arbitrarily long.

  However, once longer Passcodes are supported, we will have to add an
  Enter key. Right now, the lockscreen checks the Passcode once 4 digits
  are added so that you don't have to press Enter. I guess this was done
  for usability, but would be a security issue because an attacker can
  easily determine the Passcode length, which makes it easier to for an
  attacker to guess the Passcode. Eg, if I have a 5 digit Passcode set,
  then an attacker need only type '1' and know that the Passcode is
  only five characters. Now, a Passcode isn't strong to begin with and
  an automated attack could rather quickly brute force Passcodes, but we
  shouldn't make it easier for someone manually trying to guess the
  Passcode.

  The passphrase lockscreen prompt correctly allows variable length
  passphrases and requires you to press Enter.

  I suggest moving the 'X' up t the left of '0' and an Enter symbol to
  the rigth of '0'.

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

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

[Touch-packages] [Bug 1436312] [NEW] Uppercase URL causes web search

2015-03-25 Thread Robie Basak

Public bug reported:

Using krilin build 20.

In the browser, I enter the URL HTTP://www.ubuntu.com.

Expected behaviour: fixes case, takes me to Ubuntu website.

Actual behaviour: does a Google search for HTTP://www.ubuntu.com.

Impact: it's awkward to scan QR codes that give me URLs in all caps,
which is how I discovered the issue.

Workaround: edit the HTTP to http manually. But after the Google search,
editing the URL is awkward because the URL changes to one suitable for
the Google search.

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

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

Title:
  Uppercase URL causes web search

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Using krilin build 20.

  In the browser, I enter the URL HTTP://www.ubuntu.com.

  Expected behaviour: fixes case, takes me to Ubuntu website.

  Actual behaviour: does a Google search for HTTP://www.ubuntu.com.

  Impact: it's awkward to scan QR codes that give me URLs in all caps,
  which is how I discovered the issue.

  Workaround: edit the HTTP to http manually. But after the Google
  search, editing the URL is awkward because the URL changes to one
  suitable for the Google search.

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

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

[Touch-packages] [Bug 1436330] [NEW] Network Manager doesn't set metric for local networks any more, causing connection issues

2015-03-25 Thread Jason Straight

Public bug reported:

With Vivid, having two connections to the same network subnet is
unstable due to missing metrics for local networks.

Example:

Being connected to 192.168.1.0/24 via both wired and wireless will cause
connectivity issues as sent packets hop between the two interfaces.

It used to be that this wasn't an issue. I would go between work and
home and plug in and my machine would automatically connect to wireless
and it would use the lower metric ethernet interface for all
communications, while the wlan interface would remain connected but
unused.

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
NonfreeKernelModules: nvidia
ApportVersion: 2.16.2-0ubuntu4
Architecture: amd64
CurrentDesktop: KDE
Date: Wed Mar 25 09:17:27 2015
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2015-01-25 (58 days ago)
InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
SourcePackage: network-manager
UpgradeStatus: Upgraded to vivid on 2015-03-17 (8 days ago)
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: 
Error: Object 'nm' is unknown, try 'nmcli help'.

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


** Tags: amd64 apport-bug vivid

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

Title:
  Network Manager doesn't set metric for local networks any more,
  causing connection issues

Status in network-manager package in Ubuntu:
  New

Bug description:
  With Vivid, having two connections to the same network subnet is
  unstable due to missing metrics for local networks.

  Example:

  Being connected to 192.168.1.0/24 via both wired and wireless will
  cause connectivity issues as sent packets hop between the two
  interfaces.

  It used to be that this wasn't an issue. I would go between work and
  home and plug in and my machine would automatically connect to
  wireless and it would use the lower metric ethernet interface for all
  communications, while the wlan interface would remain connected but
  unused.

  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
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 25 09:17:27 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-01-25 (58 days ago)
  InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-03-17 (8 days ago)
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1436162] Re: [pulsesink] abort at pthread_mutex_unlock(m-mutex) == 0' failed at pulsecore/mutex-posix.c:118, function pa_mutex_unlock() with libc 2.21

2015-03-25 Thread Ricardo Salveti

SMP support for futex_atomic_cmpxchg_inatomic was added in 2.6.38, but
it required !CPU_USE_DOMAINS.

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

Title:
  [pulsesink] abort at pthread_mutex_unlock(m-mutex) == 0' failed at
  pulsecore/mutex-posix.c:118, function pa_mutex_unlock() with libc 2.21

Status in glibc package in Ubuntu:
  Confirmed
Status in gst-plugins-good1.0 package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  current build number: 146
  device name: m75
  channel: ubuntu-touch/vivid-proposed
  last update: 2015-03-24 13:57:03
  version version: 146

  After libc 2.21 landed, pulsesink fails constantly when pausing or
  seeking the active pipeline.

  Abort message:
  Assertion 'pthread_mutex_unlock(m-mutex) == 0' failed at 
pulsecore/mutex-posix.c:118, function pa_mutex_unlock(). Aborting.

  This is basically happens when it tries to unlock a mutex that is
  already unlocked.

  This issue doesn't happen with libc 2.19.

  To reproduce the issue:
  GST_DEBUG=*pulse*:5 gst-launch-1.0 playbin uri=file:///tmp/foobar.mp3

  Then when playing, just hit control+c, which will then pause the
  pipeline, causing the crash. The crash happens with most of the times
  you pause or seek the pipeline.

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

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

[Touch-packages] [Bug 1410113] Re: [krillin] Data connection doesn't switch from Wifi to Cellular (3G/4G)

2015-03-25 Thread John McAleely

There's no 4G on Krillin

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

** Tags added: bq

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

Title:
  [krillin] Data connection doesn't switch from Wifi to Cellular (3G/4G)

Status in the base for Ubuntu mobile products:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  Conditions to reproduce are not clear.
  *Sometimes* when going out of Wifi range, data doesn't switch to 3G/4G. I 
waited 45min and the connection never established. When I'm back within Wifi 
range, the device reconnects to the AP and data is working.

  I didn't play with airplane mode.

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: network-manager 0.9.8.8-0ubuntu33
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Tue Jan 13 09:34:02 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  InstallationDate: Installed on 2015-01-12 (1 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20150112-030205)
  IpRoute:
   default via 192.168.1.254 dev wlan0  proto static 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.16  metric 
9
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  PciNetwork:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.dbus.1.system.d.org.freedesktop.NetworkManager.conf: 
2014-12-18T18:05:17
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   /ril_0 gsm   connected 
/org/freedesktop/NetworkManager/Devices/2  
   /ril_1 gsm   disconnected  
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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

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

[Touch-packages] [Bug 1436302] [NEW] python3.4 segmentation fault while running unattended-upgrade

2015-03-25 Thread Wout

Public bug reported:

We run 'unattended-upgrade -d' from cron and have seen regular core
dumps. Below is some gdb output for one case:

(gdb) where
#0 _int_malloc (av=av@entry=0x7fd4362de760 main_arena, bytes=bytes@entry=193) 
at malloc.c:3489
#1 0x7fd435fa17e1 in _int_realloc (av=0x7fd4362de760 main_arena, 
oldp=0xd6fe30, oldsize=144, nb=208) at malloc.c:4286
#2 0x7fd435fa2fc9 in _GI__libc_realloc (oldmem=0xd6fe40, bytes=200) at 
malloc.c:3029
#3 0x004851cd in PyMem_Realloc (new_size=optimized out, 
ptr=optimized out) at ../Objects/obmalloc.c:308
#4 list_resize.7991 (self=0x7fd436549e48, newsize=17) at 
../Objects/listobject.c:63
#5 0x00485269 in app1 (v=0x7fd435306288, self=0x7fd436549e48) at 
../Objects/listobject.c:294
#6 PyList_Append (op=op@entry=0x7fd436549e48, 
newitem=newitem@entry=0x7fd435306288) at ../Objects/listobject.c:306
#7 0x005bf7a9 in PyImport_Cleanup () at ../Python/import.c:464
#8 0x005bf945 in Py_Finalize.part.6.32879 () at 
../Python/pythonrun.c:616
#9 0x0060cb12 in Py_Finalize () at ../Python/pythonrun.c:564
#10 Py_Main (argc=argc@entry=3, argv=argv@entry=0xae6010) at 
../Modules/main.c:771
#11 0x0041ec0d in main (argc=3, argv=optimized out) at 
../Modules/python.c:69

Note that gdb always complains that the coredump may not match the
binary I provided. However, I'm pretty sure I got the right one.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: python3-minimal 3.4.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15
Uname: Linux 3.13.0-46-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
Date: Wed Mar 25 11:57:03 2015
Ec2AMI: ami-254ad452
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: eu-west-1b
Ec2InstanceType: r3.xlarge
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
MarkForUpload: True
ProcEnviron:
 SHELL=/bin/bash
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SourcePackage: python3-defaults
UpgradeStatus: No upgrade log present (probably fresh install)
_MarkForUpload: True

** Affects: python3-defaults (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug ec2-images trusty

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

Title:
  python3.4 segmentation fault while running unattended-upgrade

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  We run 'unattended-upgrade -d' from cron and have seen regular core
  dumps. Below is some gdb output for one case:

  (gdb) where
  #0 _int_malloc (av=av@entry=0x7fd4362de760 main_arena, 
bytes=bytes@entry=193) at malloc.c:3489
  #1 0x7fd435fa17e1 in _int_realloc (av=0x7fd4362de760 main_arena, 
oldp=0xd6fe30, oldsize=144, nb=208) at malloc.c:4286
  #2 0x7fd435fa2fc9 in _GI__libc_realloc (oldmem=0xd6fe40, bytes=200) at 
malloc.c:3029
  #3 0x004851cd in PyMem_Realloc (new_size=optimized out, 
ptr=optimized out) at ../Objects/obmalloc.c:308
  #4 list_resize.7991 (self=0x7fd436549e48, newsize=17) at 
../Objects/listobject.c:63
  #5 0x00485269 in app1 (v=0x7fd435306288, self=0x7fd436549e48) at 
../Objects/listobject.c:294
  #6 PyList_Append (op=op@entry=0x7fd436549e48, 
newitem=newitem@entry=0x7fd435306288) at ../Objects/listobject.c:306
  #7 0x005bf7a9 in PyImport_Cleanup () at ../Python/import.c:464
  #8 0x005bf945 in Py_Finalize.part.6.32879 () at 
../Python/pythonrun.c:616
  #9 0x0060cb12 in Py_Finalize () at ../Python/pythonrun.c:564
  #10 Py_Main (argc=argc@entry=3, argv=argv@entry=0xae6010) at 
../Modules/main.c:771
  #11 0x0041ec0d in main (argc=3, argv=optimized out) at 
../Modules/python.c:69

  Note that gdb always complains that the coredump may not match the
  binary I provided. However, I'm pretty sure I got the right one.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: python3-minimal 3.4.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15
  Uname: Linux 3.13.0-46-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  Date: Wed Mar 25 11:57:03 2015
  Ec2AMI: ami-254ad452
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: eu-west-1b
  Ec2InstanceType: r3.xlarge
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  MarkForUpload: True
  ProcEnviron:
   SHELL=/bin/bash
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SourcePackage: python3-defaults
  UpgradeStatus: No upgrade log present (probably fresh install)
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1436302/+subscriptions

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

[Touch-packages] [Bug 1434124] Re: Uninstallation confirmation screen inconsistent with other dialogs

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

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

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

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

Title:
  Uninstallation confirmation screen inconsistent with other dialogs

Status in Ubuntu UX bugs:
  Triaged
Status in unity-scope-click package in Ubuntu:
  Triaged

Bug description:
  On current rtm trying to uninstall a click from the dash you get a
  confirmation screen with a confirm button on the left and an orange
  cancel one on the right, that seems inconsistant with the
  guideline/what other part of the system are doing

  - why is cancel in orange? 
https://design.ubuntu.com/apps/building-blocks/buttons states that the color is 
for negative actions
  - unsure that confirm is conveying what the button does, could it be 
uninstall or confirm uninstallation?

  it feels like that the left button should be the red one and have
  something in its label stating what you are confirming (since the
  rational is that users tend to not read the text description, so the
  button should summarize the action they are doing)

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

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

[Touch-packages] [Bug 1436281] Re: package libssl1.0.0:amd64 1.0.1f-1ubuntu9.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 5

2015-03-25 Thread Ubuntu Foundations Team Bug Bot

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

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

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

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

Title:
  package libssl1.0.0:amd64 1.0.1f-1ubuntu9.4 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 5

Status in openssl package in Ubuntu:
  Invalid

Bug description:
  ive been having these issues with mainly kernal updates.  after
  lubuntu 12.04 ive not been able to get  stable install on my acer
  d255-2331.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: libssl1.0.0:amd64 1.0.1f-1ubuntu9.4
  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: Wed Mar 25 03:46:21 2015
  DuplicateSignature: package:libssl1.0.0:amd64:1.0.1f-1ubuntu9.4:subprocess 
installed post-installation script returned error exit status 5
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 5
  SourcePackage: openssl
  Title: package libssl1.0.0:amd64 1.0.1f-1ubuntu9.4 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 5
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1427358] Re: Network indicator should deal with AP/P2P Wi-Fi devices as well as active AP/P2P connections

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

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

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

Title:
  Network indicator should deal with AP/P2P Wi-Fi devices as well as
  active AP/P2P connections

Status in Ubuntu UX bugs:
  Triaged
Status in indicator-network package in Ubuntu:
  New

Bug description:
  Using vivid on krillin

  Background:
  From the spec on networking [1]:

  A hotspot requires Wi-Fi to work. To warn you that turning off Wi-Fi
  will turn off the hotspot, whenever Hotspot is on, the “Wi-Fi” switch
  wherever it appears (in the quick-access area, in the “Wi-Fi” screen,
  and in the network menu) should instead be “Wi-Fi used for hotspot”.
  In addition, turning on Flight Mode should warn that it will turn off
  Hotspot.

  Reproduce:
  Start an AP hotspot using [2]

  What happens:
  1. The network indicator gives no indication that turning off Wi-Fi will 
disable the hotspot
  2. Flight mode silently disables hotspot and does not restore it after being 
turned off
  3. The AP looks like any 'normal', connected network

  What should happen:
  1. The Wi-Fi switch should have a different label (see [1])
  2. Going into flight mode should yield a warning
  3. The AP should probably be visually separated from 'normal' networks

  [1] https://wiki.ubuntu.com/Networking#hotspot
  [2] 
http://bazaar.launchpad.net/~mathieu-tl/+junk/touch-hotspot/view/head:/hotspot.py

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

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

[Touch-packages] [Bug 1436100] Re: Location reverts periodically to City of Westminster even with wifi and GPS location enabled

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

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

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

Title:
  Location reverts periodically to City of Westminster even with wifi
  and GPS location enabled

Status in location-service package in Ubuntu:
  Confirmed

Bug description:
  In Nearby scope, Westminster attractions are displayed. Can be
  corrected by refreshing. I am using build 20.

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

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

[Touch-packages] [Bug 1300565] Re: please syntax highlight debdiff files

What's a debdiff file?  Can you add an example?

And would you want it to be coloured in the same manner as normal diff
and patch files?

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

Title:
  please syntax highlight debdiff files

Status in nano package in Ubuntu:
  New

Bug description:
  nano source highlights diff and patch files.  It would be nice if it
  did the same with debdiff files.

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

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

[Touch-packages] [Bug 1378350] Re: [Browser] Need to allow multiple apps to handle the same url patterns

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

** Changed in: ubuntu-ux
 Assignee: Magdalena Mirowicz (magdalena-mirowicz) = (unassigned)

** Changed in: ubuntu-ux
 Assignee: (unassigned) = Matthew Paul Thomas (mpt)

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

Title:
  [Browser] Need to allow multiple apps to handle the same url patterns

Status in Ubuntu UX bugs:
  Triaged
Status in content-hub package in Ubuntu:
  New
Status in url-dispatcher package in Ubuntu:
  Triaged

Bug description:
  Steps:
  * install gmail and dekko apps

  Expected:
  * when using a mailto: URL (see bug #1351222) URL, the user should be asked 
which app to open (and cache the response optionally?)

  Current:
  * not sure what would happen ;)

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

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

[Touch-packages] [Bug 1435083] Re: If bluetooth is turned ON, device is always visible

2015-03-25 Thread Nephilim1973

Oh sorry...
I am using an Aquaris E4.5 Ubuntu Phone...

Wrong place ?

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

Title:
  If bluetooth is turned ON, device is always visible

Status in indicator-bluetooth package in Ubuntu:
  Incomplete

Bug description:
  If bluetooth is turned on, there is no way to switch between visible/hidden 
mode.
  Device is always visible.

  Regards.

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

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

[Touch-packages] [Bug 1436312] Re: Uppercase URL causes web search

2015-03-25 Thread Olivier Tilloy

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

** Also affects: webbrowser-app
   Importance: Undecided
   Status: New

** Changed in: webbrowser-app
   Status: New = Confirmed

** Changed in: webbrowser-app
   Importance: Undecided = Low

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

Title:
  Uppercase URL causes web search

Status in Web Browser App:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  Using krilin build 20.

  In the browser, I enter the URL HTTP://www.ubuntu.com.

  Expected behaviour: fixes case, takes me to Ubuntu website.

  Actual behaviour: does a Google search for HTTP://www.ubuntu.com.

  Impact: it's awkward to scan QR codes that give me URLs in all caps,
  which is how I discovered the issue.

  Workaround: edit the HTTP to http manually. But after the Google
  search, editing the URL is awkward because the URL changes to one
  suitable for the Google search.

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

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

[Touch-packages] [Bug 1045062] Re: No option to save without BOM (Byte Order Mark)

But nano can, just like those other editors, remove the invisible BOM:
when on the first line of the file, press Home and Delete, and save,
and the BOM is gone.  Does this not work for you?

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

Title:
  No option to save without BOM (Byte Order Mark)

Status in nano package in Ubuntu:
  Confirmed

Bug description:
  This may be a wishlist type bug.

  Currently, Nano in precise saves with BOM (Byte Order Mark) by
  default.  There is no way within nano to save without BOM, which
  requires me to download remote server documents to this system and
  then update and reupload the documents after using gedit, kate, or
  some other editor.

  This sometimes screws up remote PHP programs and scripts, which means
  it may be prudent to give the option to decide whether to save with or
  without the Byte Order Mark.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nano 2.2.6-1
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: amd64
  Date: Sun Sep  2 14:36:54 2012
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: nano
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

** Changed in: ubuntu-ux
 Assignee: (unassigned) = Olga Kemmet (olga-kemmet)

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

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

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

Title:
  tutorial not adapted to desktop mode

Status in Ubuntu UX bugs:
  Triaged
Status in unity8 package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1303354] Re: [Dash] App Summary appears to be part of Description

2015-03-25 Thread James Tait

** Changed in: click-package-index
   Importance: Medium = High

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

Title:
  [Dash] App Summary appears to be part of Description

Status in Click Package metadata search service:
  Triaged
Status in Online service used by software center:
  New
Status in Ubuntu UX bugs:
  Fix Committed
Status in The Unity 8 shell:
  Fix Released
Status in click package in Ubuntu:
  New
Status in unity-scope-click package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  The tagline in app descriptions looks like it is part of the main
  description, without any spacing or difference in font, which makes it
  hard to read. Is it possible to make the tagline bold or separated in
  some way?

  Desired solution
  -
  Separate out tagline from rest of info and place directly below screenshots - 
see attached design including the tagline / strapline

To manage notifications about this bug go to:
https://bugs.launchpad.net/click-package-index/+bug/1303354/+subscriptions

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

[Touch-packages] [Bug 1425991] Re: Networks I have never connected to should be confined to an Unknown Networks folder

** Summary changed:

- Networks I have never connected to should be confined to the More Networks 
folder
+ Networks I have never connected to should be confined to an Unknown 
Networks folder

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

Title:
  Networks I have never connected to should be confined to an Unknown
  Networks folder

Status in indicator-network package in Ubuntu:
  New

Bug description:
  When a user clicks the network manager indicator, a dropdown appears
  and lists wifi networks. This menu should NOT display networks that
  the user has never connected to. Networks the user has never connected
  to should only display in the More networks folder. At a mininum,
  the user should be given the ability to confine unwanted networks in
  the More networks folder.

  It is an unproductive design choice to force users to have to wade
  through networks they have never connected to (networks they will
  never connect to) in their menu. Numerous reasons exist why a user
  will not use the Auto-Connect setting for wireless networks. So it
  makes sense and is more efficient to have the menu only display the
  networks the user makes active use of and no more.

  When I click on the Network Manager Indicator and select Edit
  Connections and then look under the Wifi heading, only a couple
  networks appear. So why do 5 or more networks (networks I have never
  connected to, networks I never will connect to) perpetually show in
  the Network Indicator menu? They should not be displayed like they
  are. They should be confined to the More networks folder.
  Alternatively, there should be a way to manually confine/sandbox
  unwanted networks to this folder so they no longer display in the
  dropdown menu.

  In the interest of providing a visual example of what I am talking about, 
here is a picture of some networks I would like to hide/remove from my Network 
Indicator menu.
  http://a.pomf.se/fdqlnn.png

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

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

[Touch-packages] [Bug 1435685] Re: [Asus X751MD] Double mouse cursor

2015-03-25 Thread lecolo

penalvch, thanx for your job,

for the touchpad, i sent ubuntu-bug linux 
https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1436327
(maybe i made a mistake letting utopic in repport instead of trusty)

Keyboard is not totaly ok . Maybe a bad choice in install.

pf...

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

Title:
  [Asus X751MD] Double mouse cursor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I have a double mouse cursor.

  WORKAROUND: Installed nvidia driver from Ubuntu repository.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7
  Uname: Linux 3.16.0-33-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Mar 24 07:51:42 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation ValleyView Gen7 [8086:0f31] (rev 0e) (prog-if 00 [VGA 
controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:16dd]
  InstallationDate: Installed on 2015-03-22 (1 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS Trusty Tahr - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. X751MD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic.efi.signed 
root=UUID=e919445c-9bea-469f-a036-22c3f5fb6dbb ro splash quiet
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X751MD.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X751MD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX751MD.208:bd02/06/2015:svnASUSTeKCOMPUTERINC.:pnX751MD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX751MD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X751MD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  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: Tue Mar 24 07:49:15 2015
  xserver.configfile: default
  xserver.errors:
   Failed to load module nvidia (module does not exist, 0)
   Failed to load module nvidia (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5928
   vendor CMN
  xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

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

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

[Touch-packages] [Bug 1400372] Re: keyboard re-appears in webbrowser after dismissing