[Touch-packages] [Bug 1544530] Re: cant open app from the dash

[Michał Sawicz]

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

I assume by "form dash" you actually meant from the launcher (since the
Apps scope is in the dash). In that case you'll soon get a fix for that
- bug #1541388.

** This bug has been marked a duplicate of bug 1541388
   Icons in launcher sometimes refuse to launch application

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

Title:
  cant open app from the dash

Status in unity8 package in Ubuntu:
  New

Bug description:
  Sometimes when you try to open app from a icon in the dash the app isn't 
opened. It happened to me with telegram app and also with dekko. You can open 
those apps from the apps scope.
  You can open the other apps from the dash when it happens. I mean, when it 
happened with telegram i could open the others apps from the dash. When it 
happened with dekko i could open the oder apps. Telegram included.

  Here is the log from unity 8:
  http://paste.ubuntu.com/14860912/

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

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

[Touch-packages] [Bug 1294195] Re: Please consider enabling Unattended-Upgrade::Remove-Unused-Dependencies by default

[Jarno Suni]

** This bug is no longer a duplicate of bug 1267059
   "Unattended-Upgrade::Remove-Unused-Dependencies" does not work

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

Title:
  Please consider enabling Unattended-Upgrade::Remove-Unused-
  Dependencies by default

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  When you install Ubuntu today with full disk encryption you end up
  with a separate small /boot partition (approx 200Mb).  It doesn't take
  long for this to fill up with old kernels.

  While we mark old kernels for auto-removal nothing (on the default
  system) actually triggers removal of unused packages; a human needs to
  invoke (or arrange to be invoked) 'apt-get autoremove'.

  /etc/apt/apt.conf.d/50unattended-upgrades documents an
  Unattended-Upgrade::Remove-Unused-Dependencies configuration option.
  I'd suggest we consider enabling this option by default on new
  installs.

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

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

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

[Jarno Suni]

LP: #1267059 is about automatic removing fails even if 
Unattended-Upgrade::Remove-Unused-Dependencies "true";
It was fixed already in unattended-upgrades - 0.76ubuntu1.2. There is an error 
in the changelog of unattended-upgrades. This is not a duplicate of bug 
#1267059. This bug is about making the autoremoval of excessive the default 
behavior.


** This bug is no longer a duplicate of bug 1267059
   "Unattended-Upgrade::Remove-Unused-Dependencies" does not work

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

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted installation or on any installation, when /boot partition
  gets full

Status in unattended-upgrades package in Ubuntu:
  Fix Committed

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

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

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

[Touch-packages] [Bug 1544874] [NEW] dbus.user-session.upstart could avoid mktemp

[Simon McVittie]

Public bug reported:

While investigating a separate bug I happened to look at dbus.user-
session.upstart, and noticed that it is somewhat more complex than it
needs to be.

> pre-start script
> DBUS_SESSION_BUS_ADDRESS=unix:abstract=$(mktemp -u /tmp/dbus-XX)
> initctl set-env DBUS_SESSION_BUS_ADDRESS=$DBUS_SESSION_BUS_ADDRESS
> end script
>
>
> exec dbus-daemon --fork --session --address="$DBUS_SESSION_BUS_ADDRESS"

One obvious simplification you could use here would be to ask dbus-
daemon to listen on an arbitrarily selected abstract AF_UNIX address and
tell you which one it used. In principle libdbus could have a retry loop
to try multiple possibilities if the one it selects first is in use
(which this use of mktemp obviously won't do); at the moment it doesn't,
because the probability of a successful DoS by creating lots of abstract
sockets is low (approximately n in 3e15, where n is the number of
sockets created by an attacker), but I'd review a patch to dbus/dbus-
server-unix.c if someone wanted to add that retry loop.

That would look something like this (please interpret this as pseudocode
rather than a proposed patch, I don't actually know Upstart syntax):

exec script
# the default listening address is equivalent to 
--address=unix:tmpdir=/tmp
dbus-daemon --fork --session --print-address=5 
5>"$XDG_RUNTIME_DIR/dbus-session"
end script

post-start script
DBUS_SESSION_BUS_ADDRESS="$(cat "$XDG_RUNTIME_DIR/dbus-session")"
initctl set-env --global 
DBUS_SESSION_BUS_ADDRESS="$DBUS_SESSION_BUS_ADDRESS"
initctl notify-dbus-address "$DBUS_SESSION_BUS_ADDRESS"
end script

which is already somewhat simpler. This would also have the advantage
that the advertised address would contain the bus's GUID like it does
with traditional dbus-launch, meaning that dbus_connection_open() would
work ().

However, since the current script only seems to support one dbus-daemon
per $XDG_RUNTIME_DIR anyway, there's little point in using mktemp or
unix:tmpdir: the job could instead force a specific address, like the
systemd unit in dbus-user-session does. Modern libdbus (1.10+) and GDBus
(2.45.3+) will try $XDG_RUNTIME_DIR/bus if there is no
DBUS_SESSION_BUS_ADDRESS, so setting the DBUS_SESSION_BUS_ADDRESS is
really only there to support reimplementations like dbus-sharp.

exec dbus-daemon --fork --session --address="unix:path=$XDG_RUNTIME_DIR/bus"
post-start initctl set-env --global 
DBUS_SESSION_BUS_ADDRESS="unix:path=$XDG_RUNTIME_DIR/bus"
post-start initctl notify-dbus-address "unix:path=$XDG_RUNTIME_DIR/bus"

(This could be combined with --print-address if you want to know the
full address with the guid.)

Or, if the intention is to support multiple login sessions per user-
session (see  for terminology), the Upstart job could
force the bus to be "$XDG_RUNTIME_DIR/session-$XDG_SESSION_ID/bus" or
something.

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

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

Title:
  dbus.user-session.upstart could avoid mktemp

Status in dbus package in Ubuntu:
  New

Bug description:
  While investigating a separate bug I happened to look at dbus.user-
  session.upstart, and noticed that it is somewhat more complex than it
  needs to be.

  > pre-start script
  > DBUS_SESSION_BUS_ADDRESS=unix:abstract=$(mktemp -u /tmp/dbus-XX)
  > initctl set-env DBUS_SESSION_BUS_ADDRESS=$DBUS_SESSION_BUS_ADDRESS
  > end script
  >
  >
  > exec dbus-daemon --fork --session --address="$DBUS_SESSION_BUS_ADDRESS"

  One obvious simplification you could use here would be to ask dbus-
  daemon to listen on an arbitrarily selected abstract AF_UNIX address
  and tell you which one it used. In principle libdbus could have a
  retry loop to try multiple possibilities if the one it selects first
  is in use (which this use of mktemp obviously won't do); at the moment
  it doesn't,  because the probability of a successful DoS by creating
  lots of abstract sockets is low (approximately n in 3e15, where n is
  the number of sockets created by an attacker), but I'd review a patch
  to dbus/dbus-server-unix.c if someone wanted to add that retry loop.

  That would look something like this (please interpret this as
  pseudocode rather than a proposed patch, I don't actually know Upstart
  syntax):

  exec script
  # the default listening address is equivalent to 
--address=unix:tmpdir=/tmp
  dbus-daemon --fork --session --print-address=5 
5>"$XDG_RUNTIME_DIR/dbus-session"
  end script

  post-start script
  DBUS_SESSION_BUS_ADDRESS="$(cat "$XDG_RUNTIME_DIR/dbus-session")"
  initctl set-env --global 

[Touch-packages] [Bug 1323593] Re: Unattended upgrades crash

[Jarno Suni]

** This bug is no longer a duplicate of bug 1267059
   "Unattended-Upgrade::Remove-Unused-Dependencies" does not work

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

Title:
  Unattended upgrades crash

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  Based this bug report upon https://bugs.launchpad.net/ubuntu/+source
  /unattended-upgrades/+bug/1052360/comments/17

  Installed latest updates on Xubuntu Trusty, immediately during the
  update process the system detected an error, after reboot an error
  report again emerged, hence reporting this bug as suggested above.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unattended-upgrades 0.82.1ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue May 27 12:40:58 2014
  InstallationDate: Installed on 2014-05-17 (10 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1544033] Re: Account details page needs design love

[Launchpad Bug Tracker]

** Branch linked: lp:~mardy/ubuntu-system-settings-online-
accounts/spacing-1544033

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

Title:
  Account details page needs design love

Status in Online Accounts setup for Ubuntu Touch:
  In Progress
Status in webapps-sprint:
  In Progress
Status in pay-ui package in Ubuntu:
  New
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  In Progress

Bug description:
  See attached screenshot. There's multiple issues with this page:

  * Empty space at the top
  * missing icon for PayUI
  * PayUI displays appid instead of user friendly name

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

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

[Touch-packages] [Bug 1250668] Re: upstart session for dbus has hard coded .cache directory

[Simon McVittie]

> far more complicated than it needs to be

That may have been overstating it; in the absence of systemd-style
socket activation, there's a limit to how much it can be simplified
without having things try to connect to dbus-daemon before it's running
:-(

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

Title:
  upstart session for dbus has hard coded .cache directory

Status in dbus package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu 13.10
  Release:13.10

  
  Package: dbus
  Architecture: amd64
  Version: 1.6.12-0ubuntu10


  The file /usr/share/upstart/sessions/dbus.conf contains a hardcoded
  path to the .cache directory, making the use of XDG_CACHE_HOME
  variable non working.

  The fix could to change line
  echo "DBUS_SESSION_BUS_ADDRESS=${DBUS_SESSION_BUS_ADDRESS}" 
>$HOME/.cache/upstart/dbus-session
  into
  echo "DBUS_SESSION_BUS_ADDRESS=${DBUS_SESSION_BUS_ADDRESS}" 
>${XDG_CACHE_HOME:-$HOME/.cache}/upstart/dbus-session

  I tested it and it works for me...

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

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

[Touch-packages] [Bug 1447839] Re: Mouse cursor never changes when moving over widgets in app windows

[Daniel van Vugt]

Although in my case, running Xmir in Unity8 the cursor gets stuck on the
text selection "I" one.

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

Title:
  Mouse cursor never changes when moving over widgets in app windows

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in unity-system-compositor package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  currently on the unity8 desktop windowed mode, the mouse remains in
  it's "arrow" form not prompting the user when it's on the edge of a
  window where the window can be rescaled.

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

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

[Touch-packages] [Bug 1447839] Re: Mouse cursor never changes when moving over apps in Unity8

[Daniel van Vugt]

Just noticed this in Xmir too. Although Xmir and Mir demo servers seem
to change the mouse cursor fine now, Unity8 hasn't implemented the same
yet.

Just try running "gedit" and expect the cursor to change between text
selection and arrow as you move it around.

** Summary changed:

- Support dynamic mouse cursor icons
+ Mouse cursor never changes when moving over apps in Unity8

** Summary changed:

- Mouse cursor never changes when moving over apps in Unity8
+ Mouse cursor never changes when moving widgets in app windows

** Summary changed:

- Mouse cursor never changes when moving widgets in app windows
+ Mouse cursor never changes when moving over widgets in app windows

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

Title:
  Mouse cursor never changes when moving over widgets in app windows

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in unity-system-compositor package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  currently on the unity8 desktop windowed mode, the mouse remains in
  it's "arrow" form not prompting the user when it's on the edge of a
  window where the window can be rescaled.

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

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

[Touch-packages] [Bug 1517597] Re: [regression] mouse pointer support on emulator is broken

[Andreas Pokorny]

I wanted to share some status update, the emulated touchscreen troubles
have been resolved. Now ui elements fail to detect any gestures, the
display claims its phsyical width, height and dpi to be 0.

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

Title:
  [regression] mouse pointer support on emulator is broken

Status in Client Developer Experience:
  New
Status in Canonical System Image:
  Confirmed
Status in Mir:
  Opinion
Status in Mir 0.18 series:
  Opinion
Status in android package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Invalid

Bug description:
  STEPS:
  1. Flash with sudo ubuntu-emulator create --channel ubuntu-touch/rc/ubuntu 
rc-test
  2. Wait for it to build
  3. Run with ubuntu-emulator run rc-test
  4. Starts up but the mouse never moves meaning you can't leave the first page 
of the welcome wizard

  EXPECTED:
  I expect the emulator cursor to follow the mouse cursor and be able to click 
on things

  ACTUAL:
  Emulator cursors stay in the top left preventing movement.

  As noted below F6 toggles the input mode.
  The pointer movement is quite slow and jerky.
  You also can no longer initiate an edge swipe even in trackball mode.

  This is a major regression from how the emulator used to perform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-developer-experience/+bug/1517597/+subscriptions

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

[Touch-packages] [Bug 1519499] Re: Shutdown failure: Assertion 'sd_id128_randomize() >= 0' failed at ../src/core/dbus.c:657, function bus_on_connection(). Aborting.

[Sven R. Kunze]

@Martin Is there some update on this?

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

Title:
  Shutdown failure: Assertion 'sd_id128_randomize() >= 0' failed at
  ../src/core/dbus.c:657, function bus_on_connection(). Aborting.

Status in systemd package in Ubuntu:
  New

Bug description:
  This is a follow-up on this issue here:
  https://github.com/lxc/lxd/issues/1336 I cannot stop a LXD container
  gently and as it seems the issue lies within ubuntu/systemd which does
  not handle SIGPWR correctly.

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

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

[Touch-packages] [Bug 1530464] Re: [GA-MA770T-UD3P, Realtek ALC888, Green Line Out, Rear] No sound at all

[Raymond]

You have to send email to author if it is a regression of this patch
which should check the codec is alc889 when gigabyte motherboards have
same pci ssid

https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/hda/patch_realtek.c?id=b2c53e206967d01fd4fb6dd525f89ae738beb2e6

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

Title:
  [GA-MA770T-UD3P, Realtek ALC888, Green Line Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  after several  attempts to remove, re-install and reload the pulse audio as 
well as confirming alsa mixer settings and mute settings, sound is no longer 
coming out of speakers on 14.04 after something was installed.
  Steps included downgrading Skype version which did not help.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-42.48~14.04.1-generic 3.19.8-ckt10
  Uname: Linux 3.19.0-42-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan  1 13:37:48 2016
  InstallationDate: Installed on 2015-11-02 (60 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB failed
  Symptom_Card: Built-in Audio - HDA ATI SB
  Symptom_Jack: Green Line Out, Rear
  Symptom_Type: No sound at all
  Title: [GA-MA770T-UD3P, Realtek ALC888, Green Line Out, Rear] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/22/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F12
  dmi.board.name: GA-MA770T-UD3P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF12:bd03/22/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA770T-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA770T-UD3P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA770T-UD3P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1542305] Re: Pressing button on bluetooth game pad shuts unity down

[Michał Sawicz]

Potentially duplicate of bug #1544878.

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

Title:
  Pressing button on bluetooth game pad shuts unity down

Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  I have a bluetooth Ouya game controller. One of these:-

  http://www.amazon.co.uk/OUYA-Wireless-Controller-Electronic-
  Games-y/dp/B002I0GX38

  Note it has a bunch of buttons and the black square in the middle is a
  mouse/touchpad.

  Associated it with my bq e4.5 running todays rc-proposed.
  Mouse cursor appears (kinda expected, but a bit odd - on Android the mouse 
cursor doesn't appear until you touch the pad).
  Press any button and unity8 crashes hard.

  No crash file in /var/crash.

  The following appears immediately after pressing the button, in the
  unity8 log.

  qtmir.surfaces: MirSurfaceItem::MirSurfaceItem
  QObject: Cannot create children for a parent that is in a different thread.
  (Parent is DashCommunicator(0xfe96b0), parent's thread is QThread(0xf1ef90), 
current thread is DashCommunicator(0xfe96b0)
  UbuntuKeyboardInfo - socket error: "QLocalSocket::connectToServer: Connection 
refused"
  Fail to connect with service: 
QDBusError("org.freedesktop.DBus.Error.Disconnected", "Connection was 
disconnected before a reply was received")

  Running gdb produces this output when the crash happens:-

  Program received signal SIGTERM, Terminated.
  0xb6aa4fa8 in QV4::ExecutionEngine::qmlContextObject() const () from 
/usr/lib/arm-linux-gnueabihf/libQt5Qml.so.5

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.11+15.04.20160129-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.17.2-0ubuntu1.3touch1
  Architecture: armhf
  Date: Fri Feb  5 12:24:52 2016
  InstallationDate: Installed on 2016-02-05 (0 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20160205-020304)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1544878] Re: Mir servers crash if I press the side mouse button (thumb)

[Michał Sawicz]

This seems similar to bug #1542305, even though that one has different
log/.crash results.

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

Title:
  Mir servers crash if I press the side mouse button (thumb)

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

Bug description:
  Mir servers crash if I press the side mouse button (thumb).

  There are two of them on the side of my Intellimouse Explorer 3.0. The
  kernel calls them BTN_SIDE and BTN_EXTRA. And X calls them buttons 8
  and 9.

  When the crash happens I see in unity8.log:

  [1455268365.782990]  MirSurfaceAPI: Caught exception at client library 
boundary (in mir_surface_release): 
/build/mir-wMQ7xO/mir-0.19.2+16.04.20160210/src/client/rpc/stream_socket_transport.cpp(168):
 Throw in function virtual void 
mir::client::rpc::StreamSocketTransport::send_message(const 
std::vector&, const std::vector&)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: Failed to send message to server: Broken pipe
  32, "Broken pipe"
  *** Error in `unity8': free(): invalid size: 0x7fcb4c03fe90 ***

  Also happens with the Mir demo servers; they segfault but without a
  usable stack trace due to exception handling.

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

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

[Touch-packages] [Bug 1323593] Re: Unattended upgrades crash

[Jarno Suni]

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

** This bug has been marked a duplicate of bug 1054927
   Autoupdater fills /boot and crashes because old kernel images are never 
removed

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

Title:
  Unattended upgrades crash

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  Based this bug report upon https://bugs.launchpad.net/ubuntu/+source
  /unattended-upgrades/+bug/1052360/comments/17

  Installed latest updates on Xubuntu Trusty, immediately during the
  update process the system detected an error, after reboot an error
  report again emerged, hence reporting this bug as suggested above.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unattended-upgrades 0.82.1ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue May 27 12:40:58 2014
  InstallationDate: Installed on 2014-05-17 (10 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1544677] Re: webbrowser-app crashed with SIGABRT in base::debug::BreakDebugger()

[Michał Sawicz]

** Attachment added: "application-legacy-webbrowser-app-.log.1"
   
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1544677/+attachment/4569889/+files/application-legacy-webbrowser-app-.log.1

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

Title:
  webbrowser-app crashed with SIGABRT in base::debug::BreakDebugger()

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  This happens on startup under unity8 mir session on desktop.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: webbrowser-app 0.23+16.04.20160129.1-0ubuntu1
  Uname: Linux 4.4.0-4-generic x86_64
  Architecture: amd64
  Date: Thu Feb 11 17:07:51 2016
  ExecutablePath: /usr/bin/webbrowser-app
  ExecutableTimestamp: 1454061140
  ProcCmdline: webbrowser-app
  ProcCwd: /home/kodi
  RetraceOutdatedPackages:
   no debug symbol package found for libtrust-store2
   no debug symbol package found for libflac8
  Signal: 6
  SourcePackage: webbrowser-app
  StacktraceTop:
   base::debug::BreakDebugger () at 
../../../../third_party/chromium/src/base/debug/debugger_posix.cc:247
   logging::LogMessage::~LogMessage (this=0x7ffd08aa5c10, __in_chrg=) at ../../../../third_party/chromium/src/base/logging.cc:721
   oxide::Compositor::DidFailToInitializeOutputSurface (this=0x55977f7b0160) at 
../../../../shared/browser/compositor/oxide_compositor.cc:172
   cc::ThreadProxy::DidInitializeOutputSurface (this=0x55977f66c790, 
success=, capabilities=...) at 
../../../../third_party/chromium/src/cc/trees/thread_proxy.cc:208
   base::Callback::Run() const (this=0x7ffd08aa6058) at 
../../../../third_party/chromium/src/base/callback.h:396
  UserGroups: nopasswdlogin

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

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

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

[Jarno Suni]

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

** This bug has been marked a duplicate of bug 1054927
   Autoupdater fills /boot and crashes because old kernel images are never 
removed

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

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted installation or on any installation, when /boot partition
  gets full

Status in unattended-upgrades package in Ubuntu:
  Fix Committed

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

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

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

[Touch-packages] [Bug 1544677] Re: webbrowser-app crashed with SIGABRT in base::debug::BreakDebugger()

[Olivier Tilloy]

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

** This bug has been marked a duplicate of bug 1520537
   webbrowser-app crashes after 1 sec on unity8

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

Title:
  webbrowser-app crashed with SIGABRT in base::debug::BreakDebugger()

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  This happens on startup under unity8 mir session on desktop.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: webbrowser-app 0.23+16.04.20160129.1-0ubuntu1
  Uname: Linux 4.4.0-4-generic x86_64
  Architecture: amd64
  Date: Thu Feb 11 17:07:51 2016
  ExecutablePath: /usr/bin/webbrowser-app
  ExecutableTimestamp: 1454061140
  ProcCmdline: webbrowser-app
  ProcCwd: /home/kodi
  RetraceOutdatedPackages:
   no debug symbol package found for libtrust-store2
   no debug symbol package found for libflac8
  Signal: 6
  SourcePackage: webbrowser-app
  StacktraceTop:
   base::debug::BreakDebugger () at 
../../../../third_party/chromium/src/base/debug/debugger_posix.cc:247
   logging::LogMessage::~LogMessage (this=0x7ffd08aa5c10, __in_chrg=) at ../../../../third_party/chromium/src/base/logging.cc:721
   oxide::Compositor::DidFailToInitializeOutputSurface (this=0x55977f7b0160) at 
../../../../shared/browser/compositor/oxide_compositor.cc:172
   cc::ThreadProxy::DidInitializeOutputSurface (this=0x55977f66c790, 
success=, capabilities=...) at 
../../../../third_party/chromium/src/cc/trees/thread_proxy.cc:208
   base::Callback::Run() const (this=0x7ffd08aa6058) at 
../../../../third_party/chromium/src/base/callback.h:396
  UserGroups: nopasswdlogin

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

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

[Touch-packages] [Bug 1054927] Re: Autoupdater fills /boot and crashes because old kernel images are never removed

[Jarno Suni]

** Also affects: unattended-upgrades (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Autoupdater fills /boot and crashes because old kernel images are
  never removed

Status in unattended-upgrades package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1) Install Ubuntu with the default LVM encryption recipe
  2) Set Ubuntu to automatically install security updates on the background
  3) Use ubuntu for 5 months

  Actual results:
  The system automatically installs security updates for the kernel under 
/boot. It's never removes previous kernel images. After about five months, the 
/boot partition created by the install recipe (i.e. sized according to the 
judgment of Ubuntu developers—not me) fills up and the unattended updater 
crashes during the next kernel update.

  Expected results:
  Expected the unattended updater to leave the nearest kernel and the previous 
one on /boot and to automatically remove older kernel images. Expected the 
system installer to set up /boot such that it never runs out of space when the 
system updater operates automatically.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: update-manager 1:0.156.14.9
  ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
  Uname: Linux 3.2.0-31-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: amd64
  Date: Sun Sep 23 12:53:52 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  PackageArchitecture: all
  SourcePackage: update-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1544033] Re: Account details page needs design love

[Alberto Mardegan]

** Changed in: ubuntu-system-settings-online-accounts (Ubuntu)
 Assignee: (unassigned) => Alberto Mardegan (mardy)

** Changed in: ubuntu-system-settings-online-accounts
 Assignee: (unassigned) => Alberto Mardegan (mardy)

** Changed in: ubuntu-system-settings-online-accounts
   Status: Confirmed => In Progress

** Changed in: ubuntu-system-settings-online-accounts (Ubuntu)
   Status: Confirmed => In Progress

** Also affects: webapps-sprint
   Importance: Undecided
   Status: New

** Changed in: webapps-sprint
 Assignee: (unassigned) => Alberto Mardegan (mardy)

** Changed in: webapps-sprint
Milestone: None => sprint-19

** Changed in: webapps-sprint
   Importance: Undecided => High

** Changed in: webapps-sprint
   Status: New => In Progress

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

Title:
  Account details page needs design love

Status in Online Accounts setup for Ubuntu Touch:
  In Progress
Status in webapps-sprint:
  In Progress
Status in pay-ui package in Ubuntu:
  New
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  In Progress

Bug description:
  See attached screenshot. There's multiple issues with this page:

  * Empty space at the top
  * missing icon for PayUI
  * PayUI displays appid instead of user friendly name

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

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

[Touch-packages] [Bug 1544875] [NEW] unity8-dash flickers when changing modes

[Daniel van Vugt]

Public bug reported:

unity8-dash flickers when changing modes.

On my desktop (for some unknown reason) I only have three icons in the
dash, so regardless of the current mode they always all fit into the
dash window. When I switch from "All" to "Communication" and back
though, I see a frame or so of flickering particularly under the orange
Ubuntu Store icon.

During the brief flicker, the "A" icon is stretched horizontally, and
then quickly resolves itself.

Is this related to bug 1532974?

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

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

Title:
  unity8-dash flickers when changing modes

Status in unity8 package in Ubuntu:
  New

Bug description:
  unity8-dash flickers when changing modes.

  On my desktop (for some unknown reason) I only have three icons in the
  dash, so regardless of the current mode they always all fit into the
  dash window. When I switch from "All" to "Communication" and back
  though, I see a frame or so of flickering particularly under the
  orange Ubuntu Store icon.

  During the brief flicker, the "A" icon is stretched horizontally, and
  then quickly resolves itself.

  Is this related to bug 1532974?

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

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

[Touch-packages] [Bug 1459809] Re: [greeter infographic] Remove entries with zero count

[Bartosz Kosiorek]

** Changed in: libusermetrics (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  [greeter infographic] Remove entries with zero count

Status in Ubuntu UX:
  Won't Fix
Status in libusermetrics package in Ubuntu:
  Invalid

Bug description:
  I would like to have a setting so the phone only displays entries with
  at least one occurrence. I know that having "0" is information too,
  but I don’t need my phone to tell my I haven’t gotten any sms/taken no
  photos/played no songs today.

  - Design comment -
    04/08/2015

  It can't be fixed as a single bug. The desired resolution and specs
  will be updated as soon as they are available.
  https://canonical.leankit.com/Boards/View/109386535/113890502

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

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

[Touch-packages] [Bug 1544878] [NEW] Mir servers crash if I press the side mouse button (thumb)

[Daniel van Vugt]

Public bug reported:

Mir servers crash if I press the side mouse button (thumb).

There are two of them on the side of my Intellimouse Explorer 3.0. The
kernel calls them BTN_SIDE and BTN_EXTRA. And X calls them buttons 8 and
9.

When the crash happens I see in unity8.log:

[1455268365.782990]  MirSurfaceAPI: Caught exception at client library 
boundary (in mir_surface_release): 
/build/mir-wMQ7xO/mir-0.19.2+16.04.20160210/src/client/rpc/stream_socket_transport.cpp(168):
 Throw in function virtual void 
mir::client::rpc::StreamSocketTransport::send_message(const 
std::vector&, const std::vector&)
Dynamic exception type: 
boost::exception_detail::clone_impl
std::exception::what: Failed to send message to server: Broken pipe
32, "Broken pipe"
*** Error in `unity8': free(): invalid size: 0x7fcb4c03fe90 ***

Also happens with the Mir demo servers; they segfault but without a
usable stack trace due to exception handling.

** Affects: mir
 Importance: High
 Status: New

** Affects: mir (Ubuntu)
 Importance: High
 Status: New


** Tags: input

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

** Summary changed:

- Unity8 crashes if I press the side mouse button (thumb) 
+ Mir servers crash if I press the side mouse button (thumb)

** Package changed: unity8 (Ubuntu) => mir (Ubuntu)

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

** Tags added: input

** Description changed:

- Unity8 crashes if I press the side mouse button (thumb).
+ Mir servers crash if I press the side mouse button (thumb).
  
  There are two of them on the side of my Intellimouse Explorer 3.0. The
  kernel calls them BTN_SIDE and BTN_EXTRA. And X calls them buttons 8 and
  9.
  
  When the crash happens I see in unity8.log:
  
  [1455268365.782990]  MirSurfaceAPI: Caught exception at client library 
boundary (in mir_surface_release): 
/build/mir-wMQ7xO/mir-0.19.2+16.04.20160210/src/client/rpc/stream_socket_transport.cpp(168):
 Throw in function virtual void 
mir::client::rpc::StreamSocketTransport::send_message(const 
std::vector&, const std::vector&)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: Failed to send message to server: Broken pipe
  32, "Broken pipe"
  *** Error in `unity8': free(): invalid size: 0x7fcb4c03fe90 ***
+ 
+ Also happens with the Mir demo servers; they segfault but without a
+ usable stack trace due to exception handling.

** Changed in: mir
   Importance: Undecided => High

** Changed in: mir
Milestone: None => 0.20.0

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

Title:
  Mir servers crash if I press the side mouse button (thumb)

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

Bug description:
  Mir servers crash if I press the side mouse button (thumb).

  There are two of them on the side of my Intellimouse Explorer 3.0. The
  kernel calls them BTN_SIDE and BTN_EXTRA. And X calls them buttons 8
  and 9.

  When the crash happens I see in unity8.log:

  [1455268365.782990]  MirSurfaceAPI: Caught exception at client library 
boundary (in mir_surface_release): 
/build/mir-wMQ7xO/mir-0.19.2+16.04.20160210/src/client/rpc/stream_socket_transport.cpp(168):
 Throw in function virtual void 
mir::client::rpc::StreamSocketTransport::send_message(const 
std::vector&, const std::vector&)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: Failed to send message to server: Broken pipe
  32, "Broken pipe"
  *** Error in `unity8': free(): invalid size: 0x7fcb4c03fe90 ***

  Also happens with the Mir demo servers; they segfault but without a
  usable stack trace due to exception handling.

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

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

[Touch-packages] [Bug 1544875] Re: Cards flicker when changing department in the dash

[Michał Sawicz]

No, unrelated to that bug, what you reported here is internal to the
dash.

** Summary changed:

- unity8-dash flickers when changing modes
+ Cards flicker when changing department in the dash

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

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

** Description changed:

- unity8-dash flickers when changing modes.
+ unity8-dash flickers when changing departments.
  
  On my desktop (for some unknown reason) I only have three icons in the
- dash, so regardless of the current mode they always all fit into the
- dash window. When I switch from "All" to "Communication" and back
- though, I see a frame or so of flickering particularly under the orange
- Ubuntu Store icon.
+ dash, so regardless of the current department they always all fit into
+ the dash window. When I switch from "All" to "Communication" and back
+ though, I see a frame or so of the orange Ubuntu Store icon getting
+ stretched horizontally, and then quickly resolving itself.
  
- During the brief flicker, the "A" icon is stretched horizontally, and
- then quickly resolves itself.
- 
- Is this related to bug 1532974?
+ Is this related to bug #1532974?

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

Title:
  Cards flicker when changing department in the dash

Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  unity8-dash flickers when changing departments.

  On my desktop (for some unknown reason) I only have three icons in the
  dash, so regardless of the current department they always all fit into
  the dash window. When I switch from "All" to "Communication" and back
  though, I see a frame or so of the orange Ubuntu Store icon getting
  stretched horizontally, and then quickly resolving itself.

  Is this related to bug #1532974?

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

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

[Touch-packages] [Bug 1054927] Re: Autoupdater fills /boot and crashes because old kernel images are never removed

[Launchpad Bug Tracker]

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

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Confirmed

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

Title:
  Autoupdater fills /boot and crashes because old kernel images are
  never removed

Status in unattended-upgrades package in Ubuntu:
  Confirmed
Status in update-manager package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1) Install Ubuntu with the default LVM encryption recipe
  2) Set Ubuntu to automatically install security updates on the background
  3) Use ubuntu for 5 months

  Actual results:
  The system automatically installs security updates for the kernel under 
/boot. It's never removes previous kernel images. After about five months, the 
/boot partition created by the install recipe (i.e. sized according to the 
judgment of Ubuntu developers—not me) fills up and the unattended updater 
crashes during the next kernel update.

  Expected results:
  Expected the unattended updater to leave the nearest kernel and the previous 
one on /boot and to automatically remove older kernel images. Expected the 
system installer to set up /boot such that it never runs out of space when the 
system updater operates automatically.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: update-manager 1:0.156.14.9
  ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
  Uname: Linux 3.2.0-31-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: amd64
  Date: Sun Sep 23 12:53:52 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  PackageArchitecture: all
  SourcePackage: update-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1515977] Re: Shell rotates inappropriately in windowed mode

[Vesa Rautiainen]

** Changed in: ubuntu-ux
   Status: Fix Committed => Fix Released

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

Title:
  Shell rotates inappropriately in windowed mode

Status in The Avila project:
  Fix Committed
Status in Canonical System Image:
  Fix Committed
Status in Canonical Pocket Desktop:
  Fix Committed
Status in Ubuntu UX:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Install latest rc proposed on a nexus 4.
  Attach a bluetooth mouse - this triggers windowed mode.
  Orient device in landscape
  Open weather app - which is locked portrait in the .desktop file

  Shell rotates to become portrait and there's no way to get it out of
  that mode easily.

  The shell should probably ignore the .desktop setting which says that
  an app is portrait only if it's windowed.

  
  - Desired UX 
  The shell should not rotate automatically when it's in windowed mode. 
  It should just ignore .desktop file orientations since in windowed mode it's 
possible to show a portrait window in landscape mode and vice versa.

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

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

[Touch-packages] [Bug 1054927] Re: Autoupdater fills /boot and crashes because old kernel images are never removed

[Jarno Suni]

It also affects desktop users and users who install kernels "manually"
by Software Updater (update-manager).

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

Title:
  Autoupdater fills /boot and crashes because old kernel images are
  never removed

Status in unattended-upgrades package in Ubuntu:
  Confirmed
Status in update-manager package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1) Install Ubuntu with the default LVM encryption recipe
  2) Set Ubuntu to automatically install security updates on the background
  3) Use ubuntu for 5 months

  Actual results:
  The system automatically installs security updates for the kernel under 
/boot. It's never removes previous kernel images. After about five months, the 
/boot partition created by the install recipe (i.e. sized according to the 
judgment of Ubuntu developers—not me) fills up and the unattended updater 
crashes during the next kernel update.

  Expected results:
  Expected the unattended updater to leave the nearest kernel and the previous 
one on /boot and to automatically remove older kernel images. Expected the 
system installer to set up /boot such that it never runs out of space when the 
system updater operates automatically.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: update-manager 1:0.156.14.9
  ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
  Uname: Linux 3.2.0-31-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: amd64
  Date: Sun Sep 23 12:53:52 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  PackageArchitecture: all
  SourcePackage: update-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1519681] Re: Some media keys on BT keyboard do not work as expected

[John McAleely]

added unity8 & bluez. Not sure who decided what keycodes map to what.

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

** Changed in: avila
Milestone: None => ww06-2016

** Changed in: avila
   Status: New => Confirmed

** Changed in: avila
   Importance: Undecided => High

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

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

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

Title:
  Some media keys on BT keyboard do not work as expected

Status in The Avila project:
  Confirmed
Status in Canonical System Image:
  New
Status in Canonical Pocket Desktop:
  New
Status in bluez package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  $ system-image-cli -i
  current build number: 75
  device name: mako
  channel: ubuntu-touch/rc-proposed/ubuntu-pd
  last update: 2015-11-24 05:39:02
  version version: 75
  version ubuntu: 20151124
  version device: 20150911
  version custom: 20150929-2-vivid

  Steps to reproduce:
  1. Windowed mode is enabled with BT mouse/keyboard connected
  2. Launch music app to play all of a playlist
  3. Press Pause/Play, Fast forward/Rewind keys on BT keyboard

  Actual results:
  Press media keys(Pause/Play, Fast forward/Rewind) on BT keyboard has no 
control for playback 
  currently only Volume Up/ Down and Mute/Unmute media keys work

  BT keyboard type: Logitech K480 and Rapoo E6350

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

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

[Touch-packages] [Bug 1530807] Re: Bluetooth cannot be activated on several devices

[John McAleely]

** Changed in: avila
 Assignee: (unassigned) => Alejandro J. Cura (alecu)

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

Title:
  Bluetooth cannot be activated on several devices

Status in The Avila project:
  Confirmed
Status in Canonical System Image:
  Confirmed
Status in Canonical Pocket Desktop:
  Confirmed
Status in indicator-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  Using RC proposed 04/01/2016 bluetooth cannot be enabled.

  Tested on a nexus 7.

  Expected behavior:
  Bluetooth slider is moved to on
  Bluetooth activates
  Available devices appear in the list

  Experienced behavior: 
  Bluetooth slider is moved to on
  Activity spinners appear 
  Bluetooth slider moves to off.

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

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

[Touch-packages] [Bug 1543495] Re: boot splash not in native orientation

[kevin gunn]

** Changed in: unity-system-compositor (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  boot splash not in native orientation

Status in The Avila project:
  Confirmed
Status in Canonical System Image:
  Confirmed
Status in Unity System Compositor:
  Fix Committed
Status in Unity System Compositor 0.4 series:
  Fix Committed
Status in Unity System Compositor 0.5 series:
  Fix Committed
Status in unity-system-compositor package in Ubuntu:
  Fix Committed

Bug description:
  When the frieza is booted, the 'ubuntu + dots' splash from unity is
  displayed in portrait.

  The natural (out of the box) orientation for this device is landscape.

  I expected the splash to display in landscape.

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

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

[Touch-packages] [Bug 1535399] Re: Need screen size thresholds for switching to windowed automatically

[John McAleely]

** Changed in: avila
Milestone: None => ww04-2016

** Changed in: avila
 Assignee: Michał Sawicz (saviq) => (unassigned)

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

Title:
  Need screen size thresholds for switching to windowed automatically

Status in The Avila project:
  Fix Committed
Status in Canonical System Image:
  Fix Committed
Status in Canonical Pocket Desktop:
  Fix Committed
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Phones should never switch to windowed mode automatically. Smaller
  tablets should switch based on mouse and bigger screens should switch
  with either mouse or keyboard.

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

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

[Touch-packages] [Bug 1389761] Re: Don't show the volume overlay when changing the volume with the slider

[Matthew Paul Thomas]

Specification updated.


** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: In Progress => Triaged

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: Matthew Paul Thomas (mpt) => (unassigned)

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

Title:
  Don't show the volume overlay when changing the volume with the slider

Status in indicator-sound package in Ubuntu:
  Triaged
Status in ubuntu-system-settings package in Ubuntu:
  Triaged
Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged

Bug description:
  The overlay and the slider are redundant when the user changes the
  volume with the slider and the overlay shouldn't be displayed.

  : “The system volume control should
  automatically reflect, and adjust, the audio volume for the current
  output role through the current output device.”

  : “There should be no
  extra visible notification if the focused window contains a system
  volume control.”

  : “The “Silent Mode”
  switch should be followed by a system volume control for adjusting the
  volume…”

  : “The indicator and the
  system volume control — identical to its counterpart in System
  Settings — should both represent, and the slider should adjust, the
  volume…”

  The equivalent for track changes is bug 652978.

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: indicator-sound 12.10.2+14.10.20141021~rtm-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ActionStates: ({'mediaplayer-app.desktop.greeter': (true, signature '', 
[<{'running': , 'state': <'Paused'>}>]), 'mute': (true, '', []), 
'phone-settings': (true, '', []), 'mic-volume': (true, '', [<1.0>]), 'scroll': 
(true, 'i', []), 'high-volume': (true, '', []), 
'play-playlist.mediaplayer-app.desktop': (true, 's', []), 'desktop-settings': 
(true, '', []), 'mediaplayer-app.desktop': (true, '', [<{'running': , 
'state': <'Paused'>}>]), 'play.mediaplayer-app.desktop': (true, '', 
[<'Paused'>]), 'volume': (true, 'i', [<1.0>]), 'next.mediaplayer-app.desktop': 
(true, '', []), 'root': (true, '', [<{'title': <'Son'>, 'accessible-desc': 
<'Volume (100%)'>, 'icon': <('themed', <['audio-volume-high-panel', 
'audio-volume-high', 'audio-volume', 'audio']>)>, 'visible': }>]), 
'previous.mediaplayer-app.desktop': (true, '', []), 'silent-mode': (true, '', 
[])},)
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Wed Nov  5 16:58:35 2014
  InstallationDate: Installed on 2014-11-05 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141105-120036)
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1389761] Re: Don't show the volume overlay when changing the volume with the slider

[Matthew Paul Thomas]

** Description changed:

  The overlay and the slider are redundant when the user changes the
  volume with the slider and the overlay shouldn't be displayed.
+ 
+ : “The system volume control should automatically
+ reflect, and adjust, the audio volume for the current output role
+ through the current output device.”
+ 
+ : “There should be no extra
+ visible notification if the focused window contains a system volume
+ control.”
+ 
+ : “The “Silent Mode”
+ switch should be followed by a system volume control for adjusting the
+ volume…”
+ 
+ : “The indicator and the
+ system volume control — identical to its counterpart in System Settings
+ — should both represent, and the slider should adjust, the volume…”
  
  The equivalent for track changes is bug 652978.
  
  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: indicator-sound 12.10.2+14.10.20141021~rtm-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ActionStates: ({'mediaplayer-app.desktop.greeter': (true, signature '', 
[<{'running': , 'state': <'Paused'>}>]), 'mute': (true, '', []), 
'phone-settings': (true, '', []), 'mic-volume': (true, '', [<1.0>]), 'scroll': 
(true, 'i', []), 'high-volume': (true, '', []), 
'play-playlist.mediaplayer-app.desktop': (true, 's', []), 'desktop-settings': 
(true, '', []), 'mediaplayer-app.desktop': (true, '', [<{'running': , 
'state': <'Paused'>}>]), 'play.mediaplayer-app.desktop': (true, '', 
[<'Paused'>]), 'volume': (true, 'i', [<1.0>]), 'next.mediaplayer-app.desktop': 
(true, '', []), 'root': (true, '', [<{'title': <'Son'>, 'accessible-desc': 
<'Volume (100%)'>, 'icon': <('themed', <['audio-volume-high-panel', 
'audio-volume-high', 'audio-volume', 'audio']>)>, 'visible': }>]), 
'previous.mediaplayer-app.desktop': (true, '', []), 'silent-mode': (true, '', 
[])},)
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Wed Nov  5 16:58:35 2014
  InstallationDate: Installed on 2014-11-05 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141105-120036)
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Don't show the volume overlay when changing the volume with the slider

Status in indicator-sound package in Ubuntu:
  Triaged
Status in ubuntu-system-settings package in Ubuntu:
  Triaged
Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged

Bug description:
  The overlay and the slider are redundant when the user changes the
  volume with the slider and the overlay shouldn't be displayed.

  : “The system volume control should
  automatically reflect, and adjust, the audio volume for the current
  output role through the current output device.”

  : “There should be no
  extra visible notification if the focused window contains a system
  volume control.”

  : “The “Silent Mode”
  switch should be followed by a system volume control for adjusting the
  volume…”

  : “The indicator and the
  system volume control — identical to its counterpart in System
  Settings — should both represent, and the slider should adjust, the
  volume…”

  The equivalent for track changes is bug 652978.

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: indicator-sound 12.10.2+14.10.20141021~rtm-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ActionStates: ({'mediaplayer-app.desktop.greeter': (true, signature '', 
[<{'running': , 'state': <'Paused'>}>]), 'mute': (true, '', []), 
'phone-settings': (true, '', []), 'mic-volume': (true, '', [<1.0>]), 'scroll': 
(true, 'i', []), 'high-volume': (true, '', []), 
'play-playlist.mediaplayer-app.desktop': (true, 's', []), 'desktop-settings': 
(true, '', []), 'mediaplayer-app.desktop': (true, '', [<{'running': , 
'state': <'Paused'>}>]), 'play.mediaplayer-app.desktop': (true, '', 
[<'Paused'>]), 'volume': (true, 'i', [<1.0>]), 'next.mediaplayer-app.desktop': 
(true, '', []), 'root': (true, '', [<{'title': <'Son'>, 'accessible-desc': 
<'Volume (100%)'>, 'icon': <('themed', <['audio-volume-high-panel', 
'audio-volume-high', 'audio-volume', 'audio']>)>, 'visible': }>]), 
'previous.mediaplayer-app.desktop': (true, '', []), 'silent-mode': (true, '', 
[])},)
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Wed Nov  5 16:58:35 2014
  InstallationDate: Installed on 2014-11-05 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141105-120036)
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage 

[Touch-packages] [Bug 1466479] Re: "Searching for available drivers..." gives no indication of progress

[Matthew Paul Thomas]

** Changed in: software-properties (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  "Searching for available drivers..." gives no indication of progress

Status in software-properties package in Ubuntu:
  In Progress

Bug description:
  software-properties 0.92.37.3, Ubuntu 14.04

  1. Open System Settings > "Software & Updates".
  2. Choose "Additional Drivers".
  3. Wait 30 seconds.

  What you see:
  2. The text "Searching for available drivers..." centered in the box, but no 
other hint of progress.
  3. A list of drivers.

  What you should see:
  2. A progress bar, if the driver search has determinate progress; otherwise a 
spinner.

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

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

[Touch-packages] [Bug 1541994] Re: Two languages lack visible names in boot wizard

[Lukáš Tinkl]

Looks like missing glyphs in our font (the language name is displayed in
that language, natively)

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

Title:
  Two languages lack visible names in boot wizard

Status in The Avila project:
  Confirmed
Status in Canonical System Image:
  Confirmed
Status in unity8 package in Ubuntu:
  New

Bug description:
  Flash a frieza device with a recent image. Observe that in the opening
  page of the wizard, the language drop-down contains two entries that
  look wrong:

  1: (   )
  2: (   )

  They appear between hebrew and what looks like korean to me. On my
  image they were 7 places from the bottom of the list, and both appear
  together

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

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

[Touch-packages] [Bug 1544909] [NEW] Text overspills notifications

[Alan Pope ]

Public bug reported:

I get emails with long subject lines sometimes. Seems these overspill
the notification and should probably be truncated and ellipses added ...

See screenshot.

Screenshot taken on OTA-9 krillin.

** Affects: unity8 (Ubuntu)
 Importance: Medium
 Status: Triaged

** Attachment added: "screenshot20160212_100717822.png"
   
https://bugs.launchpad.net/bugs/1544909/+attachment/4569938/+files/screenshot20160212_100717822.png

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

Title:
  Text overspills notifications

Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  I get emails with long subject lines sometimes. Seems these overspill
  the notification and should probably be truncated and ellipses added
  ...

  See screenshot.

  Screenshot taken on OTA-9 krillin.

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

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

[Touch-packages] [Bug 1544909] Re: Text overspills notifications

[Michał Sawicz]

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

** Changed in: unity8 (Ubuntu)
   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/1544909

Title:
  Text overspills notifications

Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  I get emails with long subject lines sometimes. Seems these overspill
  the notification and should probably be truncated and ellipses added
  ...

  See screenshot.

  Screenshot taken on OTA-9 krillin.

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

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

[Touch-packages] [Bug 1524215] Re: Lenovo B50-70 inverted internal microphone

[Launchpad Bug Tracker]

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

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

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

Title:
  Lenovo B50-70 inverted internal microphone

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1002978 
  Attached the alsa-info txt to this bug
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marian 1981 F pulseaudio
   /dev/snd/pcmC1D0c:   marian 1981 F...m pulseaudio
   /dev/snd/pcmC1D0p:   marian 1981 F...m pulseaudio
   /dev/snd/controlC1:  marian 1981 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=10570c82-8e52-4379-9a8e-2e30baae9f63
  InstallationDate: Installed on 2015-09-10 (90 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20384
  Package: linux (not installed)
  ProcFB:
   0 inteldrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic 
root=UUID=1791e4c1-12de-4fef-88b1-31716c981648 ro quiet splash
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.149.3
  Tags:  wily
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: Upgraded to wily on 2015-10-24 (45 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/21/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9DCN34WW(V3.04)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo B50-70
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo B50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9DCN34WW(V3.04):bd07/21/2015:svnLENOVO:pn20384:pvrLenovoB50-70:rvnLENOVO:rnLenovoB50-70:rvrNODPK:cvnLENOVO:ct10:cvrLenovoB50-70:
  dmi.product.name: 20384
  dmi.product.version: Lenovo B50-70
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1506708] Re: Dash reset when pulling out launcher is too eager

[Vesa Rautiainen]

** Changed in: ubuntu-ux
   Status: In Progress => Fix Committed

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

Title:
  Dash reset when pulling out launcher is too eager

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

Bug description:
  1) Go the app store, look at an app page, maybe start writing a review
  2) Pull out the launcher

  If you are even a little enthusiastic with your pull, the dash resets,
  and you lose your place.

  I do it by accident often, and it's annoying. I think it would be
  reasonable to wait till the drag goes more than a launcher's width
  past the launcher or something similar.

  Desired design-

  Don't go home scope (left most) yet when gesture has passed the
  launcher width. Follow the same logic here as when performing left
  edge gesture when some other app than Dash is focused.

  I don't think there is exact spec or parameters anywhere but basic rules are:
  - Only trigger switch on finger release (the home scope can and should 
already be revealed during the gesture)
  - To go to home scope certain horizontal threshold value needs to be exceeded 
and gesture direction on release needs to be from left to right.

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

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

[Touch-packages] [Bug 1544747] Re: Strange device names for USB NICs

[Martin Pitt]

Subscribing server and snappy developers for collecting some opinions
about which default naming policy for USB devices we want.

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

Title:
  Strange device names for USB NICs

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Fresh install of Xenial on an intel NUC with 1 onboard GigE and one
  USB GigE NIC.

  I was setting up networking for MAAS and discovered that the device
  names were ridiculous:

  bladernr@critical-maas:/etc/udev$ ifconfig |grep HWaddr
  eno1  Link encap:Ethernet  HWaddr ec:a8:6b:fb:9f:66  
  enx8cae4cff4099 Link encap:Ethernet  HWaddr 8c:ae:4c:ff:40:99  

  In the previous Trusty install on this NUC with the same USB dongle,
  they were named eth0 and em1.  The predictable standard device names.

  Looking at udevadm:
  P: /devices/pci:00/:00:19.0/net/eno1
  E: DEVPATH=/devices/pci:00/:00:19.0/net/eno1
  E: ID_BUS=pci
  E: ID_MM_CANDIDATE=1
  E: ID_MODEL_FROM_DATABASE=82579LM Gigabit Network Connection
  E: ID_MODEL_ID=0x1502
  E: ID_NET_DRIVER=e1000e
  E: ID_NET_LABEL_ONBOARD=en L1U1
  E: ID_NET_LINK_FILE=/lib/systemd/network/99-default.link
  E: ID_NET_NAME_MAC=enxeca86bfb9f66
  E: ID_NET_NAME_ONBOARD=eno1
  E: ID_NET_NAME_PATH=enp0s25
  E: ID_OUI_FROM_DATABASE=ELITEGROUP COMPUTER SYSTEMS CO., LTD.
  E: ID_PATH=pci-:00:19.0
  E: ID_PATH_TAG=pci-_00_19_0
  E: ID_PCI_CLASS_FROM_DATABASE=Network controller
  E: ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller
  E: ID_VENDOR_FROM_DATABASE=Intel Corporation
  E: ID_VENDOR_ID=0x8086
  E: IFINDEX=2
  E: INTERFACE=eno1
  E: SUBSYSTEM=net
  E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/eno1
  E: TAGS=:systemd:
  E: USEC_INITIALIZED=5400250

  P: 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/net/enx8cae4cff4099
  E: 
DEVPATH=/devices/pci:00/:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/net/enx8cae4cff4099
  E: ID_BUS=usb
  E: ID_MM_CANDIDATE=1
  E: ID_MODEL=AX88178
  E: ID_MODEL_ENC=AX88178\x20
  E: ID_MODEL_FROM_DATABASE=AX88178
  E: ID_MODEL_ID=1780
  E: ID_NET_DRIVER=asix
  E: ID_NET_LINK_FILE=/lib/systemd/network/90-mac-for-usb.link
  E: ID_NET_NAME=enx8cae4cff4099
  E: ID_NET_NAME_MAC=enx8cae4cff4099
  E: ID_NET_NAME_PATH=enp0s29u1u5
  E: ID_OUI_FROM_DATABASE=Plugable Technologies
  E: ID_PATH=pci-:00:1d.0-usb-0:1.5:1.0
  E: ID_PATH_TAG=pci-_00_1d_0-usb-0_1_5_1_0
  E: ID_REVISION=0001
  E: ID_SERIAL=ASIX_Elec._Corp._AX88178_02
  E: ID_SERIAL_SHORT=02
  E: ID_TYPE=generic
  E: ID_USB_CLASS_FROM_DATABASE=Vendor Specific Class
  E: ID_USB_DRIVER=asix
  E: ID_USB_INTERFACES=:00:
  E: ID_USB_INTERFACE_NUM=00
  E: ID_USB_SUBCLASS_FROM_DATABASE=Vendor Specific Subclass
  E: ID_VENDOR=ASIX_Elec._Corp.
  E: ID_VENDOR_ENC=ASIX\x20Elec.\x20Corp.
  E: ID_VENDOR_FROM_DATABASE=ASIX Electronics Corp.
  E: ID_VENDOR_ID=0b95
  E: IFINDEX=3
  E: INTERFACE=enx8cae4cff4099
  E: SUBSYSTEM=net
  E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/enx8cae4cff4099 
/sys/subsystem/net/devices/enx8cae4cff4099
  E: TAGS=:systemd:
  E: USEC_INITIALIZED=8700146

  And finally, looking in /etc/udev:
  bladernr@critical-maas:/etc/udev$ sudo ls -ra /etc/udev/*
  /etc/udev/udev.conf

  /etc/udev/rules.d:
  ..  .

  /etc/udev/hwdb.d:
  ..  .

  There are NO rules at all in udev for persistent names.  Not even some
  samples and defaults.

  Looking at a completely different Xenial system with a single GigE NIC:
  bladernr@galactica:~$ ifconfig
  enp2s0Link encap:Ethernet  HWaddr 40:8d:5c:51:5b:0d  

  P: /devices/pci:00/:00:1b.2/:02:00.0/net/enp2s0
  E: DEVPATH=/devices/pci:00/:00:1b.2/:02:00.0/net/enp2s0
  E: ID_BUS=pci
  E: ID_MM_CANDIDATE=1
  E: ID_MODEL_FROM_DATABASE=Killer E220x Gigabit Ethernet Controller
  E: ID_MODEL_ID=0xe091
  E: ID_NET_DRIVER=alx
  E: ID_NET_LINK_FILE=/lib/systemd/network/99-default.link
  E: ID_NET_NAME_MAC=enx408d5c515b0d
  E: ID_NET_NAME_PATH=enp2s0
  E: ID_OUI_FROM_DATABASE=GIGA-BYTE TECHNOLOGY CO.,LTD.
  E: ID_PATH=pci-:02:00.0
  E: ID_PATH_TAG=pci-_02_00_0
  E: ID_PCI_CLASS_FROM_DATABASE=Network controller
  E: ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller
  E: ID_VENDOR_FROM_DATABASE=Qualcomm Atheros
  E: ID_VENDOR_ID=0x1969
  E: IFINDEX=2
  E: INTERFACE=enp2s0
  E: SUBSYSTEM=net
  E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/enp2s0
  E: TAGS=:systemd:
  E: USEC_INITIALIZED=752502

  and again, nothing in the udev rules:
  bladernr@galactica:~$ ls -a /etc/udev/*
  /etc/udev/udev.conf

  /etc/udev/hwdb.d:
  .  ..

  /etc/udev/rules.d:
  .  ..

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: udev 228-6ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  Date: Thu Feb 11 16:36:35 2016
  InstallationDate: Installed on 2016-02-10 (1 days 

[Touch-packages] [Bug 1528384] Re: unity-system-compositor crashed with std::runtime_error in mir::compositor::CompositingFunctor::wait_until_started() from usc::MirScreen::set_screen_power_mode (mir_

[Alan Griffiths]

Fix landed in 0.19.2

** Changed in: mir
   Status: In Progress => Fix Committed

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

Title:
  unity-system-compositor crashed with std::runtime_error in
  mir::compositor::CompositingFunctor::wait_until_started() from
  usc::MirScreen::set_screen_power_mode (mir_power_mode_on)

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Fix Committed
Status in Unity System Compositor:
  In Progress
Status in mir package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Confirmed

Bug description:
  Top crash over past week (ww02) on errors.u.c for rc-proposed
  channels.

  Started with u-s-c 0.2.0+15.04.20151216.1-0ubuntu1

  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity-system-compositor.  This problem was most recently
  seen with version 0.2.0+15.04.20151216.1-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/7bcfcf599b35b264c0be45d5290ad9ae3c50adcf
  contains more details.

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

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

[Touch-packages] [Bug 1504057] Re: [indicators] Bluetooth icon should turn blue when there's traffic happening

[Launchpad Bug Tracker]

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

** Changed in: indicator-bluetooth (Ubuntu)
   Status: New => Confirmed

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

Title:
  [indicators] Bluetooth icon should turn blue when there's traffic
  happening

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  Triaged
Status in indicator-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  The Bluetooth  icon in the panel is currently an outline icon when
  Bluetooth is turned on but nothing is connected, it will turn to the
  filled icon when something connects. Additionally it would be useful
  if the icon would turn blue when there is actual traffic happening.
  This is something I've been used to from previous phones and it helps
  greatly to identify the state of the connection. For instance, the
  Music player playing music to a Bluetooth headset would be immediately
  visible when you've put the headset away already and forgot to stop
  the music player.

  Also, it causes bug reports of failed connections to be more detailed
  as this gives details to the developer whether the connection failed
  when establishing the ACL link or if something failed after a profile
  has been connected already.

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

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

[Touch-packages] [Bug 1530807] Re: Bluetooth cannot be activated on several devices

[Dave Morley]

** Tags added: qa-frieza

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

Title:
  Bluetooth cannot be activated on several devices

Status in The Avila project:
  Confirmed
Status in Canonical System Image:
  Confirmed
Status in Canonical Pocket Desktop:
  Confirmed
Status in indicator-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  Using RC proposed 04/01/2016 bluetooth cannot be enabled.

  Tested on a nexus 7.

  Expected behavior:
  Bluetooth slider is moved to on
  Bluetooth activates
  Available devices appear in the list

  Experienced behavior: 
  Bluetooth slider is moved to on
  Activity spinners appear 
  Bluetooth slider moves to off.

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

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

[Touch-packages] [Bug 1544909] Re: Text overspills notifications

[Andrea Cimitan]

** Branch linked: lp:~cimi/unity8/fix1544909

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

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

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

Title:
  Text overspills notifications

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  I get emails with long subject lines sometimes. Seems these overspill
  the notification and should probably be truncated and ellipses added
  ...

  See screenshot.

  Screenshot taken on OTA-9 krillin.

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

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

[Touch-packages] [Bug 1536714] Re: Fix the user login experience on the greeter on a tablet

[John McAleely]

** Changed in: avila
Milestone: ww06-2016 => None

** No longer affects: avila

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

Title:
  Fix the user login experience on the greeter on a tablet

Status in Canonical System Image:
  Fix Committed
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu RTM:
  Fix Released
Status in unity8 package in Ubuntu RTM:
  In Progress

Bug description:
  The current UX for tablets or when converged with a mouse attached is
  a bit of a placeholder showing the default phablet user.

  We need to support two modes of the greeter that scales according to
  the available input devices. The first one is one that works across
  mobile and tablet devices in non-mouse connected / touch-centric
  state. Unlocking with no mouse connected would be exactly as it is
  today on the phone, which displays the Infographic until you touch the
  screen, and then you get a message that says "swipe to unlock" If you
  don't have a pin code set, the screen unlocks. if you have a pincode
  set, the touch pincode-entry pad appears.

  If a mouse is connected, however, you get the more "desktop-friendly"
  greeter with the infographic, user-name and password entry field (just
  like what we have today) on tablet.  If the user taps or clicks into
  the password edit box, the OSK is popped up (unless an external
  keyboard is also attached). If no password or pincode has been set,
  then instead of the password entry field, you would instead have a
  "login" button that clears the greeter.

  On a tablet with mouse connected and no pincode set, the user could
  either swipe away the greeter or tap on the login button. If the user
  has a password/pincode set and attempts to swipe away the greeter, we
  should put up a hint message asking the user to enter their
  password/pincode to continue.

  This incremental enhancement to recognize the mouse is more consistent
  with convergence because tablets are mobile devices, and if no mouse
  is attached, we should follow a touch-centric approach. In a mouse-
  connected state, we can assume the user will be favoring that device.

  ===

  Immediate problem: "phablet" name on the greeter login list. A bigger
  refactoring of the greeter for bigger screens will follow.

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

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

[Touch-packages] [Bug 1543984] Re: "Today" screen, display the top news image, cut in the half.

[Michał Sawicz]

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

This was fixed very recently, can you please give the output of:

$ apt-cache policy unity8

In case the fix was incomplete?

** This bug has been marked a duplicate of bug 1540490
   app icons getting their top cut off (Ubuntu Touch)

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

Title:
  "Today" screen, display the top news image, cut in the half.

Status in The Avila project:
  Confirmed
Status in Canonical System Image:
  Confirmed
Status in unity8 package in Ubuntu:
  New

Bug description:
  Enviroment
   
  Product: Freezer
  FW version:  Ubuntu 15.04 (r9)
  HW version:  MP
  Material:
   
  Description
   
  Steps to Reproduce:

  Use the tablet like an hour, and go back to the "Today" screen

  
  Actual Result:

  The image displayed is cut at half.

  Expected Result:

  The image must be shown completely.

  Reproducibility: 50%

  
  Additional info: 

  Please check the image attach.

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

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

[Touch-packages] [Bug 1542094] Re: [camera] LED & Flash toggles are shown even when no LED or Flash present on hardware

[John McAleely]

** Changed in: avila
 Assignee: (unassigned) => John McAleely (john.mcaleely)

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

Title:
  [camera] LED & Flash toggles are shown even when no LED or Flash
  present on hardware

Status in The Avila project:
  Confirmed
Status in Canonical System Image:
  Confirmed
Status in android package in Ubuntu:
  New
Status in camera-app package in Ubuntu:
  Invalid

Bug description:
  could be Freiza specific.

  We shouldn't be showing controls for flash, torchlight if they are not
  present on hardware, but apparently we are (according to design)

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

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

[Touch-packages] [Bug 1543495] Re: boot splash not in native orientation

[John McAleely]

** Changed in: avila
 Assignee: (unassigned) => kevin gunn (kgunn72)

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

Title:
  boot splash not in native orientation

Status in The Avila project:
  Confirmed
Status in Canonical System Image:
  Confirmed
Status in Unity System Compositor:
  Fix Committed
Status in Unity System Compositor 0.4 series:
  Fix Committed
Status in Unity System Compositor 0.5 series:
  Fix Committed
Status in unity-system-compositor package in Ubuntu:
  In Progress

Bug description:
  When the frieza is booted, the 'ubuntu + dots' splash from unity is
  displayed in portrait.

  The natural (out of the box) orientation for this device is landscape.

  I expected the splash to display in landscape.

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

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

[Touch-packages] [Bug 1541994] Re: Two languages lack visible names in boot wizard

[John McAleely]

** Changed in: avila
 Assignee: (unassigned) => Pat McGowan (pat-mcgowan)

** Changed in: avila
 Assignee: Pat McGowan (pat-mcgowan) => (unassigned)

** Changed in: canonical-devices-system-image
 Assignee: Pat McGowan (pat-mcgowan) => Michał Sawicz (saviq)

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

** Changed in: avila
 Assignee: (unassigned) => Michał Sawicz (saviq)

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

Title:
  Two languages lack visible names in boot wizard

Status in The Avila project:
  Confirmed
Status in Canonical System Image:
  Confirmed
Status in unity8 package in Ubuntu:
  New

Bug description:
  Flash a frieza device with a recent image. Observe that in the opening
  page of the wizard, the language drop-down contains two entries that
  look wrong:

  1: (   )
  2: (   )

  They appear between hebrew and what looks like korean to me. On my
  image they were 7 places from the bottom of the list, and both appear
  together

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

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

[Touch-packages] [Bug 1517205] Re: [mali] egl_demo_client_flicker has graphics corruption on android

[John McAleely]

** Changed in: avila
 Assignee: (unassigned) => kevin gunn (kgunn72)

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

Title:
  [mali] egl_demo_client_flicker has graphics corruption on android

Status in The Avila project:
  In Progress
Status in Canonical Pocket Desktop:
  In Progress
Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  Triaged

Bug description:
  Investigation of lp: #1406725 yielded two different problems, this is
  the second problem that affected mir_demo_client_flicker most heavily.

  When running mir_demo_client_flicker against "mir_demo_server
  --disable-overlays true", you could see cache-line artifacts, as well
  as an occasional tile-render-gpu artifact displayed on screen.

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

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

[Touch-packages] [Bug 1544942] [NEW] removes unneeded packages even if --dry-run is used

[Jarno Suni]

Public bug reported:

The two consequent runs of unattended-upgrade shows the difference:

$ sudo unattended-upgrade --dry-run -d
Initial blacklisted packages: 
Initial whitelisted packages: 
Starting unattended upgrades script
Allowed origins are: ['o=Ubuntu,a=wily-security']
pkgs that look like they should be upgraded: 
Fetched 0 B in 0s (0 B/s) 
fetch.run() result: 0
blacklist: []
whitelist: []
Option --dry-run given, *not* performing real actions
Packages that will be upgraded: 
marking linux-headers-4.2.0-16-generic for remove
marking linux-headers-4.2.0-16 for remove
marking linux-image-4.2.0-16-generic for remove
marking linux-image-extra-4.2.0-16-generic for remove
Packages that are auto removed: 'linux-headers-4.2.0-16-generic 
linux-headers-4.2.0-16 linux-image-4.2.0-16-generic 
linux-image-extra-4.2.0-16-generic'
/usr/bin/dpkg --status-fd 9 --force-depends --force-remove-essential --remove 
linux-headers-4.2.0-16-generic:amd64 linux-headers-4.2.0-16:all 
linux-image-extra-4.2.0-16-generic:amd64 linux-image-4.2.0-16-generic:amd64 
/usr/bin/dpkg --status-fd 11 --configure --pending 
Packages were successfully auto-removed
InstCount=0 DelCount=4 BrokenCount=0
$ sudo unattended-upgrade --dry-run -d
Initial blacklisted packages: 
Initial whitelisted packages: 
Starting unattended upgrades script
Allowed origins are: ['o=Ubuntu,a=wily-security']
pkgs that look like they should be upgraded: 
Fetched 0 B in 0s (0 B/s) 
fetch.run() result: 0
blacklist: []
whitelist: []
No packages found that can be upgraded unattended and no pending auto-removals

Expected behaviour is that dpkg is run with --dry-run, if unattended-
upgrade is run with that, so that it does not actually remove packages.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: unattended-upgrades 0.86.2ubuntu1.1
ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
Uname: Linux 4.2.0-27-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Feb 12 13:58:29 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-01-24 (18 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
PackageArchitecture: all
SourcePackage: unattended-upgrades
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.apt.apt.conf.d.50unattended.upgrades: 
2016-02-12T13:53:13.426454

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug wily

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

Title:
  removes unneeded packages even if --dry-run is used

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  The two consequent runs of unattended-upgrade shows the difference:

  $ sudo unattended-upgrade --dry-run -d
  Initial blacklisted packages: 
  Initial whitelisted packages: 
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=wily-security']
  pkgs that look like they should be upgraded: 
  Fetched 0 B in 0s (0 B/s) 
  fetch.run() result: 0
  blacklist: []
  whitelist: []
  Option --dry-run given, *not* performing real actions
  Packages that will be upgraded: 
  marking linux-headers-4.2.0-16-generic for remove
  marking linux-headers-4.2.0-16 for remove
  marking linux-image-4.2.0-16-generic for remove
  marking linux-image-extra-4.2.0-16-generic for remove
  Packages that are auto removed: 'linux-headers-4.2.0-16-generic 
linux-headers-4.2.0-16 linux-image-4.2.0-16-generic 
linux-image-extra-4.2.0-16-generic'
  /usr/bin/dpkg --status-fd 9 --force-depends --force-remove-essential --remove 
linux-headers-4.2.0-16-generic:amd64 linux-headers-4.2.0-16:all 
linux-image-extra-4.2.0-16-generic:amd64 linux-image-4.2.0-16-generic:amd64 
  /usr/bin/dpkg --status-fd 11 --configure --pending 
  Packages were successfully auto-removed
  InstCount=0 DelCount=4 BrokenCount=0
  $ sudo unattended-upgrade --dry-run -d
  Initial blacklisted packages: 
  Initial whitelisted packages: 
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=wily-security']
  pkgs that look like they should be upgraded: 
  Fetched 0 B in 0s (0 B/s) 
  fetch.run() result: 0
  blacklist: []
  whitelist: []
  No packages found that can be upgraded unattended and no pending auto-removals

  Expected behaviour is that dpkg is run with --dry-run, if unattended-
  upgrade is run with that, so that it does not actually remove
  packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: unattended-upgrades 0.86.2ubuntu1.1
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 

[Touch-packages] [Bug 1536662] Re: [regression] Black screen: Mir hangs and then crashes on login due to reading from /dev/random

[Alan Griffiths]

** Changed in: mir
Milestone: 0.20.0 => 0.21.0

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

Title:
  [regression] Black screen: Mir hangs and then crashes on login due to
  reading from /dev/random

Status in Mir:
  Triaged
Status in Unity System Compositor:
  Fix Committed
Status in mir package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  cookie_factory attempts to read data from /dev/random at boot, and
  blocks until it has enough random data or timesout after 30 seconds.

  How I can reproduce
  1. Run the Unity8 greeter as a mir server
  2. Reboot

  Expected behavior: Greeter is displayed as mir && USC run happily
  Actual behavior: Mir throws an exception after 30 seconds

  Work-around:
  Before logging in, move the mouse around lots, for at least 20 seconds. And 
after logging in, while you're looking at a black screen, move the mouse around 
furiously. This will populate the kernel entropy pool sufficiently to avoid the 
hang and crash.

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

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

[Touch-packages] [Bug 1544878] Re: Mir servers crash if I press the side mouse button (thumb)

[Alan Griffiths]

** Changed in: mir
Milestone: 0.20.0 => 0.21.0

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

Title:
  Mir servers crash if I press the side mouse button (thumb)

Status in Mir:
  New
Status in mir package in Ubuntu:
  Confirmed

Bug description:
  Mir servers crash if I press the side mouse button (thumb).

  There are two of them on the side of my Intellimouse Explorer 3.0. The
  kernel calls them BTN_SIDE and BTN_EXTRA. And X calls them buttons 8
  and 9.

  When the crash happens I see in unity8.log:

  [1455268365.782990]  MirSurfaceAPI: Caught exception at client library 
boundary (in mir_surface_release): 
/build/mir-wMQ7xO/mir-0.19.2+16.04.20160210/src/client/rpc/stream_socket_transport.cpp(168):
 Throw in function virtual void 
mir::client::rpc::StreamSocketTransport::send_message(const 
std::vector&, const std::vector&)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: Failed to send message to server: Broken pipe
  32, "Broken pipe"
  *** Error in `unity8': free(): invalid size: 0x7fcb4c03fe90 ***

  Also happens with the Mir demo servers; they segfault but without a
  usable stack trace due to exception handling.

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

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

[Touch-packages] [Bug 1544747] Re: No udev persistent rules in Xenial = strange device names for NICs

[Martin Pitt]

See https://lists.ubuntu.com/archives/ubuntu-devel/2015-May/038761.html
for more details about the change, and
/usr/share/doc/udev/README.Debian.gz how the current schema works, and
how to set custom names or change the policy, if you desire so.

So the lack of /etc/udev/rules.d/70-persistent-net.rules is intended,
unless this was an upgrade from trusty -- in that case the file should
of course continue to exist (we don't remove it automatically on
upgrades). But it sounds like this was a new install.

So for the most part this all works as intended. The main point of
contention is the naming of USB devices ("enx8cae4cff4099") -- see the
ML discussion for why this is currently done. I'm fine to change this to
a different policy if desired by the server or other teams, but
everytime I asked about it I get a resounding silence as an answer :-)
Retitling the bug accordingly.

I. e. an alternative policy would be: Always use the kernel names for
USB devices. As long as you have only one, it will always be eth0, but
as soon as you have multiple ones *and* you need to refer to their names
in configuration files, then you need to define a naming policy
yourself, as the kernel names are not persistent and predictable.

In theory we could also use the path based names for USB devices, which
would name the interface according to the port you plug it into. That'd
be a good policy for things like a RasPi where you deploy the same image
(with that policy) to lots of devices and port location would make
sense. This policy makes less sense on a laptop where you might plug in
your mobile phone on different ports every time -- but then again those
usually use NetworkManager and dynamic configurations where you don't
care about device names.

** Summary changed:

- No udev persistent rules in Xenial = strange device names for NICs
+ Strange device names for USB NICs

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

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

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

Title:
  Strange device names for USB NICs

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Fresh install of Xenial on an intel NUC with 1 onboard GigE and one
  USB GigE NIC.

  I was setting up networking for MAAS and discovered that the device
  names were ridiculous:

  bladernr@critical-maas:/etc/udev$ ifconfig |grep HWaddr
  eno1  Link encap:Ethernet  HWaddr ec:a8:6b:fb:9f:66  
  enx8cae4cff4099 Link encap:Ethernet  HWaddr 8c:ae:4c:ff:40:99  

  In the previous Trusty install on this NUC with the same USB dongle,
  they were named eth0 and em1.  The predictable standard device names.

  Looking at udevadm:
  P: /devices/pci:00/:00:19.0/net/eno1
  E: DEVPATH=/devices/pci:00/:00:19.0/net/eno1
  E: ID_BUS=pci
  E: ID_MM_CANDIDATE=1
  E: ID_MODEL_FROM_DATABASE=82579LM Gigabit Network Connection
  E: ID_MODEL_ID=0x1502
  E: ID_NET_DRIVER=e1000e
  E: ID_NET_LABEL_ONBOARD=en L1U1
  E: ID_NET_LINK_FILE=/lib/systemd/network/99-default.link
  E: ID_NET_NAME_MAC=enxeca86bfb9f66
  E: ID_NET_NAME_ONBOARD=eno1
  E: ID_NET_NAME_PATH=enp0s25
  E: ID_OUI_FROM_DATABASE=ELITEGROUP COMPUTER SYSTEMS CO., LTD.
  E: ID_PATH=pci-:00:19.0
  E: ID_PATH_TAG=pci-_00_19_0
  E: ID_PCI_CLASS_FROM_DATABASE=Network controller
  E: ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller
  E: ID_VENDOR_FROM_DATABASE=Intel Corporation
  E: ID_VENDOR_ID=0x8086
  E: IFINDEX=2
  E: INTERFACE=eno1
  E: SUBSYSTEM=net
  E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/eno1
  E: TAGS=:systemd:
  E: USEC_INITIALIZED=5400250

  P: 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/net/enx8cae4cff4099
  E: 
DEVPATH=/devices/pci:00/:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/net/enx8cae4cff4099
  E: ID_BUS=usb
  E: ID_MM_CANDIDATE=1
  E: ID_MODEL=AX88178
  E: ID_MODEL_ENC=AX88178\x20
  E: ID_MODEL_FROM_DATABASE=AX88178
  E: ID_MODEL_ID=1780
  E: ID_NET_DRIVER=asix
  E: ID_NET_LINK_FILE=/lib/systemd/network/90-mac-for-usb.link
  E: ID_NET_NAME=enx8cae4cff4099
  E: ID_NET_NAME_MAC=enx8cae4cff4099
  E: ID_NET_NAME_PATH=enp0s29u1u5
  E: ID_OUI_FROM_DATABASE=Plugable Technologies
  E: ID_PATH=pci-:00:1d.0-usb-0:1.5:1.0
  E: ID_PATH_TAG=pci-_00_1d_0-usb-0_1_5_1_0
  E: ID_REVISION=0001
  E: ID_SERIAL=ASIX_Elec._Corp._AX88178_02
  E: ID_SERIAL_SHORT=02
  E: ID_TYPE=generic
  E: ID_USB_CLASS_FROM_DATABASE=Vendor Specific Class
  E: ID_USB_DRIVER=asix
  E: ID_USB_INTERFACES=:00:
  E: ID_USB_INTERFACE_NUM=00
  E: ID_USB_SUBCLASS_FROM_DATABASE=Vendor Specific Subclass
  E: ID_VENDOR=ASIX_Elec._Corp.
  E: ID_VENDOR_ENC=ASIX\x20Elec.\x20Corp.
  E: ID_VENDOR_FROM_DATABASE=ASIX Electronics Corp.
  E: ID_VENDOR_ID=0b95
  E: IFINDEX=3
  E: INTERFACE=enx8cae4cff4099
  E: SUBSYSTEM=net
  E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/enx8cae4cff4099 

[Touch-packages] [Bug 1544777] Re: package libunity-scopes1.0 1.0.2+16.04.20151218.2-0ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Colin Watson]

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

** This bug has been marked a duplicate of bug 1544776
   package click 0.4.42+16.04.20151229-0ubuntu1 failed to install/upgrade: 
subprocess installed pre-removal script returned error exit status 1

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

Title:
  package libunity-scopes1.0 1.0.2+16.04.20151218.2-0ubuntu1 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 1

Status in click package in Ubuntu:
  New
Status in unity-scopes-api package in Ubuntu:
  Invalid

Bug description:
  happened while upgrading from xenial-proposed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libunity-scopes1.0 1.0.2+16.04.20151218.2-0ubuntu1
  Uname: Linux 4.4.1-040401-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  Date: Thu Feb 11 23:32:19 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-01-26 (16 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.1.10
  SourcePackage: unity-scopes-api
  Title: package libunity-scopes1.0 1.0.2+16.04.20151218.2-0ubuntu1 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1544776] Re: package click 0.4.42+16.04.20151229-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

[Colin Watson]

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

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

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

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

Title:
  package click 0.4.42+16.04.20151229-0ubuntu1 failed to
  install/upgrade: subprocess installed pre-removal script returned
  error exit status 1

Status in click package in Ubuntu:
  In Progress

Bug description:
  happend while upgrading from xenial-proposed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: click 0.4.42+16.04.20151229-0ubuntu1
  Uname: Linux 4.4.1-040401-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  Date: Thu Feb 11 23:28:44 2016
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2016-01-26 (16 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.1.10
  SourcePackage: click
  Title: package click 0.4.42+16.04.20151229-0ubuntu1 failed to 
install/upgrade: subprocess installed pre-removal script returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1544925] [NEW] location-service and system-settings have opposite needs from ofono on a non-cellular device

[John McAleely]

Public bug reported:

In a set of recent changes to support devices which have no modem, but
do have GPS & HERE servcies enabled:

 - System Settings now tries not to display 'cellular' options
 - Location service has a hard dependency on ofono starting (bug #1544712)

The correct behaviour is for location services to function, and system
settings to not display 'cellular' options.

In the medium term, ofono will be disabled on devices like this: bug
#1544210

** Affects: avila
 Importance: Critical
 Status: Confirmed

** Affects: canonical-devices-system-image
 Importance: Critical
 Status: Confirmed

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

** Changed in: avila
   Status: New => Confirmed

** Changed in: avila
   Importance: Undecided => Critical

** Changed in: avila
Milestone: None => ww04-2016

** Information type changed from Proprietary to Public

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

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

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

** Changed in: canonical-devices-system-image
Milestone: None => ww04-2016

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

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

Title:
  location-service and system-settings have opposite needs from ofono on
  a non-cellular device

Status in The Avila project:
  Confirmed
Status in Canonical System Image:
  Confirmed
Status in location-service package in Ubuntu:
  New

Bug description:
  In a set of recent changes to support devices which have no modem, but
  do have GPS & HERE servcies enabled:

   - System Settings now tries not to display 'cellular' options
   - Location service has a hard dependency on ofono starting (bug #1544712)

  The correct behaviour is for location services to function, and system
  settings to not display 'cellular' options.

  In the medium term, ofono will be disabled on devices like this: bug
  #1544210

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

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

[Touch-packages] [Bug 1541588] Re: [System Settings] Changes needed for the UI on a tablet device

[John McAleely]

See bug #1544925 for the developing story re ofono

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

Title:
  [System Settings] Changes needed for the UI on a tablet device

Status in Canonical System Image:
  In Progress
Status in Ubuntu UX:
  New
Status in indicator-network package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released

Bug description:
  Note for design: can we simply avoid referring to the/this phone as in
  most uses its not necessary for clarity, and then the same text can
  always apply..

  Main panel:
  Hide Cellular
  Hide Hotspot
  Hide Phone
  About this phone -> About this device or just About
  Reset phone -> Reset device or just Reset

  Background
  Ensure default for images is landscape

  Sound:
  Hide Ringer, Phone Calls and Messages sections

  Security and Privacy
  Hide SIM PIN
  Locking and unlocking > Lock security "Unlock the phone using" --> "Unlock 
the device using"
  Locking and unlocking > Lock when idle  "Lock the phone when..." --> "Lock 
the device when ..."
  "Phone won't lock..." --> Device won't lock ..."

  About this device
  Hide IMEI
  Developer mode >  "this phone" --> "this device"

  A minor point but what happens when we search in settings for hidden
  stuff

  
  
  Note from design:

  - The text in the UI should never refer to "Phone", "Tablet" or
  "Desktop".  Instead the word "Device" should be used.

  - e.g. "About This Computer" or "About This Phone" is incorrect. This
  wording should be changed to "About this device" in both the indicator
  and System Settings to be convergence friendly.

  - This change applies to all device references in the UI.

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

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

[Touch-packages] [Bug 1523573] Re: Doesn't let you share several images

[Launchpad Bug Tracker]

** Branch linked: lp:~artmello/gallery-app/gallery-app-fix_1523573

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

Title:
  Doesn't let you share several images

Status in Canonical System Image:
  Confirmed
Status in camera-app package in Ubuntu:
  Confirmed
Status in gallery-app package in Ubuntu:
  In Progress
Status in messaging-app package in Ubuntu:
  Confirmed

Bug description:
  Using ota8 on bq devices, the share menu is disabled when more than
  one image is selected.

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

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

[Touch-packages] [Bug 1442050] Re: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2

[dino99]

Still get that error on xenial 64 bits logged with gnome-shell

colord[834]: (colord:834): Cd-WARNING **: failed to get session [pid
2855]: No such device or address


** Tags added: xenial

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

Title:
  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

Status in colord package in Ubuntu:
  Confirmed

Bug description:
  Get that error logged into journalctl

  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-6ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Thu Apr  9 11:57:02 2015
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic 
root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

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

[Touch-packages] [Bug 1523573] Re: Doesn't let you share several images

[Arthur Mello]

** Changed in: gallery-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 camera-app in Ubuntu.
https://bugs.launchpad.net/bugs/1523573

Title:
  Doesn't let you share several images

Status in Canonical System Image:
  Confirmed
Status in camera-app package in Ubuntu:
  Confirmed
Status in gallery-app package in Ubuntu:
  In Progress
Status in messaging-app package in Ubuntu:
  Confirmed

Bug description:
  Using ota8 on bq devices, the share menu is disabled when more than
  one image is selected.

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

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

[Touch-packages] [Bug 1543984] Re: "Today" screen, display the top news image, cut in the half.

[John McAleely]

@davemor2, could you get unity logs when you also saw this?

** Changed in: avila
 Assignee: Ethan Chang (ethan.chang) => (unassigned)

** Information type changed from Proprietary to Public

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

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

** Changed in: canonical-devices-system-image
Milestone: None => ww08-2016

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

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Michał Sawicz (saviq)

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

Title:
  "Today" screen, display the top news image, cut in the half.

Status in The Avila project:
  Confirmed
Status in Canonical System Image:
  Confirmed
Status in unity8 package in Ubuntu:
  New

Bug description:
  Enviroment
   
  Product: Freezer
  FW version:  Ubuntu 15.04 (r9)
  HW version:  MP
  Material:
   
  Description
   
  Steps to Reproduce:

  Use the tablet like an hour, and go back to the "Today" screen

  
  Actual Result:

  The image displayed is cut at half.

  Expected Result:

  The image must be shown completely.

  Reproducibility: 50%

  
  Additional info: 

  Please check the image attach.

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

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

[Touch-packages] [Bug 1447839] Re: Mouse cursor never changes when moving over widgets in app windows

[Lukáš Tinkl]

This should work fine already in regular apps, not sure about xmir

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

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

Title:
  Mouse cursor never changes when moving over widgets in app windows

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in unity-system-compositor package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  currently on the unity8 desktop windowed mode, the mouse remains in
  it's "arrow" form not prompting the user when it's on the edge of a
  window where the window can be rescaled.

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

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

[Touch-packages] [Bug 1519681] Re: Some media keys on BT keyboard do not work as expected

[Michael Zanetti]

As of Bluez5, AVRCP does not inject keypresses any more, but bluez
connects to MPRIS.

The issue is either in our bluez setup or the media-hub mpris interface

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

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

Title:
  Some media keys on BT keyboard do not work as expected

Status in The Avila project:
  Confirmed
Status in Canonical System Image:
  New
Status in Canonical Pocket Desktop:
  New
Status in bluez package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  $ system-image-cli -i
  current build number: 75
  device name: mako
  channel: ubuntu-touch/rc-proposed/ubuntu-pd
  last update: 2015-11-24 05:39:02
  version version: 75
  version ubuntu: 20151124
  version device: 20150911
  version custom: 20150929-2-vivid

  Steps to reproduce:
  1. Windowed mode is enabled with BT mouse/keyboard connected
  2. Launch music app to play all of a playlist
  3. Press Pause/Play, Fast forward/Rewind keys on BT keyboard

  Actual results:
  Press media keys(Pause/Play, Fast forward/Rewind) on BT keyboard has no 
control for playback 
  currently only Volume Up/ Down and Mute/Unmute media keys work

  BT keyboard type: Logitech K480 and Rapoo E6350

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

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

[Touch-packages] [Bug 1517205] Re: [mali] egl_demo_client_flicker has graphics corruption on android

[kevin gunn]

** Changed in: mir (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  [mali] egl_demo_client_flicker has graphics corruption on android

Status in The Avila project:
  In Progress
Status in Canonical Pocket Desktop:
  In Progress
Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  Fix Committed

Bug description:
  Investigation of lp: #1406725 yielded two different problems, this is
  the second problem that affected mir_demo_client_flicker most heavily.

  When running mir_demo_client_flicker against "mir_demo_server
  --disable-overlays true", you could see cache-line artifacts, as well
  as an occasional tile-render-gpu artifact displayed on screen.

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

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

[Touch-packages] [Bug 1054927] Re: Autoupdater fills /boot and crashes because old kernel images are never removed

[Jarno Suni]

Corrective to my previous comment: If one installs kernels by Software
Updater, /boot becomes full in time by default thus preventing
installation of the new kernel. Bug #1389620

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

Title:
  Autoupdater fills /boot and crashes because old kernel images are
  never removed

Status in unattended-upgrades package in Ubuntu:
  Confirmed
Status in update-manager package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1) Install Ubuntu with the default LVM encryption recipe
  2) Set Ubuntu to automatically install security updates on the background
  3) Use ubuntu for 5 months

  Actual results:
  The system automatically installs security updates for the kernel under 
/boot. It's never removes previous kernel images. After about five months, the 
/boot partition created by the install recipe (i.e. sized according to the 
judgment of Ubuntu developers—not me) fills up and the unattended updater 
crashes during the next kernel update.

  Expected results:
  Expected the unattended updater to leave the nearest kernel and the previous 
one on /boot and to automatically remove older kernel images. Expected the 
system installer to set up /boot such that it never runs out of space when the 
system updater operates automatically.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: update-manager 1:0.156.14.9
  ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
  Uname: Linux 3.2.0-31-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: amd64
  Date: Sun Sep 23 12:53:52 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  PackageArchitecture: all
  SourcePackage: update-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1544925] Re: location-service and system-settings have opposite needs from ofono on a non-cellular device

[John McAleely]

bug for system settings changes bug #1541588

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

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

Title:
  location-service and system-settings have opposite needs from ofono on
  a non-cellular device

Status in The Avila project:
  Confirmed
Status in Canonical System Image:
  Confirmed
Status in location-service package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  In a set of recent changes to support devices which have no modem, but
  do have GPS & HERE servcies enabled:

   - System Settings now tries not to display 'cellular' options
   - Location service has a hard dependency on ofono starting (bug #1544712)

  The correct behaviour is for location services to function, and system
  settings to not display 'cellular' options.

  In the medium term, ofono will be disabled on devices like this: bug
  #1544210

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

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

[Touch-packages] [Bug 1544878] Re: Mir servers crash if I press the side mouse button (thumb)

[Launchpad Bug Tracker]

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

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

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

Title:
  Mir servers crash if I press the side mouse button (thumb)

Status in Mir:
  New
Status in mir package in Ubuntu:
  Confirmed

Bug description:
  Mir servers crash if I press the side mouse button (thumb).

  There are two of them on the side of my Intellimouse Explorer 3.0. The
  kernel calls them BTN_SIDE and BTN_EXTRA. And X calls them buttons 8
  and 9.

  When the crash happens I see in unity8.log:

  [1455268365.782990]  MirSurfaceAPI: Caught exception at client library 
boundary (in mir_surface_release): 
/build/mir-wMQ7xO/mir-0.19.2+16.04.20160210/src/client/rpc/stream_socket_transport.cpp(168):
 Throw in function virtual void 
mir::client::rpc::StreamSocketTransport::send_message(const 
std::vector&, const std::vector&)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: Failed to send message to server: Broken pipe
  32, "Broken pipe"
  *** Error in `unity8': free(): invalid size: 0x7fcb4c03fe90 ***

  Also happens with the Mir demo servers; they segfault but without a
  usable stack trace due to exception handling.

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

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

[Touch-packages] [Bug 1543984] Re: "Today" screen, display the top news image, cut in the half.

[Dave Morley]

** Attachment added: "unity8.log"
   
https://bugs.launchpad.net/avila/+bug/1543984/+attachment/4569966/+files/unity8.log

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

Title:
  "Today" screen, display the top news image, cut in the half.

Status in The Avila project:
  Confirmed
Status in Canonical System Image:
  Confirmed
Status in unity8 package in Ubuntu:
  New

Bug description:
  Enviroment
   
  Product: Freezer
  FW version:  Ubuntu 15.04 (r9)
  HW version:  MP
  Material:
   
  Description
   
  Steps to Reproduce:

  Use the tablet like an hour, and go back to the "Today" screen

  
  Actual Result:

  The image displayed is cut at half.

  Expected Result:

  The image must be shown completely.

  Reproducibility: 50%

  
  Additional info: 

  Please check the image attach.

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

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

[Touch-packages] [Bug 1543984] Re: "Today" screen, display the top news image, cut in the half.

[Dave Morley]

Done :)

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

Title:
  "Today" screen, display the top news image, cut in the half.

Status in The Avila project:
  Confirmed
Status in Canonical System Image:
  Confirmed
Status in unity8 package in Ubuntu:
  New

Bug description:
  Enviroment
   
  Product: Freezer
  FW version:  Ubuntu 15.04 (r9)
  HW version:  MP
  Material:
   
  Description
   
  Steps to Reproduce:

  Use the tablet like an hour, and go back to the "Today" screen

  
  Actual Result:

  The image displayed is cut at half.

  Expected Result:

  The image must be shown completely.

  Reproducibility: 50%

  
  Additional info: 

  Please check the image attach.

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

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

[Touch-packages] [Bug 1537028] Re: unity8 crashed while using pocket desktop

[John McAleely]

** Changed in: avila
   Status: Confirmed => Incomplete

** Changed in: avila
 Assignee: (unassigned) => Victor Tuson Palau (vtuson)

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

Title:
  unity8 crashed while using pocket desktop

Status in The Avila project:
  Incomplete
Status in Canonical System Image:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  while using the device on pocket desktop mode, unity8 restarted going
  back to the 4 dots ubuntu splash screen. loosing all open apps states
  and data

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

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

[Touch-packages] [Bug 1532868] Re: [Avila] OSK generates random touch events after switching from physical keyboard

[John McAleely]

** Changed in: avila
Milestone: ww06-2016 => None

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

Title:
  [Avila] OSK generates random touch events after switching from
  physical keyboard

Status in The Avila project:
  Invalid
Status in Canonical Pocket Desktop:
  Invalid
Status in Mir:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Steps:
  connect a USB keyboard 
  Use for a bit
  Disconnect keyboard
  try using the onboard keyboard

  Result:
  The keyboard starts producing random touch events as soon as you try to use 
it.

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

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

[Touch-packages] [Bug 1262116] Re: Nested servers prevent overlays or fullscreen bypass from working

[Alan Griffiths]

** Changed in: mir
Milestone: 0.20.0 => 0.21.0

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

Title:
  Nested servers prevent overlays or fullscreen bypass from working

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

Bug description:
  Nested servers prevent fullscreen bypass from working.

  This would explain why nesting fullscreen clients is measurably slower than 
non-nesting:
  Direct (bypass) 2600
  Direct (bypass off) 2400
  Nested (bypass) 2450
  Nested (bypass off) 2330

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

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

[Touch-packages] [Bug 1240909] Re: [performance] Restore support for better-than-triple buffering by default.

[Alan Griffiths]

** Changed in: mir
Milestone: 0.20.0 => 0.21.0

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

Title:
  [performance] Restore support for better-than-triple buffering by
  default.

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

Bug description:
  We really should restore support for double-buffering where possible.
  Presently we're on triple-buffering all the time.

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

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

[Touch-packages] [Bug 1540811] Re: [GDK] patch - avoid integer overflow when allocating a large block of memory

[Marc Deslauriers]

Since this is a security update, I'll sponsor these as security updates,
and not as SRUs.

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2013-7447

** Also affects: gtk+2.0 (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: gtk+2.0 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: gtk+2.0 (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: gtk+2.0 (Ubuntu Xenial)
   Importance: High
   Status: Fix Released

** Changed in: gtk+2.0 (Ubuntu Precise)
   Status: New => Confirmed

** Changed in: gtk+2.0 (Ubuntu Trusty)
   Status: New => Confirmed

** Changed in: gtk+2.0 (Ubuntu Wily)
   Status: New => Confirmed

** Changed in: gtk+2.0 (Ubuntu Precise)
   Importance: Undecided => Medium

** Changed in: gtk+2.0 (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: gtk+2.0 (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: gtk+2.0 (Ubuntu Precise)
 Assignee: (unassigned) => Marc Deslauriers (mdeslaur)

** Changed in: gtk+2.0 (Ubuntu Trusty)
 Assignee: (unassigned) => Marc Deslauriers (mdeslaur)

** Changed in: gtk+2.0 (Ubuntu Wily)
 Assignee: (unassigned) => Marc Deslauriers (mdeslaur)

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

Title:
  [GDK] patch - avoid integer overflow when allocating a large block of
  memory

Status in GTK+:
  Fix Released
Status in gtk+2.0 package in Ubuntu:
  Fix Released
Status in gtk+2.0 source package in Precise:
  Confirmed
Status in gtk+2.0 source package in Trusty:
  Confirmed
Status in gtk+2.0 source package in Wily:
  Confirmed
Status in gtk+2.0 source package in Xenial:
  Fix Released
Status in gtk+2.0 package in Debian:
  New

Bug description:
  [Impact]

  Due to a logic error, an attempt to allocate a large block of memory
  fails in gdk_cairo_set_source_pixbuf, leading to a crash of the app
  that called it, for example, eom [1].

  This issue had been fixed [2] in GTK+3, but GTK+2 apps that use the
  mentioned function still crash when trying to allocate a lot of
  memory. An example of such app is eom (Eye of MATE), an image viewer,
  which crashes when trying to load a large image.

  I propose fixing it in current Ubuntu releases with the patch which fixes the 
crash.
  The debdiffs are in the attachments in the comments below.

  [Test Case]

  Steps to reproduce:

  1. Have a 64-bit installation of Ubuntu.
  2. Install eom if it isn't installed.
  3. Download the archive from the attachment of this post and unpack it. 
(Firefox doesn't allow me to upload image as is - tries to make thumbnail of it 
right in the file open dialog, then crashes.)
  4. Open the unpacked image (27000_27000_1437947845.png) in eom.
  5. eom crashes. The full backtrace is at [3].

  You'll also see an error message: "failed to allocate
  18446744072330584320 bytes". This huge number appears due to overflow
  during multiplication of two 32-bit signed integers. In the patch,
  this error is avoided by using a different memory allocation function.

  [Regression Potential]

  After several months of testing the patch in Debian Jessie, Debian
  Testing and Ubuntu 14.04, I haven't noticed any regressions.

  
  [1] https://github.com/mate-desktop/eom/issues/93
  [2] 
https://git.gnome.org/browse/gtk+/commit?id=894b1ae76a32720f4bb3d39cf460402e3ce331d6
  [3] https://github.com/mate-desktop/eom/issues/93#issuecomment-141035799

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

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

[Touch-packages] [Bug 1544976] [NEW] [Wishlist] Owner info on lock screen

[Anupam]

Public bug reported:

It would be great if the user is allowed to enter details (owner info)
which will be shown in the circle on the lock screen (like the way one
can do in android)

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

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

Title:
  [Wishlist] Owner info on lock screen

Status in libusermetrics package in Ubuntu:
  New

Bug description:
  It would be great if the user is allowed to enter details (owner info)
  which will be shown in the circle on the lock screen (like the way one
  can do in android)

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

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

[Touch-packages] [Bug 1541994] Re: Two languages lack visible names in boot wizard

[Pat McGowan]

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

** This bug has been marked a duplicate of bug 1539361
   Empty items displayed in language list

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

Title:
  Two languages lack visible names in boot wizard

Status in The Avila project:
  Confirmed
Status in Canonical System Image:
  Confirmed
Status in unity8 package in Ubuntu:
  New

Bug description:
  Flash a frieza device with a recent image. Observe that in the opening
  page of the wizard, the language drop-down contains two entries that
  look wrong:

  1: (   )
  2: (   )

  They appear between hebrew and what looks like korean to me. On my
  image they were 7 places from the bottom of the list, and both appear
  together

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

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

[Touch-packages] [Bug 1508081] Re: Fails to receive OTA updates

[Barry Warsaw]

One other thing to remember: we probably want a cli switch to also
override allowGSM, though there we won't need to set that on an existing
group download since si-cli blocks while a download is happening.

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

Title:
  Fails to receive OTA updates

Status in Canonical System Image:
  In Progress
Status in Ubuntu system image:
  In Progress
Status in system-image package in Ubuntu:
  Confirmed
Status in ubuntu-download-manager package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  In Progress

Bug description:
  Ubuntu Touch 15.04 (r23) [mako]

  Issue: Phone appears to fail to receive OTA updates. Previously, I jumped 
from (r15) to (r23) due to missing OTA updates. Currently, I see (r24) appears 
to be released on 2015 Oct 16.
  Expected behavior: System Settings > System > Updates (or System Settings > 
About this phone > Check for updates) reveals new image that I can release and 
download.
  Actual behavior: Checking for updates... > Software is up to date

  See the comment regarding similar issues for large app installs.
  It seems if anything interrupts the transfer or if the connection is somewhat 
slow the download performance degenerates then times out.

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

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

[Touch-packages] [Bug 1540811] Re: [GDK] patch - avoid integer overflow when allocating a large block of memory

[Bug Watch Updater]

** Changed in: gtk+2.0 (Debian)
   Status: New => Confirmed

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

Title:
  [GDK] patch - avoid integer overflow when allocating a large block of
  memory

Status in GTK+:
  Fix Released
Status in gtk+2.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+2.0 source package in Precise:
  Confirmed
Status in gtk+3.0 source package in Precise:
  Confirmed
Status in gtk+2.0 source package in Trusty:
  Confirmed
Status in gtk+3.0 source package in Trusty:
  Fix Released
Status in gtk+2.0 source package in Wily:
  Confirmed
Status in gtk+3.0 source package in Wily:
  Fix Released
Status in gtk+2.0 source package in Xenial:
  Fix Released
Status in gtk+3.0 source package in Xenial:
  Fix Released
Status in gtk+2.0 package in Debian:
  Confirmed

Bug description:
  [Impact]

  Due to a logic error, an attempt to allocate a large block of memory
  fails in gdk_cairo_set_source_pixbuf, leading to a crash of the app
  that called it, for example, eom [1].

  This issue had been fixed [2] in GTK+3, but GTK+2 apps that use the
  mentioned function still crash when trying to allocate a lot of
  memory. An example of such app is eom (Eye of MATE), an image viewer,
  which crashes when trying to load a large image.

  I propose fixing it in current Ubuntu releases with the patch which fixes the 
crash.
  The debdiffs are in the attachments in the comments below.

  [Test Case]

  Steps to reproduce:

  1. Have a 64-bit installation of Ubuntu.
  2. Install eom if it isn't installed.
  3. Download the archive from the attachment of this post and unpack it. 
(Firefox doesn't allow me to upload image as is - tries to make thumbnail of it 
right in the file open dialog, then crashes.)
  4. Open the unpacked image (27000_27000_1437947845.png) in eom.
  5. eom crashes. The full backtrace is at [3].

  You'll also see an error message: "failed to allocate
  18446744072330584320 bytes". This huge number appears due to overflow
  during multiplication of two 32-bit signed integers. In the patch,
  this error is avoided by using a different memory allocation function.

  [Regression Potential]

  After several months of testing the patch in Debian Jessie, Debian
  Testing and Ubuntu 14.04, I haven't noticed any regressions.

  
  [1] https://github.com/mate-desktop/eom/issues/93
  [2] 
https://git.gnome.org/browse/gtk+/commit?id=894b1ae76a32720f4bb3d39cf460402e3ce331d6
  [3] https://github.com/mate-desktop/eom/issues/93#issuecomment-141035799

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

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

[Touch-packages] [Bug 1532607] Re: Phone not usable while a call comes in - followed by "restart"

[kevin gunn]

** Changed in: unity-system-compositor (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Phone not usable while a call comes in - followed by "restart"

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Committed
Status in Mir 0.19 series:
  Fix Released
Status in Mir 0.20 series:
  Fix Committed
Status in mir package in Ubuntu:
  Fix Released
Status in unity-system-compositor package in Ubuntu:
  Fix Released

Bug description:
  My system:

  current build number: 225
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-01-09 06:52:53
  version version: 225
  version ubuntu: 20160109
  version device: 20151216-378d4f3
  version custom: 2015--36-46-vivid

  What happened:
  Someone called me and I wanted to take the call on the phone (nothing 
attached to the phone). The screen was locked and I pressed the power button to 
unlock the screen. The phone did not react on any pushed buttons. The phone 
continued ringing but I was not able to do anything with the phone during this 
time.

  During the next minute the phone was blocked. After this period a
  "restart" followed.

  "Restart":
  The restart was not a real reset. The phone screen was black. Then approx. 1 
- 2 minutes after the call was gone, the screen went on again and the ubuntu 
logo with the dots appeared (same screen when you start the phone but without 
the "bq"-screen). 

  I did not need to enter the PIN code of the SIM card. The phone was
  again fully operational.

  This happened on January, 10th at approx. 13:30 h. I have attached the
  sys.log for your review and hopefully for tracing back the issue to
  the root cause.

  Matthias

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

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

[Touch-packages] [Bug 1545005] [NEW] system settings displays 'cellular' control panel item when no modems are present

[John McAleely]

Public bug reported:

In bug #1541588 several items were removed from system settings for
tablets which have no cellular modem.

In a related bug #1544712 ofono must still be present on such devices,
in order for location to work.

It seems that when it was tested, the landing for  bug #1541588 happened
when ofono was not running.

I conclude therefore that the decision to display/not display cellular
is keyed merely on the presence of ofono, rather than, say the count of
modems ofono reports.

** Affects: canonical-devices-system-image
 Importance: Low
 Status: New

** Affects: connectivity-api (Ubuntu)
 Importance: Undecided
 Status: New

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

** Also affects: connectivity-api (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  system settings displays 'cellular' control panel item when no modems
  are present

Status in Canonical System Image:
  New
Status in connectivity-api package in Ubuntu:
  New
Status in indicator-network package in Ubuntu:
  New

Bug description:
  In bug #1541588 several items were removed from system settings for
  tablets which have no cellular modem.

  In a related bug #1544712 ofono must still be present on such devices,
  in order for location to work.

  It seems that when it was tested, the landing for  bug #1541588
  happened when ofono was not running.

  I conclude therefore that the decision to display/not display cellular
  is keyed merely on the presence of ofono, rather than, say the count
  of modems ofono reports.

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

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

[Touch-packages] [Bug 1528955] Re: Camera app can be uninstalled permanently.

[Launchpad Bug Tracker]

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

** Changed in: camera-app (Ubuntu)
   Status: New => Confirmed

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

Title:
  Camera app can be uninstalled permanently.

Status in camera-app:
  New
Status in camera-app package in Ubuntu:
  Confirmed

Bug description:
  When I do long-tapping on the camera app icon, the app store is opened, 
showing the camera app's descrition.
  Then it is possible to click on "Uninstall" to unistall the camera app.
  After that the camera app is uninstalled and no photos can be taken, so far 
so good.

  But then it is not possible to reinstall the camera app, because the
  app can't be found in app store by searching for "camera".

  This happened on Nexus 4 in stable channel.
  This did NOT happen on Nexus 4 in rc-proposed channel.
  This happened on  Aquaris E4.5. 

  Further information here:

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

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

[Touch-packages] [Bug 1499879] Re: Moonphase could not be read

[Kyle Nitzsche]

Ilonka: OK I understand. That was probably a previous translation that
has already been replaced on launchpad.

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

Title:
  Moonphase could not be read

Status in Day Scope:
  Confirmed
Status in Today Scope:
  New
Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Hello guys!
  I want to read information for the moon phase in TodayScope. Problem is that 
the displayed text is to long, so I can see first word but not the rest.
  I think it is really a good think with this information, thank you for this 
:-)

  I use a BQ Aquaris E4.5 with Ubuntu 15.04 r25 dashboard 1.9.2

  I sent a screenshot

To manage notifications about this bug go to:
https://bugs.launchpad.net/day-scope/+bug/1499879/+subscriptions

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

Re: [Touch-packages] [Bug 1499879] Moonphase could not be read

[Ilonka]

Hi Kyle,

I can't tell you the complete sentence because I only know first word of 
the sentence "einwachsend" And this word I can't find in german 
translations.
I think next week should be this moonphase which it depends. If this word 
will appear again, we' ll know that the shown sentence isn't be part of the 
moonphase strings and then we'll see what to do 

Until next week
Greetings 
Ilonka

Am Mittwoch, 10. Februar 2016 00:20:41 CET schrieb Kyle Nitzsche 
:
> Hi Ilonaka,
> 
> I don't see any complete *sentences* in your screen shot from comment
> #1.
> 
> But, as mentioned, all the translations for the Day scope (this part of
> the Today scope) are done here: https://translations.launchpad.net/day-
> scope/trunk/+pots/day/de/
> 
> If you don't see it there, please type the string here and I will try
> and direct you to it.
> 


-- 
Mit Dekko von meinem Ubuntu-Gerät gesendet

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

Title:
  Moonphase could not be read

Status in Day Scope:
  Confirmed
Status in Today Scope:
  New
Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Hello guys!
  I want to read information for the moon phase in TodayScope. Problem is that 
the displayed text is to long, so I can see first word but not the rest.
  I think it is really a good think with this information, thank you for this 
:-)

  I use a BQ Aquaris E4.5 with Ubuntu 15.04 r25 dashboard 1.9.2

  I sent a screenshot

To manage notifications about this bug go to:
https://bugs.launchpad.net/day-scope/+bug/1499879/+subscriptions

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

[Touch-packages] [Bug 1540811] Re: [GDK] patch - avoid integer overflow when allocating a large block of memory

[Marc Deslauriers]

** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gtk+3.0 (Ubuntu Precise)
   Importance: Undecided => Medium

** Changed in: gtk+3.0 (Ubuntu Precise)
   Status: New => Confirmed

** Changed in: gtk+3.0 (Ubuntu Precise)
 Assignee: (unassigned) => Marc Deslauriers (mdeslaur)

** Changed in: gtk+3.0 (Ubuntu Trusty)
   Status: New => Fix Released

** Changed in: gtk+3.0 (Ubuntu Wily)
   Status: New => Fix Released

** Changed in: gtk+3.0 (Ubuntu Xenial)
   Status: New => Fix Released

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

Title:
  [GDK] patch - avoid integer overflow when allocating a large block of
  memory

Status in GTK+:
  Fix Released
Status in gtk+2.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+2.0 source package in Precise:
  Confirmed
Status in gtk+3.0 source package in Precise:
  Confirmed
Status in gtk+2.0 source package in Trusty:
  Confirmed
Status in gtk+3.0 source package in Trusty:
  Fix Released
Status in gtk+2.0 source package in Wily:
  Confirmed
Status in gtk+3.0 source package in Wily:
  Fix Released
Status in gtk+2.0 source package in Xenial:
  Fix Released
Status in gtk+3.0 source package in Xenial:
  Fix Released
Status in gtk+2.0 package in Debian:
  New

Bug description:
  [Impact]

  Due to a logic error, an attempt to allocate a large block of memory
  fails in gdk_cairo_set_source_pixbuf, leading to a crash of the app
  that called it, for example, eom [1].

  This issue had been fixed [2] in GTK+3, but GTK+2 apps that use the
  mentioned function still crash when trying to allocate a lot of
  memory. An example of such app is eom (Eye of MATE), an image viewer,
  which crashes when trying to load a large image.

  I propose fixing it in current Ubuntu releases with the patch which fixes the 
crash.
  The debdiffs are in the attachments in the comments below.

  [Test Case]

  Steps to reproduce:

  1. Have a 64-bit installation of Ubuntu.
  2. Install eom if it isn't installed.
  3. Download the archive from the attachment of this post and unpack it. 
(Firefox doesn't allow me to upload image as is - tries to make thumbnail of it 
right in the file open dialog, then crashes.)
  4. Open the unpacked image (27000_27000_1437947845.png) in eom.
  5. eom crashes. The full backtrace is at [3].

  You'll also see an error message: "failed to allocate
  18446744072330584320 bytes". This huge number appears due to overflow
  during multiplication of two 32-bit signed integers. In the patch,
  this error is avoided by using a different memory allocation function.

  [Regression Potential]

  After several months of testing the patch in Debian Jessie, Debian
  Testing and Ubuntu 14.04, I haven't noticed any regressions.

  
  [1] https://github.com/mate-desktop/eom/issues/93
  [2] 
https://git.gnome.org/browse/gtk+/commit?id=894b1ae76a32720f4bb3d39cf460402e3ce331d6
  [3] https://github.com/mate-desktop/eom/issues/93#issuecomment-141035799

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

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

[Touch-packages] [Bug 997737] Re: Detroit is not in Canada, 12.04

[Robert McKee]

This is still a bug in 16.04. If installing with Detroit for the
location as stated above "it will match it with Canadian sources.list",
as well as the "settings for Canada, rather than the US. So, I had
Canadian date format, units, and currency".

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

Title:
  Detroit is not in Canada, 12.04

Status in tzdata package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 12.04 over the weekend.  When it asked me to select
  my location or time zone or whatever, I selected Detroit, Michigan,
  Eastern Time Zone.  When I booted up, I saw that my locale settings
  were for Canada, rather than the US.  So, I had Canadian date format,
  units, and currency.

  I changed it to US per this askubuntu thread:
  
http://askubuntu.com/questions/133011/set-default-language-to-english-us-in-12-04

  Not sure where this geography information is stored, but this fixed
  the problem for me after the fact.

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

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

[Touch-packages] [Bug 1445064] Re: Re-implement container crash forwarding

[Martin Pitt]

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

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

Title:
  Re-implement container crash forwarding

Status in apport package in Ubuntu:
  In Progress

Bug description:
  The container crash forwarding feature must be re-implemented to use a
  safe design.

  The current thought is:
   - Introduce a systemd unit and upstart job to have a socket activated apport 
crash handler
   - When a crash comes from a container, have apport connect to the socket in 
the crashed process' root, write the arguments it received to the socket.
   - The crash handler in the container will then run and close the socket when 
it doesn't need the crashed process anymore.
   - The host crash handler then exits.

  This means that we only rely on an accessible root directory for the
  crashed process and the crash handler will be spawned by init inside
  that container. This makes it safe for privileged and unprivileged
  containers.

  As an extra security measure, rate limiting should be added so that we
  can only have 10 in-flight crashes and that any crash taking more than
  30s to be handled get cancelled (preventing host DoS).

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

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

[Touch-packages] [Bug 1528384] Re: unity-system-compositor crashed with std::runtime_error in mir::compositor::CompositingFunctor::wait_until_started() from usc::MirScreen::set_screen_power_mode (mir_

[Alberto Aguirre]

** Also affects: mir/0.19
   Importance: Undecided
   Status: New

** Also affects: mir/0.20
   Importance: Undecided
   Status: New

** Changed in: mir/0.19
   Status: New => Fix Released

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

Title:
  unity-system-compositor crashed with std::runtime_error in
  mir::compositor::CompositingFunctor::wait_until_started() from
  usc::MirScreen::set_screen_power_mode (mir_power_mode_on)

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Fix Committed
Status in Mir 0.19 series:
  Fix Released
Status in Mir 0.20 series:
  New
Status in Unity System Compositor:
  In Progress
Status in mir package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Confirmed

Bug description:
  Top crash over past week (ww02) on errors.u.c for rc-proposed
  channels.

  Started with u-s-c 0.2.0+15.04.20151216.1-0ubuntu1

  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity-system-compositor.  This problem was most recently
  seen with version 0.2.0+15.04.20151216.1-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/7bcfcf599b35b264c0be45d5290ad9ae3c50adcf
  contains more details.

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

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

[Touch-packages] [Bug 1532974] Re: large window flicker on ubuntu apps launching in window mode

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/qtmir/qtmir-ubuntu-xenial-landing-064

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

Title:
  large window flicker on ubuntu apps launching in window mode

Status in The Avila project:
  In Progress
Status in Canonical System Image:
  In Progress
Status in Canonical Pocket Desktop:
  In Progress
Status in qtmir package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  I don't recall ever seeing this, and I believe i would have noticed, so I 
think this is a regression
  This only seems to occur for ubuntu apps (not puritine/xmir apps)
  This is probably best demonstrated with the Clock app because of the trusted 
prompt - which in the clock app case actually holds the large window on screen

  steps to repro
  1) connect bt mouse
  2) connect slimport to device
  3) launch clock app (or any other ubuntu app and keep your eyes on the screen 
for the flicker)

  also, tested this on both n7 and n4, it occurs on both

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

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

[Touch-packages] [Bug 1524488] Re: Manually setting the time into the past makes flickables misbehave

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/qtmir/qtmir-ubuntu-xenial-landing-064

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

Title:
  Manually setting the time into the past makes flickables misbehave

Status in mir package in Ubuntu:
  Invalid
Status in qtdeclarative-opensource-src package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Unexpected behavior while testing a U1 silo:

  TEST CASE
  1.  Open ubuntu-system-settings, set time manually into the past a few hours
  2.  Return to scopes
  3.  Swipe left for next scope
  EXPECTED
  Scope swipes left, next scope appears.
  ACTUAL
  Stunted swipe appears to register late, fails to switch scope.

  Please feel free to reassign if the gesture itself is dependent on
  time?  Pathological use case but maybe worth examining if it exposes
  some pathological codepaths ;) .

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

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

[Touch-packages] [Bug 1389761] Re: Don't show the volume overlay when changing the volume with the slider

[Pat McGowan]

** Tags removed: apport-bug armhf beta utopic
** Tags added: audioroles

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

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

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

** Changed in: canonical-devices-system-image
Milestone: None => backlog

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Pat McGowan (pat-mcgowan)

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

Title:
  Don't show the volume overlay when changing the volume with the slider

Status in Canonical System Image:
  Confirmed
Status in indicator-sound package in Ubuntu:
  Triaged
Status in ubuntu-system-settings package in Ubuntu:
  Triaged
Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged

Bug description:
  The overlay and the slider are redundant when the user changes the
  volume with the slider and the overlay shouldn't be displayed.

  : “The system volume control should
  automatically reflect, and adjust, the audio volume for the current
  output role through the current output device.”

  : “There should be no
  extra visible notification if the focused window contains a system
  volume control.”

  : “The “Silent Mode”
  switch should be followed by a system volume control for adjusting the
  volume…”

  : “The indicator and the
  system volume control — identical to its counterpart in System
  Settings — should both represent, and the slider should adjust, the
  volume…”

  The equivalent for track changes is bug 652978.

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: indicator-sound 12.10.2+14.10.20141021~rtm-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ActionStates: ({'mediaplayer-app.desktop.greeter': (true, signature '', 
[<{'running': , 'state': <'Paused'>}>]), 'mute': (true, '', []), 
'phone-settings': (true, '', []), 'mic-volume': (true, '', [<1.0>]), 'scroll': 
(true, 'i', []), 'high-volume': (true, '', []), 
'play-playlist.mediaplayer-app.desktop': (true, 's', []), 'desktop-settings': 
(true, '', []), 'mediaplayer-app.desktop': (true, '', [<{'running': , 
'state': <'Paused'>}>]), 'play.mediaplayer-app.desktop': (true, '', 
[<'Paused'>]), 'volume': (true, 'i', [<1.0>]), 'next.mediaplayer-app.desktop': 
(true, '', []), 'root': (true, '', [<{'title': <'Son'>, 'accessible-desc': 
<'Volume (100%)'>, 'icon': <('themed', <['audio-volume-high-panel', 
'audio-volume-high', 'audio-volume', 'audio']>)>, 'visible': }>]), 
'previous.mediaplayer-app.desktop': (true, '', []), 'silent-mode': (true, '', 
[])},)
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Wed Nov  5 16:58:35 2014
  InstallationDate: Installed on 2014-11-05 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141105-120036)
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1542094] Re: [camera] LED & Flash toggles are shown even when no LED or Flash present on hardware

[Pat McGowan]

Entered bug #1544982

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

Title:
  [camera] LED & Flash toggles are shown even when no LED or Flash
  present on hardware

Status in The Avila project:
  Confirmed
Status in Canonical System Image:
  Invalid
Status in android package in Ubuntu:
  New
Status in camera-app package in Ubuntu:
  Invalid

Bug description:
  could be Freiza specific.

  We shouldn't be showing controls for flash, torchlight if they are not
  present on hardware, but apparently we are (according to design)

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

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

[Touch-packages] [Bug 1542094] Re: [camera] LED & Flash toggles are shown even when no LED or Flash present on hardware

[Pat McGowan]

This was reported by John also and I marked it invalid.  I believe the back 
camera on freiza has a flash (of course it should) and its simply not working.
The front camera doesn't display a flash option.

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

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

Title:
  [camera] LED & Flash toggles are shown even when no LED or Flash
  present on hardware

Status in The Avila project:
  Confirmed
Status in Canonical System Image:
  Invalid
Status in android package in Ubuntu:
  New
Status in camera-app package in Ubuntu:
  Invalid

Bug description:
  could be Freiza specific.

  We shouldn't be showing controls for flash, torchlight if they are not
  present on hardware, but apparently we are (according to design)

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

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

[Touch-packages] [Bug 1544957] Re: Scrolling is not smooth

[Kyle Nitzsche]

HI Martin,

Sorry about this and thanks for filing the bug!

I am going to add unity-scopes-shell and unity8 to this bug because
smooth or jerky scrolling is not controlled by the scope itself.

Also, can you please get the following file (right after you see the
problem) and attach it to this bug:

/home/phablet/.cache/upstart/scope-registry.log

Thanks!

** Also affects: unity-scopes-shell (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  Scrolling is not smooth

Status in twitter scope:
  New
Status in unity-scopes-shell package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  I use a BQ 4.5 but unfortunately I can't use the scope, because the scrolling 
 jerky so extreme.
  I hope you can fix this, because the scope is actually great.

To manage notifications about this bug go to:
https://bugs.launchpad.net/twitter-scope/+bug/1544957/+subscriptions

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

[Touch-packages] [Bug 1541989] Re: SMS are sent to my own phone number instead of a typed number

[Jean-Philippe Ayanides]

I have more details about that bug :
I updated my smartphone on january, 25th to OTA 9.0

If I try to send a message to a new number or to someone I didn't talk
to after THAT update, the message is sent to me and not to my contact.

So for now, I cannot communicate with my contacts if they have not sent a 
message to me since january, 25th.
As a consequence, I cannot communicate with new contacts at all.

It is VERY ANNOYING!

If this bug is not solved quickly, I will be desperate enough to switch
back to Android. What else can I do?

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

Title:
   SMS are sent to my own phone number instead of a typed number

Status in messaging-app package in Ubuntu:
  New

Bug description:
  Since I have upgraded to version OTA-9 on my BQ Aquaris 5, I cannot sent a 
SMS to a new number.
  How to reproduce the bug:

  -run application "Messages" (in french)
  -pull the screen from the bottom
  -enter the new phone number
  -enter the message and send it.
  The message has been sent back to you!!!

  version 0.1+15.04.20160109.1-0ubuntu1

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

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

[Touch-packages] [Bug 1541588] Re: [System Settings] Changes needed for the UI on a tablet device

[Launchpad Bug Tracker]

** Branch linked: lp:~pete-woods/indicator-network/lp1541588

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

Title:
  [System Settings] Changes needed for the UI on a tablet device

Status in Canonical System Image:
  In Progress
Status in Ubuntu UX:
  New
Status in indicator-network package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released

Bug description:
  Note for design: can we simply avoid referring to the/this phone as in
  most uses its not necessary for clarity, and then the same text can
  always apply..

  Main panel:
  Hide Cellular
  Hide Hotspot
  Hide Phone
  About this phone -> About this device or just About
  Reset phone -> Reset device or just Reset

  Background
  Ensure default for images is landscape

  Sound:
  Hide Ringer, Phone Calls and Messages sections

  Security and Privacy
  Hide SIM PIN
  Locking and unlocking > Lock security "Unlock the phone using" --> "Unlock 
the device using"
  Locking and unlocking > Lock when idle  "Lock the phone when..." --> "Lock 
the device when ..."
  "Phone won't lock..." --> Device won't lock ..."

  About this device
  Hide IMEI
  Developer mode >  "this phone" --> "this device"

  A minor point but what happens when we search in settings for hidden
  stuff

  
  
  Note from design:

  - The text in the UI should never refer to "Phone", "Tablet" or
  "Desktop".  Instead the word "Device" should be used.

  - e.g. "About This Computer" or "About This Phone" is incorrect. This
  wording should be changed to "About this device" in both the indicator
  and System Settings to be convergence friendly.

  - This change applies to all device references in the UI.

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

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

[Touch-packages] [Bug 1532974] Re: large window flicker on ubuntu apps launching in window mode

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/unity-api/unity-api-ubuntu-xenial-
landing-064

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

Title:
  large window flicker on ubuntu apps launching in window mode

Status in The Avila project:
  In Progress
Status in Canonical System Image:
  In Progress
Status in Canonical Pocket Desktop:
  In Progress
Status in qtmir package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  I don't recall ever seeing this, and I believe i would have noticed, so I 
think this is a regression
  This only seems to occur for ubuntu apps (not puritine/xmir apps)
  This is probably best demonstrated with the Clock app because of the trusted 
prompt - which in the clock app case actually holds the large window on screen

  steps to repro
  1) connect bt mouse
  2) connect slimport to device
  3) launch clock app (or any other ubuntu app and keep your eyes on the screen 
for the flicker)

  also, tested this on both n7 and n4, it occurs on both

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

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

[Touch-packages] [Bug 1539123] Re: Quick photos from lock screen

[Anupam]

if implemented, this lock screen camera option shouldn't have a slide
from right to go to "Photo Roll" option we see in the camera app to
maintain user's privacy

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

Title:
  Quick photos from lock screen

Status in camera-app package in Ubuntu:
  Confirmed

Bug description:
  It's almost impossible to take quick snapshots with locked phone:
  Swiping, pine code, launching the photo app just takes way too long.
  The fascinating scene you wanted to photograph is long gone until the
  photo app is ready. Therefore the lock screen should contain an easy
  to hit button that instantly starts the photo app, ready for taking
  the snapshot of the year. Android and iOS show how to do this.

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

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

[Touch-packages] [Bug 1545005] Re: system settings displays 'cellular' control panel item when no modems are present

[Ken VanDine]

The real bug is probably in ofono, see the output of list-modems from a
device without a modem and ofono running:

http://pastebin.ubuntu.com/15024416/

So I think the real bug is that ofono reports a /ril_0 without any
interfaces or features

Connectivity API could work around this by assuming the modem isn't real
if those values are NULL, but I think it's really an ofono bug.

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

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

Title:
  system settings displays 'cellular' control panel item when no modems
  are present

Status in Canonical System Image:
  New
Status in connectivity-api package in Ubuntu:
  New
Status in indicator-network package in Ubuntu:
  New
Status in ofono package in Ubuntu:
  New

Bug description:
  In bug #1541588 several items were removed from system settings for
  tablets which have no cellular modem.

  In a related bug #1544712 ofono must still be present on such devices,
  in order for location to work.

  It seems that when it was tested, the landing for  bug #1541588
  happened when ofono was not running.

  I conclude therefore that the decision to display/not display cellular
  is keyed merely on the presence of ofono, rather than, say the count
  of modems ofono reports.

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

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

[Touch-packages] [Bug 1526959] Re: openssl 1.0.2e breaks sbsigntool

[Marc Deslauriers]

** Changed in: openssl (Ubuntu)
   Status: Incomplete => 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/1526959

Title:
  openssl 1.0.2e breaks sbsigntool

Status in openssl package in Ubuntu:
  Invalid
Status in sbsigntool package in Ubuntu:
  Fix Released

Bug description:
  Looks like sbsigntool now fails again to verify signed EFI binaries
  against a valid cert (and the signature is known to be valid).
  Reverting to 1.0.2d-0ubuntu2 lets it work again:

  [15:40:30] mtrudel@moloch:~u/shim-signed-1.12 $ sbverify --cert 
MicCorUEFCA2011_2011-06-27.crt shim.efi.signed
  warning: data remaining[1170360 vs 1289424]: gaps between PE/COFF sections?
  PKCS7 verification failed
  140048473532048:error:21075076:PKCS7 routines:PKCS7_verify:content and data 
present:pk7_smime.c:280:
  Signature verification failed
  [15:50:03] mtrudel@moloch:~u/shim-signed-1.12 $ sudo dpkg -i 
../openssl_1.0.2d-0ubuntu2_amd64.deb ../libssl1.0.0_1.0.2d-0ubuntu2_amd64.deb
  dpkg : avertissement : dégradation (« downgrade ») de openssl depuis 
1.0.2e-1ubuntu1 vers 1.0.2d-0ubuntu2
  (Lecture de la base de données... 291770 fichiers et répertoires déjà 
installés.)
  Préparation du dépaquetage de .../openssl_1.0.2d-0ubuntu2_amd64.deb ...
  Dépaquetage de openssl (1.0.2d-0ubuntu2) sur (1.0.2e-1ubuntu1) ...
  dpkg : avertissement : dégradation (« downgrade ») de libssl1.0.0:amd64 
depuis 1.0.2e-1ubuntu1 vers 1.0.2d-0ubuntu2
  Préparation du dépaquetage de .../libssl1.0.0_1.0.2d-0ubuntu2_amd64.deb ...
  Dépaquetage de libssl1.0.0:amd64 (1.0.2d-0ubuntu2) sur (1.0.2e-1ubuntu1) ...
  Paramétrage de libssl1.0.0:amd64 (1.0.2d-0ubuntu2) ...
  Paramétrage de openssl (1.0.2d-0ubuntu2) ...
  Traitement des actions différées (« triggers ») pour man-db (2.7.5-1) ...
  Traitement des actions différées (« triggers ») pour libc-bin (2.21-0ubuntu5) 
...
  [15:50:18] mtrudel@moloch:~u/shim-signed-1.12 $ sbverify --cert 
MicCorUEFCA2011_2011-06-27.crt shim.efi.signed
  warning: data remaining[1170360 vs 1289424]: gaps between PE/COFF sections?
  Signature verification OK

  We've hit a similar issue in the past; in lieue of
  sbsigntool/0.6-0ubuntu8:
  
http://launchpadlibrarian.net/211726228/sbsigntool_0.6-0ubuntu7_0.6-0ubuntu8.diff.gz

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

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