date:20140716

Public bug reported:

The latest 'proposed' systemd-shim 6.3-ubuntu1 package install cgmanager. As a 
result X is first killed and then its impossible to login again.
This happen on Utopic i386 with unity-greeter, systemd-boot and a gtx 750 
nvidia card.

The bad experience:
- trying to purge cgmanager also wants to remove a bunch of packages that will 
deeply break the system
- X can be started but the login always fail
- there is no way to open a terminal (ctrl+t) or (ctrl+alt+t) from X
- even cant get a command line

** Affects: systemd-shim (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bot-stop-nagging regression-proposed systemd-boot utopic

** Tags added: regression-proposed systemd-boot utopic

** Description changed:

- The latest 'proposed' systemd-shim package install cgmanager. As a result X 
is first kill and then its impossible to login again.
+ The latest 'proposed' systemd-shim package install cgmanager. As a result X 
is first killed and then its impossible to login again.
  This happen on Utopic i386 with unity-greeter, systemd-boot and a gtx 750 
nvidia card.
  
  The bad experience:
  - trying to purge cgmanager also wants to remove a bunch of packages that 
will deeply break the system
  - X can be started but the login always fail
  - there is no way to open a terminal (ctrl+t) or (ctrl+alt+t) from X
  - even cant get a command line

** Tags added: bot-stop-nagging

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

Title:
  [utopic] [proposed] cgmanager breaks lightdm login

Status in “systemd-shim” package in Ubuntu:
  New

Bug description:
  The latest 'proposed' systemd-shim 6.3-ubuntu1 package install cgmanager. As 
a result X is first killed and then its impossible to login again.
  This happen on Utopic i386 with unity-greeter, systemd-boot and a gtx 750 
nvidia card.

  The bad experience:
  - trying to purge cgmanager also wants to remove a bunch of packages that 
will deeply break the system
  - X can be started but the login always fail
  - there is no way to open a terminal (ctrl+t) or (ctrl+alt+t) from X
  - even cant get a command line

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

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

[Touch-packages] [Bug 1342586] Re: [utopic] [proposed] cgmanager breaks lightdm login

** Description changed:

- The latest 'proposed' systemd-shim package install cgmanager. As a result X 
is first killed and then its impossible to login again.
+ The latest 'proposed' systemd-shim 6.3-ubuntu1 package install cgmanager. As 
a result X is first killed and then its impossible to login again.
  This happen on Utopic i386 with unity-greeter, systemd-boot and a gtx 750 
nvidia card.
  
  The bad experience:
  - trying to purge cgmanager also wants to remove a bunch of packages that 
will deeply break the system
  - X can be started but the login always fail
  - there is no way to open a terminal (ctrl+t) or (ctrl+alt+t) from X
  - even cant get a command line

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

Title:
  [utopic] [proposed] cgmanager breaks lightdm login

Status in “systemd-shim” package in Ubuntu:
  New

Bug description:
  The latest 'proposed' systemd-shim 6.3-ubuntu1 package install cgmanager. As 
a result X is first killed and then its impossible to login again.
  This happen on Utopic i386 with unity-greeter, systemd-boot and a gtx 750 
nvidia card.

  The bad experience:
  - trying to purge cgmanager also wants to remove a bunch of packages that 
will deeply break the system
  - X can be started but the login always fail
  - there is no way to open a terminal (ctrl+t) or (ctrl+alt+t) from X
  - even cant get a command line

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

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

[Touch-packages] [Bug 1189939] Re: Initialization leaks file descriptors to /prox/self/auxv

2014-07-16 Thread Christian

Works for me with libjpeg-turbo8 version 1.1.90+svn733-0ubuntu4.4.
thanks!

** 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 libjpeg-turbo in Ubuntu.
https://bugs.launchpad.net/bugs/1189939

Title:
  Initialization leaks file descriptors to /prox/self/auxv

Status in “libjpeg-turbo” package in Ubuntu:
  Invalid
Status in “libjpeg-turbo” source package in Precise:
  Fix Committed
Status in “libjpeg-turbo” source package in Quantal:
  Invalid
Status in “libjpeg-turbo” source package in Raring:
  Invalid
Status in “libjpeg-turbo” source package in Saucy:
  Invalid

Bug description:
  [impact]
  In precise only, an Ubuntu-specific patch (FixLibraryStartup.patch) causes 
/proc/self/auxv to be opened on library initialization, but the file is never 
closed.  For long running processes that periodically re-initialize the library 
(Firefox's plugin-container loading the VLC plugin for me), this leads to the 
available file descriptors being exhausted.

  This also causes
  https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1177684.

  [test case]
  Fresh and clean Ubuntu Precise 12.04.2 install

  # apt-get install apache2-mpm-itk libapache2-mod-php5 php5-gd

  Restart Apache to ensure gd.so is loaded

  # for pid in `pidof apache2`; do find /proc/$pid/fd -ls; done | awk '/auxv/ 
{print $11 $12 $13}'
  # apache2ctl graceful
  # for pid in `pidof apache2`; do find /proc/$pid/fd -ls; done | awk '/auxv/ 
{print $11 $12 $13}'
  # apache2ctl graceful
  # for pid in `pidof apache2`; do find /proc/$pid/fd -ls; done | awk '/auxv/ 
{print $11 $12 $13}'
  .. etc

  [regression potential]
  This affects patch designed for ARM. Although all it does it properly close 
the file descriptor, I have not specifically tested it on ARM.

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

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

[Touch-packages] [Bug 1342602] [NEW] Cannot make or receive calls on #133 (and possibly before) mako

2014-07-16 Thread Alan Pope ㋛

Public bug reported:

Can't receive calls (they go direct to answer phone)
Can't make calls (dial button is greyed out)
Signal indicator shows no bars.

Swapped SIM with another phone to confirm it's the phone/software and
not the SIM.

phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-modems
[ /ril_0 ]
Manufacturer = Fake Manufacturer
Features = sim 
Type = hardware
Model = Fake Modem Model
Lockdown = 0
Serial = 355136054298131
Interfaces = org.ofono.SimManager 
Powered = 1
Emergency = 0
Revision = M9615A-CEFWMAZM-2.0.1700.84
Online = 0
[ org.ofono.SimManager ]
Present = 0

phablet@ubuntu-phablet:~$ nmcli d

** (process:3361): CRITICAL **: dbus_g_proxy_add_signal: assertion
'g_dbus_is_member_name (signal_name)' failed

** (process:3361): CRITICAL **: dbus_g_proxy_connect_signal: assertion
'g_dbus_is_member_name (signal_name)' failed

** (process:3361): WARNING **: demarshal_generic: NMAccessPoint/last-
seen (type guint) couldn't be set with type gint.

** (process:3361): WARNING **: handle_property_changed: failed to update
property 'last-seen' of object type NMAccessPoint.

** (process:3361): WARNING **: demarshal_generic: NMAccessPoint/last-
seen (type guint) couldn't be set with type gint.

** (process:3361): WARNING **: handle_property_changed: failed to update
property 'last-seen' of object type NMAccessPoint.

** (process:3361): WARNING **: demarshal_generic: NMAccessPoint/last-
seen (type guint) couldn't be set with type gint.

** (process:3361): WARNING **: handle_property_changed: failed to update
property 'last-seen' of object type NMAccessPoint.

** (process:3361): WARNING **: demarshal_generic: NMAccessPoint/last-
seen (type guint) couldn't be set with type gint.

** (process:3361): WARNING **: handle_property_changed: failed to update
property 'last-seen' of object type NMAccessPoint.

** (process:3361): WARNING **: demarshal_generic: NMAccessPoint/last-
seen (type guint) couldn't be set with type gint.

** (process:3361): WARNING **: handle_property_changed: failed to update
property 'last-seen' of object type NMAccessPoint.

** (process:3361): WARNING **: demarshal_generic: NMAccessPoint/last-
seen (type guint) couldn't be set with type gint.

** (process:3361): WARNING **: handle_property_changed: failed to update 
property 'last-seen' of object type NMAccessPoint.
DEVICE TYPE  STATE
/ril_0 gsm   disconnected 
wlan0  802-11-wireless   connected

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

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

Title:
  Cannot make or receive calls on #133 (and possibly before) mako

Status in “telephony-service” package in Ubuntu:
  New

Bug description:
  Can't receive calls (they go direct to answer phone)
  Can't make calls (dial button is greyed out)
  Signal indicator shows no bars.

  Swapped SIM with another phone to confirm it's the phone/software and
  not the SIM.

  phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-modems
  [ /ril_0 ]
  Manufacturer = Fake Manufacturer
  Features = sim 
  Type = hardware
  Model = Fake Modem Model
  Lockdown = 0
  Serial = 355136054298131
  Interfaces = org.ofono.SimManager 
  Powered = 1
  Emergency = 0
  Revision = M9615A-CEFWMAZM-2.0.1700.84
  Online = 0
  [ org.ofono.SimManager ]
  Present = 0

  phablet@ubuntu-phablet:~$ nmcli d

  ** (process:3361): CRITICAL **: dbus_g_proxy_add_signal: assertion
  'g_dbus_is_member_name (signal_name)' failed

  ** (process:3361): CRITICAL **: dbus_g_proxy_connect_signal: assertion
  'g_dbus_is_member_name (signal_name)' failed

  ** (process:3361): WARNING **: demarshal_generic: NMAccessPoint/last-
  seen (type guint) couldn't be set with type gint.

  ** (process:3361): WARNING **: handle_property_changed: failed to
  update property 'last-seen' of object type NMAccessPoint.

  ** (process:3361): WARNING **: demarshal_generic: NMAccessPoint/last-
  seen (type guint) couldn't be set with type gint.

  ** (process:3361): WARNING **: handle_property_changed: failed to
  update property 'last-seen' of object type NMAccessPoint.

  ** (process:3361): WARNING **: demarshal_generic: NMAccessPoint/last-
  seen (type guint) couldn't be set with type gint.

  ** (process:3361): WARNING **: handle_property_changed: failed to
  update property 'last-seen' of object type NMAccessPoint.

  ** (process:3361): WARNING **: demarshal_generic: NMAccessPoint/last-
  seen (type guint) couldn't be set with type gint.

  ** (process:3361): WARNING **: handle_property_changed: failed to
  update property 'last-seen' of object type NMAccessPoint.

  ** (process:3361): WARNING **: demarshal_generic: NMAccessPoint/last-
  seen (type guint) couldn't be set

[Touch-packages] [Bug 1342609] [NEW] altspace on windowless desktop opens window accessibility menu

2014-07-16 Thread Krister

Public bug reported:

1. Go to a desktop with now windows open.
2. Press altspace.
3. See that the window accessibility menu opens.

Clicking on entries in this menu causes problems with Unity.
For example if you click on Move Workspace Left, then many graphical issues 
arrise.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.1+14.04.20140513-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
Uname: Linux 3.13.0-30-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Wed Jul 16 11:11:27 2014
InstallationDate: Installed on 2013-10-03 (285 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
SourcePackage: unity
UpgradeStatus: Upgraded to trusty on 2014-04-23 (83 days ago)

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


** Tags: amd64 apport-bug third-party-packages trusty

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

Title:
  altspace on windowless desktop opens window accessibility menu

Status in “unity” package in Ubuntu:
  New

Bug description:
  1. Go to a desktop with now windows open.
  2. Press altspace.
  3. See that the window accessibility menu opens.

  Clicking on entries in this menu causes problems with Unity.
  For example if you click on Move Workspace Left, then many graphical issues 
arrise.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.1+14.04.20140513-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Wed Jul 16 11:11:27 2014
  InstallationDate: Installed on 2013-10-03 (285 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-04-23 (83 days ago)

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

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

[Touch-packages] [Bug 1342151] Re: [Indicators] Silent mode control in the indicator

2014-07-16 Thread Daniela Ferrai

** Description changed:

  Should the indicator expose the control for silent mode for easy access?
  
  Implementing in settings now but would like to leverage a common
  implementation
+ 
+ --
+ 
+ I've attached a wireframe which shows an additional setting in the sound
+ indicator for turning on and off silent mode.

** Attachment added: Wireframe of new silent toggle under sound indicator
   
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1342151/+attachment/4153798/+files/silent%20wireframe.png

** Changed in: ubuntu-ux
   Status: New = Fix Committed

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

Title:
  [Indicators] Silent mode control in the indicator

Status in Ubuntu UX bugs:
  Fix Committed
Status in “indicator-sound” package in Ubuntu:
  Confirmed

Bug description:
  Should the indicator expose the control for silent mode for easy
  access?

  Implementing in settings now but would like to leverage a common
  implementation

  --

  I've attached a wireframe which shows an additional setting in the
  sound indicator for turning on and off silent mode.

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

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

[Touch-packages] [Bug 1342602] Re: Cannot make or receive calls on #133 (and possibly before) mako

2014-07-16 Thread Alan Pope ㋛

Something odd has happened to this phone. I have now reverted all the
way back to #119 (the last promoted image) - without wiping my device -
and the cell modem still doesn't work. Seems like something has wedged
it in an off state and I can't switch it back on again.

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

Title:
  Cannot make or receive calls on #133 (and possibly before) mako

Status in “telephony-service” package in Ubuntu:
  New

Bug description:
  Can't receive calls (they go direct to answer phone)
  Can't make calls (dial button is greyed out)
  Signal indicator shows no bars.

  Swapped SIM with another phone to confirm it's the phone/software and
  not the SIM.

  phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-modems
  [ /ril_0 ]
  Manufacturer = Fake Manufacturer
  Features = sim 
  Type = hardware
  Model = Fake Modem Model
  Lockdown = 0
  Serial = 355136054298131
  Interfaces = org.ofono.SimManager 
  Powered = 1
  Emergency = 0
  Revision = M9615A-CEFWMAZM-2.0.1700.84
  Online = 0
  [ org.ofono.SimManager ]
  Present = 0

  phablet@ubuntu-phablet:~$ nmcli d

  ** (process:3361): CRITICAL **: dbus_g_proxy_add_signal: assertion
  'g_dbus_is_member_name (signal_name)' failed

  ** (process:3361): CRITICAL **: dbus_g_proxy_connect_signal: assertion
  'g_dbus_is_member_name (signal_name)' failed

  ** (process:3361): WARNING **: demarshal_generic: NMAccessPoint/last-
  seen (type guint) couldn't be set with type gint.

  ** (process:3361): WARNING **: handle_property_changed: failed to
  update property 'last-seen' of object type NMAccessPoint.

  ** (process:3361): WARNING **: demarshal_generic: NMAccessPoint/last-
  seen (type guint) couldn't be set with type gint.

  ** (process:3361): WARNING **: handle_property_changed: failed to
  update property 'last-seen' of object type NMAccessPoint.

  ** (process:3361): WARNING **: demarshal_generic: NMAccessPoint/last-
  seen (type guint) couldn't be set with type gint.

  ** (process:3361): WARNING **: handle_property_changed: failed to
  update property 'last-seen' of object type NMAccessPoint.

  ** (process:3361): WARNING **: demarshal_generic: NMAccessPoint/last-
  seen (type guint) couldn't be set with type gint.

  ** (process:3361): WARNING **: handle_property_changed: failed to
  update property 'last-seen' of object type NMAccessPoint.

  ** (process:3361): WARNING **: demarshal_generic: NMAccessPoint/last-
  seen (type guint) couldn't be set with type gint.

  ** (process:3361): WARNING **: handle_property_changed: failed to
  update property 'last-seen' of object type NMAccessPoint.

  ** (process:3361): WARNING **: demarshal_generic: NMAccessPoint/last-
  seen (type guint) couldn't be set with type gint.

  ** (process:3361): WARNING **: handle_property_changed: failed to update 
property 'last-seen' of object type NMAccessPoint.
  DEVICE TYPE  STATE
  /ril_0 gsm   disconnected 
  wlan0  802-11-wireless   connected

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

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

[Touch-packages] [Bug 1222705] Re: init assert failure: alloc.c:633: Assertion failed in nih_unref: ref != NULL

2014-07-16 Thread James Hunt

** Branch linked: lp:~jamesodhunt/upstart/bug-1222705-reprise

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

Title:
  init assert failure: alloc.c:633: Assertion failed in nih_unref: ref
  != NULL

Status in Upstart:
  Confirmed
Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  Occurred immediately after bug 1222702 happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: upstart 1.10-0ubuntu1 [modified: 
usr/share/upstart/sessions/upstart-file-bridge.conf]
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: i386
  AssertionMessage: alloc.c:633: Assertion failed in nih_unref: ref != NULL
  Date: Mon Sep  9 09:44:34 2013
  ExecutablePath: /sbin/init
  InstallationDate: Installed on 2010-10-21 (1054 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  MarkForUpload: True
  ProcCmdline: init --user
  ProcEnviron:
   LANGUAGE=en_GB
   PATH=(custom, user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: upstart
  StacktraceTop:
   nih_unref () from /lib/i386-linux-gnu/libnih.so.1
   ?? ()
   ?? ()
   ?? ()
   nih_child_poll () from /lib/i386-linux-gnu/libnih.so.1
  Title: init assert failure: alloc.c:633: Assertion failed in nih_unref: ref 
!= NULL
  UpgradeStatus: Upgraded to saucy on 2013-06-23 (77 days ago)
  UpstartBugCategory: Session
  UpstartRunningSessionCount: 1
  UpstartRunningSessionVersion: init (upstart 1.10)
  UpstartRunningSystemVersion: init (upstart 1.10)
  UserGroups: adm admin audio cdrom dialout kvm libvirtd lpadmin plugdev 
sambashare sbuild vboxusers
  upstart.shutdown.override: manual

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

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

[Touch-packages] [Bug 1342568] Re: bluetooth connect fails

2014-07-16 Thread JPTTEST

Enabled debugging by adding -d to /etc/init/bluetooth.conf
But I don't understand what exactly is going on and why it fails.

I stripped pid, date (except secs) and hostname from log.

** Attachment added: debug log

https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1342568/+attachment/4153829/+files/bluetooth.log

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

Title:
bluetooth connect fails

Status in “bluez” package in Ubuntu:
New

Bug description:
I want to connect to a BT-serial adapter. Always get the error
Unknown command complete for opcode 37.

If I supply the correct pin, connection is reported successful, but
the device immediately disappears.

I tried three different host BT hardware and two different PCs. always
the same.

Kubuntu 14.04
Bluez-4.101-ubuntu13

syslog: First with correct pin, second using wrong pin:

bluetoothd[1107]: Discovery session 0x7f66d5221040 with :1.117 activated
bluetoothd[1107]: Unknown command complete for opcode 37
bluetoothd[1107]: Stopping discovery

bluetoothd[1107]: Discovery session 0x7f66d52209a0 with :1.118 activated
bluetoothd[1107]: Unknown command complete for opcode 37
bluetoothd[1107]: Stopping discovery
bluetoothd[1107]: hci0: Cancel Pair Device (0x001a) failed: Invalid
Parameters (0x0d)

How do I enable more detailed logging?

I am quite sure this is no duplicate of those BT-suspend bugs. Because
it always fails and the rfkill workaround doesn't help.

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

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

[Touch-packages] [Bug 1342586] Re: [utopic] [proposed] cgmanager breaks lightdm login

Feedback from a recovery boot:

/var/crash:

get a _lib_systemd_systemd.0.crash :
systemd assert failure: alloc.c:315: Assertion failed in nih_free: ptr !=NULL

StacktraceTop:
__GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
__GI_abort() at abort.c:89
nih_free() from /lib/i386-linux-gnu/libnih.so.1


.xsession-errors:

x-session-manager: could not get session id for session. Check that
logind is properly installed and pam_systemd is getting used at login.
Connection refused.

initctl: UPSTART_SESSION isn't set in the environment. Unable to locate
the Upstart instance.

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

Title:
  [utopic] [proposed] cgmanager breaks lightdm login

Status in “systemd-shim” package in Ubuntu:
  New

Bug description:
  The latest 'proposed' systemd-shim 6.3-ubuntu1 package install cgmanager. As 
a result X is first killed and then its impossible to login again.
  This happen on Utopic i386 with unity-greeter, systemd-boot and a gtx 750 
nvidia card.

  The bad experience:
  - trying to purge cgmanager also wants to remove a bunch of packages that 
will deeply break the system
  - X can be started but the login always fail
  - there is no way to open a terminal (ctrl+t) or (ctrl+alt+t) from X
  - even cant get a command line

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

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

[Touch-packages] [Bug 1329141] Re: qmlscene crashed while running test_can_launch_multiple_applications

2014-07-16 Thread Tim Peeters

We get a lot of failures in autolanding lately, with errors like:

  File /usr/lib/python2.7/dist-packages/psutil/__init__.py, line 331, in _init
raise NoSuchProcess(pid, None, msg)
NoSuchProcess: no process found with pid 4908

See https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-
mako/2289/testReport/junit/ubuntuuitoolkit.tests.custom_proxy_objects.test_textfield/TextFieldTestCase/test_select_all_selects_all_text/


Is it caused by this bug?

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

Title:
  qmlscene crashed while running test_can_launch_multiple_applications

Status in Ubuntu Application Launcher:
  Invalid
Status in “qtubuntu” package in Ubuntu:
  Incomplete

Bug description:
  On the daily image testing for mako, image#78, one of the lifecycle
  management tests in unity failed because of a qmlscene crash (see
  attachment).

  21:15:34.162 INFO _launcher:116 - Attempting to launch application 
'tmp991xm1vf' with URIs '' via upstart-app-launch
  21:15:36.367 INFO _launcher:116 - Attempting to launch application 
'tmpbeb_op_3' with URIs '' via upstart-app-launch
  21:16:08.689 ERROR _launcher:202 - Timed out waiting for Application with 
app_id 'tmpbeb_op_3' to stop.

  
http://ci.ubuntu.com/smokeng/utopic/touch/mako/78:20140611.1:20140530/8530/unity8/1241528/

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

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

[Touch-packages] [Bug 741869] Re: Unity/compiz intercepts Super and Alt keypresses from grabbed windows like VMs.

The trusty-proposed packages with suposedly contain fix for this bug
didn't actually fix it. The Super key is still intercepted in windowed
mode and Dash opens in both VirtualBox (tested with 12.04.4 and 14.04)
and in regular session. When running VirtualBox in fullscreen the Dash
opens only in virtual machine.

Also in virt-manager the Super key isn't intercepted when you open Dash
but is intercepted when you hold the Super key to display shortcuts
overlay.

** Tags added: verification-failed

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

Title:
  Unity/compiz intercepts Super and Alt keypresses from grabbed windows
  like VMs.

Status in Ayatana Design:
  Fix Committed
Status in Compiz:
  Triaged
Status in Compiz Core:
  Triaged
Status in OEM Priority Project:
  Won't Fix
Status in OEM Priority Project precise series:
  Won't Fix
Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in “compiz” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  New
Status in “unity” source package in Trusty:
  New

Bug description:
  [Impact]
  After upgrading from Maverick to Natty, I can no longer use the Super 
(windows) key in Virtual Machine Manager. Previously, as long as I had the 
Virtual Machine Manager console window in the foreground, I could press the 
Super key and the start menu would pop up. Since upgrading to Natty, this no 
longer works, and the search box appears in the upper left.

  Also see bug #934921

  [Test Case]
  (1) Install virtualbox or virt-manager and qemu-system, create and boot a 
virtual machine
  (2) while in the virtual machine (and it should grab the keyboard), press the 
Super key
  Expected Result: the super key acts inside the VM (check by install unity on 
it or using xev)
  Buggy Result: the super key acts in the host and the Unity Dash is displayed

  [regression Potential]This patch plays with key grabs and ungrabs:
  the most likely potential for regression is (a) the existing grabs
  continue and no fix obtains or (2) the grab is not resumed when
  returning control from the VM and the Super key does not invoke the
  Unity Dash.

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

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

[Touch-packages] [Bug 1338984] Re: [Launcher] Icon emblem implementation is not according to the current design

2014-07-16 Thread Michael Zanetti

** Changed in: unity8
   Status: New = In Progress

** Branch linked: lp:~mzanetti/unity8/launcher-new-count-emblem

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

Title:
  [Launcher] Icon emblem implementation is not according to the current
  design

Status in Ubuntu UX bugs:
  Fix Committed
Status in The Unity 8 shell:
  In Progress
Status in “unity8” package in Ubuntu:
  New

Bug description:
  The emblem design has changed from the current semi-transparent to
  opaque ubuntu orange. Implementation needs updating.

  ---
  Desired solution:

  See the attached screenshot. 
  For more precise implementation details and key parameters see the UX 
specification: 
https://docs.google.com/a/canonical.com/document/d/1rNCz_HZIGBNf0Lq568q_iYXWvgmZF6v1jC726gmwlfw/edit#

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

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

[Touch-packages] [Bug 1342663] [NEW] a big bug

2014-07-16 Thread Ericyann

Public bug reported:

help me

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-32.56-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic i686
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Jul 16 11:43:41 2014
DistUpgraded: 2014-06-21 12:40:44,173 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 ndiswrapper, 1.59, 3.11.0-23-generic, i686: installed
 ndiswrapper, 1.59, 3.13.0-30-generic, i686: installed
 ndiswrapper, 1.59, 3.13.0-31-generic, i686: installed
 ndiswrapper, 1.59, 3.13.0-32-generic, i686: installed
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 18) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:1be2]
InstallationDate: Installed on 2013-11-21 (236 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424)
Lsusb:
 Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 003: ID 04f2:b1e5 Chicony Electronics Co., Ltd 
 Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK Computer Inc. K52F
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=06b62b2c-4710-4907-9fd1-47d64944a7c9 ro vesafb.invalid=1 splash quiet
SourcePackage: xorg
UpgradeStatus: Upgraded to trusty on 2014-06-21 (24 days ago)
dmi.bios.date: 03/09/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: K52F.215
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K52F
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK52F.215:bd03/09/2011:svnASUSTeKComputerInc.:pnK52F:pvr1.0:rvnASUSTeKComputerInc.:rnK52F:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: K52F
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
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
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 Jul 16 08:09:30 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 592 
 vendor LGD
xserver.version: 2:1.15.1-0ubuntu2

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


** Tags: apport-bug compiz-0.9 i386 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/1342663

Title:
  a big bug

Status in “xorg” package in Ubuntu:
  New

Bug description:
  help me

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-32.56-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Jul 16 11:43:41 2014
  DistUpgraded: 2014-06-21 12:40:44,173 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   ndiswrapper, 1.59, 3.11.0-23-generic, i686: installed
   ndiswrapper, 1.59, 3.13.0-30-generic, i686: installed
   ndiswrapper, 1.59, 3.13.0-31-generic, i686: installed
   ndiswrapper, 1.59, 3.13.0-32-generic, i686: installed
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 18) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1be2]
  InstallationDate: Installed on 2013-11-21 (236 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424)
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel

Re: [Touch-packages] [Bug 741869] Re: Unity/compiz intercepts Super and Alt keypresses from grabbed windows like VMs.

2014-07-16 Thread Treviño

 The trusty-proposed packages with suposedly contain fix for this bug
 didn't actually fix it. The Super key is still intercepted in windowed
 mode and Dash opens in both VirtualBox (tested with 12.04.4 and 14.04)

That's the correct behavior for now (see the test case, a prerequisite it
full screen), since when VirtualBox doesn't grab the keyboard, the unity
host gets the event and it will display the dash if needed.

 and in regular session. When running VirtualBox in fullscreen the Dash
 opens only in virtual machine.

Fine

 Also in virt-manager the Super key isn't intercepted when you open Dash
 but is intercepted when you hold the Super key to display shortcuts
 overlay.

Mh right... I actually think this is sane since the overlay should alway be
available when requested, since it doesn't need input and thus it doesn't
create any trouble.

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

Title:
  Unity/compiz intercepts Super and Alt keypresses from grabbed windows
  like VMs.

Status in Ayatana Design:
  Fix Committed
Status in Compiz:
  Triaged
Status in Compiz Core:
  Triaged
Status in OEM Priority Project:
  Won't Fix
Status in OEM Priority Project precise series:
  Won't Fix
Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in “compiz” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  New
Status in “unity” source package in Trusty:
  New

Bug description:
  [Impact]
  After upgrading from Maverick to Natty, I can no longer use the Super 
(windows) key in Virtual Machine Manager. Previously, as long as I had the 
Virtual Machine Manager console window in the foreground, I could press the 
Super key and the start menu would pop up. Since upgrading to Natty, this no 
longer works, and the search box appears in the upper left.

  Also see bug #934921

  [Test Case]
  (1) Install virtualbox or virt-manager and qemu-system, create and boot a 
virtual machine
  (2) while in the virtual machine (and it should grab the keyboard), press the 
Super key
  Expected Result: the super key acts inside the VM (check by install unity on 
it or using xev)
  Buggy Result: the super key acts in the host and the Unity Dash is displayed

  [regression Potential]This patch plays with key grabs and ungrabs:
  the most likely potential for regression is (a) the existing grabs
  continue and no fix obtains or (2) the grab is not resumed when
  returning control from the VM and the Super key does not invoke the
  Unity Dash.

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

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

[Touch-packages] [Bug 1307738] Re: Lockscreen caps lock icon drawn under text entry, should be a white icon.

** 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 unity in Ubuntu.
https://bugs.launchpad.net/bugs/1307738

Title:
  Lockscreen caps lock icon drawn under text entry, should be a white
  icon.

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  Fix Released
Status in “unity” source package in Trusty:
  Fix Committed

Bug description:
  Lockscreen caps lock icon drawn under text entry, should be a white
  icon.

  [Inpact]
  The old Caps lock icon was rendering below the Text Entry causeing it to grey 
out. This is hard to see.

  [Test case]
  1) Press Super + L (lockscreen)
  2) Press Caps Lock (unless its already active)

  Expected Result:
    White Caps lock icon.

  [Regression potential]
  Very low, worse case the icon doesn't render correctly, yeilding a grey icon.

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

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

[Touch-packages] [Bug 741869] Re: Unity/compiz intercepts Super and Alt keypresses from grabbed windows like VMs.

Well VirtualBox grabs the keyboard even in widowed mode. At least the
Alt+F2 , Ctrl+Alt+T, Super+S and Super+W shortcuts are properly grabbed.

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

Title:
  Unity/compiz intercepts Super and Alt keypresses from grabbed windows
  like VMs.

Status in Ayatana Design:
  Fix Committed
Status in Compiz:
  Triaged
Status in Compiz Core:
  Triaged
Status in OEM Priority Project:
  Won't Fix
Status in OEM Priority Project precise series:
  Won't Fix
Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in “compiz” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  New
Status in “unity” source package in Trusty:
  New

Bug description:
  [Impact]
  After upgrading from Maverick to Natty, I can no longer use the Super 
(windows) key in Virtual Machine Manager. Previously, as long as I had the 
Virtual Machine Manager console window in the foreground, I could press the 
Super key and the start menu would pop up. Since upgrading to Natty, this no 
longer works, and the search box appears in the upper left.

  Also see bug #934921

  [Test Case]
  (1) Install virtualbox or virt-manager and qemu-system, create and boot a 
virtual machine
  (2) while in the virtual machine (and it should grab the keyboard), press the 
Super key
  Expected Result: the super key acts inside the VM (check by install unity on 
it or using xev)
  Buggy Result: the super key acts in the host and the Unity Dash is displayed

  [regression Potential]This patch plays with key grabs and ungrabs:
  the most likely potential for regression is (a) the existing grabs
  continue and no fix obtains or (2) the grab is not resumed when
  returning control from the VM and the Super key does not invoke the
  Unity Dash.

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

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

[Touch-packages] [Bug 1308911] Re: Clipboard contents are accessible within lockscreen

** 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 unity in Ubuntu.
https://bugs.launchpad.net/bugs/1308911

Title:
  Clipboard contents are accessible within lockscreen

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  Fix Released
Status in “unity” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]
  It's possible to paste clipboard content into the lockscreen text fields

  [Testcase]
  1. Copy some text
  2. Lock the screen (Super+L or Ctrl+Alt+L)
  3. Try to paste the contents of your clipboard using Ctrl+V into the 
lockscreen input(s)
 field.
  4. Nothing should be pasted there

  [Regression Potential]
  Anything known

  ---

  - Copy e.g. my password to the clipboard (highlight and/or Ctrl+C)
  - Lock the screen (Ctrl+Alt+L)
  - Paste content from clipboard using middle mouse button or Ctrl+V into input 
field
  - Login possible (if copied text was the password)

  Expected behaviour:
  No content from clipboard available at all in lockscreen

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

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

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

[Touch-packages] [Bug 1189939] Re: Initialization leaks file descriptors to /proc/self/auxv

2014-07-16 Thread Colin Watson

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

** Summary changed:

- Initialization leaks file descriptors to /prox/self/auxv
+ Initialization leaks file descriptors to /proc/self/auxv

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

Title:
  Initialization leaks file descriptors to /proc/self/auxv

Status in “libjpeg-turbo” package in Ubuntu:
  Invalid
Status in “libjpeg-turbo” source package in Precise:
  Fix Released
Status in “libjpeg-turbo” source package in Quantal:
  Invalid
Status in “libjpeg-turbo” source package in Raring:
  Invalid
Status in “libjpeg-turbo” source package in Saucy:
  Invalid

Bug description:
  [impact]
  In precise only, an Ubuntu-specific patch (FixLibraryStartup.patch) causes 
/proc/self/auxv to be opened on library initialization, but the file is never 
closed.  For long running processes that periodically re-initialize the library 
(Firefox's plugin-container loading the VLC plugin for me), this leads to the 
available file descriptors being exhausted.

  This also causes
  https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1177684.

  [test case]
  Fresh and clean Ubuntu Precise 12.04.2 install

  # apt-get install apache2-mpm-itk libapache2-mod-php5 php5-gd

  Restart Apache to ensure gd.so is loaded

  # for pid in `pidof apache2`; do find /proc/$pid/fd -ls; done | awk '/auxv/ 
{print $11 $12 $13}'
  # apache2ctl graceful
  # for pid in `pidof apache2`; do find /proc/$pid/fd -ls; done | awk '/auxv/ 
{print $11 $12 $13}'
  # apache2ctl graceful
  # for pid in `pidof apache2`; do find /proc/$pid/fd -ls; done | awk '/auxv/ 
{print $11 $12 $13}'
  .. etc

  [regression potential]
  This affects patch designed for ARM. Although all it does it properly close 
the file descriptor, I have not specifically tested it on ARM.

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

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

[Touch-packages] [Bug 1313280] Re: Fullscreen window set to Always on Top in single-monitor will hide the lockscreen

Packages from trusty-proposed resolve this bug.

I've checked with Totem, VLC, Firefox and Opera-developer. Also the
indicators were drawn in lockscreen.

** 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 unity in Ubuntu.
https://bugs.launchpad.net/bugs/1313280

Title:
  Fullscreen window set to Always on Top in single-monitor will hide
  the lockscreen

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  Fix Released
Status in “unity” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]
  A fullscreen window set to always on top hides the lockscreem.

  [Test Case]
  (1) Open a video in Totem
  (2) Right-click on the titlebar and set Totem to Always on Top
  (3) Make Totem full screen (eg. with the F11 key or clicking on the control)
  (4) Manually Lock the screen using Super+L

  (5) The lockscreen should go above the Totem window now.

  If you don't lock it manually and just pause the video and let it lock
  automatically this will show the same behavior.

  The same behavior occurs with any application that can enter full
  screen mode.

  [Regression Potential]Two cases may potentially source regressions.
  (1) windows that need to appear above the lockscreen, such as on-screen 
keyboards,(2) applications presenting fullscreen windows using unusual or 
non-standard toolkits.It is unlikely that regressions in either of these cases 
would be introduced by this bug fix, but rather would be pre-existing problems 
not fixed here.
  (3) Indicator menus might be not being drawn

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

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

[Touch-packages] [Bug 1310200] Re: Indicators disappear at the panel (clementine, dropbox, skype etc)

I've only checked with Clementine so it probably should be also looked
at by people using Skype and Dropbox.

** 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 unity in Ubuntu.
https://bugs.launchpad.net/bugs/1310200

Title:
  Indicators disappear at the panel (clementine, dropbox, skype etc)

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  Fix Released
Status in “unity” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]
  Some indicators icons (such as skype, clementine, dropbox) disappear from 
panel when changing graphical state.

  [Test case]
  1. Run one of the affected software (i.e. skype)
  2. The skype icon should show in the unity panel
  3. Change your status in skype to something else (i.e. Away)
  4. The skype icon in the panel should change without disappearing

  [Regression potential]
  Nothing known, the icons database is reloaded for safety checks and this does 
nothing but updating the icons.

  

  
  Unconstant indicators (which are changig their graphical state during work of 
the app, for example skype, clemetine) disappears on the panel. They appear 
again if you click the mouse on th closest rightest indicator and pull it into 
left side or they appear after some time.

  ProblemType: BugDistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140416-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6
  Uname: Linux 3.11.0-20-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sun Apr 20 12:26:14 2014
  InstallationDate: Installed on 2014-01-14 (95 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (1 days ago)

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

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

[Touch-packages] [Bug 1316005] Re: Panel shadow appears over full screen applications w/ locally integrated menus enabled

** 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 unity in Ubuntu.
https://bugs.launchpad.net/bugs/1316005

Title:
  Panel shadow appears over full screen applications w/ locally
  integrated menus enabled

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  Fix Released
Status in “unity” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  An ugly Panel shadow can be drawn over full screen windows which is
  visually unappealing.

  [Test Case]

  1. Enable local menus.  System Settings-Appearance-Behavior and then select 
In the window's title bar in the Show the menus for a window section.
  2. Open an image in Image Viewer
  3. Double click the image to full-screen it
  4. Move the mouse to the top of the screen to access the controls

  [Regression Potential]

  None identified.

  Original Description:

  The shadow of the top Unity panel draws over full screen applications
  that have controls visible when the mouse is moved.

  Steps to reproduce:

  1) Open an image in Image Viewer
  2) Double click the image to full-screen it
  3) Move the mouse to the top of the screen to access the controls

  Expected behavior:

  Only the image and the Image Viewer controls should be visible

  Acutal behavior:

  The Unity panel shadow is drawn on top of the controls at the top of
  the screen

  Notes:

  This also appears in the Videos application, but does not in VLC or
  gimp. I believe it is GTK applications with UI elements that only
  appear on mouse movement (gimp's UI is static, and I believe VLC is Qt
  based).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3
  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: Sun May  4 22:37:44 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed
   nvidia-331, 331.38, 3.13.0-24-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GK107M [GeForce GTX 660M] [10de:0fd4] (rev a1) (prog-if 
00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:2117]
  InstallationDate: Installed on 2014-04-19 (15 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: ASUSTeK COMPUTER INC. G55VW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed 
root=UUID=927ff2bd-c81d-4a5d-9acb-3bd3dd820e35 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/05/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G55VW.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G55VW
  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.:bvrG55VW.206:bd04/05/2012:svnASUSTeKCOMPUTERINC.:pnG55VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG55VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: G55VW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev

[Touch-packages] [Bug 1335481] Re: unity-system-compositor crashed with SIGABRT - assertion failed at buffer_queue.cpp:136 - !pending_client_notifications.empty()

2014-07-16 Thread Alexandros Frantzis

This seems related to https://code.launchpad.net/~mir-
team/mir/fix-1339700/+merge/226233 , so it may be a different
manifestation of  bug 1339700.

From Alberto's last comment in the MP above:

Ok, after staring at TimeoutFrameDroppingPolicy there are scenarios
that can lead to an assert. (referring to the assertion we are seeing
in this bug)

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

Title:
  unity-system-compositor crashed with SIGABRT - assertion failed at
  buffer_queue.cpp:136 - !pending_client_notifications.empty()

Status in Mir:
  Triaged
Status in Mir 0.4 series:
  Won't Fix
Status in Mir 0.5 series:
  Triaged
Status in “mir” package in Ubuntu:
  Triaged
Status in “unity-system-compositor” package in Ubuntu:
  Invalid

Bug description:
  Can't say so much, opened the launched an had a crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: unity-system-compositor 0.0.4+14.10.20140625-0ubuntu1
  ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0
  Uname: Linux 3.15.0-6-generic x86_64
  ApportVersion: 2.14.3-0ubuntu2
  Architecture: amd64
  BootLog:
   * Setting up X socket directories...   [160G 
[154G[ OK ]
* Starting automatic crash report generation: apport   [160G 
[154G[ OK ]
  Date: Sat Jun 28 20:23:03 2014
  ExecutablePath: /usr/sbin/unity-system-compositor
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:0136]
 Subsystem: Acer Incorporated [ALI] Device [1025:0136]
  InstallationDate: Installed on 2014-06-19 (9 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64+mac (20140619)
  ProcCmdline: /usr/sbin/unity-system-compositor --file /run/mir_socket 
--from-dm-fd 10 --to-dm-fd 13 --vt 7
  ProcEnviron:
   
  Signal: 6
  SourcePackage: unity-system-compositor
  SystemImageInfo: Error: [Errno 2] No such file or directory: 
'system-image-cli'
  Title: unity-system-compositor crashed with SIGABRT in __assert_fail_base()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  version.libdrm: libdrm2 2.4.54-1
  version.lightdm: lightdm 1.11.3-0ubuntu1
  version.mesa: libegl1-mesa-dev N/A

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

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

[Touch-packages] [Bug 1342707] [NEW] initial installation of package virtualbox-guest-utils fails

2014-07-16 Thread LAZA

Public bug reported:

I have the problem in virtuell machines that the favored virtualbox
packages for the guest does not install correct.

- make a new Linux VM
- install Xubuntu (i think, we have the same problem in all the other Ubuntu 
distros)
- reboot -- get a real small window (800x640?)
- install package Synaptic
- open Synpatic
- go through the options
- - Ubuntu Software all ticked (except sources)
-- other software all ticked (except sources, again)
-- Updates all ticked
-- additional propietary drivers 
-- activate Virtualbox-guest
-- accept/do now
-- installation starts (blue bar) but hangs forever

This is cause of NOT reloading the software sources/packages so i got an error 
that the source is not reachable (or something like that).
After closing the Software-properties window and reloading the packages all 
works flawless.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: software-properties-gtk 0.92.37.1
ProcVersionSignature: Ubuntu 3.13.0-32.56-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
Date: Wed Jul 16 14:43:49 2014
InstallationDate: Installed on 2014-03-16 (121 days ago)
InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140225)
PackageArchitecture: all
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug third-party-packages trusty

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

Title:
  initial installation of package virtualbox-guest-utils fails

Status in “software-properties” package in Ubuntu:
  New

Bug description:
  I have the problem in virtuell machines that the favored virtualbox
  packages for the guest does not install correct.

  - make a new Linux VM
  - install Xubuntu (i think, we have the same problem in all the other Ubuntu 
distros)
  - reboot -- get a real small window (800x640?)
  - install package Synaptic
  - open Synpatic
  - go through the options
  - - Ubuntu Software all ticked (except sources)
  -- other software all ticked (except sources, again)
  -- Updates all ticked
  -- additional propietary drivers 
  -- activate Virtualbox-guest
  -- accept/do now
  -- installation starts (blue bar) but hangs forever

  This is cause of NOT reloading the software sources/packages so i got an 
error that the source is not reachable (or something like that).
  After closing the Software-properties window and reloading the packages all 
works flawless.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.1
  ProcVersionSignature: Ubuntu 3.13.0-32.56-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  Date: Wed Jul 16 14:43:49 2014
  InstallationDate: Installed on 2014-03-16 (121 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140225)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1329014] Re: [Audigy2 - SB Audigy 2 [SB0240], playback] No sound at all

2014-07-16 Thread Joel Chav

Hello Daniel Letzeisen (dtl131),

I've download an application called Gnome ALSA Mixer ...

I've succeed to modify that toggle

'Audigy Analog/Digital Output Jack'

Sound is now back on my Creative SoundBlaster Audigy 2 Platinium

Thanks.

Joe

** Attachment added: Gnome-ALSA-mixer Ubuntu 14.04.png
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1329014/+attachment/4153954/+files/Gnome-ALSA-mixer%20Ubuntu%2014.04.png

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

Title:
  [Audigy2 - SB Audigy 2 [SB0240], playback] No sound at all

Status in “alsa-driver” package in Ubuntu:
  Incomplete

Bug description:
  newage@newage-desktop:~$ aplay -l
   Lista PLAYBACK de dispozitive 
  placa 0: Audigy2 [SB Audigy 2 [SB0240]], dispozitiv 0: emu10k1 [ADC 
Capture/Standard PCM Playback]
subdispozitive: 32/32
Subdispozitiv #0: subdevice #0
Subdispozitiv #1: subdevice #1
Subdispozitiv #2: subdevice #2
Subdispozitiv #3: subdevice #3
Subdispozitiv #4: subdevice #4
Subdispozitiv #5: subdevice #5
Subdispozitiv #6: subdevice #6
Subdispozitiv #7: subdevice #7
Subdispozitiv #8: subdevice #8
Subdispozitiv #9: subdevice #9
Subdispozitiv #10: subdevice #10
Subdispozitiv #11: subdevice #11
Subdispozitiv #12: subdevice #12
Subdispozitiv #13: subdevice #13
Subdispozitiv #14: subdevice #14
Subdispozitiv #15: subdevice #15
Subdispozitiv #16: subdevice #16
Subdispozitiv #17: subdevice #17
Subdispozitiv #18: subdevice #18
Subdispozitiv #19: subdevice #19
Subdispozitiv #20: subdevice #20
Subdispozitiv #21: subdevice #21
Subdispozitiv #22: subdevice #22
Subdispozitiv #23: subdevice #23
Subdispozitiv #24: subdevice #24
Subdispozitiv #25: subdevice #25
Subdispozitiv #26: subdevice #26
Subdispozitiv #27: subdevice #27
Subdispozitiv #28: subdevice #28
Subdispozitiv #29: subdevice #29
Subdispozitiv #30: subdevice #30
Subdispozitiv #31: subdevice #31
  placa 0: Audigy2 [SB Audigy 2 [SB0240]], dispozitiv 2: emu10k1 efx 
[Multichannel Capture/PT Playback]
subdispozitive: 8/8
Subdispozitiv #0: subdevice #0
Subdispozitiv #1: subdevice #1
Subdispozitiv #2: subdevice #2
Subdispozitiv #3: subdevice #3
Subdispozitiv #4: subdevice #4
Subdispozitiv #5: subdevice #5
Subdispozitiv #6: subdevice #6
Subdispozitiv #7: subdevice #7
  placa 0: Audigy2 [SB Audigy 2 [SB0240]], dispozitiv 3: emu10k1 [Multichannel 
Playback]
subdispozitive: 1/1
Subdispozitiv #0: subdevice #0
  placa 0: Audigy2 [SB Audigy 2 [SB0240]], dispozitiv 4: p16v [p16v]
subdispozitive: 1/1
Subdispozitiv #0: subdevice #0

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  newage 2071 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jun 11 20:38:53 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-06-11 (0 days ago)
  InstallationMedia: It
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Audigy2 failed
  Symptom_Card: SB0240 Audigy 2 Platinum 6.1 - SB Audigy 2 [SB0240]
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  newage 2071 F pulseaudio
  Symptom_Type: No sound at all
  Title: [Audigy2 - SB Audigy 2 [SB0240], playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/31/2005
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BZ87510A.86A.0125.P34.0503312215
  dmi.board.name: D875PBZ
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAC26680-205
  dmi.chassis.type: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBZ87510A.86A.0125.P34.0503312215:bd03/31/2005:svn:pn:pvr:rvnIntelCorporation:rnD875PBZ:rvrAAC26680-205:cvn:ct2:cvr:

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

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

[Touch-packages] [Bug 1310200] Re: Indicators disappear at the panel (clementine, dropbox, skype etc)

2014-07-16 Thread Yanpas

I have just been testing Dropbox, Skype and clementine. Everything works
fine. And this fix seems to fix the bug with displaying unplugged flash
drive on Launcher :)

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

Title:
  Indicators disappear at the panel (clementine, dropbox, skype etc)

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  Fix Released
Status in “unity” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]
  Some indicators icons (such as skype, clementine, dropbox) disappear from 
panel when changing graphical state.

  [Test case]
  1. Run one of the affected software (i.e. skype)
  2. The skype icon should show in the unity panel
  3. Change your status in skype to something else (i.e. Away)
  4. The skype icon in the panel should change without disappearing

  [Regression potential]
  Nothing known, the icons database is reloaded for safety checks and this does 
nothing but updating the icons.

  

  
  Unconstant indicators (which are changig their graphical state during work of 
the app, for example skype, clemetine) disappears on the panel. They appear 
again if you click the mouse on th closest rightest indicator and pull it into 
left side or they appear after some time.

  ProblemType: BugDistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140416-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6
  Uname: Linux 3.11.0-20-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sun Apr 20 12:26:14 2014
  InstallationDate: Installed on 2014-01-14 (95 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (1 days ago)

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

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

[Touch-packages] [Bug 1342247] Re: OSK behaviour in webapp ( webapp-container )

2014-07-16 Thread Olivier Tilloy

I can reliably reproduce, and I’m also seeing the cursor in the wrong
position, always at the start of the field.

This particular webapp uses the old policy (version 1.0), meaning that
by default the webapp container uses QtWebKit as a backend. The new
policy (starting from 1.1 IIRC, use 1.2 to target 14.10) will by default
use Oxide, which is not affected by this bug.

Unfortunately we can’t commit resources to fixing bugs in QtWebKit, now
that our focus is on Oxide. Updating the app to use the new policy
should do the trick. I’m subscribing Timo to this bug in case he’s
interested in updating his app.

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

Title:
  OSK behaviour in webapp ( webapp-container )

Status in “webbrowser-app” package in Ubuntu:
  New

Bug description:
  In the google-maps webapp (a click package on ubuntu touch by Timo 
Leppiniemi), the osk handles default upper- and lowercase settings the wrong 
way around. When you start typing text, the first letter will be in lowercase 
and all the following in uppercase. Expected would ofcourse be the opposite. I 
have only seen this happen within this particular app.
  I am on ubuntu touch utopic channel devel r  #119. Device: Mako

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

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

[Touch-packages] [Bug 1342774] [NEW] xorg segfault on suspend/wake (not allways)

2014-07-16 Thread Picek

Public bug reported:

sometimes I face Xorg segfault on wake up from suspend/hibernation. I use this: 
http://askubuntu.com/a/387676/293492  workaraound and it works in 90% of cases. 
I also use radeon propertiary driver fglrx ( version 13.35.5). I may be wrong 
but I suspect that thos bug occurs when suspend is triggered by closing the 
laptop lid - when I use suspend button or pm-suspend command everything works 
fine. 
I`m using ubuntu 14.04, xorg version is 1:7.7+1ubuntu8

to reproduce:
change power management close lid behaviour to suspend

close lid

open lid

Xserver does not restore correctly (blank screen). you can change
session to tty1-6 and log in. Killing xorg restores systems
functionality. if no action is made bu user after about 30 seconds X
server resets automatically rastoring systems functionality

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
Uname: Linux 3.13.0-29-generic x86_64
NonfreeKernelModules: fglrx
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Wed Jul 16 16:50:15 2014
DistUpgraded: 2014-06-13 21:03:32,211 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 fglrx-updates, 13.350.1, 3.13.0-29-generic, x86_64: installed
 fglrx-updates, 13.350.1, 3.13.0-30-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:05eb]
 Advanced Micro Devices, Inc. [AMD/ATI] Venus PRO [Radeon HD 8850M] [1002:6823] 
(prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:05eb]
InstallationDate: Installed on 2014-06-12 (33 days ago)
InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release amd64 
(20140204)
MachineType: Dell Inc. Inspiron 5537
ProcEnviron:
 LANGUAGE=pl
 PATH=(custom, no user)
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic 
root=UUID=1cfa4110-8461-483d-8643-833762298079 ro
SourcePackage: xorg
UpgradeStatus: Upgraded to trusty on 2014-06-13 (32 days ago)
dmi.bios.date: 08/19/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: 03MV2R
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A04
dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd08/19/2013:svnDellInc.:pnInspiron5537:pvrA04:rvnDellInc.:rn03MV2R:rvrA00:cvnDellInc.:ct8:cvrA04:
dmi.product.name: Inspiron 5537
dmi.product.version: A04
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.11.1+14.04.20140701-0ubuntu1
version.fglrx-installer: fglrx-installer N/A
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 N/A

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


** Tags: amd64 apport-bug 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/1342774

Title:
  xorg segfault on suspend/wake (not allways)

Status in “xorg” package in Ubuntu:
  New

Bug description:
  sometimes I face Xorg segfault on wake up from suspend/hibernation. I use 
this: http://askubuntu.com/a/387676/293492  workaraound and it works in 90% of 
cases. I also use radeon propertiary driver fglrx ( version 13.35.5). I may be 
wrong but I suspect that thos bug occurs when suspend is triggered by closing 
the laptop lid - when I use suspend button or pm-suspend command everything 
works fine. 
  I`m using ubuntu 14.04, xorg version is 1:7.7+1ubuntu8

  to reproduce:
  change power management close lid behaviour to suspend

  close lid

  open lid

  Xserver does not restore correctly (blank screen). you can change
  session to tty1-6 and log in. Killing xorg restores systems
  functionality. if no action is made bu user after about 30 seconds X
  server resets automatically rastoring systems functionality

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture:

[Touch-packages] [Bug 741869] Re: Unity/compiz intercepts Super and Alt keypresses from grabbed windows like VMs.

Yes this is much better than having no solution at all and if this is
the best that can be done then it should land in main archives.

** 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 unity in Ubuntu.
https://bugs.launchpad.net/bugs/741869

Title:
  Unity/compiz intercepts Super and Alt keypresses from grabbed windows
  like VMs.

Status in Ayatana Design:
  Fix Committed
Status in Compiz:
  Triaged
Status in Compiz Core:
  Triaged
Status in OEM Priority Project:
  Won't Fix
Status in OEM Priority Project precise series:
  Won't Fix
Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in “compiz” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  New
Status in “unity” source package in Trusty:
  New

Bug description:
  [Impact]
  After upgrading from Maverick to Natty, I can no longer use the Super 
(windows) key in Virtual Machine Manager. Previously, as long as I had the 
Virtual Machine Manager console window in the foreground, I could press the 
Super key and the start menu would pop up. Since upgrading to Natty, this no 
longer works, and the search box appears in the upper left.

  Also see bug #934921

  [Test Case]
  (1) Install virtualbox or virt-manager and qemu-system, create and boot a 
virtual machine
  (2) while in the virtual machine (and it should grab the keyboard), press the 
Super key
  Expected Result: the super key acts inside the VM (check by install unity on 
it or using xev)
  Buggy Result: the super key acts in the host and the Unity Dash is displayed

  [regression Potential]This patch plays with key grabs and ungrabs:
  the most likely potential for regression is (a) the existing grabs
  continue and no fix obtains or (2) the grab is not resumed when
  returning control from the VM and the Super key does not invoke the
  Unity Dash.

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

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

[Touch-packages] [Bug 1332119] Re: [Launcher] Icons' Ubuntu shape highlight is wrong

2014-07-16 Thread Michał Sawicz

We've currently fixed this in unity8 with a custom approach.

** Branch linked: lp:~mzanetti/unity8/launcher-update-item-glow

** Changed in: unity8
   Status: Opinion = Fix Released

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

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

Title:
  [Launcher] Icons' Ubuntu shape highlight is wrong

Status in Ubuntu UI Toolkit:
  New
Status in Ubuntu UX bugs:
  Fix Committed
Status in The Unity 8 shell:
  Fix Released
Status in “ubuntu-ui-toolkit” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  Fix Released

Bug description:
  Icons in the launcher are supposed to pop out instead of being carved
  in / sunk in the launcher background. Current UbuntuShape highlight
  give a wrong feeling. UbuntuShape2 was supposed to fix this issue and
  support different highlight style to achieve this. But as far as I
  know that component is not ready yet and there is no guarantee it will
  be in the near future.

  Desired solution:
  Use UbuntuShape without any inner shadow or highlight visuals just the shape 
the icon graphics to UbuntuShape.

  Attach top graphic on top of the icon to provide needed highlight
  (provided as an attachment: icon-top-highlight.png)

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

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

[Touch-packages] [Bug 1342784]

2014-07-16 Thread Apport retracing service

Stacktrace:
 #0  0xb678557c in ?? ()
 No symbol table info available.
 #1  0xb6785574 in ?? ()
 No symbol table info available.
 Backtrace stopped: previous frame identical to this frame (corrupt stack?)
StacktraceSource:
 #0  0xb678557c in ?? ()
 #1  0xb6785574 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()

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

Title:
  unity8 crashed with SIGSEGV

Status in “unity8” package in Ubuntu:
  Invalid

Bug description:
  Had a lot of apps opened, was trying to switch to one of them and
  unity8 crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: unity8 7.90+14.10.20140714-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: armhf
  CurrentDesktop: Unity
  Date: Wed Jul 16 20:14:37 2014
  Disassembly: = 0xb678557c:   Cannot access memory at address 0xb678557c
  ExecutablePath: /usr/bin/unity8
  InstallationDate: Installed on 2014-07-15 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140715-193707)
  ProcCmdline: unity8
  Signal: 11
  SourcePackage: unity8
  Stacktrace:
   #0  0xb678557c in ?? ()
   No symbol table info available.
   #1  0xb6785574 in ?? ()
   No symbol table info available.
   Backtrace stopped: previous frame identical to this frame (corrupt stack?)
  StacktraceTop:
   ?? ()
   ?? ()
  Title: unity8 crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dialout dip nopasswdlogin plugdev sudo tty 
video

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

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

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

2014-07-16 Thread Apport retracing service

** Attachment added: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1342784/+attachment/4154129/+files/ThreadStacktrace.txt

** 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/1342784

Title:
  unity8 crashed with SIGSEGV

Status in “unity8” package in Ubuntu:
  Invalid

Bug description:
  Had a lot of apps opened, was trying to switch to one of them and
  unity8 crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: unity8 7.90+14.10.20140714-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: armhf
  CurrentDesktop: Unity
  Date: Wed Jul 16 20:14:37 2014
  Disassembly: = 0xb678557c:   Cannot access memory at address 0xb678557c
  ExecutablePath: /usr/bin/unity8
  InstallationDate: Installed on 2014-07-15 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140715-193707)
  ProcCmdline: unity8
  Signal: 11
  SourcePackage: unity8
  Stacktrace:
   #0  0xb678557c in ?? ()
   No symbol table info available.
   #1  0xb6785574 in ?? ()
   No symbol table info available.
   Backtrace stopped: previous frame identical to this frame (corrupt stack?)
  StacktraceTop:
   ?? ()
   ?? ()
  Title: unity8 crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dialout dip nopasswdlogin plugdev sudo tty 
video

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

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

[Touch-packages] [Bug 1342796] [NEW] Key label Begin vs Key label Home

2014-07-16 Thread Ubuntu-QC-1

Public bug reported:

In the resource gtk+3.0 Utopic translations, we have a Key label Home and a Key 
label Begin. I fail to see what keyboard key Begin is as opposed to Home.
Same thing for key labels KP_home and KP_begin.

P.S. I did open a question about this in launchpad but it got closed
with no answer by user actionparsnip, suggesting to open a bug. There
might actually be a good reason, if so which one.

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Key label Begin vs Key label Home

Status in “gtk+3.0” package in Ubuntu:
  New

Bug description:
  In the resource gtk+3.0 Utopic translations, we have a Key label Home and a 
Key label Begin. I fail to see what keyboard key Begin is as opposed to Home.
  Same thing for key labels KP_home and KP_begin.

  P.S. I did open a question about this in launchpad but it got closed
  with no answer by user actionparsnip, suggesting to open a bug. There
  might actually be a good reason, if so which one.

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

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

[Touch-packages] [Bug 1322864] Re: Sometimes the app search doesn't work in the Dash

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

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

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

Title:
  Sometimes the app search doesn't work in the Dash

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  Sometimes I open the Dash by using the Super key or by clicking in the Dash 
icon; when I search for an app the Dash just shows files and folders.
  It is really annoying because I need to log out to solve it.

  I'm using the stock Unity Packages in Ubuntu 14.04.

  I don't know how to reproduce it. It happens once in a while but I
  can't seem to find out why.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.2
  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: Sat May 24 09:40:50 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3903]
  InstallationDate: Installed on 2014-04-27 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: LENOVO IdeaPad U310
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=d69245b3-9c0a-42d7-97d2-469d6b3f1c3d ro quiet splash 
intel_pstate=enable vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/04/2012
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 65CN89WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo
  dmi.board.vendor: LENOVO
  dmi.board.version: 3194WIN8 STD SGL
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo U310
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr65CN89WW:bd09/04/2012:svnLENOVO:pnIdeaPadU310:pvrLenovoU310:rvnLENOVO:rnLenovo:rvr3194WIN8STDSGL:cvnLENOVO:ct10:cvrLenovoU310:
  dmi.product.name: IdeaPad U310
  dmi.product.version: Lenovo U310
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  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: Sat May 24 09:04:55 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4140 
   vendor AUO
  xserver.version: 2:1.15.1-0ubuntu2

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

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

[Touch-packages] [Bug 964705] Re: System policy prevents modification of network settings for all users

2014-07-16 Thread Ben Bailess

I am still seeing this bug in 14.04 with gnome-core (minimal gnome). I
also get the prompt for admin (sudo) password when the connection/signal
is weak, since it might disconnect/reconnect quickly. Instead, that
automatic reconnection doesn't happen since I might miss the password
prompt and the reconnection never occurs if my PC is unattended.

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

Title:
  System policy prevents modification of network settings for all users

Status in NetworkManager:
  Invalid
Status in “network-manager” package in Ubuntu:
  Confirmed
Status in “network-manager” package in Debian:
  Fix Released
Status in “network-manager” package in openSUSE:
  Fix Released

Bug description:
  This seems like a regression? The screen shot is at
  http://thesii.org/Screenshot.jpg The nearest link I can find is from
  the forum area at http://ubuntuforums.org/showthread.php?p=1146

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  ApportVersion: 1.95-0ubuntu1
  Architecture: amd64
  CRDA: Error: [Errno 2] No such file or directory
  Date: Sun Mar 25 19:36:45 2012
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Lubuntu 12.04 Precise Pangolin - Alpha amd64 (20120323)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 990129] Re: Suspend/Resume hangs and fails - Ubuntu 12.04LTS

2014-07-16 Thread Toby

For those of you looking for a workaround until this bug gets a proper
fix...

The following has worked for me on Ubuntu 14.04 x64 running on an intel
based motherboard (Core i3 2nd gen) with Realtek onboard ethernet

Step 1: Open up a terminal and create a script file as follows:

~~~
gksudo gedit /etc/pm/sleep.d/20_custom-ehci_hcd
~~~

Step 2: copy and paste the following code into the file:

~~~
#!/bin/sh
# File: /etc/pm/sleep.d/20_custom-ehci_hcd.
TMPLIST=/tmp/ehci-dev-list

case ${1} in
hibernate|suspend)

;;
resume|thaw)

 chvt 1
 chvt 7
;;
esac
~~~

Step 3:
Give the script permission to run by typing the following in the terminal:

~~~
sudo chmod 755 /etc/pm/sleep.d/20_custom-ehci_hcd
~~~

NOTE 1: This script was found from this thread:-
http://ubuntuforums.org/showthread.php?t=1978290p=12014988#post12014988
All credit to the original author

NOTE 2: Do not copy and paste the ~~'s, they are there purely to
demarcate code blocks from the rest of the text.

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

Title:
  Suspend/Resume hangs and fails - Ubuntu 12.04LTS

Status in “pm-utils” package in Ubuntu:
  Confirmed

Bug description:
  Suspend/Resume hangs on a black screen and a hard reset is needed to
  start system.

  System76 laptop
  Ubuntu 12.04LTS 64bit

  Hardware Profile:
  pst007x@pst007x-Serval-Professional:~$ lspci
  00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family 
DRAM Controller (rev 09)
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core 
Processor Family PCI Express Root Port (rev 09)
  00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 05)
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 05)
  00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 1 (rev b5)
  00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 2 (rev b5)
  00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 3 (rev b5)
  00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 4 (rev b5)
  00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 05)
  00:1f.0 ISA bridge: Intel Corporation HM65 Express Chipset Family LPC 
Controller (rev 05)
  00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset 
Family 6 port SATA AHCI Controller (rev 05)
  00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus 
Controller (rev 05)
  01:00.0 VGA compatible controller: NVIDIA Corporation Device 1211 (rev a1)
  01:00.1 Audio device: NVIDIA Corporation GF110 High Definition Audio 
Controller (rev a1)
  02:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller 
(rev 04)
  03:00.0 Ethernet controller: JMicron Technology Corp. JMC250 PCI Express 
Gigabit Ethernet Controller (rev 05)
  03:00.1 System peripheral: JMicron Technology Corp. SD/MMC Host Controller 
(rev 90)
  03:00.2 SD Host controller: JMicron Technology Corp. Standard SD Host 
Controller (rev 90)
  03:00.3 System peripheral: JMicron Technology Corp. MS Host Controller (rev 
90)
  04:00.0 Network controller: Intel Corporation Centrino Advanced-N 6230 (rev 
34)
  05:00.0 FireWire (IEEE 1394): JMicron Technology Corp. IEEE 1394 Host 
Controller (rev 30)
  pst007x@pst007x-Serval-Professional:~$

  Linux pst007x-Serval-Professional 3.2.0-24-generic #37-Ubuntu SMP Wed
  Apr 25 08:43:22 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

  
  May have something to do with the gnome-power-manager and pm-utils

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

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

[Touch-packages] [Bug 1342807] [NEW] gpg --verify has race conditions when used concurrently

2014-07-16 Thread Scott Moser

Public bug reported:

There is a race condition with gnupg --verify when multiple processes
act at the same time.
strace helps cause the race condition (probably by slowing thing down)
gpgv does not seem to have the issue.

The result is you will see transient verify failures with output like below.
using '--lock-once' seems to improve the problem, but not to entirely fix it.

gpg: Signature made Fri 10 Jan 2014 05:41:43 PM UTC using DSA key ID 437D05B5
gpg: 12: read expected rec type 10, got 0
gpg: lookup_hashtable failed: trust database error
gpg: trustdb: searching trust record failed: trust database error
gpg: Error: The trustdb is corrupted.
gpg: You may try to re-create the trustdb using the commands:
gpg:   cd ~/.gnupg
gpg:   gpg2 --export-ownertrust  otrust.tmp
gpg:   rm trustdb.gpg
gpg:   gpg2 --import-ownertrust  otrust.tmp
gpg: If that does not work, please consult the manual

See the attached 'verify-race' to show the issue.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: gnupg 1.4.16-1.2ubuntu1
ProcVersionSignature: User Name 3.16.0-3.8-generic 3.16.0-rc4
Uname: Linux 3.16.0-3-generic x86_64
ApportVersion: 2.14.4-0ubuntu2
Architecture: amd64
Date: Wed Jul 16 16:09:42 2014
Ec2AMI: ami-002c
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: m1.small
Ec2Kernel: aki-0002
Ec2Ramdisk: ari-0002
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnupg
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug ec2-images utopic

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

Title:
  gpg --verify has race conditions when used concurrently

Status in “gnupg” package in Ubuntu:
  New

Bug description:
  There is a race condition with gnupg --verify when multiple processes
  act at the same time.
  strace helps cause the race condition (probably by slowing thing down)
  gpgv does not seem to have the issue.

  The result is you will see transient verify failures with output like below.
  using '--lock-once' seems to improve the problem, but not to entirely fix it.

  gpg: Signature made Fri 10 Jan 2014 05:41:43 PM UTC using DSA key ID 437D05B5
  gpg: 12: read expected rec type 10, got 0
  gpg: lookup_hashtable failed: trust database error
  gpg: trustdb: searching trust record failed: trust database error
  gpg: Error: The trustdb is corrupted.
  gpg: You may try to re-create the trustdb using the commands:
  gpg:   cd ~/.gnupg
  gpg:   gpg2 --export-ownertrust  otrust.tmp
  gpg:   rm trustdb.gpg
  gpg:   gpg2 --import-ownertrust  otrust.tmp
  gpg: If that does not work, please consult the manual

  See the attached 'verify-race' to show the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: gnupg 1.4.16-1.2ubuntu1
  ProcVersionSignature: User Name 3.16.0-3.8-generic 3.16.0-rc4
  Uname: Linux 3.16.0-3-generic x86_64
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: amd64
  Date: Wed Jul 16 16:09:42 2014
  Ec2AMI: ami-002c
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: aki-0002
  Ec2Ramdisk: ari-0002
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnupg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1342398] Re: display tests fail

2014-07-16 Thread Lars Uebernickel

Sorry Robert, I can't reproduce this failure (and neither can seb128).
Is there anything weird about your display settings that I might not
have though about?

** Changed in: gtk+3.0 (Ubuntu)
   Status: New = Incomplete

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

Title:
  display tests fail

Status in “gtk+3.0” package in Ubuntu:
  Incomplete

Bug description:
  When building from lp:~ubuntu-desktop/gtk/ubuntugtk3 the following
  tests fail:

  make[4]: Entering directory 
'/home/bob/bzr/ubuntu/build-area/gtk+3.0-3.12.2/debian/build/shared/testsuite/gdk'
  ...
  TEST: display... (pid=20429)
/display/unset-display:  **
  
ERROR:/home/bob/bzr/ubuntu/build-area/gtk+3.0-3.12.2/./testsuite/gdk/display.c:29:test_unset_display:
 child process (/display/unset-display/subprocess/1 [20448]) failed unexpectedly
  FAIL
  GTester: last random seed: R02Scd205e936736e45c81367fd045319a1b
  (pid=20451)
/display/bad-display:**
  
ERROR:/home/bob/bzr/ubuntu/build-area/gtk+3.0-3.12.2/./testsuite/gdk/display.c:60:test_bad_display:
 child process (/display/bad-display/subprocess/1 [20465]) failed unexpectedly
  FAIL
  GTester: last random seed: R02Sc24a7df014203697a2a5cae40b501d27
  (pid=20468)
  FAIL: display

  However when I change to the build directory and run make check they
  pass.

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

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

[Touch-packages] [Bug 1342807] Re: gpg --verify has race conditions when used concurrently

2014-07-16 Thread Scott Moser

** Attachment added: script that shows the issue
   
https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/1342807/+attachment/4154140/+files/race-verify

** Description changed:

  There is a race condition with gnupg --verify when multiple processes
  act at the same time.
  strace helps cause the race condition (probably by slowing thing down)
  gpgv does not seem to have the issue.
+ 
+ The result is you will see transient verify failures with output like:
+ 
+ gpg: Signature made Fri 10 Jan 2014 05:41:43 PM UTC using DSA key ID 437D05B5
+ gpg: 12: read expected rec type 10, got 0
+ gpg: lookup_hashtable failed: trust database error
+ gpg: trustdb: searching trust record failed: trust database error
+ gpg: Error: The trustdb is corrupted.
+ gpg: You may try to re-create the trustdb using the commands:
+ gpg:   cd ~/.gnupg
+ gpg:   gpg2 --export-ownertrust  otrust.tmp
+ gpg:   rm trustdb.gpg
+ gpg:   gpg2 --import-ownertrust  otrust.tmp
+ gpg: If that does not work, please consult the manual
  
  See the attached 'verify-race' to show the issue.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: gnupg 1.4.16-1.2ubuntu1
  ProcVersionSignature: User Name 3.16.0-3.8-generic 3.16.0-rc4
  Uname: Linux 3.16.0-3-generic x86_64
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: amd64
  Date: Wed Jul 16 16:09:42 2014
  Ec2AMI: ami-002c
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: aki-0002
  Ec2Ramdisk: ari-0002
  ProcEnviron:
-  TERM=xterm
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=set
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=set
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gnupg
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  There is a race condition with gnupg --verify when multiple processes
  act at the same time.
  strace helps cause the race condition (probably by slowing thing down)
  gpgv does not seem to have the issue.
  
- The result is you will see transient verify failures with output like:
+ The result is you will see transient verify failures with output like below.
+ using '--lock-once' seems to improve the problem, but not to entirely fix it.
  
  gpg: Signature made Fri 10 Jan 2014 05:41:43 PM UTC using DSA key ID 437D05B5
  gpg: 12: read expected rec type 10, got 0
  gpg: lookup_hashtable failed: trust database error
  gpg: trustdb: searching trust record failed: trust database error
  gpg: Error: The trustdb is corrupted.
  gpg: You may try to re-create the trustdb using the commands:
  gpg:   cd ~/.gnupg
  gpg:   gpg2 --export-ownertrust  otrust.tmp
  gpg:   rm trustdb.gpg
  gpg:   gpg2 --import-ownertrust  otrust.tmp
  gpg: If that does not work, please consult the manual
  
  See the attached 'verify-race' to show the issue.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: gnupg 1.4.16-1.2ubuntu1
  ProcVersionSignature: User Name 3.16.0-3.8-generic 3.16.0-rc4
  Uname: Linux 3.16.0-3-generic x86_64
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: amd64
  Date: Wed Jul 16 16:09:42 2014
  Ec2AMI: ami-002c
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: aki-0002
  Ec2Ramdisk: ari-0002
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnupg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  gpg --verify has race conditions when used concurrently

Status in “gnupg” package in Ubuntu:
  New

Bug description:
  There is a race condition with gnupg --verify when multiple processes
  act at the same time.
  strace helps cause the race condition (probably by slowing thing down)
  gpgv does not seem to have the issue.

  The result is you will see transient verify failures with output like below.
  using '--lock-once' seems to improve the problem, but not to entirely fix it.

  gpg: Signature made Fri 10 Jan 2014 05:41:43 PM UTC using DSA key ID 437D05B5
  gpg: 12: read expected rec type 10, got 0
  gpg: lookup_hashtable failed: trust database error
  gpg: trustdb: searching trust record failed: trust database error
  gpg: Error: The trustdb is corrupted.
  gpg: You may try to re-create the trustdb using the commands:
  gpg:   cd ~/.gnupg
  gpg:   gpg2 --export-ownertrust  otrust.tmp
  gpg:   rm trustdb.gpg
  gpg:   gpg2 --import-ownertrust  otrust.tmp
  gpg: If that does not work, please consult the manual

  See the attached 'verify-race' to show the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: gnupg 1.4.16-1.2ubuntu1
  ProcVersionSignature: User Name 3.16.0-3.8-generic 3.16.0-rc4
  Uname: Linux 3.16.0-3-generic x86_64
  ApportVersion:

[Touch-packages] [Bug 1231737] Re: please add trust-store integration to friends

2014-07-16 Thread Jamie Strandboge

Friends is being removed in 14.10. The friends policy group will be
removed from the 1.2 apparmor-easyprof-ubuntu policy.

** Changed in: friends (Ubuntu)
   Status: Confirmed = Won't Fix

** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
   Status: Confirmed = Won't Fix

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

Title:
  please add trust-store integration to friends

Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
  Won't Fix
Status in “friends” package in Ubuntu:
  Won't Fix
Status in “apparmor-easyprof-ubuntu” source package in Saucy:
  Won't Fix
Status in “friends” source package in Saucy:
  Won't Fix
Status in “apparmor-easyprof-ubuntu” source package in Trusty:
  Won't Fix
Status in “friends” source package in Trusty:
  Won't Fix

Bug description:
  Currently the 'friends' policy group is reserved because giving access
  to the friend's DBus API allows applications to send messages without
  the user knowing. If 'friends' is going to be made generally available
  to untrusted appstore apps, the friends service needs to be modified
  to use trust-store, like location-service does. Integrating with
  trust-store means that when an app tries to connect to the friends
  service over DBus, friends will contact trust-store, the trust-store
  will prompt the user (Foo wants to access your friends accounts. Is
  this ok? Yes|No), optionally cache the result and return the result
  to the friends service. In this manner the user is given a contextual
  prompt at the time of access by the app. Using caching this decision
  can be remembered the next time. If caching is used, there should be a
  method to change the decision in settings.

  Targeting to T-Series for now, since the trust-store is not in a
  reusable form yet.

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

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

[Touch-packages] [Bug 1342708] Re: Calendar security should allow dbus calls to com.canonical.indicator.datetime

2014-07-16 Thread Jamie Strandboge

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

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

Title:
  Calendar security should allow dbus calls to
  com.canonical.indicator.datetime

Status in Clock application for Ubuntu devices:
  Confirmed
Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
  In Progress

Bug description:
  The clock app needs to make dbus calls (Set, Get, GetAll) to the
  following dBus service to retrieve alarm settings,

  service: com.canonical.indicator.datetime
  path: /com/canonical/indicator/datetime/AlarmProperties
  interface: org.freedesktop.DBus.Properties

  Currently doing so results in APP_ARMOR DENIAL errors listed below,

  Jul 16 14:16:13 ubuntu-phablet dbus[1441]: apparmor=DENIED
  operation=dbus_method_call  bus=session
  path=/com/canonical/indicator/datetime/AlarmProperties
  interface=org.freedesktop.DBus.Properties member=GetAll
  mask=send name=com.canonical.indicator.datetime pid=25761
  profile=com.ubuntu.clock.devel_ubuntu-clock-app_0.1 peer_pid=2425
  peer_profile=unconfined

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

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

[Touch-packages] [Bug 1208019] Re: Eclipse menus doesn't show up in Saucy

2014-07-16 Thread Ubuntu Foundations Team Bug Bot

The attachment gtk+3.0_3.10.8-0ubuntu1.2.debdiff seems to be a
debdiff.  The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff.  If the
attachment isn't a patch, please remove the patch flag from the
attachment, remove the patch tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  Eclipse menus doesn't show up in Saucy

Status in Eclipse:
  Unknown
Status in GTK+ GUI Toolkit:
  Fix Released
Status in Unity GTK+ module:
  In Progress
Status in “gtk+3.0” package in Ubuntu:
  New
Status in “oracle-jdk7-installer” package in Ubuntu:
  Invalid
Status in “unity-gtk-module” package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

  Switching tabs between open source files with different file types in
  Eclipse causes the Source and Refactor menus to be empty in the global
  menu bar under Unity.

  This is a severe usability problem for many Eclipse users. The fix
  proposed has been available in a PPA and is well-tested.

  [Test Case]

  1. Open a new project in Eclipse.
  2. Open two files: one with a .java extension, another with a .txt extension.
  3. Switch between the .java file and the .txt file and back again.
  4. Open the Source or Refactor menu in the Unity global menu bar.

  Expected result: menus with menu items
  Actual result: empty menus for both

  [Regression Potential]

  The fix involves changes to both gtk and unity-gtk-module.

  The changes to gtk are minimal and only involve the reversal of a pair
  of signal emissions, in a part of the code (GtkMenuTracker) which is
  normally used by desktop environments, not typical user applications.
  Therefore regression potential for the gtk update is unlikely.

  The changes to unity-gtk-module involve emitting show and hide signals
  where they were none before has some regression potential for
  applications that are explicitly watching for when their menus are
  opening and closing. But this is rare for applications to do, and we
  likely would have already received bug reports for those that do.
  Being completely sure would require extensive testing across all gtk
  apps though.

  Both changes together have been available as a PPA, thoroughly tested
  for quite some time now.

  [Other Info]

  The changes to unity-gtk-module depend on the changes to gtk, so both
  must be tested in simultaneity. Suggested to upload both to trusty-
  proposed at the same time.

  Original bug report follows:

  === % ===

  
  HOW TO REPRODUCE
  

  1. Run Eclipse, Gimp or Inkscape.
  2. Move the cursor to the top of the screen.
  3. Click on any of the menu items (File, Edit, Navigate, ...)

  **
  EXPECTED BEHAVIOUR
  **

  - The content of the submenus show up.

  **
  REAL BEHAVIOUR
  **

  - Only the top-level headers are available.
  - Nothing happens when clicking on them
  - They don't show up in the HUD either.

  ***
  WORK-AROUND
  ***

  To modify /usr/share/applications/eclipse.desktop to look like this:

  [Desktop Entry]
  Type=Application
  Name=Eclipse
  Comment=Eclipse Integrated Development Environment
  Icon=eclipse
  Exec=env UBUNTU_MENUPROXY= eclipse
  Terminal=false
  Categories=Development;IDE;Java;

  
  RELEVANT DETAILS
  

  - Doesn't affect Ubuntu releases prior to 13.10.

  **
  TECHNICAL INFO
  **

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: eclipse 3.8.1-1ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
  Uname: Linux 3.10.0-6-generic i686
  ApportVersion: 2.11-0ubuntu1
  Architecture: i386
  Date: Sat Aug  3 17:03:55 2013
  InstallationDate: Installed on 2013-07-08 (25 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130708)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: eclipse
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1342807] Re: gpg --verify has race conditions when used concurrently

2014-07-16 Thread Scott Moser

updated race-verify a bit. no functional change.

** Attachment added: script that shows the issue
   
https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/1342807/+attachment/4154169/+files/race-verify

** Attachment removed: script that shows the issue
   
https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/1342807/+attachment/4154140/+files/race-verify

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

Title:
  gpg --verify has race conditions when used concurrently

Status in “gnupg” package in Ubuntu:
  New

Bug description:
  There is a race condition with gnupg --verify when multiple processes
  act at the same time.
  strace helps cause the race condition (probably by slowing thing down)
  gpgv does not seem to have the issue.

  The result is you will see transient verify failures with output like below.
  using '--lock-once' seems to improve the problem, but not to entirely fix it.

  gpg: Signature made Fri 10 Jan 2014 05:41:43 PM UTC using DSA key ID 437D05B5
  gpg: 12: read expected rec type 10, got 0
  gpg: lookup_hashtable failed: trust database error
  gpg: trustdb: searching trust record failed: trust database error
  gpg: Error: The trustdb is corrupted.
  gpg: You may try to re-create the trustdb using the commands:
  gpg:   cd ~/.gnupg
  gpg:   gpg2 --export-ownertrust  otrust.tmp
  gpg:   rm trustdb.gpg
  gpg:   gpg2 --import-ownertrust  otrust.tmp
  gpg: If that does not work, please consult the manual

  See the attached 'verify-race' to show the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: gnupg 1.4.16-1.2ubuntu1
  ProcVersionSignature: User Name 3.16.0-3.8-generic 3.16.0-rc4
  Uname: Linux 3.16.0-3-generic x86_64
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: amd64
  Date: Wed Jul 16 16:09:42 2014
  Ec2AMI: ami-002c
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: aki-0002
  Ec2Ramdisk: ari-0002
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnupg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1329014] Re: [Audigy2 - SB Audigy 2 [SB0240], playback] No sound at all

2014-07-16 Thread Raymond

do you mean that this control should be assigned to playback devices by
using an asym plugin for playback and capture of Audigy2.pcm.iec958.0

http://git.alsa-project.org/?p=alsa-
lib.git;a=blob;f=src/conf/cards/Audigy2.conf;hb=HEAD

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

Title:
  [Audigy2 - SB Audigy 2 [SB0240], playback] No sound at all

Status in “alsa-driver” package in Ubuntu:
  Incomplete

Bug description:
  newage@newage-desktop:~$ aplay -l
   Lista PLAYBACK de dispozitive 
  placa 0: Audigy2 [SB Audigy 2 [SB0240]], dispozitiv 0: emu10k1 [ADC 
Capture/Standard PCM Playback]
subdispozitive: 32/32
Subdispozitiv #0: subdevice #0
Subdispozitiv #1: subdevice #1
Subdispozitiv #2: subdevice #2
Subdispozitiv #3: subdevice #3
Subdispozitiv #4: subdevice #4
Subdispozitiv #5: subdevice #5
Subdispozitiv #6: subdevice #6
Subdispozitiv #7: subdevice #7
Subdispozitiv #8: subdevice #8
Subdispozitiv #9: subdevice #9
Subdispozitiv #10: subdevice #10
Subdispozitiv #11: subdevice #11
Subdispozitiv #12: subdevice #12
Subdispozitiv #13: subdevice #13
Subdispozitiv #14: subdevice #14
Subdispozitiv #15: subdevice #15
Subdispozitiv #16: subdevice #16
Subdispozitiv #17: subdevice #17
Subdispozitiv #18: subdevice #18
Subdispozitiv #19: subdevice #19
Subdispozitiv #20: subdevice #20
Subdispozitiv #21: subdevice #21
Subdispozitiv #22: subdevice #22
Subdispozitiv #23: subdevice #23
Subdispozitiv #24: subdevice #24
Subdispozitiv #25: subdevice #25
Subdispozitiv #26: subdevice #26
Subdispozitiv #27: subdevice #27
Subdispozitiv #28: subdevice #28
Subdispozitiv #29: subdevice #29
Subdispozitiv #30: subdevice #30
Subdispozitiv #31: subdevice #31
  placa 0: Audigy2 [SB Audigy 2 [SB0240]], dispozitiv 2: emu10k1 efx 
[Multichannel Capture/PT Playback]
subdispozitive: 8/8
Subdispozitiv #0: subdevice #0
Subdispozitiv #1: subdevice #1
Subdispozitiv #2: subdevice #2
Subdispozitiv #3: subdevice #3
Subdispozitiv #4: subdevice #4
Subdispozitiv #5: subdevice #5
Subdispozitiv #6: subdevice #6
Subdispozitiv #7: subdevice #7
  placa 0: Audigy2 [SB Audigy 2 [SB0240]], dispozitiv 3: emu10k1 [Multichannel 
Playback]
subdispozitive: 1/1
Subdispozitiv #0: subdevice #0
  placa 0: Audigy2 [SB Audigy 2 [SB0240]], dispozitiv 4: p16v [p16v]
subdispozitive: 1/1
Subdispozitiv #0: subdevice #0

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  newage 2071 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jun 11 20:38:53 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-06-11 (0 days ago)
  InstallationMedia: It
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Audigy2 failed
  Symptom_Card: SB0240 Audigy 2 Platinum 6.1 - SB Audigy 2 [SB0240]
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  newage 2071 F pulseaudio
  Symptom_Type: No sound at all
  Title: [Audigy2 - SB Audigy 2 [SB0240], playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/31/2005
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BZ87510A.86A.0125.P34.0503312215
  dmi.board.name: D875PBZ
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAC26680-205
  dmi.chassis.type: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBZ87510A.86A.0125.P34.0503312215:bd03/31/2005:svn:pn:pvr:rvnIntelCorporation:rnD875PBZ:rvrAAC26680-205:cvn:ct2:cvr:

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

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

[Touch-packages] [Bug 1342833] [NEW] update /etc/*-release to reflect new 12.04.5

2014-07-16 Thread Celsius

Public bug reported:

1) according to lsb_release I'm using 12.04.4 but I'm actually on
12.04.5 (kernel  3.13.0-30-generic #55~precise1-Ubuntu, 64-bit), that's
actually what this bug report is about

2) base-files: 6.5ubuntu6.7

3) I just updated to 12.04.5 (not too painful process, but I did it
through synaptic because I had some trouble since I was using the
quantal kernel, see at the end for more details). Expected result:
lsb_release indicates 12.04.5

4) lsb_release still indicates 12.04.4.

More details:

running commands

$ lsb_release -a

or

$ cat /etc/*release

 still show 12.04.4 as the version, although the command:

$ hwe-support-status --verbose

returns:

Your Hardware Enablement Stack (HWE) is supported until avril 2017.

which means that it detects properly that I'm using trusty HWE Stack
(i.e. kernel 3.13 and package xserver-xorg-lts-trusty)

my bug report is that I suppose both /etc/lsb-release and /etc/os-
release should reflect this somehow, but it doesn't and no update is
currently proposed for the base-files package.

A bit of background on the not-too-painful update, just to be sure
it's not the cause of this issue:

since I was using xserver-xorg-lts-quantal stack (kernel 3.5) the direct
update from 12.04.4 to .5 didn't work (I had this kind of error:
http://askubuntu.com/questions/493541/hardware-enablement-stack-hwe-out-
of-support)

So, through synaptic, I simply switched back to xserver-xorg-lts-precise
stack (as suggested on some forum/askslashdot posts, cannot remember
where exactly) and then I could install xserver-xorg-lts-trusty and all
dependencies that followed, with first an uninstall of xserver-xorg-lts-
precise and some other packages (and wine for some reason).

I restarted and booted fine on kernel 3.13:

$ uname -a

Linux laptop 3.13.0-30-generic #55~precise1-Ubuntu SMP Fri Jul 4
21:52:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

update manager then proposed some further updates (notably to virtualbox
4.2) but did not propose anymore the HWE Stack update.

So is it a secondary issue of my non-conventional update process
(through synaptic and not update manager) or is it simply that the
package base-files needs an update of the file to reflect the new
version 12.04.5 ?

Thanks!

** Affects: base-files (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  1) according to lsb_release I'm using 12.04.4 but I'm actually on
  12.04.5 (kernel  3.13.0-30-generic #55~precise1-Ubuntu, 64-bit), that's
  actually what this bug report is about
  
  2) base-files: 6.5ubuntu6.7
  
  3) I just updated to 12.04.5 (not too painful process, but I did it
  through synaptic because I had some trouble since I was using the
  quantal kernel, see at the end for more details). Expected result:
  lsb_release indicates 12.04.5
  
  4) lsb_release still indicates 12.04.4.
  
  More details:
  
  running commands
  
  $ lsb_release -a
  
  or
  
  $ cat /etc/*release
  
-  still show 12.04.4 as the version, although the command:
+  still show 12.04.4 as the version, although the command:
  
- $hwe-support-status --verbose
+ $ hwe-support-status --verbose
  
  returns:
  
  Your Hardware Enablement Stack (HWE) is supported until avril 2017.
  
  which means that it detects properly that I'm using trusty HWE Stack
  (i.e. kernel 3.13 and package xserver-xorg-lts-trusty)
  
  my bug report is that I suppose both /etc/lsb-release and /etc/os-
  release should reflect this somehow, but it doesn't and no update is
  currently proposed for the base-files package.
  
  A bit of background on the not-too-painful update, just to be sure
  it's not the cause of this issue:
  
  since I was using xserver-xorg-lts-quantal stack (kernel 3.5) the direct
  update from 12.04.4 to .5 didn't work (I had this kind of error:
  http://askubuntu.com/questions/493541/hardware-enablement-stack-hwe-out-
  of-support)
  
  So, through synaptic, I simply switched back to xserver-xorg-lts-precise
  stack (as suggested on some forum/askslashdot posts, cannot remember
  where exactly) and then I could install xserver-xorg-lts-trusty and all
  dependencies that followed, with first an uninstall of xserver-xorg-lts-
  precise and some other packages (and wine for some reason).
  
  I restarted and booted fine on kernel 3.13:
  
  $ uname -a
  
  Linux laptop 3.13.0-30-generic #55~precise1-Ubuntu SMP Fri Jul 4
  21:52:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
  
  update manager then proposed some further updates (notably to virtualbox
  4.2) but did not propose anymore the HWE Stack update.
  
  So is it a secondary issue of my non-conventional update process
  (through synaptic and not update manager) or is it simply that the
  package base-utils needs an update of the file to reflect the new
  version 12.04.5 ?
  
  Thanks!

** Description changed:

  1) according to lsb_release I'm using 12.04.4 but I'm actually on
  12.04.5 (kernel  3.13.0-30-generic #55~precise1-Ubuntu, 64-bit), that's

[Touch-packages] [Bug 1342129] Re: [webapps] should enable access to dbus org.freedesktop.Application

2014-07-16 Thread Alexandre Abreu

I guess that it would be something that affects any click app that uses
the SDK UriHandler (that the webapp-container uses to achieve that),
will check with Ted

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

Title:
  [webapps] should enable access to dbus org.freedesktop.Application

Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
  New

Bug description:
  Webapps recently add the capability to be invoked  open to custom
  urls (not default), but the apparmor profile needs to be updated to
  enable the org.freedesktop.Application dbus if to be accessed/created:

  Jul 15 13:57:14 ubuntu-phablet dbus[2689]: apparmor=DENIED
  operation=dbus_bind  bus=session
  name=org.freedesktop.Application mask=bind pid=28561
  profile=com.ubuntu.developer.webapps.webapp-gmail_webapp-
  gmail_1.0.12

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

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

[Touch-packages] [Bug 1342151] Re: [Indicators] Silent mode control in the indicator

2014-07-16 Thread Daniela Ferrai

@Thomas - it's a toggle button which I was told is already available in
the SDK

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

Title:
  [Indicators] Silent mode control in the indicator

Status in Ubuntu UX bugs:
  Fix Committed
Status in “indicator-sound” package in Ubuntu:
  Confirmed

Bug description:
  Should the indicator expose the control for silent mode for easy
  access?

  Implementing in settings now but would like to leverage a common
  implementation

  --

  I've attached a wireframe which shows an additional setting in the
  sound indicator for turning on and off silent mode.

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

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

[Touch-packages] [Bug 1088343] Re: please timestamp entries in .xsession-errors

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

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

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

Title:
  please timestamp entries in .xsession-errors

Status in “lightdm” package in Ubuntu:
  Confirmed

Bug description:
  Please timestamp log entries made into ~/.xsession-errors, this is
  very important information.

  References:
  bug 285787
  http://lists.debian.org/debian-policy/2010/08/msg00043.html

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

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

[Touch-packages] [Bug 1342745] Re: USC does not turn on screen through DBus interface

This bug was fixed in the package unity-system-compositor -
0.0.4+14.10.20140716-0ubuntu1

---
unity-system-compositor (0.0.4+14.10.20140716-0ubuntu1) utopic; urgency=low

  [ Alberto Aguirre ]
  * Avoid blocking QT DBus thread (LP: #1342745) (LP: #1342745)
 -- Ubuntu daily release ps-jenk...@lists.canonical.com   Wed, 16 Jul 2014 
14:44:13 +

** Changed in: unity-system-compositor (Ubuntu)
   Status: New = Fix Released

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

Title:
  USC does not turn on screen through DBus interface

Status in Unity System Compositor:
  In Progress
Status in “unity-system-compositor” package in Ubuntu:
  Fix Released

Bug description:
  When the screen is powered off, USC does not turn on screen from
  either the keepDisplayOn or setScreenPowerMode DBus interface

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-system-compositor/+bug/1342745/+subscriptions

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

[Touch-packages] [Bug 1342833] Re: update /etc/*-release to reflect new 12.04.5

2014-07-16 Thread Celsius

** Tags added: precise

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

Title:
  update /etc/*-release to reflect new 12.04.5

Status in “base-files” package in Ubuntu:
  Invalid

Bug description:
  1) according to lsb_release I'm using 12.04.4 but I'm actually on
  12.04.5 (kernel  3.13.0-30-generic #55~precise1-Ubuntu, 64-bit),
  that's actually what this bug report is about

  2) base-files: 6.5ubuntu6.7

  3) I just updated to 12.04.5 (not too painful process, but I did it
  through synaptic because I had some trouble since I was using the
  quantal kernel, see at the end for more details). Expected result:
  lsb_release indicates 12.04.5

  4) lsb_release still indicates 12.04.4.

  More details:

  running commands

  $ lsb_release -a

  or

  $ cat /etc/*release

   still show 12.04.4 as the version, although the command:

  $ hwe-support-status --verbose

  returns:

  Your Hardware Enablement Stack (HWE) is supported until avril 2017.

  which means that it detects properly that I'm using trusty HWE Stack
  (i.e. kernel 3.13 and package xserver-xorg-lts-trusty)

  my bug report is that I suppose both /etc/lsb-release and /etc/os-
  release should reflect this somehow, but it doesn't and no update is
  currently proposed for the base-files package.

  A bit of background on the not-too-painful update, just to be sure
  it's not the cause of this issue:

  since I was using xserver-xorg-lts-quantal stack (kernel 3.5) the
  direct update from 12.04.4 to .5 didn't work (I had this kind of
  error: http://askubuntu.com/questions/493541/hardware-enablement-
  stack-hwe-out-of-support)

  So, through synaptic, I simply switched back to xserver-xorg-lts-
  precise stack (as suggested on some forum/askslashdot posts, cannot
  remember where exactly) and then I could install xserver-xorg-lts-
  trusty and all dependencies that followed, with first an uninstall of
  xserver-xorg-lts-precise and some other packages (and wine for some
  reason).

  I restarted and booted fine on kernel 3.13:

  $ uname -a

  Linux laptop 3.13.0-30-generic #55~precise1-Ubuntu SMP Fri Jul 4
  21:52:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

  update manager then proposed some further updates (notably to
  virtualbox 4.2) but did not propose anymore the HWE Stack update.

  So is it a secondary issue of my non-conventional update process
  (through synaptic and not update manager) or is it simply that the
  package base-files needs an update of the file to reflect the new
  version 12.04.5 ?

  Thanks!

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

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

[Touch-packages] [Bug 1342833] Re: update /etc/*-release to reflect new 12.04.5

2014-07-16 Thread Steve Langasek

12.04.5 has not been released yet.  It is not due for release until
August 7.

Updating of base-files is a standard part of the point release process,
so no bug report needed (and unlikely to be noticed by the folks doing
the point release); closing.

** Changed in: base-files (Ubuntu)
   Status: New = Invalid

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

Title:
  update /etc/*-release to reflect new 12.04.5

Status in “base-files” package in Ubuntu:
  Invalid

Bug description:
  1) according to lsb_release I'm using 12.04.4 but I'm actually on
  12.04.5 (kernel  3.13.0-30-generic #55~precise1-Ubuntu, 64-bit),
  that's actually what this bug report is about

  2) base-files: 6.5ubuntu6.7

  3) I just updated to 12.04.5 (not too painful process, but I did it
  through synaptic because I had some trouble since I was using the
  quantal kernel, see at the end for more details). Expected result:
  lsb_release indicates 12.04.5

  4) lsb_release still indicates 12.04.4.

  More details:

  running commands

  $ lsb_release -a

  or

  $ cat /etc/*release

   still show 12.04.4 as the version, although the command:

  $ hwe-support-status --verbose

  returns:

  Your Hardware Enablement Stack (HWE) is supported until avril 2017.

  which means that it detects properly that I'm using trusty HWE Stack
  (i.e. kernel 3.13 and package xserver-xorg-lts-trusty)

  my bug report is that I suppose both /etc/lsb-release and /etc/os-
  release should reflect this somehow, but it doesn't and no update is
  currently proposed for the base-files package.

  A bit of background on the not-too-painful update, just to be sure
  it's not the cause of this issue:

  since I was using xserver-xorg-lts-quantal stack (kernel 3.5) the
  direct update from 12.04.4 to .5 didn't work (I had this kind of
  error: http://askubuntu.com/questions/493541/hardware-enablement-
  stack-hwe-out-of-support)

  So, through synaptic, I simply switched back to xserver-xorg-lts-
  precise stack (as suggested on some forum/askslashdot posts, cannot
  remember where exactly) and then I could install xserver-xorg-lts-
  trusty and all dependencies that followed, with first an uninstall of
  xserver-xorg-lts-precise and some other packages (and wine for some
  reason).

  I restarted and booted fine on kernel 3.13:

  $ uname -a

  Linux laptop 3.13.0-30-generic #55~precise1-Ubuntu SMP Fri Jul 4
  21:52:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

  update manager then proposed some further updates (notably to
  virtualbox 4.2) but did not propose anymore the HWE Stack update.

  So is it a secondary issue of my non-conventional update process
  (through synaptic and not update manager) or is it simply that the
  package base-files needs an update of the file to reflect the new
  version 12.04.5 ?

  Thanks!

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

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

[Touch-packages] [Bug 1342858] Re: old click packages are not always cleaned out

2014-07-16 Thread Jamie Strandboge

I'm going to mark this 'High' for now with the rtm14 tag. Please adjust
as necessary.

** Tags added: rtm14

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

** Description changed:

  /var/lib/apparmor/clicks still has a lot of symlinks pointing to
  security manifests for click packages that are no longer installed. I
  haven't verified this, but I think it might have something to do with
  preinstalled packages and system-image updates. Eg:
  
  $ ls -1 /var/lib/apparmor/clicks/*json | wc -l
  157
  
  $ click list | wc -l
  85
  
  $ sudo click list | wc -l
  19
  
- This doesn't actively harm the system AFAICT, but the 70+ additional and
- unneeded apparmor profiles means slower a first boot requiring policy
- regeneration.
+ None of the symlinks in /var/lib/apparmor/clicks are dangling, so while
+ this doesn't actively harm the system AFAICT, the 70+ additional and
+ unneeded apparmor profiles means a slower first boot when policy
+ regeneration is required.

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

Title:
  old click packages are not always cleaned out

Status in “click” package in Ubuntu:
  New

Bug description:
  /var/lib/apparmor/clicks still has a lot of symlinks pointing to
  security manifests for click packages that are no longer installed. I
  haven't verified this, but I think it might have something to do with
  preinstalled packages and system-image updates. Eg:

  $ ls -1 /var/lib/apparmor/clicks/*json | wc -l
  157

  $ click list | wc -l
  85

  $ sudo click list | wc -l
  19

  None of the symlinks in /var/lib/apparmor/clicks are dangling, so
  while this doesn't actively harm the system AFAICT, the 70+ additional
  and unneeded apparmor profiles means a slower first boot when policy
  regeneration is required.

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

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

[Touch-packages] [Bug 1329014] Re: [Audigy2 - SB Audigy 2 [SB0240], playback] No sound at all

2014-07-16 Thread Joel Chav

Raymond,

I'dont know if it can help you but here are my settings for Alsa :

joe@MediaCenter:~$ aplay -l
 Liste des Périphériques Matériels PLAYBACK 
carte 0: SB [HDA ATI SB], périphérique 0: ALC888 Analog [ALC888 Analog]
  Sous-périphériques: 1/1
  Sous-périphérique #0: subdevice #0
carte 0: SB [HDA ATI SB], périphérique 1: ALC888 Digital [ALC888 Digital]
  Sous-périphériques: 1/1
  Sous-périphérique #0: subdevice #0
carte 1: Audigy2 [SB Audigy 2 Platinum [SB0240P]], périphérique 0: emu10k1 [ADC 
Capture/Standard PCM Playback]
  Sous-périphériques: 29/32
  Sous-périphérique #0: subdevice #0
  Sous-périphérique #1: subdevice #1
  Sous-périphérique #2: subdevice #2
  Sous-périphérique #3: subdevice #3
  Sous-périphérique #4: subdevice #4
  Sous-périphérique #5: subdevice #5
  Sous-périphérique #6: subdevice #6
  Sous-périphérique #7: subdevice #7
  Sous-périphérique #8: subdevice #8
  Sous-périphérique #9: subdevice #9
  Sous-périphérique #10: subdevice #10
  Sous-périphérique #11: subdevice #11
  Sous-périphérique #12: subdevice #12
  Sous-périphérique #13: subdevice #13
  Sous-périphérique #14: subdevice #14
  Sous-périphérique #15: subdevice #15
  Sous-périphérique #16: subdevice #16
  Sous-périphérique #17: subdevice #17
  Sous-périphérique #18: subdevice #18
  Sous-périphérique #19: subdevice #19
  Sous-périphérique #20: subdevice #20
  Sous-périphérique #21: subdevice #21
  Sous-périphérique #22: subdevice #22
  Sous-périphérique #23: subdevice #23
  Sous-périphérique #24: subdevice #24
  Sous-périphérique #25: subdevice #25
  Sous-périphérique #26: subdevice #26
  Sous-périphérique #27: subdevice #27
  Sous-périphérique #28: subdevice #28
  Sous-périphérique #29: subdevice #29
  Sous-périphérique #30: subdevice #30
  Sous-périphérique #31: subdevice #31
carte 1: Audigy2 [SB Audigy 2 Platinum [SB0240P]], périphérique 2: emu10k1 efx 
[Multichannel Capture/PT Playback]
  Sous-périphériques: 8/8
  Sous-périphérique #0: subdevice #0
  Sous-périphérique #1: subdevice #1
  Sous-périphérique #2: subdevice #2
  Sous-périphérique #3: subdevice #3
  Sous-périphérique #4: subdevice #4
  Sous-périphérique #5: subdevice #5
  Sous-périphérique #6: subdevice #6
  Sous-périphérique #7: subdevice #7
carte 1: Audigy2 [SB Audigy 2 Platinum [SB0240P]], périphérique 3: emu10k1 
[Multichannel Playback]
  Sous-périphériques: 1/1
  Sous-périphérique #0: subdevice #0
carte 1: Audigy2 [SB Audigy 2 Platinum [SB0240P]], périphérique 4: p16v [p16v]
  Sous-périphériques: 1/1
  Sous-périphérique #0: subdevice #0
carte 2: HDMI [HDA ATI HDMI], périphérique 3: HDMI 0 [HDMI 0]
  Sous-périphériques: 1/1
  Sous-périphérique #0: subdevice #0

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

Title:
  [Audigy2 - SB Audigy 2 [SB0240], playback] No sound at all

Status in “alsa-driver” package in Ubuntu:
  Incomplete

Bug description:
  newage@newage-desktop:~$ aplay -l
   Lista PLAYBACK de dispozitive 
  placa 0: Audigy2 [SB Audigy 2 [SB0240]], dispozitiv 0: emu10k1 [ADC 
Capture/Standard PCM Playback]
subdispozitive: 32/32
Subdispozitiv #0: subdevice #0
Subdispozitiv #1: subdevice #1
Subdispozitiv #2: subdevice #2
Subdispozitiv #3: subdevice #3
Subdispozitiv #4: subdevice #4
Subdispozitiv #5: subdevice #5
Subdispozitiv #6: subdevice #6
Subdispozitiv #7: subdevice #7
Subdispozitiv #8: subdevice #8
Subdispozitiv #9: subdevice #9
Subdispozitiv #10: subdevice #10
Subdispozitiv #11: subdevice #11
Subdispozitiv #12: subdevice #12
Subdispozitiv #13: subdevice #13
Subdispozitiv #14: subdevice #14
Subdispozitiv #15: subdevice #15
Subdispozitiv #16: subdevice #16
Subdispozitiv #17: subdevice #17
Subdispozitiv #18: subdevice #18
Subdispozitiv #19: subdevice #19
Subdispozitiv #20: subdevice #20
Subdispozitiv #21: subdevice #21
Subdispozitiv #22: subdevice #22
Subdispozitiv #23: subdevice #23
Subdispozitiv #24: subdevice #24
Subdispozitiv #25: subdevice #25
Subdispozitiv #26: subdevice #26
Subdispozitiv #27: subdevice #27
Subdispozitiv #28: subdevice #28
Subdispozitiv #29: subdevice #29
Subdispozitiv #30: subdevice #30
Subdispozitiv #31: subdevice #31
  placa 0: Audigy2 [SB Audigy 2 [SB0240]], dispozitiv 2: emu10k1 efx 
[Multichannel Capture/PT Playback]
subdispozitive: 8/8
Subdispozitiv #0: subdevice #0
Subdispozitiv #1: subdevice #1
Subdispozitiv #2: subdevice #2
Subdispozitiv #3: subdevice #3
Subdispozitiv #4: subdevice #4
Subdispozitiv #5: subdevice #5
Subdispozitiv #6: subdevice #6
Subdispozitiv #7: subdevice #7
  placa 0: Audigy2 [SB Audigy 2 [SB0240]], dispozitiv 3: emu10k1 [Multichannel 
Playback]
subdispozitive: 1/1
Subdispozitiv #0: subdevice #0
  placa 0: Audigy2 [SB Audigy 2 [SB0240]], dispozitiv 4: p16v [p16v]

[Touch-packages] [Bug 1283236] Re: Alarms are triggered in UTC tz despite saving in local tz

2014-07-16 Thread Renato Araujo Oliveira Filho

** Changed in: qtorganizer5-eds (Ubuntu)
   Status: Confirmed = Fix Released

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

Title:
  Alarms are triggered in UTC tz despite saving in local tz

Status in The Date and Time Indicator:
  Fix Released
Status in Clock application for Ubuntu devices:
  Fix Released
Status in Ubuntu UI Toolkit:
  Fix Committed
Status in “indicator-datetime” package in Ubuntu:
  Fix Released
Status in “qtorganizer5-eds” package in Ubuntu:
  Fix Released
Status in “ubuntu-ui-toolkit” package in Ubuntu:
  Fix Released

Bug description:
  Setting an alarm in the local timezone is not respected by the system
  since the alarms is triggered in the equivalent UTC timezone.

  Mako build 200, 205

  Steps to reproduce: 
  1. Ensure that phone timezone is something other than UTC. For instance 
eastern tz (UTC-5)
  2. Set an alarm for 3:00 PM in the ubuntu clock app.
  3. Indicator shows a pending alarm for 3:00 PM
  4. Check a minute or so later, indicator shows an alarm pending for 8:00 PM

  What happens:
  The alarm does not go off at 3:00 PM. Instead it triggers at 8:00 PM

  What should happen:
  The alarm is triggered at 3:00 PM

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

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

[Touch-packages] [Bug 1329014] Re: [Audigy2 - SB Audigy 2 [SB0240], playback] No sound at all

2014-07-16 Thread Joel Chav

Hello Raymond,

Thanks for reply, but i'm not a very advanced Linux user, I've search
for that file on my computer for see the differences but i can't find
that one. (Unless you tell me where can i found it).

It's yesterday that i've found that annoying bug ... I've got more than
one soundcard on my computer (as you can see on the screenshot).

I'm connected in 5.1 analog with my SoundBlaster Creative Audigy 2 Platinum.
The other sound card is just connected to the VGA monitor for general purpose 
(while surfing the web or just simple use).

As i say earlier i've just found that bug, and i've just search if anyone had 
the same issue.
Thanks to Daniel for his help allow me to fix this ...

Maybe the greatest issue is the following fact : Ubuntu miss a full mixer.
Hopefully Ubuntu Store had a few apps that can do the stuff.

Joe

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

Title:
  [Audigy2 - SB Audigy 2 [SB0240], playback] No sound at all

Status in “alsa-driver” package in Ubuntu:
  Incomplete

Bug description:
  newage@newage-desktop:~$ aplay -l
   Lista PLAYBACK de dispozitive 
  placa 0: Audigy2 [SB Audigy 2 [SB0240]], dispozitiv 0: emu10k1 [ADC 
Capture/Standard PCM Playback]
subdispozitive: 32/32
Subdispozitiv #0: subdevice #0
Subdispozitiv #1: subdevice #1
Subdispozitiv #2: subdevice #2
Subdispozitiv #3: subdevice #3
Subdispozitiv #4: subdevice #4
Subdispozitiv #5: subdevice #5
Subdispozitiv #6: subdevice #6
Subdispozitiv #7: subdevice #7
Subdispozitiv #8: subdevice #8
Subdispozitiv #9: subdevice #9
Subdispozitiv #10: subdevice #10
Subdispozitiv #11: subdevice #11
Subdispozitiv #12: subdevice #12
Subdispozitiv #13: subdevice #13
Subdispozitiv #14: subdevice #14
Subdispozitiv #15: subdevice #15
Subdispozitiv #16: subdevice #16
Subdispozitiv #17: subdevice #17
Subdispozitiv #18: subdevice #18
Subdispozitiv #19: subdevice #19
Subdispozitiv #20: subdevice #20
Subdispozitiv #21: subdevice #21
Subdispozitiv #22: subdevice #22
Subdispozitiv #23: subdevice #23
Subdispozitiv #24: subdevice #24
Subdispozitiv #25: subdevice #25
Subdispozitiv #26: subdevice #26
Subdispozitiv #27: subdevice #27
Subdispozitiv #28: subdevice #28
Subdispozitiv #29: subdevice #29
Subdispozitiv #30: subdevice #30
Subdispozitiv #31: subdevice #31
  placa 0: Audigy2 [SB Audigy 2 [SB0240]], dispozitiv 2: emu10k1 efx 
[Multichannel Capture/PT Playback]
subdispozitive: 8/8
Subdispozitiv #0: subdevice #0
Subdispozitiv #1: subdevice #1
Subdispozitiv #2: subdevice #2
Subdispozitiv #3: subdevice #3
Subdispozitiv #4: subdevice #4
Subdispozitiv #5: subdevice #5
Subdispozitiv #6: subdevice #6
Subdispozitiv #7: subdevice #7
  placa 0: Audigy2 [SB Audigy 2 [SB0240]], dispozitiv 3: emu10k1 [Multichannel 
Playback]
subdispozitive: 1/1
Subdispozitiv #0: subdevice #0
  placa 0: Audigy2 [SB Audigy 2 [SB0240]], dispozitiv 4: p16v [p16v]
subdispozitive: 1/1
Subdispozitiv #0: subdevice #0

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  newage 2071 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jun 11 20:38:53 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-06-11 (0 days ago)
  InstallationMedia: It
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Audigy2 failed
  Symptom_Card: SB0240 Audigy 2 Platinum 6.1 - SB Audigy 2 [SB0240]
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  newage 2071 F pulseaudio
  Symptom_Type: No sound at all
  Title: [Audigy2 - SB Audigy 2 [SB0240], playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/31/2005
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BZ87510A.86A.0125.P34.0503312215
  dmi.board.name: D875PBZ
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAC26680-205
  dmi.chassis.type: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBZ87510A.86A.0125.P34.0503312215:bd03/31/2005:svn:pn:pvr:rvnIntelCorporation:rnD875PBZ:rvrAAC26680-205:cvn:ct2:cvr:

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

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

[Touch-packages] [Bug 1320914] Re: Timezone adjustments are not honoured by eds

2014-07-16 Thread Renato Araujo Oliveira Filho

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

** This bug has been marked a duplicate of bug 1332095
   alarms don't update their times when the timezone changes

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

Title:
  Timezone adjustments are not honoured by eds

Status in The Date and Time Indicator:
  New
Status in “qtorganizer5-eds” package in Ubuntu:
  New

Bug description:
  Have a calendar alarm set for 07:00 change your timezone in the
  settings app you alarm goes of on your original timezone and not the
  new one.

  STEPS:
  1. Open calendar.google.com set an appointment for later give it an alarm
  2. Set up your google account on online accounts
  3. Setup sync for google calendar
  4. Change the timezone
  5. Expect the alarm to go off at the right time in the new timezone

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

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

[Touch-packages] [Bug 1323837] Re: Sim toolkit is not available on UT

2014-07-16 Thread taiebot65

Hey i have seen on r133 that those services should be available but
nothing appears when i click on my phone services

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

Title:
  Sim toolkit is not available on UT

Status in “ofono” package in Ubuntu:
  Triaged
Status in “unity8” package in Ubuntu:
  Triaged

Bug description:
  E.g. of SIm toolkit is http://support.vodafone.com.au/articles/FAQ
  /SIM-Toolkit

  While a lot of those addons are completely crap and useless, the SIm
  toolkit is sometimes used by some phone provider to set your sim card
  to roaming mode when you are abroad which makes it a must have.

  For the moment i need to borrow a second phone put my sim card in it,
  go to the Sim-toolkit, enable my sim card for roaming and put the sim
  card back in my UT to get my phone working while i am abroad. I need
  to do the same when i go back home.

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

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

[Touch-packages] [Bug 1342875] [NEW] Unable to delete currently logged in user

2014-07-16 Thread Robert C Jennings

Public bug reported:

A user can not delete themselves using the command 'sudo userdel -rf
username', this is common in cloud tools that clean up running images
prior to capture.  A quick test shows that this worked from Precise
(didn't look back further) to Raring and stopped working with Saucy.

Here's a quick example of the failure (from trusty):
# sudo adduser test
# sudo usermod -aG sudo test
## As the 'test' user
# sudo userdel -rf test
userdel: user test is currently used by process 9600
userdel: cannot open /etc/subuid
## User is not removed

Previously (output from precise)
# sudo userdel -rf test
userdel: user test is currently logged in
userdel: warning: can't remove /var/mail/test: No such file or directory
## User is removed

This is being run as the last command by tools that remove the 'ubuntu'
user to clean the image prior to capture.  This had previously worked
and it is preferable that this could be made to work again.  The
alternative is removal by root, but the root user on cloud images is
locked down and we would not want the user to enable root to run userdel
on the risk of it not getting disabled properly prior to image capture.

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

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

Title:
  Unable to delete currently logged in user

Status in “shadow” package in Ubuntu:
  New

Bug description:
  A user can not delete themselves using the command 'sudo userdel -rf
  username', this is common in cloud tools that clean up running
  images prior to capture.  A quick test shows that this worked from
  Precise (didn't look back further) to Raring and stopped working with
  Saucy.

  Here's a quick example of the failure (from trusty):
  # sudo adduser test
  # sudo usermod -aG sudo test
  ## As the 'test' user
  # sudo userdel -rf test
  userdel: user test is currently used by process 9600
  userdel: cannot open /etc/subuid
  ## User is not removed

  Previously (output from precise)
  # sudo userdel -rf test
  userdel: user test is currently logged in
  userdel: warning: can't remove /var/mail/test: No such file or directory
  ## User is removed

  This is being run as the last command by tools that remove the
  'ubuntu' user to clean the image prior to capture.  This had
  previously worked and it is preferable that this could be made to work
  again.  The alternative is removal by root, but the root user on cloud
  images is locked down and we would not want the user to enable root to
  run userdel on the risk of it not getting disabled properly prior to
  image capture.

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

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

[Touch-packages] [Bug 1341205] Re: Top left icon of my apps can be placed in the middle of the apps

2014-07-16 Thread taiebot65

Happens also on r133

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

Title:
   Top left icon of my apps can be placed in the middle of the apps

Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  
  Top left icon of my apps can be placed in the middle of the apps
  Image of bug http://i.imgur.com/nceYuBL.png
  How to trigger 
  go to the app scop  click on my apps to see all the apps
  go to the media player app click on it (no video should be available on  the 
device)  message appear saying that there is no file to play click ok bug 
triggered.

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

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

[Touch-packages] [Bug 1315265] Re: Broadcom Device BCM43142 Wireless Driver for Ubuntu 14.04 LTS 64Bit Desktop not working out of box

2014-07-16 Thread Arpan Chakraborty

I am usu dell vosro 25520 ubuntu 14.04.
but my laptop blutooth driver does not working...

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

Title:
  Broadcom Device BCM43142 Wireless Driver for Ubuntu 14.04 LTS 64Bit
  Desktop not working out of box

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

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 14.04 LTS
  Release:  14.04

  $ apt-cache policy network-manager
  network-manager:
Installed: 0.9.8.8-0ubuntu7
Candidate: 0.9.8.8-0ubuntu7
Version table:
   *** 0.9.8.8-0ubuntu7 0
  500 http://in.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  
  After installing Ubuntu 14.04 Desktop version 64 bit on my Dell Vostro 2520 
Laptop, I expected the wirless card to automatically be detected and to be able 
to connect to any wireless network for seamless internet access. 

  However, the driver for wifi did not get automatically installed. I
  looked around for some information in the web and found a blog
  suggestion to run the following command for wifi to work:

  $sudo apt-get install linux-headers-generic build-essential dkms

  After running this command, I found the driver to show up in the right
  corner, but when I select a wifi network, I saw another error:

  (1) Creating object for path
  '/org/freedesktop/NetworkManager/ActiveConnection/2' failed in libnm-
  glib.

  I tried asking in the freenode ubuntu irc chatroom but did not get any
  solutions.

  After trying out several suggestions from the chat room, nothing
  worked.

  Workaround:
  Finally, through nm-applet I clicked on Edit Connections and selected the 
wifi network I was trying to add. Then in the security settings, I typed the 
password for accessing the wifi and configured it. 

  When I unplugged my LAN and restarted wifi, it worked. Now I am able
  to access the wifi.

  The forum member in Ubuntu chatroom suggested I file a bug:

  To summarize the issue is, there is no inbuilt driver for Broadcom
  BCM43142 Network Controller.

  Please help fix this in the next update.  Let me know if you need any
  further information.

  Thanks
  Sharath

  $ lsusb
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 004: ID 0c45:6473 Microdia 
  Bus 001 Device 003: ID 0a5c:21d7 Broadcom Corp. BCM43142 Bluetooth 4.0
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  $ lspci 
  00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller 
(rev 09)
  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)
  00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 04)
  00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family 
High Definition Audio Controller (rev 04)
  00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI 
Express Root Port 1 (rev c4)
  00:1c.3 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI 
Express Root Port 4 (rev c4)
  00:1c.5 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI 
Express Root Port 6 (rev c4)
  00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation HM75 Express Chipset LPC Controller 
(rev 04)
  00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port 
SATA Controller [AHCI mode] (rev 04)
  00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus 
Controller (rev 04)
  07:00.0 Network controller: Broadcom Corporation BCM43142 802.11b/g/n (rev 01)
  09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07)

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

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

[Touch-packages] [Bug 1340604] Re: [phone] crash files are only uploaded on boot

2014-07-16 Thread Paul Larson

Looking at syslog on my phone after a fresh install, I'm seeing this:
Jul 16 18:14:03 ubuntu-phablet whoopsie[2080]: whoopsie 0.2.34 starting up.
Jul 16 18:14:03 ubuntu-phablet whoopsie[2080]: Using lock path: 
/var/lock/whoopsie/lock
Jul 16 18:14:28 ubuntu-phablet whoopsie[2154]: Could not connect to the system 
bus: Timeout was reached
Jul 16 18:14:29 ubuntu-phablet whoopsie[2154]: offline

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

Title:
  [phone] crash files are only uploaded on boot

Status in “whoopsie” package in Ubuntu:
  New

Bug description:
  On the phone (mako utopic #125) it seems that crash files are only
  uploaded on boot and not when the crash occurs. whoopsie is running
  but doesn't seem to detect that a crash file is ready for upload.

  = Test Case =
  1. In a shell run:
  $ bash -c 'kill -SEGV $$'
  2. Wait until the file _bin_bash.32011.uploaded is created

  - Check that after a moment whoopsie-upload-all is running
  - Check the progress of the upload in /var/log/upstart/apport-noui.log
  - Upon upload, check that /var/log/syslog contains a OOPS entry from whoopsie

  = Actual Result =
  whoopsie-upload-all times out and the crash file is not uploaded. If the 
device is rebooted, the crash is uploaded immediately.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: whoopsie 0.2.34
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: armhf
  CrashReports:
   640:32011:114:63916:2014-07-11 10:44:24.101108181 +0200:2014-07-11 
10:44:07.613514715 +0200:/var/crash/_bin_bash.32011.crash
   644:32011:114:0:2014-07-11 10:44:24.101108181 +0200:2014-07-11 
10:44:24.101108181 +0200:/var/crash/_bin_bash.32011.upload
  Date: Fri Jul 11 10:45:02 2014
  InstallationDate: Installed on 2014-07-11 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140711-020204)
  RelatedPackageVersions: apport-noui 2.14.4-0ubuntu2
  SourcePackage: whoopsie
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1330037] Re: upower 0.99 transition

This bug was fixed in the package python-dbusmock - 0.10.3-1

---
python-dbusmock (0.10.3-1) unstable; urgency=medium


  * New upstream release:
- Fix TestCLI.test_template_system test with upower 0.99. (LP: #1330037)
- ofono template: Support adding a second modem with AddModem().
  (LP: #1340590)

 -- Martin Pitt mp...@debian.org  Wed, 16 Jul 2014 13:32:03 +0200

** Changed in: python-dbusmock (Ubuntu)
   Status: Fix Committed = Fix Released

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

Title:
  upower 0.99 transition

Status in “cairo-dock-plug-ins” package in Ubuntu:
  Fix Committed
Status in “gnome-applets” package in Ubuntu:
  New
Status in “gnome-control-center” package in Ubuntu:
  New
Status in “gnome-packagekit” package in Ubuntu:
  Fix Released
Status in “gnome-power-manager” package in Ubuntu:
  New
Status in “gnome-session” package in Ubuntu:
  New
Status in “gnome-settings-daemon” package in Ubuntu:
  New
Status in “gnome-shell” package in Ubuntu:
  New
Status in “indicator-power” package in Ubuntu:
  Triaged
Status in “kde4libs” package in Ubuntu:
  New
Status in “mate-applets” package in Ubuntu:
  New
Status in “mate-power-manager” package in Ubuntu:
  New
Status in “mate-session-manager” package in Ubuntu:
  New
Status in “mutter” package in Ubuntu:
  In Progress
Status in “powerd” package in Ubuntu:
  New
Status in “python-dbusmock” package in Ubuntu:
  Fix Released
Status in “razorqt” package in Ubuntu:
  New
Status in “sugar-0.96” package in Ubuntu:
  New
Status in “sugar-0.98” package in Ubuntu:
  New
Status in “telepathy-mission-control-5” package in Ubuntu:
  New
Status in “tracker” package in Ubuntu:
  New
Status in “ubuntu-system-settings” package in Ubuntu:
  New
Status in “unity-control-center” package in Ubuntu:
  New
Status in “unity-settings-daemon” package in Ubuntu:
  New
Status in “upower” package in Ubuntu:
  New
Status in “xfce4-power-manager” package in Ubuntu:
  New
Status in “xfce4-session” package in Ubuntu:
  New
Status in “xfce4-settings” package in Ubuntu:
  New
Status in “xfce4-systemload-plugin” package in Ubuntu:
  Fix Committed
Status in “wmbattery” package in Debian:
  New

Bug description:
  upower 0.99 needs uploading for gnome 3.12. This bug tracks the
  transition.

  A transition is required as some features were removed and the SONAME
  was changed

  Some packages are staged in
  https://launchpad.net/~noskcaj/+archive/upower/+packages

  wmbattery and sugar will probably need removing. If a package only
  needs a rebuild, mark it fix commited, if something else is needed, in
  progress.

  cairo-dock-plug-ins: needs rebuilding
  gnome-applets - patch at bgo:730588
  gnome-shell - ready, just need to drop upower revert.
  gnome-control-center: WIP
  gnome-packagekit: Upower dropped from newest upstream release. Merge from 
debian
  gnome-power-manager: Fixed in newest upstream release. Merge from debian 
experimental
  gnome-session: Done in ppa, needs patches from git or new upstream release
  gnome-settings-daemon: 3.12 is ready out of the box, however that also 
requires gnome-desktop transition. 3.8 and also u-s-d: I have a package that is 
mostly working, however had to cherry-pick quite a few patches and may just be 
better to backport 3.12 power plugin. (considering g-s-d patches will be 
temporary, but u-s-d not so)
  kde: works fine with systemd, suspend and device management broken with 
upstart
  mate: all mate packages need rebuilding
  python-dbusmock: lp:1324791
  sugar: Upstream bug now filed. Unlikely to be ready in time for 14.10. We 
should remove this from the archive till the next upstream release
  telepathy-mission-control-5: Debian has dropped upower support, needs merging
  wmbattery: needs removal. orphaned upstream/debian and doesn't work with new 
kernals
  xfce4-power-manager: Fixed upstream. Merge at lp:1334185. Will need rebuilding
  xfce4-session: patch is upstream, needs work to apply with our current 
patchset
  xfce4-settings: Patch from upstream in ppa
  xfce4-systemload-plugin: needs rebuild

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cairo-dock-plug-ins/+bug/1330037/+subscriptions

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

[Touch-packages] [Bug 1337189] Re: No access to Service Numbers on SIM

2014-07-16 Thread Tony Espy

SIM Services it landed in the past week.  I've verified the UI is
present in image #u132.  Go the bottom of the main Settings page, and
you'll see a System category, then tap Phone which will then show a
page with Operator Name Services.  If your SIM has service numbers
programmed, then this page will show them.  Note, you can also verify
whether or not your SIM has service numbers available by running
/usr/share/ofono/scripts/list-modems.

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

Title:
  No access to Service Numbers on SIM

Status in “address-book-app” package in Ubuntu:
  Fix Released

Bug description:
  Test case:
   - Insert a SIM card with service numbers stored (in the EF_SDN file of the 
SIM).
   - The numbers are correctly listed as oFono property 
org.ofono.SimManager.ServiceNumbers ...
   - ... but nowhere in the UI.

  Examples of are operators' customer support numbers, or even local
  emergency service numbers (see bug 1334860 for a real-life example).

  This is less complex to implement than the user phonebook (in the
  EF_ADN file of the SIM, see bug 1331346), as the SDNs are read-only,
  and the oFono support exists today.

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

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

[Touch-packages] [Bug 1323837] Re: Sim toolkit is not available on UT

2014-07-16 Thread Tony Espy

@taiebot65

AFAIK, there are still no plans to implement the generic SIM Toolkit for
Ubuntu Phone.

As for SIM service numbers, please refer to bug #1337189.

SIM Services it landed in the past week.  I've verified the UI is
present in image #u132.  Go the bottom of the main Settings page, and
you'll see a System category, then tap Phone which will then show a
page with Operator Name Services.  If you're SIM has service numbers
programmed, then this page will show them.  Note, you can also verify
whether or not your SIM has service numbers available by running
/usr/share/ofono/scripts/list-modems.

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

Title:
  Sim toolkit is not available on UT

Status in “ofono” package in Ubuntu:
  Triaged
Status in “unity8” package in Ubuntu:
  Triaged

Bug description:
  E.g. of SIm toolkit is http://support.vodafone.com.au/articles/FAQ
  /SIM-Toolkit

  While a lot of those addons are completely crap and useless, the SIm
  toolkit is sometimes used by some phone provider to set your sim card
  to roaming mode when you are abroad which makes it a must have.

  For the moment i need to borrow a second phone put my sim card in it,
  go to the Sim-toolkit, enable my sim card for roaming and put the sim
  card back in my UT to get my phone working while i am abroad. I need
  to do the same when i go back home.

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

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

[Touch-packages] [Bug 1342896] [NEW] Add support for lcov version 1.11 to fix build error

2014-07-16 Thread Christopher Townsend

Public bug reported:

Nux ci is failing to build because Nux says it doesn't support lcov
1.11.

** Affects: nux
 Importance: High
 Assignee: Christopher Townsend (townsend)
 Status: In Progress

** Affects: nux (Ubuntu)
 Importance: High
 Assignee: Christopher Townsend (townsend)
 Status: In Progress

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

** Changed in: nux
   Status: New = In Progress

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

** Changed in: nux
   Importance: Undecided = High

** Changed in: nux (Ubuntu)
   Importance: Undecided = High

** Changed in: nux
 Assignee: (unassigned) = Christopher Townsend (townsend)

** Changed in: nux (Ubuntu)
 Assignee: (unassigned) = Christopher Townsend (townsend)

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

Title:
  Add support for lcov version 1.11 to fix build error

Status in Nux:
  In Progress
Status in “nux” package in Ubuntu:
  In Progress

Bug description:
  Nux ci is failing to build because Nux says it doesn't support lcov
  1.11.

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

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

[Touch-packages] [Bug 1342896] Re: Add support for lcov version 1.11 to fix build error

** Branch linked: lp:~townsend/nux/fix-lcov-version

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

Title:
  Add support for lcov version 1.11 to fix build error

Status in Nux:
  In Progress
Status in “nux” package in Ubuntu:
  In Progress

Bug description:
  Nux ci is failing to build because Nux says it doesn't support lcov
  1.11.

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

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

[Touch-packages] [Bug 1342896] Re: Add support for lcov version 1.11 to fix build error

2014-07-16 Thread Christopher Townsend

** Branch unlinked: lp:~townsend/nux/fix-lcov-version

** Branch linked: lp:~townsend/nux/fix-lp1342896

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

Title:
  Add support for lcov version 1.11 to fix build error

Status in Nux:
  In Progress
Status in “nux” package in Ubuntu:
  In Progress

Bug description:
  Nux ci is failing to build because Nux says it doesn't support lcov
  1.11.

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

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

[Touch-packages] [Bug 1342903] [NEW] unity retains focus on virtualbox session when locked

2014-07-16 Thread Jackson McCrea

Public bug reported:

While using virtualbox in fullscreen mode, CTRL + ALT + L, leaves focus
with the virtual machine. However this still locks the host's unity
session. This leaves all key events trapped in the virtual machine, so
typing in your password becomes impossible. After a reboot all
functionality returned.

This could be a potential security hazard, depending on the virtual
machine being used, as it allows arbitrary commands to be executed
through a locked unity session without any authentication.


lsb_release -rd
Description:Ubuntu 14.04 LTS
Release:14.04

apt-cache policy unity
unity:
  Installed: 7.2.1+14.04.20140513-0ubuntu2
  Candidate: 7.2.1+14.04.20140513-0ubuntu2
  Version table:
 *** 7.2.1+14.04.20140513-0ubuntu2 0
500 http://ca.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
100 /var/lib/dpkg/status

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


** Tags: lockscreen trusty unity virtualbox

** Information type changed from Private Security to Public

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

Title:
  unity retains focus on virtualbox session when locked

Status in “unity” package in Ubuntu:
  New

Bug description:
  While using virtualbox in fullscreen mode, CTRL + ALT + L, leaves
  focus with the virtual machine. However this still locks the host's
  unity session. This leaves all key events trapped in the virtual
  machine, so typing in your password becomes impossible. After a reboot
  all functionality returned.

  This could be a potential security hazard, depending on the virtual
  machine being used, as it allows arbitrary commands to be executed
  through a locked unity session without any authentication.

  
  lsb_release -rd
  Description:  Ubuntu 14.04 LTS
  Release:  14.04

  apt-cache policy unity
  unity:
Installed: 7.2.1+14.04.20140513-0ubuntu2
Candidate: 7.2.1+14.04.20140513-0ubuntu2
Version table:
   *** 7.2.1+14.04.20140513-0ubuntu2 0
  500 http://ca.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1339200] Re: Beru crash after running an updates to Ubuntu Touch OS build number 113

2014-07-16 Thread gigiblabla

Hello,

There are some news about my problem : i am not alone

https://github.com/rschroll/beru/issues/52

Thank you in advance to push out a new version of Beru in Ubuntu Store

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

Title:
  Beru crash after running an updates to Ubuntu Touch OS build number
  113

Status in “qtdeclarative-opensource-src” package in Ubuntu:
  New

Bug description:
  Hello,

  I updated my system to the latest version Ubuntu Touch OS build
  number 113

  I use a Nexus 10 Tablet

  After this, I observe the following failure :

  When i execute BERU, i observe a BERU crash processus

  *** extract /var/log/apport.log ***
  ERROR: apport (pid 4682) Tue Jul  8 16:49:00 2014: called for pid 4631, 
signal 11, core limit 0
  ERROR: apport (pid 4682) Tue Jul  8 16:49:00 2014: executable: 
/usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene (command line 
/usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene -I ./ ui/main.qml --appargs=)
  ERROR: apport (pid 4682) Tue Jul  8 16:49:00 2014: gdbus call error: Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files

  ERROR: apport (pid 4682) Tue Jul  8 16:49:00 2014: debug: session gdbus call: 
  ERROR: apport (pid 4682) Tue Jul  8 16:49:00 2014: apport: report 
/var/crash/_usr_lib_arm-linux-gnueabihf_qt5_bin_qmlscene.32011.crash already 
exists and unseen, doing nothing to avoid disk usage DoS
  *** end of extract /var/log/apport.log ***

  Some other additional information :

  rschrollOS Build Details

  OS build number 113
  Ubuntu Image part 20140704
  Ubuntu Image description
  Ubuntu Utopic Unicorn (development branch)
  - armhf (20140704-020205)

  Device Image part 20140625
  Device build description
  aosp_manta-userdebug 4.4.2 KOT49H
  20140624-1505-0ubuntu1 test-keys

   
  Thank you in advance for your help

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

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

[Touch-packages] [Bug 1332306] Re: Hot-swapped SIMs should be detected and prompt user to reboot

2014-07-16 Thread Tony Espy

** Changed in: ofono (Ubuntu)
   Status: In Progress = Fix Committed

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

Title:
  Hot-swapped SIMs should be detected and prompt user to reboot

Status in “ofono” package in Ubuntu:
  Fix Committed
Status in “telepathy-ofono” package in Ubuntu:
  Confirmed
Status in “telephony-service” package in Ubuntu:
  Confirmed

Bug description:
  Our telephony stack doesn't support hot-swapping of SIM cards.  If a
  user hot-swaps a SIM, the telephony stack will become unusable.

  The telephony-service should detect when this happens and display a
  snap-decision informing the user that they need to restart their
  device.

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

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

[Touch-packages] [Bug 1342924] [NEW] Please update the .pot file

2014-07-16 Thread David Planella

Public bug reported:

It seems that the translation template is not up-to-date, and as a
result some strings appear untranslated on the phone. As an example, the
translation template in Launchpad contains:

Get more apps in Ubuntu store

whereas on a device that string is Get more apps from the store

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

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

Title:
  Please update the .pot file

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

Bug description:
  It seems that the translation template is not up-to-date, and as a
  result some strings appear untranslated on the phone. As an example,
  the translation template in Launchpad contains:

  Get more apps in Ubuntu store

  whereas on a device that string is Get more apps from the store

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

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

[Touch-packages] [Bug 1342341] Re: upowerd kills USB performance

2014-07-16 Thread Ruslan

Also, writing back the default values to the /proc/sys/vm/... files
doesn't fix the problem — so far only reboot with avoiding writing bad
values helped.

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

Title:
  upowerd kills USB performance

Status in “upower” package in Ubuntu:
  New

Bug description:
  After launching Kubuntu and logging in to KDE I mount a USB storage
  device to e.g. /mnt/tmp and try the following command:

  dd if=/dev/zero of=/mnt/tmp/testfile bs=16M count=100

  I don't wait until it finishes, because when I press Ctrl+C, it waits
  several more seconds and prints that it has copied only one record and
  the speed was from 200 kB/s to 1.8MB/s, which is nowhere near the
  speed the device can operate.

  On the other hand, if I rename /usr/lib/upower/upowerd and restart,
  the same command finishes in under a minute and says the speed was
  30MB/s for USB3 and ~30MB/s for USB2 devices/ports.

  This hasn't happened on Kubuntu 12.04, but does happen on 14.04.
  Running powertop at the Tunables tab doesn't show any difference, so it 
doesn't look related to autosuspend or similar things.
  This also happens with Kubuntu 14.04 LiveCD, not only with the already 
installed system.

  I've tested this with 3 different USB devices: Transcend JF780 16GB
  (in USB 3.0 and 2.0 ports), OCZ ATV 8GB (USB 2.0 device) and Seagate
  SRD00F2 2TB (in USB 3.0 and 2.0 ports) with identical results.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: upower 0.9.23-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic i686
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  CurrentDesktop: KDE
  Date: Wed Jul 16 00:29:34 2014
  InstallationDate: Installed on 2014-05-26 (50 days ago)
  InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release i386 (20140416.1)
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1342341] Re: upowerd kills USB performance

2014-07-16 Thread Ruslan

This appears to be because upowerd calls `pm-powersave false`, which in turn 
activates /usr/lib/pm-utils/power.d/laptop-mode, which writes 10 and 5 to 
/proc/sys/vm/dirty_ratio and /proc/sys/vm/dirty_background_ratio, respectively, 
replacing default 20 and 10.
Commenting this line in laptop-mode file works around this bug.

Now I'm not sure whether this bug is a kernel bug or a pm-utils one. It
seems definitely not a upower bug.

BTW, this bug doesn't appear on another machine I tested it on, with GA-
I915G-MF motherboard, while it appears on the problematic motherboard
MSI B85-G41 PC Mate.

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

Title:
  upowerd kills USB performance

Status in “upower” package in Ubuntu:
  New

Bug description:
  After launching Kubuntu and logging in to KDE I mount a USB storage
  device to e.g. /mnt/tmp and try the following command:

  dd if=/dev/zero of=/mnt/tmp/testfile bs=16M count=100

  I don't wait until it finishes, because when I press Ctrl+C, it waits
  several more seconds and prints that it has copied only one record and
  the speed was from 200 kB/s to 1.8MB/s, which is nowhere near the
  speed the device can operate.

  On the other hand, if I rename /usr/lib/upower/upowerd and restart,
  the same command finishes in under a minute and says the speed was
  30MB/s for USB3 and ~30MB/s for USB2 devices/ports.

  This hasn't happened on Kubuntu 12.04, but does happen on 14.04.
  Running powertop at the Tunables tab doesn't show any difference, so it 
doesn't look related to autosuspend or similar things.
  This also happens with Kubuntu 14.04 LiveCD, not only with the already 
installed system.

  I've tested this with 3 different USB devices: Transcend JF780 16GB
  (in USB 3.0 and 2.0 ports), OCZ ATV 8GB (USB 2.0 device) and Seagate
  SRD00F2 2TB (in USB 3.0 and 2.0 ports) with identical results.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: upower 0.9.23-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic i686
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  CurrentDesktop: KDE
  Date: Wed Jul 16 00:29:34 2014
  InstallationDate: Installed on 2014-05-26 (50 days ago)
  InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release i386 (20140416.1)
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1342586] Re: [utopic] [proposed] cgmanager breaks lightdm login

Other users having the same issue:
http://ubuntuforums.org/showthread.php?t=2234728

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

Title:
  [utopic] [proposed] cgmanager breaks lightdm login

Status in “systemd-shim” package in Ubuntu:
  New

Bug description:
  The latest 'proposed' systemd-shim 6.3-ubuntu1 package install cgmanager. As 
a result X is first killed and then its impossible to login again.
  This happen on Utopic i386 with unity-greeter, systemd-boot and a gtx 750 
nvidia card.

  The bad experience:
  - trying to purge cgmanager also wants to remove a bunch of packages that 
will deeply break the system
  - X can be started but the login always fail
  - there is no way to open a terminal (ctrl+t) or (ctrl+alt+t) from X
  - even cant get a command line

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

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

[Touch-packages] [Bug 984785] Re: .goutputstream files polluting $HOME

2014-07-16 Thread Sam_Ashley

I was until recently using ubuntu studio quantal 64 bit (now using
trusty) and I happened to run across this in the apparmor profile for
evince:

# evince creates a temporary stream file like '.goutputstream-XX' in the
# directory a file is saved. This allows that behavior.
owner /**/.goutputstream-* w,

This discovery has I think been reported here before, but in case it's
useful to say, I thought to check my backup drive and discovered that
indeed those goutputstream files were still piling up in ubuntu studio
quantal. For example I have a backup done on 2014-06-18 and there are 3
of those files in my home directory; another backup dated 2014-04-08 has
14.

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

Title:
  .goutputstream files polluting $HOME

Status in The G Library - GLib:
  Fix Released
Status in Light Display Manager:
  Fix Released
Status in X.Org X server:
  New
Status in “glib2.0” package in Ubuntu:
  Fix Released
Status in “lightdm” package in Ubuntu:
  Invalid
Status in “glib2.0” source package in Precise:
  Triaged
Status in “lightdm” source package in Precise:
  Invalid

Bug description:
  .goutputstream files polluting $HOME.
  Which software or operation is creating these and why?

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xauth 1:1.0.6-1
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  NonfreeKernelModules: nvidia  ati
  ApportVersion: 2.0.1-0ubuntu4
  Architecture: amd64
  Date: Wed Apr 18 13:29:31 2012
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xauth
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1342341] Re: upowerd kills USB performance

2014-07-16 Thread Ruslan

In fact, it seems enough to write any value, even default+1, i.e. 21 to
/proc/sys/vm/dirty_ratio to trigger the bug.

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

Title:
  upowerd kills USB performance

Status in “upower” package in Ubuntu:
  New

Bug description:
  After launching Kubuntu and logging in to KDE I mount a USB storage
  device to e.g. /mnt/tmp and try the following command:

  dd if=/dev/zero of=/mnt/tmp/testfile bs=16M count=100

  I don't wait until it finishes, because when I press Ctrl+C, it waits
  several more seconds and prints that it has copied only one record and
  the speed was from 200 kB/s to 1.8MB/s, which is nowhere near the
  speed the device can operate.

  On the other hand, if I rename /usr/lib/upower/upowerd and restart,
  the same command finishes in under a minute and says the speed was
  30MB/s for USB3 and ~30MB/s for USB2 devices/ports.

  This hasn't happened on Kubuntu 12.04, but does happen on 14.04.
  Running powertop at the Tunables tab doesn't show any difference, so it 
doesn't look related to autosuspend or similar things.
  This also happens with Kubuntu 14.04 LiveCD, not only with the already 
installed system.

  I've tested this with 3 different USB devices: Transcend JF780 16GB
  (in USB 3.0 and 2.0 ports), OCZ ATV 8GB (USB 2.0 device) and Seagate
  SRD00F2 2TB (in USB 3.0 and 2.0 ports) with identical results.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: upower 0.9.23-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic i686
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  CurrentDesktop: KDE
  Date: Wed Jul 16 00:29:34 2014
  InstallationDate: Installed on 2014-05-26 (50 days ago)
  InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release i386 (20140416.1)
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1342413] [NEW] multiple clicks required to register click

2014-07-16 Thread marcus aurelius

Ok. I re-installed a bunch of apps and the problem seems to have been
solved.

 Date: Tue, 15 Jul 2014 23:29:01 +
 From: 1342...@bugs.launchpad.net
 To: ad...@hotmail.com
 Subject: [Bug 1342413] [NEW] multiple clicks required to register click

 Public bug reported:

 after latest upgrades, clicking on anything does not work anymore.
 multiple clicks must be done (e.g. clicking option buttons, clicking
 window control buttons, selecting items in nautilus, etc) to register a
 click.

 ProblemType: Bug
 DistroRelease: Ubuntu 14.04
 Package: unity 7.2.1+14.04.20140513-0ubuntu2
 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
 Uname: Linux 3.13.0-30-generic x86_64
 .tmp.unity.support.test.0:

 ApportVersion: 2.14.1-0ubuntu3.2
 Architecture: amd64
 CompizPlugins: 
 [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
 CompositorRunning: compiz
 CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
 CompositorUnredirectFSW: true
 CurrentDesktop: Unity
 Date: Tue Jul 15 17:24:22 2014
 DistUpgraded: Fresh install
 DistroCodename: trusty
 DistroVariant: ubuntu
 GraphicsCard:
  Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / 
 R7 250X] [1002:683d] (prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:2710]
 InstallationDate: Installed on 2014-06-04 (41 days ago)
 InstallationMedia: It
 MachineType: MSI MS-7693
 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic 
 root=UUID=71881f16-411e-48c3-aad4-8271763e7520 ro quiet splash vt.handoff=7
 SourcePackage: unity
 UpgradeStatus: No upgrade log present (probably fresh install)
 dmi.bios.date: 04/26/2012
 dmi.bios.vendor: American Megatrends Inc.
 dmi.bios.version: V1.7
 dmi.board.asset.tag: To be filled by O.E.M.
 dmi.board.name: 970A-G46 (MS-7693)
 dmi.board.vendor: MSI
 dmi.board.version: 2.0
 dmi.chassis.asset.tag: To Be Filled By O.E.M.
 dmi.chassis.type: 3
 dmi.chassis.vendor: MSI
 dmi.chassis.version: 2.0
 dmi.modalias: 
 dmi:bvnAmericanMegatrendsInc.:bvrV1.7:bd04/26/2012:svnMSI:pnMS-7693:pvr2.0:rvnMSI:rn970A-G46(MS-7693):rvr2.0:cvnMSI:ct3:cvr2.0:
 dmi.product.name: MS-7693
 dmi.product.version: 2.0
 dmi.sys.vendor: MSI
 version.compiz: compiz 1:0.9.11.1+14.04.20140701-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: Tue Jul 15 17:20:47 2014
 xserver.configfile: default
 xserver.devices:
  inputPower Button KEYBOARD, id 6
  inputPower Button KEYBOARD, id 7
  inputMicrosoft Microsoft Wireless Optical Mouse® 1.00 MOUSE, id 8
  inputMicrosoft Comfort Curve Keyboard 2000 KEYBOARD, id 9
  inputMicrosoft Comfort Curve Keyboard 2000 KEYBOARD, id 10
 xserver.errors:

 xserver.logfile: /var/log/Xorg.0.log
 xserver.version: 2:1.15.1-0ubuntu2
 xserver.video_driver: radeon

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

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

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

 Title:
   multiple clicks required to register click

 Status in “unity” package in Ubuntu:
   New

 Bug description:
   after latest upgrades, clicking on anything does not work anymore.
   multiple clicks must be done (e.g. clicking option buttons, clicking
   window control buttons, selecting items in nautilus, etc) to register
   a click.

   ProblemType: Bug
   DistroRelease: Ubuntu 14.04
   Package: unity 7.2.1+14.04.20140513-0ubuntu2
   ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
   Uname: Linux 3.13.0-30-generic x86_64
   .tmp.unity.support.test.0:

   ApportVersion: 2.14.1-0ubuntu3.2
   Architecture: amd64
   CompizPlugins: 
 [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
   CompositorRunning: compiz
   CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
   CompositorUnredirectFSW: true
   CurrentDesktop: Unity
   Date: Tue Jul 15 17:24:22 2014
   DistUpgraded: Fresh install
   DistroCodename: trusty
   DistroVariant: ubuntu

[Touch-packages] [Bug 1289477] Re: Display brightness can lag far behind moving the slider

Working fine on mako, slider and brightness are simultaneous with the
action in the settings pages

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

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

Title:
  Display brightness can lag far behind moving the slider

Status in “indicator-power” package in Ubuntu:
  Fix Released
Status in “ubuntu-system-settings” package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu Trusty r188

  1. Access any of the brightness sliders: in System Settings  Brightness, 
or System Settings  Battery, or the Battery menu (bug 1289470).
  2. Rapidly slide the slider from minimum to maximum and back again, about ten 
times, then let go.
  3. Wait.

  What happens: The phone repeatedly dims and brightens over several
  seconds after you stop touching the slider.

  What should happen: The current brightness level is always either on,
  or less than ~500 ms from reaching, the brightness shown by the slider
  *right now*. Any values that the slider was on previously should be
  ignored.

  Compare bug 1306499, the equivalent problem with the volume slider.

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

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

[Touch-packages] [Bug 1342958] [NEW] vpn configuration cannot be edited after its added

2014-07-16 Thread Chris J Arges

Public bug reported:

[test case]
1) add a VPN connection
2) try to edit VPN connection after its added

This works in trusty

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: network-manager 0.9.8.8-0ubuntu21
ProcVersionSignature: Ubuntu 3.16.0-3.8-generic 3.16.0-rc4
Uname: Linux 3.16.0-3-generic x86_64
ApportVersion: 2.14.4-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Jul 16 15:54:24 2014
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2014-04-30 (77 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
IpRoute:
 default via 192.168.1.1 dev wlan0  proto static 
 10.0.3.0/24 dev lxcbr0  proto kernel  scope link  src 10.0.3.1 
 192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.100  metric 
9 
 192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
 ** (process:14799): CRITICAL **: dbus_g_proxy_add_signal: assertion 
'g_dbus_is_member_name (signal_name)' failed
 
 ** (process:14799): CRITICAL **: dbus_g_proxy_connect_signal: assertion 
'g_dbus_is_member_name (signal_name)' failed
 RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   WIFI  
 WWAN-HARDWARE   WWAN  
 running 0.9.8.8connected   enabled   enabled 
enabledenabled enabled

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


** Tags: amd64 apport-bug utopic

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

Title:
  vpn configuration cannot be edited after its added

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

Bug description:
  [test case]
  1) add a VPN connection
  2) try to edit VPN connection after its added

  This works in trusty

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: network-manager 0.9.8.8-0ubuntu21
  ProcVersionSignature: Ubuntu 3.16.0-3.8-generic 3.16.0-rc4
  Uname: Linux 3.16.0-3-generic x86_64
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jul 16 15:54:24 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-04-30 (77 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   10.0.3.0/24 dev lxcbr0  proto kernel  scope link  src 10.0.3.1 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.100  
metric 9 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   ** (process:14799): CRITICAL **: dbus_g_proxy_add_signal: assertion 
'g_dbus_is_member_name (signal_name)' failed
   
   ** (process:14799): CRITICAL **: dbus_g_proxy_connect_signal: assertion 
'g_dbus_is_member_name (signal_name)' failed
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled enabled

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

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

[Touch-packages] [Bug 1247694] Re: screen brightness adjusts itself constantly

autobrightness control provided

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

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

Title:
  screen brightness adjusts itself constantly

Status in PowerD:
  New
Status in “powerd” package in Ubuntu:
  Confirmed
Status in “ubuntu-system-settings” package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu 13.10 (r100)  (Touch)

  Expected:  manualy adjusted screen brightness stays that way, except
  after period of inactivity, when it goes into power saving mode

  Instead: brightness is dimmed after a few seconds

  As stated in title, screen brighness adjusts itself constantly: When 
adjusting brightness manualy, Galaxy Nexus device (maguro) is often dimmed 
immedeatly to seemingly some kind of default setting. 
  Usualy, this bug happens within seconds after the brightness is set manualy. 
Sometimes though, it happens later at (apparently) random moments. On rare 
occasions, it doesnt happen at all.
  On every occasion however, the slider for manual setting stays where it is.

  At first, I was thinking it was triggered by an overzealous proximity
  sensor (which however works perfectly on android). Now I am leaning
  towards some sort of default setting or automated brightness. Judging
  from earlier posts on xda and LP, it seems there was such a feature at
  some stage in the beta. is there some kind of automatic brightness
  process at work, that overides the manual, but which has no interface?

  content of media-info:
  Ubuntu 13.10 - armhf (20131017)

  mat@Lapbuntu:~$ adb shell getprop ro.cm.device
  maguro

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

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

[Touch-packages] [Bug 1234983] Re: greeter pin stored in plain text with hidden demo greeter code

assume this is not relevant to uss at this time?

** Changed in: ubuntu-system-settings (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/1234983

Title:
  greeter pin stored in plain text with hidden demo greeter code

Status in The Unity 8 shell:
  In Progress
Status in “ubuntu-system-settings” package in Ubuntu:
  Invalid
Status in “unity8” package in Ubuntu:
  New

Bug description:
  In previous images, there was a setting to setup a PIN or password for
  unlocking the greeter. This feature is no longer exposed in the user
  interface, so this is not a particularly important bug to fix and can
  likely just be closed when proper PAM support is used.

  Nevertheless:

  # cat /home/phablet/.unity8-greeter-demo
  [General]
  password=pin
  passwordValue=1234

  # ls -l /home/phablet/.unity8-greeter-demo
  -rw-r--r-- 1 phablet phablet 42 Sep 20 21:36 
/home/phablet/.unity8-greeter-demo

  If the demo code is going to be reintroduced into the user interface,
  it should not store the PIN/password in plain text because people may
  not realize it and store an important credential there. It could
  probably remain if both of these were done:

  1. the file is 'chmod 600'
  2. you used a proper hashing algorithm (see 'man crypt'-- ie, use SHA-512 
with a randomly generated salt when the password is set)

  If implementing the above, please contact the security team since we
  would want to review the implementation details.

  $ adb shell system-image-cli -i
  current build number: 78
  device name: mako
  channel: stable
  last update: 2013-10-03 13:05:32
  version version: 78
  version ubuntu: 20131003
  version device: 20131002.1

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

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

[Touch-packages] [Bug 1260768] Re: Fix the ApplyUpdate() D-Bus API

assuming we need to use the new api

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

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

** Changed in: ubuntu-system-settings (Ubuntu)
 Assignee: (unassigned) = Diego Sarmentero (diegosarmentero)

** Tags added: updates

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

Title:
  Fix the ApplyUpdate() D-Bus API

Status in Ubuntu system image (server/client/updater):
  Fix Released
Status in Ubuntu Touch System Settings:
  New
Status in “system-image” package in Ubuntu:
  Fix Released
Status in “ubuntu-system-settings” package in Ubuntu:
  Triaged

Bug description:
  Bug #1260712 reports the problem where the D-Bus API for ApplyUpdate()
  was changed but system-settings wasn't prepared to handle the change.
  During post-mortem discussions, Didier requested that the Rebooting()
  signal sent by ApplyUpdate() be changed to return an error message
  string instead of a boolean, with the empty string meaning no error.
  This bug tracks that request.

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

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

[Touch-packages] [Bug 1336675] [NEW] SIM unlock - UI hangs when user enters wrong PIN

You have been subscribed to a public bug:

When the user wants to unlock his SIM card and enters a wrong PIN, the
UI freezes completely on second attempt and a reboot is required.

Test Case:
1. Boot a SIM locked device
2. Go to network indicator/sim unlock
3. On the keypad enter a wrong PIN
4. After the notification that unlock failed, enter the right PIN

Actual Result
While user is entering the PIN for the second time, the UI freezes and the 
phone must be rebooted.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: ubuntu-system-settings 0.3+14.10.20140626.1-0ubuntu1
Uname: Linux 3.4.0-5-mako armv7l
ApportVersion: 2.14.3-0ubuntu2
Architecture: armhf
Date: Wed Jul  2 10:15:29 2014
InstallationDate: Installed on 2014-07-02 (0 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140702-020204)
SourcePackage: ubuntu-system-settings
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug armhf avengers qa-touch utopic
-- 
SIM unlock - UI hangs when user enters wrong PIN
https://bugs.launchpad.net/bugs/1336675
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to indicator-network in Ubuntu.

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

[Touch-packages] [Bug 1336675] Re: SIM unlock - UI hangs when user enters wrong PIN

changed to indicator-network per the description

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

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

Title:
  SIM unlock - UI hangs when user enters wrong PIN

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

Bug description:
  When the user wants to unlock his SIM card and enters a wrong PIN, the
  UI freezes completely on second attempt and a reboot is required.

  Test Case:
  1. Boot a SIM locked device
  2. Go to network indicator/sim unlock
  3. On the keypad enter a wrong PIN
  4. After the notification that unlock failed, enter the right PIN

  Actual Result
  While user is entering the PIN for the second time, the UI freezes and the 
phone must be rebooted.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: ubuntu-system-settings 0.3+14.10.20140626.1-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.3-0ubuntu2
  Architecture: armhf
  Date: Wed Jul  2 10:15:29 2014
  InstallationDate: Installed on 2014-07-02 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140702-020204)
  SourcePackage: ubuntu-system-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1342924] Re: Translation template is outdated

2014-07-16 Thread Rodney Dawes

** Summary changed:

- Please update the .pot file
+ Translation template is outdated

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

Title:
  Translation template is outdated

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

Bug description:
  It seems that the translation template is not up-to-date, and as a
  result some strings appear untranslated on the phone. As an example,
  the translation template in Launchpad contains:

  Get more apps in Ubuntu store

  whereas on a device that string is Get more apps from the store

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

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

[Touch-packages] [Bug 1342924] Re: Please update the .pot file

2014-07-16 Thread Alejandro J. Cura

** Changed in: unity-scope-click (Ubuntu)
 Assignee: (unassigned) = Rodney Dawes (dobey)

** Changed in: unity-scope-click (Ubuntu)
   Importance: Undecided = Critical

** Changed in: unity-scope-click (Ubuntu)
   Importance: Critical = High

** Changed in: unity-scope-click (Ubuntu)
   Status: New = Triaged

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

Title:
  Translation template is outdated

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

Bug description:
  It seems that the translation template is not up-to-date, and as a
  result some strings appear untranslated on the phone. As an example,
  the translation template in Launchpad contains:

  Get more apps in Ubuntu store

  whereas on a device that string is Get more apps from the store

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

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

[Touch-packages] [Bug 1337259] Re: Wifi password can't be entered on welcome screen as touches pass straight through the OSK

Daniel, did the fix for  bug #1334429 fix this for you?

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

** Changed in: ubuntu-system-settings (Ubuntu)
 Assignee: (unassigned) = Daniel van Vugt (vanvugt)

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

Title:
  Wifi password can't be entered on welcome screen as touches pass
  straight through the OSK

Status in Mir:
  New
Status in Ubuntu Keyboard:
  New
Status in “mir” package in Ubuntu:
  New
Status in “ubuntu-keyboard” package in Ubuntu:
  New
Status in “ubuntu-system-settings” package in Ubuntu:
  Incomplete

Bug description:
  Wifi password can't be entered on welcome screen as touches pass
  straight through the OSK to the surface below.

  Only happens on the first boot. Seems fine after rebooting.

# system-image-cli -i
current build number: 106
device name: mako
channel: devel
alias: ubuntu-touch/utopic
last update: 2014-07-02 10:17:01
version version: 106
version ubuntu: 20140701
version device: 20140625

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

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

[Touch-packages] [Bug 1208019] Re: Eclipse menus doesn't show up in Saucy

** Branch linked: lp:ubuntu/utopic-proposed/unity-gtk-module

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

Title:
  Eclipse menus doesn't show up in Saucy

Status in Eclipse:
  Unknown
Status in GTK+ GUI Toolkit:
  Fix Released
Status in Unity GTK+ module:
  In Progress
Status in “gtk+3.0” package in Ubuntu:
  New
Status in “oracle-jdk7-installer” package in Ubuntu:
  Invalid
Status in “unity-gtk-module” package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

  Switching tabs between open source files with different file types in
  Eclipse causes the Source and Refactor menus to be empty in the global
  menu bar under Unity.

  This is a severe usability problem for many Eclipse users. The fix
  proposed has been available in a PPA and is well-tested.

  [Test Case]

  1. Open a new project in Eclipse.
  2. Open two files: one with a .java extension, another with a .txt extension.
  3. Switch between the .java file and the .txt file and back again.
  4. Open the Source or Refactor menu in the Unity global menu bar.

  Expected result: menus with menu items
  Actual result: empty menus for both

  [Regression Potential]

  The fix involves changes to both gtk and unity-gtk-module.

  The changes to gtk are minimal and only involve the reversal of a pair
  of signal emissions, in a part of the code (GtkMenuTracker) which is
  normally used by desktop environments, not typical user applications.
  Therefore regression potential for the gtk update is unlikely.

  The changes to unity-gtk-module involve emitting show and hide signals
  where they were none before has some regression potential for
  applications that are explicitly watching for when their menus are
  opening and closing. But this is rare for applications to do, and we
  likely would have already received bug reports for those that do.
  Being completely sure would require extensive testing across all gtk
  apps though.

  Both changes together have been available as a PPA, thoroughly tested
  for quite some time now.

  [Other Info]

  The changes to unity-gtk-module depend on the changes to gtk, so both
  must be tested in simultaneity. Suggested to upload both to trusty-
  proposed at the same time.

  Original bug report follows:

  === % ===

  
  HOW TO REPRODUCE
  

  1. Run Eclipse, Gimp or Inkscape.
  2. Move the cursor to the top of the screen.
  3. Click on any of the menu items (File, Edit, Navigate, ...)

  **
  EXPECTED BEHAVIOUR
  **

  - The content of the submenus show up.

  **
  REAL BEHAVIOUR
  **

  - Only the top-level headers are available.
  - Nothing happens when clicking on them
  - They don't show up in the HUD either.

  ***
  WORK-AROUND
  ***

  To modify /usr/share/applications/eclipse.desktop to look like this:

  [Desktop Entry]
  Type=Application
  Name=Eclipse
  Comment=Eclipse Integrated Development Environment
  Icon=eclipse
  Exec=env UBUNTU_MENUPROXY= eclipse
  Terminal=false
  Categories=Development;IDE;Java;

  
  RELEVANT DETAILS
  

  - Doesn't affect Ubuntu releases prior to 13.10.

  **
  TECHNICAL INFO
  **

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: eclipse 3.8.1-1ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
  Uname: Linux 3.10.0-6-generic i686
  ApportVersion: 2.11-0ubuntu1
  Architecture: i386
  Date: Sat Aug  3 17:03:55 2013
  InstallationDate: Installed on 2013-07-08 (25 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130708)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: eclipse
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1340869] Re: friends-service should be dropped from 14.10 framework and disallowed by the SDK

This bug was fixed in the package apparmor-easyprof-ubuntu - 1.2.10

---
apparmor-easyprof-ubuntu (1.2.10) utopic; urgency=medium

  * remove ubuntu/1.2/friends policy group and adjust autopackagetest
accordingly (LP: #1340869)
  * ubuntu/calendar: com.canonical.indicator.datetime.AlarmProperties should
also be allowed on the org.freedesktop.DBus.Properties interface
(LP: #1342708)
 -- Jamie Strandboge ja...@ubuntu.com   Wed, 16 Jul 2014 11:15:29 -0500

** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
   Status: Fix Committed = Fix Released

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

Title:
  friends-service should be dropped from 14.10 framework and disallowed
  by the SDK

Status in Qt Creator plugins for Ubuntu:
  Fix Committed
Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
  Fix Released
Status in “click-reviewers-tools” package in Ubuntu:
  Fix Committed
Status in “qtcreator-plugin-ubuntu” package in Ubuntu:
  New

Bug description:
  'friends' does not actually fit the phone security model (any app with
  access can impersonate the user with impunity on social media).
  friends-app is being dropped from the phone, and friends-service
  should also be dropped from the framework definition for 14.10.

  We need to keep friends-service on the phone as long as we support the
  14.04 framework, but it should not be allowed by the SDK when
  targeting 14.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qtcreator-plugin-ubuntu/+bug/1340869/+subscriptions

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

[Touch-packages] [Bug 1342708] Re: Calendar security should allow dbus calls to com.canonical.indicator.datetime