date:20141103

This bug was fixed in the package sysvinit - 2.88dsf-53.2ubuntu1

---
sysvinit (2.88dsf-53.2ubuntu1) vivid; urgency=medium

  * Drop debian/initscripts.maintscript and other conffile cleanups which were
only necessary for P → T upgrades.
  * Drop our change to keep /etc/mtab a a file instead of a symlink to
/proc/mounts. /run/mount/utab has worked well for a long time now.
  * Merge with Debian unstable. Remaining Ubuntu changes:
- Remove some initscripts (bootlogs, motd, rmnologin) and
  /etc/network/if-up.d/mountnfs as they have been replaced by upstart jobs
  shipped in other packages.
- init.d/umountroot: If /var/run/init.upgraded exists, call telinit u
  before unmounting the root filesystem.
- debian/patches/91_sulogin_lockedpw.dpatch: Disable "root account is
  locked" warning, since this is the default in Ubuntu. Document this in
  sulogin.8.
- debian/patches/92_sulogin_support_static_sh.patch: add support for
  /bin/static-sh as fallback if the regular shell fails to execute
- debian/control: Drop Essential: yes from sysvinit-utils since we use
  Upstart.
- debian/control: Do not build the sysvinit and sysvinit-core binary
  packages. We don't want to support sysvinit as such, nor a dynamic
  selection between multiple init systems.
- Mark all binary packages as Multi-Arch: foreign to allow for upstart
  to be installable with multi-arch (needed for armhf containers on x86)
- Drop /etc/default/tmpfs, and drop mention of it from
  debian/src/initscripts/man/rcS.5.
- Include /lib/lsb/init-functions in various init.d scripts, or move it
  further to the top, so that they get skipped as there are equivalent
  upstart jobs.
- Drop /lib/init/{tmpfs.sh,mount-functions.sh} and their usage in init.d
  scripts; we do not need those scripts due to the previous change.
- Add debian/src/initscripts/etc/init.d/ondemand: Sleep for 60 seconds,
  then set CPU Frequency Scaling governor to "ondemand" (or to
  "interactive" on systems that support it).
- Remove mention of RAMLOCK, RAMSHM, and RAMTMP from the rcS(5) manual
  page.
- Fix documentation for other things handled by mountall instead of
  initscripts: tmpfs, /sys (mountall lets you specify options in
  /etc/fstab), and ASYNCMOUNTNFS.
- debian/src/initscripts/etc/init.d/sendsigs:
  + sendsigs: OMITPIDS needs to be reinitalized for every loop iteration
before concatenating pids of upstart jobs to it.
  + only omit jobs that are in the 'start' goal or that are in state
'stop/killed'. Those that are destined for 'stop' are waited on and
killed like all other processes.
  + make report_unkillable use apport instead of echoing to console; but
disable this reporting by default.
  + wait up to 300 extra seconds for upstart jobs that have been killed.
- debian/src/sysv-rc/sbin/invoke-rc.d: clean eatmydata from environment
  unless INVOKE_RCD_ALLOW_EATMYDATA is set to value other than '0'.
  (LP #1257036)
- debian/src/sysv-rc/sbin/invoke-rc.d: Call 'initctl reload-configuration'
  to work reliably on systems with broken inotify.
- invoke-rc.d, service: Cherrypick fixes from Debian git repository:
  + In upstart interfacing code, check that the job is actually known to
upstart. This is because during upgrades, pid 1 might still be an
older upstart which may not yet support syntax of the newly unpacked
jobs, thus sysv-init script should be continued to be used instead.
(Closes: #745503)
  + unset UPSTART_SESSION environment variable to make sure all upstart
initctl commands are executed against system init and not the session
one. (Closes: #745505)
  + in upstart interfacing code, map "force-reload" to restart as per
Debian policy 9.3.2, since there is no way to know for-sure if a
reload is supported.
- Revert migration of UTC setting from /etc/default/rcS to /etc/adjtime.
- init.d/rc: Disable startpar. It wreaks havoc with "task" upstart jobs as
  init.d scripts depending on them rely on them to be "running". Drop
  startpar dependencies.
- debian/sysv-rc.postinst, update-rc.d: Adjust for our insserv being in
  /usr/lib/insserv instead of $PATH.
  * Cleans up /run/shm/ compat symlink handling. (LP: #1320534)

sysvinit (2.88dsf-53.2) unstable; urgency=medium

  * Fix a formatting error in mountnfs which turned a tab character into
U+21A6.

sysvinit (2.88dsf-53.1) unstable; urgency=medium

  * Non-maintainer upload.
  * Skip the mountnfs hook when being triggered by the networking SysV init
script and instead use the systemd built-in mechanisms to mount remote
file systems.
This avoids a deadlock caused by the rpcbind SysV init script depending
on $network and the $network LSB facility being provided by the networking
SysV init

[Touch-packages] [Bug 1389028] Re: u1 account crashes and gets removed when installing app

2014-11-03 Thread Alberto Mardegan

Hi Mat, and thanks for reporting this bug. I'm going to ask a few
questions to help me understand the issue.

Do you mean that everytime you add an U1 account and then reboot, you
can no longer find the account in the Accounts panel in System Settings?
If so, can you please try adding more accounts (like google, facebook
and twitter) and see if they persist after a reboot?

** Changed in: ubuntu-system-settings-online-accounts (Ubuntu)
   Status: New => Incomplete

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

Title:
  u1 account crashes and gets removed when installing app

Status in “ubuntu-system-settings-online-accounts” package in Ubuntu:
  Incomplete

Bug description:
  platform: Ubuntu touch
  image: rtm #6
  device: Mako

  after updating to rtm #6 today, I tried installing an app from the
  store. The app in question is the new Grooveshark app by Grooveshark
  (NOT the one by Adnane Belmadiaf)

  When I hit the install button, I get an error:

  Login Error
  Please log in to your Ubuntu One account

  Sure enough, my U1 is gone fron the registered online accounts.

  I can re-add my U1 account and try again to add the app but the same
  thing happens every time. Even after a device reboot.

  Note that it has something to do with this app. Other apps install normally. 
  (Needless to say i have not tried every app or scope in the store so there 
might be others that trigger this as well.)

  Cheers,

  Mat

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

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

[Touch-packages] [Bug 1385464] Re: logrotate fails to run, if status file is corrupt (logrotate running during reboot?)

2014-11-03 Thread Daniel Holbach

Can we land this soon?

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

Title:
  logrotate fails to run, if status file is corrupt (logrotate running
  during reboot?)

Status in “logrotate” package in Ubuntu:
  New

Bug description:
  phablet@ubuntu-phablet:~$ du -h /var/log/syslog 
  654M  /var/log/syslog
  phablet@ubuntu-phablet:~$ sudo logrotate -f /etc/logrotate.conf 
  error: bad top line in state file /var/lib/logrotate/status
  phablet@ubuntu-phablet:~$ cat /var/lib/logrotate/status 
  
/opt/click.ubuntu.com/com.ubuntu.developer.webapps.webapp-gmail/1.0.25phablet@ubuntu-phablet:~$

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

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

[Touch-packages] [Bug 1302885] Re: Media keyboard shortcuts not working

2014-11-03 Thread defaria

Is there something special you need to do after these "solutions".
Because I did the gsettings thing to no avail. I tried the gnome3 thing
and again, nothing changed. Do I need to logout and back in? Do I need
to reboot?

A while ago something got flaky with X so I decided I should logout and
back in. But I couldn't log back in so I had to reboot. When I finally
got back in their were no sound icon, media keys didn't work. No
notifications menu. Emerald wouldn't start, etc. etc. I finally got back
up relatively normal but I can't get this media keys to work and I'm
quite used to them. I'm afraid to even logout and back in let along
reboot because who knows what kinda state I'm gonna come up in!

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

Title:
  Media keyboard shortcuts not working

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

Bug description:
  I can map the Volume Control keys in Keyboard Shortcuts e.g. Volume
  up/down to Volume up/down, but when I press the Volume keys on the
  keyboard nothing happens.

  I have noticed the same problem with other keys on my Logitech Internet 350 
keyboard with Tools, Mail, and HomePage.
  They can all be mapped with Keyboard Shortcuts, but nothing happens 
afterwards when the keyboard key is pressed.

  All these keyboard settings worked fine in older versions of Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140328-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
  Uname: Linux 3.13.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr  4 23:49:58 2014
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2014-04-02 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140402)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_unity-control-center:
   activity-log-manager 0.9.7-0ubuntu12
   deja-dup 30.0-0ubuntu4

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

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

[Touch-packages] [Bug 1389086] Re: package software-properties-gtk 0.92.37.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2014-11-03 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package software-properties-gtk 0.92.37.1 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 1

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

Bug description:
  I'm getting this error every time I start my machine. It's very non-
  representative when I want to show anyone that I'm running
  Linux/Ubuntu and it's spewing errors on startup.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.1
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  Date: Sat Nov  1 21:23:11 2014
  DuplicateSignature: package:software-properties-gtk:0.92.37.1:subprocess new 
pre-removal script returned error exit status 1
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2014-10-03 (31 days ago)
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  PackageArchitecture: all
  SourcePackage: software-properties
  Title: package software-properties-gtk 0.92.37.1 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to trusty on 2014-10-03 (31 days ago)

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

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

[Touch-packages] [Bug 1389086] [NEW] package software-properties-gtk 0.92.37.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2014-11-03 Thread Jiri Schlemmer

Public bug reported:

I'm getting this error every time I start my machine. It's very non-
representative when I want to show anyone that I'm running Linux/Ubuntu
and it's spewing errors on startup.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: software-properties-gtk 0.92.37.1
ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
Uname: Linux 3.13.0-39-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
Date: Sat Nov  1 21:23:11 2014
DuplicateSignature: package:software-properties-gtk:0.92.37.1:subprocess new 
pre-removal script returned error exit status 1
ErrorMessage: subprocess new pre-removal script returned error exit status 1
InstallationDate: Installed on 2014-10-03 (31 days ago)
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
PackageArchitecture: all
SourcePackage: software-properties
Title: package software-properties-gtk 0.92.37.1 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1
UpgradeStatus: Upgraded to trusty on 2014-10-03 (31 days ago)

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


** Tags: amd64 apport-package 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/1389086

Title:
  package software-properties-gtk 0.92.37.1 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 1

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

Bug description:
  I'm getting this error every time I start my machine. It's very non-
  representative when I want to show anyone that I'm running
  Linux/Ubuntu and it's spewing errors on startup.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.1
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  Date: Sat Nov  1 21:23:11 2014
  DuplicateSignature: package:software-properties-gtk:0.92.37.1:subprocess new 
pre-removal script returned error exit status 1
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2014-10-03 (31 days ago)
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  PackageArchitecture: all
  SourcePackage: software-properties
  Title: package software-properties-gtk 0.92.37.1 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to trusty on 2014-10-03 (31 days ago)

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

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

[Touch-packages] [Bug 1061037] Re: Using .xpm icons on desktop may draw huge icon

2014-11-03 Thread Swarnendu Biswas

I have this issue with Opera developer in Utopic with gnome 3 ppas.

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

Title:
  Using .xpm icons on desktop may draw huge icon

Status in pixbuf library for gtk+:
  Fix Released
Status in “gdk-pixbuf” package in Ubuntu:
  Fix Released
Status in “gdk-pixbuf” package in Gentoo Linux:
  Fix Released

Bug description:
  Using attached Eclipse .xpm icon as a desktop launcher icon will draw
  HUGE icon :-) Please see the screenshot attached. This problem started
  manifesting on Ubuntu 12.10 (just upgraded today), on Ubuntu 12.04 the
  icon was drawn correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdk-pixbuf/+bug/1061037/+subscriptions

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

[Touch-packages] [Bug 1389084] [NEW] networkmanager QtBearer backend does not support dual sim

2014-11-03 Thread Lorn Potter

Public bug reported:

Currently, the networkmanager plugin assumes one modem.
It needs to support dual sim properly.

** Affects: qtbase-opensource-src (Ubuntu)
 Importance: Undecided
 Assignee: Lorn Potter (lorn-potter)
 Status: New

** Changed in: qtbase-opensource-src (Ubuntu)
 Assignee: (unassigned) => Lorn Potter (lorn-potter)

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

Title:
  networkmanager QtBearer backend does not support dual sim

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

Bug description:
  Currently, the networkmanager plugin assumes one modem.
  It needs to support dual sim properly.

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

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

[Touch-packages] [Bug 1384243] Re: photos rotated in gallery do not display rotated in scope

Not sure who's to blame here. I suspect it's not unity-scopes-api, but
more likely some interaction between the shell and the scope
implementation.

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

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

Title:
  photos rotated in gallery do not display rotated in scope

Status in The Savilerow project:
  New
Status in “unity-scopes-api” package in Ubuntu:
  New
Status in “unity-scopes-shell” package in Ubuntu:
  New

Bug description:
  I opened a photo from My Photos scope Preview > Open in the gallery.
  When I return to the scope, fully refreshed, the photo does not
  display rotated.

  I would expect dash toolkit to honor the edited state of a photo and
  display it rotated as appropriate.

  Note:
  Gallery app uses a URI that starts with image://thumbnailer/absPathToPhoto to 
display photos with correct rotation. However, scopes require the URI starts 
with photo://. Without that, the Open button on the preview does not open the 
photo in gallery.

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

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

[Touch-packages] [Bug 1385360] Re: Change include guards to use #pragma once

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

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

Title:
  Change include guards to use #pragma once

Status in “unity-scopes-api” package in Ubuntu:
  Fix Committed

Bug description:
  We should do a pass over the code base and get rid of the old-style
  include guards, replacing them with #pragma once. That's a lot simpler
  and less error prone than having to remember to update the guard
  identifier every time copies a header to create a new one.

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

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

[Touch-packages] [Bug 1378182] Re: symbol_diff script breaks with arch= tag in symbols file

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

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

Title:
  symbol_diff script breaks with arch= tag in symbols file

Status in “unity-scopes-api” package in Ubuntu:
  Fix Committed

Bug description:
  The tools/symbol_diff.in script doesn't work with architecture-
  specific tags (or any tag other than c++, for that matter). We have
  one place where, for the ScopeExecData copy constructor, we use

  (c++|arch=amd64)

  in the symbols file. This confuses the script which, every time it
  produces a diff, deletes the "|arch=amd64" portion, so the tag gets
  rewritten to "(c++)", which causes the Jenkins builds for i386 and
  armhf to fail.

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

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

[Touch-packages] [Bug 1210397] Re: [Toshiba Satellite Pro L850] xorg freeze under intense CPU usage on quantal

[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

** Changed in: xorg (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [Toshiba Satellite Pro L850] xorg freeze under intense CPU usage on
  quantal

Status in “xorg” package in Ubuntu:
  Expired

Bug description:
  Seeing xorg freeze under intense CPU usage on quantal (AMD chipset,
  radeon drivers, x86_64). Relevant part of xorg log:

  (EE) [mi] EQ overflowing.  Additional events will be discarded until existing 
events are processed.
  (EE)
  (EE) Backtrace:
  (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x7fe6a7fddb76]
  (EE) 1: /usr/bin/X (mieqEnqueue+0x26b) [0x7fe6a7fbef5b]
  (EE) 2: /usr/bin/X (0x7fe6a7e35000+0x6a4d2) [0x7fe6a7e9f4d2]
  (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fe6a1025000+0x5f34) 
[0x7fe6a102af34]
  (EE) 4: /usr/bin/X (0x7fe6a7e35000+0x93707) [0x7fe6a7ec8707]
  (EE) 5: /usr/bin/X (0x7fe6a7e35000+0xbcee8) [0x7fe6a7ef1ee8]
  (EE) 6: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fe6a715b000+0xfcb0) 
[0x7fe6a716acb0]
  (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7fe6a5dbf000+0x14f1b1) 
[0x7fe6a5f0e1b1]
  (EE) 8: /usr/bin/X (WriteToClient+0x1ff) [0x7fe6a7fe10df]
  (EE) 9: /usr/bin/X (XkbSendStateNotify+0x1a2) [0x7fe6a7f8e232]
  (EE) 10: /usr/bin/X (XkbHandleActions+0x4be) [0x7fe6a7f9770e]
  (EE) 11: /usr/bin/X (AccessXFilterPressEvent+0x24b) [0x7fe6a7f9064b]
  (EE) 12: /usr/bin/X (mieqProcessDeviceEvent+0x1b5) [0x7fe6a7fbf385]
  (EE) 13: /usr/bin/X (mieqProcessInputEvents+0xf8) [0x7fe6a7fbf4a8]
  (EE) 14: /usr/bin/X (ProcessInputEvents+0x9) [0x7fe6a7ec8789]
  (EE) 15: /usr/bin/X (0x7fe6a7e35000+0x557d2) [0x7fe6a7e8a7d2]
  (EE) 16: /usr/bin/X (0x7fe6a7e35000+0x4456a) [0x7fe6a7e7956a]
  (EE) 17: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xed) 
[0x7fe6a5de076d]
  (EE) 18: /usr/bin/X (0x7fe6a7e35000+0x448ad) [0x7fe6a7e798ad]
  (EE)
  (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up 
the stack.
  (EE) [mi] mieq is *NOT* the cause.  It is a victim.
  [   682.730] [mi] EQ processing has resumed after 87 dropped events.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: xorg 1:7.7+1ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-36.57-generic 3.5.7.14
  Uname: Linux 3.5.0-36-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.6.1-0ubuntu11
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  Date: Fri Aug  9 15:20:46 2013
  DistUpgraded: 2013-07-15 13:05:10,878 DEBUG enabling apt cron job
  DistroCodename: quantal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices [AMD] nee ATI Thames XT/GL [Radeon HD 7600M Series] 
[1002:6840] (prog-if 00 [VGA controller])
     Subsystem: Toshiba America Info Systems Device [1179:fb31]
  InstallationDate: Installed on 2013-07-15 (25 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  MachineType: TOSHIBA Satellite Pro L850
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-36-generic 
root=UUID=37e1c61e-3c67-4da5-b08e-f2b9637da3d7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to quantal on 2013-07-15 (25 days ago)
  dmi.bios.date: 4/03/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.60
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: PLCSF8
  dmi.board.vendor: Intel
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.60:bd4/03/2013:svnTOSHIBA:pnSatelliteProL850:pvrPSKG9A-00C001:rvnIntel:rnPLCSF8:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite Pro L850
  dmi.product.version: PSKG9A-00C001
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.8.6-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.43-0ubuntu0.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.3-0ubuntu0.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.3-0ubuntu0.4
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.99.99~git20120913.8637f772-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2.2
  version.xserver-xorg-video-nouveau: xserve

[Touch-packages] [Bug 1351222] Re: URL parsing doesn't comply with RFC 3986

2014-11-03 Thread Ted Gould

** Changed in: url-dispatcher
   Status: In Progress => Fix Released

** Changed in: url-dispatcher (Ubuntu RTM)
   Status: New => Triaged

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

Title:
  URL parsing doesn't comply with RFC 3986

Status in Dialer app for Ubuntu Touch:
  In Progress
Status in URL Dispatcher:
  Fix Released
Status in “dialer-app” package in Ubuntu:
  New
Status in “url-dispatcher” package in Ubuntu:
  Fix Released
Status in “dialer-app” package in Ubuntu RTM:
  New
Status in “url-dispatcher” package in Ubuntu RTM:
  Triaged

Bug description:
  I tried opening a link without a path component (for example
  scheme:?param1=value1¶m2=value2) and I got back an error from URL
  dispatcher "com.canonical.URLDispatcher.BadURL: URL
  'scheme:?param1=value1¶m2=value2' is not handleable by the URL
  Dispatcher".

  I looked at the code, and it seems URL dispatcher parses URLs with the regex: 
^(.*)://([a-z0-9\\.-]*)?/?(.*)?$
  A URL doesn't have to look like that. Here is the URI grammar taken from the 
RFC:
  URI = scheme ":" hier-part [ "?" query ] [ "#" fragment ]
  hier-part = "//" authority path-abempty
  / path-absolute
  / path-rootless
  / path-empty

  Links that can't currently be parsed by URL dispatcher are for example magnet 
links (used for torrents).
  They look like: magnet:?xt=urn:ed2k:31D6CFE0D16AE931B73C59D7E0C089C0
  &xl=0&dn=zero_len.fil
  &xt=urn:bitprint:3I42H3S6NNFQ2MSVX7XZKYAYSCX5QBYJ
  .LWPNACQDBZRYXW3VHJVCJ64QBZNGHOHHHZWCLNQ
  &xt=urn:md5:D41D8CD98F00B204E9800998ECF8427E and therefore also can't be 
parsed by URL dispatcher.

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

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

[Touch-packages] [Bug 1256419] Re: libstdc++ pretty-printers don't work with Python 3

2014-11-03 Thread ori

This has been fixed upstream: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58962
Could the fix be applied for trusty?

** Bug watch added: GCC Bugzilla #58962
   https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58962

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

Title:
  libstdc++ pretty-printers don't work with Python 3

Status in “gcc-4.8” package in Ubuntu:
  Fix Released
Status in “gcc-4.9” package in Ubuntu:
  Fix Released
Status in “gcc-4.8” source package in Trusty:
  In Progress
Status in “gcc-4.9” source package in Trusty:
  Invalid
Status in “gcc-4.8” package in Debian:
  Fix Released
Status in “gcc-4.9” package in Debian:
  Fix Released

Bug description:
  Ubuntu builds gdb's Python support against Python 3, but the STL
  pretty-printers shipped with libstdc++ don't support Python 3:

  (gdb) python
  >import os, sys
  >stldir = '/usr/share/gcc-4.7/python/'
  >if os.path.isdir(stldir):
  >  sys.path.insert(0, stldir)
  >  from libstdcxx.v6.printers import register_libstdcxx_printers
  >  register_libstdcxx_printers (None)
  >end
  Traceback (most recent call last):
File "", line 5, in 
File "/usr/share/gcc-4.7/python/libstdcxx/v6/printers.py", line 45
  raise ValueError, "Cannot find type %s::%s" % (str(orig), name)
  ^
  SyntaxError: invalid syntax
  Error while executing Python code.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gcc-4.8 4.8.1-10ubuntu9
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Fri Nov 29 15:06:03 2013
  InstallationDate: Installed on 2012-12-02 (362 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: gcc-4.8
  UpgradeStatus: Upgraded to saucy on 2013-10-19 (41 days ago)

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

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

[Touch-packages] [Bug 1384358] Re: /usr/share/apport/whoopsie-upload-all:FileNotFoundError:process_report:add_gdb_info:/usr/share/apport/whoopsie-upload-all@161:collect_info:process_report

This bug was fixed in the package apport - 2.14.7-0ubuntu10

---
apport (2.14.7-0ubuntu10) vivid; urgency=medium

  * data/whoopsie-upload-all: confirm that the crash file exists before trying
to remove it. (LP: #1384358)
 -- Brian MurrayMon, 03 Nov 2014 17:01:55 -0800

** Changed in: apport (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  /usr/share/apport/whoopsie-upload-
  all:FileNotFoundError:process_report:add_gdb_info:/usr/share/apport
  /whoopsie-upload-all@161:collect_info:process_report

Status in “apport” package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding apport.  This problem was most recently seen with version
  2.14.7-0ubuntu8, the problem page at
  https://errors.ubuntu.com/problem/dbab8e45b9fc9d063763e2d8a03c06bac932293a
  contains more details.

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

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

[Touch-packages] [Bug 1378576] Re: /usr/bin/mtp-server:11:boost::asio::detail::epoll_reactor::run:do_run_one:boost::asio::detail::task_io_service::run:run:core::dbus::asio::Executor::run

2014-11-03 Thread Ricardo Salveti

** Also affects: mtp (Ubuntu RTM)
   Importance: Undecided
   Status: New

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

** Changed in: mtp (Ubuntu RTM)
   Importance: Undecided => Critical

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

Title:
  /usr/bin/mtp-
  
server:11:boost::asio::detail::epoll_reactor::run:do_run_one:boost::asio::detail::task_io_service::run:run:core::dbus::asio::Executor::run

Status in “mtp” package in Ubuntu:
  Fix Released
Status in “mtp” package in Ubuntu RTM:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding mtp.  This problem was most recently seen with version
  0.0.4+14.10.20140909-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/87eeef0f5fc222be4eec263453315ce37235a27d
  contains more details.

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

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

[Touch-packages] [Bug 1379836] Re: dialer and messaging app show unlocked pin as locked

This bug was fixed in the package telepathy-ofono -
0.2+14.10.20141015-0ubuntu1

---
telepathy-ofono (0.2+14.10.20141015-0ubuntu1) vivid; urgency=low

  [ Ubuntu daily release ]
  * New rebuild forced

  [ Tiago Salem Herrmann ]
  * Check if the SimManager interface is available and property not
empty before assuming the sim is locked. (LP: #1379836)
 -- Ubuntu daily releaseWed, 15 Oct 2014 
13:33:36 +

** Changed in: telepathy-ofono (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  dialer and messaging app show unlocked pin as locked

Status in Telepathy Ofono:
  In Progress
Status in “indicator-network” package in Ubuntu:
  Invalid
Status in “ofono” package in Ubuntu:
  New
Status in “telepathy-ofono” package in Ubuntu:
  Fix Released
Status in “telepathy-ofono” package in Ubuntu RTM:
  Confirmed

Bug description:
  Ubuntu System Settings and ofono say it's unlocked but trying to use
  the dialer and messaging app is blocked by thinking the PIN is locked.

  $ system-image-cli -i
  current build number: 81
  device name: mako
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2014-10-10 15:33:48
  version version: 81
  version ubuntu: 20141010.1
  version device: 20140929.1
  version custom: mako-0.7

  $ phablet-shell 
  /home/sergiusens/.ssh/known_hosts updated.
  Original contents retained as /home/sergiusens/.ssh/known_hosts.old
  Warning: Permanently added '[localhost]:' (RSA) to the list of known 
hosts.
  Welcome to Ubuntu Utopic Unicorn (development branch) (GNU/Linux 3.4.0-5-mako 
armv7l)

   * Documentation:  https://help.ubuntu.com/
  Last login: Fri Oct 10 15:37:40 2014 from localhost.localdomain
  phablet@ubuntu-phablet:~$ lis^C
  phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-modems 
  [ /ril_0 ]
  Features = gprs ussd net sms rat sim 
  Model = Fake Modem Model
  Powered = 1
  Emergency = 0
  Online = 1
  Interfaces = org.ofono.ConnectionManager org.ofono.CallBarring 
org.ofono.CallSettings org.ofono.SupplementaryServices 
org.ofono.NetworkRegistration org.ofono.CallForwarding org.ofono.SmartMessaging 
org.ofono.PushNotification org.ofono.MessageManager org.ofono.NetworkTime 
org.ofono.MessageWaiting org.ofono.RadioSettings org.ofono.SimManager 
org.ofono.CallVolume org.ofono.VoiceCallManager 
  Revision = M9615A-CEFWMAZM-2.0.1701.03
  Type = hardware
  Manufacturer = Fake Manufacturer
  Serial = 355136052657866
  Lockdown = 0
  [ org.ofono.ConnectionManager ]
  Bearer = hspa
  RoamingAllowed = 0
  Suspended = 0
  Powered = 1
  Attached = 1
  [ org.ofono.CallBarring ]
  VoiceIncoming = disabled
  VoiceOutgoing = disabled
  [ org.ofono.CallSettings ]
  CallingLineRestriction = off
  HideCallerId = default
  ConnectedLinePresentation = unknown
  ConnectedLineRestriction = unknown
  CallingLinePresentation = enabled
  CallingNamePresentation = unknown
  CalledLinePresentation = disabled
  VoiceCallWaiting = enabled
  [ org.ofono.SupplementaryServices ]
  State = idle
  [ org.ofono.NetworkRegistration ]
  Mode = auto
  Name = Personal
  LocationAreaCode = 394
  Status = registered
  CellId = 14122637
  MobileCountryCode = 722
  Technology = umts
  Strength = 61
  MobileNetworkCode = 34
  [ org.ofono.CallForwarding ]
  VoiceNotReachable = +541151009255
  VoiceNoReplyTimeout = 25
  VoiceUnconditional = 
  VoiceNoReply = +541151009255
  ForwardingFlagOnSim = 0
  VoiceBusy = +541151009255
  [ org.ofono.SmartMessaging ]
  [ org.ofono.PushNotification ]
  [ org.ofono.MessageManager ]
  Alphabet = default
  UseDeliveryReports = 0
  ServiceCenterAddress = +541151740055
  Bearer = cs-preferred
  [ org.ofono.NetworkTime ]
  [ org.ofono.MessageWaiting ]
  VoicemailWaiting = 0
  VoicemailMailboxNumber = *555
  VoicemailMessageCount = 0
  [ org.ofono.RadioSettings ]
  TechnologyPreference = umts
  ModemTechnologies = gsm umts 
  FastDormancy = 0
  [ org.ofono.SimManager ]
  CardIdentifier = 89543421113404033941
  ServiceNumbers = [Llam. a su Cargo] = '11' [Club Personal] = 
'*2582' [Personal] = '+810' [At. Clientes] = '*111' 
  Retries = 
  FixedDialing = 0
  SubscriberIdentity = 722341240403394
  MobileCountryCode = 722
  BarredDialing = 0
  PinRequired = none
  LockedPins = 
  SubscriberNumbers = 
  Present = 1
  PreferredLanguages = es e

[Touch-packages] [Bug 1358340] Re: [Indicators] Complete greeter profiles

This bug was fixed in the package indicator-transfer -
0.1+15.04.20141103-0ubuntu1

---
indicator-transfer (0.1+15.04.20141103-0ubuntu1) vivid; urgency=low

  [ Ted Gould ]
  * Fix menu path cut-and-paste error (LP: #1358340)
 -- Ubuntu daily releaseMon, 03 Nov 2014 
21:08:21 +

** Changed in: indicator-transfer (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  [Indicators] Complete greeter profiles

Status in The Date and Time Indicator:
  Invalid
Status in The Messaging Menu:
  In Progress
Status in Sound Menu:
  In Progress
Status in Transfer Indicator:
  In Progress
Status in Ubuntu UX bugs:
  Fix Committed
Status in The Unity 8 shell:
  Fix Released
Status in “gsettings-ubuntu-touch-schemas” package in Ubuntu:
  Fix Released
Status in “indicator-datetime” package in Ubuntu:
  Invalid
Status in “indicator-messages” package in Ubuntu:
  Fix Released
Status in “indicator-sound” package in Ubuntu:
  In Progress
Status in “indicator-transfer” package in Ubuntu:
  Fix Released
Status in “ubuntu-system-settings” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu RTM:
  Fix Released

Bug description:
  A recent change in the interest of security removed access to the
  indicators when the phone is locked and the greeter is showing.

  This was an accentual change based on a misunderstanding

  There had been a plan to support media playback control via the sound
  indicator. Without this the user must unlock the phone in order to
  simply pause the music or change songs, etc.

  
  Desired resolution:

  - Revert the change that caused this issue

  - Add a switch to System Settings to enable security conscious user to
  switch off Launcher and Greeter access while the phone is locked.
  This setting should *always* be off by default.
  

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

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

[Touch-packages] [Bug 1358340] Re: [Indicators] Complete greeter profiles

** Branch linked: lp:~ubuntu-branches/ubuntu/vivid/indicator-transfer
/vivid-proposed

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

Title:
  [Indicators] Complete greeter profiles

Status in The Date and Time Indicator:
  Invalid
Status in The Messaging Menu:
  In Progress
Status in Sound Menu:
  In Progress
Status in Transfer Indicator:
  In Progress
Status in Ubuntu UX bugs:
  Fix Committed
Status in The Unity 8 shell:
  Fix Released
Status in “gsettings-ubuntu-touch-schemas” package in Ubuntu:
  Fix Released
Status in “indicator-datetime” package in Ubuntu:
  Invalid
Status in “indicator-messages” package in Ubuntu:
  Fix Released
Status in “indicator-sound” package in Ubuntu:
  In Progress
Status in “indicator-transfer” package in Ubuntu:
  In Progress
Status in “ubuntu-system-settings” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu RTM:
  Fix Released

Bug description:
  A recent change in the interest of security removed access to the
  indicators when the phone is locked and the greeter is showing.

  This was an accentual change based on a misunderstanding

  There had been a plan to support media playback control via the sound
  indicator. Without this the user must unlock the phone in order to
  simply pause the music or change songs, etc.

  
  Desired resolution:

  - Revert the change that caused this issue

  - Add a switch to System Settings to enable security conscious user to
  switch off Launcher and Greeter access while the phone is locked.
  This setting should *always* be off by default.
  

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

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

[Touch-packages] [Bug 1379836] Re: dialer and messaging app show unlocked pin as locked

** Branch linked: lp:~ubuntu-branches/ubuntu/vivid/telepathy-ofono
/vivid-proposed

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

Title:
  dialer and messaging app show unlocked pin as locked

Status in Telepathy Ofono:
  In Progress
Status in “indicator-network” package in Ubuntu:
  Invalid
Status in “ofono” package in Ubuntu:
  New
Status in “telepathy-ofono” package in Ubuntu:
  In Progress
Status in “telepathy-ofono” package in Ubuntu RTM:
  Confirmed

Bug description:
  Ubuntu System Settings and ofono say it's unlocked but trying to use
  the dialer and messaging app is blocked by thinking the PIN is locked.

  $ system-image-cli -i
  current build number: 81
  device name: mako
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2014-10-10 15:33:48
  version version: 81
  version ubuntu: 20141010.1
  version device: 20140929.1
  version custom: mako-0.7

  $ phablet-shell 
  /home/sergiusens/.ssh/known_hosts updated.
  Original contents retained as /home/sergiusens/.ssh/known_hosts.old
  Warning: Permanently added '[localhost]:' (RSA) to the list of known 
hosts.
  Welcome to Ubuntu Utopic Unicorn (development branch) (GNU/Linux 3.4.0-5-mako 
armv7l)

   * Documentation:  https://help.ubuntu.com/
  Last login: Fri Oct 10 15:37:40 2014 from localhost.localdomain
  phablet@ubuntu-phablet:~$ lis^C
  phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-modems 
  [ /ril_0 ]
  Features = gprs ussd net sms rat sim 
  Model = Fake Modem Model
  Powered = 1
  Emergency = 0
  Online = 1
  Interfaces = org.ofono.ConnectionManager org.ofono.CallBarring 
org.ofono.CallSettings org.ofono.SupplementaryServices 
org.ofono.NetworkRegistration org.ofono.CallForwarding org.ofono.SmartMessaging 
org.ofono.PushNotification org.ofono.MessageManager org.ofono.NetworkTime 
org.ofono.MessageWaiting org.ofono.RadioSettings org.ofono.SimManager 
org.ofono.CallVolume org.ofono.VoiceCallManager 
  Revision = M9615A-CEFWMAZM-2.0.1701.03
  Type = hardware
  Manufacturer = Fake Manufacturer
  Serial = 355136052657866
  Lockdown = 0
  [ org.ofono.ConnectionManager ]
  Bearer = hspa
  RoamingAllowed = 0
  Suspended = 0
  Powered = 1
  Attached = 1
  [ org.ofono.CallBarring ]
  VoiceIncoming = disabled
  VoiceOutgoing = disabled
  [ org.ofono.CallSettings ]
  CallingLineRestriction = off
  HideCallerId = default
  ConnectedLinePresentation = unknown
  ConnectedLineRestriction = unknown
  CallingLinePresentation = enabled
  CallingNamePresentation = unknown
  CalledLinePresentation = disabled
  VoiceCallWaiting = enabled
  [ org.ofono.SupplementaryServices ]
  State = idle
  [ org.ofono.NetworkRegistration ]
  Mode = auto
  Name = Personal
  LocationAreaCode = 394
  Status = registered
  CellId = 14122637
  MobileCountryCode = 722
  Technology = umts
  Strength = 61
  MobileNetworkCode = 34
  [ org.ofono.CallForwarding ]
  VoiceNotReachable = +541151009255
  VoiceNoReplyTimeout = 25
  VoiceUnconditional = 
  VoiceNoReply = +541151009255
  ForwardingFlagOnSim = 0
  VoiceBusy = +541151009255
  [ org.ofono.SmartMessaging ]
  [ org.ofono.PushNotification ]
  [ org.ofono.MessageManager ]
  Alphabet = default
  UseDeliveryReports = 0
  ServiceCenterAddress = +541151740055
  Bearer = cs-preferred
  [ org.ofono.NetworkTime ]
  [ org.ofono.MessageWaiting ]
  VoicemailWaiting = 0
  VoicemailMailboxNumber = *555
  VoicemailMessageCount = 0
  [ org.ofono.RadioSettings ]
  TechnologyPreference = umts
  ModemTechnologies = gsm umts 
  FastDormancy = 0
  [ org.ofono.SimManager ]
  CardIdentifier = 89543421113404033941
  ServiceNumbers = [Llam. a su Cargo] = '11' [Club Personal] = 
'*2582' [Personal] = '+810' [At. Clientes] = '*111' 
  Retries = 
  FixedDialing = 0
  SubscriberIdentity = 722341240403394
  MobileCountryCode = 722
  BarredDialing = 0
  PinRequired = none
  LockedPins = 
  SubscriberNumbers = 
  Present = 1
  PreferredLanguages = es en pt it 
  MobileNetworkCode = 34
  [ org.ofono.CallVolume ]
  MicrophoneVolume = 0
  Muted = 1
  SpeakerVolume = 0
  [ org.ofono.VoiceCallManager ]
  EmergencyNumbers = 112 911

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

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

[Touch-packages] [Bug 1365079] Re: apport should gather package information about click packages

2014-11-03 Thread Brian Murray

However, its not possible to find these crashes in the Error Tracker
frontend because they don't have a crash signature.

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

Title:
  apport should gather package information about click packages

Status in “apport” package in Ubuntu:
  Triaged

Bug description:
  Bug 1324853 was about there being a click command line switch for
  gathering information about a click package.  This now exists and
  works:

  click info
  
/opt/click.ubuntu.com/com.ubuntu.developer.jdstrand.blabble/current/blabble.qml

  {
  "architecture": "all",
  "description": "Word search game",
  "framework": "ubuntu-sdk-14.10-qml-dev3",
  "hooks": {
  "blabble": {
  "apparmor": "blabble.json",
  "desktop": "blabble.desktop"
  }
  },
  "installed-size": "21615",
  "maintainer": "Jamie Strandboge ",
  "name": "com.ubuntu.developer.jdstrand.blabble",
  "title": "Blabble",
  "version": "0.5"
  }

  While the error tracker retracers will not be able to retrace these
  crashes, it would still be good if we could assign them to a package
  and include the package version.

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

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

[Touch-packages] [Bug 1384358] Re: /usr/share/apport/whoopsie-upload-all:FileNotFoundError:process_report:add_gdb_info:/usr/share/apport/whoopsie-upload-all@161:collect_info:process_report

2014-11-03 Thread Brian Murray

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

** Changed in: apport (Ubuntu)
 Assignee: (unassigned) => Brian Murray (brian-murray)

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

Title:
  /usr/share/apport/whoopsie-upload-
  all:FileNotFoundError:process_report:add_gdb_info:/usr/share/apport
  /whoopsie-upload-all@161:collect_info:process_report

Status in “apport” package in Ubuntu:
  In Progress

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding apport.  This problem was most recently seen with version
  2.14.7-0ubuntu8, the problem page at
  https://errors.ubuntu.com/problem/dbab8e45b9fc9d063763e2d8a03c06bac932293a
  contains more details.

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

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

[Touch-packages] [Bug 1384358] Re: /usr/share/apport/whoopsie-upload-all:FileNotFoundError:process_report:add_gdb_info:/usr/share/apport/whoopsie-upload-all@161:collect_info:process_report

** Branch linked: lp:~ubuntu-core-dev/ubuntu/vivid/apport/ubuntu

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

Title:
  /usr/share/apport/whoopsie-upload-
  all:FileNotFoundError:process_report:add_gdb_info:/usr/share/apport
  /whoopsie-upload-all@161:collect_info:process_report

Status in “apport” package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding apport.  This problem was most recently seen with version
  2.14.7-0ubuntu8, the problem page at
  https://errors.ubuntu.com/problem/dbab8e45b9fc9d063763e2d8a03c06bac932293a
  contains more details.

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

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

[Touch-packages] [Bug 1389028] [NEW] u1 account crashes and gets removed when installing app

2014-11-03 Thread Mathijs Veen

Public bug reported:

platform: Ubuntu touch
image: rtm #6
device: Mako

after updating to rtm #6 today, I tried installing an app from the
store. The app in question is the new Grooveshark app by Grooveshark
(NOT the one by Adnane Belmadiaf)

When I hit the install button, I get an error:

Sure enough, my U1 is gone fron the registered online accounts.

I can re-add my U1 account and try again to add the app but the same
thing happens every time. Even after a device reboot.

Note that it has something to do with this app. Other apps install normally.
(Needless to say i have not tried every app or scope in the store so there
might be others that trigger this as well.)

Cheers,

Mat

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

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

Title:
u1 account crashes and gets removed when installing app

Status in “ubuntu-system-settings-online-accounts” package in Ubuntu:
New

Bug description:
platform: Ubuntu touch
image: rtm #6
device: Mako

after updating to rtm #6 today, I tried installing an app from the
store. The app in question is the new Grooveshark app by Grooveshark
(NOT the one by Adnane Belmadiaf)

When I hit the install button, I get an error:

Sure enough, my U1 is gone fron the registered online accounts.

I can re-add my U1 account and try again to add the app but the same
thing happens every time. Even after a device reboot.

Note that it has something to do with this app. Other apps install normally.
(Needless to say i have not tried every app or scope in the store so there
might be others that trigger this as well.)

Cheers,

Mat

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

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

[Touch-packages] [Bug 1388962] Re: Black screen

2014-11-03 Thread Seth Arnold

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

Title:
  Black screen

Status in “xorg” package in Ubuntu:
  New

Bug description:
  I dont know what happened after i install my ati vga card setup file.
  The ubuntu is startup in black screen untel i hit alt+ctrl+f1 to go to
  terminal. Then i type startx , it goes to the interface but not as
  befor.  Pleas any help

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic i686
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Mon Nov  3 21:52:21 2014
  DistUpgraded: 2014-10-26 19:08:04,841 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.18, 3.16.0-23-generic, i686: installed
   virtualbox, 4.3.18, 3.16.0-24-generic, i686: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV550/M71 [Mobility Radeon HD 2300] 
[1002:7210] (rev ce) (prog-if 00 [VGA controller])
 Subsystem: Fujitsu Technology Solutions Device [1734:1107]
  InstallationDate: Installed on 2014-07-24 (101 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  MachineType: FUJITSU SIEMENS AMILO Pi 2530
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=616bb165-4813-4470-8ce1-b2a6a213fa85 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to utopic on 2014-10-26 (8 days ago)
  dmi.bios.date: 08/03/2007
  dmi.bios.vendor: Phoenix
  dmi.bios.version: 1.04C
  dmi.board.name: F42
  dmi.board.vendor: FUJITSU SIEMENS
  dmi.board.version: 00030D01
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU SIEMENS
  dmi.modalias: 
dmi:bvnPhoenix:bvr1.04C:bd08/03/2007:svnFUJITSUSIEMENS:pnAMILOPi2530:pvr:rvnFUJITSUSIEMENS:rnF42:rvr00030D01:cvnFUJITSUSIEMENS:ct10:cvr:
  dmi.product.name: AMILO Pi 2530
  dmi.sys.vendor: FUJITSU SIEMENS
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Mon Nov  3 21:42:59 2014
  xserver.configfile: default
  xserver.errors: Server terminated successfully (0). Closing log file.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.16.0-1ubuntu1
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1388336] Re: Browser is disabled easily

2014-11-03 Thread Seth Arnold

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

Title:
  Browser is disabled easily

Status in “xorg” package in Ubuntu:
  New

Bug description:
  My wifi is fine I cant do anything.  Chrome doesnt start sometimes it
  pops up and crashes.  Firefox does the same.  Can you recommend a good
  browser for free

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Oct 31 22:57:14 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus:
   asic0x, 1.0.1, 3.16.0-23-generic, x86_64: installed
   asic0x, 1.0.1, 3.16.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8280 / R3 Series] 
[1002:9836] (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Device [1179:fa26]
  InstallationDate: Installed on 2014-09-14 (48 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: TOSHIBA Satellite C55D-A
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=77cfc2d2-00ca-4b21-b2ae-9ef137c88a8d ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/15/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.60
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: MP
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.60:bd11/15/2013:svnTOSHIBA:pnSatelliteC55D-A:pvrPSCFWU-03H02X:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite C55D-A
  dmi.product.version: PSCFWU-03H02X
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Fri Oct 31 22:02:28 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.16.0-1ubuntu1
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1358340] Re: [Indicators] Complete greeter profiles

This bug was fixed in the package indicator-messages -
13.10.1+15.04.20141103-0ubuntu1

---
indicator-messages (13.10.1+15.04.20141103-0ubuntu1) vivid; urgency=low

  [ Ted Gould ]
  * Add filtering for lock screen. (LP: #1358340)

  [ Lars Uebernickel ]
  * libmessaging-menu: allow numbers in object paths (LP: #1384811)
  * libmessaging-menu: fix section link in the documentation and add
descriptions (LP: #1313561)
 -- Ubuntu daily releaseMon, 03 Nov 2014 
20:56:30 +

** Changed in: indicator-messages (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  [Indicators] Complete greeter profiles

Status in The Date and Time Indicator:
  Invalid
Status in The Messaging Menu:
  In Progress
Status in Sound Menu:
  In Progress
Status in Transfer Indicator:
  In Progress
Status in Ubuntu UX bugs:
  Fix Committed
Status in The Unity 8 shell:
  Fix Released
Status in “gsettings-ubuntu-touch-schemas” package in Ubuntu:
  Fix Released
Status in “indicator-datetime” package in Ubuntu:
  Invalid
Status in “indicator-messages” package in Ubuntu:
  Fix Released
Status in “indicator-sound” package in Ubuntu:
  In Progress
Status in “indicator-transfer” package in Ubuntu:
  In Progress
Status in “ubuntu-system-settings” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu RTM:
  Fix Released

Bug description:
  A recent change in the interest of security removed access to the
  indicators when the phone is locked and the greeter is showing.

  This was an accentual change based on a misunderstanding

  There had been a plan to support media playback control via the sound
  indicator. Without this the user must unlock the phone in order to
  simply pause the music or change songs, etc.

  
  Desired resolution:

  - Revert the change that caused this issue

  - Add a switch to System Settings to enable security conscious user to
  switch off Launcher and Greeter access while the phone is locked.
  This setting should *always* be off by default.
  

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

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

[Touch-packages] [Bug 1313561] Re: Description for MessagingMenuApp does not appear in devhelp

This bug was fixed in the package indicator-messages -
13.10.1+15.04.20141103-0ubuntu1

---
indicator-messages (13.10.1+15.04.20141103-0ubuntu1) vivid; urgency=low

  [ Ted Gould ]
  * Add filtering for lock screen. (LP: #1358340)

  [ Lars Uebernickel ]
  * libmessaging-menu: allow numbers in object paths (LP: #1384811)
  * libmessaging-menu: fix section link in the documentation and add
descriptions (LP: #1313561)
 -- Ubuntu daily releaseMon, 03 Nov 2014 
20:56:30 +

** Changed in: indicator-messages (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-messages in
Ubuntu.
https://bugs.launchpad.net/bugs/1313561

Title:
  Description for MessagingMenuApp does not appear in devhelp

Status in The Messaging Menu:
  New
Status in “indicator-messages” package in Ubuntu:
  Fix Released

Bug description:
  [Impact]
  The description of MessagingMenuApp contains an overview about how 
applications can integrate with the messaging menu. However, it is not included 
in the generated html and thus not visible in devhelp. The attached patch fixes 
this by referencing the right section in the doc string.

  [Test Case]
  Open devhelp, search for "MessagingMenuApp" and click on description. The 
section should be non-empty.

  [Regression Potential]
  The fix only touches documentation.

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

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

[Touch-packages] [Bug 1273524] Re: lxsession guest session shows error message "no session for pid "

2014-11-03 Thread Walter Lapchynski

i installed lightdm 1.8.4-0ubuntu1 from saucy (with lxsession
0.4.9.2-0ubuntu6) and i cannot confirm the bug.

i upgraded lxsession on that same system and i cannot confirm the bug.

long story short, regardless of lxsession version, the bug depends upon
lightdm.

** Summary changed:

- lxsession guest session shows error message "no session for pid "
+ guest session shows error message "no session for pid "

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

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

** Project changed: lightdm => lightdm (Ubuntu)

** Changed in: lightdm (Ubuntu)
   Status: Confirmed => Triaged

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

** Description changed:

  EXPECTED RESULTS:
  Log into guest session with no error messages.
  
  ACTUAL RESULTS:
  Upon log in to guest session, an error "no session for pid " is printed.
  
  STEPS TO REPRODUCE:
- 1. Using Lubuntu in trusty or utopic with either real or virtual hardware, 
log into guest session.
+ 1. Using Lubuntu in trusty, utopic, or vivid with either real or virtual 
hardware, log into guest session.
  2. After being logged in, see error message.
  
  AFFECTED VERSIONS:
- 0.4.9.2-0ubuntu7 to 0.4.9.2+git20140410-0ubuntu3
+ lightdm 1.10.0-0ubuntu3 to 1.12.1-0ubuntu1

** Summary changed:

- guest session shows error message "no session for pid "
+ LXDE guest session shows error message "no session for pid "

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

Title:
  LXDE guest session shows error message "no session for pid "

Status in One Hundred Papercuts:
  Confirmed
Status in “lightdm” package in Ubuntu:
  Triaged
Status in “lxsession” package in Ubuntu:
  Triaged

Bug description:
  EXPECTED RESULTS:
  Log into guest session with no error messages.

  ACTUAL RESULTS:
  Upon log in to guest session, an error "no session for pid " is printed.

  STEPS TO REPRODUCE:
  1. Using Lubuntu in trusty, utopic, or vivid with either real or virtual 
hardware, log into guest session.
  2. After being logged in, see error message.

  AFFECTED VERSIONS:
  lightdm 1.10.0-0ubuntu3 to 1.12.1-0ubuntu1

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

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

[Touch-packages] [Bug 1388647] Re: DRI_PRIME=1 has no effect in Ubuntu 14.10

2014-11-03 Thread Dominic Chambers

That's a clever trick, being able to downgrade dependencies like that.
Any pointers on how one goes about doing it, since even if I add
'trusty' sources to `/etc/apt/sources.list' then I still only see a
single version available to install if I run `apt-show-versions xserver-
xorg`?

Anyway, great work narrowing it down so quickly!

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

Title:
  DRI_PRIME=1 has no effect in Ubuntu 14.10

Status in “xorg” package in Ubuntu:
  Confirmed

Bug description:
  On an Optimus laptop with both GPUs enabled, having run this command
  so that the Nvidia GPU can be used to offload 3D work from the Intel
  GPU:

  ```
  xrandr --setprovideroffloadsink nouveau Intel
  ```

  Then running this command:

  ```
  DRI_PRIME=1 glxinfo | grep "OpenGL vendor string"
  ```

  provides the incorrect output:

  ```
  OpenGL vendor string: Intel Open Source Technology Center
  ```

  when it should actually show that the Nouveau driver is in use for the
  program.

  This worked previously in Ubuntu 14.04. Apart from only having a 3.16
  kernel (instead of 3.17) Ubuntu 14.10 actually supports recent enough
  versions of the requisite packages necesarry to get DRI 3 offloading
  support, so perhaps this is part of the problem.

  Or, more likely, I notice a Nouveau failure after startup, and then
  again after running xrandr commands, for example:

  ```
  [  170.912483] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  217.550205] thinkpad_acpi: EC reports that Thermal Table has changed
  [  223.857442] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [  223.858395] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [  223.860200] nouveau E[PBUS][:01:00.0] MMIO read of 0x 
FAULT at 0x002140 [ !ENGINE ]
  [  224.654622] thinkpad_acpi: EC reports that Thermal Table has changed
  [  825.172094] thinkpad_acpi: EC reports that Thermal Table has changed
  [  831.132156] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [  831.133030] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [  831.134832] nouveau E[PBUS][:01:00.0] MMIO read of 0x 
FAULT at 0x002140 [ !ENGINE ]
  ```

  Perhaps this is just a regression in either the Nouveau or Intel
  drivers for my hardware. I'm using a Lenovo T430. I can confirm that
  I'm able to start the laptop without errors when I only enable the
  Intel GPU or NVidia GPU separately, and only see this error when both
  GPUs are enabled simultaneously.

  Extra Info:

  1: Description:   Ubuntu 14.10
  Release:  14.10

  2: N/A

  3: The text 'nouveau' should have appeared in the output of the
  command.

  4: The text 'Intel' appeared in the output of the command.

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

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

[Touch-packages] [Bug 1384811] Re: indicator-messages quoting of application names overwrites version numbers

This bug was fixed in the package indicator-messages -
13.10.1+15.04.20141103-0ubuntu1

---
indicator-messages (13.10.1+15.04.20141103-0ubuntu1) vivid; urgency=low

  [ Ted Gould ]
  * Add filtering for lock screen. (LP: #1358340)

  [ Lars Uebernickel ]
  * libmessaging-menu: allow numbers in object paths (LP: #1384811)
  * libmessaging-menu: fix section link in the documentation and add
descriptions (LP: #1313561)
 -- Ubuntu daily releaseMon, 03 Nov 2014 
20:56:30 +

** Changed in: indicator-messages (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-messages in
Ubuntu.
https://bugs.launchpad.net/bugs/1384811

Title:
  indicator-messages quoting of application names overwrites version
  numbers

Status in The Messaging Menu:
  In Progress
Status in “indicator-messages” package in Ubuntu:
  Fix Released

Bug description:
  this means that sending messages from two versions of the same app
  fails with, e.g.,

  ** (process:2308): WARNING **: unable to export application interface:
  An object is already exported for the interface
  com.canonical.indicator.messages.application at
  
/com/canonical/indicator/messages/com_ubuntu_telegram_telegramdesktop

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

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

[Touch-packages] [Bug 1386711] Re: CVE-2014-4877 symlink arbitrary filesystem access

2014-11-03 Thread Seth Arnold

http://www.ubuntu.com/usn/usn-2393-1

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

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

Title:
  CVE-2014-4877 symlink arbitrary filesystem access

Status in “wget” package in Ubuntu:
  Fix Released

Bug description:
  wget prior to 1.16 allows for a web server to write arbitrary files on
  the client side. A Metasploit module is available for testing:

  https://github.com/rapid7/metasploit-framework/pull/4088

  the disclosure is here:

  https://community.rapid7.com/community/metasploit/blog/2014/10/28/r7-2014-15
  -gnu-wget-ftp-symlink-arbitrary-filesystem-access

  Redhat's bug is here:

  https://bugzilla.redhat.com/show_bug.cgi?id=1139181

  Vulnerable on:

  Description:  Ubuntu 13.10
  Release:  13.10

  Package version:

  wget:
Installed: 1.14-2ubuntu1
Candidate: 1.14-2ubuntu1
Version table:
   *** 1.14-2ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1273524] [NEW] guest session shows error message "no session for pid "

You have been subscribed to a public bug:

EXPECTED RESULTS:
Log into guest session with no error messages.

ACTUAL RESULTS:
Upon log in to guest session, an error "no session for pid " 
is printed.

STEPS TO REPRODUCE:
1. Using Lubuntu in trusty or utopic with either real or virtual hardware, log 
into guest session.
2. After being logged in, see error message.

AFFECTED VERSIONS:
0.4.9.2-0ubuntu7 to 0.4.9.2+git20140410-0ubuntu3

** Affects: hundredpapercuts
 Importance: Medium
 Status: Confirmed

** Affects: lightdm (Ubuntu)
 Importance: Undecided
 Status: Confirmed

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


** Tags: apport-bug i386 iso-testing trusty utopic vivid
-- 
guest session shows error message "no session for pid "
https://bugs.launchpad.net/bugs/1273524
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to lightdm 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 1373985] Re: foreground app doesn't get activated after we leave the lock screen

This bug was fixed in the package maliit-framework -
0.99.0+git20130923+17fdf86-0ubuntu3

---
maliit-framework (0.99.0+git20130923+17fdf86-0ubuntu3) vivid; urgency=medium

  [ Michael Sheldon ]
  * 0012-fix-focus-changes.patch: Only allow maliit to remove focus
from input fields (LP: #1373985)
 -- Ricardo Salveti de AraujoMon, 03 Nov 
2014 17:15:21 -0200

** Changed in: maliit-framework (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  foreground app doesn't get activated after we leave the lock screen

Status in “maliit-framework” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  Invalid
Status in “maliit-framework” package in Ubuntu RTM:
  In Progress

Bug description:
  Steps to reproduce the issue:
  1 - have unity8-dash on the foreground
  2 - lock the phone (reboot or have the display off and then turn it back on)
  3 - type you password [you're brought to unity8-dash]
  4 - tap on the looking glass icon in the top right [search bar text entry 
shows up with "Search apps" written on it]

  Expected outcome:
  A blinking cursor caret is displayed on the app search text entry and the VKB 
comes up.

  Actual outcome:
  Nothing happens.

  Causing unity-8 dash to be refocused, such as bringing the indicators
  panel down and then back up solves it.

  Comments:
  Happens with any application that happens to be in the foreground, 
unity8-dash being just one test case that is easy to reproduce.

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

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

[Touch-packages] [Bug 1378576] Re: /usr/bin/mtp-server:11:boost::asio::detail::epoll_reactor::run:do_run_one:boost::asio::detail::task_io_service::run:run:core::dbus::asio::Executor::run

This bug was fixed in the package mtp - 0.0.4+15.04.20141103-0ubuntu1

---
mtp (0.0.4+15.04.20141103-0ubuntu1) vivid; urgency=low

  [ Mathieu Trudel-Lapierre ]
  * Watch for exceptions in the dbus thread; and stop mtp-server
gracefully if there are any. (LP: #1378576)
 -- Ubuntu daily releaseMon, 03 Nov 2014 
19:24:01 +

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

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

Title:
  /usr/bin/mtp-
  
server:11:boost::asio::detail::epoll_reactor::run:do_run_one:boost::asio::detail::task_io_service::run:run:core::dbus::asio::Executor::run

Status in “mtp” package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding mtp.  This problem was most recently seen with version
  0.0.4+14.10.20140909-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/87eeef0f5fc222be4eec263453315ce37235a27d
  contains more details.

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

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

[Touch-packages] [Bug 1243233] Re: Holding Super key doesn't bring up shortcut overlay.

2014-11-03 Thread Wilfred

Hello everyone,

I found this post after a google search. I'm using 14.04.1 and still
experience this issue. With workspaces enabled the overlay doesn't work.
Otherwise no problem. My screen-resolution is 1024*768

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

Title:
  Holding Super key doesn't bring up shortcut overlay.

Status in Unity:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  After upgrading from 13.04 to 13.10, holding Super no longer brings up the 
help overlay. Holding Super worked before upgrading. Tapping the Super key 
still brings up the HUD, and holding it down still brings up the Launcher and 
after a second or so shows the numbers on the applications. In Compiz Config 
Manager, under Ubuntu Unity Plugin -> Launcher, the Key to show the Dash, 
Launcher and Help Overlay is set to Super. Under Ubuntu Unity Plugin -> 
General, Enable Shortcut Hints Overlay is checked.
  This is also known to affect 14.04 (without compiz) when workspaces are 
enabled and screen resolution is 1024x768.

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

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

[Touch-packages] [Bug 1378576] Re: /usr/bin/mtp-server:11:boost::asio::detail::epoll_reactor::run:do_run_one:boost::asio::detail::task_io_service::run:run:core::dbus::asio::Executor::run

** Branch linked: lp:~ubuntu-branches/ubuntu/vivid/mtp/vivid-proposed

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

Title:
  /usr/bin/mtp-
  
server:11:boost::asio::detail::epoll_reactor::run:do_run_one:boost::asio::detail::task_io_service::run:run:core::dbus::asio::Executor::run

Status in “mtp” package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding mtp.  This problem was most recently seen with version
  0.0.4+14.10.20140909-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/87eeef0f5fc222be4eec263453315ce37235a27d
  contains more details.

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

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

[Touch-packages] [Bug 1382020] Re: ido ftbfs in utopic

This bug was fixed in the package ido - 13.10.0+15.04.20141103-0ubuntu1

---
ido (13.10.0+15.04.20141103-0ubuntu1) vivid; urgency=low

  [ Ted Gould ]
  * Update tags for newer GObject Introsepction Scanner and disable
xorg-gtest tests (LP: #1382020)
 -- Ubuntu daily releaseMon, 03 Nov 2014 
20:57:41 +

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

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

Title:
  ido ftbfs in utopic

Status in “ido” package in Ubuntu:
  Fix Released

Bug description:
  ido ftbfs in utopic, on every architecture.

  seen in
  
http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20140914-utopic.html

GISCAN   Ido3-0.1.gir
  idomessagedialog.c:251: Warning: Ido3: "@Varargs" parameter is deprecated, 
please use "@..." instead:
   * @Varargs: arguments for @message_format
  ^
  idomessagedialog.c:315: Warning: Ido3: "@Varargs" parameter is deprecated, 
please use "@..." instead:
   * @Varargs: arguments for @message_format. They will be escaped to allow 
valid XML.
  ^
  idoprogressmenuitem.c:2: Error: Ido3: identifier not found on the first line:
   * Copyright 2013 Canonical Ltd.
 ^
GICOMP   Ido3-0.1.gir
  /usr/bin/vapigen --library=Ido3-0.1 \
--pkg gtk+-3.0 \
Ido3-0.1.gir
  Generation succeeded - 0 warning(s)

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

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

[Touch-packages] [Bug 1378480] Re: Location detection is always on, despite indicator

2014-11-03 Thread jtd

1a - On both OS build #5 and #6 (Channel: ubuntu-touch/ubuntu-rtm/14.09), I 
manually disable "GPS" and "Location detection".
2a - Then choose either "Restart" or "Power off." Upon boot, both settings are 
shown as selected/enabled.

1b - On both OS build #5 and #6 (Channel: ubuntu-touch/ubuntu-rtm/14.09), I 
manually disable "GPS" and "Location detection".
2b - Then start "Weather" app, click "Scan for location" and despite above 
disabled options, my geolocation is correctly suggested (was this previously 
stored when Touch installed?).
3b - Note, however, if I visit maps.google.com with "GPS" and "Location 
detection" disabled OR recently enabled, I receive "Your location could not be 
determined" (possibly see bug: 
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1368647).

***2a confirms "Location Detection (and very often, GPS too), will revert to 
being enabled, whenever I reboot my phone"
***Given 2b and 3b, I am not sure if I can confirm "Location detection is 
always on, despite indicator"

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

Title:
  Location detection is always on, despite indicator

Status in “location-service” package in Ubuntu:
  Confirmed

Bug description:
  Despite the fact that I have never actually accepted the TOS for HERE,
  and that I have explicitly disabled location detection in both the
  indicator menu, and in System Settings, Location Detection (and very
  often, GPS too), will revert to being enabled, whenever I reboot my
  phone.

  This happens on mako, krillin, and hammerhead; so I don't think it is
  device dependent, but an issue explicitly in the software.

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

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

[Touch-packages] [Bug 1386803] Re: [TOPBLOCKER] unity8 crashing a lot since image #126

2014-11-03 Thread Michał Sawicz

** Branch linked: lp:~thomas-voss/media-hub/disconnect-signal-
translation-layer-on-destruction

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

Title:
  [TOPBLOCKER] unity8 crashing a lot since image #126

Status in “dbus-cpp” package in Ubuntu:
  Fix Released
Status in “qtubuntu-media” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  Opinion
Status in “media-hub” package in Ubuntu RTM:
  Fix Released
Status in “qtubuntu-media” package in Ubuntu RTM:
  Fix Released

Bug description:
  Since RTM image #126 was released on friday, most users have been
  reporting frequent unity8 crashes. Some scenarios where this commonly
  happen appear to be:

  - Unlocking SIM cards for the first time
  - Tapping on snap notifications when receiving an SMS

  A lot of crashes are also observed during automated image testing.

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: unity8 8.00+14.10.20141017-0ubuntu1 [origin: unknown]
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Tue Oct 28 17:20:40 2014
  InstallationDate: Installed on 2014-10-28 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141028-030205)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1373985] Re: foreground app doesn't get activated after we leave the lock screen

** Branch linked: lp:~ubuntu-branches/ubuntu/vivid/maliit-framework
/vivid-proposed

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

Title:
  foreground app doesn't get activated after we leave the lock screen

Status in “maliit-framework” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  Invalid
Status in “maliit-framework” package in Ubuntu RTM:
  In Progress

Bug description:
  Steps to reproduce the issue:
  1 - have unity8-dash on the foreground
  2 - lock the phone (reboot or have the display off and then turn it back on)
  3 - type you password [you're brought to unity8-dash]
  4 - tap on the looking glass icon in the top right [search bar text entry 
shows up with "Search apps" written on it]

  Expected outcome:
  A blinking cursor caret is displayed on the app search text entry and the VKB 
comes up.

  Actual outcome:
  Nothing happens.

  Causing unity-8 dash to be refocused, such as bringing the indicators
  panel down and then back up solves it.

  Comments:
  Happens with any application that happens to be in the foreground, 
unity8-dash being just one test case that is easy to reproduce.

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

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

[Touch-packages] [Bug 1388999] [NEW] gdb is realy slow starting debugging.

2014-11-03 Thread Søren Holm

Public bug reported:

On binaries with a lot of symbols a massive performance degradation  has
happened between 14.04 and 14.10

I have bisected the gdb performance degradation to this gdb commit

commit 5840bf271c87c3fc14739173fdc91c6a14057130 (refs/bisect/bad)
Author: H.J. Lu 
Date:   Wed Jul 16 17:16:24 2014

Properly match PLT entry against .got.plt relocation

Relocations against .got.plt section may not be in the same order as
entries in PLT section.  It is incorrect to assume that the Ith reloction
index against .got.plt section always maps to the (I + 1)th entry in PLT
section.  This patch matches the .got.plt relocation offset/index in PLT
entry against the index in .got.plt relocation table.  It only checks
R_*_JUMP_SLOT and R_*_IRELATIVE relocations.  It ignores R_*_TLS_DESC
and R_*_TLSDESC relocations since they have different PLT entries.

bfd/

PR binutils/17154
* elf32-i386.c (elf_i386_plt_sym_val): Only match R_*_JUMP_SLOT
and R_*_IRELATIVE relocation offset with PLT entry.
* elf64-x86-64.c (elf_x86_64_plt_sym_val): Likewise.
(elf_x86_64_plt_sym_val_offset_plt_bnd): New.
(elf_x86_64_get_synthetic_symtab): Use it.

ld/testsuite/

PR binutils/17154
* ld-ifunc/pr17154-i386.d: New file.
* ld-ifunc/pr17154-x86-64.d: Likewise.
* ld-ifunc/pr17154-x86.s: Likewise.
* ld-x86-64/bnd-ifunc-2.d: Likewise.
* ld-x86-64/bnd-ifunc-2.s: Likewise.
* ld-x86-64/mpx.exp: Run bnd-ifunc-2.
* ld-x86-64/tlsdesc-nacl.pd: Updated.
* ld-x86-64/tlsdesc.pd: Likewise.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: gdb 7.8-1ubuntu4
ProcVersionSignature: Ubuntu 3.16.0-24.32-lowlatency 3.16.4
Uname: Linux 3.16.0-24-lowlatency x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: KDE
Date: Mon Nov  3 23:27:53 2014
InstallationDate: Installed on 2014-07-11 (115 days ago)
InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140710)
SourcePackage: gdb
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gdb (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 gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1388999

Title:
  gdb is realy slow starting debugging.

Status in “gdb” package in Ubuntu:
  New

Bug description:
  On binaries with a lot of symbols a massive performance degradation
  has happened between 14.04 and 14.10

  I have bisected the gdb performance degradation to this gdb commit

  commit 5840bf271c87c3fc14739173fdc91c6a14057130 (refs/bisect/bad)
  Author: H.J. Lu 
  Date:   Wed Jul 16 17:16:24 2014

  Properly match PLT entry against .got.plt relocation
  
  Relocations against .got.plt section may not be in the same order as
  entries in PLT section.  It is incorrect to assume that the Ith reloction
  index against .got.plt section always maps to the (I + 1)th entry in PLT
  section.  This patch matches the .got.plt relocation offset/index in PLT
  entry against the index in .got.plt relocation table.  It only checks
  R_*_JUMP_SLOT and R_*_IRELATIVE relocations.  It ignores R_*_TLS_DESC
  and R_*_TLSDESC relocations since they have different PLT entries.
  
  bfd/
  
  PR binutils/17154
  * elf32-i386.c (elf_i386_plt_sym_val): Only match R_*_JUMP_SLOT
  and R_*_IRELATIVE relocation offset with PLT entry.
  * elf64-x86-64.c (elf_x86_64_plt_sym_val): Likewise.
  (elf_x86_64_plt_sym_val_offset_plt_bnd): New.
  (elf_x86_64_get_synthetic_symtab): Use it.
  
  ld/testsuite/
  
  PR binutils/17154
  * ld-ifunc/pr17154-i386.d: New file.
  * ld-ifunc/pr17154-x86-64.d: Likewise.
  * ld-ifunc/pr17154-x86.s: Likewise.
  * ld-x86-64/bnd-ifunc-2.d: Likewise.
  * ld-x86-64/bnd-ifunc-2.s: Likewise.
  * ld-x86-64/mpx.exp: Run bnd-ifunc-2.
  * ld-x86-64/tlsdesc-nacl.pd: Updated.
  * ld-x86-64/tlsdesc.pd: Likewise.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: gdb 7.8-1ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-24.32-lowlatency 3.16.4
  Uname: Linux 3.16.0-24-lowlatency x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Nov  3 23:27:53 2014
  InstallationDate: Installed on 2014-07-11 (115 days ago)
  InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140710)
  SourcePackage: gdb
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1378480] Re: Location detection is always on, despite indicator

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

** Changed in: location-service (Ubuntu)
   Status: New => Confirmed

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

Title:
  Location detection is always on, despite indicator

Status in “location-service” package in Ubuntu:
  Confirmed

Bug description:
  Despite the fact that I have never actually accepted the TOS for HERE,
  and that I have explicitly disabled location detection in both the
  indicator menu, and in System Settings, Location Detection (and very
  often, GPS too), will revert to being enabled, whenever I reboot my
  phone.

  This happens on mako, krillin, and hammerhead; so I don't think it is
  device dependent, but an issue explicitly in the software.

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

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

[Touch-packages] [Bug 1389001] [NEW] Can not copy files by cp from Samsung S5 Mini in GVFS in MTP mode

2014-11-03 Thread Jarno Suni

Public bug reported:

In terminal:
jarnos@jarnos-OptiPlex-745:/run/user/1000/gvfs/mtp:host=%5Busb%3A002%2C013%5D/Card/DCIM/Camera$
 ls -l 20141103_114415.jpg ; cp 20141103_114415.jpg ~/Desktop/
-rw--- 1 jarnos jarnos 1205994 marra  3 11:44 20141103_114415.jpg
cp: cannot open ‘20141103_114415.jpg’ for reading: Operation not supported

But I can browse to the folder by Thunar or PCManFM and copy paste a
file to ~/Desktop/. On the other hand I can not open the files even via
those file managers.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: coreutils 8.21-1ubuntu5
ProcVersionSignature: Ubuntu 3.13.0-39.66-lowlatency 3.13.11.8
Uname: Linux 3.13.0-39-lowlatency x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Nov  4 00:19:11 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-09-21 (43 days ago)
InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.1)
SourcePackage: coreutils
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

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

Title:
  Can not copy files by cp from Samsung S5 Mini in GVFS in MTP mode

Status in “coreutils” package in Ubuntu:
  New

Bug description:
  In terminal:
  
jarnos@jarnos-OptiPlex-745:/run/user/1000/gvfs/mtp:host=%5Busb%3A002%2C013%5D/Card/DCIM/Camera$
 ls -l 20141103_114415.jpg ; cp 20141103_114415.jpg ~/Desktop/
  -rw--- 1 jarnos jarnos 1205994 marra  3 11:44 20141103_114415.jpg
  cp: cannot open ‘20141103_114415.jpg’ for reading: Operation not supported

  But I can browse to the folder by Thunar or PCManFM and copy paste a
  file to ~/Desktop/. On the other hand I can not open the files even
  via those file managers.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: coreutils 8.21-1ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-39.66-lowlatency 3.13.11.8
  Uname: Linux 3.13.0-39-lowlatency x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Nov  4 00:19:11 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-21 (43 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.1)
  SourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

2014-11-03 Thread Bruce MacNaughton

msp3k - I got the same thing but just ran unity --replace in a terminal
window I had left open on the desktop. I didn't check to see if could
open a terminal. But running unity --replace from the desktop (w/o dash,
launcher, panel, menu bar, etc.) resulted in getting them all back. It
was ugly - many errors but it worked. Everything seems fine afterwards.

Any idea when I can specifically target the software for an update? The
fix clearly hasn't hit me yet.

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

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

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

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

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

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

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

[Touch-packages] [Bug 1388359] Re: [TOPBLOCKER] User metrics can no longer be changed by double tap

2014-11-03 Thread Łukasz Zemczak

** Tags added: lt-blocker lt-category-visible lt-prio-high

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

Title:
  [TOPBLOCKER] User metrics can no longer be changed by double tap

Status in “unity8” package in Ubuntu:
  In Progress

Bug description:
  Krillin #139 proposed

  On the welcome screen I only see "No text messages sent today". In
  previous images double tapping the welcome screen would cycle through
  music played, phone calls made/received etc. I don't seem to be able
  to get it to move on.

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

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

[Touch-packages] [Bug 1373985] Re: foreground app doesn't get activated after we leave the lock screen

2014-11-03 Thread Ricardo Salveti

** Also affects: maliit-framework (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Changed in: maliit-framework (Ubuntu RTM)
   Status: New => In Progress

** Changed in: maliit-framework (Ubuntu RTM)
 Assignee: (unassigned) => Michael Sheldon (michael-sheldon)

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

Title:
  foreground app doesn't get activated after we leave the lock screen

Status in “maliit-framework” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  Invalid
Status in “maliit-framework” package in Ubuntu RTM:
  In Progress

Bug description:
  Steps to reproduce the issue:
  1 - have unity8-dash on the foreground
  2 - lock the phone (reboot or have the display off and then turn it back on)
  3 - type you password [you're brought to unity8-dash]
  4 - tap on the looking glass icon in the top right [search bar text entry 
shows up with "Search apps" written on it]

  Expected outcome:
  A blinking cursor caret is displayed on the app search text entry and the VKB 
comes up.

  Actual outcome:
  Nothing happens.

  Causing unity-8 dash to be refocused, such as bringing the indicators
  panel down and then back up solves it.

  Comments:
  Happens with any application that happens to be in the foreground, 
unity8-dash being just one test case that is easy to reproduce.

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

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

[Touch-packages] [Bug 1380848] Re: [TOPBLOCKER] Apps and services use large amount of CPU after unity8 resets

2014-11-03 Thread Łukasz Zemczak

** Tags added: lt-blocker lt-category-visible lt-prio-high

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

Title:
  [TOPBLOCKER] Apps and services use large amount of CPU after unity8
  resets

Status in Media Hub:
  In Progress
Status in “dbus-cpp” package in Ubuntu:
  New

Bug description:
  I noticed that media-hub-service can get into a state where it uses a
  large amount of CPU.

  Steps to reproduce
  1) Start music-app
  2) Play music
  3) Pause music
  4) Close the music-app
  5) $ pkill unity8 (to emulate unity crashing a resetting)

  Notice that media-hub-service is now using a large amount of CPU, note
  this [0] is the media-hub.log at the time.

  The device has to be reset to get the CPU usage back to normal.

  0 - http://pastebin.ubuntu.com/8553411/

To manage notifications about this bug go to:
https://bugs.launchpad.net/media-hub/+bug/1380848/+subscriptions

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

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

I'm agnostic as to the exact location. We just need to agree :-)

Currently, it is: ~/.local/share/unity-scopes/unconfined/@{APP_PKG_NAME}
for unconfined scopes, and ~/.local/share/unity-scopes/leaf-
net/@{APP_PKG_NAME} for confined scopes.

I can change this easily enough. However, currently,
~/.local/share/@{APP_PKGNAME} is used as the click *installation*
directory. That is the directory where the click package installs the
scope's .so and .ini file.

For data sharing between the application and the scope, I take it that
we are talking about the *cache* directory? It doesn't seem a good idea
to use the same directory for both installation files from the click
package, and data files that are created by the scope and/or the
application, so I think the install dir and the cache dir should be
different locations (but the new location you suggest is the same as the
current click installation location).

Is it OK to drop the leaf-net and unconfined components from the path?
Currently, a confined scope relies on being able to create the final
path component *itself* by calling mkdir(). So, assuming that
~/.local/share/unity-scopes/leaf-net exists, the scope will try to
create ~/.local/share/unity-scopes/leaf-net/@{APP_PKG_NAME}.

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

Title:
  add directory allowing scopes and apps to share data

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

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

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

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

Re: [Touch-packages] [Bug 1354924] Re: Networkmanager does not autoconnect to wireless network

2014-11-03 Thread Søren Holm

I can not see that file on my system.

I have these files.

-rwxr-xr-x 1 root root  549 Jan 18  2013 000resolvconf
-rwxr-xr-x 1 root root  881 Dec 30  2013 avahi-autoipd
-rwxr-xr-x 1 root root  484 Dec 30  2013 avahi-daemon
-rwxr-xr-x 1 root root 1675 Jan 28  2014 ethtool
-rwxr-xr-x 1 root root 1298 Apr  3  2013 ntpdate
-rwxr-xr-x 1 root root  945 Aug 13 01:59 openssh-server
-rwxr-xr-x 1 root root  374 May  2  2014 openvpn
-rwxr-xr-x 1 root root 1483 Jan  6  2013 upstart
lrwxrwxrwx 1 root root   32 Oct 10 16:53 wpasupplicant -> 
../../wpa_supplicant/ifupdown.sh

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

Title:
  Networkmanager does not autoconnect to wireless network

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

Bug description:
  When adding a net wireless network and enable "connect automatically'
  networkmanager does not automatically connect to the network wenever
  possible.

  I'm running kubuntu 14.10 daily.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: network-manager 0.9.8.8-0ubuntu23
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic x86_64
  ApportVersion: 2.14.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Aug 10 21:30:03 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-07-11 (29 days ago)
  InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140710)
  IpRoute:
   default via 192.168.0.2 dev wlan0  proto static 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.213  
metric 9
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1  
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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

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

[Touch-packages] [Bug 1376240] Re: pressing power button should silence incoming call

2014-11-03 Thread Andreas Pokorny

** Changed in: unity-system-compositor
   Status: New => In Progress

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

Title:
  pressing power button should silence incoming call

Status in Telephony Service:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in Unity System Compositor:
  In Progress
Status in “telephony-service” package in Ubuntu:
  New
Status in “unity-system-compositor” package in Ubuntu:
  New

Bug description:
  In the incoming call dialog there is no way to dismiss a call, only
  reject it.

  I would like a way to keep the calling active but in silent mode.

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

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

[Touch-packages] [Bug 1373985] Re: foreground app doesn't get activated after we leave the lock screen

2014-11-03 Thread Brendan Donegan

Definitely solves at least
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1385462 and
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1377817 for me. I
would suggest this fix is good

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

Title:
  foreground app doesn't get activated after we leave the lock screen

Status in “maliit-framework” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce the issue:
  1 - have unity8-dash on the foreground
  2 - lock the phone (reboot or have the display off and then turn it back on)
  3 - type you password [you're brought to unity8-dash]
  4 - tap on the looking glass icon in the top right [search bar text entry 
shows up with "Search apps" written on it]

  Expected outcome:
  A blinking cursor caret is displayed on the app search text entry and the VKB 
comes up.

  Actual outcome:
  Nothing happens.

  Causing unity-8 dash to be refocused, such as bringing the indicators
  panel down and then back up solves it.

  Comments:
  Happens with any application that happens to be in the foreground, 
unity8-dash being just one test case that is easy to reproduce.

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

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

[Touch-packages] [Bug 57797] Re: include aoTuV patch

2014-11-03 Thread bmhm

Please do not discuss OPUS. Most hw players have no opus support, thus
it is not an option.

Also, we will not drop kino because cinallera is better.

Make existing software as good as possible, as long as it has its
purpose. Vorbis definitely has one.

Please merge the current patch sets.

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

Title:
  include aoTuV patch

Status in Medibuntu:
  Invalid
Status in Ogg Vorbis:
  Confirmed
Status in “libvorbis” package in Ubuntu:
  Confirmed
Status in “libvorbis” package in Debian:
  Fix Released

Bug description:
  Would be nice to include aoTuV [1] Release 1 patch to libvorbis. aoTuV is an 
improved libvorbis encoder, that, while keeping ABI compatibility, gives many 
improvement:
  * better quality at all bitrates versus libvorbis-1.1.2 [2], giving aoTuV 
better quality than other codec (AAC, MP3, MPC, WMA, ...) [3];
  * support of quality down to -2 (32kb/s at 44kHz stereo), versus -1 (45kb/s 
at 44kHz stereo) of libvorbis-1.1.x;
  * encoding speed 10% better thanks to the included Vorbis-OptSort patch 
(improve ordering loop);

  aoTuV Release 1 have just been releases. aoTuV Release 1 is the same
  as of beta4.51 (released on 2005-11), renamed after a lot of testing
  of the audio community (especially on hydrogenaudio forum [4]) and
  this is the reccomended vorbis encoder [5].

  [1] aoTuV site: http://www.geocities.jp/aoyoume/aotuv/
  [2] comparison of aoTuV beta 4 vs libvorbis-1.1.x: 
http://wiki.xiph.org/index.php/VorbisEncoders
  [3] Wikipedia test of vorbis vs other codecs: 
http://en.wikipedia.org/wiki/Vorbis#Codec_comparisons
  [4] hydrogenaudio forum: http://www.hydrogenaudio.org
  [5] Recommended Ogg Vorbis: 
http://wiki.hydrogenaudio.org/index.php?title=Recommended_Ogg_Vorbis

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

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

[Touch-packages] [Bug 1373985] Re: foreground app doesn't get activated after we leave the lock screen

2014-11-03 Thread Olli Ries

** Tags added: rtm14

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

Title:
  foreground app doesn't get activated after we leave the lock screen

Status in “maliit-framework” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce the issue:
  1 - have unity8-dash on the foreground
  2 - lock the phone (reboot or have the display off and then turn it back on)
  3 - type you password [you're brought to unity8-dash]
  4 - tap on the looking glass icon in the top right [search bar text entry 
shows up with "Search apps" written on it]

  Expected outcome:
  A blinking cursor caret is displayed on the app search text entry and the VKB 
comes up.

  Actual outcome:
  Nothing happens.

  Causing unity-8 dash to be refocused, such as bringing the indicators
  panel down and then back up solves it.

  Comments:
  Happens with any application that happens to be in the foreground, 
unity8-dash being just one test case that is easy to reproduce.

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

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

[Touch-packages] [Bug 1388928] Re: high CPU load and system caught in loop when external monitor connected

2014-11-03 Thread Brian Murray

** Package changed: ubuntu => xorg (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/1388928

Title:
  high CPU load and system caught in loop when external monitor
  connected

Status in “xorg” package in Ubuntu:
  New

Bug description:
  When connecting my notebook to a specific projector and changing to
  the external display with xrandr (xrandr --output VGA1 --mode 1024x768
  --output LVDS1 --mode 1024x768), the system is caught in some kind of
  loop, with high CPU load and the graphical user interface getting
  unresponsive (mouse cursor jumps every few seconds). The problem
  "disappears" when the external display is turned off.

  The Xorg log file contains (repeating endlessly):

  [ 10219.665] (II) intel(0): EDID vendor "NEC", prod id 31181
  [ 10219.665] (II) intel(0): Using hsync ranges from config file
  [ 10219.665] (II) intel(0): Using vrefresh ranges from config file
  [ 10219.665] (II) intel(0): Printing DDC gathered Modelines:
  [ 10219.665] (II) intel(0): Modeline "1280x800"x0.0   83.50  1280 1352 1480 
1680  800 803 809 831 -hsync +vsync (49.7 kHz eP)
  [ 10219.665] (II) intel(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  
600 601 605 628 +hsync +vsync (37.9 kHz e)
  [ 10219.665] (II) intel(0): Modeline "800x600"x0.0   36.00  800 824 896 1024  
600 601 603 625 +hsync +vsync (35.2 kHz e)
  [ 10219.665] (II) intel(0): Modeline "640x480"x0.0   31.50  640 656 720 840  
480 481 484 500 -hsync -vsync (37.5 kHz e)
  [ 10219.665] (II) intel(0): Modeline "640x480"x0.0   31.50  640 664 704 832  
480 489 492 520 -hsync -vsync (37.9 kHz e)
  [ 10219.665] (II) intel(0): Modeline "640x480"x0.0   30.24  640 704 768 864  
480 483 486 525 -hsync -vsync (35.0 kHz e)
  [ 10219.665] (II) intel(0): Modeline "640x480"x0.0   25.18  640 656 752 800  
480 490 492 525 -hsync -vsync (31.5 kHz e)
  [ 10219.665] (II) intel(0): Modeline "720x400"x0.0   28.32  720 738 846 900  
400 412 414 449 -hsync +vsync (31.5 kHz e)
  [ 10219.665] (II) intel(0): Modeline "1280x1024"x0.0  135.00  1280 1296 1440 
1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
  [ 10219.665] (II) intel(0): Modeline "1024x768"x0.0   78.75  1024 1040 1136 
1312  768 769 772 800 +hsync +vsync (60.0 kHz e)
  [ 10219.665] (II) intel(0): Modeline "1024x768"x0.0   75.00  1024 1048 1184 
1328  768 771 777 806 -hsync -vsync (56.5 kHz e)
  [ 10219.665] (II) intel(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 
1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
  [ 10219.665] (II) intel(0): Modeline "832x624"x0.0   57.28  832 864 928 1152  
624 625 628 667 -hsync -vsync (49.7 kHz e)
  [ 10219.665] (II) intel(0): Modeline "800x600"x0.0   49.50  800 816 896 1056  
600 601 604 625 +hsync +vsync (46.9 kHz e)
  [ 10219.665] (II) intel(0): Modeline "800x600"x0.0   50.00  800 856 976 1040  
600 637 643 666 +hsync +vsync (48.1 kHz e)
  [ 10219.665] (II) intel(0): Modeline "1152x864"x0.0  108.00  1152 1216 1344 
1600  864 865 868 900 +hsync +vsync (67.5 kHz e)
  [ 10219.665] (II) intel(0): Modeline "1280x960"x0.0  108.00  1280 1376 1488 
1800  960 961 964 1000 +hsync +vsync (60.0 kHz e)
  [ 10219.665] (II) intel(0): Modeline "1400x1050"x0.0  121.75  1400 1488 1632 
1864  1050 1053 1057 1089 -hsync +vsync (65.3 kHz e)
  [ 10219.665] (II) intel(0): Modeline "1600x1200"x0.0  162.00  1600 1664 1856 
2160  1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
  [ 10219.665] (II) intel(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 
1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
  [ 10219.665] (II) intel(0): Modeline "1280x720"x60.0   74.48  1280 1336 1472 
1664  720 721 724 746 -hsync +vsync (44.8 kHz e)
  [ 10219.665] (II) intel(0): Modeline "1600x900"x60.0  119.00  1600 1696 1864 
2128  900 901 904 932 -hsync +vsync (55.9 kHz e)
  [ 10219.665] (II) intel(0): Modeline "1920x1080"x60.0  172.80  1920 2040 2248 
2576  1080 1081 1084 1118 -hsync +vsync (67.1 kHz e)
  [ 10220.237] (II) intel(0): EDID vendor "NEC", prod id 31181
  [ 10220.237] (II) intel(0): Using hsync ranges from config file
  [ 10220.237] (II) intel(0): Using vrefresh ranges from config file
  [ 10220.237] (II) intel(0): Printing DDC gathered Modelines:
  [ 10220.237] (II) intel(0): Modeline "1280x800"x0.0   83.50  1280 1352 1480 
1680  800 803 809 831 -hsync +vsync (49.7 kHz eP)
  [ 10220.237] (II) intel(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  
600 601 605 628 +hsync +vsync (37.9 kHz e)
  [ 10220.237] (II) intel(0): Modeline "800x600"x0.0   36.00  800 824 896 1024  
600 601 603 625 +hsync +vsync (35.2 kHz e)
  [ 10220.237] (II) intel(0): Modeline "640x480"x0.0   31.50  640 656 720 840  
480 481 484 500 -hsync -vsync (37.5 kHz e)
  [ 10220.237] (II) intel(0): Modeline "640x480"x0.0   31.50  640 664 704 832  
480 489 492 520 -hsync -vsync (37.9 kHz e)
  [ 10220.237] (II) intel(0): Modeline "640x480"x0.0   30.24  640 704 768 864  
480 483 486 525 -hs

[Touch-packages] [Bug 1387959] Re: [TOPBLOCKER] unity8 crash in image krillin rtm 139

2014-11-03 Thread kevin gunn

scratch that on
https://bugs.launchpad.net/unity-system-compositor/+bug/1359951
seems the driver thread spawing is unrelated to the crash we're seeing. (which 
makes sense, it's been in there since the beginning)

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

Title:
  [TOPBLOCKER] unity8 crash in image krillin rtm 139

Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  Earlier today, a few QA folks tested image krillin rtm 138 plus silo
  13, and found that it fixed the unity8 crash from bug 1382595.

  Silo 13 plus silo 10 landed in image 139.

  Now, in image 139, unity8 is crashy again.  Olli mentioned getting two
  crashes within a few minutes, and I got a unity8 crash while trying to
  accept an incoming call.  I'm not sure if it's the same crash as
  before, or if it's a new one.

  Attached is the crash dump I got just after hitting 'accept' for an
  incoming call.  I tried to pre-process it in apport-cli, but it failed
  with "Sorry, the program "unity8" closed unexpectedly  //  Your
  computer does not have enough free memory to automatically analyze the
  problem and send a report to the developers."

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

-- 
Mailing list: https://launchpad.net/~touch-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-11-03 Thread taiebot65

A little explanation about how is being used the sim toolkit in the african 
market
 http://blog.nyaruka.com/androids-achilles-heal-the-sim-toolkit

-- 
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 1388928] [NEW] high CPU load and system caught in loop when external monitor connected

You have been subscribed to a public bug:

When connecting my notebook to a specific projector and changing to the
external display with xrandr (xrandr --output VGA1 --mode 1024x768
--output LVDS1 --mode 1024x768), the system is caught in some kind of
loop, with high CPU load and the graphical user interface getting
unresponsive (mouse cursor jumps every few seconds). The problem
"disappears" when the external display is turned off.

The Xorg log file contains (repeating endlessly):

[ 10219.665] (II) intel(0): EDID vendor "NEC", prod id 31181
[ 10219.665] (II) intel(0): Using hsync ranges from config file
[ 10219.665] (II) intel(0): Using vrefresh ranges from config file
[ 10219.665] (II) intel(0): Printing DDC gathered Modelines:
[ 10219.665] (II) intel(0): Modeline "1280x800"x0.0   83.50  1280 1352 1480 
1680  800 803 809 831 -hsync +vsync (49.7 kHz eP)
[ 10219.665] (II) intel(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  
600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 10219.665] (II) intel(0): Modeline "800x600"x0.0   36.00  800 824 896 1024  
600 601 603 625 +hsync +vsync (35.2 kHz e)
[ 10219.665] (II) intel(0): Modeline "640x480"x0.0   31.50  640 656 720 840  
480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 10219.665] (II) intel(0): Modeline "640x480"x0.0   31.50  640 664 704 832  
480 489 492 520 -hsync -vsync (37.9 kHz e)
[ 10219.665] (II) intel(0): Modeline "640x480"x0.0   30.24  640 704 768 864  
480 483 486 525 -hsync -vsync (35.0 kHz e)
[ 10219.665] (II) intel(0): Modeline "640x480"x0.0   25.18  640 656 752 800  
480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 10219.665] (II) intel(0): Modeline "720x400"x0.0   28.32  720 738 846 900  
400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 10219.665] (II) intel(0): Modeline "1280x1024"x0.0  135.00  1280 1296 1440 
1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 10219.665] (II) intel(0): Modeline "1024x768"x0.0   78.75  1024 1040 1136 
1312  768 769 772 800 +hsync +vsync (60.0 kHz e)
[ 10219.665] (II) intel(0): Modeline "1024x768"x0.0   75.00  1024 1048 1184 
1328  768 771 777 806 -hsync -vsync (56.5 kHz e)
[ 10219.665] (II) intel(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 
1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 10219.665] (II) intel(0): Modeline "832x624"x0.0   57.28  832 864 928 1152  
624 625 628 667 -hsync -vsync (49.7 kHz e)
[ 10219.665] (II) intel(0): Modeline "800x600"x0.0   49.50  800 816 896 1056  
600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 10219.665] (II) intel(0): Modeline "800x600"x0.0   50.00  800 856 976 1040  
600 637 643 666 +hsync +vsync (48.1 kHz e)
[ 10219.665] (II) intel(0): Modeline "1152x864"x0.0  108.00  1152 1216 1344 
1600  864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 10219.665] (II) intel(0): Modeline "1280x960"x0.0  108.00  1280 1376 1488 
1800  960 961 964 1000 +hsync +vsync (60.0 kHz e)
[ 10219.665] (II) intel(0): Modeline "1400x1050"x0.0  121.75  1400 1488 1632 
1864  1050 1053 1057 1089 -hsync +vsync (65.3 kHz e)
[ 10219.665] (II) intel(0): Modeline "1600x1200"x0.0  162.00  1600 1664 1856 
2160  1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
[ 10219.665] (II) intel(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 
1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 10219.665] (II) intel(0): Modeline "1280x720"x60.0   74.48  1280 1336 1472 
1664  720 721 724 746 -hsync +vsync (44.8 kHz e)
[ 10219.665] (II) intel(0): Modeline "1600x900"x60.0  119.00  1600 1696 1864 
2128  900 901 904 932 -hsync +vsync (55.9 kHz e)
[ 10219.665] (II) intel(0): Modeline "1920x1080"x60.0  172.80  1920 2040 2248 
2576  1080 1081 1084 1118 -hsync +vsync (67.1 kHz e)
[ 10220.237] (II) intel(0): EDID vendor "NEC", prod id 31181
[ 10220.237] (II) intel(0): Using hsync ranges from config file
[ 10220.237] (II) intel(0): Using vrefresh ranges from config file
[ 10220.237] (II) intel(0): Printing DDC gathered Modelines:
[ 10220.237] (II) intel(0): Modeline "1280x800"x0.0   83.50  1280 1352 1480 
1680  800 803 809 831 -hsync +vsync (49.7 kHz eP)
[ 10220.237] (II) intel(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  
600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 10220.237] (II) intel(0): Modeline "800x600"x0.0   36.00  800 824 896 1024  
600 601 603 625 +hsync +vsync (35.2 kHz e)
[ 10220.237] (II) intel(0): Modeline "640x480"x0.0   31.50  640 656 720 840  
480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 10220.237] (II) intel(0): Modeline "640x480"x0.0   31.50  640 664 704 832  
480 489 492 520 -hsync -vsync (37.9 kHz e)
[ 10220.237] (II) intel(0): Modeline "640x480"x0.0   30.24  640 704 768 864  
480 483 486 525 -hsync -vsync (35.0 kHz e)
[ 10220.237] (II) intel(0): Modeline "640x480"x0.0   25.18  640 656 752 800  
480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 10220.237] (II) intel(0): Modeline "720x400"x0.0   28.32  720 738 846 900  
400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 10220.237] (II) intel(0): Modeline "1280x1024"x0.0  135.00  1280 1296 1440 
1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 10220.237] (

[Touch-packages] [Bug 1387959] Re: [TOPBLOCKER] unity8 crash in image krillin rtm 139

2014-11-03 Thread Michał Sawicz

Re: threads, there was bug #1359951 before, it was concluded that the
thread is created and destroyed by either the driver or the hwcomposer,
not much can be done without vendor support.

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

Title:
  [TOPBLOCKER] unity8 crash in image krillin rtm 139

Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  Earlier today, a few QA folks tested image krillin rtm 138 plus silo
  13, and found that it fixed the unity8 crash from bug 1382595.

  Silo 13 plus silo 10 landed in image 139.

  Now, in image 139, unity8 is crashy again.  Olli mentioned getting two
  crashes within a few minutes, and I got a unity8 crash while trying to
  accept an incoming call.  I'm not sure if it's the same crash as
  before, or if it's a new one.

  Attached is the crash dump I got just after hitting 'accept' for an
  incoming call.  I tried to pre-process it in apport-cli, but it failed
  with "Sorry, the program "unity8" closed unexpectedly  //  Your
  computer does not have enough free memory to automatically analyze the
  problem and send a report to the developers."

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

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

[Touch-packages] [Bug 1387959] Re: [TOPBLOCKER] unity8 crash in image krillin rtm 139

2014-11-03 Thread kevin gunn

worried this may be a duplicate of this
https://bugs.launchpad.net/unity-system-compositor/+bug/1359951

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

Title:
  [TOPBLOCKER] unity8 crash in image krillin rtm 139

Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  Earlier today, a few QA folks tested image krillin rtm 138 plus silo
  13, and found that it fixed the unity8 crash from bug 1382595.

  Silo 13 plus silo 10 landed in image 139.

  Now, in image 139, unity8 is crashy again.  Olli mentioned getting two
  crashes within a few minutes, and I got a unity8 crash while trying to
  accept an incoming call.  I'm not sure if it's the same crash as
  before, or if it's a new one.

  Attached is the crash dump I got just after hitting 'accept' for an
  incoming call.  I tried to pre-process it in apport-cli, but it failed
  with "Sorry, the program "unity8" closed unexpectedly  //  Your
  computer does not have enough free memory to automatically analyze the
  problem and send a report to the developers."

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

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

[Touch-packages] [Bug 1366743] Re: Ubuntu 14.04 only prints LibreOffice Docs

2014-11-03 Thread Hans Maier

I added a screenshot of the installed packages that get listed if I
search for ghostscript in synaptic.

** Attachment added: "Bildschirmfoto vom 2014-11-03 21:47:02.png"

https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1366743/+attachment/4252249/+files/Bildschirmfoto%20vom%202014-11-03%2021%3A47%3A02.png

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

Title:
Ubuntu 14.04 only prints LibreOffice Docs

Status in “cups” package in Ubuntu:
Incomplete

Bug description:
I use Ubuntu 14.04, a Logilink Fast Ethernet Printserver and a HP
Color Laserjet 2550L. Under Ubuntu 12.10 everything worked fine and I
could print any file.

The printer is connected via a USB to the Printserver and adressed via
HP Jet Direct. As already said, everything worked fine under 12.10 and
I didn't change any settings on the printserver.

I use the ubuntu tool for installing the printer, as a normal user not
su. Searching the network, for network printers offers me three
possibilities for adressing the printer. HP Jet Direct, IPP and
LPD/LPR. I tried all of them with the same result. I use the drivers
from the Database, not surprisingly HP/Color Laserjet 2550/HP Color
Laserjet 2550 Series Postscript [en] (recommended).

After installing the printer the first thing that fails is the
Testpage. The ubunut printer spooler tells me that the job is in
progress and the printer starts to blink to tell me that he is
receiving input. Unfortunatly the job never starts or gets finished.
After blinking quite a while the printer stops an nothing happes.

Interestingly, after canceling the job on my computer and a restart of
the printer, the printserver and my computer, I can open libre office
writing "Hello World" go to print and the printer starts immediately
and prints the correct result. But this only works for libreoffice and
only with text, as soon as there is an image in the document it
doesn't work. I can't print any pdf or even from gedit. Nothing works.
Always the same as with the Testpage. Printer starts to blink but
nothing happens.

lsb_release -rd
Description: Ubuntu 14.04.1 LTS
Release: 14.04

Thanks for Help.

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

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

[Touch-packages] [Bug 1366743] Re: Ubuntu 14.04 only prints LibreOffice Docs

2014-11-03 Thread Hans Maier

hans@Hacker:~/lpadmin -p HP-Color-LaserJet-2550 -o pdftops-renderer-
default=gs

hans@Hacker:~/printerdata$ lpr -P HP-Color-LaserJet-2550 -o psdebug
FC.pdf

As before

hans@Hacker:~/printerdata$ sudo restart cups
[sudo] password for hans:
cups start/running, process 7966
hans@Hacker:~/printerdata$ lp -d HP-Color-LaserJet-2550 -o psdebug FC.pdf
request id is HP-Color-LaserJet-2550-57 (1 file(s))

Again nothing... :(

hans@Hacker:~/printerdata$ sudo gedit /etc/cups/cups-files.conf
hans@Hacker:~/printerdata$ sudo restart cups
cups start/running, process 8983
hans@Hacker:~/printerdata$ lpadmin -p test -E -v file:/tmp/printout -P
/etc/cups/ppd/HP-Color-LaserJet-2550.ppd

Start the printing of FC.pdf with "test"

hans@Hacker:~/printerdata$ sudo cp /tmp/printout ~
hans@Hacker:~/printerdata$ sudo chmod 777 ~/printout
hans@Hacker:~/printerdata$ cd ..
hans@Hacker:~$ ls -l | grep printout
-rwxrwxrwx 1 root root 300692 Nov 3 21:35 printout
hans@Hacker:~$ nc -w1 10.0.0.5 9100 < printout
^C
hans@Hacker:~$

Again nothing. I uploaded the new printout. Interestingly it seems to be
still produced by cairo/poppler "pdftops" filter. I entered the command
"lpadmin -p HP-Color-LaserJet-2550 -o pdftops-renderer-default=gs"
several times, even with restarts but the output was always the same. Do
I need to have some special package installed to get that to work?

** Attachment added: "printout"

https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1366743/+attachment/4252248/+files/printout

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

Title:
Ubuntu 14.04 only prints LibreOffice Docs

Status in “cups” package in Ubuntu:
Incomplete

Bug description:
I use Ubuntu 14.04, a Logilink Fast Ethernet Printserver and a HP
Color Laserjet 2550L. Under Ubuntu 12.10 everything worked fine and I
could print any file.

The printer is connected via a USB to the Printserver and adressed via
HP Jet Direct. As already said, everything worked fine under 12.10 and
I didn't change any settings on the printserver.

lsb_release -rd
Description: Ubuntu 14.04.1 LTS
Release: 14.04

Thanks for Help.

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

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

[Touch-packages] [Bug 1388349] Re: Crashes X when viewing certain websites

2014-11-03 Thread Chris Wilson

** Package changed: xserver-xorg-video-intel (Ubuntu) => mesa (Ubuntu)

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

Title:
  Crashes X when viewing certain websites

Status in “chromium-browser” package in Ubuntu:
  New
Status in “mesa” package in Ubuntu:
  New

Bug description:
  Just visiting some URLs will crash X and bring down the whole system
  without warning. Reproducible example: visit http://ello.co/jondcook
  in Chromium and the GPU will crash.

  Ubuntu 12.04.5 LTS

  [75195.004056] [drm] stuck on render ring
  [75195.004067] [drm] GPU crash dump saved to /sys/class/drm/card0/error
  [75195.004071] [drm] GPU hangs can indicate a bug anywhere in the entire gfx 
stack, including userspace.
  [75195.004075] [drm] Please file a _new_ bug report on bugs.freedesktop.org 
against DRI -> DRM/Intel
  [75195.004078] [drm] drm/i915 developers can then reassign to the right 
component if it's not a kernel issue.
  [75195.004082] [drm] The gpu crash dump is required to analyze gpu hangs, so 
please always attach it.
  [75195.005398] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo 
(0x2088000 ctx 0) at 0x2089954
  [75195.512106] [drm:i915_reset] *ERROR* Failed to reset chip.
  [75200.348321] Watchdog[5421]: segfault at 0 ip aff4a4c8 sp ad0c4cf0 error 6 
in libcontent.so[af72f000+11ee000]
  [75205.036042] [drm:i915_gem_wait_for_error] *ERROR* Timed out waiting for 
the gpu reset to complete
  [75205.092053] [drm] GMBUS [i915 gmbus vga] timed out, falling back to bit 
banging on pin 2
  [75205.119530] [ cut here ]
  [75205.119593] WARNING: CPU: 0 PID: 1931 at 
/build/buildd/linux-lts-trusty-3.13.0/drivers/gpu/drm/i915/intel_display.c:922 
assert_pll+0x7a/0x80 [i915]()
  [75205.119597] PLL state assertion failure (expected on, current off)
  [75205.119600] Modules linked in: usb_storage nls_iso8859_1 serpent_sse2_i586 
ablk_helper cryptd glue_helper lrw serpent_generic twofish_generic twofish_i586 
twofish_common xts gf128mul hidp hid nvram pci_stub vboxpci(OX) vboxnetadp(OX) 
vboxnetflt(OX) vboxdrv(OX) ctr ccm vsock zram(C) bnep rfcomm parport_pc ppdev 
binfmt_misc dm_crypt joydev xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 
btusb bluetooth ipt_REJECT xt_LOG xt_multiport xt_limit xt_tcpudp xt_addrtype 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_state ip6table_filter ip6_tables 
nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat 
nf_conntrack_ftp nf_conntrack iptable_filter snd_hda_codec_si3054 
snd_hda_codec_realtek ip_tables x_tables snd_hda_intel hp_wmi snd_hda_codec 
sparse_keymap snd_hwdep arc4 snd_pcm r852 snd_seq_midi snd_rawmidi 
snd_seq_midi_event iwl3945 sm_common nand iwlegacy mtd snd_seq nand_ids 
nand_bch snd_timer bch r592 mac80211 nand_ecc psmouse memstick lpc_ich 
serio_raw snd_seq_device cfg80211 snd soundcore snd_page_alloc mac_hid coretemp 
lp parport i915 firewire_ohci drm_kms_helper firewire_core drm ahci crc_itu_t 
libahci i2c_algo_bit r8169 sdhci_pci sdhci mii video wmi
  [75205.119720] CPU: 0 PID: 1931 Comm: upowerd Tainted: G C OX 
3.13.0-39-generic #66~precise1-Ubuntu
  [75205.119724] Hardware name: Hewlett-Packard Presario V6500 Notebook PC  
  /30CC, BIOS F.5A  03/22/2010
  [75205.119727]    ee449c50 c1683110 f89adb0c ee449c80 
c1059c54 f89afb04
  [75205.119737]  ee449cac 078b f89adb0c 039a f895e0fa f895e0fa 
0001 0001
  [75205.119746]  0001 ee449c98 c1059d13 0009 ee449c90 f89afb04 
ee449cac ee449cbc
  [75205.119755] Call Trace:
  [75205.119766]  [] dump_stack+0x41/0x52
  [75205.119776]  [] warn_slowpath_common+0x84/0xa0
  [75205.119813]  [] ? assert_pll+0x7a/0x80 [i915]
  [75205.119847]  [] ? assert_pll+0x7a/0x80 [i915]
  [75205.119852]  [] warn_slowpath_fmt+0x33/0x40
  [75205.119887]  [] assert_pll+0x7a/0x80 [i915]
  [75205.119928]  [] intel_crtc_load_lut+0x194/0x1a0 [i915]
  [75205.119961]  [] ? i9xx_enable_pll+0x11c/0x190 [i915]
  [75205.119994]  [] i9xx_crtc_enable+0xa8/0x150 [i915]
  [75205.120059]  [] __intel_set_mode+0x244/0x2f0 [i915]
  [75205.120106]  [] ? 
intel_framebuffer_create_for_mode.constprop.57+0xa3/0xb0 [i915]
  [75205.120150]  [] intel_set_mode+0x27/0x40 [i915]
  [75205.120189]  [] intel_get_load_detect_pipe+0x21d/0x300 [i915]
  [75205.120237]  [] intel_tv_detect+0x125/0x230 [i915]
  [75205.120252]  [] ? lockref_get_not_dead+0x11/0x40
  [75205.120280]  [] status_show+0x3d/0x80 [drm]
  [75205.120286]  [] ? __kmalloc+0xa4/0x210
  [75205.120310]  [] ? dpms_show+0x60/0x60 [drm]
  [75205.120317]  [] dev_attr_show+0x1f/0x50
  [75205.120324]  [] sysfs_seq_show+0x103/0x1e0
  [75205.120329]  [] ? root_device_unregister+0x30/0x30
  [75205.120335]  [] seq_read+0xde/0x360
  [75205.120340]  [] vfs_read+0x84/0x160
  [75205.120345]  [] ? seq_lseek+0x160/0x160
  [75205.120350]  [] SyS_read+0x57/0xa0
  [75205.120355]  [] sysenter_do_call+0x12/0x1

[Touch-packages] [Bug 1358343] Re: [TOPBLOCKER] too easy to answer a call by accident

This bug was fixed in the package telephony-service - 0.1+14.10.20141031
~rtm-0ubuntu1

---
telephony-service (0.1+14.10.20141031~rtm-0ubuntu1) 14.09; urgency=low

  [ Tiago Salem Herrmann ]
  * Use swipe to answer/reject calls (LP: #1358343)
 -- Ubuntu daily releaseFri, 31 Oct 2014 
10:59:48 +

** Changed in: telephony-service (Ubuntu RTM)
   Status: Confirmed => Fix Released

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

Title:
  [TOPBLOCKER] too easy to answer a call by accident

Status in Telephony Service:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in “dialer-app” package in Ubuntu:
  Invalid
Status in “telephony-service” package in Ubuntu:
  Confirmed
Status in “unity-notifications” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  In Progress
Status in “telephony-service” package in Ubuntu RTM:
  Fix Released
Status in “unity-notifications” package in Ubuntu RTM:
  In Progress
Status in “unity8” package in Ubuntu RTM:
  In Progress

Bug description:
  If you put the phone in your pocket with locked screen and you receive
  a call is too easy to answer or reject that by mistake. Or pressing
  the screen while trying to get the phone or the call can be answered
  without you noticed by your pocket.

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

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

[Touch-packages] [Bug 1381041] Re: [TOPBLOCKER] Network indicator is sometimes blank

This bug was fixed in the package indicator-network -
0.5.1+14.10.20141031.3~rtm-0ubuntu1

---
indicator-network (0.5.1+14.10.20141031.3~rtm-0ubuntu1) 14.09; urgency=low

  [ Jussi Pakkanen ]
  * Use std::quick_exit. (LP: #1381041)

  [ Marcus Tomlinson ]
  * Fix GMainLoopDispatch dispatching ordering when. called inside
GMainLoop already Fix GMainLoopDispatch locking. Force all signals
from external (dbus-cpp) threads through. GMainLoopDispatch (LP:
#1374419)

  [ Antti Kaijanmäki ]
  * Increase the default timeouts to match industry standards. (LP:
#1381041)
  * Fix GMainLoopDispatch dispatching ordering when. called inside
GMainLoop already Fix GMainLoopDispatch locking. Force all signals
from external (dbus-cpp) threads through. GMainLoopDispatch (LP:
#1374419)
 -- Ubuntu daily releaseFri, 31 Oct 2014 
14:16:08 +

** Changed in: indicator-network (Ubuntu RTM)
   Status: In Progress => Fix Released

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

Title:
  [TOPBLOCKER] Network indicator is sometimes blank

Status in “indicator-network” package in Ubuntu:
  Fix Released
Status in “indicator-network” source package in Utopic:
  New
Status in “indicator-network” source package in Vivid:
  Fix Released
Status in “indicator-network” package in Ubuntu RTM:
  Fix Released

Bug description:
  This is on krillin r103, but it has been happening for a while.

  See attached photo. I am not certain what triggers it. but I think it
  may happen when wifi APs become in and out of range while walking
  around town (as if the list does not refresh reliably).

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

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

[Touch-packages] [Bug 1361642] Re: DBus.Properties.Get/Set having a hardcoded default timeout of 1000ms

This bug was fixed in the package dbus-cpp - 4.1.0+14.10.20141031~rtm-
0ubuntu1

---
dbus-cpp (4.1.0+14.10.20141031~rtm-0ubuntu1) 14.09; urgency=low

  [ thomas-voss ]
  * Relax timeout on org.freedesktop.Properties::{GetAll, Get, Set}.
with timeout set to 30 sec (LP: #1361642)

  [ Kevin Gunn ]
  * Relax timeout on org.freedesktop.Properties::{GetAll, Get, Set}.
with timeout set to 30 sec (LP: #1361642)
 -- Ubuntu daily releaseFri, 31 Oct 2014 
07:51:25 +

** Changed in: dbus-cpp (Ubuntu RTM)
   Status: New => Fix Released

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

Title:
  DBus.Properties.Get/Set having a hardcoded default timeout of 1000ms

Status in DBus C++:
  Confirmed
Status in “dbus-cpp” package in Ubuntu:
  New
Status in “dbus-cpp” package in Ubuntu RTM:
  Fix Released

Bug description:
  This causes issues such as found here:

  https://code.launchpad.net/~jpakkane/indicator-
  network/grace/+merge/232194

To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus-cpp/+bug/1361642/+subscriptions

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

[Touch-packages] [Bug 1374419] Re: [TOPBLOCKER] Threading issue with the MenuModel Updates

This bug was fixed in the package indicator-network -
0.5.1+14.10.20141031.3~rtm-0ubuntu1

---
indicator-network (0.5.1+14.10.20141031.3~rtm-0ubuntu1) 14.09; urgency=low

  [ Jussi Pakkanen ]
  * Use std::quick_exit. (LP: #1381041)

  [ Marcus Tomlinson ]
  * Fix GMainLoopDispatch dispatching ordering when. called inside
GMainLoop already Fix GMainLoopDispatch locking. Force all signals
from external (dbus-cpp) threads through. GMainLoopDispatch (LP:
#1374419)

  [ Antti Kaijanmäki ]
  * Increase the default timeouts to match industry standards. (LP:
#1381041)
  * Fix GMainLoopDispatch dispatching ordering when. called inside
GMainLoop already Fix GMainLoopDispatch locking. Force all signals
from external (dbus-cpp) threads through. GMainLoopDispatch (LP:
#1374419)
 -- Ubuntu daily releaseFri, 31 Oct 2014 
14:16:08 +

** Changed in: indicator-network (Ubuntu RTM)
   Status: In Progress => Fix Released

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

Title:
  [TOPBLOCKER] Threading issue with the MenuModel Updates

Status in “indicator-network” package in Ubuntu:
  Fix Released
Status in “indicator-network” source package in Utopic:
  New
Status in “indicator-network” source package in Vivid:
  Fix Released
Status in “indicator-network” package in Ubuntu RTM:
  Fix Released

Bug description:
  This and other "corruptions" in the i-network menus is caused by a
  race condition in the i-network-service GMainLoop synchronization.

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

  See attached screenshot.

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

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

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

[Touch-packages] [Bug 1388349] [NEW] Crashes X when viewing certain websites

You have been subscribed to a public bug:

Just visiting some URLs will crash X and bring down the whole system
without warning. Reproducible example: visit http://ello.co/jondcook in
Chromium and the GPU will crash.

Ubuntu 12.04.5 LTS

[75195.004056] [drm] stuck on render ring
[75195.004067] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[75195.004071] [drm] GPU hangs can indicate a bug anywhere in the entire gfx 
stack, including userspace.
[75195.004075] [drm] Please file a _new_ bug report on bugs.freedesktop.org 
against DRI -> DRM/Intel
[75195.004078] [drm] drm/i915 developers can then reassign to the right 
component if it's not a kernel issue.
[75195.004082] [drm] The gpu crash dump is required to analyze gpu hangs, so 
please always attach it.
[75195.005398] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo 
(0x2088000 ctx 0) at 0x2089954
[75195.512106] [drm:i915_reset] *ERROR* Failed to reset chip.
[75200.348321] Watchdog[5421]: segfault at 0 ip aff4a4c8 sp ad0c4cf0 error 6 in 
libcontent.so[af72f000+11ee000]
[75205.036042] [drm:i915_gem_wait_for_error] *ERROR* Timed out waiting for the 
gpu reset to complete
[75205.092053] [drm] GMBUS [i915 gmbus vga] timed out, falling back to bit 
banging on pin 2
[75205.119530] [ cut here ]
[75205.119593] WARNING: CPU: 0 PID: 1931 at 
/build/buildd/linux-lts-trusty-3.13.0/drivers/gpu/drm/i915/intel_display.c:922 
assert_pll+0x7a/0x80 [i915]()
[75205.119597] PLL state assertion failure (expected on, current off)
[75205.119600] Modules linked in: usb_storage nls_iso8859_1 serpent_sse2_i586 
ablk_helper cryptd glue_helper lrw serpent_generic twofish_generic twofish_i586 
twofish_common xts gf128mul hidp hid nvram pci_stub vboxpci(OX) vboxnetadp(OX) 
vboxnetflt(OX) vboxdrv(OX) ctr ccm vsock zram(C) bnep rfcomm parport_pc ppdev 
binfmt_misc dm_crypt joydev xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 
btusb bluetooth ipt_REJECT xt_LOG xt_multiport xt_limit xt_tcpudp xt_addrtype 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_state ip6table_filter ip6_tables 
nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat 
nf_conntrack_ftp nf_conntrack iptable_filter snd_hda_codec_si3054 
snd_hda_codec_realtek ip_tables x_tables snd_hda_intel hp_wmi snd_hda_codec 
sparse_keymap snd_hwdep arc4 snd_pcm r852 snd_seq_midi snd_rawmidi 
snd_seq_midi_event iwl3945 sm_common nand iwlegacy mtd snd_seq nand_ids 
nand_bch snd_timer bch r592 mac80211 nand_ecc psmouse memstick lpc_ich 
serio_raw snd_seq_device cfg80211 snd soundc
 ore snd_page_alloc mac_hid coretemp lp parport i915 firewire_ohci 
drm_kms_helper firewire_core drm ahci crc_itu_t libahci i2c_algo_bit r8169 
sdhci_pci sdhci mii video wmi
[75205.119720] CPU: 0 PID: 1931 Comm: upowerd Tainted: G C OX 
3.13.0-39-generic #66~precise1-Ubuntu
[75205.119724] Hardware name: Hewlett-Packard Presario V6500 Notebook PC
/30CC, BIOS F.5A  03/22/2010
[75205.119727]    ee449c50 c1683110 f89adb0c ee449c80 c1059c54 
f89afb04
[75205.119737]  ee449cac 078b f89adb0c 039a f895e0fa f895e0fa 0001 
0001
[75205.119746]  0001 ee449c98 c1059d13 0009 ee449c90 f89afb04 ee449cac 
ee449cbc
[75205.119755] Call Trace:
[75205.119766]  [] dump_stack+0x41/0x52
[75205.119776]  [] warn_slowpath_common+0x84/0xa0
[75205.119813]  [] ? assert_pll+0x7a/0x80 [i915]
[75205.119847]  [] ? assert_pll+0x7a/0x80 [i915]
[75205.119852]  [] warn_slowpath_fmt+0x33/0x40
[75205.119887]  [] assert_pll+0x7a/0x80 [i915]
[75205.119928]  [] intel_crtc_load_lut+0x194/0x1a0 [i915]
[75205.119961]  [] ? i9xx_enable_pll+0x11c/0x190 [i915]
[75205.119994]  [] i9xx_crtc_enable+0xa8/0x150 [i915]
[75205.120059]  [] __intel_set_mode+0x244/0x2f0 [i915]
[75205.120106]  [] ? 
intel_framebuffer_create_for_mode.constprop.57+0xa3/0xb0 [i915]
[75205.120150]  [] intel_set_mode+0x27/0x40 [i915]
[75205.120189]  [] intel_get_load_detect_pipe+0x21d/0x300 [i915]
[75205.120237]  [] intel_tv_detect+0x125/0x230 [i915]
[75205.120252]  [] ? lockref_get_not_dead+0x11/0x40
[75205.120280]  [] status_show+0x3d/0x80 [drm]
[75205.120286]  [] ? __kmalloc+0xa4/0x210
[75205.120310]  [] ? dpms_show+0x60/0x60 [drm]
[75205.120317]  [] dev_attr_show+0x1f/0x50
[75205.120324]  [] sysfs_seq_show+0x103/0x1e0
[75205.120329]  [] ? root_device_unregister+0x30/0x30
[75205.120335]  [] seq_read+0xde/0x360
[75205.120340]  [] vfs_read+0x84/0x160
[75205.120345]  [] ? seq_lseek+0x160/0x160
[75205.120350]  [] SyS_read+0x57/0xa0
[75205.120355]  [] sysenter_do_call+0x12/0x12
[75205.120361]  [] ? ext4_check_descriptors+0x104/0x3b0
[75205.120364] ---[ end trace ed9b043f70466751 ]---

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: chromium-browser 37.0.2062.120-0ubuntu0.12.04.1~pkg917
ProcVersionSignature: Ubuntu 3.13.0-39.66~precise1-generic 3.13.11.8
Uname: Linux 3.13.0-39-generic i686
ApportVersion: 2.0.1-0ubuntu17.8
Architecture: i386
Date: Sat Nov  1 23:36:56 2014
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release

[Touch-packages] [Bug 1157643] Re: procps fail to start

2014-11-03 Thread Mathew Hodson

** Tags removed: failed procps start verification-needed

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

Title:
  procps fail to start

Status in “procps” package in Ubuntu:
  Fix Released
Status in “procps” source package in Precise:
  Fix Released
Status in “procps” source package in Quantal:
  Fix Released
Status in “procps” source package in Raring:
  Fix Released
Status in “procps” source package in Saucy:
  Fix Released
Status in “procps” source package in Trusty:
  Fix Released

Bug description:
  [SRU justification]
  In a container, the procps package fails to upgrade because sysctl will fail 
when it can't write to certain keys.  Since the procps has just been SRUed, 
this means anyone running Ubuntu in a container (12.04 or later) will have 
upgrade failures because of the procps upstart job failing to start.

  [Test case]
  1. Set up precise in an lxc container.
  2. Apply updates from the -updates pocket.
  3. Observe that the procps package fails to install.
  4. Enable -proposed.
  5. Install the procps package from -proposed.
  6. Observe that the package upgrades successfully.

  [Regression potential]
  This patch changes the behavior of the sysctl program and causes permission 
errors to be non-fatal.  Anything relying on the current behavior (e.g., when 
sysctl is run by a non-root user) will regress as a result of this change, but 
it's not obvious why anything would rely on this since sysctl is not meant to 
be invoked by non-root users.  
  root@x:~# lsb_release -rd
  Description:Ubuntu 12.04.2 LTS
  Release:12.04

  root@xxx:~# apt-cache policy procps
  procps:
    Installed: 1:3.2.8-11ubuntu6
    Candidate: 1:3.2.8-11ubuntu6
    Version table:
   *** 1:3.2.8-11ubuntu6 0
  500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
  100 /var/lib/dpkg/status

  I have a VPS that i upgraded from Ubuntu 10.10 to 11.10 and then to 12.04.2 
LTS.
  But something is wrong and now i can't upgrade procps. I get the following 
output,

  root@xx:~# apt-get  upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue [Y/n]?
  Setting up procps (1:3.2.8-11ubuntu6) ...
  start: Job failed to start
  invoke-rc.d: initscript procps, action "start" failed.
  dpkg: error processing procps (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   procps
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  the /var/log/upstart/procps.log says,

  kernel.printk = 4 4 1 7
  net.ipv6.conf.all.use_tempaddr = 2
  net.ipv6.conf.default.use_tempaddr = 2
  error: permission denied on key 'kernel.kptr_restrict'
  net.ipv4.conf.default.rp_filter = 1
  net.ipv4.conf.all.rp_filter = 1
  net.ipv4.tcp_syncookies = 1
  vm.mmap_min_addr = 65536

  And the output when i try to start procps is just the following,

  root@x:~# service procps start
  start: Job failed to start

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

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

[Touch-packages] [Bug 1373985] Re: foreground app doesn't get activated after we leave the lock screen

2014-11-03 Thread Ricardo Salveti

I could not reproduce this bug with the attempts I tried (both vivid/7
and rtm/140).

In any case, could someone test the packages from
http://people.canonical.com/~rsalveti/1373985/ to see if it helps fixing
this bug? If so, I can upload it to vivid and create a silo for RTM
(until it gets approved).

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

Title:
  foreground app doesn't get activated after we leave the lock screen

Status in “maliit-framework” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce the issue:
  1 - have unity8-dash on the foreground
  2 - lock the phone (reboot or have the display off and then turn it back on)
  3 - type you password [you're brought to unity8-dash]
  4 - tap on the looking glass icon in the top right [search bar text entry 
shows up with "Search apps" written on it]

  Expected outcome:
  A blinking cursor caret is displayed on the app search text entry and the VKB 
comes up.

  Actual outcome:
  Nothing happens.

  Causing unity-8 dash to be refocused, such as bringing the indicators
  panel down and then back up solves it.

  Comments:
  Happens with any application that happens to be in the foreground, 
unity8-dash being just one test case that is easy to reproduce.

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

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

[Touch-packages] [Bug 1388976] [NEW] [Time & Date] After switching from Manual time setting back to Automatic, the clock does not update until rebooted

2014-11-03 Thread Brendan Donegan

Public bug reported:

Steps to reproduce:

1. Open System Settings
2. Open the Time & Date panel
3. Set 'Set the time and date:' to 'Manually'
4. Tap on the date and time label and set the date and time to something in the 
future (a few months ahead)
5. Go back and wait for the time indicator to update
6. Set 'Set the time and date:' to Automatically
7. Go back and wait for the time indicator to update again

Expected result:

The indicator reverts back to the previous time

Actual result:

The indicator never updates the time until the device is rebooted

ProblemType: Bug
DistroRelease: Ubuntu RTM 14.09
Package: indicator-datetime 13.10.0+14.10.20141009-0ubuntu1
Uname: Linux 3.4.67 armv7l
ApportVersion: 2.14.7-0ubuntu8
Architecture: armhf
Date: Fri Dec  5 21:21:42 2014
InstallationDate: Installed on 2014-10-31 (35 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141031-175022)
SourcePackage: indicator-datetime
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug armhf utopic

** Summary changed:

- After switching from Manual time setting back to Automatic, the clock does 
not update until rebooted
+ [Time & Date] After switching from Manual time setting back to Automatic, the 
clock does not update until rebooted

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

Title:
  [Time & Date] After switching from Manual time setting back to
  Automatic, the clock does not update until rebooted

Status in “indicator-datetime” package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Open System Settings
  2. Open the Time & Date panel
  3. Set 'Set the time and date:' to 'Manually'
  4. Tap on the date and time label and set the date and time to something in 
the future (a few months ahead)
  5. Go back and wait for the time indicator to update
  6. Set 'Set the time and date:' to Automatically
  7. Go back and wait for the time indicator to update again

  Expected result:

  The indicator reverts back to the previous time

  Actual result:

  The indicator never updates the time until the device is rebooted

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: indicator-datetime 13.10.0+14.10.20141009-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Fri Dec  5 21:21:42 2014
  InstallationDate: Installed on 2014-10-31 (35 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141031-175022)
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1317727] Re: documentation corrections, apport hook fixups

2014-11-03 Thread Mathew Hodson

** Tags removed: verification-needed

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

Title:
  documentation corrections, apport hook fixups

Status in “upstart” package in Ubuntu:
  Fix Released
Status in “upstart” source package in Trusty:
  Fix Released
Status in “upstart” source package in Utopic:
  Fix Released

Bug description:
  [impact]
   * miscellaneous changes in upstart SRU to trusty:
 * debian/manpages/upstart-events.7: Correction for 'rotate-logs'.
 * debian/upstart.cron.daily: Specify full path to initctl.
 * init/man/init.8: Add missing information on '--chroot-sessions'.
 * debian/upstart.apport: Sort system and session jobs.

  manpages - update to be factually correct with behavior seen in 
trusty-release upstart.
  sort upstart jobs in the apport hook, for easy of comparison/diffing during 
report aggregation and analysis.
  use the system initctl to emit rotate-logs event.

  [testcases]
* file ubuntu-bug against upstart, check that running jobs attachment has 
all jobs sorted
* inspect manpages to render correctly & describe correct behaviour
* check that rotate-logs event is emitted daily

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

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

[Touch-packages] [Bug 1387328] Re: apport-gtk: clicking on the details tree jumps the scroll position to top

** Branch linked: lp:apport

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

Title:
  apport-gtk: clicking on the details tree jumps the scroll position to
  top

Status in “apport” package in Ubuntu:
  Fix Committed

Bug description:
  1. Wait for a crash or run apport-bug /var/crash/something.crash
  2. Click Show Details
  3. Scroll down the tree view until you see something interesting like 
Stacktrace
  4. Click 'Stacktrace' to expand it

  What happens:
  - tree view gets focus, 1st (i.e. topmost) item in it gets selected and 
scrolled into view

  What I expect:
  - tree view gets focus, the 'Stacktrace'  item gets selected and view is not 
scrolled away from what I was interested in.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: apport-gtk 2.14.7-0ubuntu8
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Oct 29 21:10:33 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-07-25 (826 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to utopic on 2014-10-24 (5 days ago)

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

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

[Touch-packages] [Bug 1383297] Re: Edge tutorial's redesign: new gestures

2014-11-03 Thread Michael Terry

** Tags added: ota-1

** Summary changed:

- Edge tutorial's redesign: new gestures
+ [oobe] + [edge tutorial] Edge tutorial's redesign: new gestures

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

Title:
  [oobe] + [edge tutorial] Edge tutorial's redesign: new gestures

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

Bug description:
  The first-boot edge tutorial should cover a wider range of gestures
  than it currently does.  Things like right edge swipe, bottom edge
  swipe, and long vs short swipes.

  Visual designs (not entirely finished yet):
  https://drive.google.com/a/canonical.com/folderview?id=0B8I8ZVKH-
  8SsM1QyMmhWbkpRLTg

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

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

[Touch-packages] [Bug 1387328] Re: apport-gtk: clicking on the details tree jumps the scroll position to top

2014-11-03 Thread Martin Pitt

Thank you! Merged into trunk r2872.

** Changed in: apport (Ubuntu)
   Status: New => Fix Committed

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

Title:
  apport-gtk: clicking on the details tree jumps the scroll position to
  top

Status in “apport” package in Ubuntu:
  Fix Committed

Bug description:
  1. Wait for a crash or run apport-bug /var/crash/something.crash
  2. Click Show Details
  3. Scroll down the tree view until you see something interesting like 
Stacktrace
  4. Click 'Stacktrace' to expand it

  What happens:
  - tree view gets focus, 1st (i.e. topmost) item in it gets selected and 
scrolled into view

  What I expect:
  - tree view gets focus, the 'Stacktrace'  item gets selected and view is not 
scrolled away from what I was interested in.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: apport-gtk 2.14.7-0ubuntu8
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Oct 29 21:10:33 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-07-25 (826 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to utopic on 2014-10-24 (5 days ago)

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

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

[Touch-packages] [Bug 1383773] Re: [design] Edges Demo doesn't include a lot of steps and is missing new design

2014-11-03 Thread Michael Terry

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

Whoops, I've been tracking this in two other bugs:

new gestures: bug 1383297
design: bug 1386268

I will dup this and port important details over.

** This bug has been marked a duplicate of bug 1383297
   Edge tutorial's redesign: new gestures

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

Title:
  [design] Edges Demo doesn't include a lot of steps and is missing new
  design

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

Bug description:
  INFO:
  Edges Demo needs to include mid screen swipe for scope switch, swipe up in 
app for new page and edge swipe for app switch.

  Added by design:
  We conducted user research on the OOBE and edge education experience and 
while people didn't have problems to walk through the OOBE set up the edge 
education was considered by users as confusing. One of the main issue was that 
the current one is not explaining what exactly is triggered by carrying out the 
edge swipes.

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

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

[Touch-packages] [Bug 1386268] Re: [oobe] + [edge tutorial] Edge tutorial's redesign: new look

2014-11-03 Thread Michael Terry

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

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

Title:
  [oobe] + [edge tutorial] Edge tutorial's redesign: new look

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

Bug description:
  This is a breakout from bug 1383297 (which now just covers new
  gestures).

  This bug is just about implementing the new look and feel as well as
  dropping the first greeter screen, which is no longer in the tutorial
  designs.

  I'm making a separate bug because they will likely be given different
  priorities and implemented at different times.

  You can see the new visuals in this folder:
  https://drive.google.com/a/canonical.com/folderview?id=0B8I8ZVKH-
  8SsM1QyMmhWbkpRLTg

  And the flow in general here:
  
https://docs.google.com/a/canonical.com/document/d/1VajNkWbBH61iVixXJAmOvNGiG__GWQTMXGNOZijXWJw

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

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

[Touch-packages] [Bug 1248948] Re: lightdm gets confused after multiple login/logouts

2014-11-03 Thread Mathew Hodson

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

** This bug has been marked a duplicate of bug 1256150
   Xorg guest session fails to start if the user has logged out and logged in 
again

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

Title:
  lightdm gets confused after multiple login/logouts

Status in “lightdm” package in Ubuntu:
  Confirmed

Bug description:
  Got this on xubuntu 13.10:
  When I logout and login again and start gdmflexiserver (or any other dbus 
call to displaymanager), the screen turns black with the mouse cursor still 
visible. The session is still running since I can terminate it by executing 
'blindly' the normal logout process.

  A fishy side aspect: When i switch to ttyX via ctrl+alt+fX and login, the 
username AND password is also written to .bash_history of the user with the 
crippled X-session(if he left a shell open with focus). So you might want 
consider this as a security issue.
  --- 
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  DistroRelease: Ubuntu 13.10
  InstallationDate: Installed on 2013-10-27 (11 days ago)
  InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 
(20131016)
  LightdmConfig:
   [SeatDefaults]
   greeter-session=lightdm-gtk-greeter
   user-session=xubuntu
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:1002): WARNING **: Failed to open sessions 
directory: Error opening directory '/usr/share/lightdm/sessions': No such file 
or directory
   
   ** (lightdm-gtk-greeter:1002): WARNING **: Failed to open sessions 
directory: Error opening directory '/usr/share/lightdm/remote-sessions': No 
such file or directory
   
   ** (lightdm-gtk-greeter:1002): WARNING **: Failed to load user image: Failed 
to open file '/home/kiran/.face': No such file or directory
  LightdmGreeterLogOld:
   ** (lightdm-gtk-greeter:2580): WARNING **: Failed to open sessions 
directory: Error opening directory '/usr/share/lightdm/sessions': No such file 
or directory
   
   ** (lightdm-gtk-greeter:2580): WARNING **: Failed to open sessions 
directory: Error opening directory '/usr/share/lightdm/remote-sessions': No 
such file or directory
   
   ** (lightdm-gtk-greeter:2580): WARNING **: Failed to load user image: Failed 
to open file '/home/kiran/.face': No such file or directory
  MarkForUpload: True
  Package: lightdm 1.8.4-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Tags: saucy third-party-packages
  Uname: Linux 3.11.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 57797] Re: include aoTuV patch

2014-11-03 Thread Oibaf

Vorbis merged an old version of aotuv, latest aotuv is not in vorbis
however.

Also, according to listening tests, opus is known to be better than vorbis in 
every tested scenario, see:
http://jmspeex.livejournal.com/13547.html

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

Title:
  include aoTuV patch

Status in Medibuntu:
  Invalid
Status in Ogg Vorbis:
  Confirmed
Status in “libvorbis” package in Ubuntu:
  Confirmed
Status in “libvorbis” package in Debian:
  Fix Released

Bug description:
  Would be nice to include aoTuV [1] Release 1 patch to libvorbis. aoTuV is an 
improved libvorbis encoder, that, while keeping ABI compatibility, gives many 
improvement:
  * better quality at all bitrates versus libvorbis-1.1.2 [2], giving aoTuV 
better quality than other codec (AAC, MP3, MPC, WMA, ...) [3];
  * support of quality down to -2 (32kb/s at 44kHz stereo), versus -1 (45kb/s 
at 44kHz stereo) of libvorbis-1.1.x;
  * encoding speed 10% better thanks to the included Vorbis-OptSort patch 
(improve ordering loop);

  aoTuV Release 1 have just been releases. aoTuV Release 1 is the same
  as of beta4.51 (released on 2005-11), renamed after a lot of testing
  of the audio community (especially on hydrogenaudio forum [4]) and
  this is the reccomended vorbis encoder [5].

  [1] aoTuV site: http://www.geocities.jp/aoyoume/aotuv/
  [2] comparison of aoTuV beta 4 vs libvorbis-1.1.x: 
http://wiki.xiph.org/index.php/VorbisEncoders
  [3] Wikipedia test of vorbis vs other codecs: 
http://en.wikipedia.org/wiki/Vorbis#Codec_comparisons
  [4] hydrogenaudio forum: http://www.hydrogenaudio.org
  [5] Recommended Ogg Vorbis: 
http://wiki.hydrogenaudio.org/index.php?title=Recommended_Ogg_Vorbis

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

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

[Touch-packages] [Bug 1388876] Re: Pinch to zoom not supported when taking video

2014-11-03 Thread Jim Hodapp

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

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

Title:
  Pinch to zoom not supported when taking video

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

Bug description:
  Steps to reproduce:

  1. Open the camera application
  2. Press the Video button to switch to video mode
  3. Place two fingers on the screen and move them apart to attempt to zoom

  Expected result:

  The picture zooms in and a slider appears indicating the zoom level

  Actual result:

  The slider appears but the picture does not zoom in and there is no
  marker on the slider to indicate the zoom level

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

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

[Touch-packages] [Bug 57797] Re: include aoTuV patch

2014-11-03 Thread Thucydides411

hdante, just a few comments/questions:

> 2) Xiph vorbis encoder merged AoTuV tunings

What version of the AoTuV tunings have been merged into the Xiph
encoder? The version of oggenc that ships with Ubuntu can't go down to
32 kb/s, which is a sign that it's using the old, unpatched reference
encoder, rather than the AoTuV tunings.

> 3) the best lossy open source audio codec is opus:
http://xiph.org/press/2012/rfc-6716/

Opus and Vorbis have different uses. Opus is superior in certain
applications, like streaming over a variable-bitrate channel in the
presence of substantial packet loss, and VOIP with low latency. But
Vorbis with AoTuV tunings has far superior sound quality for music,
especially at low bitrates, than the reference Opus encoder, and has
better support on a range of devices. The fact that Opus is better for
some applications shouldn't prevent Ubuntu from shipping with the best
free/open source encoder available.

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

Title:
  include aoTuV patch

Status in Medibuntu:
  Invalid
Status in Ogg Vorbis:
  Confirmed
Status in “libvorbis” package in Ubuntu:
  Confirmed
Status in “libvorbis” package in Debian:
  Fix Released

Bug description:
  Would be nice to include aoTuV [1] Release 1 patch to libvorbis. aoTuV is an 
improved libvorbis encoder, that, while keeping ABI compatibility, gives many 
improvement:
  * better quality at all bitrates versus libvorbis-1.1.2 [2], giving aoTuV 
better quality than other codec (AAC, MP3, MPC, WMA, ...) [3];
  * support of quality down to -2 (32kb/s at 44kHz stereo), versus -1 (45kb/s 
at 44kHz stereo) of libvorbis-1.1.x;
  * encoding speed 10% better thanks to the included Vorbis-OptSort patch 
(improve ordering loop);

  aoTuV Release 1 have just been releases. aoTuV Release 1 is the same
  as of beta4.51 (released on 2005-11), renamed after a lot of testing
  of the audio community (especially on hydrogenaudio forum [4]) and
  this is the reccomended vorbis encoder [5].

  [1] aoTuV site: http://www.geocities.jp/aoyoume/aotuv/
  [2] comparison of aoTuV beta 4 vs libvorbis-1.1.x: 
http://wiki.xiph.org/index.php/VorbisEncoders
  [3] Wikipedia test of vorbis vs other codecs: 
http://en.wikipedia.org/wiki/Vorbis#Codec_comparisons
  [4] hydrogenaudio forum: http://www.hydrogenaudio.org
  [5] Recommended Ogg Vorbis: 
http://wiki.hydrogenaudio.org/index.php?title=Recommended_Ogg_Vorbis

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

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

[Touch-packages] [Bug 1289465] Re: Brightness icons are suboptimal

This bug was fixed in the package ubuntu-system-settings -
0.3+15.04.20141103-0ubuntu1

---
ubuntu-system-settings (0.3+15.04.20141103-0ubuntu1) vivid; urgency=low

  [ Ken VanDine ]
  * Use the SliderMenu component instead of the Slider component, it
matches the design and doesn't flicker while changing the
brightness. (LP: #1289465)
  * Need to create UpClient regardless of upower version

  [ Sebastien Bacher ]
  * [storage] build the correct ini name rather than guessing it (LP:
#1387834)
  * [battery] don't use a colored icon (LP: #1351383)

  [ Michael Terry ]
  * Redesign location page according to latest design visuals / text.
Allows GPS-only, GPS+HERE, or nothing at all. (LP: #1384763)

  [ Ubuntu daily release ]
  * New rebuild forced
 -- Ubuntu daily releaseMon, 03 Nov 2014 
17:30:03 +

** Changed in: ubuntu-system-settings (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Brightness icons are suboptimal

Status in “indicator-power” package in Ubuntu:
  New
Status in “ubuntu-system-settings” package in Ubuntu:
  Fix Released
Status in “ubuntu-themes” package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu Trusty r188, Ubuntu 14.10 r2, Ubuntu 14.10 r152

  1. Go to System Settings > "Battery".
  2. Look at the icons at the ends of the "Display brightness" slider.

  What you see:
  * The minimum-brightness icon is a light bulb with no rays.
  * The maximum-brightness icon is a light bulb with rays and a lightning bolt 
inside it.

  What you should see:
  * The minimum-brightness bulb should have rays, because it is not zero 
brightness.
  * The maximum-brightness icon does not have a lightning bolt, because that is 
strongly associated with battery charging.

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

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

[Touch-packages] [Bug 1387409] Re: make adding new frameworks easier

** Changed in: click-apparmor (Ubuntu)
   Status: Triaged => In Progress

** Changed in: click-apparmor (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 click-apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1387409

Title:
  make adding new frameworks easier

Status in “click-apparmor” package in Ubuntu:
  In Progress

Bug description:
  ..

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

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

[Touch-packages] [Bug 1384812] Re: should be able to specify multiple paths with aa-clickhook --include

** Changed in: click-apparmor (Ubuntu)
   Status: Triaged => In Progress

** Changed in: click-apparmor (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 click-apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1384812

Title:
  should be able to specify multiple paths with aa-clickhook --include

Status in “click-apparmor” package in Ubuntu:
  In Progress

Bug description:
  Currently aa-clickhook only allows specifying one rules file at a
  time. autopkgtests need one set of rules and autopilot tests need
  another, so it would be useful for aa-clickhook to allow for this.

  Workaround: in your test harness do something like:
  cat > /tmp/... < >> /tmp/...

  aa-clickhook -f --include=/tmp/...

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

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

[Touch-packages] [Bug 1238007] Re: aa-clickhook -f does not properly consider changes to abstractions and #include directories

** Changed in: click-apparmor (Ubuntu)
   Status: Triaged => In Progress

** Changed in: click-apparmor (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 click-apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1238007

Title:
  aa-clickhook -f does not properly consider changes to abstractions and
  #include directories

Status in “click-apparmor” package in Ubuntu:
  In Progress

Bug description:
  click-apparmor tries very hard to only use apparmor_parser when
  needed, but it is too aggressive currently. Right now it will only hit
  the parser if the output of easyprof changes. However, if an
  abstraction changes or something in the new
  /usr/share/apparmor/hardware directories change, the policy won't be
  updated. This needs to be fixed.

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

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

[Touch-packages] [Bug 1271577] Re: handle duplicate policy groups better

** Changed in: click-apparmor (Ubuntu)
   Status: Triaged => In Progress

** Changed in: click-apparmor (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 click-apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1271577

Title:
  handle duplicate policy groups better

Status in “click-apparmor” package in Ubuntu:
  In Progress

Bug description:
  This is either a bug in click-apparmor or aa-easyprof, but specifying
  the same policy group multiple times results in the tools adding the
  policy for the policy group multiple times. May reassign to apparmor
  later.

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

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

[Touch-packages] [Bug 1377698] Re: /etc/default/rcS: UTC=no is being ignored

2014-11-03 Thread Martin Pitt

> Not need applying a similar fix with Ubuntu Trusty?

No, this was introduced in utopic.

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

Title:
  /etc/default/rcS: UTC=no is being ignored

Status in “util-linux” package in Ubuntu:
  Fix Released

Bug description:
  This causes the greeter time to display utc & sets system time to utc
  Affects users who are in a different timezone
  Also affects users who dual boot with windows, their time will be off by 
amount different from utc to their time zone

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: initscripts 2.88dsf-41ubuntu18
  ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3
  Uname: Linux 3.16.0-20-generic x86_64
  ApportVersion: 2.14.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct  5 14:16:48 2014
  InstallationDate: Installed on 2014-10-05 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
  SourcePackage: sysvinit
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.default.rcS: 2014-10-05T10:58:21.042693

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

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

[Touch-packages] [Bug 1358505] Re: Need Ubuntu to preinstall ppc64-diag and other basic packages

2014-11-03 Thread Adam Conrad

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

** Also affects: debian-installer (Ubuntu Utopic)
   Importance: Undecided
   Status: New

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

** Also affects: debian-installer (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

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

Title:
  Need Ubuntu to preinstall ppc64-diag and other basic packages

Status in “debian-installer” package in Ubuntu:
  Confirmed
Status in “ubuntu-meta” package in Ubuntu:
  New
Status in “debian-installer” source package in Trusty:
  New
Status in “ubuntu-meta” source package in Trusty:
  New
Status in “debian-installer” source package in Utopic:
  New
Status in “ubuntu-meta” source package in Utopic:
  New

Bug description:
  -- Problem Description --

  We need Ubuntu support for  pre-install ppc64-diag and other basic packages.
  Below packages contains Power platform specific tools which are required by 
default.. Hence please include these packages in default installation list.

  ppc64-diag
  powerpc-ibm-utils

  We need this for 14.04 and 14.10 tree..

  -Vasant

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

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

[Touch-packages] [Bug 1388156] Re: phone locks after switching away and back to active call

2014-11-03 Thread Gustavo Pichorim Boiko

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

** Branch linked: lp:~boiko/dialer-app/rtm-fullscreen_emergency_mode

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

Title:
  phone locks after switching away and back to active call

Status in “dialer-app” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu RTM:
  In Progress

Bug description:
  build 139 on Krillin

  Steps to reproduce:
  - unlock phone
  - receive a call
  - answer the call
  - swipe away the dialer to the dash
  - press the Active Call bar at the top to go back to call

  Expected results:
  - dialer is displayed, phone remains unlocked and indicator panel is visible

  Actual results:
  - dialer is displayed, but the indicator panel is not showing
  - no way to get back to shell or other apps
  - have to press back button in dialer which brings you to the greeter where 
you have to unlock the phone to continue

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

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

[Touch-packages] [Bug 1388240] Re: on mako utopic 'ssh phablet@localhost -p 8888' fails, on mako trusty works pretty well indeed

2014-11-03 Thread Raimundo C M Leite

does ssh  work with mako on utopic 14.10?.

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

** Converted to question:
   https://answers.launchpad.net/ubuntu/+source/openssh/+question/256726

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

Title:
  on mako utopic 'ssh phablet@localhost -p ' fails, on mako trusty
  works pretty well indeed

Status in “openssh” package in Ubuntu:
  Invalid

Bug description:
  "adb shell" works pretty well indeed, without 'su - phablet'.
  on trusty mako 'ssh  -Y phablet@localhost -p ' uset to work nice :-)

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

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

[Touch-packages] [Bug 1388944] [NEW] preseed.cfg is ignored with 14.10 server

2014-11-03 Thread Kurt Hutchison

Public bug reported:

We support unattended installs of Ubuntu.

We use the preseed.cfg mechanism documented.

It works fine with the desktop, but the preseed.cfg is ignored with the
server iso.

We create a second bootable CD with the boot config and preseed file which then 
uses
the origjnal iso image to install.

I can provide the iso  on request.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: debconf 1.5.53ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
Uname: Linux 3.16.0-23-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
Date: Mon Nov  3 02:41:23 2014
InstallationDate: Installed on 2014-11-03 (0 days ago)
InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 
(20141022.2)
PackageArchitecture: all
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: debconf
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: debconf (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 debconf in Ubuntu.
https://bugs.launchpad.net/bugs/1388944

Title:
  preseed.cfg is ignored with 14.10 server

Status in “debconf” package in Ubuntu:
  New

Bug description:
  We support unattended installs of Ubuntu.

  We use the preseed.cfg mechanism documented.

  It works fine with the desktop, but the preseed.cfg is ignored with
  the server iso.

  We create a second bootable CD with the boot config and preseed file which 
then uses
  the origjnal iso image to install.

  I can provide the iso  on request.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: debconf 1.5.53ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  Date: Mon Nov  3 02:41:23 2014
  InstallationDate: Installed on 2014-11-03 (0 days ago)
  InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 
(20141022.2)
  PackageArchitecture: all
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: debconf
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1289465] Re: Brightness icons are suboptimal