[Touch-packages] [Bug 1385630] Re: systemd 215 hangs during boot

[Martin Pitt]

That's the one thing I actually tried to install, but it didn't break
the initramfs in such a way. So I still don't know at all what's wrong
here :-(

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

Title:
  systemd 215 hangs during boot

Status in “systemd” package in Ubuntu:
  Incomplete

Bug description:
  I just installed (for testing) the newest systemd from Vivid proposed 
repositories.
  Yes, that is only a proposed package.
  The version is 215-5ubuntu1. Also the new plymouth was needed to do this 
(version 0.9.0-0ubuntu8).

  After the installation I found that every now and then booting or rebooting 
fails.
  It fails in a system-fsck line. So, nowhere to go from that, no tty's, no 
nothing.
  After each failure the next booting is successful, however.

  My setup is extremely fast, I am able to get to the desktop in about 5 
seconds from grub menu.
  The setup contains Intel Core i7 4790 processor and Samsung 850 Pro SSD.

  This may also be some sort of race situation.

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

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

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

[John Muir]

This bug appears on my 14.04 twin-screen PC running Unity 7.2.3 and my 14.10 
laptop running Unity 7.3.1.
So I don't believe it's anything to do with the number of screens.

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

Title:
  launcher does not show minimized update manager while clicked

Status in Unity:
  Fix Released
Status in Unity 5.0 series:
  Fix Released
Status in Unity 6.0 series:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released
Status in “update-manager” package in Ubuntu:
  Confirmed
Status in “unity” source package in Precise:
  Fix Released
Status in “update-manager” source package in Precise:
  Confirmed
Status in “unity” source package in Quantal:
  Fix Released
Status in “update-manager” source package in Quantal:
  Confirmed

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

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

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

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

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

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

[Touch-packages] [Bug 1391609] Re: [regression] on desktop, address bar not empty when creating a new tab from the tabs view

[Olivier Tilloy]

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

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

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

Title:
  [regression] on desktop, address bar not empty when creating a new tab
  from the tabs view

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

Bug description:
  (this regression was most likely introduced by revision 795 of lp
  :webbrowser-app, it affects only desktop where the address bar gets
  active focus when opening a new tab)

  Steps to reproduce:

   1) on desktop, launch the browser with webbrowser-app --new-session
   2) Open the drawer, select open tabs to open the tabs view
   3) In the tabs view, click the Add button in the toolbar, a new tab opens 
and the address bar is given active focus

  Expected result: the address bar is cleared

  Current result: the address of the previously open tab remains

  Note that creating a new tab directly from the drawer doesn’t exhibit
  this faulty behaviour.

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

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

[Touch-packages] [Bug 1357321] Re: [TOPBLOCKER] QNetworkAccessManager doesn't support roaming on Ubuntu

[Alfonso Sanchez-Beato]

I have monitored calls to ofono DBus connection manager interfaces
following comment #7 in

https://bugs.launchpad.net/ubuntu/+source/telepathy-ofono/+bug/1226739

The command was:

# dbus-monitor --system interface=org.ofono.ConnectionManager
interface=org.ofono.ConnectionContext

I have attached the output. What I see is that a process with unique
name :1.8  is activating/deactivating periodically the cellular data
context.

# dbus-send --system --print-reply --dest=org.freedesktop.DBus
/org/freedesktop/DBus org.freedesktop.DBus.GetConnectionUnixProcessID
string::1.8

showed the PID of NetworkManager.

The output of /usr/share/ofono/scripts/monitor-ofono is:

...
{ConnectionContext} [/ril_0/context1] Settings = {}
{ConnectionContext} [/ril_0/context1] Active = False
{ConnectionContext} [/ril_0/context1] Settings = { Interface = ccmni0, Gateway 
= 10.79.188.18, DomainNameServers = 212.166.210.82 212.73.32.67, Netmask = 
255.255.255.0, Method = static, Address = 10.79.188.18 }
{ConnectionContext} [/ril_0/context1] Active = True
{ConnectionContext} [/ril_0/context1] Settings = {}
{ConnectionContext} [/ril_0/context1] Active = False
{ConnectionContext} [/ril_0/context1] Settings = { Interface = ccmni0, Gateway 
= 10.143.31.135, DomainNameServers = 212.166.210.82 212.73.32.67, Netmask = 
255.255.255.0, Method = static, Address = 10.143.31.135 }
...

ofono is just told to activate/deactivate the context, no spurious
disconnections happen.

HTH

** Attachment added: dbus-monitor.txt
   
https://bugs.launchpad.net/savilerow/+bug/1357321/+attachment/4259732/+files/dbus-monitor.txt

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

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

Title:
  [TOPBLOCKER] QNetworkAccessManager doesn't support roaming on Ubuntu

Status in Platform API:
  In Progress
Status in The Savilerow project:
  New
Status in “network-manager” package in Ubuntu:
  Incomplete
Status in “ofono” package in Ubuntu:
  Invalid
Status in “qtbase-opensource-src” package in Ubuntu:
  In Progress

Bug description:
  scope images load fine in wifi, but not on hsdpa even when there is
  good connectivity and browsing works well. Results are return, but
  images do not load.

To manage notifications about this bug go to:
https://bugs.launchpad.net/platform-api/+bug/1357321/+subscriptions

-- 
Mailing list: https://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 1081590] Re: could not determine source package name

[rodger spooncer]

On Wed, 2014-11-12 at 23:46 +, Hai NGUYEN VAN wrote:
 ** Also affects: apport
Importance: Undecided
Status: New
 
 ** No longer affects: apport
 
thanks for your reply.  I have subsequently discarded the HP750 printer
which itself developed another fault, and replaced it with HP printer
M125nw which worked 'straight out of the box'

My problem has now gone away.

Regards

Rodger

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

Title:
  could not determine source package name

Status in “apport” package in Ubuntu:
  New
Status in “cups” package in Ubuntu:
  New

Bug description:
  When I open/switch on HP printer PSC 750 to print I get an error
  message and a request to send a report, which I accept.

  The following message is then displayed

  Could not determine the package or source package name.

  
  This happens every time I try to print from Internet or Libre office 
programmes.

  I therefore do not know if the bug gets reported or the error report
  message is just terminated because of lack of information gleaned from
  my system.

  What should I do?

  Printing itself does not appear to be affected.  Problem only occurs
  in 12.04.  It was not a problem in 10.04

  Regards
  Rodger

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

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

[Touch-packages] [Bug 1376560] Re: FFe: Sync modemmanager/libqmi/libmbim (main) from Debian unstable (main)

[Graham Inggs]

Fix released in Vivid.

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

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

Title:
  FFe: Sync modemmanager/libqmi/libmbim (main) from Debian unstable
  (main)

Status in “modemmanager” package in Ubuntu:
  Fix Released

Bug description:
  Please sync modemmanager 1.4.0-1 (main) from Debian unstable (main)
  Please sync libqmi 1.10.2-2 (main) from Debian unstable (main)
  Please sync libmbim 1.10.0-2 (main) from Debian unstable (main)

  Explanation of FeatureFreeze exception:
  Please consider syncing the current versions of modemmanager, libqmi and 
libmbim in order to enable the latest hardware.

  Changelog entries since current utopic version 1.2.0-1:

  modemmanager (1.4.0-1) unstable; urgency=medium

* New upstream release.
  - Fixes conflicting definitions of mm_manager_new. (Closes: #749387)
* Refresh patches.
* Bump Build-Depends on libmbim-glib-dev to (= 1.10).
* Install NEWS file which includes the relevant upstream changes.
  (Closes: #641467)
* Update symbols file for libmm-glib0.
* Add Build-Depends on dbus, required to run the test suite.

   -- Michael Biebl bi...@debian.org  Wed, 17 Sep 2014 08:46:25 +0200

  Changelog entries since current utopic version 1.10.2-1:

  libqmi (1.10.2-2) unstable; urgency=medium

* Team upload.

[ Marius B. Kotsbak ]
* Use dh_install --list-missing to show uninstalled files.
* Drop obsolete --with-tests configure option.

[ Michael Biebl ]
* Install man pages via dh_install.
* Use a strictly versioned dependency between libqmi-proxy and libqmi-glib1,
  so the two packages don't get out of sync.
* Make any package linking against libqmi-glib1 get an explicit dependency
  on libqmi-proxy. The qmi-proxy binary is used internally by libqmi-glib1
  and the package split is an implementation detail to properly support
  multi-arch. Convince lintian that this is intentional.
* Add Depends on libglib2.0-dev to libqmi-glib-dev as required by
  qmi-glib.pc.

   -- Michael Biebl bi...@debian.org  Tue, 16 Sep 2014 23:24:51 +0200

  Changelog entries since current utopic version 1.8.0-1:

  libmbim (1.10.0-2) unstable; urgency=medium

* Team upload.
* Use a strictly versioned dependency between libmbim-proxy and
  libmbim-glib4, so the two packages don't get out of sync.
* Make any package linking against libmbim-glib4 get an explicit dependency
  on libmbim-proxy. The mbim-proxy binary is used internally by
  libmbim-glib4 and the package split is an implementation detail to
  properly support multi-arch. Convince lintian that this is intentional.

   -- Michael Biebl bi...@debian.org  Tue, 16 Sep 2014 23:03:20 +0200

  libmbim (1.10.0-1) unstable; urgency=low

* Team upload.

[ Marius B. Kotsbak ]
* New upstream release.
* Rename libmbim-glib0 → libmbim-glib4 for the soname bump.
* Add new package libmbim-proxy holding mbim-proxy binary.
* Add debug info package libmbim-glib4-dbg.

[ Michael Biebl ]
* Use dh_install --list-missing to show uninstalled files.
* Install man pages via dh_install.
* Drop obsolete --with-tests configure option.

   -- Michael Biebl bi...@debian.org  Sun, 14 Sep 2014 03:13:18 +0200

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

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

[Touch-packages] [Bug 1392252] [NEW] gnome 3

[Martin]

Public bug reported:

gnome 3 failed to instal

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
Uname: Linux 3.13.0-39-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Thu Nov 13 10:04:25 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8280] [1002:9836] 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:3678]
InstallationDate: Installed on 2014-11-10 (2 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2)
MachineType: LENOVO 10126
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic.efi.signed 
root=UUID=494dde65-bb05-4091-a2b1-afc9e4f87b98 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/05/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: I9KT50AUS
dmi.board.name: Kabini CRB
dmi.board.vendor: LENOVO
dmi.board.version: SDK0F82993 WIN
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnLENOVO:bvrI9KT50AUS:bd11/05/2013:svnLENOVO:pn10126:pvrLenovoH515s:rvnLENOVO:rnKabiniCRB:rvrSDK0F82993WIN:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: 10126
dmi.product.version: Lenovo H515s
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Thu Nov 13 08:13:36 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.15.1-0ubuntu2.1
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu

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

Title:
  gnome 3

Status in “xorg” package in Ubuntu:
  New

Bug description:
  gnome 3 failed to instal

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Nov 13 10:04:25 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8280] [1002:9836] 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3678]
  InstallationDate: Installed on 2014-11-10 (2 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: LENOVO 10126
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic.efi.signed 
root=UUID=494dde65-bb05-4091-a2b1-afc9e4f87b98 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/05/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: I9KT50AUS
  dmi.board.name: Kabini CRB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993 WIN
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrI9KT50AUS:bd11/05/2013:svnLENOVO:pn10126:pvrLenovoH515s:rvnLENOVO:rnKabiniCRB:rvrSDK0F82993WIN:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: 10126
  dmi.product.version: Lenovo H515s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 

[Touch-packages] [Bug 1392128] Re: Missing training tutorials and documents for HTML 5 development

[Olivier Tilloy]

** Package changed: webbrowser-app (Ubuntu) = unity-webapps-qml

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

Title:
  Missing training tutorials and documents for HTML 5 development

Status in Unity WebApps QML component:
  New

Bug description:
  We are going to have our developer contest soon next month (Dec). We
  need to come out the detailed training materials for the HTML 5
  development. We will not have any on-site training, instead we need to
  make sure that developers will get all of the needed info in their
  development.

  - The HTML 5 tutorials on HTML development are outdated since they
  were based on the old platform. They need to be updated

  - We need a document in high level to tell why a developer should
  choose the Cordova APIs or HTML 5 to start to development in the very
  beginning in view of the fact that we provide two ways of development.
  The document needs to be translated into Chinese once it is ready

  - More documents and tutorials/examples for Ubuntu specific APIs at
  http://developer.ubuntu.com/api/html5/development/. It would be good
  to have the offline document inside the SDK as well.

  - A tutorial on how to do Cordova API HTML 5 app providing an entry on
  our developer website. Currently, there are many versions of Cordova
  APIs there on the Cordova official website. We need clearly tell the
  developer which version to go.

  - A video introduction about our offering about HTML 5 development.

  Thanks  best regards,
  XiaoGuo

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-webapps-qml/+bug/1392128/+subscriptions

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

[Touch-packages] [Bug 1321854] Re: useradd doesn't add the default shell to /etc/passwd entry

[Jonas Björk]

This is still the case with latest installed package of passwd (where I
found useradd):

ii  passwd   1:4.1.5.1-1ubuntu9amd64
change and administer password and group data

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

Title:
  useradd doesn't add the default shell to /etc/passwd entry

Status in “shadow” package in Ubuntu:
  Triaged
Status in “shadow” source package in Trusty:
  Triaged

Bug description:
  useradd is not honoring the default shell listed in
  /etc/defaults/useradd when creating new users.

  useradd -D showing the defaults. SHELL=/bin/bash

  # useradd -D
  GROUP=100
  HOME=/home
  INACTIVE=-1
  EXPIRE=
  SHELL=/bin/bash
  SKEL=/etc/skel
  CREATE_MAIL_SPOOL=no

  Using useradd to create user test1. The /etc/passwd entry has a blank
  shell field:

  # useradd test1
  # grep test1 /etc/passwd
  test1:x:2080:2080::/home/test1:

  Using useradd -s does populate the shell field:
  # useradd -s /bin/bash test2
  #grep test2 /etc/passwd
  test2:x:2081:2081::/home/test2:/bin/bash

  Why useradd instead of adduser: puppet uses useradd to do user
  creation.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: passwd 1:4.1.5.1-1ubuntu9
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  Date: Wed May 21 17:51:57 2014
  Ec2AMI: ami-42dc302a
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1d
  Ec2InstanceType: m3.large
  Ec2Kernel: aki-919dcaf8
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: shadow
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.default.useradd: 2014-05-21T17:36:05.208686

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

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

[Touch-packages] [Bug 1392262] [NEW] Mouse isn't detected, unity icons missing, USB buggy.

[Kaushik]

Public bug reported:

A system crash occured (power failed) and since reboot, mouse isn't
working. USB is buggy (works sometimes). Unity icons are missing. I use
a PS/2 mouse.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-39.66~precise1-generic 3.13.11.8
Uname: Linux 3.13.0-39-generic x86_64
NonfreeKernelModules: usb_storage e1000e ptp pps_core
.tmp.unity.support.test.1:
 
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Thu Nov 13 16:02:34 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Device [1025:066a]
InstallationDate: Installed on 2014-11-12 (0 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2)
MachineType: Acer Veriton M6620G
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic 
root=UUID=420a1fff-f79d-4837-9549-9eac6e0c9117 ro quiet splash vt.handoff=7
ProcModules:
 e1000e 257783 0 - Live 0x
 pps_core 19381 1 ptp, Live 0x
 ptp 18980 1 e1000e, Live 0x
 usb_storage 66714 0 - Live 0x
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/29/2012
dmi.bios.vendor: Acer
dmi.bios.version: P01-A2
dmi.board.name: Veriton M6620G
dmi.board.vendor: Acer
dmi.board.version: v1.0
dmi.chassis.type: 3
dmi.chassis.vendor: Acer
dmi.modalias: 
dmi:bvnAcer:bvrP01-A2:bd11/29/2012:svnAcer:pnVeritonM6620G:pvr:rvnAcer:rnVeritonM6620G:rvrv1.0:cvnAcer:ct3:cvr:
dmi.product.name: Veriton M6620G
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Thu Nov 13 13:25:10 2014
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputAT Translated Set 2 keyboard KEYBOARD, id 8
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.15.1-0ubuntu2

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


** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu

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

Title:
  Mouse isn't detected, unity icons missing, USB buggy.

Status in “xorg” package in Ubuntu:
  New

Bug description:
  A system crash occured (power failed) and since reboot, mouse isn't
  working. USB is buggy (works sometimes). Unity icons are missing. I
  use a PS/2 mouse.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-39.66~precise1-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  NonfreeKernelModules: usb_storage e1000e ptp pps_core
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Nov 13 16:02:34 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:066a]
  InstallationDate: Installed on 2014-11-12 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: 

[Touch-packages] [Bug 1392267] [NEW] [SRU] New stable release 2.42.1

[Iain Lane]

Public bug reported:

[ Description ]

Upload this stable bugfix release

Overview of changes in GLib 2.42.1
==

* This release disables deprecation warnings by default ← we already had
this cherry-picked

* Bugs fixed:
 728256 gcredentials: add NetBSD support
 736806 gtask: Fix reference count loop causing leaks
 737143 Include stdint.h in glib/valgrind.h
 738170 g_byte_array_new_take() doesn't initialize array-alloc
 738197 g_cond_timed_wait() doesn't time out on Mac OS X·

[ QA  regression potential ]

Under the GNOME MRE, assume the bugs are fixed. Installl the update 
use your system as normal. If we don't see any regressions either
manually or on errors, we're good.

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  [SRU] New stable release 2.42.1

Status in “glib2.0” package in Ubuntu:
  New

Bug description:
  [ Description ]

  Upload this stable bugfix release

  Overview of changes in GLib 2.42.1
  ==

  * This release disables deprecation warnings by default ← we already
  had this cherry-picked

  * Bugs fixed:
   728256 gcredentials: add NetBSD support
   736806 gtask: Fix reference count loop causing leaks
   737143 Include stdint.h in glib/valgrind.h
   738170 g_byte_array_new_take() doesn't initialize array-alloc
   738197 g_cond_timed_wait() doesn't time out on Mac OS X·

  [ QA  regression potential ]

  Under the GNOME MRE, assume the bugs are fixed. Installl the update 
  use your system as normal. If we don't see any regressions either
  manually or on errors, we're good.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1392267/+subscriptions

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

[Touch-packages] [Bug 1392274] [NEW] wallpaper with multiple monitors incorrectly displays on login

[Rowan]

Public bug reported:

If I set up a wallpaper with either the Zoom or Centre options under
Appearance in System Settings with two monitors then after logging in,
my laptop screen seems to display incorrectly. With zoom, the laptop
screen zooms the image too much (perhaps to match the zoom for the
resolution of the second screen?) and with centre, it shrunk the
horizontal sides (left black bars) of the wallpaper displayed on the
laptop screen in one instance, though I'm not sure of the behaviour (the
image size matched the screen resolution, which is why it was weird).

This only starts happening *after* login. The wallpaper is displayed
correctly in the login screen until the desktop is shown. I *think* the
external monitor is unaffected, but the laptop wallpaper changes look
after login.

Laptop screen resolution: 1366x768
Separate monitor resolution: 1280x1024
Wallpaper size: 1366x768 (Though this does persist with other image 
resolutions, e.g. 1920x1080 zooms into a tiny part of the image on the laptop 
screen rather than zooming out).

Ubuntu 14.04 LTS
Unity 7.2.3 (Started happening just after update to this version)
... full information has apparently been grabbed by Apport.

Sorry about the verbosity.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.3+14.04.20140826-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
Uname: Linux 3.13.0-39-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Thu Nov 13 12:26:14 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:360b]
   Subsystem: Hewlett-Packard Company Device [103c:360b]
InstallationDate: Installed on 2014-05-11 (185 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
MachineType: Hewlett-Packard Compaq Presario CQ60 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic 
root=UUID=429b2ebe-dc30-4f8f-8b96-59e07eef1089 ro quiet splash vt.handoff=7
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/04/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.33
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 3612
dmi.board.vendor: Wistron
dmi.board.version: 09.48
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Wistron
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.33:bd02/04/2009:svnHewlett-Packard:pnCompaqPresarioCQ60NotebookPC:pvrF.33:rvnWistron:rn3612:rvr09.48:cvnWistron:ct10:cvrChassisVersion:
dmi.product.name: Compaq Presario CQ60 Notebook PC
dmi.product.version: F.33
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Thu Nov 13 12:03:12 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   51584 
 vendor LCD
xserver.version: 2:1.15.1-0ubuntu2.1

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


** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu

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

Title:
  wallpaper with multiple monitors incorrectly displays on login

Status in “unity” package in Ubuntu:
  New

Bug description:
  If I set up a wallpaper with either the Zoom or Centre options
  under Appearance in System Settings with two monitors then after
  logging in, my laptop screen seems to display incorrectly. With zoom,
  the laptop screen zooms the image too much (perhaps to match the zoom
  for the resolution of the second screen?) and with centre, it 

[Touch-packages] [Bug 1387708] Re: [TOPBLOCKER] Location services not getting location

[Victor Tuson Palau]

is this still a top blocker?

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

Title:
  [TOPBLOCKER] Location services not getting location

Status in Location Service:
  New
Status in “location-service” package in Ubuntu:
  In Progress
Status in “location-service” package in Ubuntu RTM:
  Fix Released
Status in “location-service” source package in 14.09:
  Fix Released

Bug description:
  Failing to get location fix from application.
  Neither network based nor gps location works.
  Bug has now been seen on 3 phones with and without SIM installed.
  HERE service seems to be running, but no reasonable location is reported.
  GPS is failing to get fix, tested with phone placed for 2 hours outside.

  On two of those phones location was working fine, but with OTA update to ~135 
stopped working.
  hard to guess working image but somewhere around 129~131

  
  Problem is now reproducible on RTM release 137

To manage notifications about this bug go to:
https://bugs.launchpad.net/location-service/+bug/1387708/+subscriptions

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

[Touch-packages] [Bug 1387708] Re: [TOPBLOCKER] Location services not getting location

[Thomas Voß]

No, the fix has been released to both Vivid and RTM. Manually marked as
Fix Released

** Changed in: location-service (Ubuntu)
   Status: In Progress = Fix Released

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

Title:
  [TOPBLOCKER] Location services not getting location

Status in Location Service:
  New
Status in “location-service” package in Ubuntu:
  Fix Released
Status in “location-service” package in Ubuntu RTM:
  Fix Released
Status in “location-service” source package in 14.09:
  Fix Released

Bug description:
  Failing to get location fix from application.
  Neither network based nor gps location works.
  Bug has now been seen on 3 phones with and without SIM installed.
  HERE service seems to be running, but no reasonable location is reported.
  GPS is failing to get fix, tested with phone placed for 2 hours outside.

  On two of those phones location was working fine, but with OTA update to ~135 
stopped working.
  hard to guess working image but somewhere around 129~131

  
  Problem is now reproducible on RTM release 137

To manage notifications about this bug go to:
https://bugs.launchpad.net/location-service/+bug/1387708/+subscriptions

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

[Touch-packages] [Bug 1392281] [NEW] Clicking an anchor with target _blank does not open the link

[Jean-Francois Moy]

Public bug reported:

When clicking an anchor with a _blank target in a HTML5 application
(using webapp-container), the link is not opened and the following
message is displayed in the console:

qml: Invalid message received:
{event:newtab,url:http://developer.ubuntu.com/api/html5/current/}

Steps to reproduce:

Open Ubuntu SDK
Create an HTML5 Application using the default template
Run the application on your desktop
Click any of the two buttons
Nothing happens

** Affects: ubuntu-html5-theme (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Clicking an anchor with target _blank does not open the link

Status in “ubuntu-html5-theme” package in Ubuntu:
  New

Bug description:
  When clicking an anchor with a _blank target in a HTML5 application
  (using webapp-container), the link is not opened and the following
  message is displayed in the console:

  qml: Invalid message received:
  {event:newtab,url:http://developer.ubuntu.com/api/html5/current/}

  Steps to reproduce:

  Open Ubuntu SDK
  Create an HTML5 Application using the default template
  Run the application on your desktop
  Click any of the two buttons
  Nothing happens

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

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

[Touch-packages] [Bug 1392281] Re: Clicking an anchor with target _blank does not open the link

[David Barth]

** Changed in: ubuntu-html5-theme (Ubuntu)
 Assignee: (unassigned) = Alexandre Abreu (abreu-alexandre)

** Changed in: ubuntu-html5-theme (Ubuntu)
   Importance: Undecided = Medium

** Changed in: ubuntu-html5-theme (Ubuntu)
   Status: New = Confirmed

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

Title:
  Clicking an anchor with target _blank does not open the link

Status in “ubuntu-html5-theme” package in Ubuntu:
  Confirmed

Bug description:
  When clicking an anchor with a _blank target in a HTML5 application
  (using webapp-container), the link is not opened and the following
  message is displayed in the console:

  qml: Invalid message received:
  {event:newtab,url:http://developer.ubuntu.com/api/html5/current/}

  Steps to reproduce:

  Open Ubuntu SDK
  Create an HTML5 Application using the default template
  Run the application on your desktop
  Click any of the two buttons
  Nothing happens

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

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

[Touch-packages] [Bug 1392285] [NEW] mountall counts remounts again, causing the boot procress to stop

[markusj]

Public bug reported:

For some reason, mountall failed at the last reboot of my home server. The box 
processes a few first boot steps and stops in an early boot phase. Weirdly, if 
the bootloader passed --verbose to the kernel, the boot process went well.
I compared the logs of a failed and a successful boot process and nailed it 
down to mountall, struggling with a bind mount of a read-only root fs. 
Apparently, mountall counted the remounts again as mounts, causing the total 
mount count to differ from the expected mount count. Therefore, the events 
local-filesystems and filesystems have not been emitted.

Watch for lines related to /mnt/root in mountall.log, this mount is
counted four times instead of just once.

Workarounds: 
1. Boot with init=/bin/sh, open a getty instance, exec init and run mountall 
there after the boot process has been stuck.
2. Set the problematic mount to noauto and mount it by yourself later.

One additional remark: This issue appeared the first time two days ago,
without having changed anything at all at my fstab. During the uptime of
~10 days, a few packages have been installed or updated, but nothing
mission critical. I have no idea what triggered this issue.

$ lsb_release -rd
Description:Ubuntu 14.04.1 LTS
Release:14.04

$ apt-cache policy mountall
mountall:
  Installiert:   2.53
  Installationskandidat: 2.53
  Versionstabelle:
 *** 2.53 0
500 http://ports.ubuntu.com/ubuntu-ports/ trusty/main armhf Package
100 /var/lib/dpkg/status

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

** Attachment added: mountall.log
   
https://bugs.launchpad.net/bugs/1392285/+attachment/4259865/+files/mountall.log

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

Title:
  mountall counts remounts again, causing the boot procress to stop

Status in “mountall” package in Ubuntu:
  New

Bug description:
  For some reason, mountall failed at the last reboot of my home server. The 
box processes a few first boot steps and stops in an early boot phase. Weirdly, 
if the bootloader passed --verbose to the kernel, the boot process went well.
  I compared the logs of a failed and a successful boot process and nailed it 
down to mountall, struggling with a bind mount of a read-only root fs. 
Apparently, mountall counted the remounts again as mounts, causing the total 
mount count to differ from the expected mount count. Therefore, the events 
local-filesystems and filesystems have not been emitted.

  Watch for lines related to /mnt/root in mountall.log, this mount is
  counted four times instead of just once.

  Workarounds: 
  1. Boot with init=/bin/sh, open a getty instance, exec init and run mountall 
there after the boot process has been stuck.
  2. Set the problematic mount to noauto and mount it by yourself later.

  One additional remark: This issue appeared the first time two days
  ago, without having changed anything at all at my fstab. During the
  uptime of ~10 days, a few packages have been installed or updated, but
  nothing mission critical. I have no idea what triggered this issue.

  $ lsb_release -rd
  Description:Ubuntu 14.04.1 LTS
  Release:14.04

  $ apt-cache policy mountall
  mountall:
Installiert:   2.53
Installationskandidat: 2.53
Versionstabelle:
   *** 2.53 0
  500 http://ports.ubuntu.com/ubuntu-ports/ trusty/main armhf Package
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1392285] Re: mountall counts remounts again, causing the boot procress to stop

[markusj]

** Attachment added: fstab
   
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1392285/+attachment/4259866/+files/fstab

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

Title:
  mountall counts remounts again, causing the boot procress to stop

Status in “mountall” package in Ubuntu:
  New

Bug description:
  For some reason, mountall failed at the last reboot of my home server. The 
box processes a few first boot steps and stops in an early boot phase. Weirdly, 
if the bootloader passed --verbose to the kernel, the boot process went well.
  I compared the logs of a failed and a successful boot process and nailed it 
down to mountall, struggling with a bind mount of a read-only root fs. 
Apparently, mountall counted the remounts again as mounts, causing the total 
mount count to differ from the expected mount count. Therefore, the events 
local-filesystems and filesystems have not been emitted.

  Watch for lines related to /mnt/root in mountall.log, this mount is
  counted four times instead of just once.

  Workarounds: 
  1. Boot with init=/bin/sh, open a getty instance, exec init and run mountall 
there after the boot process has been stuck.
  2. Set the problematic mount to noauto and mount it by yourself later.

  One additional remark: This issue appeared the first time two days
  ago, without having changed anything at all at my fstab. During the
  uptime of ~10 days, a few packages have been installed or updated, but
  nothing mission critical. I have no idea what triggered this issue.

  $ lsb_release -rd
  Description:Ubuntu 14.04.1 LTS
  Release:14.04

  $ apt-cache policy mountall
  mountall:
Installiert:   2.53
Installationskandidat: 2.53
Versionstabelle:
   *** 2.53 0
  500 http://ports.ubuntu.com/ubuntu-ports/ trusty/main armhf Package
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1392285] Re: mountall counts remounts again, causing the boot procress to stop

[markusj]

** Attachment added: aptitude.log
   
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1392285/+attachment/4259876/+files/aptitude.log

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

Title:
  mountall counts remounts again, causing the boot procress to stop

Status in “mountall” package in Ubuntu:
  New

Bug description:
  For some reason, mountall failed at the last reboot of my home server. The 
box processes a few first boot steps and stops in an early boot phase. Weirdly, 
if the bootloader passed --verbose to the kernel, the boot process went well.
  I compared the logs of a failed and a successful boot process and nailed it 
down to mountall, struggling with a bind mount of a read-only root fs. 
Apparently, mountall counted the remounts again as mounts, causing the total 
mount count to differ from the expected mount count. Therefore, the events 
local-filesystems and filesystems have not been emitted.

  Watch for lines related to /mnt/root in mountall.log, this mount is
  counted four times instead of just once.

  Workarounds: 
  1. Boot with init=/bin/sh, open a getty instance, exec init and run mountall 
there after the boot process has been stuck.
  2. Set the problematic mount to noauto and mount it by yourself later.

  One additional remark: This issue appeared the first time two days
  ago, without having changed anything at all at my fstab. During the
  uptime of ~10 days, a few packages have been installed or updated, but
  nothing mission critical. I have no idea what triggered this issue.

  $ lsb_release -rd
  Description:Ubuntu 14.04.1 LTS
  Release:14.04

  $ apt-cache policy mountall
  mountall:
Installiert:   2.53
Installationskandidat: 2.53
Versionstabelle:
   *** 2.53 0
  500 http://ports.ubuntu.com/ubuntu-ports/ trusty/main armhf Package
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1392267] Re: [SRU] New stable release 2.42.1

[Iain Lane]

** Changed in: glib2.0 (Ubuntu)
   Status: New = In Progress

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

Title:
  [SRU] New stable release 2.42.1

Status in “glib2.0” package in Ubuntu:
  In Progress

Bug description:
  [ Description ]

  Upload this stable bugfix release

  Overview of changes in GLib 2.42.1
  ==

  * This release disables deprecation warnings by default ← we already
  had this cherry-picked

  * Bugs fixed:
   728256 gcredentials: add NetBSD support
   736806 gtask: Fix reference count loop causing leaks
   737143 Include stdint.h in glib/valgrind.h
   738170 g_byte_array_new_take() doesn't initialize array-alloc
   738197 g_cond_timed_wait() doesn't time out on Mac OS X·

  [ QA  regression potential ]

  Under the GNOME MRE, assume the bugs are fixed. Installl the update 
  use your system as normal. If we don't see any regressions either
  manually or on errors, we're good.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1392267/+subscriptions

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

[Touch-packages] [Bug 1391354] Re: Failure to boot ephemeral image for Utopic Fast Installer deployment

[Martin Pitt]

For comparison I downloaded/booted current trusty, and I get the can
not connect to iSCSI daemon error there, too. But I do get a PATH_ID:

lrwxrwxrwx 1 root root 9 Nov 13 11:52 /dev/disk/by-path/ip-10.0.2.2:3260
-iscsi-trusty-daily-maas-amd64-lun-1 - ../../sda

ubuntu@ubuntu:~$ sudo udevadm -d test-builtin path_id /sys/block/sda
sudo: unable to resolve host ubuntu
calling: test-builtin
=== trie on-disk ===
tool version:  204
file size: 5660180 bytes
header size 80 bytes
strings1265196 bytes
nodes  4394904 bytes
load module index
device 0x15fe840 has devpath 
'/devices/platform/host2/session1/target2:0:0/2:0:0:1/block/sda'
device 0x1601ea0 has devpath 
'/devices/platform/host2/session1/target2:0:0/2:0:0:1'
device 0x16024b0 has devpath '/devices/platform/host2/session1/target2:0:0'
device 0x1602ab0 has devpath '/devices/platform/host2/session1'
device 0x1602fc0 has devpath '/devices/platform/host2'
device 0x1603590 has devpath '/devices/platform'
device 0x1603f30 has devpath 
'/devices/platform/host2/session1/iscsi_session/session1'
device 0x16047c0 has devpath 
'/devices/platform/host2/session1/connection1:0/iscsi_connection/connection1:0'
ID_PATH=ip-10.0.2.2:3260-iscsi-trusty-daily-maas-amd64-lun-1
ID_PATH_TAG=ip-10_0_2_2_3260-iscsi-trusty-daily-maas-amd64-lun-1
unload module index


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

** Summary changed:

- Failure to boot ephemeral image for Utopic Fast Installer deployment
+ Failure to boot ephemeral image for Utopic Fast Installer deployment: no 
ID_PATH for iSCSI device any more

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

** Changed in: systemd (Ubuntu Utopic)
   Status: New = Confirmed

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

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

Title:
  Failure to boot ephemeral image for Utopic Fast Installer deployment:
  no ID_PATH for iSCSI device any more

Status in MAAS:
  Incomplete
Status in “systemd” package in Ubuntu:
  Confirmed
Status in “systemd” source package in Utopic:
  Confirmed

Bug description:
  I am running into issues with the latest Utopic daily ephemeral images
  for Utopic:

Release ArchitectureSizeNodes deployed  Last update
14.10   i386391.2 MB0   Tue Nov 11 00:36:04 2014
14.10   amd64   395.6 MB0   Tue Nov 11 00:36:04 2014
14.10   ppc64el 425.8 MB1   Tue Nov 11 00:36:03 2014
14.04 LTS   i386373.3 MB0   Tue Nov 11 00:36:04 2014
14.04 LTS   ppc64el 408.5 MB1   Tue Nov 11 00:36:04 2014
14.04 LTS   amd64   380.5 MB52  Tue Nov 11 00:36:03 2014
12.04 LTS   amd64   517.5 MB245 Tue Nov 11 00:36:05 2014
12.04 LTS   i386487.3 MB0   Tue Nov 11 00:36:05 2014

  I have tried installing 2 physical servers, moline and premier as well
  as a ppc64el VM, huffman-vm10, and I get the same failure for each.

  

  iscsistart: Logging into 
iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-ppc64el-generic-utopic-daily 
10.245.0.10:3260,1
  iscsistart: can not connect to iSCSI daemon (111)!
  iscsistart: version 2.0-873
  [   17.810223] sd 1:0:0:1: [sdb] Write Protect is on
  [   17.811504] sd 1:0:0:1: [sdb] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
  [   17.828817]  sdb: unknown partition table
  [   17.839360] sd 1:0:0:1: [sdb] Attached SCSI disk
  iscsistart: initiator reported error (15 - session exists)
  done.
  [   35.868265] random: nonblocking pool is initialized
  Begin: Loading essential drivers ... done.
  Begin: Running /scripts/init-premount ... done.
  Begin: Mounting root file system ... Begin: Running /scripts/local-top ... 
IP-Config: eth0 hardware address 52:54:00:95:6b:54 mtu 1500 DHCP RARP
  IP-Config: no response after 2 secs - giving up
  IP-Config: eth0 hardware address 52:54:00:95:6b:54 mtu 1500 DHCP RARP
  hostname huffman-vm-10 hostname huffman-vm-10 IP-Config: eth0 complete (dhcp 
from 10.245.0.10):
   address: 10.245.0.173 broadcast: 10.245.63.255netmask: 255.255.192.0 
  
   gateway: 10.245.0.1   dns0 : 10.245.0.10  dns1   : 0.0.0.0   
  
   domain : oil 
   rootserver: 10.245.0.10 rootpath: 
   filename  : pxelinux.0
  iscsistart: Logging into 
iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-ppc64el-generic-utopic-daily 
10.245.0.10:3260,1
  iscsistart: version 2.0-873
  iscsistart: Connection1:0 to [target: 
iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-ppc64el-generic-utopic-daily, 
portal: 10.245.0.10,3260] through 

[Touch-packages] [Bug 1391354] Re: Failure to boot ephemeral image for Utopic Fast Installer deployment: no ID_PATH for iSCSI device any more

[Martin Pitt]

Notes for reproduction:

ipaddr=10.0.2.2
release=trusty  # or utopic
kvm -m 512 -serial stdio -kernel ${release}-kernel -initrd ${release}-initrd 
-append nomodeset iscsi_target_name=${release}-daily-maas-amd64 
iscsi_target_ip=$ipaddr iscsi_initiator=maas-enlist ip=maas-enlist:BOOTIF 
BOOTIF=01-52-54-00-12-34-56 ro root=/dev/sda overlayroot=tmpfs  console=tty1 
console=ttyS0 ds=nocloud-net;seedfrom=http://$ipaddr:32600/;

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

Title:
  Failure to boot ephemeral image for Utopic Fast Installer deployment:
  no ID_PATH for iSCSI device any more

Status in MAAS:
  Incomplete
Status in “systemd” package in Ubuntu:
  Confirmed
Status in “systemd” source package in Utopic:
  Confirmed

Bug description:
  I am running into issues with the latest Utopic daily ephemeral images
  for Utopic:

Release ArchitectureSizeNodes deployed  Last update
14.10   i386391.2 MB0   Tue Nov 11 00:36:04 2014
14.10   amd64   395.6 MB0   Tue Nov 11 00:36:04 2014
14.10   ppc64el 425.8 MB1   Tue Nov 11 00:36:03 2014
14.04 LTS   i386373.3 MB0   Tue Nov 11 00:36:04 2014
14.04 LTS   ppc64el 408.5 MB1   Tue Nov 11 00:36:04 2014
14.04 LTS   amd64   380.5 MB52  Tue Nov 11 00:36:03 2014
12.04 LTS   amd64   517.5 MB245 Tue Nov 11 00:36:05 2014
12.04 LTS   i386487.3 MB0   Tue Nov 11 00:36:05 2014

  I have tried installing 2 physical servers, moline and premier as well
  as a ppc64el VM, huffman-vm10, and I get the same failure for each.

  

  iscsistart: Logging into 
iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-ppc64el-generic-utopic-daily 
10.245.0.10:3260,1
  iscsistart: can not connect to iSCSI daemon (111)!
  iscsistart: version 2.0-873
  [   17.810223] sd 1:0:0:1: [sdb] Write Protect is on
  [   17.811504] sd 1:0:0:1: [sdb] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
  [   17.828817]  sdb: unknown partition table
  [   17.839360] sd 1:0:0:1: [sdb] Attached SCSI disk
  iscsistart: initiator reported error (15 - session exists)
  done.
  [   35.868265] random: nonblocking pool is initialized
  Begin: Loading essential drivers ... done.
  Begin: Running /scripts/init-premount ... done.
  Begin: Mounting root file system ... Begin: Running /scripts/local-top ... 
IP-Config: eth0 hardware address 52:54:00:95:6b:54 mtu 1500 DHCP RARP
  IP-Config: no response after 2 secs - giving up
  IP-Config: eth0 hardware address 52:54:00:95:6b:54 mtu 1500 DHCP RARP
  hostname huffman-vm-10 hostname huffman-vm-10 IP-Config: eth0 complete (dhcp 
from 10.245.0.10):
   address: 10.245.0.173 broadcast: 10.245.63.255netmask: 255.255.192.0 
  
   gateway: 10.245.0.1   dns0 : 10.245.0.10  dns1   : 0.0.0.0   
  
   domain : oil 
   rootserver: 10.245.0.10 rootpath: 
   filename  : pxelinux.0
  iscsistart: Logging into 
iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-ppc64el-generic-utopic-daily 
10.245.0.10:3260,1
  iscsistart: version 2.0-873
  iscsistart: Connection1:0 to [target: 
iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-ppc64el-generic-utopic-daily, 
portal: 10.245.0.10,3260] through [iface: default] is operational now
  iscsistart: Logging into 
iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-ppc64el-generic-utopic-daily 
10.245.0.10:3260,1
  iscsistart: can not connect to iSCSI daemon (111)!
  iscsistart: version 2.0-873
  iscsistart: initiator reported error (15 - session exists)
  done.
  Gave up waiting for root device.  Common problems:
   - Boot args (cat /proc/cmdline)
 - Check rootdelay= (did the system wait long enough?)
 - Check root= (did the system wait for the right device?)
   - Missing modules (cat /proc/modules; ls /dev)
  ALERT!  
/dev/disk/by-path/ip-10.245.0.10:3260-iscsi-iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-ppc64el-generic-utopic-daily-lun-1
 does not exist.  Dropping to a shell!
  [   78.856173] hidraw: raw HID events driver (C) Jiri Kosina
  [   78.860069] usbcore: registered new interface driver usbhid
  [   78.860272] usbhid: USB HID core driver

  
  BusyBox v1.22.1 (Ubuntu 1:1.22.0-8ubuntu1) built-in shell (ash)
  Enter 'help' for a list of built-in commands.

  (initramfs)

  
  

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

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

[Touch-packages] [Bug 1391354] Re: Failure to boot ephemeral image for Utopic Fast Installer deployment: no ID_PATH for iSCSI device any more

[Martin Pitt]

I confirm that this is fixed in vivid's udev. sudo ./udevadm -d test-
builtin path_id /sys/block/sda shows ID_PATH=ip-10.0.2.2:3260-iscsi-
utopic-daily-maas-amd64-lun-1 again, and replacing /lib/systemd/systemd-
udevd with 215-5's binary gets the by-path/ symlink again. So now off to
finding the fix in the history..

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

** Changed in: systemd (Ubuntu Utopic)
   Status: Confirmed = Triaged

** Changed in: systemd (Ubuntu Utopic)
 Assignee: (unassigned) = Martin Pitt (pitti)

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

Title:
  Failure to boot ephemeral image for Utopic Fast Installer deployment:
  no ID_PATH for iSCSI device any more

Status in MAAS:
  Incomplete
Status in “systemd” package in Ubuntu:
  Fix Released
Status in “systemd” source package in Utopic:
  Triaged

Bug description:
  I am running into issues with the latest Utopic daily ephemeral images
  for Utopic:

Release ArchitectureSizeNodes deployed  Last update
14.10   i386391.2 MB0   Tue Nov 11 00:36:04 2014
14.10   amd64   395.6 MB0   Tue Nov 11 00:36:04 2014
14.10   ppc64el 425.8 MB1   Tue Nov 11 00:36:03 2014
14.04 LTS   i386373.3 MB0   Tue Nov 11 00:36:04 2014
14.04 LTS   ppc64el 408.5 MB1   Tue Nov 11 00:36:04 2014
14.04 LTS   amd64   380.5 MB52  Tue Nov 11 00:36:03 2014
12.04 LTS   amd64   517.5 MB245 Tue Nov 11 00:36:05 2014
12.04 LTS   i386487.3 MB0   Tue Nov 11 00:36:05 2014

  I have tried installing 2 physical servers, moline and premier as well
  as a ppc64el VM, huffman-vm10, and I get the same failure for each.

  

  iscsistart: Logging into 
iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-ppc64el-generic-utopic-daily 
10.245.0.10:3260,1
  iscsistart: can not connect to iSCSI daemon (111)!
  iscsistart: version 2.0-873
  [   17.810223] sd 1:0:0:1: [sdb] Write Protect is on
  [   17.811504] sd 1:0:0:1: [sdb] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
  [   17.828817]  sdb: unknown partition table
  [   17.839360] sd 1:0:0:1: [sdb] Attached SCSI disk
  iscsistart: initiator reported error (15 - session exists)
  done.
  [   35.868265] random: nonblocking pool is initialized
  Begin: Loading essential drivers ... done.
  Begin: Running /scripts/init-premount ... done.
  Begin: Mounting root file system ... Begin: Running /scripts/local-top ... 
IP-Config: eth0 hardware address 52:54:00:95:6b:54 mtu 1500 DHCP RARP
  IP-Config: no response after 2 secs - giving up
  IP-Config: eth0 hardware address 52:54:00:95:6b:54 mtu 1500 DHCP RARP
  hostname huffman-vm-10 hostname huffman-vm-10 IP-Config: eth0 complete (dhcp 
from 10.245.0.10):
   address: 10.245.0.173 broadcast: 10.245.63.255netmask: 255.255.192.0 
  
   gateway: 10.245.0.1   dns0 : 10.245.0.10  dns1   : 0.0.0.0   
  
   domain : oil 
   rootserver: 10.245.0.10 rootpath: 
   filename  : pxelinux.0
  iscsistart: Logging into 
iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-ppc64el-generic-utopic-daily 
10.245.0.10:3260,1
  iscsistart: version 2.0-873
  iscsistart: Connection1:0 to [target: 
iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-ppc64el-generic-utopic-daily, 
portal: 10.245.0.10,3260] through [iface: default] is operational now
  iscsistart: Logging into 
iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-ppc64el-generic-utopic-daily 
10.245.0.10:3260,1
  iscsistart: can not connect to iSCSI daemon (111)!
  iscsistart: version 2.0-873
  iscsistart: initiator reported error (15 - session exists)
  done.
  Gave up waiting for root device.  Common problems:
   - Boot args (cat /proc/cmdline)
 - Check rootdelay= (did the system wait long enough?)
 - Check root= (did the system wait for the right device?)
   - Missing modules (cat /proc/modules; ls /dev)
  ALERT!  
/dev/disk/by-path/ip-10.245.0.10:3260-iscsi-iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-ppc64el-generic-utopic-daily-lun-1
 does not exist.  Dropping to a shell!
  [   78.856173] hidraw: raw HID events driver (C) Jiri Kosina
  [   78.860069] usbcore: registered new interface driver usbhid
  [   78.860272] usbhid: USB HID core driver

  
  BusyBox v1.22.1 (Ubuntu 1:1.22.0-8ubuntu1) built-in shell (ash)
  Enter 'help' for a list of built-in commands.

  (initramfs)

  
  

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post 

[Touch-packages] [Bug 1375259] Re: [App switcher, Spread] Black apps and app loading screens not visible in spread

[Michael Zanetti]

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

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

Title:
  [App switcher, Spread] Black apps and app loading screens not visible
  in spread

Status in Ubuntu UX bugs:
  Fix Committed
Status in “unity8” package in Ubuntu:
  In Progress

Bug description:
  For example camera application and application loading screens cannot
  be distinguished from the application spread background because they
  are all black. We would like to keep the dark background but change it
  a bit lighter version so that black apps pop out a bit better from the
  background.

  Desired design:

  Change spread background from black to #11

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

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

[Touch-packages] [Bug 1371248] Re: [Browser] No home button to take you back to the default home page

[Olivier Tilloy]

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

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

Title:
  [Browser] No home button to take you back to the default home page

Status in Ubuntu UX bugs:
  Fix Committed
Status in Web Browser App:
  Confirmed
Status in “webbrowser-app” package in Ubuntu:
  Confirmed

Bug description:
  STEPS:
  1. Open the browser on a fresh flash
  2. Note the home page
  3. Browse to planet.ubuntu.com
  4. Close the browser
  5. Open the browser
  6. Try and get back to the original home page.

  EXPECTATION:
  Every browser has a home button, it may or may not be used on mobiles but at 
some point you might want to go back to that page.

  ACTUAL:
  Once you close the browser the history registers the home page but after a 
while that would disappear then you would be left with no reference of it.

  -- SOLUTION --
  Add a default bookmark in the New Tab screen
  http://start.ubuntu.com/current/?sourceid=hp
  Title=Ubuntu Start page

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

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

[Touch-packages] [Bug 1375259] Re: [App switcher, Spread] Black apps and app loading screens not visible in spread

[Launchpad Bug Tracker]

** Branch linked: lp:~mzanetti/unity8/fix-spread-bg

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

Title:
  [App switcher, Spread] Black apps and app loading screens not visible
  in spread

Status in Ubuntu UX bugs:
  Fix Committed
Status in “unity8” package in Ubuntu:
  In Progress

Bug description:
  For example camera application and application loading screens cannot
  be distinguished from the application spread background because they
  are all black. We would like to keep the dark background but change it
  a bit lighter version so that black apps pop out a bit better from the
  background.

  Desired design:

  Change spread background from black to #11

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

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

[Touch-packages] [Bug 1392297] [NEW] resolvconf 1.69ubuntu1.1 breaks network install

[Cs-gon]

Public bug reported:

We are experiencing problems with Ubuntu 14.04 network installations,
when using the 1.69ubuntu1.1 version of resolvconf. With this version
the file /etc/resolv.conf gets reset to an empty file (does only include
just the standard resolvconf comments) during the installation of the
resolvconf package. After that the name resolution doesn't work anymore
and the subsequent installation steps fail.

If we use the 1.69ubuntu1 version, everything works fine.

If I make a diff of both package contents, the most significant change
seems to be the inclusion of a new Sys-V init script, which (besides
other things) removes the contents of the resolvconf runtime directories
when called with the option start, and the postinst script calls
invoke-rc.d resolvconf start at the end (included by dh_installinit),
which I think should do nothing during the installation because of
policy-rc.d (right?), but I wonder if it actually get's called and
removes the resolv.conf file that got migrated to the runtime
directories earlier in the postinst script. At least that would explain
our problems, because I don't really see anything else, that could cause
this problem.

I see that the inclusion of the new init script is coming from debian,
and they call the dh_installinit with the option --no-start in
debian/rules, while the Ubuntu package calls the dh_installinit only
with the option -r. And debian inserts the debhelper code a lot
earlier in the postinst script.

Could this be what's causing the problem? As soon I have more time, I
will try to debug this further and provide more information.

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

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

Title:
  resolvconf 1.69ubuntu1.1 breaks network install

Status in “resolvconf” package in Ubuntu:
  New

Bug description:
  We are experiencing problems with Ubuntu 14.04 network installations,
  when using the 1.69ubuntu1.1 version of resolvconf. With this version
  the file /etc/resolv.conf gets reset to an empty file (does only
  include just the standard resolvconf comments) during the installation
  of the resolvconf package. After that the name resolution doesn't work
  anymore and the subsequent installation steps fail.

  If we use the 1.69ubuntu1 version, everything works fine.

  If I make a diff of both package contents, the most significant change
  seems to be the inclusion of a new Sys-V init script, which (besides
  other things) removes the contents of the resolvconf runtime
  directories when called with the option start, and the postinst
  script calls invoke-rc.d resolvconf start at the end (included by
  dh_installinit), which I think should do nothing during the
  installation because of policy-rc.d (right?), but I wonder if it
  actually get's called and removes the resolv.conf file that got
  migrated to the runtime directories earlier in the postinst script. At
  least that would explain our problems, because I don't really see
  anything else, that could cause this problem.

  I see that the inclusion of the new init script is coming from debian,
  and they call the dh_installinit with the option --no-start in
  debian/rules, while the Ubuntu package calls the dh_installinit only
  with the option -r. And debian inserts the debhelper code a lot
  earlier in the postinst script.

  Could this be what's causing the problem? As soon I have more time, I
  will try to debug this further and provide more information.

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

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

[Touch-packages] [Bug 1391609] Re: [regression] on desktop, address bar not empty when creating a new tab from the tabs view

[Launchpad Bug Tracker]

This bug was fixed in the package webbrowser-app -
0.23+15.04.20141113-0ubuntu1

---
webbrowser-app (0.23+15.04.20141113-0ubuntu1) vivid; urgency=low

  [ Michael Sheldon ]
  * Add mimetype and file extension mappings for the new EBooks
ContentType. (LP: #1383732)

  [ Olivier Tilloy ]
  * Update runtime dependencies of -autopilot packages. Now that
autopilot has been removed from touch images, autopilot-touch is
what we should depend on to ensure all dependencies are correctly
installed prior to running tests using phablet-test-run.
  * Factor the security certificate details popover out of the
AddressBar component, for improved maintainability.
  * Simplify quite a bit the machinery needed to set up the QML tests.
  * Always load the webview for a new tab right away. (LP: #1391609)
  * Set a stroke color on toolbar buttons. (LP: #1351200)
  * Add a sanity unit test that runs flake8 on the autopilot tests code.
 -- Ubuntu daily release ps-jenk...@lists.canonical.com   Thu, 13 Nov 2014 
06:24:30 +

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

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

Title:
  [regression] on desktop, address bar not empty when creating a new tab
  from the tabs view

Status in Web Browser App:
  In Progress
Status in “webbrowser-app” package in Ubuntu:
  Fix Released

Bug description:
  (this regression was most likely introduced by revision 795 of lp
  :webbrowser-app, it affects only desktop where the address bar gets
  active focus when opening a new tab)

  Steps to reproduce:

   1) on desktop, launch the browser with webbrowser-app --new-session
   2) Open the drawer, select open tabs to open the tabs view
   3) In the tabs view, click the Add button in the toolbar, a new tab opens 
and the address bar is given active focus

  Expected result: the address bar is cleared

  Current result: the address of the previously open tab remains

  Note that creating a new tab directly from the drawer doesn’t exhibit
  this faulty behaviour.

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

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

[Touch-packages] [Bug 1383085] Re: background in app carousel view does not show background image

[Michael Zanetti]

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

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

Title:
  background in app carousel view does not show background image

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

Bug description:
  A swipe from the right edge of the phone towards the center fans out
  all the apps, showing a carousel-like view.

  However, the background is always black, whereas I would have expected
  the background to be the selected background image.

  Black is problematic since if one of the open apps is the camera, and
  the camera is face-down on a table for example, it will be showing a
  black image meaning that the camera app is presented as a pure black
  preview on a black background.

  krillin, r117.

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

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

[Touch-packages] [Bug 1351200] Re: Use stroke buttons in the toolbars

[Launchpad Bug Tracker]

This bug was fixed in the package webbrowser-app -
0.23+15.04.20141113-0ubuntu1

---
webbrowser-app (0.23+15.04.20141113-0ubuntu1) vivid; urgency=low

  [ Michael Sheldon ]
  * Add mimetype and file extension mappings for the new EBooks
ContentType. (LP: #1383732)

  [ Olivier Tilloy ]
  * Update runtime dependencies of -autopilot packages. Now that
autopilot has been removed from touch images, autopilot-touch is
what we should depend on to ensure all dependencies are correctly
installed prior to running tests using phablet-test-run.
  * Factor the security certificate details popover out of the
AddressBar component, for improved maintainability.
  * Simplify quite a bit the machinery needed to set up the QML tests.
  * Always load the webview for a new tab right away. (LP: #1391609)
  * Set a stroke color on toolbar buttons. (LP: #1351200)
  * Add a sanity unit test that runs flake8 on the autopilot tests code.
 -- Ubuntu daily release ps-jenk...@lists.canonical.com   Thu, 13 Nov 2014 
06:24:30 +

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

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

Title:
  Use stroke buttons in the toolbars

Status in Web Browser App:
  In Progress
Status in “webbrowser-app” package in Ubuntu:
  Fix Released
Status in “webbrowser-app” package in Ubuntu RTM:
  Confirmed

Bug description:
  The visual spec requires stroke buttons to be used in toolbars (e.g. in the 
tabs view or the history view).
  Stroke buttons are not available yet in the UITK (but work is in progress), 
this bug exists to track their use in webbrowser-app once available in the 
toolkit.

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

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

[Touch-packages] [Bug 1297234] Re: Live session set wrong keyboard layout and time zone

[ernie]

This issue still exists on all our installs at the school were I work as
systems administrator. The issue is not constant but every now and then
one has to click on language  and choose Swedish to reactivate the
Swedish keyboard. Is there a viable solution i.e permanent. I have tried
some workarounds that In have read about but none are permanent.

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

Title:
  Live session set wrong keyboard layout and time zone

Status in “console-setup” package in Ubuntu:
  Expired
Status in “ibus” package in Ubuntu:
  Expired
Status in “ubiquity” package in Ubuntu:
  Confirmed
Status in “console-setup” source package in Trusty:
  Invalid
Status in “ibus” source package in Trusty:
  Invalid
Status in “ubiquity” source package in Trusty:
  Invalid

Bug description:
  When I boot the Ubuntu Studio 14.04 beta 2 testing it will start with
  keyboard set to English US and time zone as UTC. Usually I believe
  this would be localized to my Swedish keyboard and CET.

  ubuntu-studio@ubuntu-studio:~$ lsb_release -rd
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04

  ubuntu-studio@ubuntu-studio:~$ apt-cache policy keyboard-configuration
  keyboard-configuration:
Installed: 1.70ubuntu8
Candidate: 1.70ubuntu8

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: keyboard-configuration 1.70ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-19.40-lowlatency 3.13.6
  Uname: Linux 3.13.0-19-lowlatency i686
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: i386
  CasperVersion: 1.339
  CurrentDesktop: XFCE
  Date: Tue Mar 25 11:33:44 2014
  LiveMediaBuild: Ubuntu-Studio 14.04 LTS Trusty Tahr - Beta i386 (20140325)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: console-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1383732] Re: E-book content type

[Launchpad Bug Tracker]

This bug was fixed in the package webbrowser-app -
0.23+15.04.20141113-0ubuntu1

---
webbrowser-app (0.23+15.04.20141113-0ubuntu1) vivid; urgency=low

  [ Michael Sheldon ]
  * Add mimetype and file extension mappings for the new EBooks
ContentType. (LP: #1383732)

  [ Olivier Tilloy ]
  * Update runtime dependencies of -autopilot packages. Now that
autopilot has been removed from touch images, autopilot-touch is
what we should depend on to ensure all dependencies are correctly
installed prior to running tests using phablet-test-run.
  * Factor the security certificate details popover out of the
AddressBar component, for improved maintainability.
  * Simplify quite a bit the machinery needed to set up the QML tests.
  * Always load the webview for a new tab right away. (LP: #1391609)
  * Set a stroke color on toolbar buttons. (LP: #1351200)
  * Add a sanity unit test that runs flake8 on the autopilot tests code.
 -- Ubuntu daily release ps-jenk...@lists.canonical.com   Thu, 13 Nov 2014 
06:24:30 +

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

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

Title:
  E-book content type

Status in “content-hub” package in Ubuntu:
  Fix Released
Status in “webbrowser-app” package in Ubuntu:
  Fix Released

Bug description:
  I'm writing an Epub reader which I'd like to interface with the
  Content Hub.  To do this, we need an e-book content type.

  There are several different formats for e-books (txt, html, epub,
  mobi, pdf, etc.).  I don't know if all of them should be combined into
  a single type or if each should have their own.  Also, some of those
  formats are used for purposes other than e-books.  My reader only
  supports epubs at the moment.  These have mimetype
  application/epub+zip and .epub file extension.

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

-- 
Mailing list: https://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 1003950] Re: launcher does not show minimized update manager while clicked

[Jeb E.]

A bug is a bug

On Thu, Nov 13, 2014, 3:50 AM John Muir 1003...@bugs.launchpad.net
wrote:

 This bug appears on my 14.04 twin-screen PC running Unity 7.2.3 and my
 14.10 laptop running Unity 7.3.1.
 So I don't believe it's anything to do with the number of screens.

 --
 You received this bug notification because you are subscribed to a
 duplicate bug report (925260).
 https://bugs.launchpad.net/bugs/1003950

 Title:
   launcher does not show minimized update manager while clicked

 Status in Unity:
   Fix Released
 Status in Unity 5.0 series:
   Fix Released
 Status in Unity 6.0 series:
   Fix Released
 Status in “unity” package in Ubuntu:
   Fix Released
 Status in “update-manager” package in Ubuntu:
   Confirmed
 Status in “unity” source package in Precise:
   Fix Released
 Status in “update-manager” source package in Precise:
   Confirmed
 Status in “unity” source package in Quantal:
   Fix Released
 Status in “update-manager” source package in Quantal:
   Confirmed

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

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

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

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

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


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

Title:
  launcher does not show minimized update manager while clicked

Status in Unity:
  Fix Released
Status in Unity 5.0 series:
  Fix Released
Status in Unity 6.0 series:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released
Status in “update-manager” package in Ubuntu:
  Confirmed
Status in “unity” source package in Precise:
  Fix Released
Status in “update-manager” source package in Precise:
  Confirmed
Status in “unity” source package in Quantal:
  Fix Released
Status in “update-manager” source package in Quantal:
  Confirmed

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

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

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

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

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

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

[Touch-packages] [Bug 1392292] Re: Clock doesn't update when switching time from manual to automatic

[Sebastien Bacher]

not that you mention flight mode, automatic is ntp and requires data to
be enabled

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

Title:
  Clock doesn't update when switching time from manual to automatic

Status in “systemd” package in Ubuntu:
  New

Bug description:
  TEST CASE:
  1. Go to system-settings/datetime and switch the phone to manual date/time 
update and set a date/time different from your current time
  2. Switch back to automatic
  3. Wait until clock updates to the right date/time

  EXPECTED RESULT
  The clock of the device is updated when settings is switched to automatic

  ACTUAL RESULT
  The clock of the device doesn't update unless flight mode it toggle on/off

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: ubuntu-system-settings 0.3+14.10.20141104~rtm-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Thu Nov 13 11:51:22 2014
  InstallationDate: Installed on 2014-11-12 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141112-181954)
  SourcePackage: ubuntu-system-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1392292] Re: Clock doesn't update when switching time from manual to automatic

[Sebastien Bacher]

Thanks but I can't confirm that, after selecting automatic the time at
the bottom of the settings panel catch up less than 10 seconds later. In
any case not a settings bug, we call the systemd's helper to change to
ntp on, if that doesn't work it's an issue with ntp/systemd

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

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

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

Title:
  Clock doesn't update when switching time from manual to automatic

Status in “systemd” package in Ubuntu:
  New

Bug description:
  TEST CASE:
  1. Go to system-settings/datetime and switch the phone to manual date/time 
update and set a date/time different from your current time
  2. Switch back to automatic
  3. Wait until clock updates to the right date/time

  EXPECTED RESULT
  The clock of the device is updated when settings is switched to automatic

  ACTUAL RESULT
  The clock of the device doesn't update unless flight mode it toggle on/off

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: ubuntu-system-settings 0.3+14.10.20141104~rtm-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Thu Nov 13 11:51:22 2014
  InstallationDate: Installed on 2014-11-12 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141112-181954)
  SourcePackage: ubuntu-system-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1391609] Re: [regression] on desktop, address bar not empty when creating a new tab from the tabs view

[Olivier Tilloy]

** Changed in: webbrowser-app
   Status: In Progress = Fix Released

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

Title:
  [regression] on desktop, address bar not empty when creating a new tab
  from the tabs view

Status in Web Browser App:
  Fix Released
Status in “webbrowser-app” package in Ubuntu:
  Fix Released

Bug description:
  (this regression was most likely introduced by revision 795 of lp
  :webbrowser-app, it affects only desktop where the address bar gets
  active focus when opening a new tab)

  Steps to reproduce:

   1) on desktop, launch the browser with webbrowser-app --new-session
   2) Open the drawer, select open tabs to open the tabs view
   3) In the tabs view, click the Add button in the toolbar, a new tab opens 
and the address bar is given active focus

  Expected result: the address bar is cleared

  Current result: the address of the previously open tab remains

  Note that creating a new tab directly from the drawer doesn’t exhibit
  this faulty behaviour.

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

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

[Touch-packages] [Bug 1351200] Re: Use stroke buttons in the toolbars

[Olivier Tilloy]

** Changed in: webbrowser-app
   Status: In Progress = Fix Released

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

Title:
  Use stroke buttons in the toolbars

Status in Web Browser App:
  Fix Released
Status in “webbrowser-app” package in Ubuntu:
  Fix Released
Status in “webbrowser-app” package in Ubuntu RTM:
  Confirmed

Bug description:
  The visual spec requires stroke buttons to be used in toolbars (e.g. in the 
tabs view or the history view).
  Stroke buttons are not available yet in the UITK (but work is in progress), 
this bug exists to track their use in webbrowser-app once available in the 
toolkit.

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

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

[Touch-packages] [Bug 1392307] [NEW] Can submit reviews for click apps that are not in the store

[Alejandro J. Cura]

Public bug reported:

Click apps that are not in the store currently show the input fields to
submit reviews.

I tried submitting one such review; it did not fail, but I think it got
lost because it's never shown back when opening the app preview again.

** Affects: unity-scope-click (Ubuntu)
 Importance: High
 Status: Triaged

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

Title:
  Can submit reviews for click apps that are not in the store

Status in “unity-scope-click” package in Ubuntu:
  Triaged

Bug description:
  Click apps that are not in the store currently show the input fields
  to submit reviews.

  I tried submitting one such review; it did not fail, but I think it
  got lost because it's never shown back when opening the app preview
  again.

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

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

[Touch-packages] [Bug 1392292] Re: Clock doesn't update when switching time from manual to automatic

[Jean-Baptiste Lallement]

I mentioned flight mode because it's a way to resync the clock but when
I switch to automatic wifi and cellular data are both enabled.

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

Title:
  Clock doesn't update when switching time from manual to automatic

Status in “systemd” package in Ubuntu:
  New

Bug description:
  TEST CASE:
  1. Go to system-settings/datetime and switch the phone to manual date/time 
update and set a date/time different from your current time
  2. Switch back to automatic
  3. Wait until clock updates to the right date/time

  EXPECTED RESULT
  The clock of the device is updated when settings is switched to automatic

  ACTUAL RESULT
  The clock of the device doesn't update unless flight mode it toggle on/off

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: ubuntu-system-settings 0.3+14.10.20141104~rtm-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Thu Nov 13 11:51:22 2014
  InstallationDate: Installed on 2014-11-12 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141112-181954)
  SourcePackage: ubuntu-system-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1392306] [NEW] Swipe to remove/answer/switch inconsistent

[Andrea Cimitan]

Public bug reported:

Hi guys, I noticed the horizontal swipes in the interface behave in
different ways meaning different things, I wish we could have common
positive/negative meanings on the directions they are applied.

On snap decision calls, a left to right swipe has a positive meaning, answer 
the call.
On indicator message, a left to right swipe has a negative meaning, remove the 
message.

I guess the same applies to apps, contact app does left to right with a
negative meaning, to remove the contact.

Lock screen can be swiped away any direction, but on the edge demo we
recommend doing a right to left for removing the lockscreen.

A right to left edge swipe has a meaning of switching context, like
swiping it away (maybe negative meaning or we should ignore the case?)

Can we come up with a consistent behaviour? What you think?

** Affects: ubuntu-ux
 Importance: Undecided
 Status: New

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

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

** Summary changed:

- Swipe to delete/answer/switch behaves inconsistently
+ Swipe to remove/answer/switch inconsistent

** Description changed:

- Hi guys, I noticed the horizontal swipes in the interface behaves in
+ Hi guys, I noticed the horizontal swipes in the interface behave in
  different ways meaning different things, I wish we could have common
  positive/negative meanings on the directions they are applied.
  
  On snap decision calls, a left to right swipe has a positive meaning, answer 
the call.
  On indicator message, a left to right swipe has a negative meaning, remove 
the message.
  
  I guess the same applies to apps, contact app does left to right with a
  negative meaning, to remove the contact.
  
  Lock screen can be swiped away any direction, but on the edge demo we
  recommend doing a right to left for removing the lockscreen.
  
  A right to left edge swipe has a meaning of switching context, like
  swiping it away (maybe negative meaning or we should ignore the case?)
  
  Can we come up with a consistent behaviour? What you think?

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

Title:
  Swipe to remove/answer/switch inconsistent

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

Bug description:
  Hi guys, I noticed the horizontal swipes in the interface behave in
  different ways meaning different things, I wish we could have common
  positive/negative meanings on the directions they are applied.

  On snap decision calls, a left to right swipe has a positive meaning, answer 
the call.
  On indicator message, a left to right swipe has a negative meaning, remove 
the message.

  I guess the same applies to apps, contact app does left to right with
  a negative meaning, to remove the contact.

  Lock screen can be swiped away any direction, but on the edge demo we
  recommend doing a right to left for removing the lockscreen.

  A right to left edge swipe has a meaning of switching context, like
  swiping it away (maybe negative meaning or we should ignore the case?)

  Can we come up with a consistent behaviour? What you think?

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

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

[Touch-packages] [Bug 1392292] Re: Clock doesn't update when switching time from manual to automatic

[Jean-Baptiste Lallement]

in my case when I select automatic, the date at the bottom of system-
settings doesn't change.

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

Title:
  Clock doesn't update when switching time from manual to automatic

Status in “systemd” package in Ubuntu:
  New

Bug description:
  TEST CASE:
  1. Go to system-settings/datetime and switch the phone to manual date/time 
update and set a date/time different from your current time
  2. Switch back to automatic
  3. Wait until clock updates to the right date/time

  EXPECTED RESULT
  The clock of the device is updated when settings is switched to automatic

  ACTUAL RESULT
  The clock of the device doesn't update unless flight mode it toggle on/off

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: ubuntu-system-settings 0.3+14.10.20141104~rtm-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Thu Nov 13 11:51:22 2014
  InstallationDate: Installed on 2014-11-12 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141112-181954)
  SourcePackage: ubuntu-system-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1392308] [NEW] Cannot browse indicators in daylight

[Víctor R . Ruiz]

Public bug reported:

While doing GPS tests with the phone in daylight, I found it difficult
to open the location indicator, because of the current color scheme. The
non-active indicators are too dim to be read.

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


** Tags: qa-daily-testing

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

Title:
  Cannot browse indicators in daylight

Status in “unity8” package in Ubuntu:
  New

Bug description:
  While doing GPS tests with the phone in daylight, I found it difficult
  to open the location indicator, because of the current color scheme.
  The non-active indicators are too dim to be read.

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

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

[Touch-packages] [Bug 1336665] Re: [Launcher] Weird bounce back effect when organising items

[Launchpad Bug Tracker]

** Branch linked: lp:~mzanetti/unity8/launcher-snap-after-drag

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

Title:
  [Launcher] Weird bounce back effect when organising items

Status in Ubuntu UX bugs:
  Fix Committed
Status in “unity8” package in Ubuntu:
  In Progress

Bug description:
  Steps to repro:

  1) Long press an item in the Launcher (Quicklist appear)
  2) While long pressing start moving the item (dragdrop mode entered). Item 
detaches from its previous place
  3) Drop the item at the top of the icon column to be the topmost.

  Expected behaviour:
  Item animates nice in to its place without any additional movement.

  Actual behaviour:
  Item animates in to its place ok but also whole column of items moves 
downwards and bounces back.

  --
  Desired solution:
  Expected behaviour above

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

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

[Touch-packages] [Bug 1336665] Re: [Launcher] Weird bounce back effect when organising items

[Michael Zanetti]

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

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

Title:
  [Launcher] Weird bounce back effect when organising items

Status in Ubuntu UX bugs:
  Fix Committed
Status in “unity8” package in Ubuntu:
  In Progress

Bug description:
  Steps to repro:

  1) Long press an item in the Launcher (Quicklist appear)
  2) While long pressing start moving the item (dragdrop mode entered). Item 
detaches from its previous place
  3) Drop the item at the top of the icon column to be the topmost.

  Expected behaviour:
  Item animates nice in to its place without any additional movement.

  Actual behaviour:
  Item animates in to its place ok but also whole column of items moves 
downwards and bounces back.

  --
  Desired solution:
  Expected behaviour above

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

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

[Touch-packages] [Bug 1392308] Re: Cannot browse indicators in daylight

[Michał Sawicz]

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

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

Title:
  Cannot browse indicators in daylight

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

Bug description:
  While doing GPS tests with the phone in daylight, I found it difficult
  to open the location indicator, because of the current color scheme.
  The non-active indicators are too dim to be read.

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

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

[Touch-packages] [Bug 1392306] Re: Swipe to remove/answer/switch inconsistent

[Matthew Paul Thomas]

** Package changed: unity8 (Ubuntu) = indicator-messages (Ubuntu)

** Also affects: dialer-app (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: indicator-messages (Ubuntu)
 Assignee: (unassigned) = Paty Davila (dizzypaty)

** Changed in: dialer-app (Ubuntu)
 Assignee: (unassigned) = Olga Kemmet (olga-kemmet)

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

Title:
  Swipe to remove/answer/switch inconsistent

Status in Ubuntu UX bugs:
  New
Status in “address-book-app” package in Ubuntu:
  New
Status in “dialer-app” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  New

Bug description:
  Hi guys, I noticed the horizontal swipes in the interface behave in
  different ways meaning different things, I wish we could have common
  positive/negative meanings on the directions they are applied.

  On snap decision calls, a left to right swipe has a positive meaning, answer 
the call.
  On indicator message, a left to right swipe has a negative meaning, remove 
the message.

  I guess the same applies to apps, contact app does left to right with
  a negative meaning, to remove the contact.

  Lock screen can be swiped away any direction, but on the edge demo we
  recommend doing a right to left for removing the lockscreen.

  A right to left edge swipe has a meaning of switching context, like
  swiping it away (maybe negative meaning or we should ignore the case?)

  Can we come up with a consistent behaviour? What you think?

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

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

[Touch-packages] [Bug 1392306] Re: Swipe to remove/answer/switch inconsistent

[Sebastien Bacher]

** Package changed: indicator-messages (Ubuntu) = unity8 (Ubuntu)

** Changed in: unity8 (Ubuntu)
 Assignee: Paty Davila (dizzypaty) = (unassigned)

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

Title:
  Swipe to remove/answer/switch inconsistent

Status in Ubuntu UX bugs:
  New
Status in “address-book-app” package in Ubuntu:
  New
Status in “dialer-app” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  New

Bug description:
  Hi guys, I noticed the horizontal swipes in the interface behave in
  different ways meaning different things, I wish we could have common
  positive/negative meanings on the directions they are applied.

  On snap decision calls, a left to right swipe has a positive meaning, answer 
the call.
  On indicator message, a left to right swipe has a negative meaning, remove 
the message.

  I guess the same applies to apps, contact app does left to right with
  a negative meaning, to remove the contact.

  Lock screen can be swiped away any direction, but on the edge demo we
  recommend doing a right to left for removing the lockscreen.

  A right to left edge swipe has a meaning of switching context, like
  swiping it away (maybe negative meaning or we should ignore the case?)

  Can we come up with a consistent behaviour? What you think?

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

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

[Touch-packages] [Bug 1392317] [NEW] Incorrect order of messages with RepeatedMsgReduction on

[Roger Lehmann]

Public bug reported:

In rsyslog Version 7.4.4-1ubuntu2.3 there is a bug which mixes up the order of 
some messages when $RepeatedMsgReduction is enabled.
This can sometimes result in a message missing in the current syslog and being 
printed even days later.
Using Ubuntu 14.04.1 LTS.
[…]
Nov 12 16:32:01 ws-api3 CRON[5572]: pam_unix(cron:session): session closed for 
user www-data
Nov 12 16:33:01 ws-api3 CRON[5582]: pam_unix(cron:session): session opened for 
user www-data by (uid=0)
Nov 10 11:56:01 ws-api3 CRON[5583]: (www-data) CMD (nice -n10 php 
/var/www/api/scripts/import/php/import.php all^I $CL/import.log 2 
$PL/api_cli_er
rlog)
Nov 12 16:33:01 ws-api3 CRON[5583]: (www-data) CMD (nice -n10 php 
/var/www/api/scripts/import/php/import.php all^I $CL/dev_import.log 2 
$PL/dev_ap
i_cli_errlog)
Nov 12 16:33:01 ws-api3 CRON[5582]: pam_unix(cron:session): session closed for 
user www-data
[…]


To reproduce this error, turn on $RepeatedMsgReduction in the rsyslog.conf and 
generate a whole bunch of syslog message, e.g. with the following php script:
?php
for($k=0;$k10;$k++){
 echo ** $k **\n;
 for($i=0;$i32768;$i++){
 exec(logger --id 'log  $k');
 }
}

Result will be (after a short while):
Nov 12 11:17:08 syslogTest vm[21410]: log  0
Nov 12 11:18:05 syslogTest vm[21410]: log  1
Nov 12 11:17:08 syslogTest vm[21412]: log  0
Nov 12 11:18:05 syslogTest vm[21412]: log  1
Nov 12 11:17:08 syslogTest vm[21414]: log  0
Nov 12 11:18:05 syslogTest vm[21414]: log  1

What's pretty suspicious is that after the pool of process IDs is exhausted and 
resettet, old messages are from the same process ID but from the previous 
iteration.
Is RepeatedMsgReduction somehow grouping by process ID? In the first example is 
a cron process using the same process ID like one before, therefore printing 
the old message from Nov, 10. The old message was not at the position inside 
the syslog where it should have been.

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


** Tags: mixed order repeatedmsgreduction

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

Title:
  Incorrect order of messages with RepeatedMsgReduction on

Status in “rsyslog” package in Ubuntu:
  New

Bug description:
  In rsyslog Version 7.4.4-1ubuntu2.3 there is a bug which mixes up the order 
of some messages when $RepeatedMsgReduction is enabled.
  This can sometimes result in a message missing in the current syslog and 
being printed even days later.
  Using Ubuntu 14.04.1 LTS.
  […]
  Nov 12 16:32:01 ws-api3 CRON[5572]: pam_unix(cron:session): session closed 
for user www-data
  Nov 12 16:33:01 ws-api3 CRON[5582]: pam_unix(cron:session): session opened 
for user www-data by (uid=0)
  Nov 10 11:56:01 ws-api3 CRON[5583]: (www-data) CMD (nice -n10 php 
/var/www/api/scripts/import/php/import.php all^I $CL/import.log 2 
$PL/api_cli_er
  rlog)
  Nov 12 16:33:01 ws-api3 CRON[5583]: (www-data) CMD (nice -n10 php 
/var/www/api/scripts/import/php/import.php all^I $CL/dev_import.log 2 
$PL/dev_ap
  i_cli_errlog)
  Nov 12 16:33:01 ws-api3 CRON[5582]: pam_unix(cron:session): session closed 
for user www-data
  […]

  
  To reproduce this error, turn on $RepeatedMsgReduction in the rsyslog.conf 
and generate a whole bunch of syslog message, e.g. with the following php 
script:
  ?php
  for($k=0;$k10;$k++){
   echo ** $k **\n;
   for($i=0;$i32768;$i++){
   exec(logger --id 'log  $k');
   }
  }

  Result will be (after a short while):
  Nov 12 11:17:08 syslogTest vm[21410]: log  0
  Nov 12 11:18:05 syslogTest vm[21410]: log  1
  Nov 12 11:17:08 syslogTest vm[21412]: log  0
  Nov 12 11:18:05 syslogTest vm[21412]: log  1
  Nov 12 11:17:08 syslogTest vm[21414]: log  0
  Nov 12 11:18:05 syslogTest vm[21414]: log  1

  What's pretty suspicious is that after the pool of process IDs is exhausted 
and resettet, old messages are from the same process ID but from the previous 
iteration.
  Is RepeatedMsgReduction somehow grouping by process ID? In the first example 
is a cron process using the same process ID like one before, therefore printing 
the old message from Nov, 10. The old message was not at the position inside 
the syslog where it should have been.

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

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

[Touch-packages] [Bug 1392306] Re: Swipe to remove/answer/switch inconsistent

[Matthew Paul Thomas]

(Sorry for the shuffling: Seb just explained to me that the UI controls
indicator-messages uses are provided by unity8.)

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

** No longer affects: unity8 (Ubuntu)

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

** Changed in: address-book-app (Ubuntu)
 Assignee: (unassigned) = Olga Kemmet (olga-kemmet)

** Package changed: indicator-messages (Ubuntu) = unity8 (Ubuntu)

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) = Paty Davila (dizzypaty)

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

Title:
  Swipe to remove/answer/switch inconsistent

Status in Ubuntu UX bugs:
  New
Status in “address-book-app” package in Ubuntu:
  New
Status in “dialer-app” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  New

Bug description:
  Hi guys, I noticed the horizontal swipes in the interface behave in
  different ways meaning different things, I wish we could have common
  positive/negative meanings on the directions they are applied.

  On snap decision calls, a left to right swipe has a positive meaning, answer 
the call.
  On indicator message, a left to right swipe has a negative meaning, remove 
the message.

  I guess the same applies to apps, contact app does left to right with
  a negative meaning, to remove the contact.

  Lock screen can be swiped away any direction, but on the edge demo we
  recommend doing a right to left for removing the lockscreen.

  A right to left edge swipe has a meaning of switching context, like
  swiping it away (maybe negative meaning or we should ignore the case?)

  Can we come up with a consistent behaviour? What you think?

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

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

[Touch-packages] [Bug 1377332] Re: [TOPBLOCKER] UI randomly freezes

[kevin gunn]

marking unity8 as opinion for the moment, since there's a targeted fix
in app-launch

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

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

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

Title:
  [TOPBLOCKER] UI randomly freezes

Status in “cgmanager” package in Ubuntu:
  Incomplete
Status in “ubuntu-app-launch” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  Opinion
Status in “ubuntu-app-launch” package in Ubuntu RTM:
  In Progress
Status in “unity8” package in Ubuntu RTM:
  Opinion

Bug description:
  Summary
  UI randomly freezes

  steps:
  1. unlock greeter
  2. open app
  3. pull down random indicator
  4. close indicator
  5. open app
  6. swipe to view all open apps
  7. open launcher
  8. close some open apps
  9. repeat until ui freezes

  device info:
  [service]
  base: system-image.ubuntu.com
  http_port: 80
  https_port: 443
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  device: krillin
  build_number: 79
  version_detail: 
ubuntu=20141002,device=20141002-d5938d7,custom=1412208099,version=79

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

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

[Touch-packages] [Bug 1330977] Re: 2-finger scrolling with touchpad does not work in qt apps on Qt5.3 when Ubuntu is inside virtual machine

[Timo Jyrinki]

This was reportedly fixed by earlier Qt 5.3.2 testing. Qt 5.3.2 is now
in vivid.

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: Expired = Fix Released

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

Title:
  2-finger scrolling with touchpad does not work in qt apps on Qt5.3
  when Ubuntu is inside virtual machine

Status in “qtbase-opensource-src” package in Ubuntu:
  Fix Released

Bug description:
  I installed Qt 5.3 as explained here https://launchpad.net/~canonical-
  qt5-edgers/+archive/qt5-beta2

  After that, 2-finger scrolling on my touchpad does not work in QML
  apps or QtCreator. It does work in chrome, firefox, terminal.

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

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

[Touch-packages] [Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[Oliver Grawert]

adding an android-tools task, since adb reboot forces a hard reset
without unmounting the filesystems ... adding something along:

ogra_ root@ubuntu-phablet:~# echo u  /proc/sysrq-trigger
ogra_ root@ubuntu-phablet:~# touch /userdata/foo
ogra_ touch: cannot touch ‘/userdata/foo’: Read-only file system

to core/adbd/services.c in the reboot_service function (instead of the
vdc call) should help here

** Also affects: android-tools (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: android-tools (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Changed in: android-tools (Ubuntu)
   Status: New = In Progress

** Changed in: android-tools (Ubuntu RTM)
   Status: New = In Progress

** Changed in: android-tools (Ubuntu)
   Importance: Undecided = Critical

** Changed in: android-tools (Ubuntu RTM)
   Importance: Undecided = Critical

** Changed in: android-tools (Ubuntu)
 Assignee: (unassigned) = Oliver Grawert (ogra)

** Changed in: android-tools (Ubuntu RTM)
 Assignee: (unassigned) = Oliver Grawert (ogra)

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

Title:
  [TOPBLOCKER] file corruption on touch images in rw portions of the
  filesystem

Status in “android” package in Ubuntu:
  In Progress
Status in “android-tools” package in Ubuntu:
  In Progress
Status in “initramfs-tools-ubuntu-touch” package in Ubuntu:
  Fix Released
Status in “android” package in Ubuntu RTM:
  New
Status in “android-tools” package in Ubuntu RTM:
  In Progress
Status in “initramfs-tools-ubuntu-touch” package in Ubuntu RTM:
  New

Bug description:
  Symptoms are that cache files in /var/cache/apparmor and profiles in
  /var/lib/apparmor/profiles are sometimes corrupted after a reboot.
  We've already fixed several bugs in the apparmor and click-apparmor
  and made both more robust in the face of corruption and we've reduced
  the impact when there is a corrupted profile, but we've still not
  found the cause of the corruption. This corruption can still affect
  real-world devices: if a profile in /var/lib/apparmor/profiles is
  corrupted and the cache file is out of date, then the profile won't
  compile and that app/scope won't start.

  Workaround: remove the affected profile and then run 'sudo aa-
  clickhook'. This obviously is not viable on an end-user device.

  The investigation is ongoing and this may not be a problem with the
  kernel at all, so this bug may be retargeted to another project.

  The security team and the kernel team have discussed this a lot and
  Colin King is currently looking at this. This bug is just so it can be
  tracked. Here is an excerpt from my latest email to Colin:

  I believe I have conclusively ruled out apparmor_parser and aa-
  clickhook by creating a new 'home/bug/test-with-true.sh'. Here is the
  test output:

  http://paste.ubuntu.com/8648109/

  Specifically, home/bug/test-with-true.sh changes the interesting parts
  of the algorithm to:

  1. wait for unity8 to start (this ensures the apparmor upstart job is 
finished)
  2. restore apparmor_parser and aa-clickhook, if needed
  3. if /home/bug/profiles... exists, perform a diff -Naur /home/bug/profiles...
     /var/lib/apparmor/profiles and fail if differences (note, apparmor_parser
     and aa-clickhook were /bin/true during boot so they could not have changed
     /var/lib/apparmor/profiles)
  4. verify the profiles, exit with error if they do not
  5. alternately upgrade/downgrade the packages
  6. verify the profiles, exit with error if they do not
  7. copy the known good profiles in the previous step to /home/bug/profiles...
  8. have apparmor_parser and aa-clickhook point to /bin/true
  9. reboot
  10. go to step 1

  In the paste you'll notice that in step 6 the profiles were
  successfully created by the installation of the packages, then
  verified, then copied aside, then apparmor_parser and aa-clickhook
  diverted, then rebooted, only to have the profiles in
  /var/lib/apparmor/profiles be different than what was copied aside. It
  would be nice to verify on your device as well (I reproduced several
  times here) and verify the reproducer algorithm. I think this suggests
  this is a kernel issue and not userspace.

  IMPORTANT: you will want to update the reproducer and refollow all of these 
steps (ie, I updated the scripts, the debs, the sudoers file, etc):
  $ wget http://people.canonical.com/~jamie/cking/aa-corruption.tar.gz
  $ tar -zxvf ./aa-corruption.tar.gz
  ...

  $ adb push ./aa-corruption.tar.gz /tmp
  $ adb shell
  phablet@ubuntu-phablet:~$ cd /tmp
  phablet@ubuntu-phablet:~$ tar -zxvf ./aa-corruption.tar.gz
  phablet@ubuntu-phablet:~$ sudo mount -o remount,rw /
  phablet@ubuntu-phablet:~$ sudo cp ./aa-corruption/etc/sudoers.d/phablet
  /etc/sudoers.d/
  phablet@ubuntu-phablet:~$ sudo mount -o remount,ro /
  

[Touch-packages] [Bug 1391354] Re: Failure to boot ephemeral image for Utopic Fast Installer deployment: no ID_PATH for iSCSI device any more

[Martin Pitt]

This is fixed by
http://cgit.freedesktop.org/systemd/systemd/commit/?id=cc821d02a37c8c76.
I'll prepare an SRU.

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

** Changed in: systemd (Ubuntu Utopic)
 Assignee: Martin Pitt (pitti) = (unassigned)

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

Title:
  Failure to boot ephemeral image for Utopic Fast Installer deployment:
  no ID_PATH for iSCSI device any more

Status in MAAS:
  Incomplete
Status in “systemd” package in Ubuntu:
  Fix Released
Status in “systemd” source package in Utopic:
  In Progress

Bug description:
  I am running into issues with the latest Utopic daily ephemeral images
  for Utopic:

Release ArchitectureSizeNodes deployed  Last update
14.10   i386391.2 MB0   Tue Nov 11 00:36:04 2014
14.10   amd64   395.6 MB0   Tue Nov 11 00:36:04 2014
14.10   ppc64el 425.8 MB1   Tue Nov 11 00:36:03 2014
14.04 LTS   i386373.3 MB0   Tue Nov 11 00:36:04 2014
14.04 LTS   ppc64el 408.5 MB1   Tue Nov 11 00:36:04 2014
14.04 LTS   amd64   380.5 MB52  Tue Nov 11 00:36:03 2014
12.04 LTS   amd64   517.5 MB245 Tue Nov 11 00:36:05 2014
12.04 LTS   i386487.3 MB0   Tue Nov 11 00:36:05 2014

  I have tried installing 2 physical servers, moline and premier as well
  as a ppc64el VM, huffman-vm10, and I get the same failure for each.

  

  iscsistart: Logging into 
iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-ppc64el-generic-utopic-daily 
10.245.0.10:3260,1
  iscsistart: can not connect to iSCSI daemon (111)!
  iscsistart: version 2.0-873
  [   17.810223] sd 1:0:0:1: [sdb] Write Protect is on
  [   17.811504] sd 1:0:0:1: [sdb] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
  [   17.828817]  sdb: unknown partition table
  [   17.839360] sd 1:0:0:1: [sdb] Attached SCSI disk
  iscsistart: initiator reported error (15 - session exists)
  done.
  [   35.868265] random: nonblocking pool is initialized
  Begin: Loading essential drivers ... done.
  Begin: Running /scripts/init-premount ... done.
  Begin: Mounting root file system ... Begin: Running /scripts/local-top ... 
IP-Config: eth0 hardware address 52:54:00:95:6b:54 mtu 1500 DHCP RARP
  IP-Config: no response after 2 secs - giving up
  IP-Config: eth0 hardware address 52:54:00:95:6b:54 mtu 1500 DHCP RARP
  hostname huffman-vm-10 hostname huffman-vm-10 IP-Config: eth0 complete (dhcp 
from 10.245.0.10):
   address: 10.245.0.173 broadcast: 10.245.63.255netmask: 255.255.192.0 
  
   gateway: 10.245.0.1   dns0 : 10.245.0.10  dns1   : 0.0.0.0   
  
   domain : oil 
   rootserver: 10.245.0.10 rootpath: 
   filename  : pxelinux.0
  iscsistart: Logging into 
iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-ppc64el-generic-utopic-daily 
10.245.0.10:3260,1
  iscsistart: version 2.0-873
  iscsistart: Connection1:0 to [target: 
iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-ppc64el-generic-utopic-daily, 
portal: 10.245.0.10,3260] through [iface: default] is operational now
  iscsistart: Logging into 
iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-ppc64el-generic-utopic-daily 
10.245.0.10:3260,1
  iscsistart: can not connect to iSCSI daemon (111)!
  iscsistart: version 2.0-873
  iscsistart: initiator reported error (15 - session exists)
  done.
  Gave up waiting for root device.  Common problems:
   - Boot args (cat /proc/cmdline)
 - Check rootdelay= (did the system wait long enough?)
 - Check root= (did the system wait for the right device?)
   - Missing modules (cat /proc/modules; ls /dev)
  ALERT!  
/dev/disk/by-path/ip-10.245.0.10:3260-iscsi-iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-ppc64el-generic-utopic-daily-lun-1
 does not exist.  Dropping to a shell!
  [   78.856173] hidraw: raw HID events driver (C) Jiri Kosina
  [   78.860069] usbcore: registered new interface driver usbhid
  [   78.860272] usbhid: USB HID core driver

  
  BusyBox v1.22.1 (Ubuntu 1:1.22.0-8ubuntu1) built-in shell (ash)
  Enter 'help' for a list of built-in commands.

  (initramfs)

  
  

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

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

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

[John Muir]

Such enlightening and helpful comments could only come from someone used
to Microsoft software ;-)

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

Title:
  launcher does not show minimized update manager while clicked

Status in Unity:
  Fix Released
Status in Unity 5.0 series:
  Fix Released
Status in Unity 6.0 series:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released
Status in “update-manager” package in Ubuntu:
  Confirmed
Status in “unity” source package in Precise:
  Fix Released
Status in “update-manager” source package in Precise:
  Confirmed
Status in “unity” source package in Quantal:
  Fix Released
Status in “update-manager” source package in Quantal:
  Confirmed

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

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

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

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

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

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

[Touch-packages] [Bug 1392306] Re: Swipe to remove/answer/switch inconsistent

[Michał Sawicz]

I added tasks for ubuntu-settings-components and UITK, as to standardize
most of this we should get as high upstream as possible.

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

** Also affects: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Swipe to remove/answer/switch inconsistent

Status in Ubuntu UX bugs:
  New
Status in “address-book-app” package in Ubuntu:
  New
Status in “dialer-app” package in Ubuntu:
  New
Status in “ubuntu-settings-components” package in Ubuntu:
  New
Status in “ubuntu-ui-toolkit” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  New

Bug description:
  Hi guys, I noticed the horizontal swipes in the interface behave in
  different ways meaning different things, I wish we could have common
  positive/negative meanings on the directions they are applied.

  On snap decision calls, a left to right swipe has a positive meaning, answer 
the call.
  On indicator message, a left to right swipe has a negative meaning, remove 
the message.

  I guess the same applies to apps, contact app does left to right with
  a negative meaning, to remove the contact.

  Lock screen can be swiped away any direction, but on the edge demo we
  recommend doing a right to left for removing the lockscreen.

  A right to left edge swipe has a meaning of switching context, like
  swiping it away (maybe negative meaning or we should ignore the case?)

  Can we come up with a consistent behaviour? What you think?

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

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

[Touch-packages] [Bug 1391498] Re: [TOPBLOCKER] [Dash] In the app scope, replace the Ubuntu icon in the header with the word Apps

[Alejandro J. Cura]

** Tags removed: touch-2014-11-13
** Tags added: touch-2014-11-20

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

Title:
  [TOPBLOCKER] [Dash] In the app scope, replace the Ubuntu icon in the
  header with the word Apps

Status in Ubuntu UX bugs:
  Fix Committed
Status in “unity-scope-click” package in Ubuntu:
  In Progress
Status in “unity-scope-click” package in Ubuntu RTM:
  In Progress

Bug description:
  [Dash] In the app scope, replace the Ubuntu icon in the header with
  the word Apps

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

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

[Touch-packages] [Bug 1391354] Re: Failure to boot ephemeral image for Utopic Fast Installer deployment: no ID_PATH for iSCSI device any more

[Martin Pitt]

I uploaded 208-8ubuntu8.1 to the utopic SRU review queue. I tested it
with my fake MAAS setup from above. For SRU verification it would be
good if you could test it on a real MAAS setup, just to be sure.

** Changed in: systemd (Ubuntu Utopic)
 Assignee: (unassigned) = Martin Pitt (pitti)

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

Title:
  Failure to boot ephemeral image for Utopic Fast Installer deployment:
  no ID_PATH for iSCSI device any more

Status in MAAS:
  Incomplete
Status in “systemd” package in Ubuntu:
  Fix Released
Status in “systemd” source package in Utopic:
  In Progress

Bug description:
  I am running into issues with the latest Utopic daily ephemeral images
  for Utopic:

Release ArchitectureSizeNodes deployed  Last update
14.10   i386391.2 MB0   Tue Nov 11 00:36:04 2014
14.10   amd64   395.6 MB0   Tue Nov 11 00:36:04 2014
14.10   ppc64el 425.8 MB1   Tue Nov 11 00:36:03 2014
14.04 LTS   i386373.3 MB0   Tue Nov 11 00:36:04 2014
14.04 LTS   ppc64el 408.5 MB1   Tue Nov 11 00:36:04 2014
14.04 LTS   amd64   380.5 MB52  Tue Nov 11 00:36:03 2014
12.04 LTS   amd64   517.5 MB245 Tue Nov 11 00:36:05 2014
12.04 LTS   i386487.3 MB0   Tue Nov 11 00:36:05 2014

  I have tried installing 2 physical servers, moline and premier as well
  as a ppc64el VM, huffman-vm10, and I get the same failure for each.

  

  iscsistart: Logging into 
iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-ppc64el-generic-utopic-daily 
10.245.0.10:3260,1
  iscsistart: can not connect to iSCSI daemon (111)!
  iscsistart: version 2.0-873
  [   17.810223] sd 1:0:0:1: [sdb] Write Protect is on
  [   17.811504] sd 1:0:0:1: [sdb] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
  [   17.828817]  sdb: unknown partition table
  [   17.839360] sd 1:0:0:1: [sdb] Attached SCSI disk
  iscsistart: initiator reported error (15 - session exists)
  done.
  [   35.868265] random: nonblocking pool is initialized
  Begin: Loading essential drivers ... done.
  Begin: Running /scripts/init-premount ... done.
  Begin: Mounting root file system ... Begin: Running /scripts/local-top ... 
IP-Config: eth0 hardware address 52:54:00:95:6b:54 mtu 1500 DHCP RARP
  IP-Config: no response after 2 secs - giving up
  IP-Config: eth0 hardware address 52:54:00:95:6b:54 mtu 1500 DHCP RARP
  hostname huffman-vm-10 hostname huffman-vm-10 IP-Config: eth0 complete (dhcp 
from 10.245.0.10):
   address: 10.245.0.173 broadcast: 10.245.63.255netmask: 255.255.192.0 
  
   gateway: 10.245.0.1   dns0 : 10.245.0.10  dns1   : 0.0.0.0   
  
   domain : oil 
   rootserver: 10.245.0.10 rootpath: 
   filename  : pxelinux.0
  iscsistart: Logging into 
iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-ppc64el-generic-utopic-daily 
10.245.0.10:3260,1
  iscsistart: version 2.0-873
  iscsistart: Connection1:0 to [target: 
iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-ppc64el-generic-utopic-daily, 
portal: 10.245.0.10,3260] through [iface: default] is operational now
  iscsistart: Logging into 
iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-ppc64el-generic-utopic-daily 
10.245.0.10:3260,1
  iscsistart: can not connect to iSCSI daemon (111)!
  iscsistart: version 2.0-873
  iscsistart: initiator reported error (15 - session exists)
  done.
  Gave up waiting for root device.  Common problems:
   - Boot args (cat /proc/cmdline)
 - Check rootdelay= (did the system wait long enough?)
 - Check root= (did the system wait for the right device?)
   - Missing modules (cat /proc/modules; ls /dev)
  ALERT!  
/dev/disk/by-path/ip-10.245.0.10:3260-iscsi-iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-ppc64el-generic-utopic-daily-lun-1
 does not exist.  Dropping to a shell!
  [   78.856173] hidraw: raw HID events driver (C) Jiri Kosina
  [   78.860069] usbcore: registered new interface driver usbhid
  [   78.860272] usbhid: USB HID core driver

  
  BusyBox v1.22.1 (Ubuntu 1:1.22.0-8ubuntu1) built-in shell (ash)
  Enter 'help' for a list of built-in commands.

  (initramfs)

  
  

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

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

[Touch-packages] [Bug 1281580] Re: glib-compile-schemas doesn't compile relocatable schemas

[starbroken]

** Summary changed:

- Glib-compile-schemas utility possible doesn't compibiling right relocatable 
schemas
+ glib-compile-schemas doesn't compile relocatable schemas

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

Title:
  glib-compile-schemas doesn't compile relocatable schemas

Status in “glib2.0” package in Ubuntu:
  Confirmed

Bug description:
  Dear Developers,

  I using Ubuntu 14.04 development release with GNOME Shell 3.10, and because 
my wife using too this system,  I defined with some settings in a 
gschema.override file.
  Everithing is working right, except custom keybindings related settings 
applying.
  I added following lines my gsettings.override file:
  [org.gnome.settings-daemon.plugins.media-keys]
  www='SuperAltw'
  email='Supere'
  custom-keybindings = 
['/org/gnome/settings-daemon/plugins/media-keys/custom-keybinding/custom0']

  
[org.gnome.settings-daemon.plugins.media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0/]
  name = 'Launch Gedit'
  command = 'gedit'
  binding = 'Superg'

  My gsettings.override file I putted the /usr/share/glib-2.0/schemas 
directory. After I added this lines, I ran glib-compile-schemas 
/usr/share/glib2.0/schemas command, not presented any error messages.
  Testing purpose I created a new user, logout, and login the new created 
username. Optimal case the custom keybinding need applying automaticaly, but 
this is not happened, other defined keybindings applied right.
  In gnome-control-center keyboard preference pane, keybindings tab the custom 
shortcuts containing table is empty, containing one row with empty columns.

  If I ran gsettings list-recursively org.gnome.settings-daemon.plugins
  .media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins
  /media-keys/custom-keybindings/custom0/ command, the name, command and
  binding key pairs get empty '' values.

  If I manual ran following commands, the custom keybinding is created right:
  gsettings set 
org.gnome.settings-daemon.plugins.media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0/
 name Launch Gedit
  gsettings set 
org.gnome.settings-daemon.plugins.media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0/
 command gedit
  gsettings set 
org.gnome.settings-daemon.plugins.media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0/
 binding Superg

  I doing anything wrong when I want adding the custom keybindings
  related part my schema file, or glib-compile-schemas utility realy not
  applying this part from the schema file?

  Attila

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libglib2.0-bin 2.39.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic i686
  ApportVersion: 2.13.2-0ubuntu4
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Tue Feb 18 13:58:37 2014
  InstallationDate: Installed on 2013-12-13 (67 days ago)
  InstallationMedia: BeLin 3.02 i386
  SourcePackage: glib2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1281580/+subscriptions

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

[Touch-packages] [Bug 1378938] Re: App switcher can be put in a bad state by grabbing the app before it comes into focus

[Launchpad Bug Tracker]

** Branch linked: lp:~mzanetti/unity8/disable-swipetoclose-while-
schnapping

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

Title:
  App switcher can be put in a bad state by grabbing the app before it
  comes into focus

Status in “unity8” package in Ubuntu:
  In Progress

Bug description:
  It seems it is possible to put the app switcher in an odd 'in-between'
  state through the right combination of taps. To reproduce this, open a
  few apps and:

  1. Swipe from the right to open the app switcher
  2. Tap on an app to focus it and immediately tap on it again and hold down - 
before it comes into focus - don't take your finger off yet
  3. Now swiping up or down will dismiss the app
  4. After that the switcher will be open but all of the previews will appear 
closer to the screen. Tapping the screen won't do anything. Interaction can 
only be restored by swiping from the right again.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity8 8.00+14.10.20141006-0ubuntu1 [origin: Ubuntu RTM]
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu3
  Architecture: armhf
  Date: Wed Oct  8 16:03:25 2014
  InstallationDate: Installed on 2014-10-08 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141008-090632)
  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/1378938/+subscriptions

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

[Touch-packages] [Bug 1378938] Re: App switcher can be put in a bad state by grabbing the app before it comes into focus

[Michael Zanetti]

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

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

Title:
  App switcher can be put in a bad state by grabbing the app before it
  comes into focus

Status in “unity8” package in Ubuntu:
  In Progress

Bug description:
  It seems it is possible to put the app switcher in an odd 'in-between'
  state through the right combination of taps. To reproduce this, open a
  few apps and:

  1. Swipe from the right to open the app switcher
  2. Tap on an app to focus it and immediately tap on it again and hold down - 
before it comes into focus - don't take your finger off yet
  3. Now swiping up or down will dismiss the app
  4. After that the switcher will be open but all of the previews will appear 
closer to the screen. Tapping the screen won't do anything. Interaction can 
only be restored by swiping from the right again.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity8 8.00+14.10.20141006-0ubuntu1 [origin: Ubuntu RTM]
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu3
  Architecture: armhf
  Date: Wed Oct  8 16:03:25 2014
  InstallationDate: Installed on 2014-10-08 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141008-090632)
  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/1378938/+subscriptions

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

[Touch-packages] [Bug 1383870] Re: [phone-app] + [messaging-app] + [address-book-app] list tug actions should collapse after user moves view

[Olga Kemmet]

** Also affects: ubuntu-ui-toolkit
   Importance: Undecided
   Status: New

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

Title:
  [phone-app] + [messaging-app] + [address-book-app] list tug actions
  should collapse after user moves view

Status in Address Book App:
  New
Status in Dialer app for Ubuntu Touch:
  New
Status in Messaging App:
  New
Status in Ubuntu UI Toolkit:
  New
Status in Ubuntu UX bugs:
  Fix Committed
Status in “address-book-app” package in Ubuntu:
  New
Status in “dialer-app” package in Ubuntu:
  New
Status in “messaging-app” package in Ubuntu:
  New

Bug description:
  build r120

  Steps to reproduce:
  1. open phone app
  2. carry out a bottom edge swipe to access your RECENT
  3. swipe any list item to the left or right
  4. now scroll your list view a little bit down or up, make sure the list item 
actions stay in view

  Actual Result: the actions remain on the screen, they only collapse if
  it hides behind the header or bottom of the view

  Expected result: if user starts to scroll the list view while a list item 
shows additional actions, the list item should collapse.
  Users are carrying out a different actions in that case and are likely not 
being interested anymore in the revealed list item actions.

  Same behaviour applies for the messaging app and the address-book-app.

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

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

[Touch-packages] [Bug 1297234] Re: Live session set wrong keyboard layout and time zone

[Bruno Nova]

@ernie, I think the bug you're referring is this one: Bug LP: #1240198

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

Title:
  Live session set wrong keyboard layout and time zone

Status in “console-setup” package in Ubuntu:
  Expired
Status in “ibus” package in Ubuntu:
  Expired
Status in “ubiquity” package in Ubuntu:
  Confirmed
Status in “console-setup” source package in Trusty:
  Invalid
Status in “ibus” source package in Trusty:
  Invalid
Status in “ubiquity” source package in Trusty:
  Invalid

Bug description:
  When I boot the Ubuntu Studio 14.04 beta 2 testing it will start with
  keyboard set to English US and time zone as UTC. Usually I believe
  this would be localized to my Swedish keyboard and CET.

  ubuntu-studio@ubuntu-studio:~$ lsb_release -rd
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04

  ubuntu-studio@ubuntu-studio:~$ apt-cache policy keyboard-configuration
  keyboard-configuration:
Installed: 1.70ubuntu8
Candidate: 1.70ubuntu8

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: keyboard-configuration 1.70ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-19.40-lowlatency 3.13.6
  Uname: Linux 3.13.0-19-lowlatency i686
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: i386
  CasperVersion: 1.339
  CurrentDesktop: XFCE
  Date: Tue Mar 25 11:33:44 2014
  LiveMediaBuild: Ubuntu-Studio 14.04 LTS Trusty Tahr - Beta i386 (20140325)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: console-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1281580] Re: glib-compile-schemas doesn't compile relocatable schemas

[starbroken]

I have the same problem.

All entries in my gschema.override file, that affect relocatable schemas, are 
ignored.
All other entries are applied.

** Description changed:

  Dear Developers,
  
- I using Ubuntu 14.04 development release with GNOME Shell 3.10, and because 
my wife using too this system,  I defined with some settings in a 
gschema.override file.
- Everithing is working right, except custom keybindings related settings 
applying.
- I added following lines my gsettings.override file:
+ I am using the Ubuntu 14.04 development release with the GNOME Shell 3.10 
and, because my wife is using this system as well, I defined some settings in a 
gschema.override file.
+ Everything is working right, except applying settings related to custom 
key-bindings.
+ 
+ I added following lines my gschema.override file:
  [org.gnome.settings-daemon.plugins.media-keys]
  www='SuperAltw'
  email='Supere'
  custom-keybindings = 
['/org/gnome/settings-daemon/plugins/media-keys/custom-keybinding/custom0']
  
  
[org.gnome.settings-daemon.plugins.media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0/]
  name = 'Launch Gedit'
  command = 'gedit'
  binding = 'Superg'
  
- My gsettings.override file I putted the /usr/share/glib-2.0/schemas 
directory. After I added this lines, I ran glib-compile-schemas 
/usr/share/glib2.0/schemas command, not presented any error messages.
- Testing purpose I created a new user, logout, and login the new created 
username. Optimal case the custom keybinding need applying automaticaly, but 
this is not happened, other defined keybindings applied right.
- In gnome-control-center keyboard preference pane, keybindings tab the custom 
shortcuts containing table is empty, containing one row with empty columns.
+ I put my gschema.override file in the '/usr/share/glib-2.0/schemas' 
directory. After I added these lines, I ran 'glib-compile-schemas 
/usr/share/glib2.0/schemas' and no error was reported.
+ For testing purposes I created a new user, logged out, and logged in with the 
new user. In the best case, the custom key-binding were applied automatically, 
but this has not happened. Other defined key-bindings were applied correctly.
+ In the gnome-control-center's key-bindings tab, the table containing  custom 
shortcuts is empty, containing one row with empty columns.
  
- If I ran gsettings list-recursively org.gnome.settings-daemon.plugins
+ Running 'gsettings list-recursively org.gnome.settings-daemon.plugins
  .media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins/media-
- keys/custom-keybindings/custom0/ command, the name, command and binding
- key pairs get empty '' values.
+ keys/custom-keybindings/custom0/' shows, the name, command, and binding
+ key pairs contain empty ('') values.
  
- If I manual ran following commands, the custom keybinding is created right:
+ If I manually run following commands, the custom key-binding is created 
correctly:
  gsettings set 
org.gnome.settings-daemon.plugins.media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0/
 name Launch Gedit
  gsettings set 
org.gnome.settings-daemon.plugins.media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0/
 command gedit
  gsettings set 
org.gnome.settings-daemon.plugins.media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0/
 binding Superg
  
- I doing anything wrong when I want adding the custom keybindings related
- part my schema file, or glib-compile-schemas utility realy not applying
- this part from the schema file?
+ Am I doing anything wrong when I want to add a custom key-bindings in my
+ schema file, or  is 'glib-compile-schemas' really not applying this part
+ from the schema file?
  
  Attila
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libglib2.0-bin 2.39.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic i686
  ApportVersion: 2.13.2-0ubuntu4
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Tue Feb 18 13:58:37 2014
  InstallationDate: Installed on 2013-12-13 (67 days ago)
  InstallationMedia: BeLin 3.02 i386
  SourcePackage: glib2.0
  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 glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1281580

Title:
  glib-compile-schemas doesn't compile relocatable schemas

Status in “glib2.0” package in Ubuntu:
  Confirmed

Bug description:
  Dear Developers,

  I am using the Ubuntu 14.04 development release with the GNOME Shell 3.10 
and, because my wife is using this system as well, I defined some settings in a 
gschema.override file.
  Everything is working right, except applying settings related to custom 
key-bindings.

  I added following lines my 

[Touch-packages] [Bug 1391930] Re: Need a way for applications to ask permission to read/write in pictures/videos folders on SD card

[Jamie Strandboge]

** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
   Importance: High = Wishlist

** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
   Status: Confirmed = Triaged

** Also affects: apparmor-easyprof-ubuntu (Ubuntu Vivid)
   Importance: Wishlist
 Assignee: Jamie Strandboge (jdstrand)
   Status: Triaged

** Also affects: apparmor-easyprof-ubuntu (Ubuntu Utopic)
   Importance: Undecided
   Status: New

** Changed in: apparmor-easyprof-ubuntu (Ubuntu Utopic)
   Status: New = Triaged

** Changed in: apparmor-easyprof-ubuntu (Ubuntu Utopic)
   Importance: Undecided = High

** Changed in: apparmor-easyprof-ubuntu (Ubuntu Utopic)
 Assignee: (unassigned) = Jamie Strandboge (jdstrand)

** Also affects: apparmor-easyprof-ubuntu (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Changed in: apparmor-easyprof-ubuntu (Ubuntu Vivid)
   Importance: Wishlist = High

** Changed in: apparmor-easyprof-ubuntu (Ubuntu RTM)
   Importance: Undecided = Wishlist

** Changed in: apparmor-easyprof-ubuntu (Ubuntu RTM)
 Assignee: (unassigned) = Jamie Strandboge (jdstrand)

** Tags added: application-confinement rtm14

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

Title:
  Need a way for applications to ask permission to read/write in
  pictures/videos folders on SD card

Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
  Triaged
Status in “apparmor-easyprof-ubuntu” source package in Utopic:
  Triaged
Status in “apparmor-easyprof-ubuntu” source package in Vivid:
  Triaged
Status in “apparmor-easyprof-ubuntu” package in Ubuntu RTM:
  New

Bug description:
  The camera and the gallery app today are authorized to read/write in 
/home/$USER/Pictures and /home/$USER/Videos.
  Now they also need to be able to read/write in the similar directories of the 
SD card, for example:
  - /media/phablet/064a-7494/Pictures
  - /media/phablet/064a-7494/Videos

  As a side note, we are using the following API in applications to retrieve 
the path (e.g. /home/phablet/Pictures):
  http://qt-project.org/doc/qt-5/qstandardpaths.html#writableLocation

  To retrieve the similar path on the SD card we are considering using a
  combination of that to guess the directory name (Pictures)
  concatenated with the value of http://doc-snapshot.qt-
  project.org/qt5-5.4/qstorageinfo.html#rootPath

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

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

[Touch-packages] [Bug 1240198] Re: Wrong keyboard layout active after booting into desktop

[Bruno Nova]

To apply the fix (setting use-system-keyboard-layout=true) system-wide:

1. As root, create the file
/usr/share/glib-2.0/schemas/30_ibus.gschema.override with the contents:

[org.freedesktop.ibus.general]
use-system-keyboard-layout=true

2. Then run: sudo glib-compile-schemas /usr/share/glib-2.0/schemas/

This should set the default value of use-system-keyboard-layout to true, which 
should fix the issue.
But I'm not sure if it actually fixes it (dconf is confusing).

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

Title:
  Wrong keyboard layout active after booting into desktop

Status in “ibus” package in Ubuntu:
  Triaged
Status in “indicator-keyboard” package in Ubuntu:
  Triaged

Bug description:
  I upgraded from raring to saucy.

  After booting into the desktop (unity), the english keyboard layout is
  active, although everything on the system is set to be german
  (keyboard layout, language...)

  Switching to a virtual terminal (ctrl+alt+f1) fixes the problem and
  changes the layout to the german layout.

  all the time, the new input settings indicator says the german layout
  is active.

  locale says: 
  LANG=de_DE.UTF-8
  LANGUAGE=de_DE
  LC_CTYPE=de_DE.UTF-8
  LC_NUMERIC=de_DE.UTF-8
  LC_TIME=de_DE.UTF-8
  LC_COLLATE=de_DE.UTF-8
  LC_MONETARY=de_DE.UTF-8
  LC_MESSAGES=de_DE.UTF-8
  LC_PAPER=de_DE.UTF-8
  LC_NAME=de_DE.UTF-8
  LC_ADDRESS=de_DE.UTF-8
  LC_TELEPHONE=de_DE.UTF-8
  LC_MEASUREMENT=de_DE.UTF-8
  LC_IDENTIFICATION=de_DE.UTF-8
  LC_ALL=

  /etc/default/keyboard says:
  # Check /usr/share/doc/keyboard-configuration/README.Debian for
  # documentation on what to do after having modified this file.

  # The following variables describe your keyboard and can have the same
  # values as the XkbModel, XkbLayout, XkbVariant and XkbOptions options
  # in /etc/X11/xorg.conf.

  XKBMODEL=pc105
  XKBLAYOUT=de
  XKBVARIANT=
  XKBOPTIONS=

  # If you don't want to use the XKB layout on the console, you can
  # specify an alternative keymap.  Make sure it will be accessible
  # before /usr is mounted.
  # KMAP=/etc/console-setup/defkeymap.kmap.gz

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-keyboard 0.0.0+13.10.20131010.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 15 20:49:03 2013
  InstallationDate: Installed on 2013-04-26 (171 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: indicator-keyboard
  UpgradeStatus: Upgraded to saucy on 2013-10-13 (2 days ago)

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

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

[Touch-packages] [Bug 1384286] Re: add directory allowing scopes and apps to share data

[Jamie Strandboge]

** Tags removed: ota-1

** Also affects: apparmor-easyprof-ubuntu (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Changed in: apparmor-easyprof-ubuntu (Ubuntu RTM)
   Importance: Undecided = Wishlist

** Changed in: apparmor-easyprof-ubuntu (Ubuntu RTM)
   Status: New = In Progress

** Also affects: apparmor-easyprof-ubuntu (Ubuntu Vivid)
   Importance: High
 Assignee: Jamie Strandboge (jdstrand)
   Status: In Progress

** Also affects: click-reviewers-tools (Ubuntu Vivid)
   Importance: High
 Assignee: Jamie Strandboge (jdstrand)
   Status: In Progress

** Also affects: unity-scopes-api (Ubuntu Vivid)
   Importance: High
 Assignee: Michi Henning (michihenning)
   Status: Fix Committed

** Also affects: apparmor-easyprof-ubuntu (Ubuntu Utopic)
   Importance: Undecided
   Status: New

** Also affects: click-reviewers-tools (Ubuntu Utopic)
   Importance: Undecided
   Status: New

** Also affects: unity-scopes-api (Ubuntu Utopic)
   Importance: Undecided
   Status: New

** Changed in: apparmor-easyprof-ubuntu (Ubuntu Utopic)
   Importance: Undecided = High

** Changed in: apparmor-easyprof-ubuntu (Ubuntu Utopic)
   Status: New = In Progress

** Description changed:

  Summary says it all, just need to decide on the directory. I propose using 
this rule:
    # Allow scopes to share data with the app shipped in the same click
-   owner @{HOME}/.local/share/@{APP_PKGNAME}/rw,
-   owner @{HOME}/.local/share/@{APP_PKGNAME}/**  mrwkl,
+   owner @{HOME}/.local/share/@{APP_PKGNAME}/r,
+   owner @{HOME}/.local/share/@{APP_PKGNAME}/**  mrkl,

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

Title:
  add directory allowing scopes and apps to share data

Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
  In Progress
Status in “click-reviewers-tools” package in Ubuntu:
  In Progress
Status in “unity-scopes-api” package in Ubuntu:
  Fix Committed
Status in “apparmor-easyprof-ubuntu” source package in Utopic:
  In Progress
Status in “click-reviewers-tools” source package in Utopic:
  New
Status in “unity-scopes-api” source package in Utopic:
  New
Status in “apparmor-easyprof-ubuntu” source package in Vivid:
  In Progress
Status in “click-reviewers-tools” source package in Vivid:
  In Progress
Status in “unity-scopes-api” source package in Vivid:
  Fix Committed
Status in “apparmor-easyprof-ubuntu” package in Ubuntu RTM:
  In Progress

Bug description:
  Summary says it all, just need to decide on the directory. I propose using 
this rule:
    # Allow scopes to share data with the app shipped in the same click
    owner @{HOME}/.local/share/@{APP_PKGNAME}/r,
    owner @{HOME}/.local/share/@{APP_PKGNAME}/**  mrkl,

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

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

[Touch-packages] [Bug 1386767] Re: single tap causes many letters

[John McAleely]

just to note that KyleN is using a retail handset.

** Tags added: ota-2 rtm14

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

Title:
  single tap causes many letters

Status in “ubuntu-keyboard” package in Ubuntu:
  New

Bug description:
  Sometimes, a single key press in OSK causes multiple keys to appear.

  It is hard to reproduce, but here is what I just did that caused it:

  * I installed with --wipe brand new rtm krillin image 133.

  * In Welcome Wizard, I selected English as my language and completed
  to normal shell.

  * in System Settings  Languages, I selected Spanish as display
  language, which caused a reboot

  * On reboot, I entered the scopes dashboard (not the dashboard
  scope, but the place where you see Favorites v All and a search field)

  * I tapped the search field, which display the OSK. (Note, the
  keyboard layout is still English.)

  * In OSK, I tapped the globe key to switch layouts and chose Spanish

  Now, I got weird double keys on single presses. Bad enough to be
  unusable.

  However, after switch OSK back to English and back to spanish I don't
  get them, so I wonder whether it has to do with switching the system's
  runtime locale.

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

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

[Touch-packages] [Bug 1392347] [NEW] Pause button changes to Play after low-battery notification when a video is playing

[Brendan Donegan]

Public bug reported:

Steps to reproduce:

1. Open a video in mediaplayer-app
2. Enable the mock battery:

gdbus call --session --dest com.canonical.indicator.power \
 --object-path /com/canonical/indicator/power/Testing \
 --method org.freedesktop.DBus.Properties.Set \
 com.canonical.indicator.power.Testing \
 MockBatteryEnabled \
 true

3. Trigger the low battery notification:

gdbus call --session --dest com.canonical.indicator.power \
 --object-path /com/canonical/indicator/power/Testing \
 --method org.freedesktop.DBus.Properties.Set \
 com.canonical.indicator.power.Testing \
 MockBatteryLevel \
 uint32 10

4. Dismiss the Low battery notification

Expected result:

Video resumes playing and Pause button is available in bottom left
corner

Actual result:

Video resumes playing but Pause button has changed to Play, which is
clearly wrong since the video is playing

ProblemType: Bug
DistroRelease: Ubuntu RTM 14.09
Package: mediaplayer-app 0.20.5+14.10.20141015-0ubuntu1
Uname: Linux 3.4.67 armv7l
ApportVersion: 2.14.7-0ubuntu8
Architecture: armhf
Date: Thu Nov 13 15:01:43 2014
InstallationDate: Installed on 2014-11-12 (0 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141112-181954)
SourcePackage: mediaplayer-app
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Pause button changes to Play after low-battery notification when a
  video is playing

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

Bug description:
  Steps to reproduce:

  1. Open a video in mediaplayer-app
  2. Enable the mock battery:

  gdbus call --session --dest com.canonical.indicator.power \
   --object-path /com/canonical/indicator/power/Testing \
   --method org.freedesktop.DBus.Properties.Set \
   com.canonical.indicator.power.Testing \
   MockBatteryEnabled \
   true

  3. Trigger the low battery notification:

  gdbus call --session --dest com.canonical.indicator.power \
   --object-path /com/canonical/indicator/power/Testing \
   --method org.freedesktop.DBus.Properties.Set \
   com.canonical.indicator.power.Testing \
   MockBatteryLevel \
   uint32 10

  4. Dismiss the Low battery notification

  Expected result:

  Video resumes playing and Pause button is available in bottom left
  corner

  Actual result:

  Video resumes playing but Pause button has changed to Play, which is
  clearly wrong since the video is playing

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: mediaplayer-app 0.20.5+14.10.20141015-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Thu Nov 13 15:01:43 2014
  InstallationDate: Installed on 2014-11-12 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141112-181954)
  SourcePackage: mediaplayer-app
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Burko]

sorry, that is ..leave it as it is. It does even occur

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

Title:
  launcher does not show minimized update manager while clicked

Status in Unity:
  Fix Released
Status in Unity 5.0 series:
  Fix Released
Status in Unity 6.0 series:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released
Status in “update-manager” package in Ubuntu:
  Confirmed
Status in “unity” source package in Precise:
  Fix Released
Status in “update-manager” source package in Precise:
  Confirmed
Status in “unity” source package in Quantal:
  Fix Released
Status in “update-manager” source package in Quantal:
  Confirmed

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

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

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

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

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

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

[Touch-packages] [Bug 1382109] Re: Events view should be shown on import

[Olli Ries]

** Tags added: ota-1

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

Title:
  Events view should be shown on import

Status in Gallery App:
  In Progress
Status in “gallery-app” package in Ubuntu:
  In Progress
Status in “gallery-app” package in Ubuntu RTM:
  In Progress

Bug description:
  If a photo is imported via the content-hub, we should always make sure
  to display the Events view as the photo will show up by default there.

  Currenty if the gallery is open to a specific photo or album, after
  the import occurs we don't update the view so user has no idea where
  the imported picture is.

  Would be nice to directly open the imported picture but this won't
  work as we might get multiple import events in a row from content-hub
  in the case where the user Dimissed the open dialog multiple times.
  Next time gallery-app launched or displayed it will be delivered
  multiple events so we would not know which to open.

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

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

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

[Burko]

I also still experience this Bug in 14.04. It is interesting how
canonical cares about such a severe issue - meaning that they leave it
as it does even occur in a LTS release. I wonder why it is not
confirmed by now for trusty.

And there a reports for it in utopic und some duplicates around. So
whats the problem?

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

Title:
  launcher does not show minimized update manager while clicked

Status in Unity:
  Fix Released
Status in Unity 5.0 series:
  Fix Released
Status in Unity 6.0 series:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released
Status in “update-manager” package in Ubuntu:
  Confirmed
Status in “unity” source package in Precise:
  Fix Released
Status in “update-manager” source package in Precise:
  Confirmed
Status in “unity” source package in Quantal:
  Fix Released
Status in “update-manager” source package in Quantal:
  Confirmed

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

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

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

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

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

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

[Touch-packages] [Bug 1392176] [NEW] Systemd mounts cgroups unconditionally which causes undesired effects with cpu hotplug

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

== Comment: #0 - Preeti U. Murthy preeti.mur...@in.ibm.com - 2014-10-20 
04:40:12 ==
---Problem Description---
Systemd mounts cgroups explicitly every boot. Since the user had no say in it, 
undesired consequences are observed in reaction to cpu hotplug operations.  
Here is how.

Systemd moves the tasks to the cgroup mounted by it. This cgroup automatically 
becomes the child of the root cgroup which is present by default. The children 
cgroups are not expected to remember their configured cpusets after hotplug 
operations in the kernel. Hence when cpus are taken offline and brought back 
online they are no longer used for load balancing of tasks and hence remain 
unused. 
   This is an undesired consequence because the user had not even asked for 
cgroups to be mounted, yet is not able to use the full capacity of the system.

Only when the user himself creates cgroup hierarchies, should he be
exposed to the side effects of cpu hotplug on cpusets. Else all online
cpus must be made available to him which is not happening since systemd
mounts cgroups on every boot.

Hence please revert this feature or provide an explaination as to why this is 
being done.
 
---uname output---
Linux tul181p1 3.16.0-18-generic #25-Ubuntu SMP Fri Sep 26 02:39:53 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux
 
Machine Type = Tuleta 8286-42A 
 ---Debugger---
A debugger was configured, however the system did not enter into the debugger
 
---Steps to Reproduce---
 $ taskset -p $$
$ 0-127
$ echo 0  /sys/devices/system/cpu/cpu7/online
$ taskset -p $$
$ 0-6,8-127
$ echo 1  /sys/devices/system/cpu/cpu7/online
$ taskset -p $$
$ 0-6,8-127
 
 
Userspace tool common name: systemd 
 
The userspace tool has the following bit modes: 64-bit 

Userspace rpm: systemd_208-8ubuntu8_ppc64el.deb

Userspace tool obtained from project website:   208-8ubuntu8

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


** Tags: architecture-ppc64le bot-comment bugnameltc-117800 severity-medium 
targetmilestone-inin---
-- 
Systemd mounts cgroups unconditionally which causes undesired effects with cpu 
hotplug
https://bugs.launchpad.net/bugs/1392176
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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

[Touch-packages] [Bug 1389514] Re: open photo from scope fails on first try

[Olli Ries]

** Tags removed: ota-1
** Tags added: touch-2014-11-20

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

Title:
  open photo from scope fails on first try

Status in Gallery App:
  In Progress
Status in “gallery-app” package in Ubuntu:
  In Progress
Status in “gallery-app” package in Ubuntu RTM:
  New

Bug description:
  The Photos scope and gallery app support a mechanism where a photo can
  be opened directly in the gallery by tapping 'open' on it in the
  photos scope.  However, this appears to fail on the first try if
  Gallery hasn't been run before.

  Steps to reproduce this:
  1. Flash the phone to get a fresh install.
  2. Take some photos in the camera app.
  3. Navigate to those photos in the Photos scope.
  4. Select a photo and tap 'open'.

  Expected results: Selected photo opens in the gallery app.

  Actual results: Gallery app opens and shows the 'Events' view, but does not 
open the chosen photo.
  On second attempt, the expected results happen.

  I suspect that the gallery app may be getting stuck on indexing and
  thumbnailing the first time, and once that is done things work as
  expected.

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

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

[Touch-packages] [Bug 1386767] Re: single tap causes many letters sometimes

[John McAleely]

** Summary changed:

- single tap causes many letters
+ single tap causes many letters sometimes

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

Title:
  single tap causes many letters sometimes

Status in “ubuntu-keyboard” package in Ubuntu:
  New

Bug description:
  Sometimes, a single key press in OSK causes multiple keys to appear.

  It is hard to reproduce, but here is what I just did that caused it:

  * I installed with --wipe brand new rtm krillin image 133.

  * In Welcome Wizard, I selected English as my language and completed
  to normal shell.

  * in System Settings  Languages, I selected Spanish as display
  language, which caused a reboot

  * On reboot, I entered the scopes dashboard (not the dashboard
  scope, but the place where you see Favorites v All and a search field)

  * I tapped the search field, which display the OSK. (Note, the
  keyboard layout is still English.)

  * In OSK, I tapped the globe key to switch layouts and chose Spanish

  Now, I got weird double keys on single presses. Bad enough to be
  unusable.

  However, after switch OSK back to English and back to spanish I don't
  get them, so I wonder whether it has to do with switching the system's
  runtime locale.

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

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

[Touch-packages] [Bug 1392176] Re: Systemd mounts cgroups unconditionally which causes undesired effects with cpu hotplug

[Brian Murray]

** Package changed: ubuntu = systemd (Ubuntu)

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

Title:
  Systemd mounts cgroups unconditionally which causes undesired effects
  with cpu hotplug

Status in “systemd” package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Preeti U. Murthy preeti.mur...@in.ibm.com - 2014-10-20 
04:40:12 ==
  ---Problem Description---
  Systemd mounts cgroups explicitly every boot. Since the user had no say in 
it, undesired consequences are observed in reaction to cpu hotplug operations.  
Here is how.

  Systemd moves the tasks to the cgroup mounted by it. This cgroup 
automatically becomes the child of the root cgroup which is present by default. 
The children cgroups are not expected to remember their configured cpusets 
after hotplug operations in the kernel. Hence when cpus are taken offline and 
brought back online they are no longer used for load balancing of tasks and 
hence remain unused. 
 This is an undesired consequence because the user had not even asked for 
cgroups to be mounted, yet is not able to use the full capacity of the system.

  Only when the user himself creates cgroup hierarchies, should he be
  exposed to the side effects of cpu hotplug on cpusets. Else all online
  cpus must be made available to him which is not happening since
  systemd mounts cgroups on every boot.

  Hence please revert this feature or provide an explaination as to why this is 
being done.
   
  ---uname output---
  Linux tul181p1 3.16.0-18-generic #25-Ubuntu SMP Fri Sep 26 02:39:53 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = Tuleta 8286-42A 
   ---Debugger---
  A debugger was configured, however the system did not enter into the debugger
   
  ---Steps to Reproduce---
   $ taskset -p $$
  $ 0-127
  $ echo 0  /sys/devices/system/cpu/cpu7/online
  $ taskset -p $$
  $ 0-6,8-127
  $ echo 1  /sys/devices/system/cpu/cpu7/online
  $ taskset -p $$
  $ 0-6,8-127
   
   
  Userspace tool common name: systemd 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: systemd_208-8ubuntu8_ppc64el.deb

  Userspace tool obtained from project website:   208-8ubuntu8

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

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

[Touch-packages] [Bug 1386721] Re: Graphics Slow After Upgrade 14.04 - 14.10

[Alain A Servais]

Affects me too.

Fresh install of Ubuntu 14.10 on brand new desktop computer with Intel
integrated graphics. Launching directly gedit as only graphical
application after boot, display freezes for a noticeable period of time
(10-20 seconds) when editing with a mix of keyboard entry, keyboard
shortcuts and mouse edition.

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

Title:
  Graphics Slow After Upgrade 14.04 - 14.10

Status in “xorg” package in Ubuntu:
  Confirmed

Bug description:
  Using Gnome Ubuntu 14.10, Dell XPS 13, intel 915 Graphics

  After upgrading from 14.04 to 14.10 there are a lot of places where
  the graphics are working much slower than they were before:

  - Gnome Shell Interface is very sluggish, visible chops (redrawing)
  when pressing the [Super] key.

  - Selecting text in Gedit takes a full second pr. line

  Experiences some subjective improvement when I booted kernel 3.13.0-37
  instead of 3.16.0-23, but that may be my imagination as the problem
  persists.

  I've searched google, forums, found a couple of relevant links that
  point to the issue being the Intel drivers.

  http://askubuntu.com/questions/53962...E2%86%92-14-10
  http://www.webupd8.org/2014/10/ubunt...ent-1652086424

  But the drivers currently in 14.10 should be newer than those supplied
  by Intel to 14.04 so that doesn't make sense to me. As one Intel
  developer wrote:

  I would like to point out that since what we do is bring more ecent
  versions of the software to the target distributions than they ship
  with, a 14.04 targeted installer is unlikely to bring much to a 14.10
  installation, which most likely has the same or more recent versions
  already anyway.

  Source: https://01.org/linuxgraphics/node/375

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue Oct 28 15:24:30 2014
  DistUpgraded: 2014-10-25 20:59:36,052 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus: i915-3.15-3.13, 0.01, 3.13.0-37-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:060a]
  InstallationDate: Installed on 2014-06-14 (135 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
  MachineType: Dell Inc. XPS13 9333
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic 
root=UUID=105bbbd1-365e-4063-bdca-fc5431faf5dc ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to utopic on 2014-10-25 (2 days ago)
  dmi.bios.date: 12/11/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0GFTRT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Tue Oct 28 13:44:57 2014
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4933
   vendor CMN
  xserver.version: 2:1.16.0-1ubuntu1

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

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

[Touch-packages] [Bug 1277311] Re: can't open URL in text viewed in the message indicator

[kevin gunn]

still happens

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

Title:
  can't open URL in text viewed in the message indicator

Status in “ubuntu-settings-components” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  New

Bug description:
  I received a text with a URL in it. In the messaging app, it is blue
  and I am able to tap it to open the browser, but in viewing the same
  message in the message indicator I am not.

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

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

[Touch-packages] [Bug 1350891] Re: [Dash] [design] Suru Background should scroll

[kevin gunn]

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

** Changed in: unity8 (Ubuntu)
 Assignee: Ying-Chun Liu (paulliu) = (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/1350891

Title:
  [Dash] [design] Suru Background should scroll

Status in Clock application for Ubuntu devices:
  Triaged
Status in Ubuntu UX bugs:
  Triaged
Status in “unity8” package in Ubuntu:
  Triaged

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

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

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

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

[Touch-packages] [Bug 798023] Re: apt-get update fails with error 416 Requested Range Not Satisfiable

[EOLE team]

Hello,

Any news on this issue, we are facing it on Precise Pangolin some times.

Regards.

** Tags added: precise

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

Title:
  apt-get update fails with error 416  Requested Range Not Satisfiable

Status in “apt” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: apt

  Err http://de.archive.ubuntu.com maverick-updates/main i386 Packages
416  Requested Range Not Satisfiable [IP: 141.30.13.30 80]
  Fetched 5,079B in 2s (2,296B/s)
  W: Failed to fetch 
http://de.archive.ubuntu.com/ubuntu/dists/maverick-updates/main/binary-i386/Packages.gz
  416  Requested Range Not Satisfiable [IP: 141.30.13.30 80]

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

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: apt 0.8.3ubuntu7.1
  ProcVersionSignature: Ubuntu 2.6.35-28.50-generic 2.6.35.11
  Uname: Linux 2.6.35-28-generic i686
  Architecture: i386
  Date: Thu Jun 16 07:56:13 2011
  ExecutablePath: /usr/bin/apt-get
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: apt

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

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

[Touch-packages] [Bug 1278872] Re: N10 Scrolling is jerky/laggy

[kevin gunn]

** Summary changed:

- Scrolling is jerky/laggy
+ N10 Scrolling is jerky/laggy

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

Title:
  N10 Scrolling is jerky/laggy

Status in “unity8” package in Ubuntu:
  New

Bug description:
  On the N10, scrolling (especially in unity) is very laggy, and is not
  smooth

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity8 (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Feb 11 08:38:56 2014
  InstallationDate: Installed on 2013-07-26 (199 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to trusty on 2013-11-21 (81 days ago)

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

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

[Touch-packages] [Bug 1236203] Re: [greeter] [indicators] Design requests that the clock is shown in 24 hour mode by default (i.e. they don't want to see the AM/PM part)

[Launchpad Bug Tracker]

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

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

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

Title:
  [greeter] [indicators] Design requests that the clock is shown in 24
  hour mode by default (i.e. they don't want to see the AM/PM part)

Status in Ubuntu UX bugs:
  Fix Committed
Status in “unity8” package in Ubuntu:
  Triaged

Bug description:
  As per the subject.

  
  DESIRED RESOLUTION:
  AM/PM should never be shown, irrespective of twelve or 24h clock.

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

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

[Touch-packages] [Bug 1169615] Re: [greeter] [design] Welcome screen AM/PM text is unnecessary big

[kevin gunn]

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

actually seems redundant due to bug 1236203

** Summary changed:

- [greeter] Welcome screen AM/PM text is unnecessary big
+ [greeter] [design] Welcome screen AM/PM text is unnecessary big

** This bug has been marked a duplicate of bug 1236203
   [greeter] [indicators] Design requests that the clock is shown in 24 hour 
mode by default (i.e. they don't want to see the AM/PM part)

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

Title:
  [greeter] [design] Welcome screen AM/PM text is unnecessary big

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

Bug description:
  AM or PM text in greeter time is as big as the actual time. That's why
  it looks unbalanced.

  At least the text size for AM should be smaller that for the rest of
  the text. One option would also be superscripting it. It needs a bit
  experimentation what looks good.

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

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

[Touch-packages] [Bug 1236203] Re: [greeter] [indicators] Design requests that the clock is shown in 24 hour mode by default (i.e. they don't want to see the AM/PM part)

[kevin gunn]

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

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

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

Title:
  [greeter] [indicators] Design requests that the clock is shown in 24
  hour mode by default (i.e. they don't want to see the AM/PM part)

Status in Ubuntu UX bugs:
  Fix Committed
Status in “unity8” package in Ubuntu:
  Triaged

Bug description:
  As per the subject.

  
  DESIRED RESOLUTION:
  AM/PM should never be shown, irrespective of twelve or 24h clock.

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

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

[Touch-packages] [Bug 1387708] Re: [TOPBLOCKER] Location services not getting location

[Pat McGowan]

** Changed in: location-service
   Status: New = Fix Released

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

Title:
  [TOPBLOCKER] Location services not getting location

Status in Location Service:
  Fix Released
Status in “location-service” package in Ubuntu:
  Fix Released
Status in “location-service” package in Ubuntu RTM:
  Fix Released
Status in “location-service” source package in 14.09:
  Fix Released

Bug description:
  Failing to get location fix from application.
  Neither network based nor gps location works.
  Bug has now been seen on 3 phones with and without SIM installed.
  HERE service seems to be running, but no reasonable location is reported.
  GPS is failing to get fix, tested with phone placed for 2 hours outside.

  On two of those phones location was working fine, but with OTA update to ~135 
stopped working.
  hard to guess working image but somewhere around 129~131

  
  Problem is now reproducible on RTM release 137

To manage notifications about this bug go to:
https://bugs.launchpad.net/location-service/+bug/1387708/+subscriptions

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

[Touch-packages] [Bug 1392306] Re: Swipe to remove/answer/switch inconsistent

[Andrea Cimitan]

** Changed in: ubuntu-settings-components (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 dialer-app in Ubuntu.
https://bugs.launchpad.net/bugs/1392306

Title:
  Swipe to remove/answer/switch inconsistent

Status in Ubuntu UX bugs:
  New
Status in “address-book-app” package in Ubuntu:
  New
Status in “dialer-app” package in Ubuntu:
  New
Status in “ubuntu-settings-components” package in Ubuntu:
  New
Status in “ubuntu-ui-toolkit” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  New

Bug description:
  Hi guys, I noticed the horizontal swipes in the interface behave in
  different ways meaning different things, I wish we could have common
  positive/negative meanings on the directions they are applied.

  On snap decision calls, a left to right swipe has a positive meaning, answer 
the call.
  On indicator message, a left to right swipe has a negative meaning, remove 
the message.

  I guess the same applies to apps, contact app does left to right with
  a negative meaning, to remove the contact.

  Lock screen can be swiped away any direction, but on the edge demo we
  recommend doing a right to left for removing the lockscreen.

  A right to left edge swipe has a meaning of switching context, like
  swiping it away (maybe negative meaning or we should ignore the case?)

  Can we come up with a consistent behaviour? What you think?

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

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

[Touch-packages] [Bug 1388976] Re: [Time Date] After switching from Manual time setting back to Automatic, the clock does not update until rebooted

[Brendan Donegan]

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

** This bug has been marked a duplicate of bug 1392292
   Clock doesn't update when switching time from manual to automatic

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

Title:
  [Time  Date] After switching from Manual time setting back to
  Automatic, the clock does not update until rebooted

Status in “indicator-datetime” package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Open System Settings
  2. Open the Time  Date panel
  3. Set 'Set the time and date:' to 'Manually'
  4. Tap on the date and time label and set the date and time to something in 
the future (a few months ahead)
  5. Go back and wait for the time indicator to update
  6. Set 'Set the time and date:' to Automatically
  7. Go back and wait for the time indicator to update again

  Expected result:

  The indicator reverts back to the previous time

  Actual result:

  The indicator never updates the time until the device is rebooted

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: indicator-datetime 13.10.0+14.10.20141009-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Fri Dec  5 21:21:42 2014
  InstallationDate: Installed on 2014-10-31 (35 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141031-175022)
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1392292] Re: Clock doesn't update when switching time from manual to automatic

[Launchpad Bug Tracker]

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

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

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

Title:
  Clock doesn't update when switching time from manual to automatic

Status in “systemd” package in Ubuntu:
  Confirmed

Bug description:
  TEST CASE:
  1. Go to system-settings/datetime and switch the phone to manual date/time 
update and set a date/time different from your current time
  2. Switch back to automatic
  3. Wait until clock updates to the right date/time

  EXPECTED RESULT
  The clock of the device is updated when settings is switched to automatic

  ACTUAL RESULT
  The clock of the device doesn't update unless flight mode it toggle on/off

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: ubuntu-system-settings 0.3+14.10.20141104~rtm-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Thu Nov 13 11:51:22 2014
  InstallationDate: Installed on 2014-11-12 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141112-181954)
  SourcePackage: ubuntu-system-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1236203] Re: [greeter] [indicators] Design requests that the clock is shown in 24 hour mode by default (i.e. they don't want to see the AM/PM part)

[Pat McGowan]

Comment #2 contradicts the original description
Its not a good idea IMHO to default to 24 hr format

Also system settings date time explicitly does NOT include a switch for
12 vs 24 and specifies 12 is the default

Can we clarify the fix?

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

Title:
  [greeter] [indicators] Design requests that the clock is shown in 24
  hour mode by default (i.e. they don't want to see the AM/PM part)

Status in Ubuntu UX bugs:
  Fix Committed
Status in “unity8” package in Ubuntu:
  Triaged

Bug description:
  As per the subject.

  
  DESIRED RESOLUTION:
  AM/PM should never be shown, irrespective of twelve or 24h clock.

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

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

[Touch-packages] [Bug 794311] Re: No sound on IEC958 (S/PDIF) output after switching user

[Rolf Leggewie]

We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on the current status, under the Status column, and change
the Status back to New. Thanks again!

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

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

Title:
  No sound on IEC958 (S/PDIF) output after switching user

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

Bug description:
  I have found a (sometimes) reproducible path to render the digital
  output of my soundcard useless, until reboot.

  1. Log in as user A
  2. Select Digital Stereo (IEC958) Output + Analogue Stereo Input in the 
Sound Preferences for the sound card.
  3. Play some audio, this works fine over the digital output.
  4. Log out and log in as user B with the preference of Analog Stereo Duplex
  5. Play some audio, this works fine over the analogue output.
  6. Log out and log back in as user A.
  7. Try to play some audio over the still selected digital output. This 
doesn't work. Pulseaudio seems to be unable to open the right Alsa resources 
(see my pulseaudio debug log attached - see the remarks below).
  8. Selecting other output methods won't help, restarting Pulseaudio doesn't 
make a difference.

  Notes:
  - Other paths may be valid too, I experience it also when switching between 
audio applications.
  - All information for this bug report was gathered after step 8.
  - I've disabled all sound for GDM (see below).

  This seems to be reproducible for about 50% of the times and also
  occurs sometimes when GDM is using the analogue output on the login
  screen, then switching to digital output after logging in. After I
  disabled the sounds for the GDM greeter, it saved me a lot of reboots
  to get sound even right after a cold boot.

  Of course, I've checked all alsa mixers (alsamixer from terminal).
  Also I've tried the natty-proposed kernels -9 and -10 as well as the
  stock -8.

  The Alsa driver seems to be locked up somewhere. A reboot of my machine 
always resolves the lock up and everything works fine again.
  From the Pulse verbose log I see the following interesting line a lot of 
times appearing:
  I: (alsa-lib)pcm_hw.c: open '/dev/snd/pcmC1D0p' failed (-2)
  I: alsa-util.c: Failed to set hardware parameters on plug:iec958:1: Invalid 
argument
  I: alsa-util.c: Failed to set hardware parameters on plug:hw:0: Invalid 
argument
  During the capture of this log, I was trying to get sound on my digital 
output, but I failed. I got sound after I switched to analogue output. My A/V 
receiver which is connected to my notebook didn't respond at all, not even a 
type of signal (PCM, AC-3, etc.) was displayed.

  This particular issue has never occured to me on Ubuntu versions 8.04,
  8.10, 9.04, 9.10 and 10.10. The hardware: a Thinkpad T61p notebook
  with an Intel HDA onboard soundcard.

  Please let me know on how to debug this issue better.

  Other output:

  $ iecset 
  Mode: consumer
  Data: audio
  Rate: 48000 Hz
  Copyright: permitted
  Emphasis: none
  Category: PCM coder
  Original: original
  Clock: 1000 ppm

  Disabling pulseaudio, then
  $ aplay -D plug:iec958 /usr/share/sounds/alsa/Front_Center.wav
  gives nothing, should be digital output.
  $ aplay -D plug:front /usr/share/sounds/alsa/Front_Center.wav
  works, analogue output.

  $ aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: Intel [HDA Intel], device 1: AD198x Digital [AD198x Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0

  $ getent group | grep audio
  audio:x:29:pulse

  No users have any specific alsa configuration, nor is there any
  /etc/asound.conf file present.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: alsa-base 1.0.24+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-10.44-generic 2.6.38.7
  Uname: Linux 2.6.38-10-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gert  20527 F alsamixer
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfe22 irq 49'
 Mixer name : 'Analog Devices AD1984'
 Components : 'HDA:11d41984,17aa20bb,00100400'
 Controls  : 31
 Simple ctrls  : 19
  Card1.Amixer.info:
   Card hw:1 'Camera'/'Camera at usb-:00:1a.1-1, full speed'
 Mixer name : 'USB Mixer'
 Components : 'USB046d:08f5'
 Controls  : 3
 Simple ctrls  : 2
  

[Touch-packages] [Bug 659200] Re: No headphone sound after upgrading from 10.04 to 10.10

[Rolf Leggewie]

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

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

Title:
  No headphone sound after upgrading from 10.04 to 10.10

Status in “alsa-driver” package in Ubuntu:
  Fix Released

Bug description:
  After upgrading from Ubuntu 10.04 from to 10.10 I've lost sound in my
  headphones output. I'm using a 64-bit Thinkpad T400s. Sound from
  internal speakers works fine, but when plugging in headphones I get no
  sound at all. I've gone through the steps in
  https://help.ubuntu.com/community/SoundTroubleshootingProcedure, but
  to no avail. The output of Steps 3 and 4 are included in the attached
  file.

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

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

[Touch-packages] [Bug 573493] Re: No sound from headphone jack

[Rolf Leggewie]

OK, that's unfortunate.  Thanks for reporting and getting back to me.

I'll do the housekeeping and close this ticket as unreproducible then

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

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

Title:
  No sound from headphone jack

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

Bug description:
  As a follow on from bug #549289;

  No sound from headphone jack but following code fixes the problem:

  /etc/modprobe.conf/alsa-base.conf

  code
  options snd-hda-intel model=olpc-xo-1_5
  /code

  Subsystem ID from my /proc/asound/card0/codec#0 is:

  Codec: Conexant CX20582 (Pebble)
  Address: 0
  Function Id: 0x1
  Vendor Id: 0x14f15066
  Subsystem Id: 0x17aa21b4
  Revision Id: 0x100300

  And my lspci says:

  andrew@fuji:~$ lspci
  ...
  00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio 
Controller (rev 03)
  ...

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

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

[Touch-packages] [Bug 550891] Re: internal speakers do not mute if in dockingstation

[Rolf Leggewie]

We'd like to figure out what's causing this bug for you, but we haven't
heard back from you in a while. Could you please provide the requested
information? Thanks!

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

Title:
  internal speakers do not mute if in dockingstation

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

Bug description:
  Hello,

  I have got a problem with my Thinkpad T400s and the ThinkPad Mini Dock 
Series 3 docking station. 
  Everytime I attach the nookbook to the dock (there are speakers connected) 
the internal speakers do not mute.
  Currently I do just plugin the speakers to the headphone output. But this is 
not what I want to do using a dock. 

  The operating system is Ubuntu Lucid Beta1 with all updates.

  Information about the docking station
  http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-72871

  Further information on the notebook can be found here:
  http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-72868

  In other Bugs I found the hint to put the following into the 
/etc/modprobe.d/alsa-base.conf:
  options snd-hda-intel model=laptop

  But for me this does not work.

  Thank you for your help.
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: HDA Generic [HDA Generic]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: HDA Generic [HDA Generic]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mschewe1431 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf262 irq 17'
 Mixer name : 'Conexant ID 5069'
 Components : 'HDA:14f15069,17aa2132,00100300'
 Controls  : 6
 Simple ctrls  : 4
  DistroRelease: Ubuntu 10.04
  InstallationMedia: Error: [Errno 13] Permission denied: 
'/var/log/installer/media-info'
  Package: alsa-driver (not installed)
  ProcEnviron:
   LANG=de_DE.utf8
   SHELL=/usr/bin/zsh
  ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
  Tags: lucid
  Uname: Linux 2.6.32-17-generic i686
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: HDA Generic [HDA Generic]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: HDA Generic [HDA Generic]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mschewe1488 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf262 irq 17'
 Mixer name : 'Conexant ID 5069'
 Components : 'HDA:14f15069,17aa2132,00100300'
 Controls  : 6
 Simple ctrls  : 4
  DistroRelease: Ubuntu 10.04
  InstallationMedia: Error: [Errno 13] Permission denied: 
'/var/log/installer/media-info'
  Package: alsa-driver (not installed)
  ProcEnviron:
   LANG=de_DE.utf8
   SHELL=/usr/bin/zsh
  ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
  Tags: lucid
  Uname: Linux 2.6.32-17-generic i686
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

  --- 
  AlsaVersion:
   Advanced Linux Sound Architecture Driver Version 1.0.23.
   Compiled on Apr 21 2010 for kernel 2.6.32-21-generic (SMP).
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mschewe1673 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf262 irq 31'
 Mixer name : 'Conexant CX20585'
 Components : 'HDA:14f15069,17aa2132,00100300'
 Controls  : 12
 Simple ctrls  : 10
  DistroRelease: Ubuntu 10.04
  InstallationMedia: Ubuntu 10.04 Lucid Lynx - Beta i386 (20100317.1)
  Package: alsa-driver (not installed)
  ProcEnviron:
   LANG=de_DE.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
  Tags: lucid
  Uname: Linux 2.6.32-21-generic i686
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 11/27/2009
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6HET27WW (1.12 )
  dmi.board.name: 2815W3F
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information

[Touch-packages] [Bug 472113] Re: crash reporter crashes on load

[Rolf Leggewie]

We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on the current status, under the Status column, and change
the Status back to New. Thanks again!

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

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

Title:
  crash reporter crashes on load

Status in “apport” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: thunar

  i386 566mhz 192MB jaunty 9.10 PC
  The orange splash with the exclamation mark in top 
  panel pops up with a crash report balloon.
  But when I click on the icon to get the 
  reporter started it crashes every time
  before its window appears.

  I installed up-to-date 9.04 about a month ago and updated every time
  until 9.10 came out and I updated to that and the new feature didn't
  work.

  ProblemType: Crash
  Architecture: i386
  Date: Mon Nov  2 14:33:53 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/lib/thunar/xfce4/panel-plugins/thunar-tpa
  Package: thunar 1.0.1-1ubuntu2
  ProcCmdline: /usr/lib/thunar/xfce4/panel-plugins/thunar-tpa socket_id 
23068713 name thunar-tpa id 4 display_name Trash\ Applet size 19 
screen_position 11
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  Signal: 4
  SourcePackage: thunar
  StacktraceTop:
   g_hash_table_new@plt () from /usr/lib/libgdk-x11-2.0.so.0
   ?? () from /usr/lib/libgdk-x11-2.0.so.0
   ?? () from /usr/lib/libgdk-x11-2.0.so.0
   ?? () from /usr/lib/libgdk-x11-2.0.so.0
   ?? () from /usr/lib/libgdk-x11-2.0.so.0
  Title: thunar-tpa crashed with SIGILL in g_hash_table_new@plt()
  Uname: Linux 2.6.31-14-generic i686
  UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare

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

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

[Touch-packages] [Bug 1391930] Re: Need a way for applications to ask permission to read/write in pictures/videos folders on SD card

[Jamie Strandboge]

** Changed in: apparmor-easyprof-ubuntu (Ubuntu Utopic)
   Status: Triaged = In Progress

** Changed in: apparmor-easyprof-ubuntu (Ubuntu Vivid)
   Status: Triaged = In Progress

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

Title:
  Need a way for applications to ask permission to read/write in
  pictures/videos folders on SD card

Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
  In Progress
Status in “apparmor-easyprof-ubuntu” source package in Utopic:
  In Progress
Status in “apparmor-easyprof-ubuntu” source package in Vivid:
  In Progress
Status in “apparmor-easyprof-ubuntu” package in Ubuntu RTM:
  New

Bug description:
  The camera and the gallery app today are authorized to read/write in 
/home/$USER/Pictures and /home/$USER/Videos.
  Now they also need to be able to read/write in the similar directories of the 
SD card, for example:
  - /media/phablet/064a-7494/Pictures
  - /media/phablet/064a-7494/Videos

  As a side note, we are using the following API in applications to retrieve 
the path (e.g. /home/phablet/Pictures):
  http://qt-project.org/doc/qt-5/qstandardpaths.html#writableLocation

  To retrieve the similar path on the SD card we are considering using a
  combination of that to guess the directory name (Pictures)
  concatenated with the value of http://doc-snapshot.qt-
  project.org/qt5-5.4/qstorageinfo.html#rootPath

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

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

[Touch-packages] [Bug 1384286] Re: add directory allowing scopes and apps to share data

[Jamie Strandboge]

** Changed in: apparmor-easyprof-ubuntu (Ubuntu RTM)
   Status: In Progress = New

** Changed in: apparmor-easyprof-ubuntu (Ubuntu RTM)
 Assignee: (unassigned) = Jamie Strandboge (jdstrand)

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

Title:
  add directory allowing scopes and apps to share data

Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
  In Progress
Status in “click-reviewers-tools” package in Ubuntu:
  In Progress
Status in “unity-scopes-api” package in Ubuntu:
  Fix Committed
Status in “apparmor-easyprof-ubuntu” source package in Utopic:
  In Progress
Status in “click-reviewers-tools” source package in Utopic:
  New
Status in “unity-scopes-api” source package in Utopic:
  New
Status in “apparmor-easyprof-ubuntu” source package in Vivid:
  In Progress
Status in “click-reviewers-tools” source package in Vivid:
  In Progress
Status in “unity-scopes-api” source package in Vivid:
  Fix Committed
Status in “apparmor-easyprof-ubuntu” package in Ubuntu RTM:
  New

Bug description:
  Summary says it all, just need to decide on the directory. I propose using 
this rule:
    # Allow scopes to share data with the app shipped in the same click
    owner @{HOME}/.local/share/@{APP_PKGNAME}/r,
    owner @{HOME}/.local/share/@{APP_PKGNAME}/**  mrkl,

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

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

[Touch-packages] [Bug 309042] Re: [intrepid, jaunty]: no brazil - thinkpad keyboard layout option anymore

[Rolf Leggewie]

We'd like to figure out what's causing this bug for you, but we haven't
heard back from you in a while. Could you please provide the requested
information? Thanks!

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

Title:
  [intrepid,jaunty]: no brazil - thinkpad keyboard layout option
  anymore

Status in “console-setup” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: console-setup

  I upgraded from Hardy to Intrepid and my / key stopped working. I
  have a Brazilian T61 Lenovo laptop.

  A dpkg-reconfigure console-setup doesn't show me a Brazilian -
  Thinkpad option at the layout screen (screenshot attached). That's
  odd, because the intrepid installation does show it (second screenshot
  attached).

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

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

[Touch-packages] [Bug 1392176] Re: mounts cgroups unconditionally which causes undesired effects with cpu hotplug

[Martin Pitt]

systemd (in the sense of pid 1) doesn't do that. I. e. if you boot with
init=/bin/systemd the only cgroup controller it puts tasks into (by
default) is the systemd one, for that very reason. But if you boot
with upstart (Ubuntu's default still), cgmanager creates cgroups.
cgmanager puts tasks into *all* controllers (including cpu); as far as
I know, this is so that user LXC containers work. So from cgmanager's
POV this might be a design decision which can't otherwise be
accomplished with the current kernel, but I'll let the cgmanager
maintainers decide about whether this is a wontfix or whether there is
a more elegant way to make user containers work.

** Summary changed:

- Systemd mounts cgroups unconditionally which causes undesired effects with 
cpu hotplug
+ mounts cgroups unconditionally which causes undesired effects with cpu hotplug

** Package changed: systemd (Ubuntu) = cgmanager (Ubuntu)

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

Title:
  mounts cgroups unconditionally which causes undesired effects with cpu
  hotplug

Status in “cgmanager” package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Preeti U. Murthy preeti.mur...@in.ibm.com - 2014-10-20 
04:40:12 ==
  ---Problem Description---
  Systemd mounts cgroups explicitly every boot. Since the user had no say in 
it, undesired consequences are observed in reaction to cpu hotplug operations.  
Here is how.

  Systemd moves the tasks to the cgroup mounted by it. This cgroup 
automatically becomes the child of the root cgroup which is present by default. 
The children cgroups are not expected to remember their configured cpusets 
after hotplug operations in the kernel. Hence when cpus are taken offline and 
brought back online they are no longer used for load balancing of tasks and 
hence remain unused. 
 This is an undesired consequence because the user had not even asked for 
cgroups to be mounted, yet is not able to use the full capacity of the system.

  Only when the user himself creates cgroup hierarchies, should he be
  exposed to the side effects of cpu hotplug on cpusets. Else all online
  cpus must be made available to him which is not happening since
  systemd mounts cgroups on every boot.

  Hence please revert this feature or provide an explaination as to why this is 
being done.
   
  ---uname output---
  Linux tul181p1 3.16.0-18-generic #25-Ubuntu SMP Fri Sep 26 02:39:53 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = Tuleta 8286-42A 
   ---Debugger---
  A debugger was configured, however the system did not enter into the debugger
   
  ---Steps to Reproduce---
   $ taskset -p $$
  $ 0-127
  $ echo 0  /sys/devices/system/cpu/cpu7/online
  $ taskset -p $$
  $ 0-6,8-127
  $ echo 1  /sys/devices/system/cpu/cpu7/online
  $ taskset -p $$
  $ 0-6,8-127
   
   
  Userspace tool common name: systemd 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: systemd_208-8ubuntu8_ppc64el.deb

  Userspace tool obtained from project website:   208-8ubuntu8

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

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

[Touch-packages] [Bug 1392400] [NEW] Avoid overdraws and batch breaking

[Gustavo Pichorim Boiko]

Public bug reported:

QSceneGraph's tools to identify overdraws and batch breaking found some
issues on dialer-app.

Please correct them so that rendering is buttery smooth.

** Affects: dialer-app
 Importance: Undecided
 Assignee: Gustavo Pichorim Boiko (boiko)
 Status: New

** Affects: dialer-app (Ubuntu)
 Importance: Undecided
 Assignee: Gustavo Pichorim Boiko (boiko)
 Status: In Progress

** Affects: dialer-app (Ubuntu RTM)
 Importance: Undecided
 Assignee: Gustavo Pichorim Boiko (boiko)
 Status: New

** Also affects: dialer-app (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: dialer-app (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Changed in: dialer-app
 Assignee: (unassigned) = Gustavo Pichorim Boiko (boiko)

** Changed in: dialer-app (Ubuntu)
 Assignee: (unassigned) = Gustavo Pichorim Boiko (boiko)

** Changed in: dialer-app (Ubuntu RTM)
 Assignee: (unassigned) = Gustavo Pichorim Boiko (boiko)

** Changed in: dialer-app (Ubuntu)
   Status: New = In Progress

** Branch linked: lp:~boiko/dialer-app/qsg_optimizations

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

Title:
  Avoid overdraws and batch breaking

Status in Dialer app for Ubuntu Touch:
  New
Status in “dialer-app” package in Ubuntu:
  In Progress
Status in “dialer-app” package in Ubuntu RTM:
  New

Bug description:
  QSceneGraph's tools to identify overdraws and batch breaking found
  some issues on dialer-app.

  Please correct them so that rendering is buttery smooth.

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

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

[Touch-packages] [Bug 1392399] [NEW] Enabling/Disabling the GPS provider does not reliably enforce the provider to be stopped

[Thomas Voß]

Public bug reported:

Whenever the user requests satellite-based positioning to be disabled,
the location::Engine instance should walk through all providers and
disable the ones requiring satellites for positioning.

** Affects: location-service (Ubuntu)
 Importance: Critical
 Assignee: Thomas Voß (thomas-voss)
 Status: In Progress

** Affects: location-service (Ubuntu RTM)
 Importance: Critical
 Assignee: Thomas Voß (thomas-voss)
 Status: In Progress

** Changed in: location-service (Ubuntu)
 Assignee: (unassigned) = Thomas Voß (thomas-voss)

** Changed in: location-service (Ubuntu)
   Importance: Undecided = Critical

** Changed in: location-service (Ubuntu)
   Status: New = In Progress

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

** Changed in: location-service (Ubuntu RTM)
   Status: New = In Progress

** Changed in: location-service (Ubuntu RTM)
   Importance: Undecided = Critical

** Changed in: location-service (Ubuntu RTM)
 Assignee: (unassigned) = Thomas Voß (thomas-voss)

** Branch linked: lp:~thomas-voss/location-service/allow-for-disabling-
providers

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

Title:
  Enabling/Disabling the GPS provider does not reliably enforce the
  provider to be stopped

Status in “location-service” package in Ubuntu:
  In Progress
Status in “location-service” package in Ubuntu RTM:
  In Progress

Bug description:
  Whenever the user requests satellite-based positioning to be disabled,
  the location::Engine instance should walk through all providers and
  disable the ones requiring satellites for positioning.

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

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

[Touch-packages] [Bug 1392403] [NEW] Remove obsolete tools

[Gustavo Pichorim Boiko]

Public bug reported:

History-service used to provide a tool to import logs from telepathy-
logger. This tool is not necessary anymore and thus needs to be removed.

This will also help reducing the build dependencies it currently has as
TelepathyLoggerQt5 and QtGLib won't be necessary anymore to build this
package.

** Affects: history-service
 Importance: Undecided
 Assignee: Gustavo Pichorim Boiko (boiko)
 Status: New

** Affects: history-service (Ubuntu)
 Importance: Undecided
 Assignee: Gustavo Pichorim Boiko (boiko)
 Status: In Progress

** Affects: history-service (Ubuntu RTM)
 Importance: Undecided
 Assignee: Gustavo Pichorim Boiko (boiko)
 Status: New

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

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

** Changed in: history-service
 Assignee: (unassigned) = Gustavo Pichorim Boiko (boiko)

** Changed in: history-service (Ubuntu)
 Assignee: (unassigned) = Gustavo Pichorim Boiko (boiko)

** Changed in: history-service (Ubuntu RTM)
 Assignee: (unassigned) = Gustavo Pichorim Boiko (boiko)

** Changed in: history-service (Ubuntu)
   Status: New = In Progress

** Branch linked: lp:~boiko/history-service/remove_tools

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

Title:
  Remove obsolete tools

Status in Telephony History Service:
  New
Status in “history-service” package in Ubuntu:
  In Progress
Status in “history-service” package in Ubuntu RTM:
  New

Bug description:
  History-service used to provide a tool to import logs from telepathy-
  logger. This tool is not necessary anymore and thus needs to be
  removed.

  This will also help reducing the build dependencies it currently has
  as TelepathyLoggerQt5 and QtGLib won't be necessary anymore to build
  this package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/history-service/+bug/1392403/+subscriptions

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