[Touch-packages] [Bug 1374782] Re: OpenVPN doesnt ask for pkcs12 password

2014-09-29 Thread Martin Pitt
Ubuntu does not yet install a systemd-ask-password agent. It seems
openvpn went too much ahead and is relying on this without checking
whether a password agent is running.

** Package changed: systemd (Ubuntu) = openvpn (Ubuntu)

** Summary changed:

- OpenVPN doesnt ask for pkcs12 password
+ OpenVPN interactively asks for a password in an init script

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

Title:
  OpenVPN interactively asks for a password in an init script

Status in “openvpn” package in Ubuntu:
  New

Bug description:
  Hi All,

  today I have upgraded my Kubuntu client to Utopic, 
  and now OpenVPN doesen't ask me for my pkcs12 password

  I start it via init.d script as root

root@client:~# /etc/init.d/openvpn start CLIENT1
* Starting virtual private network daemon(s)...
*   Starting VPN 'CLIENT1'
Timed out

  and in the processlist I found, the systemd-ask-password ask for fhe 
password
  but there is no popup or other password ask dialog

8523 ?Sl 0:17  \_ /usr/bin/konsole
8526 pts/0Ss 0:00  |   \_ /bin/bash
9142 pts/0S  0:00  |   |   \_ sudo -i
9143 pts/0S  0:00  |   |   \_ -bash
18807 pts/0S+ 0:00  |   |   \_ /bin/sh -e 
/etc/init.d/openvpn start CLIENT1
18830 pts/0S+ 0:00  |   |   \_ 
/usr/sbin/openvpn --writepid /run/openvpn/CLIENT1.pid --daemon ovpn-CLIENT1 
--status /run/openvpn/CLIENT1.statu
18831 pts/0S+ 0:00  |   |   \_ 
/bin/systemd-ask-password Enter Private Key Password:

  It worked unter Ubuntu Trusty and bevor!

  What is wrong?

  
  OS Infos:
Distributor ID: Ubuntu
Description:Ubuntu Utopic Unicorn (development branch)
Release:14.10
Codename:   utopic

ii  openvpn  2.3.2-9ubuntu1  amd64  
 virtual private network daemon
ii  systemd  208-8ubuntu4amd64  
 system and service manager

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: systemd 208-8ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3
  Uname: Linux 3.16.0-18-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  Date: Sat Sep 27 17:12:04 2014
  ExecutablePath: /bin/systemd-ask-password
  ProcEnviron:
   
  SourcePackage: systemd
  UpgradeStatus: Upgraded to utopic on 2014-09-27 (0 days ago)

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

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


[Touch-packages] [Bug 1374441] Re: Translations not loaded for No data sources available

2014-09-29 Thread Martin Pitt
I built new RTM langpacks yesterday, but they were based on an export
from Sep 25, so they don't yet contain these. I now adjusted
langpack-o-matic to pull translations directly from trunk to speed this
up.

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

Title:
  Translations not loaded for No data sources available

Status in Ubuntu Translations:
  Incomplete
Status in “libusermetrics” package in Ubuntu:
  Incomplete

Bug description:
  See the attached screenshot, the translations for the No data sources
  available sentence never seem to get loaded.

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

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


[Touch-packages] [Bug 1359249] Re: Launching PAVUControl works from Xubuntu, but not from Xfce

2014-09-29 Thread Roman
roman@Roman-PC:~$ echo $XDG_CURRENT_DESKTOP
XFCE
roman@Roman-PC:~$ echo $DESKTOP_SESSION
xfce


The thing is, I would rather have the gnome audio manager over PAVUControl (I 
consider it more user-friendly) and certainly o.ver the Unity one, especially 
since Unity is planning on switching to Qt-based one anyway.

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

Title:
  Launching PAVUControl works from Xubuntu, but not from Xfce

Status in “indicator-sound” package in Ubuntu:
  Confirmed

Bug description:
  In Xubuntu 14.04 when clicking the sound indicator and choosing Sound
  Settings Pavucontrol is launched, but it does not get launched in the
  same scenario when the session Xfce is launched instead, with the
  same settings. In fact I installed the xfce4 package on top of
  Xubuntu's and launched it. Both xsession files list the same thing to
  start it, so is indicator only choosing to work on whitelisted
  sessions?

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

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


[Touch-packages] [Bug 1343341] Re: /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::

2014-09-29 Thread Antti Kaijanmäki
Jussi, please take a look ASAP.

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

Title:
  /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-
  
service:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:core::dbus::Bus::send_with_reply_and_block_for_at_most

Status in “indicator-network” package in Ubuntu:
  Confirmed
Status in “indicator-network” package in Ubuntu RTM:
  Confirmed

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

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

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


[Touch-packages] [Bug 1347913] Re: Turn screen on when phone is moved during a call

2014-09-29 Thread Andreas Pokorny
The assumption here is that the speaker ouput mode or a blue tooth evice
is used for the call?

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

Title:
  Turn screen on when phone is moved during a call

Status in Dialer app for Ubuntu Touch:
  New
Status in Ubuntu UX bugs:
  Triaged
Status in “powerd” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  New

Bug description:
  This is a breakaway bug from bug 1347001.

  During a call, position the phone such that the proximity sensor is
  not enabled, i.e. put phone on table.  Let the screen shut off after
  an idle timeout.

  The screen should turn on when the phone is moved or screen is
  touched.  This is what Android and iOS do anyway, and probably what
  users expect.

  I'm assuming that powerd is the logical place to have that logic, but
  maybe I'm wrong.  Please feel free to re-assign.

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

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


[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf

2014-09-29 Thread Dariusz Gadomski
@TWC Service Thank you for checking this.

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

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

Title:
  Incorrect udev-fallback-graphics.conf

Status in “systemd” package in Ubuntu:
  Fix Released
Status in “udev” package in Ubuntu:
  Invalid
Status in “udev” source package in Precise:
  Fix Committed
Status in “systemd” source package in Trusty:
  Fix Committed
Status in “systemd” source package in Utopic:
  Fix Released

Bug description:
  [Impact]

   * When setting up primary display driver fails an attempt to load vesafb
 module is undertaken. This fails since from 3.13.0-16.36 version
 vesafb is compiled in the kernel (so no actual modprobing is needed).
 This causes false alert in the log:
 Starting load fallback graphic devices: [fail]

  [Test Case]

   * Start Ubuntu unable to load primary graphics driver (the simplest way is 
to remove module responsible for the device).
   * Wait for loading graphics devices.
   * If the primary device module has failed to load, falling back to vesafb 
will be attempted.

  [Regression Potential]

   * Implemented by the bug reported.

   * Affects only the debian/ directory.

  [Other Info]
   
   * Original bug description:

  The udev-fallback-graphics.conf script tries to load vesafb module if
  PRIMARY_DEVICE_FOR_DISPLAY has not been set earlier.

  The problem is that from kernel version 3.13.0-16.36 vesafb is
  compiled in permanently into the kernel (CONFIG_FB_VESA=y), so
  whenever the fallback mode is triggered this script will FAIL
  confusing the users.

  Most probably this file is no longer needed (or it just be used to
  print informative message).

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

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


[Touch-packages] [Bug 1289730] Re: systemd-udev fails to execute alsactl during start-up if /usr and/or /var are separate volumes

2014-09-29 Thread David Henningsson
Hi!

I believe this is now fixed in Ubuntu 14.10, because the patches were
included in upstream alsa-utils 1.0.28 which is in Utopic since end of
July. Please confirm and reopen the bug if it is not. Thanks!

Reference:
http://git.alsa-project.org/?p=alsa-utils.git;a=commitdiff;h=be4565c84163a158bec5380df6c0201f738c2013


** Changed in: alsa-utils (Ubuntu)
   Status: Confirmed = Fix Released

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

Title:
  systemd-udev fails to execute alsactl during start-up if /usr and/or
  /var are separate volumes

Status in “alsa-utils” package in Ubuntu:
  Fix Released

Bug description:
  During system startup systemd-udev will print the following error
  messages:

  [   15.089778] systemd-udevd[683]: failed to execute '/usr/sbin/alsactl' 
'/usr/sbin/alsactl -E HOME=/var/run/alsa restore 0': No such file or directory
  [   15.090130] systemd-udevd[684]: failed to execute '/usr/sbin/alsactl' 
'/usr/sbin/alsactl -E HOME=/var/run/alsa restore 1': No such file or directory

  alsactl is present:

  $ which alsactl
  /usr/sbin/alsactl

  but on a separate partition:
  $ df -h /usr/sbin/alsactl 
  DateisystemGröße Benutzt Verf. Verw% Eingehängt auf
  /dev/mapper/scaleo-usr   12G6,6G  4,1G   62% /usr

  $ df -h /var
  DateisystemGröße Benutzt Verf. Verw% Eingehängt auf
  /dev/mapper/scaleo-var  7,3G2,5G  4,4G   37% /var

  This suggests that systemd-udev is called before all local partitions
  have been mounted.

  $ lsb_release -rd
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04

  $ apt-cache policy udev
  udev:
Installiert:   204-5ubuntu13
Installationskandidat: 204-5ubuntu13
Versionstabelle:
   *** 204-5ubuntu13 0
  500 http://de.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  Kind regards,
Dominik

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

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


[Touch-packages] [Bug 1343341] Re: /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::

2014-09-29 Thread Jussi Pakkanen
** Branch linked: lp:~jpakkane/indicator-network/youknowwhat

** Changed in: indicator-network (Ubuntu)
   Status: Confirmed = In Progress

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

Title:
  /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-
  
service:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:core::dbus::Bus::send_with_reply_and_block_for_at_most

Status in “indicator-network” package in Ubuntu:
  In Progress
Status in “indicator-network” package in Ubuntu RTM:
  Confirmed

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

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

-- 
Mailing list: https://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 1374577] Re: 'unconfined' should be precached and not listed under 'Location access' (or 'Other app access')

2014-09-29 Thread David Barth
Indeed, the Location plugin in System settings does /hide/ unconfined
entries, because:
1. there is no way to get back to the actual application desktop file to
display its name and icon: we just know that an undefined unconfined
application was granted access
2. in theory unconfined applications can bypass the location service to
obtain the information they want; so an on/off toggle would give a false
sense of control


On Fri, Sep 26, 2014 at 11:09 PM, Jamie Strandboge ja...@ubuntu.com wrote:

 Ok, I was wrong, after reseting the db, I can see that while the
 location service does incorrectly prompt, system settings does not show
 it. This is somewhat worse than I thought because if you choose the
 wrong thing with the location trust store, you cannot undo it (without
 resetting the db). Marking system settings task as invalid.

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

 ** Summary changed:

 - 'unconfined' should be precached and not listed under 'Location access'
 (or 'Other app access')
 + 'unconfined' should be precached for trusted helpers

 ** Changed in: location-service (Ubuntu)
Importance: Undecided = Critical

 ** Description changed:

 - If I go to Location access under Security  Privacy, I have an entry in
 - the list that is blank which corresponds to 'unconfined' ('unconfined'
 - should be precached to default to 'allow' anyway).
 -
   We should not prompt the user for unconfined or allow the user to adjust
   entries for 'unconfined' processes in System Settings since this might
   break things in unexpected ways. Marking as Critical and for rtm14
   because this is user facing, confusing to have a blank entry, can lead
 - to unexpected behavior, it should be trivial to filter this out in
 - system settings and because it should be easy to precache this.
 + to unexpected behavior, and because it should be easy to precache this.

   Steps to reproduce (this resets the location trust-store db):
   1. $ stop ubuntu-location-service-trust-stored
   2. mv ~/.local/share/UbuntuLocationService/trust.db
 ~/.local/share/UbuntuLocationService/trust.db.bak
   3. $ start ubuntu-location-service-trust-stored
   4. launch webbrowser-app (it is unconfined)
   5. navigate to maps.google.com. it will prompt to access location
 (browser prompt). Say yes

   At this point I am presented with a trust session prompt:
   unconfined

   An unconfined application wants to access your current location.

   Deny

   Allow

   6. tap 'Allow'

   This adds the following to the trust store:
   3|unconfined|0|1411758762544069109|1

   location service shouldn't be prompting for this for the reasons
   outlined above. Adding location-service task.

   This will likely affect camera and mic in 'Other app access'.

 --
 You received this bug notification because you are a bug assignee.
 https://bugs.launchpad.net/bugs/1374577

 Title:
   'unconfined' should be precached for trusted helpers

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1374577/+subscriptions


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

Title:
  'unconfined' should be precached for trusted helpers

Status in “location-service” package in Ubuntu:
  New
Status in “ubuntu-system-settings” package in Ubuntu:
  Invalid

Bug description:
  We should not prompt the user for unconfined or allow the user to
  adjust entries for 'unconfined' processes in System Settings since
  this might break things in unexpected ways. Marking as Critical and
  for rtm14 because this is user facing, confusing to have a blank
  entry, can lead to unexpected behavior, and because it should be easy
  to precache this.

  Steps to reproduce (this resets the location trust-store db):
  1. $ stop ubuntu-location-service-trust-stored
  2. mv ~/.local/share/UbuntuLocationService/trust.db 
~/.local/share/UbuntuLocationService/trust.db.bak
  3. $ start ubuntu-location-service-trust-stored
  4. launch webbrowser-app (it is unconfined)
  5. navigate to maps.google.com. it will prompt to access location (browser 
prompt). Say yes

  At this point I am presented with a trust session prompt:
  unconfined

  An unconfined application wants to access your current location.

  Deny

  Allow

  6. tap 'Allow'

  This adds the following to the trust store:
  3|unconfined|0|1411758762544069109|1

  location service shouldn't be prompting for this for the reasons
  outlined above. Adding location-service task.

  This will likely affect camera and mic in 'Other app access'.

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

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

[Touch-packages] [Bug 1301623] Re: unity freezes when moving windows among workspaces

2014-09-29 Thread Robert Stones
Same issue on a Lenovo ThinkPad W530 Core i7

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

Title:
  unity freezes when moving windows among workspaces

Status in Unity:
  Incomplete
Status in “unity” package in Ubuntu:
  Incomplete

Bug description:
  Sometimes In Ubuntu 14.04, when I move windows from one workspace to
  another, Unity freezes, letting me with this 4 workspaces overview. I
  have to use terminal and restart Unity to resolve it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140328.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-18.32~precise1-generic 3.11.10.4
  Uname: Linux 3.11.0-18-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.13.3-0ubuntu1
  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,dbus]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Apr  2 23:26:06 2014
  DistUpgraded: 2014-03-18 07:46:56,695 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:365e]
  InstallationDate: Installed on 2014-02-10 (51 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release amd64 
(20140204)
  MachineType: LENOVO 10104
  ProcEnviron:
   LANGUAGE=cs
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-18-generic 
root=UUID=3a918684-e656-4e86-9b7b-22e0fd6b2135 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-03-18 (15 days ago)
  dmi.bios.date: 03/21/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: ELKT31AUS
  dmi.board.name: MAHOBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193 STD
  dmi.chassis.type: 13
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrELKT31AUS:bd03/21/2013:svnLENOVO:pn10104:pvrLenovoC440:rvnLENOVO:rnMAHOBAY:rvr3193STD:cvnToBeFilledByO.E.M.:ct13:cvrToBeFilledByO.E.M.:
  dmi.product.name: 10104
  dmi.product.version: Lenovo C440
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  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
  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: Mon Mar 31 16:48:50 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id8192 
   vendor LEN
  xserver.version: 2:1.15.0-1ubuntu7

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

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


[Touch-packages] [Bug 1359153] Re: YouTube labels and categories are not localized

2014-09-29 Thread Albert Astals Cid
Actually there may be a bug in unity-scope-youtube since for example
Popular on YouTube does not appear for translation in
https://translations.launchpad.net/unity-scope-youtube

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

Title:
  YouTube labels and categories are not localized

Status in Ubuntu Rest Scopes:
  Invalid
Status in Ubuntu Translations:
  Triaged
Status in “unity-scope-youtube” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  Invalid

Bug description:
  YouTube scope shows untranslated categories and labels.

  Test case.
  - Switch Ubuntu Phone to Spanish, reboot.
  - Go to YouTube scope.

  Expected result.
  - Labels and categories must be displayed in Spanish.

  Actual result.
  - Best of YouTube and its categories are displayed in English.
  - Sports, Gaming, number of views and other labels are displayed also 
in English.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-rest-scopes/+bug/1359153/+subscriptions

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


[Touch-packages] [Bug 1359153] Re: YouTube labels and categories are not localized

2014-09-29 Thread Albert Astals Cid
Nothing to do with unity8, I don't even think it's a unity-scope-youtube
bug, simply there are no translations to Spanish in
https://translations.launchpad.net/unity-scope-youtube

** Also affects: unity-scope-youtube (Ubuntu)
   Importance: Undecided
   Status: New

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

** No longer affects: unity8

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

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

Title:
  YouTube labels and categories are not localized

Status in Ubuntu Rest Scopes:
  Invalid
Status in Ubuntu Translations:
  Triaged
Status in “unity-scope-youtube” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  Invalid

Bug description:
  YouTube scope shows untranslated categories and labels.

  Test case.
  - Switch Ubuntu Phone to Spanish, reboot.
  - Go to YouTube scope.

  Expected result.
  - Labels and categories must be displayed in Spanish.

  Actual result.
  - Best of YouTube and its categories are displayed in English.
  - Sports, Gaming, number of views and other labels are displayed also 
in English.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-rest-scopes/+bug/1359153/+subscriptions

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


[Touch-packages] [Bug 1374548] Re: Manage scopes view overlaps the scope preview

2014-09-29 Thread Albert Astals Cid
** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) = Albert Astals Cid (aacid)

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

Title:
  Manage scopes view overlaps the scope preview

Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce the issue :

  - Pull up to reveal the Manage Scopes view
  - Tape on All
  - Long Tape on Applications Scope to get the preview
  - Tape on the Search button
  - Pull up again to reveal the Manage Scopes view

  see screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity8 8.00+14.10.20140918.3-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: armhf
  Date: Fri Sep 26 17:54:07 2014
  InstallationDate: Installed on 2014-09-26 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140926-020204)
  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/1374548/+subscriptions

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


[Touch-packages] [Bug 1373131] Re: PulseAudio seems to have crashed.

2014-09-29 Thread David Henningsson
Hi,

It's hard to tell why PulseAudio crashes or does not start. You do have
some worrying messages about read failures from sda (which is usually
your hard drive), but I'm not sure if that's related.

The best would be if you could also produce a PulseAudio log:
https://wiki.ubuntu.com/PulseAudio/Log - and try to connect to HDMI
while the log is running. Can you do that? Thanks in advance.

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

Title:
  PulseAudio seems to have crashed.

Status in “pulseaudio” package in Ubuntu:
  New

Bug description:
  PulseAudio seems to have crashed.
  can't conect to hdmi,
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  ApportVersion: 2.0.1-0ubuntu17.7
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D3', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xc260 irq 45'
 Mixer name : 'Intel PantherPoint HDMI'
 Components : 'HDA:10ec0269,103c1854,00100202 
HDA:80862806,80860101,0010'
 Controls  : 25
 Simple ctrls  : 11
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-anaheim-precise-amd64-20130326-1
  DistroRelease: Ubuntu 12.04
  InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 
20130326-08:07
  MarkForUpload: True
  Package: pulseaudio 1:1.1-0ubuntu15.4
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.5.0-54.81~precise1-generic 3.5.7.33
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  precise running-unity
  Uname: Linux 3.5.0-54-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 05/13/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.35
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 1854
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 64.28
  dmi.chassis.asset.tag: 5CG3262F2F
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.35:bd05/13/2013:svnHewlett-Packard:pnHP250G1NotebookPC:pvr088E1300591600010:rvnHewlett-Packard:rn1854:rvr64.28:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 250 G1 Notebook PC
  dmi.product.version: 088E1300591600010
  dmi.sys.vendor: Hewlett-Packard
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  ApportVersion: 2.0.1-0ubuntu17.7
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D3', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xc260 irq 45'
 Mixer name : 'Intel PantherPoint HDMI'
 Components : 'HDA:10ec0269,103c1854,00100202 
HDA:80862806,80860101,0010'
 Controls  : 25
 Simple ctrls  : 11
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-anaheim-precise-amd64-20130326-1
  DistroRelease: Ubuntu 12.04
  InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 
20130326-08:07
  MarkForUpload: True
  Package: pulseaudio 1:1.1-0ubuntu15.4
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.5.0-54.81~precise1-generic 3.5.7.33
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  precise running-unity
  Uname: Linux 3.5.0-54-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 

[Touch-packages] [Bug 1370464] Re: yr.no changed the api version

2014-09-29 Thread Martin Pitt
** Also affects: libgweather (Ubuntu Utopic)
   Importance: Undecided
   Status: Confirmed

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

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

Title:
  yr.no changed the api version

Status in libgweather:
  Fix Released
Status in “libgweather” package in Ubuntu:
  Fix Committed
Status in “libgweather” source package in Trusty:
  New
Status in “libgweather” source package in Utopic:
  Fix Committed
Status in “libgweather” package in Debian:
  New

Bug description:
  yr.no, e.g. used as data source in the Gnome Shell extension weather
  (https://extensions.gnome.org/extension/613/weather/), changed its API
  version. Thus this extension does not work anymore:
  https://github.com/Neroth/gnome-shell-extension-weather/issues/208

  Fixed already upstream for version 3.12, see
  https://bugzilla.gnome.org/show_bug.cgi?id=736334

  Ubuntu version: 14.04
  Package version: 3.10.2-0ubuntu1

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

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


[Touch-packages] [Bug 1370464] Re: yr.no changed the api version

2014-09-29 Thread Launchpad Bug Tracker
** Branch linked: lp:~ubuntu-desktop/libgweather/ubuntu

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

Title:
  yr.no changed the api version

Status in libgweather:
  Fix Released
Status in “libgweather” package in Ubuntu:
  Fix Committed
Status in “libgweather” source package in Trusty:
  New
Status in “libgweather” source package in Utopic:
  Fix Committed
Status in “libgweather” package in Debian:
  New

Bug description:
  yr.no, e.g. used as data source in the Gnome Shell extension weather
  (https://extensions.gnome.org/extension/613/weather/), changed its API
  version. Thus this extension does not work anymore:
  https://github.com/Neroth/gnome-shell-extension-weather/issues/208

  Fixed already upstream for version 3.12, see
  https://bugzilla.gnome.org/show_bug.cgi?id=736334

  Ubuntu version: 14.04
  Package version: 3.10.2-0ubuntu1

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

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


[Touch-packages] [Bug 1370464] Re: yr.no changed the api version

2014-09-29 Thread Martin Pitt
Utopic fix merged and uploaded, thanks!

** Changed in: libgweather (Ubuntu Utopic)
   Status: Confirmed = Fix Committed

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

Title:
  yr.no changed the api version

Status in libgweather:
  Fix Released
Status in “libgweather” package in Ubuntu:
  Fix Committed
Status in “libgweather” source package in Trusty:
  New
Status in “libgweather” source package in Utopic:
  Fix Committed
Status in “libgweather” package in Debian:
  New

Bug description:
  yr.no, e.g. used as data source in the Gnome Shell extension weather
  (https://extensions.gnome.org/extension/613/weather/), changed its API
  version. Thus this extension does not work anymore:
  https://github.com/Neroth/gnome-shell-extension-weather/issues/208

  Fixed already upstream for version 3.12, see
  https://bugzilla.gnome.org/show_bug.cgi?id=736334

  Ubuntu version: 14.04
  Package version: 3.10.2-0ubuntu1

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

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


[Touch-packages] [Bug 1374610] Re: telinit u makes upstart's /sbin/init lose all information on running processes (PIDs)

2014-09-29 Thread James Hunt
Upstart only gained the ability to re-exec statefully in Raring. The man
page for telinit on Lucid explains that state is not preserved and also
warns that running this command is not recommended.

Note that upstart has to re-exec itself on Lucid if certain key packages
are upgraded to ensure a clean filesystem unmount. However, to minimise
issues, the re-exec only occurs at shutdown after all jobs have stopped.

In summary: do not run 'telinit u' manually as the man page warns.

** Changed in: upstart (Ubuntu)
   Status: New = Won't Fix

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

Title:
  telinit u makes upstart's /sbin/init lose all information on running
  processes (PIDs)

Status in “upstart” package in Ubuntu:
  Won't Fix

Bug description:
  running telinit u causes init to re-exec itself. 
  It loses all process state information in the process, so that services can 
no longer be stopped/restarted, and restart or start will either start a daemon 
twice or fail to start it as a consequence.

  There needs to be a way that either:
  - init, telinit, initctl and possibly other manual pages warn of this loss of 
information;
  or 
  - this feature gets removed,
  or
  - init remembers the process IDs across a restart unless told otherwise.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: upstart 0.6.5-8
  ProcVersionSignature: Ubuntu 2.6.32-65.131-generic-pae 2.6.32.63+drm33.26
  Uname: Linux 2.6.32-65-generic-pae i686
  Architecture: i386
  Date: Fri Sep 26 21:35:01 2014
  SourcePackage: upstart

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

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


[Touch-packages] [Bug 1370464] Re: yr.no changed the api version

2014-09-29 Thread Martin Pitt
Trusty SRU uploaded to SRU team review queue. Unsubscribing sponsors
now.

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

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

Title:
  yr.no changed the api version

Status in libgweather:
  Fix Released
Status in “libgweather” package in Ubuntu:
  Fix Committed
Status in “libgweather” source package in Trusty:
  In Progress
Status in “libgweather” source package in Utopic:
  Fix Committed
Status in “libgweather” package in Debian:
  New

Bug description:
  yr.no, e.g. used as data source in the Gnome Shell extension weather
  (https://extensions.gnome.org/extension/613/weather/), changed its API
  version. Thus this extension does not work anymore:
  https://github.com/Neroth/gnome-shell-extension-weather/issues/208

  Fixed already upstream for version 3.12, see
  https://bugzilla.gnome.org/show_bug.cgi?id=736334

  Ubuntu version: 14.04
  Package version: 3.10.2-0ubuntu1

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

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


[Touch-packages] [Bug 1207772] Re: [Addres book] Date of birth field is missing

2014-09-29 Thread Sam Bull
The calendar app appears to list 'Birthdays  Anniversaries' as a
calendar, which makes it more confusing and inconsistent while birthdays
are still not exposed. If this is not going to be ready soon, then the
calendar app should probably not show that calendar for the time being.

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

Title:
  [Addres book] Date of birth field is missing

Status in Address Book App:
  In Progress
Status in Ubuntu UX bugs:
  Fix Committed
Status in “address-book-app” package in Ubuntu:
  In Progress

Bug description:
  There is no Date of birth field on the contact view/edit page, as per
  visual design

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

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


[Touch-packages] [Bug 1325626] Re: Inline translations from .desktop files are not loaded

2014-09-29 Thread Ugo Riboni
** Changed in: gallery-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 camera-app in Ubuntu.
https://bugs.launchpad.net/bugs/1325626

Title:
  Inline translations from .desktop files are not loaded

Status in Camera App:
  Fix Released
Status in Gallery App:
  Fix Released
Status in Music application for Ubuntu devices:
  Fix Released
Status in Notes App:
  Confirmed
Status in Sudoku game for Ubuntu Touch:
  New
Status in Calculator application for Ubuntu devices:
  Fix Released
Status in Calendar application for Ubuntu devices:
  Fix Released
Status in Clock application for Ubuntu devices:
  Fix Released
Status in File Manager application for Ubuntu devices:
  Fix Released
Status in RSS Feed Reader application for Ubuntu devices:
  Invalid
Status in Terminal application for Ubuntu devices:
  Fix Released
Status in Weather application for Ubuntu devices:
  Fix Released
Status in “camera-app” package in Ubuntu:
  Fix Released
Status in “gallery-app” package in Ubuntu:
  Fix Released
Status in “unity-scope-click” package in Ubuntu:
  Invalid

Bug description:
  Using image #60, and the Calculator app as an example, the inline
  translations of its desktop files are not loaded.

  Steps to reproduce:

  1. Set the system locale (System Settings  Language  Text) to Spanish or 
Simplified Chinese
  2. Reboot the phone
  Go to My Apps on the click scope

  Actual:
  - Calculator appears untranslated beneath the Calculator icon

  Expected:
  - Calculator appears translated beneath the Calculator icon (if inline 
translations are available in its .desktop file)

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

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


[Touch-packages] [Bug 1375163] [NEW] Stop and restart the camera automatically when app changes active state

2014-09-29 Thread Ugo Riboni
Public bug reported:

At the moment when an application that started the camera stops becoming
active, the camera remains running and other applications can't use it.

The system should automatically detect when an app is being deactivate
and stop the camera, as a minimum.

To be symmetric, when the app gets activated again, it should also
restart it. However this might not be as simple since the camera might
have been re-configured by other apps so if we want the process to be
full automatic the state of the camera configuration should be saved and
restored as well.

** Affects: qtubuntu-camera (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Stop and restart the camera automatically when app changes active
  state

Status in “qtubuntu-camera” package in Ubuntu:
  New

Bug description:
  At the moment when an application that started the camera stops
  becoming active, the camera remains running and other applications
  can't use it.

  The system should automatically detect when an app is being deactivate
  and stop the camera, as a minimum.

  To be symmetric, when the app gets activated again, it should also
  restart it. However this might not be as simple since the camera might
  have been re-configured by other apps so if we want the process to be
  full automatic the state of the camera configuration should be saved
  and restored as well.

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

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


[Touch-packages] [Bug 1274548] Re: gst-plugin-scanner crashed with SIGSEGV in __GI___pthread_mutex_lock()

2014-09-29 Thread David Pires
@ Alberto Salvia Novella:

I am perfectly aware of
https://wiki.ubuntu.com/Bugs/Triage#Apport_crash_reports but besides
the fact that this bug report refer to a a VirtualBox setup that existed
only for testing purposes, neither Stacktrace.txt, StacktraceSource.txt
and ThreadStacktrace.txt contained any sensitive information.

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

Title:
  gst-plugin-scanner crashed with SIGSEGV in __GI___pthread_mutex_lock()

Status in Gstreamer:
  Incomplete
Status in “gstreamer1.0” package in Ubuntu:
  Triaged

Bug description:
  ***
   ISSUE 
  ***

  HOW TO REPRODUCE

  -
  http://iso.qa.ubuntu.com/qatracker/milestones/308/builds/57248/testcases

  EXPECTED BEHAVIOUR

  - The distribution to upgrade without futher problems.

  REAL BEHAVIOUR

  - The gst-plugin-scanner application crashes during the installing
  the upgrades phase of the process.

  RELEVANT DETAILS

  - The user's hardware was http://phillw.net/hardware/Ed3c22qV.

  **
   SOLUTION 
  **

  WORK-AROUND

  - None known.

  FIX

  - Unknown.

  REGRESSION POTENTIAL

  - Since the application doesn't work at all and does a very specific
  action, the regression potential is very low.

  
   TECHNICAL INFO 
  

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: libgstreamer1.0-0 1.2.2-1ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic i686
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: i386
  Date: Thu Jan 30 15:16:32 2014
  ExecutablePath: 
/usr/lib/i386-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner
  InstallationDate: Installed on 2013-11-29 (61 days ago)
  InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release i386 (20131016)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner -l
  SegvAnalysis:
   Segfault happened at: 0xb74cb036 __GI___pthread_mutex_lock+22: mov
0xc(%esi),%eax
   PC (0xb74cb036) ok
   source 0xc(%esi) (0x1070) not located in a known VMA region (needed 
readable region)!
   destination %eax ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gstreamer1.0
  StacktraceTop:
   __GI___pthread_mutex_lock (mutex=0x1064) at ../nptl/pthread_mutex_lock.c:66
   crLockMutex () from /usr/lib/VBoxOGLcrutil.so
   crHashtableLock () from /usr/lib/VBoxOGLcrutil.so
   ?? () from /usr/lib/i386-linux-gnu/dri/vboxvideo_dri.so
   rtThreadMain () from /usr/lib/i386-linux-gnu/dri/vboxvideo_dri.so
  Title: gst-plugin-scanner crashed with SIGSEGV in __GI___pthread_mutex_lock()
  UpgradeStatus: Upgraded to trusty on 2014-01-30 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer1.0/+bug/1274548/+subscriptions

-- 
Mailing list: https://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 1029289] Re: Need to authorize my google account each time I boot the computer

2014-09-29 Thread Jean-Francois Moy
I can confirm that I am still facing the same issue. Michael I will try out
your patch.

On Sat, Sep 27, 2014 at 10:52 AM, Michael Blennerhassett 
1029...@bugs.launchpad.net wrote:

 This isn't fixed for me on utopic, can anyone else confirm?

 What does fix this for me is the patch I wrote for evolution-data-server
 over at LP: #1373908

 --
 You received this bug notification because you are a member of WebApps
 Team, which is subscribed to the bug report.
 https://bugs.launchpad.net/bugs/1029289

 Title:
   Need to authorize my google account each time I boot the computer

 Status in Online Accounts: Account plugins:
   In Progress
 Status in Online Accounts: OAuth2 plug-in:
   Unknown
 Status in Online Accounts: Sign-on UI:
   Fix Released
 Status in “account-plugins” package in Ubuntu:
   Fix Released
 Status in “evolution-data-server” package in Ubuntu:
   Fix Released
 Status in “signon-plugin-oauth2” package in Ubuntu:
   Fix Released
 Status in “account-plugins” source package in Quantal:
   Fix Released
 Status in “signon-plugin-oauth2” source package in Quantal:
   Fix Released
 Status in “account-plugins” source package in Trusty:
   Fix Released
 Status in “evolution-data-server” source package in Trusty:
   Fix Committed
 Status in “signon-plugin-oauth2” source package in Trusty:
   Fix Released

 Bug description:
   [Impact] Google calendar integration is broken, and users are
   requested to re-enter their Google password everytime they log in, or
   everytime they enable/disable their Google account from the System
   Settings.

   [Test Case] Disable/re-enable your Google account. When affected by
   this bug, a notification will appear and you'll be asked to enter your
   Google password in the Online Accounts panel in System Settings.

   [Regression Potential] Minimal: the fix is a backport of a patch from
   the evolution-data-server code which is already in 14.10, and which
   only touches the calendar code (which is currently broken).


   Old description
   ===

   [Test Case] Sometimes after one day, sometimes after one week, the
   system indicator will turn red and the Google account will be marked
   as needing reauthentication. Time can vary, but any period shorter
   than one month is a symptom of the bug.

   [Regression Potential] Minimal: the change to the Google plugin (in
   account-plugins) simply changes the authentication method, in a way
   that is well-documented. The change in signon-plugin-oauth2 affects
   only those accounts/providers which use the OAuth refresh tokens --
   which is only Google, at the moment -- and in a way that can't
   possibly break any existing functionality; if the new code had some
   mistake, the refresh token would be unusable and the system would
   automatically fall back to requesting a new access token (which is
   exactly what happens now, with this bug).

   I'll try to find why the account-plugins package was not uploaded;
   indeed, both are required in order to fix this bug.

 To manage notifications about this bug go to:
 https://bugs.launchpad.net/account-plugins/+bug/1029289/+subscriptions



-- 
Jean-Francois Moy
Software Engineer - Canonical Ltd.

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

Title:
  Need to authorize my google account each time I boot the computer

Status in Online Accounts: Account plugins:
  In Progress
Status in Online Accounts: OAuth2 plug-in:
  Unknown
Status in Online Accounts: Sign-on UI:
  Fix Released
Status in “account-plugins” package in Ubuntu:
  Fix Released
Status in “evolution-data-server” package in Ubuntu:
  Fix Released
Status in “signon-plugin-oauth2” package in Ubuntu:
  Fix Released
Status in “account-plugins” source package in Quantal:
  Fix Released
Status in “signon-plugin-oauth2” source package in Quantal:
  Fix Released
Status in “account-plugins” source package in Trusty:
  Fix Released
Status in “evolution-data-server” source package in Trusty:
  Fix Committed
Status in “signon-plugin-oauth2” source package in Trusty:
  Fix Released

Bug description:
  [Impact] Google calendar integration is broken, and users are
  requested to re-enter their Google password everytime they log in, or
  everytime they enable/disable their Google account from the System
  Settings.

  [Test Case] Disable/re-enable your Google account. When affected by
  this bug, a notification will appear and you'll be asked to enter your
  Google password in the Online Accounts panel in System Settings.

  [Regression Potential] Minimal: the fix is a backport of a patch from
  the evolution-data-server code which is already in 14.10, and which
  only touches the calendar code (which is currently broken).


  Old description
  ===

  [Test Case] Sometimes after one day, sometimes after one week, the
  system indicator will turn red and the Google 

Re: [Touch-packages] [Bug 1046805] Re: X IO Error : Using g_idle_add_full inside ibus_im_context_focus_in instead of gdk_threads_add_idle_full

2014-09-29 Thread Yehouda
  
  Yehouda, has this bug been fixed for you?
  

I don't know.

It doesn't bother us, because we don't use this input method, but it
hits users of our software. We tell them to set GTK_IM_MODULE to
something so it doesn't use ibus, that works around it and they don't
mind doing it. So the truth is that it is not a show stopper for us.

Since it was fixed in the project itself more than two years ago, we
kind of forgot about it. Our users probably have it somewhare in their
initialization files and forgot about it too.

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

Title:
  X IO Error : Using g_idle_add_full inside ibus_im_context_focus_in
  instead of gdk_threads_add_idle_full

Status in “ibus” package in Ubuntu:
  Confirmed

Bug description:
  This is a bug in ibus-gtk2 version 1.4, libray /usr/lib/x86_64-linux-
  gnu/gtk-2.0/2.10.0/immodules/im-ibus.so is in Ubuntu 12.04.

  It causes random X IO errors , because it is a multithreading bug.

  I reported it already to the ibus project at
   
http://code.google.com/p/ibus/issues/detail?id=1505thanks=1505ts=1346933625, 
but it is a show stopper for us so we want a fast fix.

  ibus_im_context_focus_in in ibus/client/gtk2/ibusimcontext.c uses
  g_idle_add_full with a callback that call GDK functions, so it call
  them without the GDK lock.

  It should use instead gdk_threads_add_idle_full to make the callback
  run with a lock.

  Got broken by this commit
  
https://github.com/ibus/ibus/commit/279ee5d5b3697b427cc22cd99a55f4e611318e25#client/gtk2/ibusimcontext.c

  Broken in ibus-gtk2 1.4, still ok in 1.3.

  
  backtrace 

  Breakpoint 1, 0x004b6094 in ?? ()
  (gdb) where
  #0  0x004b6094 in ?? ()
  #1  0x7569841e in _XIOError ()
 from /usr/lib/x86_64-linux-gnu/libX11.so.6
  #2  0x7569638b in _XReply () from 
/usr/lib/x86_64-linux-gnu/libX11.so.6
  #3  0x75693407 in XTranslateCoordinates ()
 from /usr/lib/x86_64-linux-gnu/libX11.so.6
  #4  0x75c02b2d in ?? ()
 from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
  #5  0x7fffd8968caf in ?? ()
 from /usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules/im-ibus.so
  #6  0x76910d53 in g_main_context_dispatch ()
 from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #7  0x769110a0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #8  0x7691149a in g_main_loop_run ()
 from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #9  0x004503ca in ?? ()
  #10 0x in ?? ()

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

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


[Touch-packages] [Bug 1366825] Re: camera_app.tests.test_zoom.TestCameraZoom.test_slider_zoom_in fails due to zoom slider not being visible

2014-09-29 Thread Florian Boucault
** Also affects: camera-app
   Importance: Undecided
   Status: New

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

Title:
  camera_app.tests.test_zoom.TestCameraZoom.test_slider_zoom_in fails
  due to zoom slider not being visible

Status in Camera App:
  New
Status in “camera-app” package in Ubuntu:
  New

Bug description:
  the method activate_zoom() fails to invoke zoom slider with a 10pixel
  pinch.

  solution: increase the initial pinch to 15pixels.

  
http://ci.ubuntu.com/smokeng/utopic/touch/mako/222:20140904.1:20140903.1/10220/camera_app/1631398/

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: camera-app (not installed)
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: armhf
  Date: Mon Sep  8 19:04:52 2014
  InstallationDate: Installed on 2014-09-08 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140908-020205)
  SourcePackage: camera-app
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1369573] Re: camera_app.tests.test_flash.TestCameraFlash.test_cycle_video_flash fails sometimes due to wrong geometry of the flash icon

2014-09-29 Thread Florian Boucault
** Also affects: camera-app
   Importance: Undecided
   Status: New

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

Title:
  camera_app.tests.test_flash.TestCameraFlash.test_cycle_video_flash
  fails sometimes due to wrong geometry of the flash icon

Status in Camera App:
  New
Status in “camera-app” package in Ubuntu:
  New

Bug description:
  test failure:
  camera_app.tests.test_flash.TestCameraFlash.test_cycle_video_flash

  
  The above test fails because the settingsProperty property is not reliable 
enough. Sometimes the test ends up clicking 'location' icon which results in 
the test failure. We need to find a better way to select this icon.

  test-log: {{{
  13:17:04.391 WARNING testcase:115 - No tracing available - install the 
python-autopilot-trace package!
  13:17:04.406 WARNING testcase:162 - Process manager backend unavailable, 
application snapshot support disabled.
  13:17:05.915 INFO _launcher:280 - Attempting to launch click application 
'(default)' from click package  'com.ubuntu.camera' and URIs ''
  13:17:06.878 INFO _launcher:120 - Attempting to launch application 
'com.ubuntu.camera_camera_3.0.0.389' with URIs '' via upstart-app-launch
  13:17:11.270 DEBUG _common:45 - Moving to object's globalRect coordinates.
  13:17:11.271 DEBUG _uinput:470 - Tapping at: 45,45
  13:17:11.419 INFO logging:45 - Panel: Open the panel if it's not already 
opened. Arguments (). Keyword arguments: {}.
  13:17:11.769 DEBUG _uinput:541 - Dragging from 384,1279 to 384,1118
  13:17:14.027 DEBUG _common:45 - Moving to object's globalRect coordinates.
  13:17:14.028 DEBUG _uinput:470 - Tapping at: 123,1163
  13:17:14.726 DEBUG dbus:352 - Selecting objects of type OptionValueButton 
with attributes: {}
  13:17:14.926 DEBUG _common:45 - Moving to object's globalRect coordinates.
  13:17:14.927 DEBUG _uinput:470 - Tapping at: 186,947
  }}}

  Traceback (most recent call last):
File /home/phablet/autopilot/camera_app/tests/test_flash.py, line 86, in 
test_cycle_video_flash
  self.assertThat(flash_button.iconName, Equals(torch-on))
File /usr/lib/python3/dist-packages/testtools/testcase.py, line 423, in 
assertThat
  raise mismatch_error
  testtools.matchers._impl.MismatchError: 'torch-on' != 'torch-off'

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: camera-app 3.0.0+14.10.20140908-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
  Uname: Linux 3.16.0-14-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Sep 15 19:00:25 2014
  InstallationDate: Installed on 2014-06-14 (92 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140610.1)
  SourcePackage: camera-app
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1371245] Re: trust-store dialog (location) not asked on the first boot after a clean flash

2014-09-29 Thread Florian Boucault
** Also affects: camera-app
   Importance: Undecided
   Status: New

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

Title:
  trust-store dialog (location) not asked on the first boot after a
  clean flash

Status in Camera App:
  New
Status in “camera-app” package in Ubuntu:
  New

Bug description:
  current build number: 48
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2014-09-18 18:32:37
  version version: 48
  version ubuntu: 20140918.1
  version device: 20140917-19d7408
  version custom: 1410739265

  Flashed with: ubuntu-device-flash --channel=ubuntu-touch/ubuntu-
  rtm/14.09-proposed --bootstrap --developer-mode --password=1234

  After first boot (wizard and etc), try opening the camera-app and
  you'll see that the trust-store dialog will not show up to the screen
  and the user is able to use the app.

  Dialog shows up after rebooting it though, so it seems to be a first-
  boot specific issue.

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

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


[Touch-packages] [Bug 1375167] Re: tracker-extract crashed with SIGABRT in g_malloc0()

2014-09-29 Thread Apport retracing service
*** This bug is a duplicate of bug 1364780 ***
https://bugs.launchpad.net/bugs/1364780

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1364780, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: CoreDump.gz
   
https://bugs.launchpad.net/bugs/1375167/+attachment/4218930/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1375167/+attachment/4218932/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1375167/+attachment/4218934/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1375167/+attachment/4218935/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1375167/+attachment/4218936/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1375167/+attachment/4218937/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1375167/+attachment/4218938/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1364780
   tracker-extract crashed with SIGABRT in g_malloc0()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  tracker-extract crashed with SIGABRT in g_malloc0()

Status in “tracker” package in Ubuntu:
  New

Bug description:
  tracker-extract crashed with SIGABRT in g_malloc0()

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: tracker-extract 1.0.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3
  Uname: Linux 3.16.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Mon Sep 29 11:42:43 2014
  ExecutablePath: /usr/lib/tracker/tracker-extract
  InstallationDate: Installed on 2014-07-10 (80 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140520)
  ProcCmdline: /usr/lib/tracker/tracker-extract
  Signal: 6
  SourcePackage: tracker
  StacktraceTop:
   g_malloc0 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_slice_free1 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_queue_pop_tail () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: tracker-extract crashed with SIGABRT in g_malloc0()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo

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

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


[Touch-packages] [Bug 1369472] Re: Often hangs for 15 to 30 seconds on start

2014-09-29 Thread Florian Boucault
** Also affects: camera-app
   Importance: Undecided
   Status: New

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

Title:
  Often hangs for 15 to 30 seconds on start

Status in Camera App:
  New
Status in “camera-app” package in Ubuntu:
  New

Bug description:
  Using the rtm-40 image on krillin (but it was already doing it with
  the previous versions of the image), often when running the camera-app
  the image shows for a few seconds, then the view/UI freezes for 15 to
  30 seconds, then it unblocks and work normally...

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

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


[Touch-packages] [Bug 1372650] Re: Camera pictures are black if flash fired

2014-09-29 Thread Florian Boucault
** Also affects: camera-app
   Importance: Undecided
   Status: New

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

Title:
  Camera pictures are black if flash fired

Status in Camera App:
  New
Status in “camera-app” package in Ubuntu:
  New

Bug description:
  Hi, everything is in the title : If there is the flash, the taken
  picture will be black.

  How to reproduce : Take the same photo, twice : one with the Flash,
  the other one without. the one with the flash will be black.

  This seems to be the same bug that happened a few months ago, but I'm
  one a fresh install, and didn't found any open bug regarding this
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: camera-app (not installed)
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: armhf
  Date: Mon Sep 22 23:09:04 2014
  InstallationDate: Installed on 2014-09-16 (6 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140916-020205)
  SourcePackage: camera-app
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1368140] Re: add guide lines overlay option

2014-09-29 Thread Florian Boucault
** Also affects: camera-app
   Importance: Undecided
   Status: New

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

Title:
  add guide lines overlay option

Status in Camera App:
  New
Status in “camera-app” package in Ubuntu:
  New

Bug description:
  Both iOS and Android cameras have an option to overlay 2 evenly-spaced
  vertical and 2 evenly-spaced horizonal white guide lines.

  These are a very useful alignment aid when composing a shot.

  For details: http://en.wikipedia.org/wiki/Rule_of_thirds

  Bonus points if we could have a  Fibonacci spiral option too :-) :
  http://en.wikipedia.org/wiki/Golden_spiral

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

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


[Touch-packages] [Bug 1374521] Re: ifup should specify '-allow=auto' not '-allow=hotplug'

2014-09-29 Thread Martin Pitt
I have some trouble reproducing this. I installed systemd-sysv into a
minimal VM without NetworkManager, and
/etc/network/interfaces.d/eth0.cfg has

  # The primary network interface
  auth eth0
  iface eth0 inet dhcp

Indeed ifquery -l --allow=hotplug doesn't mention any interface, but
eth0 comes up just fine anyway. When I comment out above file, it does
not come up, so that file and ifup is definitively being used here.

But running sudo ifup --verbose --allow=hotplug eth0 manually confirms
that the stanza is being ignored. So the most probable explanation is
that /etc/init.d/networking is being run during boot which takes care of
the auto stanzas? Why isn't that being run for you? Can you please
show systemctl status networking?

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

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

Title:
  ifup should specify '-allow=auto' not '-allow=hotplug'

Status in “systemd” package in Ubuntu:
  Incomplete

Bug description:
  /lib/systemd/system/ifup@.service specifies:

    ExecStart=/sbin/ifup --allow=hotplug %I

  This really needs to be:

    ExecStart=/sbin/ifup --allow=auto %I

  Since otherwise, for systems that don't use network-manager, the
  service will only bring up interfaces which have specified allow-
  hotplug $if in /etc/network/interfaces*.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: systemd 208-8ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3
  Uname: Linux 3.16.0-17-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Sep 26 16:54:12 2014
  InstallationDate: Installed on 2014-04-11 (167 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409)
  SourcePackage: systemd
  UpgradeStatus: Upgraded to utopic on 2014-05-08 (141 days ago)

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

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


[Touch-packages] [Bug 1362176] Re: API key needs to be passed to dash.ubuntu.com service

2014-09-29 Thread Launchpad Bug Tracker
This bug was fixed in the package unity-scope-mediascanner -
0.2+14.10.20140925-0ubuntu1

---
unity-scope-mediascanner (0.2+14.10.20140925-0ubuntu1) utopic; urgency=low

  [ Pawel Stolowski ]
  * Pass API key with dash.ubuntu.com requests. (LP: #1362176)
 -- Ubuntu daily release ps-jenk...@lists.canonical.com   Thu, 25 Sep 2014 
10:32:14 +

** Changed in: unity-scope-mediascanner (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 unity-scope-mediascanner
in Ubuntu.
https://bugs.launchpad.net/bugs/1362176

Title:
  API key needs to be passed to dash.ubuntu.com service

Status in Thumbnail generator for all kinds of files:
  In Progress
Status in Unity Media Scanner Scope:
  In Progress
Status in “unity-scope-mediascanner” package in Ubuntu:
  Fix Released

Bug description:
  API key needs to be passed to dash.ubuntu.com service. It should be
  possible to customize the key via OEM customizations.

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

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


[Touch-packages] [Bug 1370669] Re: Implement top priority features from roadmap

2014-09-29 Thread Florian Boucault
** Changed in: camera-app
   Status: New = Confirmed

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

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

Title:
  Implement top priority features from roadmap

Status in Camera App:
  Confirmed
Status in “camera-app” package in Ubuntu:
  Confirmed

Bug description:
  Color effects
  Display image properties
  Self timer
  Adjust jpeg quality
  Gridlines
  Use SD card storage
  Set video quality

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

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


[Touch-packages] [Bug 1370671] Re: Implement second phase feature priorities from roadmap

2014-09-29 Thread Florian Boucault
** Changed in: camera-app
   Status: New = Confirmed

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

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

Title:
  Implement second phase feature priorities from roadmap

Status in Camera App:
  Confirmed
Status in “camera-app” package in Ubuntu:
  Confirmed

Bug description:
  Manual exposure setting and time
  Scene modes
  White balance
  Face detection (for focus)
  Adjust Picture size (resolution)

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

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


[Touch-packages] [Bug 1368063] Re: The photo captured by Camera app show darkness.

2014-09-29 Thread Florian Boucault
** Changed in: camera-app
   Importance: Undecided = High

** Changed in: camera-app (Ubuntu)
   Importance: Undecided = High

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

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

Title:
  The photo captured by Camera app show darkness.

Status in Camera App:
  New
Status in OEM Priority Project:
  New
Status in “camera-app” package in Ubuntu:
  New

Bug description:
  Install Ubuntu 14.04 and boot into OS. 
  Opened Camera app from dash home.Clicked the roundness button to capture 
photos.
  View the photos in /home/pictures.Found the photos show darkness.

  Steps to Reproduce:
  1.Boot into OS.
  2.Opened Camera app from dash home.
  3.Clicked the roundness button to capture photos.
  4.View the photos in /home/pictures.
  5.Found the photos show darkness.

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

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


[Touch-packages] [Bug 1368063] Re: The photo captured by Camera app show darkness.

2014-09-29 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  The photo captured by Camera app show darkness.

Status in Camera App:
  New
Status in OEM Priority Project:
  New
Status in “camera-app” package in Ubuntu:
  New

Bug description:
  Install Ubuntu 14.04 and boot into OS. 
  Opened Camera app from dash home.Clicked the roundness button to capture 
photos.
  View the photos in /home/pictures.Found the photos show darkness.

  Steps to Reproduce:
  1.Boot into OS.
  2.Opened Camera app from dash home.
  3.Clicked the roundness button to capture photos.
  4.View the photos in /home/pictures.
  5.Found the photos show darkness.

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

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


[Touch-packages] [Bug 1368140] Re: add guide lines overlay option

2014-09-29 Thread Florian Boucault
** Changed in: camera-app
   Status: New = Confirmed

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

** Changed in: camera-app
   Importance: Undecided = High

** Changed in: camera-app (Ubuntu)
   Importance: Undecided = High

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

Title:
  add guide lines overlay option

Status in Camera App:
  Confirmed
Status in “camera-app” package in Ubuntu:
  Confirmed

Bug description:
  Both iOS and Android cameras have an option to overlay 2 evenly-spaced
  vertical and 2 evenly-spaced horizonal white guide lines.

  These are a very useful alignment aid when composing a shot.

  For details: http://en.wikipedia.org/wiki/Rule_of_thirds

  Bonus points if we could have a  Fibonacci spiral option too :-) :
  http://en.wikipedia.org/wiki/Golden_spiral

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

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


[Touch-packages] [Bug 1372650] Re: Camera pictures are black if flash fired

2014-09-29 Thread Florian Boucault
*** This bug is a duplicate of bug 1368063 ***
https://bugs.launchpad.net/bugs/1368063

** This bug has been marked a duplicate of bug 1368063
   The photo captured by Camera app show darkness.

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

Title:
  Camera pictures are black if flash fired

Status in Camera App:
  New
Status in “camera-app” package in Ubuntu:
  New

Bug description:
  Hi, everything is in the title : If there is the flash, the taken
  picture will be black.

  How to reproduce : Take the same photo, twice : one with the Flash,
  the other one without. the one with the flash will be black.

  This seems to be the same bug that happened a few months ago, but I'm
  one a fresh install, and didn't found any open bug regarding this
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: camera-app (not installed)
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: armhf
  Date: Mon Sep 22 23:09:04 2014
  InstallationDate: Installed on 2014-09-16 (6 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140916-020205)
  SourcePackage: camera-app
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1375191] [NEW] utopic: network-manager not started automatically on boot

2014-09-29 Thread Dylan Borg
Public bug reported:

After upgrading to utopic (around the time of when the final beta was
out), network manager caesed to auto start on boot. I can however start
it manually using sudo service network-manager start. When this
happended iI also noticed the automatic addition of 2 mins waiting time
for network interfaces on each boot. Please, can the auto start
behaviour be restored?

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


** Tags: utopic

** Summary changed:

- utopic: network-managaer not started automatically on boot
+ utopic: network-manager not started automatically on boot

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

Title:
  utopic: network-manager not started automatically on boot

Status in “network-manager” package in Ubuntu:
  New

Bug description:
  After upgrading to utopic (around the time of when the final beta was
  out), network manager caesed to auto start on boot. I can however
  start it manually using sudo service network-manager start. When
  this happended iI also noticed the automatic addition of 2 mins
  waiting time for network interfaces on each boot. Please, can the auto
  start behaviour be restored?

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

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


[Touch-packages] [Bug 1332721] Re: Add patch to allow toolbar dragging

2014-09-29 Thread Iain Lane
** Changed in: gtk+2.0 (Ubuntu)
 Assignee: (unassigned) = Iain Lane (laney)

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

Title:
  Add patch to allow toolbar dragging

Status in “gtk+2.0” package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu already has a patch - 062_dnd_menubar.patch - that allows the
  window to be dragged by clicking on empty space in the menubar.

  The attached patch builds on this and allows empty space in the
  toolbar to be also dragged.  It is essentially commit
  7491e9e97aa6b0f9950897c4f1282b470c79d451 that went into gtk+3.0 way
  back in 2010.

  This would make GTK2 themes behave much more like GTK3 themes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1332721/+subscriptions

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


[Touch-packages] [Bug 1374521] Re: ifup should specify '-allow=auto' not '-allow=hotplug'

2014-09-29 Thread James Hunt
$ systemctl status networking

networking.service - LSB: Raise network interfaces.
   Loaded: loaded (/etc/init.d/networking)
  Drop-In: /run/systemd/generator/networking.service.d
   `-50-insserv.conf-$network.conf
   Active: active (exited) since Mon 2014-09-29 09:22:44 UTC; 1min 51s ago
  Process: 332 ExecStart=/etc/init.d/networking start (code=exited, 
status=0/SUCCESS)

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

Title:
  ifup should specify '-allow=auto' not '-allow=hotplug'

Status in “systemd” package in Ubuntu:
  Incomplete

Bug description:
  /lib/systemd/system/ifup@.service specifies:

    ExecStart=/sbin/ifup --allow=hotplug %I

  This really needs to be:

    ExecStart=/sbin/ifup --allow=auto %I

  Since otherwise, for systems that don't use network-manager, the
  service will only bring up interfaces which have specified allow-
  hotplug $if in /etc/network/interfaces*.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: systemd 208-8ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3
  Uname: Linux 3.16.0-17-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Sep 26 16:54:12 2014
  InstallationDate: Installed on 2014-04-11 (167 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409)
  SourcePackage: systemd
  UpgradeStatus: Upgraded to utopic on 2014-05-08 (141 days ago)

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

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


[Touch-packages] [Bug 1341548] Re: Online detection does not work with confined apps on Nexus 4

2014-09-29 Thread Dan Chapman
** Changed in: dekko
Milestone: None = 0.3

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

Title:
  Online detection does not work with confined apps on Nexus 4

Status in dekko:
  In Progress
Status in Network Menu:
  Fix Released
Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
  Fix Released
Status in “connectivity-api” package in Ubuntu:
  Fix Released
Status in “indicator-network” package in Ubuntu:
  Fix Released
Status in “connectivity-api” package in Ubuntu RTM:
  Fix Released
Status in “indicator-network” package in Ubuntu RTM:
  Fix Released

Bug description:
  Dekko is not detecting if Online correctly. If I look at the server
  logs, I don't see anything in the email server logs for dekko to
  connect. If I look in ~/.cache/upstart/application-click-
  com.ubuntu.developer.dpniel.dekko_dekko_0.2.2.log, I don't see
  anything about connecting. If I click the globe in dekko, I see that
  it is in offline mode and selecting one of the others seems to make no
  difference (I see nothing in the server logs and the upstart logs) and
  the setting doesn't stick (ie, it *always* says 'Offline mode').

  I thought this might be bug #1226844, but if I adjust
  /var/lib/apparmor/profiles/*dekko* to remove 'deny' from in front of
  the NetworkManager and ofono rules and run apparmor_parser -r
  /var/lib/apparmor/profiles/*dekko*, there are no denials but it still
  doesn't detect if I am online or not  when on 3G.

  If I get on wifi instead of 3G, dekko can detect if I am online if I
  apply the apparmor changes I mentioned above (though, there are still
  NetworkManager dbus denials).

  For dekko to work as a confined application (ie, shipped in the Ubuntu
  App Store) it is going to need to operate without these NetworkManager
  and ofono DBus APIs, because they are not allowed to app store apps.

  
  Previous description:
  In addidtion to TLS on port 143, it would be nice to support imaps on port 
993.

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

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


[Touch-packages] [Bug 1367870] Re: Ubuntu 14.04 system with Radeon HD 6330M hangs regularly, especially when using Google Chrome

2014-09-29 Thread Pieroxy
Same problem here. This affect apparently pretty much everyone with open
source amd drivers (I am running x86_64) as far as I can tell. What
details can we help gather to help a resolution on this?

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

Title:
  Ubuntu 14.04 system with Radeon HD 6330M hangs regularly, especially
  when using Google Chrome

Status in “xorg” package in Ubuntu:
  New

Bug description:
  I'm reporting this bug at the request of k...@chromium.org at
  https://code.google.com/p/chromium/issues/detail?id=404357#c34 .
  Please see https://code.google.com/p/chromium/issues/detail?id=404357
  for details.  The appropriate package for this bug might be xserver-
  xorg-video-ati but that's a guess.

  Summary:
  Using Google Chrome 36+ on an ubuntu 14.04 system with  an AMD Radeon HD 
6330M graphics card has been regularly causing system hangs.  These appear to 
be particularly likely when playing Flash-based games such as those on 
Facebook.  Scroll up and down using the vertical scrollbar or the mousewheel 
and chrome will segfault.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: i386
  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: Wed Sep 10 19:29:10 2014
  DistUpgraded: 2014-07-06 18:19:11,036 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Robson LE [Radeon HD 6330M] 
[1002:68e5] (prog-if 00 [VGA controller])
 Subsystem: Tul Corporation / PowerColor Cedar [Radeon HD 5450] [148c:5450]
  InstallationDate: Installed on 2013-10-19 (326 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release i386 
(20130213)
  MachineType: MEDIONPC MS-7366
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic 
root=UUID=57c8f83f-22f9-4998-9943-259a1df235a0 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2014-07-06 (66 days ago)
  XorgConf:
   Section Module
Loadglx
   EndSection
  dmi.bios.date: 01/08/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A7366NM7.20E
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7366
  dmi.board.vendor: MEDIONPC
  dmi.board.version: 2.2
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  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:bvnAmericanMegatrendsInc.:bvrA7366NM7.20E:bd01/08/2008:svnMEDIONPC:pnMS-7366:pvr2.2:rvnMEDIONPC:rnMS-7366:rvr2.2:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: MS-7366
  dmi.product.version: 2.2
  dmi.sys.vendor: MEDIONPC
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  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.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Wed Sep 10 19:00:35 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2.1
  xserver.video_driver: radeon

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

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


[Touch-packages] [Bug 1374419] Re: Some APs show twice, should be merged

2014-09-29 Thread Matthew Paul Thomas
There might be multiple bugs here.

The scan list shows COGUEST twice, but it is correctly shown only once
in the screenshots. Meanwhile, the scan list shows Canonical-2.4GHz-g
four times, but it is shown twice in the screenshots -- not once, but
not four times either.

I think that problem might be that the list is showing the currently-
connected network first, and then listing all available networks,
instead of listing all *other* available networks. That is, it forgets
to exclude the current network from the second part of the list.

However, none of that would explain why Instant Staff shows up only
once in the scan list but ends up with two items in the screenshots.

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

Title:
  Some APs show twice, should be merged

Status in “indicator-network” package in Ubuntu:
  New
Status in “ubuntu-system-settings” package in Ubuntu:
  New

Bug description:
  Some access points in indicator-network show twice, when they should
  be merged into a single entry given that security and SSID are the
  same.

  See attached screenshot.

  For example, Instant Staff should only show once, not greyed out.
  There are not multiple APs with different security settings to justify
  two different entries.

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

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


[Touch-packages] [Bug 1359249] Re: Launching PAVUControl works from Xubuntu, but not from Xfce

2014-09-29 Thread Monsta
I doubt the maintainers would accept gnome-control-center in Xubuntu
just for that... We can suggest making the command configurable though.

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

Title:
  Launching PAVUControl works from Xubuntu, but not from Xfce

Status in “indicator-sound” package in Ubuntu:
  Confirmed

Bug description:
  In Xubuntu 14.04 when clicking the sound indicator and choosing Sound
  Settings Pavucontrol is launched, but it does not get launched in the
  same scenario when the session Xfce is launched instead, with the
  same settings. In fact I installed the xfce4 package on top of
  Xubuntu's and launched it. Both xsession files list the same thing to
  start it, so is indicator only choosing to work on whitelisted
  sessions?

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

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


[Touch-packages] [Bug 1375194] [NEW] lightdm session constantly switches screen appearance

2014-09-29 Thread Simon Lambourn
Public bug reported:

After installing regular software updates on 23 Sept, my screen session
has become almost unusable.  The screen appearance (font, button
style, window menu bar location) alternates about twice a second between
my usual settings and what I guess are the default un-decorated
settings.   This means that text, buttons, and input areas are often
moving around on the screen as the font size changes or the window menu
bar comes and goes.

In addition, keyboard input characters take a variable time to appear (up to a 
few seconds?) and can appear in the wrong order.
CPU utilisation is much higher when I am logged on.   See TOP output below.   I 
get the same problems with any one of Chromium, Firefox, Thunderbird, Ubuntu 
Software Centre, BASH terminal window.

When I first sign on, I get a message system software problem detected
in a panel by itself, before the desktop is displayed, and again after
the desktop is displayed.  This is connected with the bug, but I can't
find out the details of the error.   I have selected report the
problem repeatedly.

The software installed on 23 Sept included Dbus , libdbus-1-3,  and
dbus-x11 versions 1.6.18-0ubuntu4.2.  I tried downgrading these 3 to
-0ubuntu4 but the problem remained after a reboot.   There were about
20-30 packages updated at the same time, including linux-image, but I
can't spot which might be causing the problem.   I'm using a clean
install of ubuntu 14.04 but with my /home directory from an older ubuntu
installation.


TOP output:
24974 simon 20   0 2357692 181696  65696 R  27.6  4.5   2:34.62 software-c+ 
 2253 root  20   0  279028  58104  19416 S  26.6  1.4   3:19.18 Xorg
11096 simon 20   0 1391072 186192  81872 R  22.9  4.6   5:02.98 chromium-b+ 
 3899 simon 20   0  719408  32324  17924 R  19.9  0.8   2:55.82 hud-service 
17259 simon 20   0 1036360 203656  48764 R  17.9  5.0   2:47.82 thunderbird 
 4291 simon 20   0 1591956 113836  41064 S  11.6  2.8   1:20.75 compiz  
 5857 simon 20   0  860872  76324  14440 S   5.3  1.9   1:09.93 gnome-term+ 
 3915 simon 20   0  590728  71048  10796 S   2.7  1.8   0:41.92 ibus-ui-gt+ 
 3918 simon 20   0  769636  73648  11544 S   2.7  1.8   0:42.82 unity-pane+ 
 4402 simon 20   0  511960  71072  12024 S   2.7  1.8   0:41.36 nm-applet   
 7212 simon 20   0  847244  67792  12680 S   2.7  1.7   0:37.13 update-not+ 
 3865 simon 20   0  666200  67632   7956 S   2.3  1.7   0:37.61 bamfdaemon  
 3911 simon 20   0  906492  68264   7816 S   2.3  1.7   0:38.02 gnome-sess+ 
 4130 simon 20   0  776980  67892   8080 S   2.3  1.7   0:36.34 indicator-+ 
 4146 simon 20   0  499124  66596   8156 S   2.3  1.6   0:35.04 indicator-+ 
 4410 simon 20   0  405976  73952   9800 S   2.3  1.8   0:34.70 smart-noti+ 
 4194 simon 20   0  391836  65148   7236 S   2.0  1.6   0:35.79 notify-osd

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
Uname: Linux 3.13.0-36-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.4
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Mon Sep 29 10:06:59 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:2127]
Lsusb:
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic 
root=/dev/mapper/vg1-rootfs ro nodmraid nomdmonddf nomdmonisw
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/02/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0507
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M3N78-VM
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0507:bd07/02/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N78-VM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System 

[Touch-packages] [Bug 1375195] [NEW] webapp-container fails to inhibit screen blanking

2014-09-29 Thread Olivier Tilloy
Public bug reported:

When watching a video in the youtube webapp, the screen eventually
blanks while the video is playing. I’m seeing this in the app’s log:

[0929/113347:ERROR:logging.h(739)] Failed to call method: 
com.canonical.Unity.Screen.keepDisplayOn: object_path= 
/com/canonical/Unity/Screen: org.freedesktop.DBus.Error.AccessDenied: An 
AppArmor policy prevents this sender from sending this message to this 
recipient, 0 matched rules; type=method_call, sender=:1.110 (uid=32011 
pid=11942 comm=webapp-container --webappUrlPatterns=https?://*.yo) 
interface=com.canonical.Unity.Screen member=keepDisplayOn error 
name=(unset) requested_reply=0 destination=com.canonical.Unity.Screen 
(uid=0 pid=2166 comm=unity-system-compositor --disable-overlays=false -)
[0929/113347:ERROR:oxide_power_save_blocker.cc(109)] Failed to inhibit screen 
blanking

Playing the same video in the webbrowser app does prevent the screen
from blanking.

** Affects: webapps-touch
 Importance: Undecided
 Status: New

** Affects: apparmor-easyprof-ubuntu (Ubuntu)
 Importance: Undecided
 Status: Confirmed

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

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

Title:
  webapp-container fails to inhibit screen blanking

Status in Webapps for Ubuntu Touch:
  New
Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
  Confirmed

Bug description:
  When watching a video in the youtube webapp, the screen eventually
  blanks while the video is playing. I’m seeing this in the app’s log:

  [0929/113347:ERROR:logging.h(739)] Failed to call method: 
com.canonical.Unity.Screen.keepDisplayOn: object_path= 
/com/canonical/Unity/Screen: org.freedesktop.DBus.Error.AccessDenied: An 
AppArmor policy prevents this sender from sending this message to this 
recipient, 0 matched rules; type=method_call, sender=:1.110 (uid=32011 
pid=11942 comm=webapp-container --webappUrlPatterns=https?://*.yo) 
interface=com.canonical.Unity.Screen member=keepDisplayOn error 
name=(unset) requested_reply=0 destination=com.canonical.Unity.Screen 
(uid=0 pid=2166 comm=unity-system-compositor --disable-overlays=false -)
  [0929/113347:ERROR:oxide_power_save_blocker.cc(109)] Failed to inhibit screen 
blanking

  Playing the same video in the webbrowser app does prevent the screen
  from blanking.

To manage notifications about this bug go to:
https://bugs.launchpad.net/webapps-touch/+bug/1375195/+subscriptions

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


[Touch-packages] [Bug 1375195] Re: webapp-container fails to inhibit screen blanking

2014-09-29 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  webapp-container fails to inhibit screen blanking

Status in Webapps for Ubuntu Touch:
  New
Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
  Confirmed

Bug description:
  When watching a video in the youtube webapp, the screen eventually
  blanks while the video is playing. I’m seeing this in the app’s log:

  [0929/113347:ERROR:logging.h(739)] Failed to call method: 
com.canonical.Unity.Screen.keepDisplayOn: object_path= 
/com/canonical/Unity/Screen: org.freedesktop.DBus.Error.AccessDenied: An 
AppArmor policy prevents this sender from sending this message to this 
recipient, 0 matched rules; type=method_call, sender=:1.110 (uid=32011 
pid=11942 comm=webapp-container --webappUrlPatterns=https?://*.yo) 
interface=com.canonical.Unity.Screen member=keepDisplayOn error 
name=(unset) requested_reply=0 destination=com.canonical.Unity.Screen 
(uid=0 pid=2166 comm=unity-system-compositor --disable-overlays=false -)
  [0929/113347:ERROR:oxide_power_save_blocker.cc(109)] Failed to inhibit screen 
blanking

  Playing the same video in the webbrowser app does prevent the screen
  from blanking.

To manage notifications about this bug go to:
https://bugs.launchpad.net/webapps-touch/+bug/1375195/+subscriptions

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


[Touch-packages] [Bug 1368680] Re: [Dash] pagination graphic should remain static when swiping between favourites.

2014-09-29 Thread James Mulholland
** Description changed:

  Pagination graphic should remain fixed in place when swiping between 
favourites contained within the dash.
  'Dot' used to communicate which favourite is currently being viewed should be 
more visible (switch colour from Dark Grey to Orange colour used for 
highlights, etc):
  
- See here for more info on dash pagination  states:
- 
https://sites.google.com/a/canonical.com/unity-8-dash-rtm-1/home/dash-pagination
+ See here for more info on dash pagination (page 10):
+ 
https://docs.google.com/a/canonical.com/document/d/1LsjdqKDVcFN8Zxb_Oe-Zk1X_DiqviXr8D7-ELt2LEFI/edit?usp=sharing
  
  
  UX Testing Report finding  recommendation:
  
  No incentive to discover scopes beyond the apps scope.  Lack of strong
  visual cues to hint swiping from the apps scope to discover more scopes
  on the right.
  
  In the SURU divider pagination pattern (as currently used by the Dash),
  change the selected colour from orange to white.
  
  When the Scopes slide, the SURU divider portion of the screen should
  not slide (it should remain static).  The state of the 'dot' pagination
  pattern should of course change. Keeping the SURU divider static should
  make the change to the pagination pattern more noticeable.

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

Title:
  [Dash] pagination graphic should remain static when swiping between
  favourites.

Status in Ubuntu UX bugs:
  Triaged
Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  Pagination graphic should remain fixed in place when swiping between 
favourites contained within the dash.
  'Dot' used to communicate which favourite is currently being viewed should be 
more visible (switch colour from Dark Grey to Orange colour used for 
highlights, etc):

  See here for more info on dash pagination (page 10):
  
https://docs.google.com/a/canonical.com/document/d/1LsjdqKDVcFN8Zxb_Oe-Zk1X_DiqviXr8D7-ELt2LEFI/edit?usp=sharing

  
  UX Testing Report finding  recommendation:

  No incentive to discover scopes beyond the apps scope.  Lack of
  strong visual cues to hint swiping from the apps scope to discover
  more scopes on the right.

  In the SURU divider pagination pattern (as currently used by the
  Dash), change the selected colour from orange to white.

  When the Scopes slide, the SURU divider portion of the screen should
  not slide (it should remain static).  The state of the 'dot'
  pagination pattern should of course change. Keeping the SURU divider
  static should make the change to the pagination pattern more
  noticeable.

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

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


[Touch-packages] [Bug 1375195] Re: webapp-container fails to inhibit screen blanking

2014-09-29 Thread Tom Haddon
Following syslog entry confirms:

Sep 29 11:02:50 ubuntu-phablet dbus[745]: apparmor=DENIED
operation=dbus_method_call  bus=system
path=/com/canonical/Unity/Screen
interface=com.canonical.Unity.Screen member=keepDisplayOn
mask=send name=com.canonical.Unity.Screen pid=19918
profile=com.popey.youtube_youtube_0.3 peer_pid=1568
peer_profile=unconfined

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

Title:
  webapp-container fails to inhibit screen blanking

Status in Webapps for Ubuntu Touch:
  New
Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
  Confirmed

Bug description:
  When watching a video in the youtube webapp, the screen eventually
  blanks while the video is playing. I’m seeing this in the app’s log:

  [0929/113347:ERROR:logging.h(739)] Failed to call method: 
com.canonical.Unity.Screen.keepDisplayOn: object_path= 
/com/canonical/Unity/Screen: org.freedesktop.DBus.Error.AccessDenied: An 
AppArmor policy prevents this sender from sending this message to this 
recipient, 0 matched rules; type=method_call, sender=:1.110 (uid=32011 
pid=11942 comm=webapp-container --webappUrlPatterns=https?://*.yo) 
interface=com.canonical.Unity.Screen member=keepDisplayOn error 
name=(unset) requested_reply=0 destination=com.canonical.Unity.Screen 
(uid=0 pid=2166 comm=unity-system-compositor --disable-overlays=false -)
  [0929/113347:ERROR:oxide_power_save_blocker.cc(109)] Failed to inhibit screen 
blanking

  Playing the same video in the webbrowser app does prevent the screen
  from blanking.

To manage notifications about this bug go to:
https://bugs.launchpad.net/webapps-touch/+bug/1375195/+subscriptions

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


[Touch-packages] [Bug 1373225] Re: Unity Control Center icons in the dash don't point to the right section in the Control Center

2014-09-29 Thread Alberto Salvia Novella
@ Gunnar Hjalmarsson:

If I uninstall the gnome-control-center package, then all the broken
icons go away.

** No longer affects: unity

** No longer affects: unity (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/1373225

Title:
  Unity Control Center icons in the dash don't point to the right
  section in the Control Center

Status in One Hundred Papercuts:
  Triaged
Status in “unity-control-center” package in Ubuntu:
  Triaged

Bug description:
  
  HOW TO REPRODUCE
  

  - In the dash, open one of these applications: Notifications, Online
  Accounts, Privacy, Security, Sharing.

  
  **
  EXPECTED BEHAVIOUR
  **

  - Going to the right section in the Control Center.

  
  **
  REAL BEHAVIOUR
  **

  - You go to the main page in the Control Center.

  
  
  RELEVANT DETAILS
  

  - Old icons are still there, and should be removed too.

  **
  TECHNICAL INFO
  **

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity-control-center 14.10.0+14.10.20140922-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3
  Uname: Linux 3.16.0-17-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Sep 24 06:43:11 2014
  InstallationDate: Installed on 2013-05-21 (490 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  SourcePackage: unity-control-center
  UpgradeStatus: Upgraded to utopic on 2014-09-24 (0 days ago)
  usr_lib_unity-control-center:
   activity-log-manager 0.9.7-0ubuntu15
   deja-dup 32.0-0ubuntu1

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

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


[Touch-packages] [Bug 1371651] Re: Daily does not boot into graphical interface after installation

2014-09-29 Thread Andy Whitcroft
@Cee Gee -- I believe your issue is not the same because lightdm has
started, that sounds more like a brightness issue and I would recommend
filing a new bug for that.  Feel free to add that bug number here.

** Changed in: linux (Ubuntu)
   Status: Triaged = Invalid

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

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

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

Title:
  Daily does not boot into graphical interface after installation

Status in Light Display Manager:
  Invalid
Status in “lightdm” package in Ubuntu:
  Invalid
Status in “linux” package in Ubuntu:
  Invalid
Status in “plymouth” package in Ubuntu:
  In Progress

Bug description:
  used the daily iso 2015-09-19 i386
  ran installation on virtualbox 4.3.16

  after installation, the system won't boot into the graphical
  interface. instead, switching to vt1 and back to vt7 reveals the
  attached errors.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2
  Uname: Linux 3.16.0-16-generic i686
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: i386
  Date: Fri Sep 19 17:09:17 2014
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash -- debian-installer/language=de 
keyboard-configuration/layoutcode?=de
  InstallationDate: Installed on 2014-09-19 (0 days ago)
  InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha i386 (20140919)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1371048] Re: phone believed to enforce undocumented password policy

2014-09-29 Thread Oliver Grawert
** Also affects: android-tools (Ubuntu RTM)
   Importance: Undecided
   Status: New

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

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

** 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 android-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1371048

Title:
  phone believed to enforce undocumented password policy

Status in “android-tools” package in Ubuntu:
  Fix Released
Status in “android-tools” package in Ubuntu RTM:
  In Progress

Bug description:
  Per conversation on IRC with ogra.

  The phone will reject passwords which match the username.

  Fine and dandy, but isn't password security the responsibilty of other
  entities and code. Rejecting just this insecure password, hard-coded,
  seems a bit odd.

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

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


[Touch-packages] [Bug 1368778] Re: [Launcher] Consider removing launcher hide time out

2014-09-29 Thread Vesa Rautiainen
** Changed in: ubuntu-ux
   Importance: Low = Medium

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

Title:
  [Launcher] Consider removing launcher hide time out

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

Bug description:
  In user testing some users were confused when launcher kept hiding
  when they were trying to look at the items to find some specific
  application. They even tried to keep the launcher open with one finger
  while scrolling with another.

  As far as I remember the Launcher is the only place where we use hide
  time out (inconsistent). I agree that it makes sense to have a time
  out when  desktop in question mouse is used as a pointer device. But
  on the phone and other touch devices where launcher is revealed with
  edge gesture I find it irritating and doesn't really serve any
  purpose.

  I would consider removing the time out from touch devices.

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

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


[Touch-packages] [Bug 1223050] Re: [PageStack] Calling positionViewAtIndex cause the page header misbehave

2014-09-29 Thread Tim Peeters
** Changed in: ubuntu-ui-toolkit
   Importance: Critical = High

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

Title:
  [PageStack] Calling positionViewAtIndex cause the page header
  misbehave

Status in Address Book App:
  Confirmed
Status in Music application for Ubuntu devices:
  New
Status in Ubuntu UI Toolkit:
  Confirmed
Status in “address-book-app” package in Ubuntu:
  Confirmed
Status in “ubuntu-ui-toolkit” package in Ubuntu:
  Confirmed
Status in “address-book-app” source package in Trusty:
  Confirmed
Status in “ubuntu-ui-toolkit” source package in Trusty:
  Confirmed

Bug description:
  Using a ListView inside of a PageStack causes the ListView header
  misbehave after calling positionViewAtIndex:

  How to reproduce (using the example attached):

  1- run: qmlscene main.qml
  2- click in the button click me
  3- scroll the list 
  4- click in the button click me again

  Expected behavior:
  The section header should be fully visible at the top

  Current behavior:
  The page header  overlaps the listview and the section header

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

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


[Touch-packages] [Bug 1370146] Re: Adjust header behaviour UI in multi select mode

2014-09-29 Thread Tim Peeters
** Changed in: ubuntu-ui-toolkit
   Status: Confirmed = In Progress

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

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) = Tim Peeters (tpeeters)

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

Title:
  Adjust header behaviour  UI in multi select mode

Status in Address Book App:
  Confirmed
Status in Dialer app for Ubuntu Touch:
  Confirmed
Status in Messaging App:
  Confirmed
Status in Clock application for Ubuntu devices:
  Fix Released
Status in Ubuntu UI Toolkit:
  In Progress
Status in Ubuntu UX bugs:
  Fix Released
Status in “address-book-app” package in Ubuntu:
  Confirmed
Status in “dialer-app” package in Ubuntu:
  Confirmed
Status in “messaging-app” package in Ubuntu:
  Confirmed
Status in “ubuntu-ui-toolkit” package in Ubuntu:
  In Progress

Bug description:
  Steps to reproduce:

  1. Open Messaging app (or Address Book app, Phone app), make sure you have a 
list in your messages view
  2. Long press on any of the list items

  Actual Result:
  3. Header is changing and shows an X button on the left hand side and two 
action buttons on the right hand side. Selection checkboxes appear from the 
left hand side.

  Expected result - desired solution:
  - The header should display a BACK button instead of the X on the left hand 
side, same as we have in all other headers
  - Remove the change in the background colour when a list item is selected, 
change in the colour of the checkbox is enough
  - Add labels for all visible actions in this mode in the header, except for 
'BACK'
  - Tapping on the BACK in this mode, cancels the multi-select mode and does 
NOT navigate back to the previous view
  - There is no title in this header

  Please see attached wireframe for reference. This change applies
  across all apps which use a multi select in their list views.

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

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


[Touch-packages] [Bug 1347147] Re: krb5 database operations enter infinite loop

2014-09-29 Thread Iain Lane
Thanks Sam, I've uploaded krb5.

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

** Changed in: krb5 (Ubuntu Trusty)
 Assignee: (unassigned) = Sam Hartman (hartmans)

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

Title:
  krb5 database operations enter infinite loop

Status in The GNU Compiler Collection:
  Fix Released
Status in Network Authentication System:
  Unknown
Status in “gcc-4.8” package in Ubuntu:
  Fix Released
Status in “gcc-4.9” package in Ubuntu:
  Fix Released
Status in “krb5” package in Ubuntu:
  Fix Released
Status in “gcc-4.8” source package in Trusty:
  Confirmed
Status in “krb5” source package in Trusty:
  In Progress

Bug description:
  [Impact]

  On krb5 KDC databases with more than a few hundred principals,
  operations can enter an infinite loop in the database library.  This
  affects both read and write operations.  If operators are fortunate,
  they will encounter this bug while testing a migration.  If they are
  not so fortunate, they will encounter this bug in a production KDC
  when the number of principals crosses the threshold where this bug
  manifests, resulting in a service outage and possible database
  corruption.  Probably the only way to restore service in that
  situation is to install a patched KDC or to downgrade to an unaffected
  version.

  Both Trusty and Utopic amd64 have been verified to have this issue.

  One concrete reported example is an invocation of kdb5_util load (as
  part of a slave KDC propagation) spinning:

  http://mailman.mit.edu/pipermail/kerberos/2014-July/020007.html

  Additional failure modes are likely

  A branch is linked including the upstream work around for this bug,
  along with two other patches to bugs already nominated for trusty
  applied to the krb5 in trusty.

  For utopic, the simplest fix is to rebuild krb5 with the compiler
  currently in utopic.  An alternative is to request that the Debian
  maintainers (both monitoring this bug for such a request) upload the
  upstream work around to Debian and sync that.  You could do an ubuntu-
  specific upload but it seems undesirable to introduce a change between
  Ubuntu and Debian when all the right parties are happy to avoid it.

  The upstream patch works around a compiler optimizer bug in the
  gcc-4.8 series, which incorrectly deduces that a strict aliasing
  violation has occurred and miscompiles part of the bundled libdb2
  library that the KDC database back end depends upon.  The
  miscompilation causes a data structure to contain an inappropriate
  cycle, which leads to an infinite loop when the structure is
  traversed.

  [Test Case]

  apt-get install krb5-kdc krb5-admin-server
  kdb5_util -W -r T create -s
  awk 'BEGIN{ for (i = 0; i  1024; i++) { printf(ank -randkey a%06d\n, i) } 
}' /dev/null | kadmin.local -r T

  (Enter any password for the master key when requested.)

  On platforms with this issue, kadmin.local spins consuming 100% CPU
  after a few hundred principals have been created.  (This is a000762
  on two examples.)

  To clean up,

  rm /etc/krb5kdc/principal*

  or

  krb5kdc -r T destroy

  but the latter can possibly enter the same infinite loop.

  [Regression Potential]

  Negligible.

  It is theoretically possible that our upstream workaround, which
  involves using TAILQ macros instead of CIRCLEQ macros in the bundled
  libdb2 that backs the KDC database, will have some as-yet undiscovered
  bugs or compiler interactions with consequences worse than this
  current issue.  I think this is rather unlikely.

  The patched libdb2 passes both the extensive libdb2 test suite and the
  rest of the krb5 test suite.  Prior to patching, compiling krb5 with
  an affected gcc would cause the krb5 test suite to stall when it
  reached the libdb2 test suite.  (The test suite stall is how we became
  aware of the gcc optimizer bug.)

  The BSD TAILQ macros are generally considered to be safer than the
  CIRCLEQ macros, and the various open-source BSD derivatives have made
  the corresponding change to their libdb sources years ago, with no
  reported ill effects that I can see.

  Original report from Ben Kaduk:

  ==

  In some conditions, propagating a kerberos database to a slave KDC server can 
stall.
  This is due to a misoptimization by gcc 4.8 of the CIRCLEQ famliy of macros, 
apparently due to overzealous strict aliasing deductions.

  One case of this stall is reported at
  http://mailman.mit.edu/pipermail/kerberos/2014-July/020007.html (and
  the rest of the thread), and there is an entry in the upstream
  bugtracker at http://krbdev.mit.edu/rt/Ticket/Display.html?id=7860 .

  gcc 4.9 (as used in Debian unstable at present) is not believed to
  induce this problem.  Upstream has patched their code to use the TAILQ
  family of macros instead, as a workaround, but that workaround 

[Touch-packages] [Bug 1368839] Re: [Design] Application opening animation to start from where the launching action is rooted

2014-09-29 Thread Vesa Rautiainen
Now I actually think this is not that good idea. Technically it's a bit
tricky to implement and visually doesn't really enforce our model where
recent app stack live behind the right edge. I would have the same
transition we use for app switch (short right edge swipe) for app
opening animation as well.

** Changed in: ubuntu-ux
   Importance: Medium = Low

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

Title:
  [Design] Application opening animation to start from where the
  launching action is rooted

Status in Ubuntu UX bugs:
  Triaged
Status in “unity8” package in Ubuntu:
  Incomplete

Bug description:
  Update the app launching animation so that it shows the app expanding
  out from the app icon that was tapped on, see
  
https://docs.google.com/a/canonical.com/drawings/d/1FgkVPsU6g53nSf2pO7SgRYJsI4UPwrItKXNBVhWqrZs/edit

  Principle of “consequence of action rooted in the action”

  There is lots of options how the visual appearance of the opening
  animation could be. Design team to explore idea before implementation.

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

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


[Touch-packages] [Bug 1199877] Re: unity-panel-service memory leak and 100% CPU usage

2014-09-29 Thread KrautOS
This is still an hard issue with up to date trusty, i'm only able to
write this with running:

while true; do sleep 5  kill -s 1 $(pgrep unity-panel-ser); done

That's keep the system alive under heavy load from repeated
Thunderbird messages and probably indicator-notifications.

dpkg -l | egrep ^ii | egrep -o indicator-\\S*

indicator-appmenu
indicator-bluetooth
indicator-cpufreq
indicator-datetime
indicator-keyboard
indicator-messages
indicator-notifications
indicator-power
indicator-printers
indicator-session
indicator-sound

Nice to watch the balloning ;)

top -p $(pgrep unity-panel-ser)

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

Title:
  unity-panel-service memory leak and 100% CPU usage

Status in The Application Menu:
  Fix Released
Status in Application Menu Indicator 13.10 series:
  Fix Released
Status in The Ubuntu Power Consumption Project:
  Fix Released
Status in Unity:
  Invalid
Status in Ubuntu:
  Fix Released
Status in “indicator-appmenu” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Invalid
Status in The Saucy Salamander:
  Fix Released
Status in “indicator-appmenu” source package in Saucy:
  Fix Released

Bug description:
  Impact: high CPU/memory usage from unity-panel-service

  Test case:

  Open a large image in the GIMP and activate a lot of items from the
  global menu. Using shortcuts is enough and faster to reproduce this
  bug (I've always used Ctrl+A and Ctrl+Shift+A). Memory usage of unity-
  panel-service increases steadily and it uses a lot of CPU shortly
  after activating the menu items in a short time.

  Regression potential: check that the menus are stable/working as they
  should

  -
  Just going about my business on Ubuntu Raring amd64 on an x230 and I heard 
the fan kick into action.  top showed me that unity-panel-service was consuming 
all the free cycles on one of my CPUs.  I killed it before my machine 
overheated, so I didn't attach a debugger to see why it was totally pegging out 
a  CPU.

  I'm not sure if this adds any context, but I was using a LibreOffice
  spreadsheet and I could not insert a table because the menu had lost
  it's mind, and then I observed the overly loaded CPU a very short
  while after that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-appmenu/+bug/1199877/+subscriptions

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


[Touch-packages] [Bug 1346723] Re: Cannot delete my chroot.

2014-09-29 Thread Colin Watson
** No longer affects: click

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

Title:
  Cannot delete my chroot.

Status in “click” package in Ubuntu:
  In Progress
Status in “qtcreator-plugin-ubuntu” package in Ubuntu:
  Fix Released

Bug description:
  I found that my install chroot did not appear when I tried to manage
  my kits to add the build for it. The started to delete it. However, I
  found that I could not delete it, and it gave me the error.

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

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


[Touch-packages] [Bug 1374131] Re: qtcreator-plugin autopkgtest fails on AMD64 mesa mesa_10.3.0

2014-09-29 Thread Maarten Lankhorst
I've managed to reproduce this. This seems to be caused because swrast is now 
linked into the gallium megablob as well.
Before llvmpipe was statically linked into libGL.so

Adding a depends on libgl1-mesa-dri to libegl1-mesa and libgl1-mesa-glx
should fix things. I'm verifying this in a ppa.

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

Title:
  qtcreator-plugin autopkgtest fails on AMD64 mesa mesa_10.3.0

Status in “mesa” package in Ubuntu:
  Confirmed

Bug description:
  So, in the course of a unity8 package migration it got halted due to
  qtcreator-plugin autopkg test failing

  see here
  
http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html

  which lead me to look at the jenkins run, note its only failling on amd64 arch
  and...you can see from here
  
https://jenkins.qa.ubuntu.com/job/utopic-adt-qtcreator-plugin-ubuntu/ARCH=amd64,label=adt/
  it started failing about 24 hrs ago with can't init gxl...almost certainly 
meaning it's unhappy with mesa.
  low and behold the difference between the pasing jenkins and failing is

  passing - 
https://jenkins.qa.ubuntu.com/job/utopic-adt-qtcreator-plugin-ubuntu/ARCH=amd64,label=adt/266/console
  which uses
  mesa 10.2.6-1ubuntu3

  failing - 
https://jenkins.qa.ubuntu.com/job/utopic-adt-qtcreator-plugin-ubuntu/ARCH=amd64,label=adt/267/console
  which uses 
  mesa 10.3.0-0ubuntu1

  So can we do a couple of things?
  - revert mesa and see if that fixes the autopkgtest to confirm
  - if so, please leave reverted until we find out why so we can actually 
continue landing our unity8/uitk/webbrowser stuff
  - lastly, might be good to add qtcreator-plugin as an autopkgtest dependency 
to land a new mesa

  sorry for marking critical, but we're sunk until we get this sorted

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

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


[Touch-packages] [Bug 1259251] Re: [browser] Can't copy URLs from the autocomplete list

2014-09-29 Thread Giorgio Venturi
** Changed in: ubuntu-ux
   Status: Fix Committed = Incomplete

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

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

Title:
  [browser] Can't copy URLs from  the autocomplete list

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

Bug description:
  Steps :
  1- You want to go to http://ubuntu.com/phone
  2- You type ubuntu on the adress bar.
  3- You get a list of URLs from which contains http://ubuntu.com/

  Result:
  - You need to type the FULL URL

  Expected :
  - A button to tell the browser put that url for me on the adresse bar.

  Chrome mobile does provide a button next to each URL on the autocomple
  list, once you click on it you get that URL on the adresse bar so you
  can complete your URL.

  -- SOLUTION --
  The design species the suggestions to be populated by the search engine. ATM 
they only surface bookmarks and history

  https://docs.google.com/a/canonical.com/presentation/d/1Qrd4Flfs3EH-
  fI79IfrYgLdAx2nce-L7ve8NKLCX324/edit#slide=id.g2b64bc8c2_525

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

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


[Touch-packages] [Bug 1347913] Re: Turn screen on when phone is moved during a call

2014-09-29 Thread Olga Kemmet
** Changed in: ubuntu-ux
   Status: Triaged = In Progress

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

Title:
  Turn screen on when phone is moved during a call

Status in Dialer app for Ubuntu Touch:
  New
Status in Ubuntu UX bugs:
  In Progress
Status in “powerd” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  New

Bug description:
  This is a breakaway bug from bug 1347001.

  During a call, position the phone such that the proximity sensor is
  not enabled, i.e. put phone on table.  Let the screen shut off after
  an idle timeout.

  The screen should turn on when the phone is moved or screen is
  touched.  This is what Android and iOS do anyway, and probably what
  users expect.

  I'm assuming that powerd is the logical place to have that logic, but
  maybe I'm wrong.  Please feel free to re-assign.

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

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


[Touch-packages] [Bug 1375224] [NEW] Loud noise is heard in headset when call is hanged up

2014-09-29 Thread Jussi Kangas
Public bug reported:

USED SW: 
current build number: 72
device name: krillin
channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
last update: 2014-09-29 07:53:33
version version: 72
version ubuntu: 20140929
version device: 20140925-6623bf1
version custom: 1411735617

TEST STEPS:
1. Select Music app.
2. Start playing a mp3 
3. Call to device under test (DUT)
4. Answer to call
5. Hangup the call from either from DUT or calling phone

EXPECTED RESULT:
mp3 resumes nicely to be played

ACTUAL RESULT:
There is a almost painfully load noise played momentarily before mp3 resumes.  
Used volume in phone or song volume do not seem to affect to issue. 

Used headset: Sennheiser PX 100 - 11. http://en-us.sennheiser.com/on-
ear-headphones-travel-lightweigt-px-100-ii

** Affects: telepathy-ofono (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Loud noise is heard in headset when call is hanged up

Status in “telepathy-ofono” package in Ubuntu:
  New

Bug description:
  USED SW: 
  current build number: 72
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2014-09-29 07:53:33
  version version: 72
  version ubuntu: 20140929
  version device: 20140925-6623bf1
  version custom: 1411735617

  TEST STEPS:
  1. Select Music app.
  2. Start playing a mp3 
  3. Call to device under test (DUT)
  4. Answer to call
  5. Hangup the call from either from DUT or calling phone

  EXPECTED RESULT:
  mp3 resumes nicely to be played

  ACTUAL RESULT:
  There is a almost painfully load noise played momentarily before mp3 resumes. 
 Used volume in phone or song volume do not seem to affect to issue. 

  Used headset: Sennheiser PX 100 - 11. http://en-us.sennheiser.com/on-
  ear-headphones-travel-lightweigt-px-100-ii

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

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


[Touch-packages] [Bug 1375224] Re: Loud noise is heard in headset when call is hanged up

2014-09-29 Thread Jussi Kangas
There is no problem if no headset was used

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

Title:
  Loud noise is heard in headset when call is hanged up

Status in “telepathy-ofono” package in Ubuntu:
  New

Bug description:
  USED SW: 
  current build number: 72
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2014-09-29 07:53:33
  version version: 72
  version ubuntu: 20140929
  version device: 20140925-6623bf1
  version custom: 1411735617

  TEST STEPS:
  1. Select Music app.
  2. Start playing a mp3 
  3. Call to device under test (DUT)
  4. Answer to call
  5. Hangup the call from either from DUT or calling phone

  EXPECTED RESULT:
  mp3 resumes nicely to be played

  ACTUAL RESULT:
  There is a almost painfully load noise played momentarily before mp3 resumes. 
 Used volume in phone or song volume do not seem to affect to issue. 

  Used headset: Sennheiser PX 100 - 11. http://en-us.sennheiser.com/on-
  ear-headphones-travel-lightweigt-px-100-ii

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

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


[Touch-packages] [Bug 241331] Re: Running a non-existing command in the background causes exit

2014-09-29 Thread Jaakov
I found out that though the bug is pretty reproducible on long path lengths, 
for short path lengths, the bug is sometimes reproducible, but sometimes not.
Test case: 
1. Open an xterm with a bash.
2. Make sure that the command q is not present on your system.
3. cd / [Enter]
4. q  [Enter]

Continue doing 4. until your bash exits. I needed 66 attempts for the root 
directory / and command qqq. With the command q it was 51 attempts.
The tested locale is de_DE.UTF-8 for LANG, LC_..., and LANGUAGE on ubuntu, 
bash has version 4.3-7ubuntu1.3,
xterm has version 297-1ubuntu1.
Since the behavior is not deterministic on the user input, it looks like a 
memory corruption issue or a race. Any help?

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

Title:
  Running a non-existing command in the background causes exit

Status in “bash” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: gnome-terminal

  In Ubuntu 8.04, running a command which does not exist can sometimes
  cause an exit command.  Here is an example cut and pasted when gnome-
  terminal is set to stay open on exit.

  richard@sepulchrave:~$ gedit test 
  [1] 13336
  richard@sepulchrave:~$ gdit test 
  [2] 13340
  richard@sepulchrave:~$ exit

  Other times  the exit will not happen but the command will return an
  Exit 127 status.

  richard@sepulchrave:~$ gdit test 
  [1] 13403
  richard@sepulchrave:~$ bash: gdit: command not found

  [1]+  Exit 127gdit test
  richard@sepulchrave:~$ gdit test 
  [1] 13405
  richard@sepulchrave:~$ exit

  Package is
  gnome-terminal:
Installed: 2.22.1-0ubuntu2
Candidate: 2.22.1-0ubuntu2
Version table:
   *** 2.22.1-0ubuntu2 0
  500 http://gb.archive.ubuntu.com hardy/main Packages
  100 /var/lib/dpkg/status

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

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


[Touch-packages] [Bug 1365471] Re: Long-tapping doesn't work on any control

2014-09-29 Thread Matthew Paul Thomas
** Description changed:

  Problem occurs with: Ubuntu 14.10 r22
  Does not occur with: iOS 7, Windows Phone 8.0
  
  1. Long-tap on any control: for example, a button, switch, checkbox, or page 
stack item.
  2. Let go.
  
  What happens: Nothing.
  
  What should happen: Unless the control has a specific action for long-
  tapping, it should activate just as if you did a short tap.
+ 
+ Fixing this would be one way of fixing bug 1289329.

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

Title:
  Long-tapping doesn't work on any control

Status in “ubuntu-ui-toolkit” package in Ubuntu:
  New

Bug description:
  Problem occurs with: Ubuntu 14.10 r22
  Does not occur with: iOS 7, Windows Phone 8.0

  1. Long-tap on any control: for example, a button, switch, checkbox, or page 
stack item.
  2. Let go.

  What happens: Nothing.

  What should happen: Unless the control has a specific action for long-
  tapping, it should activate just as if you did a short tap.

  Fixing this would be one way of fixing bug 1289329.

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

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


[Touch-packages] [Bug 1372559] [NEW] [system-settings] Settings application section headlines

2014-09-29 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

In Settings application.
For example go to SecurityPrivacy view.

Headlines for Security and Privacy are confusing.
- they appear to be clickable, but without any response.
- they are lacking any visual differentiation from actual settings items.

Possible solution:
- increase spacing from the top, to break it from previous section
- use different font, or at least bolt font, to highlight it as section headline
- when clicked, do not highlight the line/row to give impression it's clickable

Same problem is all over the Settings application

** Affects: ubuntu-ux
 Importance: Undecided
 Assignee: Matthew Paul Thomas (mpt)
 Status: New

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

-- 
[system-settings] Settings application section headlines
https://bugs.launchpad.net/bugs/1372559
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to ubuntu-ui-toolkit 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 1375224] Re: Loud noise is heard in headset when call is hanged up

2014-09-29 Thread Jussi Kangas
I hear the extra noise with earbud headset too I took from another
phone, but that's not so loud.

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

Title:
  Loud noise is heard in headset when call is hanged up

Status in “telepathy-ofono” package in Ubuntu:
  New

Bug description:
  USED SW: 
  current build number: 72
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2014-09-29 07:53:33
  version version: 72
  version ubuntu: 20140929
  version device: 20140925-6623bf1
  version custom: 1411735617

  TEST STEPS:
  1. Select Music app.
  2. Start playing a mp3 
  3. Call to device under test (DUT)
  4. Answer to call
  5. Hangup the call from either from DUT or calling phone

  EXPECTED RESULT:
  mp3 resumes nicely to be played

  ACTUAL RESULT:
  There is a almost painfully load noise played momentarily before mp3 resumes. 
 Used volume in phone or song volume do not seem to affect to issue. 

  Used headset: Sennheiser PX 100 - 11. http://en-us.sennheiser.com/on-
  ear-headphones-travel-lightweigt-px-100-ii

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

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


[Touch-packages] [Bug 1374390] Re: when the screen is locked, the old unlocking screen apeears instead the new unity (14.04) lockscreen

2014-09-29 Thread Balazs Pere
Sorry, there's no bug.

dconf reset -f /

solved the problem, although it is not the most elegant solution.

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

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

Title:
  when the screen is locked, the old unlocking screen apeears instead
  the new unity (14.04) lockscreen

Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  When I lock the screen (with Ctrl+Alt+l or Super+l) the old (gnome?)
  screen appears to unlock. I tried to reinstall unity, unity-services,
  lightdm, unity-greeter, but nothing has changed.


  Remark: I have two other machines, one of them works correctly, but on
  the other the locking (Ctrl+Alt+l) doesn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.3+14.04.20140826-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Sep 26 12:35:49 2014
  DistUpgraded: 2014-04-18 09:55:47,870 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:108d]
  InstallationDate: Installed on 2013-10-15 (345 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131007)
  MachineType: ASUSTeK COMPUTER INC. X202E
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed 
root=UUID=bcc104a1-a7cd-4485-b9ff-bf585e1eec22 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (161 days ago)
  dmi.bios.date: 06/20/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X202E.210
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X202E
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX202E.210:bd06/20/2013:svnASUSTeKCOMPUTERINC.:pnX202E:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX202E:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X202E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  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.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Fri Sep 26 12:10:59 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12380 
   vendor AUO
  xserver.version: 2:1.15.1-0ubuntu2.1

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

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


[Touch-packages] [Bug 1375215] Re: White screen in webbrowser and webapps

2014-09-29 Thread Olivier Tilloy
Added a unity8 task to the report as it appears unity8-dash is eating up
a lot of memory, even when idle after a reboot. Tom is seeing it consume
45% memory, while I’m seeing it at a stable 12.7%, which still feels a
lot to me (if one adds to that the 8.8% of unity8, then the shell is
already consuming more than 20% of the system’s available memory).

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

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

Title:
  White screen in webbrowser and webapps / system runs out of memory and
  kills oxide-renderer

Status in “oxide-qt” package in Ubuntu:
  Confirmed
Status in “unity8” package in Ubuntu:
  New

Bug description:
  krillin 14.09 #2 + all updates applied

  After installing the youtube webapps, the browser and all the webapps
  render briefly the go all white.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: liboxideqtcore0 1.2.0-0ubuntu1 [origin: Ubuntu RTM]
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: armhf
  Date: Mon Sep 29 12:51:34 2014
  InstallationDate: Installed on 2014-09-24 (5 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140924-030204)
  SourcePackage: oxide-qt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1372559] Re: [system-settings] Settings application section headlines

2014-09-29 Thread Matthew Paul Thomas
*** This bug is a duplicate of bug 1242666 ***
https://bugs.launchpad.net/bugs/1242666

There's only a certain amount of punishment my designs can take before
they stop working. Here System Settings is suffering from three separate
toolkit problems.

First, as shown in the wireframe
https://wiki.ubuntu.com/SecurityAndPrivacySettings#Phone, Security
and Privacy aren't supposed to be list items at all -- they're
supposed to be standalone labels introducing their respective lists. But
this is impossible in the toolkit, which is bug 1242666.

Second, in the absence of a standalone label element, the System
Settings engineers have used ListItem.Header, but this looks identical
to a normal list item, which is bug 1191029.

And third, list items that don't do anything still look tappable. That's
bug 1362305.

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

** This bug has been marked a duplicate of bug 1242666
   Standalone labels as an element distinct from group headers

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

Title:
  [system-settings] Settings application section headlines

Status in Ubuntu UX bugs:
  New
Status in “ubuntu-ui-toolkit” package in Ubuntu:
  New

Bug description:
  In Settings application.
  For example go to SecurityPrivacy view.

  Headlines for Security and Privacy are confusing.
  - they appear to be clickable, but without any response.
  - they are lacking any visual differentiation from actual settings items.

  Possible solution:
  - increase spacing from the top, to break it from previous section
  - use different font, or at least bolt font, to highlight it as section 
headline
  - when clicked, do not highlight the line/row to give impression it's 
clickable

  Same problem is all over the Settings application

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

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


[Touch-packages] [Bug 1242666] Re: Standalone labels as an element distinct from group headers

2014-09-29 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New = Confirmed

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

Title:
  Standalone labels as an element distinct from group headers

Status in “ubuntu-ui-toolkit” package in Ubuntu:
  Confirmed

Bug description:
  The toolkit currently lacks a standalone label element. This is used,
  for example, for labels introducing controls in the many cases where a
  group header would be inappropriate.

  I have written up a full rationale, including example wireframes, and
  discussed it with other designers at the patterns meeting.
  http://goo.gl/F6dlNd

  The font style for standalone labels should be the same as for other
  labels, such as those next to checkboxes or switches.

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

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


[Touch-packages] [Bug 1375215] Re: White screen in webbrowser and webapps

2014-09-29 Thread Jean-Baptiste Lallement
** Changed in: unity8 (Ubuntu)
   Importance: Undecided = Critical

** Changed in: oxide-qt (Ubuntu)
   Importance: Undecided = Critical

** Tags added: rtm14

** Summary changed:

- White screen in webbrowser and webapps
+ White screen in webbrowser and webapps / system runs out of memory and kills 
oxide-renderer

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

Title:
  White screen in webbrowser and webapps / system runs out of memory and
  kills oxide-renderer

Status in “oxide-qt” package in Ubuntu:
  Confirmed
Status in “unity8” package in Ubuntu:
  New

Bug description:
  krillin 14.09 #2 + all updates applied

  After installing the youtube webapps, the browser and all the webapps
  render briefly the go all white.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: liboxideqtcore0 1.2.0-0ubuntu1 [origin: Ubuntu RTM]
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: armhf
  Date: Mon Sep 29 12:51:34 2014
  InstallationDate: Installed on 2014-09-24 (5 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140924-030204)
  SourcePackage: oxide-qt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1375231] [NEW] iwl3945abg: Can not connect to 'eduroam' (PEAP, MSCHAPv2)

2014-09-29 Thread Maui Muc
Public bug reported:

Since I am running Trusty on my ThinkPad T60 with Intel PRO/Wireless
3945ABG I can no longer connect to the 'eduroam' wireless network of
University of Potsdam. It again and again asks for user-name and
password. Dead certain, there is no spelling mistake. My Nexus 5
connects just fine. It is even more. With Ubuntu 12.04.5 live and
earlier I can OOB successfully connect with the 'eduroam' network.

While trying to connect syslog says:
wpa_supplicant[2949]: wlan0: CTRL-EVENT-SSID-REENABLED id=0 ssid=eduroam
wpa_supplicant[2949]: wlan0: SME: Trying to authenticate with 64:d9:89:6d:ce:dd 
(SSID='eduroam' freq=5320 MHz)
kernel: [  277.639922] wlan0: authenticate with 64:d9:89:6d:ce:dd
kernel: [  277.643045] wlan0: direct probe to 64:d9:89:6d:ce:dd (try 1/3)
NetworkManager[2719]: info (wlan0): supplicant interface state: scanning - 
authenticating
wpa_supplicant[2949]: wlan0: Trying to associate with 64:d9:89:6d:ce:dd 
(SSID='eduroam' freq=5320 MHz)
kernel: [  277.844094] wlan0: send auth to 64:d9:89:6d:ce:dd (try 2/3)
kernel: [  277.845687] wlan0: authenticated
kernel: [  277.846031] iwl3945 :03:00.0 wlan0: disabling HT as WMM/QoS is 
not supported by the AP
kernel: [  277.846040] iwl3945 :03:00.0 wlan0: disabling VHT as WMM/QoS is 
not supported by the AP
kernel: [  277.853237] wlan0: associate with 64:d9:89:6d:ce:dd (try 1/3)
NetworkManager[2719]: info (wlan0): supplicant interface state: 
authenticating - associating
wpa_supplicant[2949]: wlan0: Associated with 64:d9:89:6d:ce:dd
kernel: [  277.857918] wlan0: RX AssocResp from 64:d9:89:6d:ce:dd (capab=0x11 
status=0 aid=2)
kernel: [  277.859119] wlan0: associated
kernel: [  277.859208] cfg80211: Calling CRDA for country: DE
wpa_supplicant[2949]: wlan0: CTRL-EVENT-EAP-STARTED EAP authentication started
NetworkManager[2719]: info (wlan0): supplicant interface state: associating 
- associated
kernel: [  277.865527] cfg80211: Regulatory domain changed to country: DE
kernel: [  277.865533] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp)
kernel: [  277.865536] cfg80211:   (240 KHz - 2483500 KHz @ 4 KHz), 
(N/A, 2000 mBm)
kernel: [  277.865539] cfg80211:   (515 KHz - 525 KHz @ 4 KHz), 
(N/A, 2000 mBm)
kernel: [  277.865541] cfg80211:   (525 KHz - 535 KHz @ 4 KHz), 
(N/A, 2000 mBm)
kernel: [  277.865544] cfg80211:   (547 KHz - 5725000 KHz @ 4 KHz), 
(N/A, 2698 mBm)
kernel: [  277.865546] cfg80211:   (5724 KHz - 6588 KHz @ 216 KHz), 
(N/A, 4000 mBm)
NetworkManager[2719]: warn Activation (wlan0/wireless): association took too 
long.
NetworkManager[2719]: info (wlan0): device state change: config - need-auth 
(reason 'none') [50 60 0]
NetworkManager[2719]: warn Activation (wlan0/wireless): asking for new secrets
kernel: [  285.004318] wlan0: deauthenticating from 64:d9:89:6d:ce:dd by local 
choice (reason=3)
wpa_supplicant[2949]: wlan0: CTRL-EVENT-DISCONNECTED bssid=64:d9:89:6d:ce:dd 
reason=3 locally_generated=1
kernel: [  285.028971] cfg80211: Calling CRDA to update world regulatory domain
kernel: [  285.035784] cfg80211: World regulatory domain updated:
kernel: [  285.035790] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp)
kernel: [  285.035793] cfg80211:   (2402000 KHz - 2472000 KHz @ 4 KHz), 
(300 mBi, 2000 mBm)
kernel: [  285.035796] cfg80211:   (2457000 KHz - 2482000 KHz @ 4 KHz), 
(300 mBi, 2000 mBm)
kernel: [  285.035799] cfg80211:   (2474000 KHz - 2494000 KHz @ 2 KHz), 
(300 mBi, 2000 mBm)
kernel: [  285.035801] cfg80211:   (517 KHz - 525 KHz @ 4 KHz), 
(300 mBi, 2000 mBm)
kernel: [  285.035804] cfg80211:   (5735000 KHz - 5835000 KHz @ 4 KHz), 
(300 mBi, 2000 mBm)
NetworkManager[2719]: warn Connection disconnected (reason -3)
NetworkManager[2719]: info (wlan0): supplicant interface state: associated - 
disconnected
NetworkManager[2719]: warn Couldn't disconnect supplicant interface: This 
interface is not connected.
NetworkManager[2719]: warn Connection disconnected (reason -3)
NetworkManager[2719]: warn No agents were available for this request.
NetworkManager[2719]: info (wlan0): device state change: need-auth - failed 
(reason 'no-secrets') [60 120 7]
NetworkManager[2719]: info NetworkManager state is now DISCONNECTED
NetworkManager[2719]: info Marking connection 'eduroam' invalid.
NetworkManager[2719]: warn Activation (wlan0) failed for connection 'eduroam'
NetworkManager[2719]: info (wlan0): device state change: failed - 
disconnected (reason 'none') [120 30 0]
NetworkManager[2719]: info (wlan0): deactivating device (reason 'none') [0]
wpa_supplicant[2949]: wlan0: CTRL-EVENT-SCAN-STARTED

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: network-manager 0.9.8.8-0ubuntu7
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CasperVersion: 1.340
CurrentDesktop: Unity
Date: Mon Sep 29 

[Touch-packages] [Bug 1375215] Re: White screen in webbrowser and webapps / system runs out of memory and kills oxide-renderer

2014-09-29 Thread Olivier Tilloy
Not sure whether something can be done at the system level to mitigate
the aggressiveness with which oxide-renderer is being killed (with
regards to other applications).

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

Title:
  White screen in webbrowser and webapps / system runs out of memory and
  kills oxide-renderer

Status in “oxide-qt” package in Ubuntu:
  Confirmed
Status in “unity8” package in Ubuntu:
  New

Bug description:
  krillin 14.09 #2 + all updates applied

  After installing the youtube webapps, the browser and all the webapps
  render briefly the go all white.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: liboxideqtcore0 1.2.0-0ubuntu1 [origin: Ubuntu RTM]
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: armhf
  Date: Mon Sep 29 12:51:34 2014
  InstallationDate: Installed on 2014-09-24 (5 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140924-030204)
  SourcePackage: oxide-qt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1370376] Re: Can't receive MMS despite ability to send on Tele2

2014-09-29 Thread Sergio Schvezov
Please follow
https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1371032/comments/5

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

** Changed in: nuntium (Ubuntu)
 Assignee: Sergio Schvezov (sergiusens) = Tomas Öqvist (tomoqv)

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

Title:
  Can't receive MMS despite ability to send on Tele2

Status in “network-manager” package in Ubuntu:
  New
Status in “nuntium” package in Ubuntu:
  Incomplete

Bug description:
  I can send MMS (and they actually come through to the recipient), but
  I can't receive MMS. I am not sure if this is an APN settings issue,
  but I would have thought it either worked both ways or not at all.

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

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


[Touch-packages] [Bug 1375215] Re: White screen in webbrowser and webapps / system runs out of memory and kills oxide-renderer

2014-09-29 Thread David Barth
I think there are still 2 options there. Either the OOM killer should
get rid of the whole process group, so that webbrowser or webapps are
not half killed'. Or oxide should trap a signal indicating that the
underlying renderer processes died, and let the client apps quit.

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

Title:
  White screen in webbrowser and webapps / system runs out of memory and
  kills oxide-renderer

Status in “oxide-qt” package in Ubuntu:
  Confirmed
Status in “unity8” package in Ubuntu:
  New

Bug description:
  krillin 14.09 #2 + all updates applied

  After installing the youtube webapps, the browser and all the webapps
  render briefly the go all white.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: liboxideqtcore0 1.2.0-0ubuntu1 [origin: Ubuntu RTM]
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: armhf
  Date: Mon Sep 29 12:51:34 2014
  InstallationDate: Installed on 2014-09-24 (5 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140924-030204)
  SourcePackage: oxide-qt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1374131] Re: qtcreator-plugin autopkgtest fails on AMD64 mesa mesa_10.3.0

2014-09-29 Thread Maarten Lankhorst
Ok, it also seems that libgbm1 was pulling in libgl1-mesa-dri directly
in 10.2.6, this is why libgl1-mesa-dri was installed in the first place.

/usr/lib/$ARCH/gbm/gbm_gallium_drm.so was linking to the shared
libgallium.so . This no longer happens with 10.3.0 because we drop the
patches that build gallium shared, because upstream handles it better.

I would say this proves that the tests are all broken and need to add an
explicit depend on libgl1-mesa-dri somewhere.

But since this has been going on for so long I think the easiest thing
to do is fixing up the mesa packaging for backwards compatability.

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

Title:
  qtcreator-plugin autopkgtest fails on AMD64 mesa mesa_10.3.0

Status in “mesa” package in Ubuntu:
  Confirmed

Bug description:
  So, in the course of a unity8 package migration it got halted due to
  qtcreator-plugin autopkg test failing

  see here
  
http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html

  which lead me to look at the jenkins run, note its only failling on amd64 arch
  and...you can see from here
  
https://jenkins.qa.ubuntu.com/job/utopic-adt-qtcreator-plugin-ubuntu/ARCH=amd64,label=adt/
  it started failing about 24 hrs ago with can't init gxl...almost certainly 
meaning it's unhappy with mesa.
  low and behold the difference between the pasing jenkins and failing is

  passing - 
https://jenkins.qa.ubuntu.com/job/utopic-adt-qtcreator-plugin-ubuntu/ARCH=amd64,label=adt/266/console
  which uses
  mesa 10.2.6-1ubuntu3

  failing - 
https://jenkins.qa.ubuntu.com/job/utopic-adt-qtcreator-plugin-ubuntu/ARCH=amd64,label=adt/267/console
  which uses 
  mesa 10.3.0-0ubuntu1

  So can we do a couple of things?
  - revert mesa and see if that fixes the autopkgtest to confirm
  - if so, please leave reverted until we find out why so we can actually 
continue landing our unity8/uitk/webbrowser stuff
  - lastly, might be good to add qtcreator-plugin as an autopkgtest dependency 
to land a new mesa

  sorry for marking critical, but we're sunk until we get this sorted

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

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


[Touch-packages] [Bug 1374521] Re: ifup should specify '-allow=auto' not '-allow=hotplug'

2014-09-29 Thread Martin Pitt
Right, I get the same (on both current utopic and your Ubuntu Core
environment). So /etc/init.d/networking exists and is being run --
what's missing? What does ip a show? It gets a proper DHCP assignment
and routing 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/1374521

Title:
  ifup should specify '-allow=auto' not '-allow=hotplug'

Status in “systemd” package in Ubuntu:
  Incomplete

Bug description:
  /lib/systemd/system/ifup@.service specifies:

    ExecStart=/sbin/ifup --allow=hotplug %I

  This really needs to be:

    ExecStart=/sbin/ifup --allow=auto %I

  Since otherwise, for systems that don't use network-manager, the
  service will only bring up interfaces which have specified allow-
  hotplug $if in /etc/network/interfaces*.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: systemd 208-8ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3
  Uname: Linux 3.16.0-17-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Sep 26 16:54:12 2014
  InstallationDate: Installed on 2014-04-11 (167 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409)
  SourcePackage: systemd
  UpgradeStatus: Upgraded to utopic on 2014-05-08 (141 days ago)

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

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


[Touch-packages] [Bug 1375242] [NEW] Low Brightness when started after battery discharge in suspend state

2014-09-29 Thread Abhinav Dwivedi
Public bug reported:

I upgraded from 12.04 to 14.04 after which i have noticed this issue and able 
to reproduce it.
After the system discharges during suspend state and i reboot it after 
connecting power. The screen brightness is very low. 
Sometimes the decrease brightness key works which infact increases the 
brightness. Cannot increase brightness from Brightness and Lock.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
Uname: Linux 3.13.0-36-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.4
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
Date: Mon Sep 29 17:43:40 2014
DistUpgraded: 2014-09-06 16:19:53,120 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 4.3.10, 3.13.0-35-generic, x86_64: installed
 virtualbox, 4.3.10, 3.13.0-36-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:215a]
InstallationDate: Installed on 2012-05-27 (854 days ago)
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
MachineType: LENOVO 0578PMQ
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic 
root=UUID=637e803b-1b0a-43dc-9a7d-933c8ec78f14 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to trusty on 2014-09-06 (23 days ago)
dmi.bios.date: 10/14/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 80ET42WW (1.19 )
dmi.board.name: 0578PMQ
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr80ET42WW(1.19):bd10/14/2010:svnLENOVO:pn0578PMQ:pvrThinkPadEdge:rvnLENOVO:rn0578PMQ:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 0578PMQ
dmi.product.version: ThinkPad Edge
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.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Mon Sep 29 17:41:25 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   16544 
 vendor LEN
xserver.version: 2:1.15.1-0ubuntu2.1

** 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/1375242

Title:
  Low Brightness when started after battery discharge in suspend state

Status in “xorg” package in Ubuntu:
  New

Bug description:
  I upgraded from 12.04 to 14.04 after which i have noticed this issue and able 
to reproduce it.
  After the system discharges during suspend state and i reboot it after 
connecting power. The screen brightness is very low. 
  Sometimes the decrease brightness key works which infact increases the 
brightness. Cannot increase brightness from Brightness and Lock.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.4
  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
  Date: Mon Sep 29 17:43:40 2014
  DistUpgraded: 2014-09-06 16:19:53,120 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.10, 3.13.0-35-generic, 

[Touch-packages] [Bug 1232130] Re: Uninstalling an app doesn't stop it

2014-09-29 Thread Colin Watson
We seeded upstart-app-launch-tools (now ubuntu-app-launch-tools) some
time ago.

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

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

Title:
  Uninstalling an app doesn't stop it

Status in “click” package in Ubuntu:
  Confirmed
Status in “ubuntu-touch-meta” package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  Launch an installed app, uninstall it.  Not only is it still listed in
  the list of installed apps (bug #1232129), it's also still in the
  running app lists, and if you press on the installed app icon or slide
  right, you get back to the running app.

  I think any running instance of this app should be killed along the
  removal.

  Cheers,

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

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


[Touch-packages] [Bug 1368492] Re: crash opening image file

2014-09-29 Thread Jussi Pakkanen
I instrumented thumbnailer to print some text when it is created and
called. Then I copied images to the Pictures directory and clicked
around. It turns out that ThumbnailGenerator::requestImage is never
called. The generated thumbnails do not appear in ~/.cache/thumbnails
either (which they should, unless gallery-app is requesting large enough
images).

I wrote a thread torture test for thumbnailer and ran it under helgrind
for 15 minutes or so and it produced no thread errors.

Even more strangely I can't reproduce this any more. Tapping on an image
while others are loading works just fine.

All of this, combined with bug #1375238, makes me suspect that there is
a threading bug/buffer overrun somewhere else in the stack and it just
happens to manifest itself as this bug.

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

Title:
  crash opening image file

Status in “thumbnailer” package in Ubuntu:
  Confirmed

Bug description:
  krillin image 25
  libthumbailer version 1.2+14.10.20140814-0ubuntu1

  - take a picture with the camera
  - open the gallery app
  - click on the thumbnail of the photo just taken
  - boom, crash happens

  Here is the stack trace. Core file and picture used are attached

  [Thread debugging using libthread_db enabled]
  Using host libthread_db library /lib/arm-linux-gnueabihf/libthread_db.so.1.
  Core was generated by `./gallery-app'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0xb5b2201c in std::string::assign(std::string const) ()
 from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  (gdb) bt
  #0  0xb5b2201c in std::string::assign(std::string const) ()
 from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  #1  0xacebe712 in ?? () from /usr/lib/arm-linux-gnueabihf/libthumbnailer.so.0
  #2  0xacebec62 in ?? () from /usr/lib/arm-linux-gnueabihf/libthumbnailer.so.0
  #3  0xacebff34 in Thumbnailer::get_thumbnail(std::string const, 
ThumbnailSize, ThumbnailPolicy) () from 
/usr/lib/arm-linux-gnueabihf/libthumbnailer.so.0
  #4  0xacec00ae in Thumbnailer::get_thumbnail(std::string const, 
ThumbnailSize)
  () from /usr/lib/arm-linux-gnueabihf/libthumbnailer.so.0
  #5  0xacf7b70e in ThumbnailGenerator::requestImage(QString const, QSize*, 
QSize const) ()
 from 
/usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/libUbuntuComponents.so
  #6  0xb640acfa in ?? () from /usr/lib/arm-linux-gnueabihf/libQt5Quick.so.5
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

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

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


[Touch-packages] [Bug 1267059] Re: Unattended-Upgrade::Remove-Unused-Dependencies does not work

2014-09-29 Thread urusha
Lars Heide, your patch works great for me, I think it should be applied
upstream. But some people may find differential behavior
(now_auto_removable-pkgs_auto_removable) safer. Then the right solution
may be: implementing logic described in #7 (in addition to patch from
#4) with adding new config option like Remove-Unused-Dependencies-
NewOnly.

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

Title:
  Unattended-Upgrade::Remove-Unused-Dependencies does not work

Status in “unattended-upgrades” package in Ubuntu:
  Triaged

Bug description:
  I have a system that runs unattended-upgrades just fine. Now i want to
  automate removal of old kernels and kernel header packages that are
  accumulating otherwise. So i set 'Unattended-Upgrade::Remove-Unused-
  Dependencies true;'. But it doesn't work.

  
  Details: Lots of stuff pending autoremoval:

  $ apt-get --assume-no autoremove 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED
linux-headers-3.2.0-38 linux-headers-3.2.0-38-generic 
linux-headers-3.2.0-39 linux-headers-3.2.0-39-generic linux-headers-3.2.0-40 
linux-headers-3.2.0-40-generic linux-headers-3.2.0-41 
linux-headers-3.2.0-41-generic linux-headers-3.2.0-43 
linux-headers-3.2.0-43-generic linux-headers-3.2.0-44 
linux-headers-3.2.0-44-generic linux-headers-3.2.0-45 
linux-headers-3.2.0-45-generic linux-headers-3.2.0-48 
linux-headers-3.2.0-48-generic linux-headers-3.2.0-51 
linux-headers-3.2.0-51-generic linux-headers-3.2.0-52 
linux-headers-3.2.0-52-generic linux-headers-3.2.0-53 
linux-headers-3.2.0-53-generic linux-headers-3.2.0-54 
linux-headers-3.2.0-54-generic linux-headers-3.2.0-55 
linux-headers-3.2.0-55-generic linux-headers-3.2.0-56 
linux-headers-3.2.0-56-generic linux-image-3.2.0-39-generic 
linux-image-3.2.0-40-generic linux-image-3.2.0-41-generic 
linux-image-3.2.0-43-generic linux-image-3.2.0-44-generic 
linux-image-3.2.0-45-generic linux-image-3.2.0-48-generic 
linux-image-3.2.0-51-generic linux-image-3.2.0-52-generic 
linux-image-3.2.0-53-generic linux-image-3.2.0-54-generic 
linux-image-3.2.0-55-generic linux-image-3.2.0-56-generic
  0 upgraded, 0 newly installed, 41 to remove and 13 not upgraded.
  After this operation, 2,893 MB disk space will be freed.
  Do you want to continue [Y/n]? N
  Abort.

  Note that the majority of these packages have been installed by
  unattended-upgrades from precise-security.

  According to the comments within/etc/apt/apt.conf.d/50unattended-
  upgrades, this should automate autoremoval:

// Do automatic removal of new unused dependencies after the upgrade
// (equivalent to apt-get autoremove)
Unattended-Upgrade::Remove-Unused-Dependencies true;

  but nothing happens (note the line Packages that are auto removed: ''
  :

  $ unattended-upgrades --debug --dry-run
  Initial blacklisted packages: 
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=precise-security']
  adjusting candidate version: 'Version: package:'accountsservice' 
version:'0.6.15-2ubuntu9.6.1''
  adjusting candidate version: 'Version: package:'libaccountsservice0' 
version:'0.6.15-2ubuntu9.6.1''
  adjusting candidate version: 'Version: package:'libdrm-intel1' 
version:'2.4.43-0ubuntu0.0.3''
  adjusting candidate version: 'Version: package:'libdrm-nouveau1a' 
version:'2.4.43-0ubuntu0.0.3''
  adjusting candidate version: 'Version: package:'libdrm-radeon1' 
version:'2.4.43-0ubuntu0.0.3''
  adjusting candidate version: 'Version: package:'libdrm2' 
version:'2.4.43-0ubuntu0.0.3''
  Checking: bc ([Origin component:'main' archive:'precise-updates' 
origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True])
  Checking: grub-common ([Origin component:'main' archive:'precise-updates' 
origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True])
  Checking: grub-pc ([Origin component:'main' archive:'precise-updates' 
origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True])
  Checking: grub-pc-bin ([Origin component:'main' archive:'precise-updates' 
origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True])
  Checking: grub2-common ([Origin component:'main' archive:'precise-updates' 
origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True])
  Checking: iproute ([Origin component:'main' archive:'precise-updates' 
origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True])
  Checking: landscape-common ([Origin component:'main' 
archive:'precise-updates' origin:'Ubuntu' label:'Ubuntu' 
site:'gb.archive.ubuntu.com' isTrusted:True])
  pkgs that look like they should be upgraded: 
  Fetched 0 B in 0s (0 B/s) 

[Touch-packages] [Bug 1371651] Re: Daily does not boot into graphical interface after installation

2014-09-29 Thread Ian Bruntlett
I've experienced the no GUI after installing lubuntu problem.

Here are the details relevant to my case:-

Here are the technical details:-
-rw-rw-r-- 1 ian ian 630M Sep 28 17:10 lubuntu-14.10-beta2-alternate-i386.iso
-rw-rw-r-- 1 ian ian  444 Sep 28 17:07 MD5SUMS_lubuntu
ian@rutherford:~/isos$ md5sum lubuntu-14.10-beta2-alternate-i386.iso
62da9daeaa314fa22b6fbced57568827  lubuntu-14.10-beta2-alternate-i386.iso

It installed OK with no problems. However, when booted up, apart from
the BIOS screen, nothing is displayed. This PC originally had a working
lubuntu 14.04LTS running on it perfectly.

Hardware used:-
Dell Optiplex GX50
1.3GHz Celeron
512MB RAM
20GB Hard disc
CD-ROM drive

Grub2 does run. I've switched it on and pressed the left shift button to
get to the Grub2 screen and played around with that to no a

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

Title:
  Daily does not boot into graphical interface after installation

Status in Light Display Manager:
  Invalid
Status in “lightdm” package in Ubuntu:
  Invalid
Status in “linux” package in Ubuntu:
  Invalid
Status in “plymouth” package in Ubuntu:
  In Progress

Bug description:
  used the daily iso 2015-09-19 i386
  ran installation on virtualbox 4.3.16

  after installation, the system won't boot into the graphical
  interface. instead, switching to vt1 and back to vt7 reveals the
  attached errors.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2
  Uname: Linux 3.16.0-16-generic i686
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: i386
  Date: Fri Sep 19 17:09:17 2014
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash -- debian-installer/language=de 
keyboard-configuration/layoutcode?=de
  InstallationDate: Installed on 2014-09-19 (0 days ago)
  InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha i386 (20140919)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1366380] Re: telepathy-mission-control is trying to open weird files on startup

2014-09-29 Thread David Barth
I am also observing this on a phone, running utopic image #257

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

Title:
  telepathy-mission-control is trying to open weird files on startup

Status in “telepathy-mission-control-5” package in Ubuntu:
  Invalid

Bug description:
  Upon startup I'm getting a notice that an error occured. When I check
  the syslog I see errors like:

  Sep  6 19:57:22 Earth kernel: [   86.045357] type=1400 
audit(1410026242.433:76): apparmor=DENIED operation=open 
profile=/usr/lib/telepathy/mission-control-5 
name=2F6D656469612F53746F726167652F50726F66696C652F5562756E74752031342E30342F6C6F6F7374726F2F2E636F6E6669672F6C69626163636F756E74732D676C69622F6163636F756E74732E6462
 pid=3007 comm=mission-control requested_mask=rw denied_mask=rw 
fsuid=1000 ouid=1000
  Sep  6 19:57:22 Earth kernel: [   86.045707] type=1400 
audit(1410026242.433:77): apparmor=DENIED operation=open 
profile=/usr/lib/telepathy/mission-control-5 
name=2F6D656469612F53746F726167652F50726F66696C652F5562756E74752031342E30342F6C6F6F7374726F2F2E636F6E6669672F6C69626163636F756E74732D676C69622F6163636F756E74732E6462
 pid=3007 comm=mission-control requested_mask=r denied_mask=r fsuid=1000 
ouid=1000
  Sep  6 19:57:22 Earth kernel: [   86.050493] type=1400 
audit(1410026242.437:78): apparmor=DENIED operation=open 
profile=/usr/lib/telepathy/mission-control-5 
name=2F6D656469612F53746F726167652F50726F66696C652F5562756E74752031342E30342F6C6F6F7374726F2F2E636F6E6669672F64636F6E662F75736572
 pid=3007 comm=mission-control requested_mask=r denied_mask=r fsuid=1000 
ouid=1000
  Sep  6 19:57:22 Earth kernel: [   86.108894] type=1400 
audit(1410026242.497:79): apparmor=DENIED operation=open 
profile=/usr/lib/telepathy/mission-control-5 
name=2F6D656469612F53746F726167652F50726F66696C652F5562756E74752031342E30342F6C6F6F7374726F2F2E6C6F63616C2F73686172652F74656C6570617468792F6D697373696F6E2D636F6E74726F6C2F6163636F756E74732E636667
 pid=3007 comm=mission-control requested_mask=r denied_mask=r fsuid=1000 
ouid=1000

  According to http://askubuntu.com/questions/410808/what-is-reason-for-
  apparmor-denied-operation-open, telepathy-mission-control-5 is trying
  to open a file it has no access to.

  However, the name part is completely rubbish. How can check what
  file telepathy is actually trying to open? How do I fix that?

  I am on Ubuntu 14.04 LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1366380/+subscriptions

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


[Touch-packages] [Bug 1274548] Re: gst-plugin-scanner crashed with SIGSEGV in __GI___pthread_mutex_lock()

2014-09-29 Thread Alberto Salvia Novella
** Package changed: gstreamer1.0 (Ubuntu) = virtualbox (Ubuntu)

** Changed in: virtualbox (Ubuntu)
   Status: Triaged = Confirmed

** No longer affects: gstreamer1.0

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

Title:
  gst-plugin-scanner crashed with SIGSEGV in __GI___pthread_mutex_lock()

Status in “virtualbox” package in Ubuntu:
  Confirmed

Bug description:
  ***
   ISSUE 
  ***

  HOW TO REPRODUCE

  -
  http://iso.qa.ubuntu.com/qatracker/milestones/308/builds/57248/testcases

  EXPECTED BEHAVIOUR

  - The distribution to upgrade without futher problems.

  REAL BEHAVIOUR

  - The gst-plugin-scanner application crashes during the installing
  the upgrades phase of the process.

  RELEVANT DETAILS

  - The user's hardware was http://phillw.net/hardware/Ed3c22qV.

  **
   SOLUTION 
  **

  WORK-AROUND

  - None known.

  FIX

  - Unknown.

  REGRESSION POTENTIAL

  - Since the application doesn't work at all and does a very specific
  action, the regression potential is very low.

  
   TECHNICAL INFO 
  

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: libgstreamer1.0-0 1.2.2-1ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic i686
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: i386
  Date: Thu Jan 30 15:16:32 2014
  ExecutablePath: 
/usr/lib/i386-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner
  InstallationDate: Installed on 2013-11-29 (61 days ago)
  InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release i386 (20131016)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner -l
  SegvAnalysis:
   Segfault happened at: 0xb74cb036 __GI___pthread_mutex_lock+22: mov
0xc(%esi),%eax
   PC (0xb74cb036) ok
   source 0xc(%esi) (0x1070) not located in a known VMA region (needed 
readable region)!
   destination %eax ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gstreamer1.0
  StacktraceTop:
   __GI___pthread_mutex_lock (mutex=0x1064) at ../nptl/pthread_mutex_lock.c:66
   crLockMutex () from /usr/lib/VBoxOGLcrutil.so
   crHashtableLock () from /usr/lib/VBoxOGLcrutil.so
   ?? () from /usr/lib/i386-linux-gnu/dri/vboxvideo_dri.so
   rtThreadMain () from /usr/lib/i386-linux-gnu/dri/vboxvideo_dri.so
  Title: gst-plugin-scanner crashed with SIGSEGV in __GI___pthread_mutex_lock()
  UpgradeStatus: Upgraded to trusty on 2014-01-30 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Touch-packages] [Bug 1375242] Re: Low Brightness when started after battery discharge in suspend state

2014-09-29 Thread Abhinav Dwivedi
** Description changed:

  I upgraded from 12.04 to 14.04 after which i have noticed this issue and able 
to reproduce it.
- After the system discharges during suspend state and i reboot it after 
connecting power. The screen brightness is very low. 
+ After the system discharges during suspend state and i reboot it after 
connecting power. The screen brightness is very low.
  Sometimes the decrease brightness key works which infact increases the 
brightness. Cannot increase brightness from Brightness and Lock.
+ Another restart fixes the brightness.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  .tmp.unity.support.test.0:
-  
+ 
  ApportVersion: 2.14.1-0ubuntu3.4
  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
  Date: Mon Sep 29 17:43:40 2014
  DistUpgraded: 2014-09-06 16:19:53,120 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
-  virtualbox, 4.3.10, 3.13.0-35-generic, x86_64: installed
-  virtualbox, 4.3.10, 3.13.0-36-generic, x86_64: installed
+  virtualbox, 4.3.10, 3.13.0-35-generic, x86_64: installed
+  virtualbox, 4.3.10, 3.13.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
-Subsystem: Lenovo Device [17aa:215a]
+  Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
+    Subsystem: Lenovo Device [17aa:215a]
  InstallationDate: Installed on 2012-05-27 (854 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MachineType: LENOVO 0578PMQ
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic 
root=UUID=637e803b-1b0a-43dc-9a7d-933c8ec78f14 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to trusty on 2014-09-06 (23 days ago)
  dmi.bios.date: 10/14/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 80ET42WW (1.19 )
  dmi.board.name: 0578PMQ
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr80ET42WW(1.19):bd10/14/2010:svnLENOVO:pn0578PMQ:pvrThinkPadEdge:rvnLENOVO:rn0578PMQ:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 0578PMQ
  dmi.product.version: ThinkPad Edge
  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.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Sep 29 17:41:25 2014
  xserver.configfile: default
  xserver.errors:
-  
+ 
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
-  product id   16544 
-  vendor LEN
+  product id   16544
+  vendor LEN
  xserver.version: 2:1.15.1-0ubuntu2.1

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

Title:
  Low Brightness when started after battery discharge in suspend state

Status in “xorg” package in Ubuntu:
  New

Bug description:
  I upgraded from 12.04 to 14.04 after which i have noticed this issue and able 
to reproduce it.
  After the system discharges during suspend state and i reboot it after 
connecting power. The screen brightness is very low.
  Sometimes the decrease brightness key works which infact increases the 
brightness. Cannot increase brightness from Brightness and Lock.
  Another restart fixes the brightness.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  .tmp.unity.support.test.0:

  

[Touch-packages] [Bug 1374131] Re: qtcreator-plugin autopkgtest fails on AMD64 mesa mesa_10.3.0

2014-09-29 Thread Maarten Lankhorst
** Tags removed: block-proposed

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

Title:
  qtcreator-plugin autopkgtest fails on AMD64 mesa mesa_10.3.0

Status in “mesa” package in Ubuntu:
  Confirmed

Bug description:
  So, in the course of a unity8 package migration it got halted due to
  qtcreator-plugin autopkg test failing

  see here
  
http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html

  which lead me to look at the jenkins run, note its only failling on amd64 arch
  and...you can see from here
  
https://jenkins.qa.ubuntu.com/job/utopic-adt-qtcreator-plugin-ubuntu/ARCH=amd64,label=adt/
  it started failing about 24 hrs ago with can't init gxl...almost certainly 
meaning it's unhappy with mesa.
  low and behold the difference between the pasing jenkins and failing is

  passing - 
https://jenkins.qa.ubuntu.com/job/utopic-adt-qtcreator-plugin-ubuntu/ARCH=amd64,label=adt/266/console
  which uses
  mesa 10.2.6-1ubuntu3

  failing - 
https://jenkins.qa.ubuntu.com/job/utopic-adt-qtcreator-plugin-ubuntu/ARCH=amd64,label=adt/267/console
  which uses 
  mesa 10.3.0-0ubuntu1

  So can we do a couple of things?
  - revert mesa and see if that fixes the autopkgtest to confirm
  - if so, please leave reverted until we find out why so we can actually 
continue landing our unity8/uitk/webbrowser stuff
  - lastly, might be good to add qtcreator-plugin as an autopkgtest dependency 
to land a new mesa

  sorry for marking critical, but we're sunk until we get this sorted

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

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


[Touch-packages] [Bug 1366380] Re: telepathy-mission-control is trying to open weird files on startup

2014-09-29 Thread Jamie Strandboge
Thank you for using Ubuntu and filing a bug.

$ aa-decode 
2F6D656469612F53746F726167652F50726F66696C652F5562756E74752031342E30342F6C6F6F7374726F2F2E6C6F63616C2F73686172652F74656C6570617468792F6D697373696F6E2D636F6E74726F6C2F6163636F756E74732E636667
Decoded: /media/Storage/Profile/Ubuntu 
14.04/loostro/.local/share/telepathy/mission-control/accounts.cfg

Piotr, it looks like you have your HOME set to something non-standard.
Please see https://wiki.ubuntu.com/DebuggingApparmor#Adjusting_Tunables
for how to adjust your system to work with this.

** Changed in: telepathy-mission-control-5 (Ubuntu)
   Status: New = Invalid

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

Title:
  telepathy-mission-control is trying to open weird files on startup

Status in “telepathy-mission-control-5” package in Ubuntu:
  Invalid

Bug description:
  Upon startup I'm getting a notice that an error occured. When I check
  the syslog I see errors like:

  Sep  6 19:57:22 Earth kernel: [   86.045357] type=1400 
audit(1410026242.433:76): apparmor=DENIED operation=open 
profile=/usr/lib/telepathy/mission-control-5 
name=2F6D656469612F53746F726167652F50726F66696C652F5562756E74752031342E30342F6C6F6F7374726F2F2E636F6E6669672F6C69626163636F756E74732D676C69622F6163636F756E74732E6462
 pid=3007 comm=mission-control requested_mask=rw denied_mask=rw 
fsuid=1000 ouid=1000
  Sep  6 19:57:22 Earth kernel: [   86.045707] type=1400 
audit(1410026242.433:77): apparmor=DENIED operation=open 
profile=/usr/lib/telepathy/mission-control-5 
name=2F6D656469612F53746F726167652F50726F66696C652F5562756E74752031342E30342F6C6F6F7374726F2F2E636F6E6669672F6C69626163636F756E74732D676C69622F6163636F756E74732E6462
 pid=3007 comm=mission-control requested_mask=r denied_mask=r fsuid=1000 
ouid=1000
  Sep  6 19:57:22 Earth kernel: [   86.050493] type=1400 
audit(1410026242.437:78): apparmor=DENIED operation=open 
profile=/usr/lib/telepathy/mission-control-5 
name=2F6D656469612F53746F726167652F50726F66696C652F5562756E74752031342E30342F6C6F6F7374726F2F2E636F6E6669672F64636F6E662F75736572
 pid=3007 comm=mission-control requested_mask=r denied_mask=r fsuid=1000 
ouid=1000
  Sep  6 19:57:22 Earth kernel: [   86.108894] type=1400 
audit(1410026242.497:79): apparmor=DENIED operation=open 
profile=/usr/lib/telepathy/mission-control-5 
name=2F6D656469612F53746F726167652F50726F66696C652F5562756E74752031342E30342F6C6F6F7374726F2F2E6C6F63616C2F73686172652F74656C6570617468792F6D697373696F6E2D636F6E74726F6C2F6163636F756E74732E636667
 pid=3007 comm=mission-control requested_mask=r denied_mask=r fsuid=1000 
ouid=1000

  According to http://askubuntu.com/questions/410808/what-is-reason-for-
  apparmor-denied-operation-open, telepathy-mission-control-5 is trying
  to open a file it has no access to.

  However, the name part is completely rubbish. How can check what
  file telepathy is actually trying to open? How do I fix that?

  I am on Ubuntu 14.04 LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1366380/+subscriptions

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


[Touch-packages] [Bug 1330770] Re: click packages rely upon tls for integrity and authenticity

2014-09-29 Thread Diego Sarmentero
** Changed in: ubuntu-system-settings (Ubuntu)
   Status: Triaged = In Progress

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

Title:
  click packages rely upon tls for integrity and authenticity

Status in Click Package metadata search service:
  Fix Released
Status in Online service used by software center:
  Fix Released
Status in Click Packages Scope for Unity:
  Fix Committed
Status in “click” package in Ubuntu:
  Fix Released
Status in “ubuntu-system-settings” package in Ubuntu:
  In Progress
Status in “unity-scope-click” package in Ubuntu:
  Fix Released

Bug description:
  Hello, I just completed a quick review of the click source and the
  unity-scope-click source and behaviours, and found some opportunities
  for improvement.

  Debian, and Ubuntu, rely upon signed repository files with
  cryptographic hashes of packages to provide both integrity and
  authenticity checks for the packages hosted on that repository.

  The click framework and the unity-scope-click discovery and
  installation tool do not use signed repository files, nor do they have
  signatures of any sort on downloaded packages. The only integrity and
  authenticity checks are provided by the use of HTTPS.  The click
  verify command will check files within the archive against MD5sums
  stored inside the archive but the click verify command is not used
  during package installation. (This is suitable for validating
  integrity against accidental changes only.)

  While it appears that unity-scope-click properly uses HTTPS to
  download package metadata and packages, HTTPS alone is insufficient
  for our needs:

  - Someone in a position to create new certificates at any of several
  hundred certificate authorities could create certificates purporting
  to be our update servers. This actual problem has been discovered in
  the wild with several certificate authorities issuing wild-card
  certificates or even certificates with signing authority.

  - X.509 is extremely complicated; TLS is extremely complicated. Flaws
  in both are inevitable.

  - HTTPS prevents the use of caching.

  - HTTPS only 'works' for data-in-motion; it is useless for data-at-
  rest integrity and authenticity checks.

  I have not yet reviewed the tools that application authors will use to
  upload their packages to our distribution servers but note in passing
  that most of these issues are also issues for adding packages to our
  update servers -- packages in flight within our network can be
  corrupted for many reasons, packages on disk can be corrupted for many
  reasons. A signature mechanism can protect against internal network
  faults, storage faults, and provide assurance months or years later
  that an uploaded package was uploaded by someone in control of a
  corresponding private key.

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/click-package-index/+bug/1330770/+subscriptions

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


[Touch-packages] [Bug 258110] Re: Camera application cannot record video

2014-09-29 Thread Oliver Grawert
** Changed in: cmpc
   Status: In Progress = Won't Fix

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

Title:
  Camera application cannot record video

Status in Cheese Camera Application:
  Expired
Status in Application and image devlopment around the Classmate PC:
  Won't Fix
Status in “cheese” package in Ubuntu:
  Fix Released
Status in “gstreamer0.10” package in Ubuntu:
  Fix Released
Status in “cheese” source package in Hardy:
  Fix Released
Status in “gstreamer0.10” source package in Hardy:
  Fix Released
Status in “cheese” source package in Intrepid:
  Fix Released
Status in “gstreamer0.10” source package in Intrepid:
  Fix Released

Bug description:
  Run cheese, select video and start recording.Try clicking stop
  recording but there's no response.

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

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


[Touch-packages] [Bug 1364003] Re: [FFE] mesa 10.3

2014-09-29 Thread Maarten Lankhorst
Hey,

It is my opinion the autopkgtests themselves were broken, but I've added
explicit depends in mesa to always force libgl1-mesa-dri to be installed
when libgl1-mesa-dri, libegl1-mesa or libgbm1 are installed.

This allows the tests to run correctly again, and presumably fixes the
armhf tests too.

~Maarten

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

Title:
  [FFE] mesa 10.3

Status in “mesa” package in Ubuntu:
  Fix Committed

Bug description:
  Impact to ubuntu:
  Proper support for llvm 3.5 without crashing llvmpipe when running tests 
on i386.
  kms swrast was requested, will be available in 10.3.
  Build fixes to support a gallium megablob, reducing size even further.

  New features
  GL_ARB_ES3_compatibility on nv50, nvc0, r600, radeonsi, softpipe, llvmpipe
  GL_ARB_clear_texture on i965
  GL_ARB_compressed_texture_pixel_storage on all drivers
  GL_ARB_conditional_render_inverted on i965, nvc0, softpipe, llvmpipe
  GL_ARB_derivative_control on i965, nv50, nvc0, r600
  GL_ARB_draw_indirect on nvc0, radeonsi
  GL_ARB_explicit_uniform_location (all drivers that support GLSL)
  GL_ARB_fragment_layer_viewport on nv50, nvc0, llvmpipe, r600
  GL_ARB_gpu_shader5 on i965/gen7, nvc0
  GL_ARB_multi_draw_indirect on nvc0, radeonsi
  GL_ARB_sample_shading on radeonsi
  GL_ARB_seamless_cubemap_per_texture on i965, llvmpipe, nvc0, r600, 
radeonsi, softpipe
  GL_ARB_stencil_texturing on nv50, nvc0, r600, and radeonsi
  GL_ARB_texture_barrier on nv50, nvc0, r300, r600, radeonsi
  GL_ARB_texture_compression_bptc on i965/gen7+, nvc0, r600/evergreen+, 
radeonsi
  GL_ARB_texture_cube_map_array on radeonsi
  GL_ARB_texture_gather on r600, radeonsi
  GL_ARB_texture_query_levels on nv50, nvc0, llvmpipe, r600, radeonsi, 
softpipe
  GL_ARB_texture_query_lod on r600, radeonsi
  GL_ARB_viewport_array on nvc0
  GL_AMD_vertex_shader_viewport_index on i965/gen7+, r600
  GL_OES_compressed_ETC1_RGB8_texture on nv30, nv50, nvc0, r300, r600, 
radeonsi, softpipe, llvmpipe
  GLX_MESA_query_renderer on nv30, nv50, nvc0, r300, r600, radeonsi, 
softpipe, llvmpipe
  A new software rasterizer driver (kms_swrast_dri.so) that works with DRM 
drivers that don't have a full-fledged GEM (such as qxl or simpledrm)
  Distribute the Khronos GL/glcorearb.h header file.

  Changes
  Removed support for the GL_ATI_envmap_bumpmap extension
  The hacky --enable-32/64-bit is no longer available in configure. To 
build 32/64 bit mesa refer to the default method recommended by your 
distribution

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

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


[Touch-packages] [Bug 1370146] Re: Adjust header behaviour UI in multi select mode

2014-09-29 Thread Tim Peeters
** Changed in: ubuntu-ui-toolkit
   Importance: Medium = High

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

Title:
  Adjust header behaviour  UI in multi select mode

Status in Address Book App:
  Confirmed
Status in Dialer app for Ubuntu Touch:
  Confirmed
Status in Messaging App:
  Confirmed
Status in Clock application for Ubuntu devices:
  Fix Released
Status in Ubuntu UI Toolkit:
  In Progress
Status in Ubuntu UX bugs:
  Fix Released
Status in “address-book-app” package in Ubuntu:
  Confirmed
Status in “dialer-app” package in Ubuntu:
  Confirmed
Status in “messaging-app” package in Ubuntu:
  Confirmed
Status in “ubuntu-ui-toolkit” package in Ubuntu:
  In Progress

Bug description:
  Steps to reproduce:

  1. Open Messaging app (or Address Book app, Phone app), make sure you have a 
list in your messages view
  2. Long press on any of the list items

  Actual Result:
  3. Header is changing and shows an X button on the left hand side and two 
action buttons on the right hand side. Selection checkboxes appear from the 
left hand side.

  Expected result - desired solution:
  - The header should display a BACK button instead of the X on the left hand 
side, same as we have in all other headers
  - Remove the change in the background colour when a list item is selected, 
change in the colour of the checkbox is enough
  - Add labels for all visible actions in this mode in the header, except for 
'BACK'
  - Tapping on the BACK in this mode, cancels the multi-select mode and does 
NOT navigate back to the previous view
  - There is no title in this header

  Please see attached wireframe for reference. This change applies
  across all apps which use a multi select in their list views.

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

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


[Touch-packages] [Bug 1374521] Re: auto interfaces do not come up with r/o images

2014-09-29 Thread Martin Pitt
ifup@.service works as intended. The idea is that /etc/init.d/networking
brings up all auto interfaces, and that unit takes care of the
hotplugged interfaces only.

The problem is that /etc/init.d/networking (or something it calls)
doesn't work if / is read-only. I'll investigate what it's trying to do.

** Summary changed:

- ifup should specify '-allow=auto' not '-allow=hotplug'
+ auto interfaces do not come up with r/o images

** Package changed: systemd (Ubuntu) = ifupdown (Ubuntu)

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

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

Title:
  auto interfaces do not come up with r/o images

Status in “ifupdown” package in Ubuntu:
  New

Bug description:
  /lib/systemd/system/ifup@.service specifies:

    ExecStart=/sbin/ifup --allow=hotplug %I

  This really needs to be:

    ExecStart=/sbin/ifup --allow=auto %I

  Since otherwise, for systems that don't use network-manager, the
  service will only bring up interfaces which have specified allow-
  hotplug $if in /etc/network/interfaces*.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: systemd 208-8ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3
  Uname: Linux 3.16.0-17-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Sep 26 16:54:12 2014
  InstallationDate: Installed on 2014-04-11 (167 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409)
  SourcePackage: systemd
  UpgradeStatus: Upgraded to utopic on 2014-05-08 (141 days ago)

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

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


[Touch-packages] [Bug 1375249] [NEW] telepathy-ofono tries to open /proc/1728/fd/ and is DENIED access by apparmor

2014-09-29 Thread David Barth
Public bug reported:

I noticed quite a few occurences of these in my logs:

hablet@ubuntu-phablet:/usr/share/ofono/scripts$ sudo dmesg  | grep -i ofo
[sudo] password for phablet: 
[   16.814527] type=1400 audit(1411984297.763:93): apparmor=DENIED 
operation=open profile=/usr/lib/telepathy/telepathy-ofono 
name=/proc/1728/fd/ pid=1728 comm=telepathy-ofono requested_mask=r 
denied_mask=r fsuid=32011 ouid=32011
[   16.827926] type=1400 audit(1411984297.783:94): apparmor=DENIED 
operation=exec profile=/usr/lib/telepathy/telepathy-ofono 
name=/usr/bin/pulseaudio pid=1728 comm=telepathy-ofono requested_mask=x 
denied_mask=x fsuid=32011 ouid=0
[   16.843247] type=1400 audit(1411984297.793:95): apparmor=DENIED 
operation=open profile=/usr/lib/telepathy/telepathy-ofono 
name=/proc/1729/fd/ pid=1729 comm=telepathy-ofono requested_mask=r 
denied_mask=r fsuid=32011 ouid=32011
[   16.865588] type=1400 audit(1411984297.813:96): apparmor=DENIED 
operation=exec profile=/usr/lib/telepathy/telepathy-ofono 
name=/usr/bin/pulseaudio pid=1729 comm=telepathy-ofono requested_mask=x 
denied_mask=x fsuid=32011 ouid=0
[   16.878315] type=1400 audit(1411984297.833:97): apparmor=DENIED 
operation=open profile=/usr/lib/telepathy/telepathy-ofono 
name=/proc/1735/fd/ pid=1735 comm=telepathy-ofono requested_mask=r 
denied_mask=r fsuid=32011 ouid=32011
[   16.882130] type=1400 audit(1411984297.833:98): apparmor=DENIED 
operation=exec profile=/usr/lib/telepathy/telepathy-ofono 
name=/usr/bin/pulseaudio pid=1735 comm=telepathy-ofono requested_mask=x 
denied_mask=x fsuid=32011 ouid=0

Not sure how bad that is. But incidentally, I have not been able to get
my new SIM to be recognized by the system.

This is on an N4 running utopic, image #257

** Affects: telepathy-mission-control-5 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  telepathy-ofono tries to open /proc/1728/fd/ and is DENIED access by
  apparmor

Status in “telepathy-mission-control-5” package in Ubuntu:
  New

Bug description:
  I noticed quite a few occurences of these in my logs:

  hablet@ubuntu-phablet:/usr/share/ofono/scripts$ sudo dmesg  | grep -i ofo
  [sudo] password for phablet: 
  [   16.814527] type=1400 audit(1411984297.763:93): apparmor=DENIED 
operation=open profile=/usr/lib/telepathy/telepathy-ofono 
name=/proc/1728/fd/ pid=1728 comm=telepathy-ofono requested_mask=r 
denied_mask=r fsuid=32011 ouid=32011
  [   16.827926] type=1400 audit(1411984297.783:94): apparmor=DENIED 
operation=exec profile=/usr/lib/telepathy/telepathy-ofono 
name=/usr/bin/pulseaudio pid=1728 comm=telepathy-ofono requested_mask=x 
denied_mask=x fsuid=32011 ouid=0
  [   16.843247] type=1400 audit(1411984297.793:95): apparmor=DENIED 
operation=open profile=/usr/lib/telepathy/telepathy-ofono 
name=/proc/1729/fd/ pid=1729 comm=telepathy-ofono requested_mask=r 
denied_mask=r fsuid=32011 ouid=32011
  [   16.865588] type=1400 audit(1411984297.813:96): apparmor=DENIED 
operation=exec profile=/usr/lib/telepathy/telepathy-ofono 
name=/usr/bin/pulseaudio pid=1729 comm=telepathy-ofono requested_mask=x 
denied_mask=x fsuid=32011 ouid=0
  [   16.878315] type=1400 audit(1411984297.833:97): apparmor=DENIED 
operation=open profile=/usr/lib/telepathy/telepathy-ofono 
name=/proc/1735/fd/ pid=1735 comm=telepathy-ofono requested_mask=r 
denied_mask=r fsuid=32011 ouid=32011
  [   16.882130] type=1400 audit(1411984297.833:98): apparmor=DENIED 
operation=exec profile=/usr/lib/telepathy/telepathy-ofono 
name=/usr/bin/pulseaudio pid=1735 comm=telepathy-ofono requested_mask=x 
denied_mask=x fsuid=32011 ouid=0

  Not sure how bad that is. But incidentally, I have not been able to
  get my new SIM to be recognized by the system.

  This is on an N4 running utopic, image #257

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1375249/+subscriptions

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


[Touch-packages] [Bug 1259251] Re: [browser] Can't copy URLs from the autocomplete list

2014-09-29 Thread Giorgio Venturi
I've marked the bug as incomplete, as it could point to 3 separate
features

1) display suggestions from history and bookmarks - currently available
2) display suggestions from Search Engine - current not available, but planned
3) provide a 'fill address bar' action on search suggestions as in Chrome 
mobile - not planned, but we can discuss it for tablet and desktop browser as 
we have more real estate

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

Title:
  [browser] Can't copy URLs from  the autocomplete list

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

Bug description:
  Steps :
  1- You want to go to http://ubuntu.com/phone
  2- You type ubuntu on the adress bar.
  3- You get a list of URLs from which contains http://ubuntu.com/

  Result:
  - You need to type the FULL URL

  Expected :
  - A button to tell the browser put that url for me on the adresse bar.

  Chrome mobile does provide a button next to each URL on the autocomple
  list, once you click on it you get that URL on the adresse bar so you
  can complete your URL.

  -- SOLUTION --
  The design species the suggestions to be populated by the search engine. ATM 
they only surface bookmarks and history

  https://docs.google.com/a/canonical.com/presentation/d/1Qrd4Flfs3EH-
  fI79IfrYgLdAx2nce-L7ve8NKLCX324/edit#slide=id.g2b64bc8c2_525

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

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


[Touch-packages] [Bug 1359262] Re: Chrome + Radeon + hardware acceleration: black Google maps tab

2014-09-29 Thread Maarten Lankhorst
ScottK, the upload was acked by infinity:
http://irclogs.ubuntu.com/2014/09/24/%23ubuntu-release.html

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

Title:
  Chrome + Radeon + hardware acceleration: black Google maps tab

Status in “mesa” package in Ubuntu:
  Confirmed

Bug description:
  When opening Google Maps, i got a completely black tab instead - see
  the attached image.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.3
  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: Wed Aug 20 17:29:32 2014
  DistUpgraded: 2014-04-04 15:34:47,605 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 5430] 
[1002:68e1] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Caicos [Radeon HD 
5450] [174b:3000]
  InstallationDate: Installed on 2012-11-15 (643 days ago)
  InstallationMedia: Ubuntu-Server 12.10 Quantal Quetzal - Release amd64 
(20121017.2)
  MachineType: Intel Corporation Shark Bay Client platform
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic 
root=UUID=5f908618-7000-4276-855c-8ec7a19ce316 ro crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M
  SourcePackage: mesa
  UpgradeStatus: Upgraded to trusty on 2014-04-04 (138 days ago)
  dmi.bios.date: 01/28/2013
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: HSWLPTU1.86C.0109.R03.1301282055
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Flathead Creek Crb
  dmi.board.vendor: Intel Corp.
  dmi.board.version: 2
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrHSWLPTU1.86C.0109.R03.1301282055:bd01/28/2013:svnIntelCorporation:pnSharkBayClientplatform:pvr0.1:rvnIntelCorp.:rnFlatheadCreekCrb:rvr2:cvnIntelCorporation:ct3:cvr0.1:
  dmi.product.name: Shark Bay Client platform
  dmi.product.version: 0.1
  dmi.sys.vendor: Intel Corporation
  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: Wed Aug 20 11:04:41 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2
  xserver.video_driver: radeon

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

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


  1   2   3   4   5   >