[Touch-packages] [Bug 1330959] Re: Art in cards with backgrounds are Ubuntu-shaped

[Zsombor Egri]

Kevin, Pat, the UITK fix [1] wasn't planned for RTM (UITK v1.1) but for
Vivid (UITK 1.2) as  it introduces a brand new component. The fix is
based on a major UbuntuShape refactoring [2], and needs smoke tested.

However, we can redirect both MPs to land in UITK 1.1, RTM in case this
is so urgent. It's a bit risky, but if the house is burning, we can live
with that.

[1] 
https://code.launchpad.net/~loic.molinari/ubuntu-ui-toolkit/ubuntu-ui-toolkit-shape-overlay/+merge/243324
[2] 
https://code.launchpad.net/~loic.molinari/ubuntu-ui-toolkit/ubuntu-ui-toolkit-shape-rewrite/+merge/242791

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

Title:
  Art in cards with backgrounds are Ubuntu-shaped

Status in the base for Ubuntu mobile products:
  Confirmed
Status in unity8 package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  When a card has its background enabled, the art should not have its
  bottom edge shaped.

  Until the new shape item comes, we should probably use the
  UbuntuShapeForItem component.

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

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

[Touch-packages] [Bug 1400730] Re: libxext fills up .xsession-errors log files

[netb2c]

** Changed in: libxext (Ubuntu Utopic)
   Status: Fix Committed => Fix Released

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

Title:
  libxext fills up .xsession-errors log files

Status in libxext package in Ubuntu:
  Fix Released
Status in libxext source package in Utopic:
  Fix Released
Status in libxext source package in Vivid:
  Fix Released

Bug description:
  libxext can write debug output, and it can write so much of it that it
  fills up .xsession-errors t be several GB and fill up the hard disk
  (or the equivalent file with lightdm).

  error is "_xgeWireToEvent: Unknown extension 148, this should never
  happen"

  [TEST CASE]
  Install Plasma 5 on utopic
  Use it for a while
  Notice that ~/.xsession-errors is filling up saying "_xgeWireToEvent: Unknown 
extension 148, this should never happen"

  with the new packages this will not happen

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

-- 
Mailing list: https://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 1412333] Re: unable to properly mount/unmount multiple img files

[John]

I only used one single command and that was the output. There wasn't any
other output other than what I posted because the terminal acted as if the
operation was successful with just #. I had mounted all 3 IMG from the file
explorer, then used mkisofs -o /home/john/Downloads/Tizen_2.2-20140122/ and
I listed the directory 3 times on the command to merge the 3 mounted IMG
into 1 but it only merge two and some of them became mounted twice and
wouldn't unmount. If you mount 3 IMG and used mkisofs -o you will see it
doesn't work out. I'm sorry I've been unable to help you. I've already
rebooted since and I never had any more output other than me typing
ubuntu-bug help and a couple other things trying to figure out how to
report the problem.
On Jan 21, 2015 8:25 AM, "Phillip Susi"  wrote:

> You haven't given any command list or output at all.  You named one
> single command you used, and gave a very rough description of what you
> were doing with it ( which I can't follow ).  I need the full commands
> and output.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1412333
>
> Title:
>   unable to properly mount/unmount multiple img files
>
> Status in util-linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I mounted 3 img files and attempted to mkisofs -o  with the path to 3
> img (all img files were in the same directory), then the output was
> data.img merged with platform.img successfully but now the platform.img is
> mounted twice and won't unmount, data.img was mounted twice but I could
> unmount it, and the ums.img is mounted but completely inaccessable,
> unmountable, and doesn't have the eject button next to it's name in the
> files window. I probably wasn't supposed to try it with 3 but now they're
> stuck mounted even after it asked for my password. Terminal output this...
>51.32% done, estimate finish Mon Jan 19 01:36:57 2015
>   Total translation table size: 0
>   Total rockridge attributes bytes: 0
>   Total directory bytes: 342016
>   Path table size(bytes): 2316
>   Max brk space used ca000
>   9768 extents written (19 MB)
>   (process:4299): GLib-CRITICAL **: g_slice_set_config: assertion
> 'sys_page_size == 0' failed
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 14.04
>   Package: mount 2.20.1-5.1ubuntu20.3
>   ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
>   Uname: Linux 3.13.0-44-generic x86_64
>   ApportVersion: 2.14.1-0ubuntu3.6
>   Architecture: amd64
>   Date: Mon Jan 19 01:39:52 2015
>   InstallationDate: Installed on 2014-12-26 (23 days ago)
>   InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64
> (20140722.2)
>   ProcEnviron:
>LANGUAGE=en_US
>TERM=xterm
>PATH=(custom, no user)
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: util-linux
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1412333/+subscriptions
>

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

Title:
  unable to properly mount/unmount multiple img files

Status in util-linux package in Ubuntu:
  Incomplete

Bug description:
  I mounted 3 img files and attempted to mkisofs -o  with the path to 3 img 
(all img files were in the same directory), then the output was data.img merged 
with platform.img successfully but now the platform.img is mounted twice and 
won't unmount, data.img was mounted twice but I could unmount it, and the 
ums.img is mounted but completely inaccessable, unmountable, and doesn't have 
the eject button next to it's name in the files window. I probably wasn't 
supposed to try it with 3 but now they're stuck mounted even after it asked for 
my password. Terminal output this...
   51.32% done, estimate finish Mon Jan 19 01:36:57 2015
  Total translation table size: 0
  Total rockridge attributes bytes: 0
  Total directory bytes: 342016
  Path table size(bytes): 2316
  Max brk space used ca000
  9768 extents written (19 MB)
  (process:4299): GLib-CRITICAL **: g_slice_set_config: assertion 
'sys_page_size == 0' failed

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: mount 2.20.1-5.1ubuntu20.3
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  Date: Mon Jan 19 01:39:52 2015
  InstallationDate: Installed on 2014-12-26 (23 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bu

[Touch-packages] [Bug 1413139] Re: [regression] mir_demo_client_fingerpaint doesn't paint anything any more (with the mouse)

[PS Jenkins bot]

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.11.0

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

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

Title:
  [regression] mir_demo_client_fingerpaint doesn't paint anything any
  more (with the mouse)

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  Triaged

Bug description:
  [regression] mir_demo_client_fingerpaint doesn't paint anything any
  more

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

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

[Touch-packages] [Bug 1217407] Re: whoopsie spams the log with "online" messages

[Bryan Quigley]

Simple check to see if the state has changed before printing.

** Tags added: vivid

** Patch added: "only_log_when_changed.patch"
   
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1217407/+attachment/4303477/+files/only_log_when_changed.patch

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

Title:
  whoopsie spams the log with "online" messages

Status in One Hundred Papercuts:
  Invalid
Status in Ubuntu error tracker client (whoopsie):
  Confirmed
Status in whoopsie package in Ubuntu:
  Confirmed

Bug description:
  It is mostly the "online" messages:

  $ grep whoopsie /var/log/syslog
  Aug 27 07:42:21 xango3 whoopsie[1832]: online
  Aug 27 07:42:27 xango3 whoopsie[1832]: online
  Aug 27 07:43:32  whoopsie[1832]: last message repeated 18 times
  Aug 27 07:44:50  whoopsie[1832]: last message repeated 17 times
  Aug 27 07:45:50  whoopsie[1832]: last message repeated 16 times
  Aug 27 07:46:50  whoopsie[1832]: last message repeated 16 times
  Aug 27 07:47:50  whoopsie[1832]: last message repeated 18 times
  Aug 27 07:48:50  whoopsie[1832]: last message repeated 15 times
  Aug 27 07:49:50  whoopsie[1832]: last message repeated 16 times
  Aug 27 07:50:50  whoopsie[1832]: last message repeated 21 times
  Aug 27 07:51:50  whoopsie[1832]: last message repeated 18 times
  Aug 27 07:52:50  whoopsie[1832]: last message repeated 20 times
  Aug 27 07:53:50  whoopsie[1832]: last message repeated 22 times
  Aug 27 07:54:50  whoopsie[1832]: last message repeated 15 times
  Aug 27 07:55:50  whoopsie[1832]: last message repeated 22 times
  Aug 27 07:56:50  whoopsie[1832]: last message repeated 20 times
  Aug 27 07:57:50  whoopsie[1832]: last message repeated 18 times
  Aug 27 07:58:51  whoopsie[1832]: last message repeated 16 times
  Aug 27 07:59:46  whoopsie[1832]: last message repeated 17 times
  Aug 27 07:59:47 xango3 whoopsie[1832]: online
  Aug 27 08:00:51  whoopsie[1832]: last message repeated 24 times
  Aug 27 08:01:51  whoopsie[1832]: last message repeated 24 times
  Aug 27 08:02:51  whoopsie[1832]: last message repeated 19 times
  Aug 27 08:03:51  whoopsie[1832]: last message repeated 19 times
  Aug 27 08:04:51  whoopsie[1832]: last message repeated 17 times
  Aug 27 08:05:51  whoopsie[1832]: last message repeated 19 times
  Aug 27 08:06:51  whoopsie[1832]: last message repeated 16 times
  Aug 27 08:07:51  whoopsie[1832]: last message repeated 18 times
  Aug 27 08:08:51  whoopsie[1832]: last message repeated 28 times
  Aug 27 08:09:51  whoopsie[1832]: last message repeated 21 times
  Aug 27 08:10:51  whoopsie[1832]: last message repeated 22 times
  Aug 27 08:11:51  whoopsie[1832]: last message repeated 20 times
  Aug 27 08:12:51  whoopsie[1832]: last message repeated 18 times
  Aug 27 08:13:51  whoopsie[1832]: last message repeated 16 times
  Aug 27 08:14:51  whoopsie[1832]: last message repeated 18 times
  Aug 27 08:15:51  whoopsie[1832]: last message repeated 18 times
  Aug 27 08:16:51  whoopsie[1832]: last message repeated 15 times
  Aug 27 08:17:01  whoopsie[1832]: last message repeated 2 times
  Aug 27 08:17:12 xango3 whoopsie[1832]: online
  Aug 27 08:18:21  whoopsie[1832]: last message repeated 22 times
  Aug 27 08:19:21  whoopsie[1832]: last message repeated 15 times
  Aug 27 08:19:44  whoopsie[1832]: last message repeated 5 times
  Aug 27 08:19:44 xango3 whoopsie[1832]: online
  Aug 27 08:20:48  whoopsie[1832]: last message repeated 29 times
  Aug 27 08:21:49  whoopsie[1832]: last message repeated 23 times
  Aug 27 08:22:50  whoopsie[1832]: last message repeated 24 times
  Aug 27 08:23:05  whoopsie[1832]: last message repeated 8 times
  Aug 27 08:23:10 xango3 whoopsie[1832]: online
  Aug 27 08:23:11 xango3 whoopsie[1832]: online
  Aug 27 08:23:15 xango3 whoopsie[1832]: online
  Aug 27 08:23:16 xango3 whoopsie[1832]: online
  Aug 27 08:24:17  whoopsie[1832]: last message repeated 22 times
  Aug 27 08:24:27 xango3 whoopsie[1832]: online
  Aug 27 08:24:28 xango3 whoopsie[1832]: online
  Aug 27 08:25:29  whoopsie[1832]: last message repeated 17 times
  Aug 27 08:25:40  whoopsie[1832]: last message repeated 3 times
  Aug 27 08:25:42 xango3 whoopsie[1832]: online
  Aug 27 08:25:42 xango3 whoopsie[1832]: online
  Aug 27 08:25:43 xango3 whoopsie[1832]: online
  Aug 27 08:26:44  whoopsie[1832]: last message repeated 15 times
  Aug 27 08:26:55  whoopsie[1832]: last message repeated 2 times
  Aug 27 08:26:56 xango3 whoopsie[1832]: online
  Aug 27 08:33:23 xango3 whoopsie[1568]: whoopsie 0.2.23 starting up.
  Aug 27 08:33:23 xango3 whoopsie[1568]: Using lock path: 
/var/lock/whoopsie/lock
  Aug 27 08:33:23 xango3 whoopsie[1794]: offline
  Aug 27 08:33:27 xango3 whoopsie[1794]: offline
  Aug 27 08:33:27 xango3 whoopsie[1794]: online
  Aug 27 08:33:28 xango3 whoopsie[1794]: online
  Aug 27 08:33:29 xango3 whoopsie[1794]: online
  Aug 27 08:33:29 xango3 whoopsie[1794]: online
 

Re: [Touch-packages] [Bug 1393624] Re: Lock screen rejects password on Ubuntu 14.04

[Andrea Azzarone]

The correct output should be:
-rw-r- 1 root shadow 2823 Jan 21 21:02 /etc/shadow

Please note that the group owner MUST be "shadow". Not sure why it got
changed during the update, for sure not a unity bug. Please try to change
the group owner of that file and try to lock/unlock again.

2015-01-22 1:37 GMT+01:00 LexLythius <1393...@bugs.launchpad.net>:

> @bregma It does happen regardless of how many monitors I have connected.
>
> @andyrock $ ls -l /etc/shadow
> -rw-r- 1 root root 1529 oct 15 22:20 /etc/shadow
>
> FWIW, password is hashed with CRYPT/SHA512 ($6$...), using default
> number of rounds.
>
> --
> You received this bug notification because you are subscribed to Unity.
> https://bugs.launchpad.net/bugs/1393624
>
> Title:
>   Lock screen rejects password on Ubuntu 14.04
>
> Status in Unity:
>   Incomplete
> Status in unity package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Password is systematically rejected on the lock screen. However, if I
>   click Switch account, the *greeter* does accept the same password.
>
>   This issue is reproducible either by hitting the Ctrl+Alt+L shortcut key
> or by runnibg
>   `gnome-screensaver-command -l`
>
>   This happens after I upgraded from Ubuntu 12.04 to 14.04.
>   I had ATI Radeon HD 3870 with open source drivers, now I have GeForce
> GTX 750 Ti with NVIDIA proprietary drivers. Same thing.
>
>   Ubuntu 14.04.1 LTS
>   Linux 3.13.0-39-generic x86_64
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/unity/+bug/1393624/+subscriptions
>


-- 
Andrea Azzarone
http://launchpad.net/~andyrock
http://wiki.ubuntu.com/AndreaAzzarone

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

Title:
  Lock screen rejects password on Ubuntu 14.04

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

Bug description:
  Password is systematically rejected on the lock screen. However, if I
  click Switch account, the *greeter* does accept the same password.

  This issue is reproducible either by hitting the Ctrl+Alt+L shortcut key or 
by runnibg
  `gnome-screensaver-command -l`

  This happens after I upgraded from Ubuntu 12.04 to 14.04.
  I had ATI Radeon HD 3870 with open source drivers, now I have GeForce GTX 750 
Ti with NVIDIA proprietary drivers. Same thing.

  Ubuntu 14.04.1 LTS
  Linux 3.13.0-39-generic x86_64

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

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

[Touch-packages] [Bug 1411323] Re: [address book] share handler screen has a confusing "ok" icon

[Selene Scriven]

This is certainly better than it was before, but it's still a little
confusing.  Now the icons are "X" on the left, and two checkmarks on the
right (one in a box, one without a box).  The difference between the two
checkmarks isn't particularly obvious based only on appearance.

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

Title:
  [address book] share handler screen has a confusing "ok" icon

Status in Address Book App:
  In Progress
Status in the base for Ubuntu mobile products:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in address-book-app package in Ubuntu:
  Fix Released
Status in address-book-app package in Ubuntu RTM:
  In Progress

Bug description:
  as found on user testing, the share icon is confusing for users that
  get to this screen and do not know how to proceed.

  Steps to reproduce:
  Using telegram
  click in contacts
  then click  in import
  select from address book
  once the content hub launches, select the address book
  select a few contact

  Expected result:
  there is a clear button to "ok" selection, that matches the "X" to cancel. 
Maybe a tick like in the camera app

  Actual result:
  A share icon is used to "ok"

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

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

[Touch-packages] [Bug 1314095] Re: Unity Lockscreen in 14.04 can't unlock when using LDAP account

[Mario Codeniera]

It same error here, based on my understanding it only fetch to the
/etc/shadow not on the nscd cache (/var/cache/nscd/passwd) where
pam_ldap is pointing with. But if I switch user, and login with the same
user it will retain the previous desktop during the lock screen (even
changing desktop say MATE, GNOME classic upon relogin). Tried with
gnome-screensaver and with mate-screensaver same result. Sadly not on
the Lock Screen as it generate the following log:

Jan 22 17:14:35 ambotlang gnome-screensaver-dialog: 
pam_unix(gnome-screensaver:auth): authentication failure; logname= uid=104781 
euid=104781 tty=:1.0 ruser= rhost=  user=txunil
Jan 22 17:14:44 ambotlang lightdm: pam_unix(lightdm:auth): authentication 
failure; logname= uid=0 euid=0 tty=:0 ruser= rhost=  user=txunil

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

Title:
  Unity Lockscreen in 14.04 can't unlock when using LDAP account

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

Bug description:
  My setup is:

  Ubuntu 14.04 LTS,
  ldap accounts,
  krb5 authentication,
  Lightdm,
  Unity session

  ldap+krb5 is configured using nss-ldapd and nslcd. It works fine. getent 
passwd and getent shadow works fine.
  I am able to login in console without any problems.
  I was able to login in lightdm.
  Then I used the lock screen.
  I could not disable the lock screen using my password.
  I rebooted my computer.

  Now:
  After logging in through lightdm, the unity lockscreen locks the screen 
immediately and I can not disable it using my password.

  From my short inspection of auth.log and unix_chkpwd sources it seems,
  that unix_chkpwd works fine when called from lightdm and fails to get
  user info when called from unity lockscreen.


  lsb_release -rd
  Description:  Ubuntu 14.04 LTS
  Release:  14.04

  apt-cache policy unity lightdm libpam-modules
  unity:
Installed: 7.2.0+14.04.20140416-0ubuntu1
Candidate: 7.2.0+14.04.20140416-0ubuntu1
Version table:
   *** 7.2.0+14.04.20140416-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status
  lightdm:
Installed: 1.10.0-0ubuntu3
Candidate: 1.10.0-0ubuntu3
Version table:
   *** 1.10.0-0ubuntu3 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status
  libpam-modules:
Installed: 1.1.8-1ubuntu2
Candidate: 1.1.8-1ubuntu2
Version table:
   *** 1.1.8-1ubuntu2 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  Contents of /var/log/auth.log:

  Apr 29 06:49:27 localhost lightdm: pam_succeed_if(lightdm:auth): requirement 
"user ingroup nopasswdlogin" not met by user "user"
  Apr 29 06:49:31 localhost lightdm: pam_unix(lightdm:auth): authentication 
failure; logname= uid=0 euid=0 tty=:2 ruser= rhost=  user=user
  Apr 29 06:49:31 localhost lightdm: pam_krb5(lightdm:auth): user user 
authenticated as user@NETWORK
  Apr 29 06:49:32 localhost lightdm[15604]: pam_unix(lightdm-greeter:session): 
session closed for user lightdm
  Apr 29 06:49:37 localhost unix_chkpwd[15825]: check pass; user unknown
  Apr 29 06:49:37 localhost unix_chkpwd[15825]: password check failed for user 
(user)
  Apr 29 06:49:37 localhost compiz: pam_unix(lightdm:auth): authentication 
failure; logname= uid=1001 euid=1001 tty= ruser= rhost=  user=user
  Apr 29 06:49:37 localhost compiz: pam_krb5(lightdm:auth): user user 
authenticated as user@NETWORK
  Apr 29 06:49:37 localhost unix_chkpwd[15826]: could not obtain user info 
(user)
  Apr 29 06:49:37 localhost unix_chkpwd[15827]: could not obtain user info 
(user)
  Apr 29 06:49:37 localhost compiz: pam_succeed_if(lightdm:auth): requirement 
"user ingroup nopasswdlogin" not met by user "user"

  cat /etc/pam.d/common-auth 
  account requiredpam_unix.so
  authrequiredpam_group.so
  auth [success=2 default=ignore] pam_unix.so try_first_pass nullok_secure
  auth [success=1 default=ignore] pam_krb5.so try_first_pass minimum_uid=200
  authrequisite   pam_deny.so
  authrequiredpam_permit.so

  authoptionalpam_afs_session.so minimum_uid=200
  authoptionalpam_ecryptfs.so unwrap
  authoptionalpam_cap.so

  cat /etc/pam.d/common-account 
  account requiredpam_unix.so

  cat /etc/pam.d/lightdm
  authrequisite   pam_nologin.so
  authsufficient  pam_succeed_if.so user ingroup nopasswdlogin
  @include common-auth
  authoptionalpam_gnome_keyring.so
  @include common-account
  session [success=ok ignore=ignore module_unknown=ignore default=bad] 
pam_selinux.so close
  authoptionalpam_group.so
  session requiredpam_limits.so
  @include common-session
  session [success=ok ignore=ignore module_unknown=ignor

[Touch-packages] [Bug 1317449]

[Cfeck]

*** Bug 343014 has been marked as a duplicate of this bug. ***

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

Title:
  sqlite3 version 3.8.2 breaks digikam

Status in digiKam - digital photo management:
  Won't Fix
Status in SQLite:
  Won't Fix
Status in digikam package in Ubuntu:
  Fix Released
Status in sqlite3 package in Ubuntu:
  Fix Released
Status in digikam source package in Trusty:
  Confirmed
Status in sqlite3 source package in Trusty:
  Confirmed
Status in digikam source package in Utopic:
  Fix Released
Status in sqlite3 source package in Utopic:
  Fix Released

Bug description:
  Please update sqlite to a version > 3.8.2.

  According to https://bugs.kde.org/show_bug.cgi?id=329697 sqlite3 version 
3.8.2 causes crashes in digikam (and possibly other software) in various 
situations. Several reports confirm, that versions > 3.8.2 fix the issue.
  I'm using the 3.8.4.3 package from debian testing right now and can't trigger 
crashes anymore.

  Workaround:
  Install sqlite3 > 3.8.2, e.g. you can manually install the corresponding deb 
packages from either utopic or debian.

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

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

[Touch-packages] [Bug 1217407] Re: whoopsie spams the log with "online" messages

[Bryan Quigley]

I can confirm this running Vivid using systemd as the init system.

Whoopsie Toal $ sudo journalctl | grep whoopsie | wc -l
4498
Just telling me it's online $ sudo journalctl | grep whoopsie | grep online | 
wc -l
4470
Total log $ sudo journalctl | wc -l
36838

This is for 1 day of use...

** Changed in: hundredpapercuts
   Status: Incomplete => Invalid

** Changed in: whoopsie (Ubuntu)
   Status: Incomplete => Confirmed

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

** Changed in: whoopsie (Ubuntu)
   Importance: Medium => Low

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

Title:
  whoopsie spams the log with "online" messages

Status in One Hundred Papercuts:
  Invalid
Status in Ubuntu error tracker client (whoopsie):
  Confirmed
Status in whoopsie package in Ubuntu:
  Confirmed

Bug description:
  It is mostly the "online" messages:

  $ grep whoopsie /var/log/syslog
  Aug 27 07:42:21 xango3 whoopsie[1832]: online
  Aug 27 07:42:27 xango3 whoopsie[1832]: online
  Aug 27 07:43:32  whoopsie[1832]: last message repeated 18 times
  Aug 27 07:44:50  whoopsie[1832]: last message repeated 17 times
  Aug 27 07:45:50  whoopsie[1832]: last message repeated 16 times
  Aug 27 07:46:50  whoopsie[1832]: last message repeated 16 times
  Aug 27 07:47:50  whoopsie[1832]: last message repeated 18 times
  Aug 27 07:48:50  whoopsie[1832]: last message repeated 15 times
  Aug 27 07:49:50  whoopsie[1832]: last message repeated 16 times
  Aug 27 07:50:50  whoopsie[1832]: last message repeated 21 times
  Aug 27 07:51:50  whoopsie[1832]: last message repeated 18 times
  Aug 27 07:52:50  whoopsie[1832]: last message repeated 20 times
  Aug 27 07:53:50  whoopsie[1832]: last message repeated 22 times
  Aug 27 07:54:50  whoopsie[1832]: last message repeated 15 times
  Aug 27 07:55:50  whoopsie[1832]: last message repeated 22 times
  Aug 27 07:56:50  whoopsie[1832]: last message repeated 20 times
  Aug 27 07:57:50  whoopsie[1832]: last message repeated 18 times
  Aug 27 07:58:51  whoopsie[1832]: last message repeated 16 times
  Aug 27 07:59:46  whoopsie[1832]: last message repeated 17 times
  Aug 27 07:59:47 xango3 whoopsie[1832]: online
  Aug 27 08:00:51  whoopsie[1832]: last message repeated 24 times
  Aug 27 08:01:51  whoopsie[1832]: last message repeated 24 times
  Aug 27 08:02:51  whoopsie[1832]: last message repeated 19 times
  Aug 27 08:03:51  whoopsie[1832]: last message repeated 19 times
  Aug 27 08:04:51  whoopsie[1832]: last message repeated 17 times
  Aug 27 08:05:51  whoopsie[1832]: last message repeated 19 times
  Aug 27 08:06:51  whoopsie[1832]: last message repeated 16 times
  Aug 27 08:07:51  whoopsie[1832]: last message repeated 18 times
  Aug 27 08:08:51  whoopsie[1832]: last message repeated 28 times
  Aug 27 08:09:51  whoopsie[1832]: last message repeated 21 times
  Aug 27 08:10:51  whoopsie[1832]: last message repeated 22 times
  Aug 27 08:11:51  whoopsie[1832]: last message repeated 20 times
  Aug 27 08:12:51  whoopsie[1832]: last message repeated 18 times
  Aug 27 08:13:51  whoopsie[1832]: last message repeated 16 times
  Aug 27 08:14:51  whoopsie[1832]: last message repeated 18 times
  Aug 27 08:15:51  whoopsie[1832]: last message repeated 18 times
  Aug 27 08:16:51  whoopsie[1832]: last message repeated 15 times
  Aug 27 08:17:01  whoopsie[1832]: last message repeated 2 times
  Aug 27 08:17:12 xango3 whoopsie[1832]: online
  Aug 27 08:18:21  whoopsie[1832]: last message repeated 22 times
  Aug 27 08:19:21  whoopsie[1832]: last message repeated 15 times
  Aug 27 08:19:44  whoopsie[1832]: last message repeated 5 times
  Aug 27 08:19:44 xango3 whoopsie[1832]: online
  Aug 27 08:20:48  whoopsie[1832]: last message repeated 29 times
  Aug 27 08:21:49  whoopsie[1832]: last message repeated 23 times
  Aug 27 08:22:50  whoopsie[1832]: last message repeated 24 times
  Aug 27 08:23:05  whoopsie[1832]: last message repeated 8 times
  Aug 27 08:23:10 xango3 whoopsie[1832]: online
  Aug 27 08:23:11 xango3 whoopsie[1832]: online
  Aug 27 08:23:15 xango3 whoopsie[1832]: online
  Aug 27 08:23:16 xango3 whoopsie[1832]: online
  Aug 27 08:24:17  whoopsie[1832]: last message repeated 22 times
  Aug 27 08:24:27 xango3 whoopsie[1832]: online
  Aug 27 08:24:28 xango3 whoopsie[1832]: online
  Aug 27 08:25:29  whoopsie[1832]: last message repeated 17 times
  Aug 27 08:25:40  whoopsie[1832]: last message repeated 3 times
  Aug 27 08:25:42 xango3 whoopsie[1832]: online
  Aug 27 08:25:42 xango3 whoopsie[1832]: online
  Aug 27 08:25:43 xango3 whoopsie[1832]: online
  Aug 27 08:26:44  whoopsie[1832]: last message repeated 15 times
  Aug 27 08:26:55  whoopsie[1832]: last message repeated 2 times
  Aug 27 08:26:56 xango3 whoopsie[1832]: online
  Aug 27 08:33:23 xango3 whoopsie[1568]: whoopsie 0.2.23 starting up.
  Aug 27 08:33:23 xango3 whoopsie[1568]: Using lock path: 
/var/lock

[Touch-packages] [Bug 1413458] [NEW] Intermittent Intel GPU Lockup: intel_crtc_wait_for_pending_flips

[David R. Hedges]

Public bug reported:

Sometimes when playing a video (VLC) or browsing in chromium, the
display stops updating except for the mouse pointer. Audio playback will
continue. I can press ctrl-alt-F1 to get to another VT (though there is
a delay of ~10 seconds before this occurs) and then switch back and
things seem fine. I see this in the syslog after it's occurred:

Jan 21 21:52:33 sydney kernel: [365284.305075] CPU: 7 PID: 1567 Comm: Xorg 
Tainted: GW 3.16.0-29-generic #39-Ubuntu
Jan 21 21:52:33 sydney kernel: [365284.305077] Hardware name: Dell Inc. 
OptiPlex 9010/051FJ8, BIOS A19 08/18/2014
Jan 21 21:52:33 sydney kernel: [365284.305079]  0009 
8803f9cebbf8 8278218a 
Jan 21 21:52:33 sydney kernel: [365284.305083]  8803f9cebc30 
8206fedd  8804039fc000
Jan 21 21:52:33 sydney kernel: [365284.305086]  880403788210 
880403ae6000 880403ae6000 8803f9cebc40
Jan 21 21:52:33 sydney kernel: [365284.305089] Call Trace:
Jan 21 21:52:33 sydney kernel: [365284.305097]  [] 
dump_stack+0x45/0x56
Jan 21 21:52:33 sydney kernel: [365284.305102]  [] 
warn_slowpath_common+0x7d/0xa0
Jan 21 21:52:33 sydney kernel: [365284.305106]  [] 
warn_slowpath_null+0x1a/0x20
Jan 21 21:52:33 sydney kernel: [365284.305129]  [] 
intel_crtc_wait_for_pending_flips+0x16c/0x180 [i915]
Jan 21 21:52:33 sydney kernel: [365284.305134]  [] ? 
prepare_to_wait_event+0x100/0x100
Jan 21 21:52:33 sydney kernel: [365284.305155]  [] 
intel_crtc_disable_planes+0x33/0x1c0 [i915]
Jan 21 21:52:33 sydney kernel: [365284.305174]  [] 
ironlake_crtc_disable+0x50/0x980 [i915]
Jan 21 21:52:33 sydney kernel: [365284.305193]  [] ? 
drm_modeset_lock+0x33/0xf0 [drm]
Jan 21 21:52:33 sydney kernel: [365284.305197]  [] ? 
mutex_lock+0x12/0x30
Jan 21 21:52:33 sydney kernel: [365284.305217]  [] 
intel_crtc_update_dpms+0x67/0xa0 [i915]
Jan 21 21:52:33 sydney kernel: [365284.305237]  [] 
intel_connector_dpms+0x59/0x70 [i915]
Jan 21 21:52:33 sydney kernel: [365284.305253]  [] 
drm_mode_obj_set_property_ioctl+0x399/0x3a0 [drm]
Jan 21 21:52:33 sydney kernel: [365284.305267]  [] 
drm_mode_connector_property_set_ioctl+0x30/0x40 [drm]
Jan 21 21:52:33 sydney kernel: [365284.305278]  [] 
drm_ioctl+0x1df/0x680 [drm]
Jan 21 21:52:33 sydney kernel: [365284.305284]  [] ? 
fsnotify+0x27c/0x350
Jan 21 21:52:33 sydney kernel: [365284.305287]  [] ? 
fsnotify+0x27c/0x350
Jan 21 21:52:33 sydney kernel: [365284.305291]  [] 
do_vfs_ioctl+0x2c8/0x4a0
Jan 21 21:52:33 sydney kernel: [365284.305295]  [] ? 
__sb_end_write+0x31/0x60
Jan 21 21:52:33 sydney kernel: [365284.305299]  [] ? 
vfs_write+0x1b2/0x1f0
Jan 21 21:52:33 sydney kernel: [365284.305302]  [] 
SyS_ioctl+0x81/0xa0
Jan 21 21:52:33 sydney kernel: [365284.305306]  [] 
system_call_fastpath+0x1a/0x1f
Jan 21 21:52:33 sydney kernel: [365284.305309] ---[ end trace 491ebdb18d4be6c4 
]---

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: libgl1-mesa-dri 10.3.2-0ubuntu0.1
ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
Uname: Linux 3.16.0-29-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.7-0ubuntu8.1
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,decor,move,place,grid,mousepoll,session,snap,vpswitch,wall,neg,obs,compiztoolbox,regex,imgpng,resize,gnomecompat,animation,expo,ezoom,workarounds,unitymtgrabhandles,screenshot,fade,scale,unityshell]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed Jan 21 21:55:30 2015
DistUpgraded: Fresh install
DistroCodename: utopic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:052c]
InstallationDate: Installed on 2014-11-29 (53 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: Dell Inc. OptiPlex 9010
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.16.0-29-generic.efi.signed 
root=UUID=3a6b7e94-440c-4aaf-adea-643f6518b8cf ro rootflags=subvol=@ quiet 
splash vt.handoff=7
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/18/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A19
dmi.board.name: 051FJ8
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 15
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd08/18/2014:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr:
dmi.product.name: OptiPlex 9010
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
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.2-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.

[Touch-packages] [Bug 1308540] Re: [lockscreen] the password entry is not shared between screens

[franglais.125]

I can confirm that the new version fixes the problem.

Running 7.2.4+14.04.20141217-0ubuntu1

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

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

Title:
  [lockscreen] the password entry is not shared between screens

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

Bug description:
  [Impact]

  Using the Unity lockscreen on a multiple-screen session results in the
  password field being cleared every time different screen is focused.

  [Test Case]

  Using trusty candidate on a dual monitor config
  - log into unity
  - lock screen
  - start typing your password on one screen
  - move the pointer on the other screen

  -> the entry is displayed empty

  Ideally the same entry would be move so you can keep typing even if
  you happened to have move the focus, that's what lightdm/unity-greeter
  is doing

  [Regression Potential]

  Any modification to the password dialogs could result in the inability
  to unlock the screen or make passwords available in cleartext.  Care
  has been take to avoind introducing such situations with this change.

  [Other info]

  The Ubuntu 14.04 LTS SRU fix has been cherry-picked from the Ubuntu
  14.10 release, where it has been in production use for a few months.

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

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

[Touch-packages] [Bug 1256576] Re: Ubuntu 12.04 LTS: OpenSSL downlevel version is 1.0.0, and does not support TLS 1.2

[spbike]

Mark what exact tests did you run?
https://www.ssllabs.com/ssltest/analyze.html by chance?

In your apache config file did you have:
SSLProtocol -ALL -SSLv3 +TLSv1 +TLSv1.1 +TLSv1.2

Reference for that command (Ubuntu 12.04 uses apache 2.2):
http://httpd.apache.org/docs/2.2/mod/mod_ssl.html

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

Title:
  Ubuntu 12.04 LTS: OpenSSL downlevel version is 1.0.0, and does not
  support TLS 1.2

Status in openssl package in Ubuntu:
  Fix Released

Bug description:
  The long term support version of Ubuntu 12.04 provides OpenSSL 1.0.0.
  A wireshark trace shows the version of OpenSSL used by Ubuntu does not
  support TLS 1.2. According to the change logs, TLS 1.2 support was
  added 14 March 2012. The change log can be found at
  http://www.openssl.org/news/changelog.html, and the TLS additions can
  be found under the heading "Changes between 1.0.0h and 1.0.1".

  $ ldd /usr/lib/x86_64-linux-gnu/libssl.so
  linux-vdso.so.1 =>  (0x7fffd9d84000)
  libcrypto.so.1.0.0 => /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
  (0x7f1e0691e000)
  libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f1e0655e000)
  libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f1e06359000)
  libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f1e06142000)
  /lib64/ld-linux-x86-64.so.2 (0x7f1e06f6d000)

  ***

  OpenSSL 1.0.1 is compatible with 1.0.0. From the OpenSSL FAQ
  (http://www.openssl.org/support/faq.html):

  8. How does the versioning scheme work?

  After the release of OpenSSL 1.0.0 the versioning scheme changed.
  Letter releases (e.g. 1.0.1a) can only contain bug and security fixes
  and no new features. Minor releases change the last number (e.g.
  1.0.2) and can contain new features that retain binary compatibility.
  Changes to the middle number are considered major releases and neither
  source nor binary compatibility is guaranteed.

  **

  By the way, its nearly impossible to file a bug report through the
  launch pad. The maze that's been created is impossible to navigate,
  and its worse than one of those phone menu systems. I had to look up
  the URL to file at http://www.cryptopp.com/wiki/Talk:Linux. Great job
  to the designers of the system. Its probably the same idiots who
  thought a tablet manager was a great idea on the desktop..

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

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

[Touch-packages] [Bug 1401916] Re: Configuration of screens positions and geometry

[Daniel van Vugt]

Every large toolkit already has it's own preferred config storage and
API to access that. Putting a redundant implementation in Mir is not
helpful. You would either end up with the old problem of many different
config file formats in unrelated places accessed using unrelated APIs,
or a redundant config API that real shells will never use.

The best outcome for Unity8 would be for it to have a nice GUI that talks 
GSettings (or whatever it prefers) directly. Such an implementation would 
bypass any storage features in Mir. It should not exist in Mir. If you look at 
the thread, most people are saying what I'm saying here:
https://lists.ubuntu.com/archives/mir-devel/2015-January/thread.html#1018

There is a compromise that might make sense however...
While libmir* should not have any feature that touches the disk or writes 
files, it might provide a serialization function to convert a config structure 
into a string (and vice versa). And a string is something that any 
configuration API can use; QSettings, GSettings, gconf, INI, XML. So we can 
make it easier for shells, without imposing any particular file structure from 
Mir.

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

Title:
  Configuration of screens positions and geometry

Status in Mir:
  Fix Released
Status in Qt integration with the Mir display server:
  New
Status in Ubuntu UX bugs:
  New
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Under unity7/xorg it's possible to configure the position of the screens and 
their geometry, that includes
  - resolution of each screen
  - rotation possible
  - relative position (external on top of laptop, or on the right)
  - definition of a "primary" monitor (the one containing the launcher if you 
decide to have that UI element only on one screen)
  - etc

  Under unity7 the configuration is applied on login by unity-settings-
  daemon using xrandr. In the new world unity8 should probably be the
  one setting up the configuration at start

  It would be useful to have input from design as well, on what should
  happen when connecting an unity8 powered device to an external screen.
  Should it mirror by default? Do we need settings control to configure
  what to do, ...

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

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

[Touch-packages] [Bug 678421] Re: Error message for a faulty ~/.profile script

[Gunnar Hjalmarsson]

Thanks for the correction, Brian.

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

Title:
  Error message for a faulty ~/.profile script

Status in GDM: The Gnome Display Manager:
  New
Status in gdm package in Ubuntu:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in gdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Trusty:
  Fix Committed
Status in gdm source package in Utopic:
  Fix Committed
Status in lightdm source package in Utopic:
  Fix Committed
Status in gdm package in Debian:
  New

Bug description:
  trusty and utopic SRU requests
  ==

  [Impact]

  In case of a syntax error in either of ~/.profile or a few other
  similar files, the Xorg login is interrupted, and the user is taken
  back to the login screen without an explanation. Debugging this
  problem may be a time consuming exercise, especially for non-
  experienced users.

  With the proposed change, lightdm/gdm does not try to load such a
  file, but shows a warning dialog instead. (A warning dialog is also
  shown in case of some other type of error, which would not have caused
  the login to fail.)

  [Test Case]

  To reproduce:

  * Edit ~/.profile and add something bad, e.g. a non-closed parenthesis.
  * Log out and find that you can't log in to a graphical session.

  After installing the proposed lightdm/gdm version, you'll instead see
  the dialog and can log in.

  [Regression Potential]

  Since this is only about improved exception handling, it does not at
  all affect users with correct configuration files. The regression risk
  ought to be minimal.

  [Original description]

  Binary package hint: gdm

  After adding "function AddPath { PATH="$1:$PATH" }" to $HOME/.profile
  made the Xorg startup fail. (At that moment I had already forgotten
  the changes made to the .profile). As I had autologin that meant it
  kept trying to login and finally showed me the graphics
  reconfiguration screen. That sent me to a huge hunt for xorg conf and
  setup problems.

  Anyway finally tracked this down. I had used bash syntax in .profile
  file whereas it was run with sh.

  This is not a bug per se but I think a user mistake in ".profile"
  shouldn't bring the whole xorg startup to a halt as it does with
  autologin. I propose running user ".profile" and ".xprofile" scripts
  so that Xsession script continues running even if they have errors.
  I'm not sure whether this change would have some negative effects as
  well.

  1) Ubuntu Lucid, Linux egon-laptop 2.6.32-25-generic #45-Ubuntu SMP Sat Oct 
16 19:48:22 UTC 2010 i686 GNU/Linux
  2) gdm 2.30.2.is.2.30.0-0ubuntu4

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

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

[Touch-packages] [Bug 1400626] Re: Please backport xtrans, libdrm, x11proto-{fonts, core} packages for 14.04.2

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-branches/ubuntu/trusty/xf86-input-wacom-
lts-utopic/trusty-proposed

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

Title:
  Please backport xtrans, libdrm, x11proto-{fonts,core} packages for
  14.04.2

Status in libdrm package in Ubuntu:
  In Progress
Status in x11proto-core package in Ubuntu:
  New
Status in x11proto-fonts package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  In Progress
Status in xtrans package in Ubuntu:
  In Progress
Status in libdrm source package in Trusty:
  Fix Released
Status in x11proto-core source package in Trusty:
  Fix Released
Status in x11proto-fonts source package in Trusty:
  Fix Released
Status in xorg source package in Trusty:
  Fix Committed
Status in xtrans source package in Trusty:
  Fix Released

Bug description:
  In order to upload the new xorg-server we need to backport the following 
packages from utopic:
  libdrm
  x11proto-core
  x11proto-fonts
  xtrans

  libdrm 2.4.52-1->2.4.56-1 seems to have the following changes:
  - Hides private symbols from all libdrm libraries
  - fixes MSAA on Hawaii (radeon).
  - Adds cherryview pci-ids (intel).
  - Makes libdrm-nouveau threadsafe with concurrent access to the drm fd.
  - Fixes to exynos and freedreno.
  - Enables building libdrm-freedreno1 and libdrm-exynos1

  x11proto-core's main change appears to be changing from the 'pointer' type to 
'void *':
  
https://launchpadlibrarian.net/173873109/x11proto-core_7.0.24-1_7.0.26-1.diff.gz

  x11proto-fonts' main change is the same as x11proto-core, but the 
documentation is reformatted too:
  
https://launchpadlibrarian.net/173873038/x11proto-fonts_2.1.2-1_2.1.3-1.diff.gz

  xtrans seems to have 2 minor changes, increase default unix pipe size and add 
support for systemd socket activation:
  https://launchpadlibrarian.net/173873112/xtrans_1.3.2-1_1.3.4-1.diff.gz

  xorg needs to be slightly updated, to allow xserver-xorg to provide
  the unrenamed lts-utopic, and to allow xorg to be installed with the
  renamed xorg-server.

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

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

[Touch-packages] [Bug 704123] Re: Network Manager asks for the PIN even if it is memorized

[Anders Feder]

Uqbar (uqbar): Unfortunately, nothing is ever accomplished by sitting
around and complaining. I personally don't have the PC where I
experienced this issue anymore, so I can't attempt to reproduce the
reports that it is still occuring. Someone who is experiencing the issue
will need to pinpoint the bug in the code before anyone can attempt to
address it.

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

Title:
  Network Manager asks for the PIN even if it is memorized

Status in One Hundred Papercuts:
  Triaged
Status in NetworkManager:
  New
Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager package in Debian:
  New

Bug description:
  
  HOW TO REPRODUCE
  

  1. Plug the USB modem into a port.

  2. When you are asked to enter the modem's PIN, do along with the
  "automatically unlock this device" option.

  3. Unplug the modem, and plug it again.

  **
  EXPECTED BEHAVIOUR
  **

  - The modem to be automatically unlocked.

  **
  REAL BEHAVIOUR
  **

  - You are asked to enter the PIN again.

  
  WORK-AROUNDS
  

  - Changing the SIM's PIN to empty.

  - Renaming the "/usr/share/nm-applet/gsm-unlock.ui" file.

  
  
  RELEVANT DETAILS
  

  - The same behaviour when configuring the PIN from the "Network
  Connections" menu.

  - Even if the PIN is stored in "/etc/NetworkManager/system-
  connections/", Network Manager cannot retrieve it.

  - The bug makes the device to become locked as soon as network
  connectivity is lost for a while.

  - This bug forces administrators to tell the PIN to other users, while
  they will rather want to keep it in secret and just allow themselves
  to be able to configure the connectivity in specific devices.

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

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

[Touch-packages] [Bug 678421] Re: Error message for a faulty ~/.profile script

[Brian Murray]

@Gunnar - the SRU team tools understand the tags v-done and
v-done-$release, but not v-done-$release-$package.

** Tags removed: verification-done-trusty-gdm verification-done-trusty-lightdm
** Tags added: verification-done-trusty

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

Title:
  Error message for a faulty ~/.profile script

Status in GDM: The Gnome Display Manager:
  New
Status in gdm package in Ubuntu:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in gdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Trusty:
  Fix Committed
Status in gdm source package in Utopic:
  Fix Committed
Status in lightdm source package in Utopic:
  Fix Committed
Status in gdm package in Debian:
  New

Bug description:
  trusty and utopic SRU requests
  ==

  [Impact]

  In case of a syntax error in either of ~/.profile or a few other
  similar files, the Xorg login is interrupted, and the user is taken
  back to the login screen without an explanation. Debugging this
  problem may be a time consuming exercise, especially for non-
  experienced users.

  With the proposed change, lightdm/gdm does not try to load such a
  file, but shows a warning dialog instead. (A warning dialog is also
  shown in case of some other type of error, which would not have caused
  the login to fail.)

  [Test Case]

  To reproduce:

  * Edit ~/.profile and add something bad, e.g. a non-closed parenthesis.
  * Log out and find that you can't log in to a graphical session.

  After installing the proposed lightdm/gdm version, you'll instead see
  the dialog and can log in.

  [Regression Potential]

  Since this is only about improved exception handling, it does not at
  all affect users with correct configuration files. The regression risk
  ought to be minimal.

  [Original description]

  Binary package hint: gdm

  After adding "function AddPath { PATH="$1:$PATH" }" to $HOME/.profile
  made the Xorg startup fail. (At that moment I had already forgotten
  the changes made to the .profile). As I had autologin that meant it
  kept trying to login and finally showed me the graphics
  reconfiguration screen. That sent me to a huge hunt for xorg conf and
  setup problems.

  Anyway finally tracked this down. I had used bash syntax in .profile
  file whereas it was run with sh.

  This is not a bug per se but I think a user mistake in ".profile"
  shouldn't bring the whole xorg startup to a halt as it does with
  autologin. I propose running user ".profile" and ".xprofile" scripts
  so that Xsession script continues running even if they have errors.
  I'm not sure whether this change would have some negative effects as
  well.

  1) Ubuntu Lucid, Linux egon-laptop 2.6.32-25-generic #45-Ubuntu SMP Sat Oct 
16 19:48:22 UTC 2010 i686 GNU/Linux
  2) gdm 2.30.2.is.2.30.0-0ubuntu4

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

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

[Touch-packages] [Bug 1413428] Re: apt-get's HTTP pipeline desynchronizes, hilarity ensues

[Edward Z. Yang]

Oh, apparently you have to set the timestamp on the files sometime
before 29 Dec 2014 too, because nginx doesn't spazz unless the if-range
is also sent.

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

Title:
  apt-get's HTTP pipeline desynchronizes, hilarity ensues

Status in apt package in Ubuntu:
  New

Bug description:
  tl;dr: apt-get improperly handles servers which respond 404 with HTTP
  content to a Range query, resulting in a desychronized HTTP buffer and
  hilarious bugs.

  OK, this is going to be a long one. Where to begin? I was updating my
  Aptitude packages and noticed that my Dropbox source was not updating
  correctly:

  Err http://linux.dropbox.com utopic/main amd64 Packages
Bad header line

  Silly Dropbox, not checking their package list! I report it to them,
  and they report back that the URL being fetched seems to be giving
  back a well formed HTTP response, and that they couldn't reproduce. I
  verify that is the case. We ponder the problem for a while, clearing
  caches and permuting the source.list line, and finally someone
  suggests running -o Debug::Acquire::http=true. I take the log and
  scroll to the error line:

  Answer for: 
http://linux.dropbox.com/ubuntu/dists/utopic/main/i18n/Translation-en_US.lzma
  Package: dropbox
  Priority: optional
  Section: gnome
  Installed-Size: 404
  Maintainer: Rian Hunter 
  Architecture: amd64
  Version: 2.10.0
  Replaces: nautilus-dropbox
  Provides: nautilus-dropbox
  Depends: procps, python-gtk2 (>= 2.12), python (>= 2.5), libatk1.0-0 (>= 
1.20.0), libc6 (>= 2.4), libcairo2 (>= 1.6.0), libglib2.0-0 (>= 2.16.0), 
libgtk2.0-0 (>= 2.12.0), libpango1.0-0 (>= 1.20.1)
  Suggests: nautilus (>= 2.16.0), python-gpgme (>= 0.1)
  Breaks: nautilus-dropbox
  Filename: pool/main/dropbox_2.10.0_amd64.deb
  Size: 94296
  MD5sum: 39d2f6558a35defbb4e3346c66651da9
  SHA1: f68b9e102b96a72f37e79f74ac7030cd881db284
  SHA256: 5ddf820c1f2e2b12c7824f9691d09f204c33ec7073736891544b774f7e0a0812
  Description: cloud synchronization engine - CLI and Nautilus extension
   Dropbox is a free service that lets you bring your photos, docs, and videos
   anywhere and share them easily.
   .
   This package provides a command-line tool and a Nautilus extension that
   integrates the Dropbox web service with your GNOME Desktop.
  Homepage: https://www.dropbox.com/

  Err http://linux.dropbox.com utopic/main amd64 Packages
Bad header line

  Well. That *sort* of looks reasonable. But I looked around at some of
  the other responses in the log, and I realized, "Oh shit, these should
  be HTTP headers!"

  Answer for: http://debian.stanford.edu/ubuntu/dists/utopic/InRelease
  HTTP/1.1 404 Not Found
  Date: Wed, 21 Jan 2015 22:54:17 GMT
  Server: Apache
  Vary: Accept-Encoding
  Content-Length: 227
  Content-Type: text/html; charset=iso-8859-1

  So, why, then, does Apt think that the content is the HTTP headers? I
  was reminded of an old bug I encountered in MediaWiki:

  https://issues.apache.org/bugzilla/show_bug.cgi?id=40953
  https://bugzilla.mozilla.org/show_bug.cgi?id=363109#c12
  https://phabricator.wikimedia.org/T19537

  Checking the source, it does seem apt pipelines requests by default,
  so if it desynchronized in its processing of the HTTP stream, that
  would be bad news. Seeking back in the log, we see this:

  
  Answer for: 
http://linux.dropbox.com/ubuntu/dists/utopic/main/binary-amd64/Packages.bz2
  HTTP/1.1 404 Not Found
  Server: nginx
  Date: Wed, 21 Jan 2015 22:54:17 GMT
  Content-Type: text/html
  Content-Length: 162
  Connection: keep-alive
  Content-Range: bytes */1142

  GET /ubuntu/dists/utopic/main/binary-i386/Packages.bz2 HTTP/1.1
  Host: linux.dropbox.com
  Cache-Control: max-age=0
  Range: bytes=2635-
  If-Range: Mon, 29 Dec 2014 22:30:54 GMT
  User-Agent: Debian APT-HTTP/1.3 (1.0.9.2ubuntu2)

  
  Answer for: 
http://linux.dropbox.com/ubuntu/dists/utopic/main/binary-i386/Packages.bz2
  
  404 Not Found
  
  404 Not Found
  nginx
  
  

  Bingo.

  By the way, you won't be able to reproduce the error unless you can
  induce apt-get to send the If-Range/Range header to the server. apt-
  get only sends the header if it has some cached partial lists (which,
  BY THE WAY, are not cleared when you clear your apt cache, WHY?!) I'll
  attach some files which you can put in /var/lib/apt/lists/partial
  which, along with adding

  deb [arch=amd64,i386] http://linux.dropbox.com/ubuntu utopic main

  to your sources list, should cause you to be able to reproduce the
  error.

  For what it's worth, I also think the server is also partially to
  blame; I'm not sure but 404 doesn't seem like the right code to return
  here. I'll also attach full HTTP cache logs.

  Can forward to upstream on request. (In fact, I'll probably do it
  anyway.)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: apt 1.0.9.2ubuntu

[Touch-packages] [Bug 1393624] Re: Lock screen rejects password on Ubuntu 14.04

[LexLythius]

@bregma It does happen regardless of how many monitors I have connected.

@andyrock $ ls -l /etc/shadow
-rw-r- 1 root root 1529 oct 15 22:20 /etc/shadow

FWIW, password is hashed with CRYPT/SHA512 ($6$...), using default
number of rounds.

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

Title:
  Lock screen rejects password on Ubuntu 14.04

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

Bug description:
  Password is systematically rejected on the lock screen. However, if I
  click Switch account, the *greeter* does accept the same password.

  This issue is reproducible either by hitting the Ctrl+Alt+L shortcut key or 
by runnibg
  `gnome-screensaver-command -l`

  This happens after I upgraded from Ubuntu 12.04 to 14.04.
  I had ATI Radeon HD 3870 with open source drivers, now I have GeForce GTX 750 
Ti with NVIDIA proprietary drivers. Same thing.

  Ubuntu 14.04.1 LTS
  Linux 3.13.0-39-generic x86_64

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

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

[Touch-packages] [Bug 1400626] Re: Please backport xtrans, libdrm, x11proto-{fonts, core} packages for 14.04.2

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-branches/ubuntu/trusty/mesa-lts-utopic
/trusty-proposed

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

Title:
  Please backport xtrans, libdrm, x11proto-{fonts,core} packages for
  14.04.2

Status in libdrm package in Ubuntu:
  In Progress
Status in x11proto-core package in Ubuntu:
  New
Status in x11proto-fonts package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  In Progress
Status in xtrans package in Ubuntu:
  In Progress
Status in libdrm source package in Trusty:
  Fix Released
Status in x11proto-core source package in Trusty:
  Fix Released
Status in x11proto-fonts source package in Trusty:
  Fix Released
Status in xorg source package in Trusty:
  Fix Committed
Status in xtrans source package in Trusty:
  Fix Released

Bug description:
  In order to upload the new xorg-server we need to backport the following 
packages from utopic:
  libdrm
  x11proto-core
  x11proto-fonts
  xtrans

  libdrm 2.4.52-1->2.4.56-1 seems to have the following changes:
  - Hides private symbols from all libdrm libraries
  - fixes MSAA on Hawaii (radeon).
  - Adds cherryview pci-ids (intel).
  - Makes libdrm-nouveau threadsafe with concurrent access to the drm fd.
  - Fixes to exynos and freedreno.
  - Enables building libdrm-freedreno1 and libdrm-exynos1

  x11proto-core's main change appears to be changing from the 'pointer' type to 
'void *':
  
https://launchpadlibrarian.net/173873109/x11proto-core_7.0.24-1_7.0.26-1.diff.gz

  x11proto-fonts' main change is the same as x11proto-core, but the 
documentation is reformatted too:
  
https://launchpadlibrarian.net/173873038/x11proto-fonts_2.1.2-1_2.1.3-1.diff.gz

  xtrans seems to have 2 minor changes, increase default unix pipe size and add 
support for systemd socket activation:
  https://launchpadlibrarian.net/173873112/xtrans_1.3.2-1_1.3.4-1.diff.gz

  xorg needs to be slightly updated, to allow xserver-xorg to provide
  the unrenamed lts-utopic, and to allow xorg to be installed with the
  renamed xorg-server.

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

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

[Touch-packages] [Bug 1321309] Re: [Indicators] Missed calendar or alarm events need to be properly indicated

[Nekhelesh Ramananthan]

** Changed in: ubuntu-clock-app
Milestone: ota-1 => ota-2

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

Title:
  [Indicators] Missed calendar or alarm events need to be properly
  indicated

Status in The Date and Time Indicator:
  Confirmed
Status in Clock application for Ubuntu devices:
  Triaged
Status in Themes for Ubuntu:
  New
Status in Ubuntu UX bugs:
  Fix Committed
Status in indicator-datetime package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Imagine a scenario where you have a calendar event or a clock alarm to
  go of at 10:00. If you get a call at the same time, then obviously the
  call gets the highest priority and the alarm or calendar audible
  notification is suppressed by the system. So a phone user can actually
  miss the event.

  This can be resolved by turning the alarm icon shown in the indicator
  to blue similar to messages to indicate that an alarm or event was
  missed by the user.

  ---

  Desired solution:

  The alarm icon turns its state to active like notification
  center/messages indicator as suggested in the bug description.

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

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

[Touch-packages] [Bug 1413428] Re: apt-get's HTTP pipeline desynchronizes, hilarity ensues

[Edward Z. Yang]

** Attachment added: "apt-get update -o Debug::Acquire::http=true log"
   
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1413428/+attachment/4303390/+files/log2

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

Title:
  apt-get's HTTP pipeline desynchronizes, hilarity ensues

Status in apt package in Ubuntu:
  New

Bug description:
  tl;dr: apt-get improperly handles servers which respond 404 with HTTP
  content to a Range query, resulting in a desychronized HTTP buffer and
  hilarious bugs.

  OK, this is going to be a long one. Where to begin? I was updating my
  Aptitude packages and noticed that my Dropbox source was not updating
  correctly:

  Err http://linux.dropbox.com utopic/main amd64 Packages
Bad header line

  Silly Dropbox, not checking their package list! I report it to them,
  and they report back that the URL being fetched seems to be giving
  back a well formed HTTP response, and that they couldn't reproduce. I
  verify that is the case. We ponder the problem for a while, clearing
  caches and permuting the source.list line, and finally someone
  suggests running -o Debug::Acquire::http=true. I take the log and
  scroll to the error line:

  Answer for: 
http://linux.dropbox.com/ubuntu/dists/utopic/main/i18n/Translation-en_US.lzma
  Package: dropbox
  Priority: optional
  Section: gnome
  Installed-Size: 404
  Maintainer: Rian Hunter 
  Architecture: amd64
  Version: 2.10.0
  Replaces: nautilus-dropbox
  Provides: nautilus-dropbox
  Depends: procps, python-gtk2 (>= 2.12), python (>= 2.5), libatk1.0-0 (>= 
1.20.0), libc6 (>= 2.4), libcairo2 (>= 1.6.0), libglib2.0-0 (>= 2.16.0), 
libgtk2.0-0 (>= 2.12.0), libpango1.0-0 (>= 1.20.1)
  Suggests: nautilus (>= 2.16.0), python-gpgme (>= 0.1)
  Breaks: nautilus-dropbox
  Filename: pool/main/dropbox_2.10.0_amd64.deb
  Size: 94296
  MD5sum: 39d2f6558a35defbb4e3346c66651da9
  SHA1: f68b9e102b96a72f37e79f74ac7030cd881db284
  SHA256: 5ddf820c1f2e2b12c7824f9691d09f204c33ec7073736891544b774f7e0a0812
  Description: cloud synchronization engine - CLI and Nautilus extension
   Dropbox is a free service that lets you bring your photos, docs, and videos
   anywhere and share them easily.
   .
   This package provides a command-line tool and a Nautilus extension that
   integrates the Dropbox web service with your GNOME Desktop.
  Homepage: https://www.dropbox.com/

  Err http://linux.dropbox.com utopic/main amd64 Packages
Bad header line

  Well. That *sort* of looks reasonable. But I looked around at some of
  the other responses in the log, and I realized, "Oh shit, these should
  be HTTP headers!"

  Answer for: http://debian.stanford.edu/ubuntu/dists/utopic/InRelease
  HTTP/1.1 404 Not Found
  Date: Wed, 21 Jan 2015 22:54:17 GMT
  Server: Apache
  Vary: Accept-Encoding
  Content-Length: 227
  Content-Type: text/html; charset=iso-8859-1

  So, why, then, does Apt think that the content is the HTTP headers? I
  was reminded of an old bug I encountered in MediaWiki:

  https://issues.apache.org/bugzilla/show_bug.cgi?id=40953
  https://bugzilla.mozilla.org/show_bug.cgi?id=363109#c12
  https://phabricator.wikimedia.org/T19537

  Checking the source, it does seem apt pipelines requests by default,
  so if it desynchronized in its processing of the HTTP stream, that
  would be bad news. Seeking back in the log, we see this:

  
  Answer for: 
http://linux.dropbox.com/ubuntu/dists/utopic/main/binary-amd64/Packages.bz2
  HTTP/1.1 404 Not Found
  Server: nginx
  Date: Wed, 21 Jan 2015 22:54:17 GMT
  Content-Type: text/html
  Content-Length: 162
  Connection: keep-alive
  Content-Range: bytes */1142

  GET /ubuntu/dists/utopic/main/binary-i386/Packages.bz2 HTTP/1.1
  Host: linux.dropbox.com
  Cache-Control: max-age=0
  Range: bytes=2635-
  If-Range: Mon, 29 Dec 2014 22:30:54 GMT
  User-Agent: Debian APT-HTTP/1.3 (1.0.9.2ubuntu2)

  
  Answer for: 
http://linux.dropbox.com/ubuntu/dists/utopic/main/binary-i386/Packages.bz2
  
  404 Not Found
  
  404 Not Found
  nginx
  
  

  Bingo.

  By the way, you won't be able to reproduce the error unless you can
  induce apt-get to send the If-Range/Range header to the server. apt-
  get only sends the header if it has some cached partial lists (which,
  BY THE WAY, are not cleared when you clear your apt cache, WHY?!) I'll
  attach some files which you can put in /var/lib/apt/lists/partial
  which, along with adding

  deb [arch=amd64,i386] http://linux.dropbox.com/ubuntu utopic main

  to your sources list, should cause you to be able to reproduce the
  error.

  For what it's worth, I also think the server is also partially to
  blame; I'm not sure but 404 doesn't seem like the right code to return
  here. I'll also attach full HTTP cache logs.

  Can forward to upstream on request. (In fact, I'll probably do it
  anyway.)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: apt 

[Touch-packages] [Bug 1413428] Re: apt-get's HTTP pipeline desynchronizes, hilarity ensues

[Edward Z. Yang]

** Attachment added: 
"linux.dropbox.com_ubuntu_dists_utopic_main_i18n_Translation-en%5fUS.gz"
   
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1413428/+attachment/4303389/+files/linux.dropbox.com_ubuntu_dists_utopic_main_i18n_Translation-en%255fUS.gz

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

Title:
  apt-get's HTTP pipeline desynchronizes, hilarity ensues

Status in apt package in Ubuntu:
  New

Bug description:
  tl;dr: apt-get improperly handles servers which respond 404 with HTTP
  content to a Range query, resulting in a desychronized HTTP buffer and
  hilarious bugs.

  OK, this is going to be a long one. Where to begin? I was updating my
  Aptitude packages and noticed that my Dropbox source was not updating
  correctly:

  Err http://linux.dropbox.com utopic/main amd64 Packages
Bad header line

  Silly Dropbox, not checking their package list! I report it to them,
  and they report back that the URL being fetched seems to be giving
  back a well formed HTTP response, and that they couldn't reproduce. I
  verify that is the case. We ponder the problem for a while, clearing
  caches and permuting the source.list line, and finally someone
  suggests running -o Debug::Acquire::http=true. I take the log and
  scroll to the error line:

  Answer for: 
http://linux.dropbox.com/ubuntu/dists/utopic/main/i18n/Translation-en_US.lzma
  Package: dropbox
  Priority: optional
  Section: gnome
  Installed-Size: 404
  Maintainer: Rian Hunter 
  Architecture: amd64
  Version: 2.10.0
  Replaces: nautilus-dropbox
  Provides: nautilus-dropbox
  Depends: procps, python-gtk2 (>= 2.12), python (>= 2.5), libatk1.0-0 (>= 
1.20.0), libc6 (>= 2.4), libcairo2 (>= 1.6.0), libglib2.0-0 (>= 2.16.0), 
libgtk2.0-0 (>= 2.12.0), libpango1.0-0 (>= 1.20.1)
  Suggests: nautilus (>= 2.16.0), python-gpgme (>= 0.1)
  Breaks: nautilus-dropbox
  Filename: pool/main/dropbox_2.10.0_amd64.deb
  Size: 94296
  MD5sum: 39d2f6558a35defbb4e3346c66651da9
  SHA1: f68b9e102b96a72f37e79f74ac7030cd881db284
  SHA256: 5ddf820c1f2e2b12c7824f9691d09f204c33ec7073736891544b774f7e0a0812
  Description: cloud synchronization engine - CLI and Nautilus extension
   Dropbox is a free service that lets you bring your photos, docs, and videos
   anywhere and share them easily.
   .
   This package provides a command-line tool and a Nautilus extension that
   integrates the Dropbox web service with your GNOME Desktop.
  Homepage: https://www.dropbox.com/

  Err http://linux.dropbox.com utopic/main amd64 Packages
Bad header line

  Well. That *sort* of looks reasonable. But I looked around at some of
  the other responses in the log, and I realized, "Oh shit, these should
  be HTTP headers!"

  Answer for: http://debian.stanford.edu/ubuntu/dists/utopic/InRelease
  HTTP/1.1 404 Not Found
  Date: Wed, 21 Jan 2015 22:54:17 GMT
  Server: Apache
  Vary: Accept-Encoding
  Content-Length: 227
  Content-Type: text/html; charset=iso-8859-1

  So, why, then, does Apt think that the content is the HTTP headers? I
  was reminded of an old bug I encountered in MediaWiki:

  https://issues.apache.org/bugzilla/show_bug.cgi?id=40953
  https://bugzilla.mozilla.org/show_bug.cgi?id=363109#c12
  https://phabricator.wikimedia.org/T19537

  Checking the source, it does seem apt pipelines requests by default,
  so if it desynchronized in its processing of the HTTP stream, that
  would be bad news. Seeking back in the log, we see this:

  
  Answer for: 
http://linux.dropbox.com/ubuntu/dists/utopic/main/binary-amd64/Packages.bz2
  HTTP/1.1 404 Not Found
  Server: nginx
  Date: Wed, 21 Jan 2015 22:54:17 GMT
  Content-Type: text/html
  Content-Length: 162
  Connection: keep-alive
  Content-Range: bytes */1142

  GET /ubuntu/dists/utopic/main/binary-i386/Packages.bz2 HTTP/1.1
  Host: linux.dropbox.com
  Cache-Control: max-age=0
  Range: bytes=2635-
  If-Range: Mon, 29 Dec 2014 22:30:54 GMT
  User-Agent: Debian APT-HTTP/1.3 (1.0.9.2ubuntu2)

  
  Answer for: 
http://linux.dropbox.com/ubuntu/dists/utopic/main/binary-i386/Packages.bz2
  
  404 Not Found
  
  404 Not Found
  nginx
  
  

  Bingo.

  By the way, you won't be able to reproduce the error unless you can
  induce apt-get to send the If-Range/Range header to the server. apt-
  get only sends the header if it has some cached partial lists (which,
  BY THE WAY, are not cleared when you clear your apt cache, WHY?!) I'll
  attach some files which you can put in /var/lib/apt/lists/partial
  which, along with adding

  deb [arch=amd64,i386] http://linux.dropbox.com/ubuntu utopic main

  to your sources list, should cause you to be able to reproduce the
  error.

  For what it's worth, I also think the server is also partially to
  blame; I'm not sure but 404 doesn't seem like the right code to return
  here. I'll also attach full HTTP cache logs.

  Can forward to upstream on request. (In fact, I'll

[Touch-packages] [Bug 1413428] Re: apt-get's HTTP pipeline desynchronizes, hilarity ensues

[Edward Z. Yang]

** Attachment added: 
"linux.dropbox.com_ubuntu_dists_utopic_main_binary-i386_Packages.bz2"
   
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1413428/+attachment/4303387/+files/linux.dropbox.com_ubuntu_dists_utopic_main_binary-i386_Packages.bz2

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

Title:
  apt-get's HTTP pipeline desynchronizes, hilarity ensues

Status in apt package in Ubuntu:
  New

Bug description:
  tl;dr: apt-get improperly handles servers which respond 404 with HTTP
  content to a Range query, resulting in a desychronized HTTP buffer and
  hilarious bugs.

  OK, this is going to be a long one. Where to begin? I was updating my
  Aptitude packages and noticed that my Dropbox source was not updating
  correctly:

  Err http://linux.dropbox.com utopic/main amd64 Packages
Bad header line

  Silly Dropbox, not checking their package list! I report it to them,
  and they report back that the URL being fetched seems to be giving
  back a well formed HTTP response, and that they couldn't reproduce. I
  verify that is the case. We ponder the problem for a while, clearing
  caches and permuting the source.list line, and finally someone
  suggests running -o Debug::Acquire::http=true. I take the log and
  scroll to the error line:

  Answer for: 
http://linux.dropbox.com/ubuntu/dists/utopic/main/i18n/Translation-en_US.lzma
  Package: dropbox
  Priority: optional
  Section: gnome
  Installed-Size: 404
  Maintainer: Rian Hunter 
  Architecture: amd64
  Version: 2.10.0
  Replaces: nautilus-dropbox
  Provides: nautilus-dropbox
  Depends: procps, python-gtk2 (>= 2.12), python (>= 2.5), libatk1.0-0 (>= 
1.20.0), libc6 (>= 2.4), libcairo2 (>= 1.6.0), libglib2.0-0 (>= 2.16.0), 
libgtk2.0-0 (>= 2.12.0), libpango1.0-0 (>= 1.20.1)
  Suggests: nautilus (>= 2.16.0), python-gpgme (>= 0.1)
  Breaks: nautilus-dropbox
  Filename: pool/main/dropbox_2.10.0_amd64.deb
  Size: 94296
  MD5sum: 39d2f6558a35defbb4e3346c66651da9
  SHA1: f68b9e102b96a72f37e79f74ac7030cd881db284
  SHA256: 5ddf820c1f2e2b12c7824f9691d09f204c33ec7073736891544b774f7e0a0812
  Description: cloud synchronization engine - CLI and Nautilus extension
   Dropbox is a free service that lets you bring your photos, docs, and videos
   anywhere and share them easily.
   .
   This package provides a command-line tool and a Nautilus extension that
   integrates the Dropbox web service with your GNOME Desktop.
  Homepage: https://www.dropbox.com/

  Err http://linux.dropbox.com utopic/main amd64 Packages
Bad header line

  Well. That *sort* of looks reasonable. But I looked around at some of
  the other responses in the log, and I realized, "Oh shit, these should
  be HTTP headers!"

  Answer for: http://debian.stanford.edu/ubuntu/dists/utopic/InRelease
  HTTP/1.1 404 Not Found
  Date: Wed, 21 Jan 2015 22:54:17 GMT
  Server: Apache
  Vary: Accept-Encoding
  Content-Length: 227
  Content-Type: text/html; charset=iso-8859-1

  So, why, then, does Apt think that the content is the HTTP headers? I
  was reminded of an old bug I encountered in MediaWiki:

  https://issues.apache.org/bugzilla/show_bug.cgi?id=40953
  https://bugzilla.mozilla.org/show_bug.cgi?id=363109#c12
  https://phabricator.wikimedia.org/T19537

  Checking the source, it does seem apt pipelines requests by default,
  so if it desynchronized in its processing of the HTTP stream, that
  would be bad news. Seeking back in the log, we see this:

  
  Answer for: 
http://linux.dropbox.com/ubuntu/dists/utopic/main/binary-amd64/Packages.bz2
  HTTP/1.1 404 Not Found
  Server: nginx
  Date: Wed, 21 Jan 2015 22:54:17 GMT
  Content-Type: text/html
  Content-Length: 162
  Connection: keep-alive
  Content-Range: bytes */1142

  GET /ubuntu/dists/utopic/main/binary-i386/Packages.bz2 HTTP/1.1
  Host: linux.dropbox.com
  Cache-Control: max-age=0
  Range: bytes=2635-
  If-Range: Mon, 29 Dec 2014 22:30:54 GMT
  User-Agent: Debian APT-HTTP/1.3 (1.0.9.2ubuntu2)

  
  Answer for: 
http://linux.dropbox.com/ubuntu/dists/utopic/main/binary-i386/Packages.bz2
  
  404 Not Found
  
  404 Not Found
  nginx
  
  

  Bingo.

  By the way, you won't be able to reproduce the error unless you can
  induce apt-get to send the If-Range/Range header to the server. apt-
  get only sends the header if it has some cached partial lists (which,
  BY THE WAY, are not cleared when you clear your apt cache, WHY?!) I'll
  attach some files which you can put in /var/lib/apt/lists/partial
  which, along with adding

  deb [arch=amd64,i386] http://linux.dropbox.com/ubuntu utopic main

  to your sources list, should cause you to be able to reproduce the
  error.

  For what it's worth, I also think the server is also partially to
  blame; I'm not sure but 404 doesn't seem like the right code to return
  here. I'll also attach full HTTP cache logs.

  Can forward to upstream on request. (In fact, I'll probabl

[Touch-packages] [Bug 1413428] Re: apt-get's HTTP pipeline desynchronizes, hilarity ensues

[Edward Z. Yang]

** Attachment added: 
"linux.dropbox.com_ubuntu_dists_utopic_main_binary-i386_Packages.gz"
   
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1413428/+attachment/4303388/+files/linux.dropbox.com_ubuntu_dists_utopic_main_binary-i386_Packages.gz

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

Title:
  apt-get's HTTP pipeline desynchronizes, hilarity ensues

Status in apt package in Ubuntu:
  New

Bug description:
  tl;dr: apt-get improperly handles servers which respond 404 with HTTP
  content to a Range query, resulting in a desychronized HTTP buffer and
  hilarious bugs.

  OK, this is going to be a long one. Where to begin? I was updating my
  Aptitude packages and noticed that my Dropbox source was not updating
  correctly:

  Err http://linux.dropbox.com utopic/main amd64 Packages
Bad header line

  Silly Dropbox, not checking their package list! I report it to them,
  and they report back that the URL being fetched seems to be giving
  back a well formed HTTP response, and that they couldn't reproduce. I
  verify that is the case. We ponder the problem for a while, clearing
  caches and permuting the source.list line, and finally someone
  suggests running -o Debug::Acquire::http=true. I take the log and
  scroll to the error line:

  Answer for: 
http://linux.dropbox.com/ubuntu/dists/utopic/main/i18n/Translation-en_US.lzma
  Package: dropbox
  Priority: optional
  Section: gnome
  Installed-Size: 404
  Maintainer: Rian Hunter 
  Architecture: amd64
  Version: 2.10.0
  Replaces: nautilus-dropbox
  Provides: nautilus-dropbox
  Depends: procps, python-gtk2 (>= 2.12), python (>= 2.5), libatk1.0-0 (>= 
1.20.0), libc6 (>= 2.4), libcairo2 (>= 1.6.0), libglib2.0-0 (>= 2.16.0), 
libgtk2.0-0 (>= 2.12.0), libpango1.0-0 (>= 1.20.1)
  Suggests: nautilus (>= 2.16.0), python-gpgme (>= 0.1)
  Breaks: nautilus-dropbox
  Filename: pool/main/dropbox_2.10.0_amd64.deb
  Size: 94296
  MD5sum: 39d2f6558a35defbb4e3346c66651da9
  SHA1: f68b9e102b96a72f37e79f74ac7030cd881db284
  SHA256: 5ddf820c1f2e2b12c7824f9691d09f204c33ec7073736891544b774f7e0a0812
  Description: cloud synchronization engine - CLI and Nautilus extension
   Dropbox is a free service that lets you bring your photos, docs, and videos
   anywhere and share them easily.
   .
   This package provides a command-line tool and a Nautilus extension that
   integrates the Dropbox web service with your GNOME Desktop.
  Homepage: https://www.dropbox.com/

  Err http://linux.dropbox.com utopic/main amd64 Packages
Bad header line

  Well. That *sort* of looks reasonable. But I looked around at some of
  the other responses in the log, and I realized, "Oh shit, these should
  be HTTP headers!"

  Answer for: http://debian.stanford.edu/ubuntu/dists/utopic/InRelease
  HTTP/1.1 404 Not Found
  Date: Wed, 21 Jan 2015 22:54:17 GMT
  Server: Apache
  Vary: Accept-Encoding
  Content-Length: 227
  Content-Type: text/html; charset=iso-8859-1

  So, why, then, does Apt think that the content is the HTTP headers? I
  was reminded of an old bug I encountered in MediaWiki:

  https://issues.apache.org/bugzilla/show_bug.cgi?id=40953
  https://bugzilla.mozilla.org/show_bug.cgi?id=363109#c12
  https://phabricator.wikimedia.org/T19537

  Checking the source, it does seem apt pipelines requests by default,
  so if it desynchronized in its processing of the HTTP stream, that
  would be bad news. Seeking back in the log, we see this:

  
  Answer for: 
http://linux.dropbox.com/ubuntu/dists/utopic/main/binary-amd64/Packages.bz2
  HTTP/1.1 404 Not Found
  Server: nginx
  Date: Wed, 21 Jan 2015 22:54:17 GMT
  Content-Type: text/html
  Content-Length: 162
  Connection: keep-alive
  Content-Range: bytes */1142

  GET /ubuntu/dists/utopic/main/binary-i386/Packages.bz2 HTTP/1.1
  Host: linux.dropbox.com
  Cache-Control: max-age=0
  Range: bytes=2635-
  If-Range: Mon, 29 Dec 2014 22:30:54 GMT
  User-Agent: Debian APT-HTTP/1.3 (1.0.9.2ubuntu2)

  
  Answer for: 
http://linux.dropbox.com/ubuntu/dists/utopic/main/binary-i386/Packages.bz2
  
  404 Not Found
  
  404 Not Found
  nginx
  
  

  Bingo.

  By the way, you won't be able to reproduce the error unless you can
  induce apt-get to send the If-Range/Range header to the server. apt-
  get only sends the header if it has some cached partial lists (which,
  BY THE WAY, are not cleared when you clear your apt cache, WHY?!) I'll
  attach some files which you can put in /var/lib/apt/lists/partial
  which, along with adding

  deb [arch=amd64,i386] http://linux.dropbox.com/ubuntu utopic main

  to your sources list, should cause you to be able to reproduce the
  error.

  For what it's worth, I also think the server is also partially to
  blame; I'm not sure but 404 doesn't seem like the right code to return
  here. I'll also attach full HTTP cache logs.

  Can forward to upstream on request. (In fact, I'll probably 

[Touch-packages] [Bug 1413428] [NEW] apt-get's HTTP pipeline desynchronizes, hilarity ensues

[Edward Z. Yang]

Public bug reported:

tl;dr: apt-get improperly handles servers which respond 404 with HTTP
content to a Range query, resulting in a desychronized HTTP buffer and
hilarious bugs.

OK, this is going to be a long one. Where to begin? I was updating my
Aptitude packages and noticed that my Dropbox source was not updating
correctly:

Err http://linux.dropbox.com utopic/main amd64 Packages
  Bad header line

Silly Dropbox, not checking their package list! I report it to them, and
they report back that the URL being fetched seems to be giving back a
well formed HTTP response, and that they couldn't reproduce. I verify
that is the case. We ponder the problem for a while, clearing caches and
permuting the source.list line, and finally someone suggests running -o
Debug::Acquire::http=true. I take the log and scroll to the error line:

Answer for: 
http://linux.dropbox.com/ubuntu/dists/utopic/main/i18n/Translation-en_US.lzma
Package: dropbox
Priority: optional
Section: gnome
Installed-Size: 404
Maintainer: Rian Hunter 
Architecture: amd64
Version: 2.10.0
Replaces: nautilus-dropbox
Provides: nautilus-dropbox
Depends: procps, python-gtk2 (>= 2.12), python (>= 2.5), libatk1.0-0 (>= 
1.20.0), libc6 (>= 2.4), libcairo2 (>= 1.6.0), libglib2.0-0 (>= 2.16.0), 
libgtk2.0-0 (>= 2.12.0), libpango1.0-0 (>= 1.20.1)
Suggests: nautilus (>= 2.16.0), python-gpgme (>= 0.1)
Breaks: nautilus-dropbox
Filename: pool/main/dropbox_2.10.0_amd64.deb
Size: 94296
MD5sum: 39d2f6558a35defbb4e3346c66651da9
SHA1: f68b9e102b96a72f37e79f74ac7030cd881db284
SHA256: 5ddf820c1f2e2b12c7824f9691d09f204c33ec7073736891544b774f7e0a0812
Description: cloud synchronization engine - CLI and Nautilus extension
 Dropbox is a free service that lets you bring your photos, docs, and videos
 anywhere and share them easily.
 .
 This package provides a command-line tool and a Nautilus extension that
 integrates the Dropbox web service with your GNOME Desktop.
Homepage: https://www.dropbox.com/

Err http://linux.dropbox.com utopic/main amd64 Packages
  Bad header line

Well. That *sort* of looks reasonable. But I looked around at some of
the other responses in the log, and I realized, "Oh shit, these should
be HTTP headers!"

Answer for: http://debian.stanford.edu/ubuntu/dists/utopic/InRelease
HTTP/1.1 404 Not Found
Date: Wed, 21 Jan 2015 22:54:17 GMT
Server: Apache
Vary: Accept-Encoding
Content-Length: 227
Content-Type: text/html; charset=iso-8859-1

So, why, then, does Apt think that the content is the HTTP headers? I
was reminded of an old bug I encountered in MediaWiki:

https://issues.apache.org/bugzilla/show_bug.cgi?id=40953
https://bugzilla.mozilla.org/show_bug.cgi?id=363109#c12
https://phabricator.wikimedia.org/T19537

Checking the source, it does seem apt pipelines requests by default, so
if it desynchronized in its processing of the HTTP stream, that would be
bad news. Seeking back in the log, we see this:


Answer for: 
http://linux.dropbox.com/ubuntu/dists/utopic/main/binary-amd64/Packages.bz2
HTTP/1.1 404 Not Found
Server: nginx
Date: Wed, 21 Jan 2015 22:54:17 GMT
Content-Type: text/html
Content-Length: 162
Connection: keep-alive
Content-Range: bytes */1142

GET /ubuntu/dists/utopic/main/binary-i386/Packages.bz2 HTTP/1.1
Host: linux.dropbox.com
Cache-Control: max-age=0
Range: bytes=2635-
If-Range: Mon, 29 Dec 2014 22:30:54 GMT
User-Agent: Debian APT-HTTP/1.3 (1.0.9.2ubuntu2)


Answer for: 
http://linux.dropbox.com/ubuntu/dists/utopic/main/binary-i386/Packages.bz2

404 Not Found

404 Not Found
nginx



Bingo.

By the way, you won't be able to reproduce the error unless you can
induce apt-get to send the If-Range/Range header to the server. apt-get
only sends the header if it has some cached partial lists (which, BY THE
WAY, are not cleared when you clear your apt cache, WHY?!) I'll attach
some files which you can put in /var/lib/apt/lists/partial which, along
with adding

deb [arch=amd64,i386] http://linux.dropbox.com/ubuntu utopic main

to your sources list, should cause you to be able to reproduce the
error.

For what it's worth, I also think the server is also partially to blame;
I'm not sure but 404 doesn't seem like the right code to return here.
I'll also attach full HTTP cache logs.

Can forward to upstream on request. (In fact, I'll probably do it
anyway.)

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: apt 1.0.9.2ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
Uname: Linux 3.16.0-28-generic x86_64
NonfreeKernelModules: openafs
ApportVersion: 2.14.7-0ubuntu8.1
Architecture: amd64
Date: Wed Jan 21 15:27:02 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-11-21 (426 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
SourcePackage: apt
UpgradeStatus: Upgraded to utopic on 2014-12-04 (48 days ago)

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


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

** Attachment added: 
"linux.dropbox.com_ubuntu_dist

[Touch-packages] [Bug 1410830] Re: Shutdown dialog appears on resume, after a long delay in screen turning on

[Launchpad Bug Tracker]

This bug was fixed in the package unity8 -
8.02+15.04.20150121.2-0ubuntu1

---
unity8 (8.02+15.04.20150121.2-0ubuntu1) vivid; urgency=low

  [ Michael Terry ]
  * Don't show any power dialogs while the screen is off. This is a
band-aid to avoid the symptom, while we still investigate the source
of why the screen doesn't turn on (and why we seem to not handle the
power-button-release event). (LP: #1409003, #1410830)
  * Don't refocus the dialer-app when a call is started by the user.
Because of how qtmir works, this would cause the dialer-app to
unfocus momentarily, causing interface oddities for the user. (LP:
#1413065)

  [ CI Train Bot ]
  * Resync trunk

  [ Albert Astals Cid ]
  * Build with ninja
  * Fixes for Table Preview Widget (LP: #1410420)

  [ Michael Zanetti ]
  * Add support for earpiece media buttons (LP: #1398427)
  * Add a WindowMoveResizeArea and tests for it
 -- Ubuntu daily releaseWed, 21 Jan 2015 
18:33:18 +

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

Title:
  Shutdown dialog appears on resume, after a long delay in screen
  turning on

Status in the base for Ubuntu mobile products:
  In Progress
Status in unity8 package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  Sometimes, if you press the power button to resume your device, the
  screen will stay black for a long time.  When it does come on again,
  the shutdown dialog is likely showing instead of the greeter.

  You might press the power button again while the screen is black,
  thinking you didn't actually press it the first time.  This will
  immediately turn the screen on and then off again.  At which point a
  third power button press will turn the screen on for good.

  This bug is very similar to bug 1383277 (fixed), which involves a
  shutdown dialog appearing on resume, but for a different reason.  This
  is also very similar to (and may be a dup of) bug 1409003.  But since
  bug 1409003 currently involves an incoming text and this bug does not,
  I'm treating them as separate for now.

  This bug is hard to reproduce.  It seems to involve leaving and
  entering wifi/3G zones (or maybe simply toggling the wifi indicator
  button).  But no reliable steps have been recorded yet.

  I'm guessing that like bug 1383277, it involves some resume-event
  handler blocking the input stack so that Qt doesn't notice the power-
  button-release event.  And since it takes so long to resume, Qt thinks
  the user held down the power button long enough to trigger the
  shutdown dialog.

  A trivial band-aid for this is to not start the shutdown-dialog timer
  if the screen is off.  But that wouldn't address the source cause of a
  blocking event handler.  So I think this still merits investigation.
  But if this is a critical/time-sensitive bug, we could slap a band-aid
  on it.

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

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

[Touch-packages] [Bug 1409003] Re: receiving an sms while roaming and suspended renders the phone difficult to use on resume

[Launchpad Bug Tracker]

This bug was fixed in the package unity8 -
8.02+15.04.20150121.2-0ubuntu1

---
unity8 (8.02+15.04.20150121.2-0ubuntu1) vivid; urgency=low

  [ Michael Terry ]
  * Don't show any power dialogs while the screen is off. This is a
band-aid to avoid the symptom, while we still investigate the source
of why the screen doesn't turn on (and why we seem to not handle the
power-button-release event). (LP: #1409003, #1410830)
  * Don't refocus the dialer-app when a call is started by the user.
Because of how qtmir works, this would cause the dialer-app to
unfocus momentarily, causing interface oddities for the user. (LP:
#1413065)

  [ CI Train Bot ]
  * Resync trunk

  [ Albert Astals Cid ]
  * Build with ninja
  * Fixes for Table Preview Widget (LP: #1410420)

  [ Michael Zanetti ]
  * Add support for earpiece media buttons (LP: #1398427)
  * Add a WindowMoveResizeArea and tests for it
 -- Ubuntu daily releaseWed, 21 Jan 2015 
18:33:18 +

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

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

Title:
  receiving an sms while roaming and suspended renders the phone
  difficult to use on resume

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Ubuntu system image (server/client/updater):
  New
Status in unity8 package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  3 times in a row this happened
   1. I left my apartment or co-working space, so I was "roaming" on data
   2. my phone was suspended
   3. I received a text message (sms, etc...) while the phone was suspended
   4. when I turned on the phone, I had trouble getting past the shutdown 
dialog, twice I had to reboot

  This is r186 with silo 7 and silo 3 installed

  After reflashing and updating to r190, I can no longer repro

  Repro steps:
  1. Be connected to a known wireless access point (at your home or office for 
example)
  2. unplug your phone from computer or power 
  3. use power button to suspend your phone
  4. move far enough away from your known AP so that you phone could not see it 
  5. wake the phone and interact long enough that it switches to cell data (for 
me this is always edge because krillin in the US)
  6. suspend your phone again
  7. receive a text message and try to wake your phone

  Result: The shutdown dialog appears, and you cannot get past it.
  Sometimes the phone settles after a few tries and become usable,
  sometimes a hard reboot is required

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

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

[Touch-packages] [Bug 1410420] Re: [dash] preview table runs off right side

[Launchpad Bug Tracker]

This bug was fixed in the package unity8 -
8.02+15.04.20150121.2-0ubuntu1

---
unity8 (8.02+15.04.20150121.2-0ubuntu1) vivid; urgency=low

  [ Michael Terry ]
  * Don't show any power dialogs while the screen is off. This is a
band-aid to avoid the symptom, while we still investigate the source
of why the screen doesn't turn on (and why we seem to not handle the
power-button-release event). (LP: #1409003, #1410830)
  * Don't refocus the dialer-app when a call is started by the user.
Because of how qtmir works, this would cause the dialer-app to
unfocus momentarily, causing interface oddities for the user. (LP:
#1413065)

  [ CI Train Bot ]
  * Resync trunk

  [ Albert Astals Cid ]
  * Build with ninja
  * Fixes for Table Preview Widget (LP: #1410420)

  [ Michael Zanetti ]
  * Add support for earpiece media buttons (LP: #1398427)
  * Add a WindowMoveResizeArea and tests for it
 -- Ubuntu daily releaseWed, 21 Jan 2015 
18:33:18 +

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

Title:
  [dash] preview table runs off right side

Status in Ubuntu UX bugs:
  Fix Committed
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  I see a preview table running off the right side of the preview.

  See attached.

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

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

[Touch-packages] [Bug 1398427] Re: [dialer] + [sound] Can't use earphone to answer or disconnect a call

[Launchpad Bug Tracker]

This bug was fixed in the package unity8 -
8.02+15.04.20150121.2-0ubuntu1

---
unity8 (8.02+15.04.20150121.2-0ubuntu1) vivid; urgency=low

  [ Michael Terry ]
  * Don't show any power dialogs while the screen is off. This is a
band-aid to avoid the symptom, while we still investigate the source
of why the screen doesn't turn on (and why we seem to not handle the
power-button-release event). (LP: #1409003, #1410830)
  * Don't refocus the dialer-app when a call is started by the user.
Because of how qtmir works, this would cause the dialer-app to
unfocus momentarily, causing interface oddities for the user. (LP:
#1413065)

  [ CI Train Bot ]
  * Resync trunk

  [ Albert Astals Cid ]
  * Build with ninja
  * Fixes for Table Preview Widget (LP: #1410420)

  [ Michael Zanetti ]
  * Add support for earpiece media buttons (LP: #1398427)
  * Add a WindowMoveResizeArea and tests for it
 -- Ubuntu daily releaseWed, 21 Jan 2015 
18:33:18 +

** Changed in: unity8 (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 telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1398427

Title:
  [dialer] + [sound] Can't use earphone to answer or disconnect a call

Status in the base for Ubuntu mobile products:
  In Progress
Status in Telephony Service:
  New
Status in Ubuntu UX bugs:
  Triaged
Status in qtmir package in Ubuntu:
  Fix Released
Status in telephony-service package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu RTM:
  Fix Released
Status in telephony-service package in Ubuntu RTM:
  In Progress
Status in unity8 package in Ubuntu RTM:
  Triaged

Bug description:
  [Procedures]
  1.insert the earphone
  2.make a MO call to DUT
  3.use the Hook key to answer the call
  4.when connected the call use the hook key to disconnect the call

  [Expect results]
  earphone hook key can answer and disconnect the call
  [Actual results]
  can't answer and disconnect the call

  [Reproduce]
  Always

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

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

[Touch-packages] [Bug 1413065] Re: [Call]The call interface sometimes disappears when making emergency call

[Launchpad Bug Tracker]

This bug was fixed in the package unity8 -
8.02+15.04.20150121.2-0ubuntu1

---
unity8 (8.02+15.04.20150121.2-0ubuntu1) vivid; urgency=low

  [ Michael Terry ]
  * Don't show any power dialogs while the screen is off. This is a
band-aid to avoid the symptom, while we still investigate the source
of why the screen doesn't turn on (and why we seem to not handle the
power-button-release event). (LP: #1409003, #1410830)
  * Don't refocus the dialer-app when a call is started by the user.
Because of how qtmir works, this would cause the dialer-app to
unfocus momentarily, causing interface oddities for the user. (LP:
#1413065)

  [ CI Train Bot ]
  * Resync trunk

  [ Albert Astals Cid ]
  * Build with ninja
  * Fixes for Table Preview Widget (LP: #1410420)

  [ Michael Zanetti ]
  * Add support for earpiece media buttons (LP: #1398427)
  * Add a WindowMoveResizeArea and tests for it
 -- Ubuntu daily releaseWed, 21 Jan 2015 
18:33:18 +

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

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

Title:
  [Call]The call interface sometimes disappears when making emergency
  call

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Dialer app for Ubuntu Touch:
  Invalid
Status in unity8 package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  This is the public version of the following bug:
  https://bugs.launchpad.net/barajas/+bug/1393641

  After debugging seems the issue is that the application is getting
  deactivated and then activated (via Qt.application.active) when making
  a call in greeter (emergency) mode. This is causing problems for the
  app as it pops pages when it gets deactivated and causes the bug
  sometimes. The underlying problem is that this signal should not be
  occuring when the app is clearly in the foreground. It doesn't happen
  when not in greeter mode.

  An easy way to test is to install telepathy-ofono deb which is
  attached and set a fake emergency number to allow you to dial a normal
  number in emergency mode to help test by running this command at the
  shell:

  mc-tool set ofono/ofono/account0
  string:fakeEmergencyNumber=

  Then adding console.log() to the applicationActive signal in dialer-
  app.qml will verify. When pressing the call button the app is
  deactivated then reactivated.

  Steps to reproduce:
  1) install attached telephathy-ofono deb and reboot
  2) run
  mc-tool set ofono/ofono/account0 string:fakeEmergencyNumber=
  and then follow secondary instructions (if any)
  3) lock phone
  4) press emergency call button
  5) dial  which will be a fake emergency call
  6) press the call button
  7) sometimes you will see a blank Emergency Call page after you press the 
call button, and when it works you will see the live call page
  8) adding debug to dialer-app.qml will show the active=false then active=true 
behavior after performing step 6.

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

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

[Touch-packages] [Bug 1282392] Re: nothing listens to keyringError signal

[Launchpad Bug Tracker]

** Branch linked: lp:~dobey/ubuntuone-credentials/announce-errors-rtm

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

Title:
  nothing listens to keyringError signal

Status in the base for Ubuntu mobile products:
  Confirmed
Status in ubuntuone-credentials package in Ubuntu:
  Fix Released
Status in ubuntuone-credentials package in Ubuntu RTM:
  Triaged

Bug description:
  several places in keyring.cpp emit keyringError, which is not listened
  to by ssoservice.

  It should be listened to and forwarded as an error to the client of
  ssoservice.

  I noticed this after the following UOA errors:

  2014-02-19 21:33:54,704 - DEBUG - after startDownload in run() 
  2014-02-19 21:33:54,704 - DEBUG - findToken(): Using Ubuntu One account ' 215 
'. 
  2014-02-19 21:33:54,705 - DEBUG - ../../../../lib/SignOn/identityimpl.cpp 96 
updateState Updating state:  "PendingRegistration" 
SignOn::IdentityImpl(0x42e8ab98) 
  2014-02-19 21:33:54,706 - DEBUG - ../../../../lib/SignOn/authsessionimpl.cpp 
94 initInterface 
  2014-02-19 21:33:54,706 - DEBUG - ../../../../lib/SignOn/authsessionimpl.cpp 
94 initInterface 
  2014-02-19 21:33:54,708 - DEBUG - ../../../../lib/SignOn/identityimpl.cpp 96 
updateState Updating state:  "Ready" SignOn::IdentityImpl(0x42e8ab98) 
  2014-02-19 21:33:54,780 - DEBUG - ../../../../lib/SignOn/authsessionimpl.cpp 
184 errorSlot 
QDBusError("com.google.code.AccountsSSO.SingleSignOn.Error.UserInteraction", 
"userActionFinished error: 10") 
  2014-02-19 21:33:54,780 - CRITICAL - Error: "userActionFinished error: 10" 

  
  Note the final CRITICAL line, that comes from keyring.cpp's keyringError 
function.

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

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

[Touch-packages] [Bug 1413410] Re: Unable to match unix bind rule

[Jamie Strandboge]

** Description changed:

  On Ubuntu 14.10, I had this in my logs:
  Jan 21 16:32:30 localhost kernel: [24900.927939] audit: type=1400 
audit(1421879550.441:534): apparmor="DENIED" operation="bind" 
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=12356 comm="plugin-containe" 
family="unix" sock_type="dgram" protocol=0 requested_mask="bind" 
denied_mask="bind" 
addr="@676F6F676C652D6E61636C2D6F316431323335362D33393100"
  
  $ aa-decode 
676F6F676C652D6E61636C2D6F316431323335362D33393100
  Decoded: google-nacl-o1d12356-391
  
  $ aa-decode 676F6F676C652D6E61636C2D6
  Decoded: google-nacl-`
  
  So I tried the following:
  unix bind type=dgram addr=@google-nacl*,
  unix bind type=dgram addr="@google-nacl*",
  unix bind type=dgram addr=@676F6F676C652D6E61636C2D6*,
  unix bind type=dgram addr="@676F6F676C652D6E61636C2D6*",
+ unix bind type=dgram addr=@google-nacl*\\000*,
+ unix bind type=dgram 
addr=@google-nacl*[0-9a-zA-Z]\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000{,\\000,\\000\\000},
+ 
  
  but none of them match. The best I could do was:
  unix bind type=dgram,
  
  This is likely going to be important for snappy since snappy will have the 
concept of different coordinating snaps interacting via abstract sockets. What 
is interesting is that this seems to work ok for some things, eg:
  ./lightdm:  unix (bind, listen) type=stream 
addr="@/com/ubuntu/upstart-session/**",
  ./lightdm:  unix (bind, listen) type=stream addr="@/tmp/dbus-*",
  ./lightdm:  unix (bind, listen) type=stream addr="@/tmp/.ICE-unix/[0-9]*",
  ./lightdm:  unix (bind, listen) type=stream addr="@/dbus-vfs-daemon/*",
  ./lightdm:  unix (bind, listen) type=stream addr="@guest*",
  
  Is this something in how firefox is setting up the socket?
  
- 
- To reproduce, enable the firefox profile, start firefox and try to attend a 
google hangout.
+ To reproduce, enable the firefox profile, start firefox and try to
+ attend a google hangout.

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

Title:
  Unable to match unix bind rule

Status in AppArmor Linux application security framework:
  New
Status in apparmor package in Ubuntu:
  New

Bug description:
  On Ubuntu 14.10, I had this in my logs:
  Jan 21 16:32:30 localhost kernel: [24900.927939] audit: type=1400 
audit(1421879550.441:534): apparmor="DENIED" operation="bind" 
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=12356 comm="plugin-containe" 
family="unix" sock_type="dgram" protocol=0 requested_mask="bind" 
denied_mask="bind" 
addr="@676F6F676C652D6E61636C2D6F316431323335362D33393100"

  $ aa-decode 
676F6F676C652D6E61636C2D6F316431323335362D33393100
  Decoded: google-nacl-o1d12356-391

  $ aa-decode 676F6F676C652D6E61636C2D6
  Decoded: google-nacl-`

  So I tried the following:
  unix bind type=dgram addr=@google-nacl*,
  unix bind type=dgram addr="@google-nacl*",
  unix bind type=dgram addr=@676F6F676C652D6E61636C2D6*,
  unix bind type=dgram addr="@676F6F676C652D6E61636C2D6*",
  unix bind type=dgram addr=@google-nacl*\\000*,
  unix bind type=dgram 
addr=@google-nacl*[0-9a-zA-Z]\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000{,\\000,\\000\\000},

  
  but none of them match. The best I could do was:
  unix bind type=dgram,

  This is likely going to be important for snappy since snappy will have the 
concept of different coordinating snaps interacting via abstract sockets. What 
is interesting is that this seems to work ok for some things, eg:
  ./lightdm:  unix (bind, listen) type=strea

[Touch-packages] [Bug 1409003] Re: receiving an sms while roaming and suspended renders the phone difficult to use on resume

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/vivid-proposed/unity8

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

Title:
  receiving an sms while roaming and suspended renders the phone
  difficult to use on resume

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Ubuntu system image (server/client/updater):
  New
Status in unity8 package in Ubuntu:
  New
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  3 times in a row this happened
   1. I left my apartment or co-working space, so I was "roaming" on data
   2. my phone was suspended
   3. I received a text message (sms, etc...) while the phone was suspended
   4. when I turned on the phone, I had trouble getting past the shutdown 
dialog, twice I had to reboot

  This is r186 with silo 7 and silo 3 installed

  After reflashing and updating to r190, I can no longer repro

  Repro steps:
  1. Be connected to a known wireless access point (at your home or office for 
example)
  2. unplug your phone from computer or power 
  3. use power button to suspend your phone
  4. move far enough away from your known AP so that you phone could not see it 
  5. wake the phone and interact long enough that it switches to cell data (for 
me this is always edge because krillin in the US)
  6. suspend your phone again
  7. receive a text message and try to wake your phone

  Result: The shutdown dialog appears, and you cannot get past it.
  Sometimes the phone settles after a few tries and become usable,
  sometimes a hard reboot is required

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

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

[Touch-packages] [Bug 1410830] Re: Shutdown dialog appears on resume, after a long delay in screen turning on

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/vivid-proposed/unity8

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

Title:
  Shutdown dialog appears on resume, after a long delay in screen
  turning on

Status in the base for Ubuntu mobile products:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  Sometimes, if you press the power button to resume your device, the
  screen will stay black for a long time.  When it does come on again,
  the shutdown dialog is likely showing instead of the greeter.

  You might press the power button again while the screen is black,
  thinking you didn't actually press it the first time.  This will
  immediately turn the screen on and then off again.  At which point a
  third power button press will turn the screen on for good.

  This bug is very similar to bug 1383277 (fixed), which involves a
  shutdown dialog appearing on resume, but for a different reason.  This
  is also very similar to (and may be a dup of) bug 1409003.  But since
  bug 1409003 currently involves an incoming text and this bug does not,
  I'm treating them as separate for now.

  This bug is hard to reproduce.  It seems to involve leaving and
  entering wifi/3G zones (or maybe simply toggling the wifi indicator
  button).  But no reliable steps have been recorded yet.

  I'm guessing that like bug 1383277, it involves some resume-event
  handler blocking the input stack so that Qt doesn't notice the power-
  button-release event.  And since it takes so long to resume, Qt thinks
  the user held down the power button long enough to trigger the
  shutdown dialog.

  A trivial band-aid for this is to not start the shutdown-dialog timer
  if the screen is off.  But that wouldn't address the source cause of a
  blocking event handler.  So I think this still merits investigation.
  But if this is a critical/time-sensitive bug, we could slap a band-aid
  on it.

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

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

[Touch-packages] [Bug 1390136] Re: need a transition state for indicators reflecting laggy backends

[Pat McGowan]

** Changed in: canonical-devices-system-image
Milestone: ww05-2015 => ww09-2015

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

Title:
  need a transition state for indicators reflecting laggy backends

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in indicator-network package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Triaged
Status in indicator-network source package in Utopic:
  Confirmed
Status in ubuntu-system-settings source package in Utopic:
  Confirmed
Status in indicator-network source package in Vivid:
  Confirmed
Status in ubuntu-system-settings source package in Vivid:
  Confirmed
Status in unity8 source package in Vivid:
  Triaged
Status in indicator-network package in Ubuntu RTM:
  New
Status in ubuntu-system-settings package in Ubuntu RTM:
  New
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  spawned from efforts in bug 1336715

  because the user's input toggle for airplane mode is both a reflection
  of user intent & the state of the backendand the backend is
  unfortunately variable & lengthy to change (anywhere from 1 to ~10+
  seconds sometimes) we need to have an intermediate/transition
  statee.g. toggle to airplane mode onthen animate somehow that
  there's a transition happening, until it either fails/succeeds

  comment from dizzypaty

  Between the user’s action of toggling the airplane switcher on and/or
  off and the backend updating the state, the indicator icon displayed
  on the statusbar should be the following: network-idle.svg

  
(https://drive.google.com/drive/#folders/0BzbnWoHmYF3aZTA4WHNPYW1jeUE/0BzbnWoHmYF3aS2pVejVicktrdm8/0BzbnWoHmYF3ablBITVByRnpzdEk).

  
  Desired resolution

  Summary: the interface should immediately respond to user input
  confirming the action, even if the backend takes up to 20 seconds to
  actually change state.  Having the UI and backend out of sync for up
  to 30 seconds is not a problem, as long as it always goes back into
  sync after this delay.

  1.When the user changes the flight mode toggle switch it should
  instantly change state.

  2.The backend should then be informed of the state change.

  3.Up to 30 seconds later the backend completes the state change

  Note: The cellular connection indicator should always display the
  backend state, not the current flight mode toggle switch state

  
  Variation - user switches the flight mode toggle on and off rapidly.

  Once a flight mode state change request has been sent to the backend
  but before a conformation that the state change is complete is
  received, all further user interactions should be buffered on the
  client.  When the client receives conformation of the state change
  from the backend it should check to see if the state is in sync with
  its buffer.  If it is in sync nothing happens and the buffer is
  cleared.  If it is not in sync another state change signal is sent to
  the backend and the buffer is cleared.

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

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

[Touch-packages] [Bug 1410420] Re: [dash] preview table runs off right side

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/vivid-proposed/unity8

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

Title:
  [dash] preview table runs off right side

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

Bug description:
  I see a preview table running off the right side of the preview.

  See attached.

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

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

[Touch-packages] [Bug 1398427] Re: [dialer] + [sound] Can't use earphone to answer or disconnect a call

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/vivid-proposed/unity8

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

Title:
  [dialer] + [sound] Can't use earphone to answer or disconnect a call

Status in the base for Ubuntu mobile products:
  In Progress
Status in Telephony Service:
  New
Status in Ubuntu UX bugs:
  Triaged
Status in qtmir package in Ubuntu:
  Fix Released
Status in telephony-service package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  In Progress
Status in qtmir package in Ubuntu RTM:
  Fix Released
Status in telephony-service package in Ubuntu RTM:
  In Progress
Status in unity8 package in Ubuntu RTM:
  Triaged

Bug description:
  [Procedures]
  1.insert the earphone
  2.make a MO call to DUT
  3.use the Hook key to answer the call
  4.when connected the call use the hook key to disconnect the call

  [Expect results]
  earphone hook key can answer and disconnect the call
  [Actual results]
  can't answer and disconnect the call

  [Reproduce]
  Always

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

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

[Touch-packages] [Bug 1385882] Re: Unable to mount iPad with IOS 8

[dave wy]

I am getting the same errors as the original description, as well as the
issues described by Max Barry.  Happening for me with an iPhone 5S with
iOS 8.1.2, with Ubuntu 14.04 on the host.  Any ideas or progress on this
issue?

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

Title:
  Unable to mount iPad with IOS 8

Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  I can't mount my iPad after I upgraded to IOS 8. After plugging in I
  get a series of error messages, also my iPad keep asking wether I
  trust my computer.

  I get messages like:
  Unable to mount ...'s iPad: Location is already mounted  - (it's not)
  Unable to mount iPhone: Unhandled lockdown error (-3) (also sometimes -20)

  If I remember correctly this happened last year after I upgraded to
  iOS 7.

  The problem exists in Utopic too.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libimobiledevice4 1.1.5+git20140313.bafe6a9e-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 26 14:36:14 2014
  InstallationDate: Installed on 2014-01-10 (288 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: libimobiledevice
  UpgradeStatus: Upgraded to trusty on 2014-04-10 (198 days ago)

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

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

[Touch-packages] [Bug 1392368] Re: Support storing and viewing photos on an SD card

[Pat McGowan]

** Changed in: gallery-app (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 apparmor-easyprof-ubuntu
in Ubuntu.
https://bugs.launchpad.net/bugs/1392368

Title:
  Support storing and viewing photos on an SD card

Status in Camera App:
  In Progress
Status in the base for Ubuntu mobile products:
  Fix Released
Status in Gallery App:
  In Progress
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Fix Released
Status in camera-app package in Ubuntu:
  Fix Released
Status in gallery-app package in Ubuntu:
  Fix Released
Status in apparmor-easyprof-ubuntu package in Ubuntu RTM:
  Fix Released
Status in camera-app package in Ubuntu RTM:
  Fix Released
Status in ciborium package in Ubuntu RTM:
  In Progress
Status in gallery-app package in Ubuntu RTM:
  Fix Released

Bug description:
  If an SD card is present we will use it as extended storage for the device.
  The camera and gallery apps need to be able to access this storage.

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

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

[Touch-packages] [Bug 1413411] [NEW] underscore in mounted drive name mishandled in menu

[Carl Cerecke]

Public bug reported:

If you have a mounted drive with an underscore in it's name (e.g.
host_S), then, when you right-click on the drive icon in the sidebar,
the menu interprets the underscore as a keyboard-shortcut indicator, so
shows the name as hostS (with S underlined). Hovering over the drive
results in the correct "host_S" name; the bug is only in the right-click
menu. Note that right-clicking on the "Files" icon will show a menu that
includes the correct mounted disk names. It is only right-clicking on
the drive-icons themselves that shows the incorrect name.

Ubuntu 14.10

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: unity 7.3.1+14.10.20141016-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
Uname: Linux 3.16.0-23-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Thu Jan 22 11:51:46 2015
InstallationDate: Installed on 2015-01-21 (0 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  underscore in mounted drive name mishandled in menu

Status in unity package in Ubuntu:
  New

Bug description:
  If you have a mounted drive with an underscore in it's name (e.g.
  host_S), then, when you right-click on the drive icon in the sidebar,
  the menu interprets the underscore as a keyboard-shortcut indicator,
  so shows the name as hostS (with S underlined). Hovering over the
  drive results in the correct "host_S" name; the bug is only in the
  right-click menu. Note that right-clicking on the "Files" icon will
  show a menu that includes the correct mounted disk names. It is only
  right-clicking on the drive-icons themselves that shows the incorrect
  name.

  Ubuntu 14.10

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity 7.3.1+14.10.20141016-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Thu Jan 22 11:51:46 2015
  InstallationDate: Installed on 2015-01-21 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1382109] Re: Events view should be shown on import

[Pat McGowan]

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

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

Title:
  Events view should be shown on import

Status in the base for Ubuntu mobile products:
  Fix Released
Status in Gallery App:
  Fix Released
Status in gallery-app package in Ubuntu:
  Fix Released
Status in gallery-app package in Ubuntu RTM:
  Fix Released

Bug description:
  If a photo is imported via the content-hub, we should always make sure
  to display the Events view as the photo will show up by default there.

  Currenty if the gallery is open to a specific photo or album, after
  the import occurs we don't update the view so user has no idea where
  the imported picture is.

  Would be nice to directly open the imported picture but this won't
  work as we might get multiple import events in a row from content-hub
  in the case where the user "Dimissed" the open dialog multiple times.
  Next time gallery-app launched or displayed it will be delivered
  multiple events so we would not know which to open.

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

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

[Touch-packages] [Bug 1403205] Re: Gallery does not handle .gif files

[Pat McGowan]

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

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

** Changed in: canonical-devices-system-image
Milestone: None => ww05-2015

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

Title:
  Gallery does not handle .gif files

Status in the base for Ubuntu mobile products:
  New
Status in Gallery App:
  Fix Released
Status in gallery-app package in Ubuntu:
  Fix Released

Bug description:
  Gallery app does not display .gif files on the collection.

  Test Case:
  1. Import a .gif file (i.e. Saving from Gmail, Browser or manually copying to 
the ~/Pictures folder) 
  2. Open gallery-app after the import is finished

  Expected result
  Verify that the photo is saved in the gallery app, and a thumbnail is 
generated.

  Current result:
  The photo is saved on the folder but no thumbanil is generated

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

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

[Touch-packages] [Bug 1413410] Re: Unable to match unix bind rule

[Jamie Strandboge]

** Description changed:

  On Ubuntu 14.10, I had this in my logs:
  Jan 21 16:32:30 localhost kernel: [24900.927939] audit: type=1400 
audit(1421879550.441:534): apparmor="DENIED" operation="bind" 
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=12356 comm="plugin-containe" 
family="unix" sock_type="dgram" protocol=0 requested_mask="bind" 
denied_mask="bind" 
addr="@676F6F676C652D6E61636C2D6F316431323335362D33393100"
  
  $ aa-decode 
676F6F676C652D6E61636C2D6F316431323335362D33393100
  Decoded: google-nacl-o1d12356-391
  
  $ aa-decode 676F6F676C652D6E61636C2D6
  Decoded: google-nacl-`
  
  So I tried the following:
  unix bind type=dgram addr=@google-nacl*,
  unix bind type=dgram addr="@google-nacl*",
  unix bind type=dgram addr=@676F6F676C652D6E61636C2D6*,
  unix bind type=dgram addr="@676F6F676C652D6E61636C2D6*",
  
  but none of them match. The best I could do was:
  unix bind type=dgram,
  
  This is likely going to be important for snappy since snappy will have the 
concept of different coordinating snaps interacting via abstract sockets. What 
is interesting is that this seems to work ok for some things, eg:
  ./lightdm:  unix (bind, listen) type=stream 
addr="@/com/ubuntu/upstart-session/**",
  ./lightdm:  unix (bind, listen) type=stream addr="@/tmp/dbus-*",
  ./lightdm:  unix (bind, listen) type=stream addr="@/tmp/.ICE-unix/[0-9]*",
  ./lightdm:  unix (bind, listen) type=stream addr="@/dbus-vfs-daemon/*",
  ./lightdm:  unix (bind, listen) type=stream addr="@guest*",
  
  Is this something in how firefox is setting up the socket?
+ 
+ 
+ To reproduce, enable the firefox profile, start firefox and try to attend a 
google hangout.

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

Title:
  Unable to match unix bind rule

Status in AppArmor Linux application security framework:
  New
Status in apparmor package in Ubuntu:
  New

Bug description:
  On Ubuntu 14.10, I had this in my logs:
  Jan 21 16:32:30 localhost kernel: [24900.927939] audit: type=1400 
audit(1421879550.441:534): apparmor="DENIED" operation="bind" 
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=12356 comm="plugin-containe" 
family="unix" sock_type="dgram" protocol=0 requested_mask="bind" 
denied_mask="bind" 
addr="@676F6F676C652D6E61636C2D6F316431323335362D33393100"

  $ aa-decode 
676F6F676C652D6E61636C2D6F316431323335362D33393100
  Decoded: google-nacl-o1d12356-391

  $ aa-decode 676F6F676C652D6E61636C2D6
  Decoded: google-nacl-`

  So I tried the following:
  unix bind type=dgram addr=@google-nacl*,
  unix bind type=dgram addr="@google-nacl*",
  unix bind type=dgram addr=@676F6F676C652D6E61636C2D6*,
  unix bind type=dgram addr="@676F6F676C652D6E61636C2D6*",

  but none of them match. The best I could do was:
  unix bind type=dgram,

  This is likely going to be important for snappy since snappy will have the 
concept of different coordinating snaps interacting via abstract sockets. What 
is interesting is that this seems to work ok for some things, eg:
  ./lightdm:  unix (bind, listen) type=stream 
addr="@/com/ubuntu/upstart-session/**",
  ./lightdm:  unix (bind, listen) type=stream addr="@/tmp/dbus-*",
  ./lightdm:  unix (bind, listen) type=stream addr="@/tmp/.ICE-unix/[0-9]*",
  ./lightdm:  unix (bind, listen) type=stream addr="@/dbus-vfs-daemon/*",
  ./lightdm:  unix (bind, listen) type=stream addr="@guest*",

  Is this something in how firefox is setting up the socket?

  
  To reproduce, enable the firefox profile, start firefox and try to attend a 
google hangout.

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

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

[Touch-packages] [Bug 1413271] Re: [vivid] emulator fails to mount root partition (Invalid argument), landing in busybox

[Sergio Schvezov]

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

** This bug has been marked a duplicate of bug 1412495
   ubuntu-emulator fails to start on Vivid

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

Title:
  [vivid] emulator fails to mount root partition (Invalid argument),
  landing in busybox

Status in android-tools package in Ubuntu:
  New

Bug description:
  These days the emulator fails to boot:

  $ sudo ubuntu-emulator create --channel=ubuntu-touch/devel devel
  $ ubuntu-emulator run devel
  [...]
  Begin: Running /scripts/local-premount ... [0.190059] mmc0: new SDHC card 
at address e118
  done.
  [0.195316] mmcblk0: mmc0:e118 SU02G 3.72 GiB 
  [0.195983]  mmcblk0: unknown partition table
  [0.270180] initrd: checking filesystem integrity for the userdata 
partition
  [0.271256] EXT4-fs (mmcblk0): couldn't mount as ext3 due to feature 
incompatibilities
  [0.273543] EXT4-fs (mmcblk0): couldn't mount as ext2 due to feature 
incompatibilities
  [0.284652] EXT4-fs (mmcblk0): bad geometry: block count 976562 exceeds 
size of device (976512 blocks)
  [0.333267] yaffs: dev is 187695104 name is "mmcblk0" rw
  [0.30] yaffs: passed flags "errors=remount-ro"
  [0.59] yaffs: Bad mount option "errors=remount-ro"
  [0.343222] yaffs: dev is 187695104 name is "mmcblk0" rw
  [0.343271] yaffs: passed flags "errors=remount-ro"
  [0.343300] yaffs: Bad mount option "errors=remount-ro"
  mount: mounting /dev/mmcblk0 on /tmpmnt failed: Invalid argument
  umount: can't umount /tmpmnt: Invalid argument
  [0.370651]  mmcblk0: unknown partition table
  [0.375414] initrd: checking filesystem for userdata took (including 
e2fsck) 0 seconds
  [0.375497] initrd: mounting /dev/mmcblk0
  [0.464983] EXT4-fs: Warning: mounting with data=journal disables delayed 
allocation and O_DIRECT support!
  [0.465039] EXT4-fs (mmcblk0): couldn't mount as ext3 due to feature 
incompatibilities
  [0.473248] EXT4-fs (mmcblk0): couldn't mount as ext2 due to feature 
incompatibilities
  [0.483957] EXT4-fs (mmcblk0): bad geometry: block count 976562 exceeds 
size of device (976512 blocks)
  [0.533049] yaffs: dev is 187695104 name is "mmcblk0" rw
  [0.533113] yaffs: passed flags "discard,data=journal"
  [0.533140] yaffs: Bad mount option "discard"
  [0.543012] yaffs: dev is 187695104 name is "mmcblk0" rw
  [0.543059] yaffs: passed flags "discard,data=journal"
  [0.543086] yaffs: Bad mount option "discard"
  mount: mounting /dev/mmcblk0 on /tmpmnt failed: Invalid argument
  [0.554010] initrd: boot mode: ubuntu
  [0.554108] initrd: Couldn't find a system partition.
  Couldn't find a system partition. Spawning adbd ...
  [0.558145] initrd: enabling USB debugging
  /scripts/panic/adbd: line 22: can't create 
/sys/class/android_usb/android0/idVendor: nonexistent directory
  /scripts/panic/adbd: line 23: can't create 
/sys/class/android_usb/android0/idProduct: nonexistent directory
  /scripts/panic/adbd: line 24: can't create 
/sys/class/android_usb/android0/functions: nonexistent directory
  /scripts/panic/adbd: line 25: can't create 
/sys/class/android_usb/android0/enable: nonexistent directory
  [0.559371] initrd: starting adbd for USB debugging
  [0.560620] adbd[168]: segfault at c ip 0804cb29 sp bf98e2d8 error 4 in 
adbd[8048000+2]
  Segmentation fault

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

  So the primary problem seems to be

mount: mounting /dev/mmcblk0 on /tmpmnt failed: Invalid argument

  The adbd  crash also seems important, but secondary.

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

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

[Touch-packages] [Bug 1413410] [NEW] Unable to match unix bind rule

[Jamie Strandboge]

Public bug reported:

On Ubuntu 14.10, I had this in my logs:
Jan 21 16:32:30 localhost kernel: [24900.927939] audit: type=1400 
audit(1421879550.441:534): apparmor="DENIED" operation="bind" 
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=12356 comm="plugin-containe" 
family="unix" sock_type="dgram" protocol=0 requested_mask="bind" 
denied_mask="bind" 
addr="@676F6F676C652D6E61636C2D6F316431323335362D33393100"

$ aa-decode 
676F6F676C652D6E61636C2D6F316431323335362D33393100
Decoded: google-nacl-o1d12356-391

$ aa-decode 676F6F676C652D6E61636C2D6
Decoded: google-nacl-`

So I tried the following:
unix bind type=dgram addr=@google-nacl*,
unix bind type=dgram addr="@google-nacl*",
unix bind type=dgram addr=@676F6F676C652D6E61636C2D6*,
unix bind type=dgram addr="@676F6F676C652D6E61636C2D6*",

but none of them match. The best I could do was:
unix bind type=dgram,

This is likely going to be important for snappy since snappy will have the 
concept of different coordinating snaps interacting via abstract sockets. What 
is interesting is that this seems to work ok for some things, eg:
./lightdm:  unix (bind, listen) type=stream 
addr="@/com/ubuntu/upstart-session/**",
./lightdm:  unix (bind, listen) type=stream addr="@/tmp/dbus-*",
./lightdm:  unix (bind, listen) type=stream addr="@/tmp/.ICE-unix/[0-9]*",
./lightdm:  unix (bind, listen) type=stream addr="@/dbus-vfs-daemon/*",
./lightdm:  unix (bind, listen) type=stream addr="@guest*",

Is this something in how firefox is setting up the socket?

** Affects: apparmor
 Importance: Undecided
 Status: New

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


** Tags: aa-kernel aa-parser

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

** Tags added: aa-kernel aa-parser

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

** Description changed:

- I had this in my logs:
+ On Ubuntu 14.10, I had this in my logs:
  Jan 21 16:32:30 localhost kernel: [24900.927939] audit: type=1400 
audit(1421879550.441:534): apparmor="DENIED" operation="bind" 
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=12356 comm="plugin-containe" 
family="unix" sock_type="dgram" protocol=0 requested_mask="bind" 
denied_mask="bind" 
addr="@676F6F676C652D6E61636C2D6F316431323335362D33393100"
- 
  
  $ aa-decode 
676F6F676C652D6E61636C2D6F316431323335362D33393100
  Decoded: google-nacl-o1d12356-391
  
- 
  $ aa-decode 676F6F676C652D6E61636C2D6
  Decoded: google-nacl-`
- 
  
  So I tried the following:
  unix bind type=dgram addr=@google-nacl*,
  unix bind type=dgram addr="@google-nacl*",
  unix bind type=dgram addr=@676F6F676C652D6E61636C2D6*,
  unix bind type=dgram addr="@676F6F676C652D6E61636C2D6*",
  
  but none of them match. The best I could do was:
  unix bind type=dgram,
  
- 
  This is likely going to be important for snappy since snappy will have the 
concept of different coordinating snaps interacting via abstract sockets. What 
is interesting is that this seems to work ok for some things, eg:
  ./lightdm:  unix (bind, listen) type=stream 
addr="@/com/ubuntu/upstart-session/**",
  ./lightdm:  unix (bind, listen) type=stream addr="@/tmp/dbus-*",
  ./lightdm:  unix (bind, listen) type=stream addr="@/tmp/.ICE-unix/[0-9]*",
  ./lightdm:  unix (bind, listen) type=stream addr="@/dbus-vfs-daemon/*",
  ./lightdm:  unix (bind, listen) type=stream addr="@guest*",
  
  Is this something in how firefox is setting up the socket?

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

Title:
  Unable to match unix bind rule

Status in AppArmor Linux application security framework:
  New
Status in apparmor package in Ubuntu:
  New

Bug description:
  On Ubuntu 14.10, I had this in my logs:
  Jan 21 16:32:30 localhost kernel: [24900.927939] audit: type=1400 
audit(1421879550.441:534): apparmor="DENIED" operation="bind" 
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=12356 comm="plugin-containe" 
family="unix" sock_type="dgram" protocol=0 requested_mask="bind" 
denied_mask="bind" 
addr="@676F6F676C652D6E61636C2D6F316431323335362D3339310

[Touch-packages] [Bug 1376445] Re: Addition of signon-apparmor-extension causes token lookup problems

[Launchpad Bug Tracker]

** Branch linked: lp:~dobey/ubuntuone-credentials/acl-unconfined-rtm

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

Title:
  Addition of signon-apparmor-extension causes token lookup problems

Status in the base for Ubuntu mobile products:
  Confirmed
Status in go-onlineaccounts:
  Incomplete
Status in The Savilerow project:
  Invalid
Status in ACL for signond, AppArmor backend:
  Fix Released
Status in Online Accounts setup for Ubuntu Touch:
  Fix Released
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  In Progress
Status in ubuntuone-credentials package in Ubuntu:
  Fix Released
Status in signon-apparmor-extension package in Ubuntu RTM:
  Triaged
Status in ubuntu-system-settings-online-accounts package in Ubuntu RTM:
  New
Status in ubuntuone-credentials package in Ubuntu RTM:
  Confirmed

Bug description:
  As of image ~264 of ubuntu-touch, the signon-apparmor-extension
  package is included. As a result, apps like pay-ui cannot find the
  token any longer, and are not being notified that they are not allowed
  to access the token. The following error appears in the payui log
  file:

  2014-10-01 19:15:51,550 - DEBUG -
  ../../../../lib/SignOn/authsessionimpl.cpp 184 errorSlot
  QDBusError("com.google.code.AccountsSSO.SingleSignOn.Error.PermissionDenied",
  "Client has insuficient permissions to access the
  service.Method:getAuthSessionObjectPath")

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

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

[Touch-packages] [Bug 1370014] Re: Remmina Launching Remote Sessions Larger than Workspace

[Robert Ancell]

You suggest that version 1.1.1 has this fixed so I had a look through the log 
to see what has changed. I *think* this may be the fix you need:
https://github.com/FreeRDP/Remmina/commit/348e01d27869a577ad5df9bf6286f876b34a40c0

** No longer affects: unity (Ubuntu)

** No longer affects: unity

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

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

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

** Also affects: remmina (Ubuntu Precise)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

** Changed in: remmina (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Remmina Launching Remote Sessions Larger than Workspace

Status in remmina package in Ubuntu:
  Fix Released
Status in remmina source package in Precise:
  Triaged
Status in remmina source package in Trusty:
  Triaged
Status in remmina source package in Utopic:
  Triaged

Bug description:
  Please view this video of the bug I'm reporting:
  http://youtu.be/wKGLff7HhS8

  To reproduce this bug, you will have to Enable Workspaces In Ubuntu
  Unity, like this:

  System Settings > Appearance > Behavior > Enable Workspaces

  Essentially, when using the Unity desktop (using workspaces), Remmina
  is launching remote sessions into a window larger than the workspace
  to which I'm launching it.

  Another thing to note about my set up, is that I do use Ubuntu's
  scaling feature to make things about 10% larger than the default size
  (to accommodate my otherwise straining eyes). Some times I use large
  text too. These facts may be totally unrelated to the bug, but I
  thought I would at least mention them. Also, I do use multiple
  monitors, but this too might be unrelated to the bug. I think the
  essential thing, is that I have Workspaces enabled.

  I'm using a fully update Ubuntu 14.04 Desktop 64bit.

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

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

[Touch-packages] [Bug 1370014] Re: Remmina Launching Remote Sessions Larger than Workspace

[Robert Ancell]

As I understand it the sourceforge.net project is obsolete and Remmina
is now developed on https://github.com/FreeRDP/Remmina. That will
probably be why there is no response to your bug report. I think the
current developers don't have access to the old project to remove it.

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

Title:
  Remmina Launching Remote Sessions Larger than Workspace

Status in remmina package in Ubuntu:
  Fix Released
Status in remmina source package in Precise:
  Triaged
Status in remmina source package in Trusty:
  Triaged
Status in remmina source package in Utopic:
  Triaged

Bug description:
  Please view this video of the bug I'm reporting:
  http://youtu.be/wKGLff7HhS8

  To reproduce this bug, you will have to Enable Workspaces In Ubuntu
  Unity, like this:

  System Settings > Appearance > Behavior > Enable Workspaces

  Essentially, when using the Unity desktop (using workspaces), Remmina
  is launching remote sessions into a window larger than the workspace
  to which I'm launching it.

  Another thing to note about my set up, is that I do use Ubuntu's
  scaling feature to make things about 10% larger than the default size
  (to accommodate my otherwise straining eyes). Some times I use large
  text too. These facts may be totally unrelated to the bug, but I
  thought I would at least mention them. Also, I do use multiple
  monitors, but this too might be unrelated to the bug. I think the
  essential thing, is that I have Workspaces enabled.

  I'm using a fully update Ubuntu 14.04 Desktop 64bit.

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

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

[Touch-packages] [Bug 1413302] Re: GSM connected, but no data plan - should report disconnected

[Michał Karnicki]

list-modems
http://paste.ubuntu.com/9810922/

list-contexts
http://paste.ubuntu.com/9810930/

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

Title:
  GSM connected, but no data plan - should report disconnected

Status in the base for Ubuntu mobile products:
  New
Status in Ubuntu Connectivity API:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce:
  1. insert SIM card with data plan that has run out/expired
  2. notice NetworkingStatus reports connected, but there's "no Internet"

  phablet@ubuntu-phablet:~$  nmcli d
  DEVICE TYPE  STATE
  /ril_1 gsm   connected
  /ril_0 gsm   disconnected

  phablet@ubuntu-phablet:~$ system-image-cli --info
  current build number: 205
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2015-01-21 10:06:15
  version version: 205
  version ubuntu: 20150121
  version device: 20150113-2a2e4c5
  version custom: 20150112-494-23-173

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

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

[Touch-packages] [Bug 1413390] Re: GRID_UNIT_PX no longer supplied for autopilot desktop sessions

[Allan LeSage]

My mistake, please ignore, now using scenarios properly.

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

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

Title:
  GRID_UNIT_PX no longer supplied for autopilot desktop sessions

Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Testing of autopilot tests on the desktop has depended on the settings
  of a GRID_UNIT_PX env var; this mysteriously disappeared recently.

  Filing here for the unity8 autopilot suite; investigate and at least
  supply a temp env var depending on platform (we'll be doing this in
  tests until such exists.)

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

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

[Touch-packages] [Bug 879826] Re: [CMI8786 - Xonar DG, playback] volume position not saved on shutdown

[Bugston]

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

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

Title:
  [CMI8786 - Xonar DG, playback] volume position not saved on shutdown

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Volume position is not saved upon system shutdown. Volume returns to
  max on log in.

  Ubuntu 11.10
  ALSA 1.0.24

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: alsa-base 1.0.24+dfsg-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: DG [Xonar DG], device 0: Multichannel [Multichannel]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chase  1636 F pulseaudio
   /dev/snd/pcmC0D0p:   chase  1636 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'DG'/'C-Media Oxygen HD Audio at 0xe800, irq 16'
 Mixer name : 'CMI8786'
 Components : 'CS4245 CMI8786'
 Controls  : 15
 Simple ctrls  : 10
  Date: Sat Oct 22 02:08:40 2011
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: CMI8788 [Oxygen HD Audio] - Xonar DG
  Symptom_Type: Volume slider, or mixer problems
  Title: [CMI8786 - Xonar DG, playback] volume slider problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/02/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.9
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P55-CD53 (MS-7586)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd09/02/2010:svnMSI:pnMS-7586:pvr1.0:rvnMSI:rnP55-CD53(MS-7586):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7586
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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

[Touch-packages] [Bug 1401717] Re: Scope test fixture throws exception when scope uses cache_directory()

[Michi Henning]

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

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

Title:
  Scope test fixture throws exception when scope uses cache_directory()

Status in unity-scopes-api package in Ubuntu:
  Fix Released

Bug description:
  When using TypedScopeFixture to  test a scope that makes use of
  cache_directory any tests will always fail with the following message
  (regardless of where the cache_directory call is in the scope code):

  C++ exception with description "unity::LogicException:
  ScopeBase::cache_directory() cannot be called from constructor" thrown
  in the test body.

  A similar problem with scope_directory() was solved by adding a
  set_scope_directory() method to the fixture.

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

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

[Touch-packages] [Bug 1410125] Re: /usr/lib/x86_64-linux-gnu/unity-scopes/smartscopesproxy:smartscopesproxy: src/lib_json/json_value.cpp:1176: const Json::Value& Json::Value::operator[](const char*) c

[Michi Henning]

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

Title:
  /usr/lib/x86_64-linux-gnu/unity-
  scopes/smartscopesproxy:smartscopesproxy:
  src/lib_json/json_value.cpp:1176: const Json::Value&
  Json::Value::operator[](const char*) const: Assertion `type_ ==
  nullValue || type_ == objectValue' failed.

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

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity-scopes-api.  This problem was most recently seen with
  version 0.6.10+15.04.20141212-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/6f30572de3a80023aad871427ab550250dcc2a89
  contains more details.

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

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

[Touch-packages] [Bug 1370014] Re: Remmina Launching Remote Sessions Larger than Workspace

[Robert Ancell]

Lonnie - we don't update to newer versions of packages in stable
releases, see https://wiki.ubuntu.com/StableReleaseUpdates

** Tags removed: upgrade-software-version

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

Title:
  Remmina Launching Remote Sessions Larger than Workspace

Status in Unity:
  New
Status in remmina package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Please view this video of the bug I'm reporting:
  http://youtu.be/wKGLff7HhS8

  To reproduce this bug, you will have to Enable Workspaces In Ubuntu
  Unity, like this:

  System Settings > Appearance > Behavior > Enable Workspaces

  Essentially, when using the Unity desktop (using workspaces), Remmina
  is launching remote sessions into a window larger than the workspace
  to which I'm launching it.

  Another thing to note about my set up, is that I do use Ubuntu's
  scaling feature to make things about 10% larger than the default size
  (to accommodate my otherwise straining eyes). Some times I use large
  text too. These facts may be totally unrelated to the bug, but I
  thought I would at least mention them. Also, I do use multiple
  monitors, but this too might be unrelated to the bug. I think the
  essential thing, is that I have Workspaces enabled.

  I'm using a fully update Ubuntu 14.04 Desktop 64bit.

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

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

[Touch-packages] [Bug 1324142] Re: Support providing fallback images

[Michi Henning]

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

Title:
  Support providing fallback images

Status in Thumbnail generator for all kinds of files:
  New
Status in unity-scopes-api package in Ubuntu:
  Fix Committed
Status in unity-scopes-shell package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  If the URI for a scope result icon can not be loaded, the scope result
  is not easily visible.

  To counter this, the shell should replace the result image with a
  fallback image if the Image QML component changes to the Error state.
  At a minimum a single standard fallback image would be sufficient, but
  letting the scope pick a custom fallback via the category renderer
  template would be better.

  One reason I'd like to see this is so we can switch the album art
  image provider to stop returning a fallback image.  This has been
  requested by the music-app guys, and seems sensible since we might
  want different fallbacks in different contexts:

  https://code.launchpad.net/~jamesh/thumbnailer/no-fallback-
  albumart/+merge/219460

  It might also be useful for remote scopes using http: URIs for result
  icons.

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

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

[Touch-packages] [Bug 1412373] Re: Trusted sessions don't receive focus after switching apps

[Josh Arenson]

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

** This bug has been marked a duplicate of bug 1395724
   Cannot type into account login input boxes

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

Title:
  Trusted sessions don't receive focus after switching apps

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  While trying to create an account from the Youtube scope, I was not
  able to enter my Google account confirmation code, as the keyboard
  would not display.

  To reproduce:
  - navigate to the Youtbe scope, or activate it from the scope catalog
  - scroll down to find the "Log-in to Youtube" button
  - let the trust prompt slide up, where you will be able to login to you 
Google account
  - Switch to another app and then switch back
  - Tap a text field in the login prompt

  What should happen: the OSK appears
  What happens instead: the OSK does not pop up

  This happens because focus is being given to unity8-dash, instead of
  the trusted session. This can also be reproduced using the Gmail app
  by following similar steps (without having a Google account already
  setup).

  Tested on vivid mako/r67.

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

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

[Touch-packages] [Bug 1332118] Re: Update to 0.9.6

[Robert Ancell]

This must be fixed by now...

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

Title:
  Update to 0.9.6

Status in folks package in Ubuntu:
  Fix Released

Bug description:
  JFYI. I've merged this in my ppa:laney/arm for testing, will upload
  soonish.

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

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

[Touch-packages] [Bug 1413313] Re: apparmor denied messages in log, may be responsible for not printing anymore

[C de-Avillez]

for the record, adjusting as above makes my printer work.

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

Title:
  apparmor denied messages in log, may be responsible for not printing
  anymore

Status in cups package in Ubuntu:
  New

Bug description:
  The printer is a HP-3600N. Was printing nicely, got out-of-tone on
  magenta. Loaded a new toner, print output is still held with "printer
  out of toner" messages.

  /var/log/syslog shows many messages like:

  2015-01-21T11:09:15.511793-06:00 icatu kernel: [336562.378463] audit:
  type=1400 audit(1421860155.504:481): apparmor="DENIED"
  operation="sendmsg" info="Failed name lookup - disconnected path"
  error=-13 profile="/usr/sbin/cupsd//third_party"
  name="run/systemd/journal/dev-log" pid=24704 comm="hp"
  requested_mask="w" denied_mask="w" fsuid=7 ouid=0

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: cups 1.7.5-10ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic x86_64
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  CupsErrorLog:
   E [21/Jan/2015:07:53:58 -0600] Unknown configuration directive 
CM-Calibration on line 13 of printers.conf.
   E [21/Jan/2015:11:10:01 -0600] [Client 21] Returning IPP 
client-error-bad-request for Print-Job (ipp://localhost/printers/HP-CL3600) 
from localhost
   W [21/Jan/2015:11:10:19 -0600] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 'HP-CL3600-Gray..' 
already exists
   W [21/Jan/2015:11:10:19 -0600] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 'HP-CL3600-RGB..' already 
exists
   E [21/Jan/2015:11:14:16 -0600] [Job 46] Stopping unresponsive job.
  CurrentDesktop: Unity
  Date: Wed Jan 21 11:18:00 2015
  InstallationDate: Installed on 2013-11-07 (440 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  Lpstat: device for HP-CL3600: hp:/net/HP_Color_LaserJet_3600?zc=NPI70F7DC
  MachineType: System76, Inc. Gazelle Professional
  Papersize: letter
  PpdFiles: HP-CL3600: HP Color LaserJet 3600 Foomatic/pxljr
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic 
root=/dev/mapper/ubuntu--vg-root ro allow-discards root_trim=yes quiet splash 
acpi_backlight=vendor vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to vivid on 2014-11-11 (71 days ago)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.00.05RS76
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Gazelle Professional
  dmi.board.vendor: System76, Inc.
  dmi.board.version: gazp9
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: gazp9
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.00.05RS76:bd08/15/2013:svnSystem76,Inc.:pnGazelleProfessional:pvrgazp9:rvnSystem76,Inc.:rnGazelleProfessional:rvrgazp9:cvnSystem76,Inc.:ct9:cvrgazp9:
  dmi.product.name: Gazelle Professional
  dmi.product.version: gazp9
  dmi.sys.vendor: System76, Inc.

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

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

[Touch-packages] [Bug 1400836] Re: Calling voicemail from notification doesn't populate the number when locked

[Pat McGowan]

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

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

Title:
  Calling voicemail from notification doesn't populate the number when
  locked

Status in the base for Ubuntu mobile products:
  Fix Released
Status in Dialer app for Ubuntu Touch:
  In Progress
Status in dialer-app package in Ubuntu:
  Fix Released
Status in dialer-app package in Ubuntu RTM:
  Fix Released

Bug description:
  Phone is locked/suspend
  Get a voicemail notification
  select the voicemail event 
  Unlock screen presented
  dialer is shown but no number is provided

  If you unlock the phone before selecting the notification it works

  This is a bit of a problem if you haven't made a note of the number in
  your address book as you lose the notification and cannot try again

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

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

[Touch-packages] [Bug 1359337] Re: dialer not remembering current view after lock/unlock

[Pat McGowan]

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

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

Title:
  dialer not remembering current view after lock/unlock

Status in the base for Ubuntu mobile products:
  Fix Released
Status in Dialer app for Ubuntu Touch:
  Confirmed
Status in dialer-app package in Ubuntu:
  Fix Released
Status in dialer-app package in Ubuntu RTM:
  Fix Released

Bug description:
  build 199
  open dialer
  navigate to contacts page or recents page
  lock the phone
  unlock the phone

  Expected results:
  dialer should be on the page you left it on

  Actual results:
  keypad view is always shown

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

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

[Touch-packages] [Bug 1404304] Re: placing a second call from messaging-app/address-book does not work

[Pat McGowan]

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

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

Title:
  placing a second call from messaging-app/address-book does not work

Status in the base for Ubuntu mobile products:
  Fix Released
Status in Dialer app for Ubuntu Touch:
  In Progress
Status in dialer-app package in Ubuntu:
  Fix Released
Status in dialer-app package in Ubuntu RTM:
  Fix Released

Bug description:
  rtm build 184

  Steps to reproduce:
  - open dialer app and make a call
  - wait until the call is active
  - Switch to messaging app or contacts app
  - select a contact from either app, expand the contact and press the "Call" 
icon

  Expected results:
  - the dialer app should move to the foreground and show the keypad view with 
the number populated

  Actual results:
  - the dialer app moves to the foreground and shows the existing live call view

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

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

[Touch-packages] [Bug 1413390] [NEW] GRID_UNIT_PX no longer supplied for autopilot desktop sessions

[Allan LeSage]

Public bug reported:

Testing of autopilot tests on the desktop has depended on the settings
of a GRID_UNIT_PX env var; this mysteriously disappeared recently.

Filing here for the unity8 autopilot suite; investigate and at least
supply a temp env var depending on platform (we'll be doing this in
tests until such exists.)

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

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

Title:
  GRID_UNIT_PX no longer supplied for autopilot desktop sessions

Status in unity8 package in Ubuntu:
  New

Bug description:
  Testing of autopilot tests on the desktop has depended on the settings
  of a GRID_UNIT_PX env var; this mysteriously disappeared recently.

  Filing here for the unity8 autopilot suite; investigate and at least
  supply a temp env var depending on platform (we'll be doing this in
  tests until such exists.)

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

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

[Touch-packages] [Bug 1359337] Re: dialer not remembering current view after lock/unlock

[Launchpad Bug Tracker]

This bug was fixed in the package dialer-app - 0.1+15.04.20150121~rtm-
0ubuntu1

---
dialer-app (0.1+15.04.20150121~rtm-0ubuntu1) 14.09; urgency=low

  [ Ubuntu daily release ]
  * New rebuild forced

  [ Gustavo Pichorim Boiko ]
  * Update pot file.
  * Emergency mode refactor. Use two page stacks: one for normal mode
and another for emergency mode. (LP: #1404304, #1359337, #1400836)
 -- Ubuntu daily releaseWed, 21 Jan 2015 
03:10:41 +

** Changed in: dialer-app (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 dialer-app in Ubuntu.
https://bugs.launchpad.net/bugs/1359337

Title:
  dialer not remembering current view after lock/unlock

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Dialer app for Ubuntu Touch:
  Confirmed
Status in dialer-app package in Ubuntu:
  Fix Released
Status in dialer-app package in Ubuntu RTM:
  Fix Released

Bug description:
  build 199
  open dialer
  navigate to contacts page or recents page
  lock the phone
  unlock the phone

  Expected results:
  dialer should be on the page you left it on

  Actual results:
  keypad view is always shown

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

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

[Touch-packages] [Bug 1400836] Re: Calling voicemail from notification doesn't populate the number when locked

[Launchpad Bug Tracker]

This bug was fixed in the package dialer-app - 0.1+15.04.20150121~rtm-
0ubuntu1

---
dialer-app (0.1+15.04.20150121~rtm-0ubuntu1) 14.09; urgency=low

  [ Ubuntu daily release ]
  * New rebuild forced

  [ Gustavo Pichorim Boiko ]
  * Update pot file.
  * Emergency mode refactor. Use two page stacks: one for normal mode
and another for emergency mode. (LP: #1404304, #1359337, #1400836)
 -- Ubuntu daily releaseWed, 21 Jan 2015 
03:10:41 +

** Changed in: dialer-app (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 dialer-app in Ubuntu.
https://bugs.launchpad.net/bugs/1400836

Title:
  Calling voicemail from notification doesn't populate the number when
  locked

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Dialer app for Ubuntu Touch:
  In Progress
Status in dialer-app package in Ubuntu:
  Fix Released
Status in dialer-app package in Ubuntu RTM:
  Fix Released

Bug description:
  Phone is locked/suspend
  Get a voicemail notification
  select the voicemail event 
  Unlock screen presented
  dialer is shown but no number is provided

  If you unlock the phone before selecting the notification it works

  This is a bit of a problem if you haven't made a note of the number in
  your address book as you lose the notification and cannot try again

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

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

[Touch-packages] [Bug 1404304] Re: placing a second call from messaging-app/address-book does not work

[Launchpad Bug Tracker]

This bug was fixed in the package dialer-app - 0.1+15.04.20150121~rtm-
0ubuntu1

---
dialer-app (0.1+15.04.20150121~rtm-0ubuntu1) 14.09; urgency=low

  [ Ubuntu daily release ]
  * New rebuild forced

  [ Gustavo Pichorim Boiko ]
  * Update pot file.
  * Emergency mode refactor. Use two page stacks: one for normal mode
and another for emergency mode. (LP: #1404304, #1359337, #1400836)
 -- Ubuntu daily releaseWed, 21 Jan 2015 
03:10:41 +

** Changed in: dialer-app (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 dialer-app in Ubuntu.
https://bugs.launchpad.net/bugs/1404304

Title:
  placing a second call from messaging-app/address-book does not work

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Dialer app for Ubuntu Touch:
  In Progress
Status in dialer-app package in Ubuntu:
  Fix Released
Status in dialer-app package in Ubuntu RTM:
  Fix Released

Bug description:
  rtm build 184

  Steps to reproduce:
  - open dialer app and make a call
  - wait until the call is active
  - Switch to messaging app or contacts app
  - select a contact from either app, expand the contact and press the "Call" 
icon

  Expected results:
  - the dialer app should move to the foreground and show the keypad view with 
the number populated

  Actual results:
  - the dialer app moves to the foreground and shows the existing live call view

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

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

[Touch-packages] [Bug 1223055] Re: System Hangs With Kernel Migration Processes Consuming 100% CPU

[Andrew Piziali]

I have not seen this hang since I stopped using the direct rendering
(DRI) of the ATI Mobility Radeon X1400 in this ThinkPad T60. I switched
video drivers (now using the X.Org "radeon" driver) because the new
external monitor I am using (ViewSonic VG2439m) would glitch, loose sync
and scamble text) with the ATI driver I was using.

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

Title:
  System Hangs With Kernel Migration Processes Consuming 100% CPU

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Once or twice a week, the system becomes non-responsive, with the
  mouse cursor tracking mouse movement but no keyboard response. Until
  today I would resort to using the kernel magic keys to reboot the
  system (R-E-I-S-U-B). Today I remotely logged in from another machine
  on the LAN and discovered that not only was the kernel alive and all
  processes running, but that the "migration/0" and "migration/1"
  processes were consuming 50% of the CPU each, as reported by top(1). I
  suspect this is why the system becomes non-responsive.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-generic 3.2.0.53.63
  ProcVersionSignature: Ubuntu 3.2.0-53.81-generic 3.2.50
  Uname: Linux 3.2.0-53-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu17.4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  andy   2195 F pulseaudio
   /dev/snd/controlC0:  andy   2195 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xee40 irq 47'
 Mixer name : 'Analog Devices AD1981'
 Components : 'HDA:11d41981,17aa2025,00100200'
 Controls  : 21
 Simple ctrls  : 12
  Card1.Amixer.info:
   Card hw:1 'U0x46d0x804'/'USB Device 0x46d:0x804 at usb-:00:1d.7-6.2.2, 
high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB046d:0804'
 Controls  : 2
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'Mic',0
 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
 Capture channels: Mono
 Limits: Capture 0 - 6144
 Mono: Capture 4608 [75%] [24.00dB] [on]
  Card29.Amixer.info:
   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
79HT50WW-1.07'
 Mixer name : 'ThinkPad EC 79HT50WW-1.07'
 Components : ''
 Controls  : 2
 Simple ctrls  : 1
  Card29.Amixer.values:
   Simple mixer control 'Console',0
 Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum
 Playback channels: Mono
 Limits: Playback 0 - 14
 Mono: Playback 7 [50%] [on]
  Date: Mon Sep  9 16:56:22 2013
  HibernationDevice: RESUME=UUID=5301c707-e227-46f3-8b49-a319582091a4
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  MachineType: LENOVO 8743CTO
  MarkForUpload: True
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-53-generic 
root=UUID=a9ba509e-76a3-4c03-b898-0409f24233eb ro quiet splash nomodeset 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-53-generic N/A
   linux-backports-modules-3.2.0-53-generic  N/A
   linux-firmware1.79.6
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/05/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7IET32WW (1.13 )
  dmi.board.name: 8743CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7IET32WW(1.13):bd02/05/2008:svnLENOVO:pn8743CTO:pvrThinkPadT60:rvnLENOVO:rn8743CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 8743CTO
  dmi.product.version: ThinkPad T60
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1412060] Re: Indicator sound fails to start with Asus Xonar

[Elfy]

Booting with a livesession of vivid - get the same.

No sound indicator.

Pulse is running.

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

Title:
  Indicator sound fails to start with Asus Xonar

Status in indicator-sound package in Ubuntu:
  New

Bug description:
  Replaced Audigy with Xonar.

  Clean installed to new drive and partition.

  sound indicator fails to start

  upstart --user --startup-event indicator-services-start

  tries to start indicator - space in indicators shows where it is,
  clicking and menu doesn't appear

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: indicator-sound 12.10.2+15.04.20141105-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Jan 17 21:37:27 2015
  InstallationDate: Installed on 2015-01-09 (8 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150108)
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1392368] Re: Support storing and viewing photos on an SD card

[Pat McGowan]

** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Released

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

Title:
  Support storing and viewing photos on an SD card

Status in Camera App:
  In Progress
Status in the base for Ubuntu mobile products:
  Fix Released
Status in Gallery App:
  In Progress
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Fix Released
Status in camera-app package in Ubuntu:
  Fix Released
Status in gallery-app package in Ubuntu:
  Fix Released
Status in apparmor-easyprof-ubuntu package in Ubuntu RTM:
  Fix Released
Status in camera-app package in Ubuntu RTM:
  Fix Released
Status in ciborium package in Ubuntu RTM:
  In Progress
Status in gallery-app package in Ubuntu RTM:
  In Progress

Bug description:
  If an SD card is present we will use it as extended storage for the device.
  The camera and gallery apps need to be able to access this storage.

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

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

[Touch-packages] [Bug 1413363] Re: bluetooth speaker and suspension issue

[Mathieu Trudel-Lapierre]

Could you also try to re-pair the speaker by pressing a button after the
system is resumed?

** Package changed: bluez-utils (Ubuntu) => bluez (Ubuntu)

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

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

Title:
  bluetooth speaker and suspension issue

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  STEPS:
  1. Open settings bluetooth
  2. Turn on your blue tooth speaker
  3. Pair the speaker
  4. Open the music app
  5. Play music
  6. Pause the music
  7. Let the phone suspend
  8. After a while it goes into deep sleep and the speaker disconnects
  9. Wake the phone press the play button

  EXPECTED:
  I expected the music to play out of the bluetooth speaker

  ACTUAL:
  A long pause, then a click then the music plays from the internal speaker.  
You can no longer get the music to play  from the bluetooth speaker.

  Things I've tried:
  Reboot the phone re connect to the bt speaker music still plays from the loud 
speaker on the phone.
  Turned off the speaker, restarted it still plays through the Loud speaker on 
the phone

  WORK AROUND:
  Forget the connection. Re pair the device now press play now it works as 
expected.

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

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

[Touch-packages] [Bug 1410874] Re: Alarm sounds vs Calendar sounds

[Launchpad Bug Tracker]

** Branch linked: lp:~charlesk/indicator-datetime/rtm-14.09-lp-1410874
-alarm-sounds-vs-calendar-sounds

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

Title:
  Alarm sounds vs Calendar sounds

Status in the base for Ubuntu mobile products:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  In Progress
Status in indicator-datetime package in Ubuntu RTM:
  New

Bug description:
  As discussed with rsalveti and pmcgowan in #phablet on 14 Jan

  There are two issues in the datetime notification code that need to be
  changed.

  1. Right now we only set role=alarm if the sound is looping; ie if it's an 
alarm clock event rather than calendar event.
  Set calendar event role to alert

  2. Calendar events shouldn't play in silent mode. We can test for
  silent mode on the bus, http://bazaar.launchpad.net/~phablet-team
  /telephony-
  service/trunk/view/head:/libtelephonyservice/greetercontacts.cpp has
  an example: getUserValue("com.ubuntu.touch.AccountsService.Sound",
  "SilentMode");

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

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

[Touch-packages] [Bug 1413363] [NEW] bluetooth speaker and suspension issue

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

STEPS:
1. Open settings bluetooth
2. Turn on your blue tooth speaker
3. Pair the speaker
4. Open the music app
5. Play music
6. Pause the music
7. Let the phone suspend
8. After a while it goes into deep sleep and the speaker disconnects
9. Wake the phone press the play button

EXPECTED:
I expected the music to play out of the bluetooth speaker

ACTUAL:
A long pause, then a click then the music plays from the internal speaker.  You 
can no longer get the music to play  from the bluetooth speaker.

Things I've tried:
Reboot the phone re connect to the bt speaker music still plays from the loud 
speaker on the phone.
Turned off the speaker, restarted it still plays through the Loud speaker on 
the phone

WORK AROUND:
Forget the connection. Re pair the device now press play now it works as 
expected.

** Affects: bluez (Ubuntu)
 Importance: High
 Assignee: Mathieu Trudel-Lapierre (mathieu-tl)
 Status: New


** Tags: qa-manual-testing
-- 
bluetooth speaker and suspension issue
https://bugs.launchpad.net/bugs/1413363
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to bluez 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 1413272] Re: Many department names are not translated into Spanish

[Alejandro J. Cura]

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

** Changed in: unity-scope-click (Ubuntu RTM)
 Assignee: (unassigned) => Alejandro J. Cura (alecu)

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Alejandro J. Cura (alecu)

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

Title:
  Many department names are not translated into Spanish

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Click Package metadata search service:
  Fix Released
Status in unity-scope-click package in Ubuntu:
  In Progress
Status in unity-scope-click package in Ubuntu RTM:
  New

Bug description:
  Flash krillin with rtm 205, with --wipe.
  Selected "Spanish-Spain" in the first boot sequence.
  Check the departments of the Apps scope, and the Ubuntu Store scope.

  What should happen?
  - the department names are translated

  What happens?
  - the department names are shown in English

  This is a bug both in the click webservice and in the departments db
  of the preinstalled apps shipped in the device.

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

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

[Touch-packages] [Bug 1413272] Re: Many department names are not translated into Spanish

[Launchpad Bug Tracker]

** Branch linked: lp:~alecu/unity-scope-click/spanish-departments

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

Title:
  Many department names are not translated into Spanish

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Click Package metadata search service:
  Fix Released
Status in unity-scope-click package in Ubuntu:
  In Progress

Bug description:
  Flash krillin with rtm 205, with --wipe.
  Selected "Spanish-Spain" in the first boot sequence.
  Check the departments of the Apps scope, and the Ubuntu Store scope.

  What should happen?
  - the department names are translated

  What happens?
  - the department names are shown in English

  This is a bug both in the click webservice and in the departments db
  of the preinstalled apps shipped in the device.

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

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

[Touch-packages] [Bug 1408029] Re: telephony-service-handler crashing

[Pat McGowan]

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

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

** Changed in: canonical-devices-system-image
Milestone: None => ww05-2015

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

Title:
  telephony-service-handler crashing

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Telephony Service:
  New
Status in telephony-service package in Ubuntu:
  Fix Released
Status in telephony-service package in Ubuntu RTM:
  In Progress

Bug description:
  This was reported by om26er on rtm image and crash report is here:
  https://errors.ubuntu.com/oops/54247740-88c5-11e4-9904-fa163e373683

  It appears the handler is crashing trying to acknowledge a chat
  message, top of stack trace is following:

  StacktraceTop 
  AccountEntry::accountId() const ()
  TextHandler::existingChat(QStringList const&, QString const&) ()
  TextHandler::acknowledgeMessages(QStringList const&, QStringList const&, 
QString const&) ()
  ?? ()
  TelephonyServiceHandlerAdaptor::qt_metacall(QMetaObject::Call, int, void**) ()

  Omer please list the steps to reproduce or the circumstances that
  caused this crash

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

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

[Touch-packages] [Bug 1410961] Re: Incoming calls show the Emergency Call version of the dialer

[Bill Filler]

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

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

Title:
  Incoming calls show the Emergency Call version of the dialer

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Dialer app for Ubuntu Touch:
  New
Status in dialer-app package in Ubuntu:
  Fix Released
Status in telephony-service package in Ubuntu:
  Fix Released
Status in dialer-app package in Ubuntu RTM:
  New
Status in telephony-service package in Ubuntu RTM:
  New

Bug description:
  Both just before  answering and just after hanging up the user sees
  Emergency Call in the header.

  We could go directly to the active call when answering, and directly
  back to welcome screen after hangup.

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

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

[Touch-packages] [Bug 1410989] Re: SSL_connect:unknown state

[Circa Lucid]

Is there a way to get openssl to negotiate the correct cipher suite?
Maybe a retry option? I have squid3 inspecting ssl traffic and it's
hanging on these sites. Or would retrying be something that should be
implemented in squid3?

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

Title:
  SSL_connect:unknown state

Status in openssl package in Ubuntu:
  New

Bug description:
  Running "openssl s_client", I'm getting some websites (www.tm3.com,
  ws.myfax.com) that cause requests to hang. I compiled openssl-1.0.1k
  and it seems to be working now. Is there a more correct fix other than
  compiling the newest openssl?

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

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

[Touch-packages] [Bug 1413269] Re: Qt network being unreliable establishing a connection

[Pat McGowan]

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

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

** Changed in: canonical-devices-system-image
Milestone: None => ww05-2015

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

Title:
  Qt network being unreliable establishing a connection

Status in the base for Ubuntu mobile products:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  Qt network manager is unreliable as it sometimes reports the device
  being not online when in fact it is. This manifest in bugs like bug
  #1409995 or some scopes querying online resources just being empty.

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

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

[Touch-packages] [Bug 1390096] Re: peer picker briefly shows no available apps

[Pat McGowan]

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

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

** Changed in: canonical-devices-system-image
Milestone: None => ww05-2015

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

Title:
  peer picker briefly shows no available apps

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Content sharing/picking infrastructure and service:
  New
Status in content-hub package in Ubuntu:
  Fix Released
Status in content-hub package in Ubuntu RTM:
  New

Bug description:
  build 140 rtm on krillin

  In certain instances, when attempting to save or export from apps, the peer 
picker is first displayed very briefly saying "No apps available" before 
updating to show the correct list of apps. It should not show this message when 
there are apps to be displayed.
  This doesn't always occur, but have certainly seen it happen depending on 
which app I'm using.

  Steps to reproduce:
  - Open gmail
  - create a new message
  - press the attach button

  Expected results:
  - peer picker with list of available apps

  Actual results:
  - peer picker first displaying "No apps" message then changing to list of 
available apps

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

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

[Touch-packages] [Bug 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled

[Yanpas]

If so we are waiting backport of fix to Trusty

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

Title:
  missing PrepareForSleep signal after resuming, causing networking to
  stay disabled

Status in NetworkManager:
  New
Status in wicd:
  New
Status in systemd-shim package in Ubuntu:
  Confirmed
Status in systemd-shim source package in Saucy:
  Won't Fix
Status in systemd-shim source package in Trusty:
  Confirmed

Bug description:
  As per request from bug #1184262, this is a new report, along with
  dbus (to be attached)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: systemd-services 204-0ubuntu19
  Uname: Linux 3.12.0-custom x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Sun Nov 17 20:24:41 2013
  MarkForUpload: True
  SourcePackage: systemd
  UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago)

  SRU INFORMATION:
  FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty 
already)

  Regression potential: Low. Flushing the session bus was introduced in
  version 4 and is obviously bogus as in a system D-BUS service there is
  no session bus. This causes lots of confusing error messages and
  unnecessary overhead like trying to start dbus-launch. Flushing the
  system bus is low-risk, in most cases it's a no-op and it would
  otherwise prevent losing signals after waking up. No known
  regressions.

  TEST CASE: Run several suspend/resume cycles with the lid, session
  indicator menu, and verify that the network comes back up. It is known
  that this fix is necessary but not sufficient, so it is not expected
  to fix all cases. But it should not make things worse, so if network
  now does not come up any more on a machine where it previously worked
  this would count as failure/regression.

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

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

[Touch-packages] [Bug 1410874] Re: Alarm sounds vs Calendar sounds

[Launchpad Bug Tracker]

** Branch linked: lp:~charlesk/indicator-datetime/lp-1410874-alarm-
sounds-vs-calendar-sounds

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

Title:
  Alarm sounds vs Calendar sounds

Status in the base for Ubuntu mobile products:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  In Progress
Status in indicator-datetime package in Ubuntu RTM:
  New

Bug description:
  As discussed with rsalveti and pmcgowan in #phablet on 14 Jan

  There are two issues in the datetime notification code that need to be
  changed.

  1. Right now we only set role=alarm if the sound is looping; ie if it's an 
alarm clock event rather than calendar event.
  Set calendar event role to alert

  2. Calendar events shouldn't play in silent mode. We can test for
  silent mode on the bus, http://bazaar.launchpad.net/~phablet-team
  /telephony-
  service/trunk/view/head:/libtelephonyservice/greetercontacts.cpp has
  an example: getUserValue("com.ubuntu.touch.AccountsService.Sound",
  "SilentMode");

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

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

[Touch-packages] [Bug 1413367] Re: package libc6 2.19-0ubuntu6.5 failed to install/upgrade: cannot copy extracted data for './lib/i386-linux-gnu/libm-2.19.so' to '/lib/i386-linux-gnu/libm-2.19.so.dpkg

[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 eglibc in Ubuntu.
https://bugs.launchpad.net/bugs/1413367

Title:
  package libc6 2.19-0ubuntu6.5 failed to install/upgrade: cannot copy
  extracted data for './lib/i386-linux-gnu/libm-2.19.so' to '/lib/i386
  -linux-gnu/libm-2.19.so.dpkg-new': unexpected end of file or stream

Status in eglibc package in Ubuntu:
  New

Bug description:
  Updating my box

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libc6 2.19-0ubuntu6.5
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  Date: Wed Jan 21 21:14:17 2015
  Dependencies:
   gcc-4.9-base 4.9.1-0ubuntu1
   libc6 2.19-0ubuntu6.5
   libgcc1 1:4.9.1-0ubuntu1
   multiarch-support 2.19-0ubuntu6.4
  DuplicateSignature: package:libc6:2.19-0ubuntu6.5:cannot copy extracted data 
for './lib/i386-linux-gnu/libm-2.19.so' to 
'/lib/i386-linux-gnu/libm-2.19.so.dpkg-new': unexpected end of file or stream
  ErrorMessage: cannot copy extracted data for 
'./lib/i386-linux-gnu/libm-2.19.so' to 
'/lib/i386-linux-gnu/libm-2.19.so.dpkg-new': unexpected end of file or stream
  InstallationDate: Installed on 2013-11-09 (438 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: eglibc
  Title: package libc6 2.19-0ubuntu6.5 failed to install/upgrade: cannot copy 
extracted data for './lib/i386-linux-gnu/libm-2.19.so' to 
'/lib/i386-linux-gnu/libm-2.19.so.dpkg-new': unexpected end of file or stream
  UpgradeStatus: Upgraded to trusty on 2014-05-03 (263 days ago)

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

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

[Touch-packages] [Bug 1413367] [NEW] package libc6 2.19-0ubuntu6.5 failed to install/upgrade: cannot copy extracted data for './lib/i386-linux-gnu/libm-2.19.so' to '/lib/i386-linux-gnu/libm-2.19.so.dp

[smogol]

Public bug reported:

Updating my box

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libc6 2.19-0ubuntu6.5
ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
Uname: Linux 3.13.0-27-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
Date: Wed Jan 21 21:14:17 2015
Dependencies:
 gcc-4.9-base 4.9.1-0ubuntu1
 libc6 2.19-0ubuntu6.5
 libgcc1 1:4.9.1-0ubuntu1
 multiarch-support 2.19-0ubuntu6.4
DuplicateSignature: package:libc6:2.19-0ubuntu6.5:cannot copy extracted data 
for './lib/i386-linux-gnu/libm-2.19.so' to 
'/lib/i386-linux-gnu/libm-2.19.so.dpkg-new': unexpected end of file or stream
ErrorMessage: cannot copy extracted data for 
'./lib/i386-linux-gnu/libm-2.19.so' to 
'/lib/i386-linux-gnu/libm-2.19.so.dpkg-new': unexpected end of file or stream
InstallationDate: Installed on 2013-11-09 (438 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
SourcePackage: eglibc
Title: package libc6 2.19-0ubuntu6.5 failed to install/upgrade: cannot copy 
extracted data for './lib/i386-linux-gnu/libm-2.19.so' to 
'/lib/i386-linux-gnu/libm-2.19.so.dpkg-new': unexpected end of file or stream
UpgradeStatus: Upgraded to trusty on 2014-05-03 (263 days ago)

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

Title:
  package libc6 2.19-0ubuntu6.5 failed to install/upgrade: cannot copy
  extracted data for './lib/i386-linux-gnu/libm-2.19.so' to '/lib/i386
  -linux-gnu/libm-2.19.so.dpkg-new': unexpected end of file or stream

Status in eglibc package in Ubuntu:
  New

Bug description:
  Updating my box

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libc6 2.19-0ubuntu6.5
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  Date: Wed Jan 21 21:14:17 2015
  Dependencies:
   gcc-4.9-base 4.9.1-0ubuntu1
   libc6 2.19-0ubuntu6.5
   libgcc1 1:4.9.1-0ubuntu1
   multiarch-support 2.19-0ubuntu6.4
  DuplicateSignature: package:libc6:2.19-0ubuntu6.5:cannot copy extracted data 
for './lib/i386-linux-gnu/libm-2.19.so' to 
'/lib/i386-linux-gnu/libm-2.19.so.dpkg-new': unexpected end of file or stream
  ErrorMessage: cannot copy extracted data for 
'./lib/i386-linux-gnu/libm-2.19.so' to 
'/lib/i386-linux-gnu/libm-2.19.so.dpkg-new': unexpected end of file or stream
  InstallationDate: Installed on 2013-11-09 (438 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: eglibc
  Title: package libc6 2.19-0ubuntu6.5 failed to install/upgrade: cannot copy 
extracted data for './lib/i386-linux-gnu/libm-2.19.so' to 
'/lib/i386-linux-gnu/libm-2.19.so.dpkg-new': unexpected end of file or stream
  UpgradeStatus: Upgraded to trusty on 2014-05-03 (263 days ago)

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

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

[Touch-packages] [Bug 1410506] Re: MTP looping between start and stopping causing constant ~10% cpu load

[Mathieu Trudel-Lapierre]

The fix for this is now in RTM:

mtp (0.0.4+15.04.20150120~rtm-0ubuntu1) 14.09; urgency=low

  [ Mathieu Trudel-Lapierre ]
  * Adjust start and stop conditions to properly handle USB connection
*and* disconnection, and to do the right thing at boot-time if USB
is connected already.

Closing as Fix Released.

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

** Changed in: mtp (Ubuntu)
 Assignee: Mathieu Trudel-Lapierre (mathieu-tl) => (unassigned)

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

Title:
  MTP looping between start and stopping causing constant ~10% cpu load

Status in the base for Ubuntu mobile products:
  Fix Released
Status in mtp package in Ubuntu:
  Fix Released
Status in mtp package in Ubuntu RTM:
  Fix Released

Bug description:
  When unplugged from USB, I notice when running $ top that init, dbus-
  daemon, mpdecision are constantly using in total ~10% CPU.

  The steps I have performed to cause this:
  1) Ensure the device is off
  2) Plug a USB cable into the device and a computer with MTP support
  3) Boot the device
  4) Unlock the device, run the terminal and the command $ top
  5) Wait until the CPU settles, then unplug the USB cable
  6) Now notice that init, dbus-daemon, mpdecision start using ~10% CPU

  This is the output from running dbus-monitor [0]

  Note that when I plugged my device into a PC the CPU usage reduced
  back to normal, but then when I unplugged it again it increased back
  to ~10% again.

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

  $ system-image-cli -i
  current build number: 161
  device name: mako
  channel: ubuntu-touch/ubuntu-rtm/devel-proposed
  alias: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2015-01-13 18:37:40
  version version: 161
  version ubuntu: 20150113
  version device: 20141119
  version custom: mako-1.1

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

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

[Touch-packages] [Bug 1291359] Re: multiscreen spanning wallpaper does not span on lock screen

[Andrea Azzarone]

** Information type changed from Public Security to Public

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

Title:
  multiscreen spanning wallpaper does not span on lock screen

Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  (It has same look as unity-greeter in lightdm but am given to believe
  lock screen is handled by gnome-screensaver; move if i'm wrong!
  lightdm seems to get it wrong a different way.)

  If, having made a wide wallpaper to span multiple monitors, and having
  set it as your wallpaper with type "Span" in Appearance settings, you
  then go to the new "Lock" screen...

  ... you will see that instead of that wide wallpaper spanning all
  monitors, you get the image scaled down to be shown whole on *each*
  monitor. As shown in screenshot attached.

  It needs to honour the appearance settings in this regard.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-screensaver 3.6.1-0ubuntu10
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar 12 13:02:42 2014
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session session-name 'ubuntu'
   org.gnome.desktop.session idle-delay uint32 300
  InstallationDate: Installed on 2014-03-08 (3 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gnome-screensaver
  UpgradeStatus: Upgraded to trusty on 2014-03-10 (1 days ago)

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

-- 
Mailing list: https://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 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled

[Seth Goldin]

The issue seems be resolved for me in Lubuntu 14.10.

On Wed Jan 21 2015 at 2:01:06 PM Andy Somerville 
wrote:

> @r0lf this is still happening in 14.10/Utopic  should it be reopened
> there?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1252121
>
> Title:
>   missing PrepareForSleep signal after resuming, causing networking to
>   stay disabled
>
> Status in NetworkManager:
>   New
> Status in wicd:
>   New
> Status in systemd-shim package in Ubuntu:
>   Confirmed
> Status in systemd-shim source package in Saucy:
>   Won't Fix
> Status in systemd-shim source package in Trusty:
>   Confirmed
>
> Bug description:
>   As per request from bug #1184262, this is a new report, along with
>   dbus (to be attached)
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 13.10
>   Package: systemd-services 204-0ubuntu19
>   Uname: Linux 3.12.0-custom x86_64
>   ApportVersion: 2.12.5-0ubuntu2.1
>   Architecture: amd64
>   Date: Sun Nov 17 20:24:41 2013
>   MarkForUpload: True
>   SourcePackage: systemd
>   UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago)
>
>   SRU INFORMATION:
>   FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty
> already)
>
>   Regression potential: Low. Flushing the session bus was introduced in
>   version 4 and is obviously bogus as in a system D-BUS service there is
>   no session bus. This causes lots of confusing error messages and
>   unnecessary overhead like trying to start dbus-launch. Flushing the
>   system bus is low-risk, in most cases it's a no-op and it would
>   otherwise prevent losing signals after waking up. No known
>   regressions.
>
>   TEST CASE: Run several suspend/resume cycles with the lid, session
>   indicator menu, and verify that the network comes back up. It is known
>   that this fix is necessary but not sufficient, so it is not expected
>   to fix all cases. But it should not make things worse, so if network
>   now does not come up any more on a machine where it previously worked
>   this would count as failure/regression.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/network-manager/+bug/1252121/+subscriptions
>

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

Title:
  missing PrepareForSleep signal after resuming, causing networking to
  stay disabled

Status in NetworkManager:
  New
Status in wicd:
  New
Status in systemd-shim package in Ubuntu:
  Confirmed
Status in systemd-shim source package in Saucy:
  Won't Fix
Status in systemd-shim source package in Trusty:
  Confirmed

Bug description:
  As per request from bug #1184262, this is a new report, along with
  dbus (to be attached)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: systemd-services 204-0ubuntu19
  Uname: Linux 3.12.0-custom x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Sun Nov 17 20:24:41 2013
  MarkForUpload: True
  SourcePackage: systemd
  UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago)

  SRU INFORMATION:
  FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty 
already)

  Regression potential: Low. Flushing the session bus was introduced in
  version 4 and is obviously bogus as in a system D-BUS service there is
  no session bus. This causes lots of confusing error messages and
  unnecessary overhead like trying to start dbus-launch. Flushing the
  system bus is low-risk, in most cases it's a no-op and it would
  otherwise prevent losing signals after waking up. No known
  regressions.

  TEST CASE: Run several suspend/resume cycles with the lid, session
  indicator menu, and verify that the network comes back up. It is known
  that this fix is necessary but not sufficient, so it is not expected
  to fix all cases. But it should not make things worse, so if network
  now does not come up any more on a machine where it previously worked
  this would count as failure/regression.

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

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

[Touch-packages] [Bug 1291359] Re: multiscreen spanning wallpaper does not span on lock screen

[Bluegrassin]

** Information type changed from Public to Public Security

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

Title:
  multiscreen spanning wallpaper does not span on lock screen

Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  (It has same look as unity-greeter in lightdm but am given to believe
  lock screen is handled by gnome-screensaver; move if i'm wrong!
  lightdm seems to get it wrong a different way.)

  If, having made a wide wallpaper to span multiple monitors, and having
  set it as your wallpaper with type "Span" in Appearance settings, you
  then go to the new "Lock" screen...

  ... you will see that instead of that wide wallpaper spanning all
  monitors, you get the image scaled down to be shown whole on *each*
  monitor. As shown in screenshot attached.

  It needs to honour the appearance settings in this regard.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-screensaver 3.6.1-0ubuntu10
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar 12 13:02:42 2014
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session session-name 'ubuntu'
   org.gnome.desktop.session idle-delay uint32 300
  InstallationDate: Installed on 2014-03-08 (3 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gnome-screensaver
  UpgradeStatus: Upgraded to trusty on 2014-03-10 (1 days ago)

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

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

[Touch-packages] [Bug 1362341] Re: OneTime alarms are not automatically dismissed or delete after they are triggered

[Ubuntu Phone Apps Jenkins Bot]

Fix committed into lp:ubuntu-clock-app at revision 188, scheduled for
release in ubuntu-clock-app, milestone ota-1

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

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

Title:
  OneTime alarms are not automatically dismissed or delete after they
  are triggered

Status in the base for Ubuntu mobile products:
  Fix Released
Status in The Date and Time Indicator:
  Fix Released
Status in Clock application for Ubuntu devices:
  Fix Committed
Status in indicator-datetime package in Ubuntu:
  Fix Released
Status in ubuntu-clock-app package in Ubuntu:
  New
Status in indicator-datetime package in Ubuntu RTM:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Create a one time alarm to ring in a few minutes
  2. Let the alarm ring
  3. Dismiss the alarm

  What happens:
  The OneTime alarm is still shown as enabled and as a result shows the wrong 
status in the clock app. The alarm is no longer shown in the indicator-datetime.

  What should happen:
  The OneTime alarm is either disabled or deleted from the alarm model.

  The clock app cannot disable the alarm since most likely the clock app
  is not even open at the time the alarm is triggered. Since the alarm
  is no longer shown in the indicator-datetime, my intuition tells me
  that indicator-datetime and EDS did its job. Its now up to the SDK
  Alarms API to update the alarm model correctly.

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

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

[Touch-packages] [Bug 298567] Re: No Permission to Eject CD

[Ken Sharp]

** Tags added: i386 intrepid precise

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

Title:
  No Permission to Eject CD

Status in eject package in Ubuntu:
  New

Bug description:
  Binary package hint: eject

  I have two logins running.  The one in the background is idle.  When I
  am in my current login and inserting CD's, copying contents to home
  and then ejecting the CD, it will often report I do not have
  permissions to eject the CD.

  When I look at the details it shows the other login with permission.
  I then switch to find the CD folder open on that desktop.

  I have to force it to eject from my current login with sudo eject.  I
  would think whichever is the currently active login, that it would the
  permissions to eject/umount the CD.

  I am running Intrepid 2.6.27-7.

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 8.10
  ExecutablePath: /usr/bin/yelp
  NonfreeKernelModules: nvidia
  Package: yelp 2.24.0-0ubuntu2
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: yelp
  Uname: Linux 2.6.27-7-generic i686

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

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

[Touch-packages] [Bug 1413343] Re: lxc-create debug output is broken or useless

[Serge Hallyn]

You need to specify a template for the container to create.  For
instance,

lxc-create -t download -n buildbox -- -d ubuntu -r trusty -a amd64

In newer releases, you do get a better error message:

# lxc-create -n b1
A template must be specified.
Use "none" if you really want a container without a rootfs.


** Changed in: lxc (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  lxc-create debug output is broken or useless

Status in lxc package in Ubuntu:
  Fix Released

Bug description:
  Can't create container and debug output doesn't explain anything:

  $ lxc-create --logpriority=DEBUG -n buildbox -o here.log
  lxc-create: Error creating container buildbox
  $ cat here.log 
   lxc-create 1421867190.847 WARN lxc_log - lxc_log_init called with 
log already initialized
   lxc-create 1421867190.847 ERRORlxc_create_ui - Error creating 
container buildbox

  I doubt that --logpriority option is processed at all:

  $ lxc-create --logpriority=wat -n buildbox -o here.log
  lxc-create: Error creating container buildbox

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lxc 1.0.6-0ubuntu0.1
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: i386
  CurrentDesktop: Unity
  Date: Wed Jan 21 21:55:50 2015
  InstallationDate: Installed on 2012-03-12 (1045 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
  KernLog:
   Jan 21 07:40:13 SONiC kernel: [82266.453659] type=1400 
audit(1421815213.422:96): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=17589 
comm="apparmor_parser"
   Jan 21 07:40:13 SONiC kernel: [82266.453673] type=1400 
audit(1421815213.422:97): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd" pid=17589 comm="apparmor_parser"
   Jan 21 07:40:13 SONiC kernel: [82266.454329] type=1400 
audit(1421815213.422:98): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd" pid=17589 comm="apparmor_parser"
  SourcePackage: lxc
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (277 days ago)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

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

[Touch-packages] [Bug 726785] Re: Cannot eject CDROM with bad media inserted - IO error

[Ken Sharp]

** Tags added: i386 precise

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

Title:
  Cannot eject CDROM with bad media inserted - IO error

Status in eject package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: eject

  I have media which cannot be read
  [ 7707.154066] Buffer I/O error on device sr0, logical block 1024
  [ 7707.154070] Buffer I/O error on device sr0, logical block 1025
  During read error I cant eject media even with eject command.
  I know about /proc/sys/dev/cdrom/lock and /proc/sys/dev/cdrom/autoclose 
variables but they need to be set before inserting media, and only way to fast 
remove is hard reset system. Eject should have --force option not as a feature 
but as solution of critical bug - in my case Cdrom gave strange sound and there 
was a risk it will brake.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: eject 2.1.5+deb1+cvs20081104-7
  Uname: Linux 2.6.34-02063407-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Mon Feb 28 21:43:17 2011
  EcryptfsInUse: Yes
  ProcEnviron:
   LANGUAGE=pl_PL
   LANG=pl_PL.utf8
   SHELL=/bin/bash
  SourcePackage: eject

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

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

[Touch-packages] [Bug 726785] Re: Cannot eject CDROM with bad media inserted - IO error

[Launchpad Bug Tracker]

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

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

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

Title:
  Cannot eject CDROM with bad media inserted - IO error

Status in eject package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: eject

  I have media which cannot be read
  [ 7707.154066] Buffer I/O error on device sr0, logical block 1024
  [ 7707.154070] Buffer I/O error on device sr0, logical block 1025
  During read error I cant eject media even with eject command.
  I know about /proc/sys/dev/cdrom/lock and /proc/sys/dev/cdrom/autoclose 
variables but they need to be set before inserting media, and only way to fast 
remove is hard reset system. Eject should have --force option not as a feature 
but as solution of critical bug - in my case Cdrom gave strange sound and there 
was a risk it will brake.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: eject 2.1.5+deb1+cvs20081104-7
  Uname: Linux 2.6.34-02063407-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Mon Feb 28 21:43:17 2011
  EcryptfsInUse: Yes
  ProcEnviron:
   LANGUAGE=pl_PL
   LANG=pl_PL.utf8
   SHELL=/bin/bash
  SourcePackage: eject

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

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

[Touch-packages] [Bug 726785] Re: Cannot eject CDROM with bad media inserted - IO error

[Ken Sharp]

Confirming.

[21281.116107] Volume set (in), Read cd: be 00 00 02 3d 13 00 00 01 f8 00 00
[21281.116130] ata2.00: cmd a0/01:00:00:30:09/00:00:00:00:00/a0 tag 19 dma 2352 
in
[21281.116130]  res 40/00:02:00:38:00/00:00:00:00:00/a0 Emask 0x4 
(timeout)
[21281.116135] ata2.00: status: { DRDY }
[21286.156034] ata2: link is slow to respond, please be patient (ready=0)
[21291.140036] ata2: device not ready (errno=-16), forcing hardreset
[21291.140049] ata2: soft resetting link
[21296.336067] ata2: link is slow to respond, please be patient (ready=0)
[21301.152050] ata2: SRST failed (errno=-16)
[21301.152067] ata2: soft resetting link
[21306.348090] ata2: link is slow to respond, please be patient (ready=0)
[21311.164039] ata2: SRST failed (errno=-16)
[21311.164053] ata2: soft resetting link
[21316.360103] ata2: link is slow to respond, please be patient (ready=0)
[21346.208037] ata2: SRST failed (errno=-16)
[21346.208052] ata2: soft resetting link
[21351.236034] ata2: SRST failed (errno=-16)
[21351.247334] ata2: reset failed, giving up
[21351.247349] ata2.00: disabled
[21351.247357] ata2.01: disabled
[21351.247441] ata2: EH complete

$ sudo eject -v /dev/sr0
eject: device name is `/dev/sr0'
eject: expanded name is `/dev/sr0'
eject: `/dev/sr0' is not mounted
eject: `/dev/sr0' is not a mount point
eject: `/dev/sr0' is not a multipartition device
eject: trying to eject `/dev/sr0' using CD-ROM eject command
eject: CD-ROM eject command failed
eject: trying to eject `/dev/sr0' using SCSI commands
eject: SCSI eject failed
eject: trying to eject `/dev/sr0' using floppy eject command
eject: floppy eject command failed
eject: trying to eject `/dev/sr0' using tape offline command
eject: tape offline command failed
eject: unable to eject, last error: Inappropriate ioctl for device

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

Title:
  Cannot eject CDROM with bad media inserted - IO error

Status in eject package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: eject

  I have media which cannot be read
  [ 7707.154066] Buffer I/O error on device sr0, logical block 1024
  [ 7707.154070] Buffer I/O error on device sr0, logical block 1025
  During read error I cant eject media even with eject command.
  I know about /proc/sys/dev/cdrom/lock and /proc/sys/dev/cdrom/autoclose 
variables but they need to be set before inserting media, and only way to fast 
remove is hard reset system. Eject should have --force option not as a feature 
but as solution of critical bug - in my case Cdrom gave strange sound and there 
was a risk it will brake.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: eject 2.1.5+deb1+cvs20081104-7
  Uname: Linux 2.6.34-02063407-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Mon Feb 28 21:43:17 2011
  EcryptfsInUse: Yes
  ProcEnviron:
   LANGUAGE=pl_PL
   LANG=pl_PL.utf8
   SHELL=/bin/bash
  SourcePackage: eject

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

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

[Touch-packages] [Bug 1412916] Re: evince: Bad PDF rendering: invalid font scale

[Charles Baylis]

I would like this bug to be considered for a Stable Release Update to
14.04 (and 14.10 if applicable)

[Impact]

 * Many PDFs do not display correctly, including the boarding passes
from a major European airline

 * Printing a boarding pass is a common simple task which users expect
to work, and therefore should be fixed in the stable release.

 * see upstream bug report for discussion about the mechanism of the
fix.

[Test Case]

 * attempt to view the test case in the linked upstream bug using
'evince attachment.pdf'

 * observe corrupted text displayed

[Regression Potential]

 * theoretically, other PDFs which currently display correctly could be
displayed incorrectly after this change, but is intended to emulate
acroread, so this is unlikely.

 * patch has been reviewed and committed upstream, so should be safe

[Other Info]
 
 * none

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

Title:
  evince: Bad PDF rendering: invalid font scale

Status in Poppler:
  Fix Released
Status in poppler package in Ubuntu:
  Fix Released

Bug description:
  Evince in ubuntu 14.04 (3.10.3-0ubuntu10.1) suffers from this bug:
  https://www.libreoffice.org/bugzilla/show_bug.cgi?id=78042

  The test case which is attached to the upstream bug demonstrates the
  problem with Evince in Ubuntu.

  Hopefully, the patch attached to the upstream bug report would fix the
  problem in ubuntu.

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

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

[Touch-packages] [Bug 1320788] Re: USSD code result shows useless Cancel button

[Tiago Salem Herrmann]

When we first implemented this feature we tried to use only one button,
but the snap decision wouldn't allow us to place only one button in the
bubble. Not sure if that is currently possible.

USSD must be a modal notification as per GSM spec and should not
timeout. It requires an interaction from users in order to go away. And
IIRC, regular on screen notification also do not support that.

We ended up adding the cancel button as a workaround. The right fix in
my opinion would be allowing snap decisions with only one action button.

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

Title:
  USSD code result shows useless Cancel button

Status in Dialer app for Ubuntu Touch:
  Confirmed
Status in dialer-app package in Ubuntu:
  Confirmed

Bug description:
  Hi there,

  This is on T-Mobile with devel build #28.

  When running USSD code #225# to get the account balance, I get a nice
  popup with the resulting text from T-Mobile, but it has both Ok and
  Cancel buttons which do the same thing.  The Cancel button should be
  removed.

  Cheers,

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

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

[Touch-packages] [Bug 1330770] Re: click packages rely upon tls for integrity and authenticity

[Ken VanDine]

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

** Changed in: ubuntu-system-settings (Ubuntu RTM)
   Status: New => Confirmed

** Changed in: ubuntu-system-settings (Ubuntu RTM)
   Importance: Undecided => Critical

** Changed in: ubuntu-system-settings (Ubuntu RTM)
 Assignee: (unassigned) => Manuel de la Peña (mandel)

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

Title:
  click packages rely upon tls for integrity and authenticity

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Click Package metadata search service:
  Fix Released
Status in Online service used by software center:
  Fix Released
Status in click package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in unity-scope-click package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu RTM:
  Confirmed

Bug description:
  Hello, I just completed a quick review of the click source and the
  unity-scope-click source and behaviours, and found some opportunities
  for improvement.

  Debian, and Ubuntu, rely upon signed repository files with
  cryptographic hashes of packages to provide both integrity and
  authenticity checks for the packages hosted on that repository.

  The click framework and the unity-scope-click discovery and
  installation tool do not use signed repository files, nor do they have
  signatures of any sort on downloaded packages. The only integrity and
  authenticity checks are provided by the use of HTTPS.  The click
  verify command will check files within the archive against MD5sums
  stored inside the archive but the click verify command is not used
  during package installation. (This is suitable for validating
  integrity against accidental changes only.)

  While it appears that unity-scope-click properly uses HTTPS to
  download package metadata and packages, HTTPS alone is insufficient
  for our needs:

  - Someone in a position to create new certificates at any of several
  hundred certificate authorities could create certificates purporting
  to be our update servers. This actual problem has been discovered in
  the wild with several certificate authorities issuing wild-card
  certificates or even certificates with signing authority.

  - X.509 is extremely complicated; TLS is extremely complicated. Flaws
  in both are inevitable.

  - HTTPS prevents the use of caching.

  - HTTPS only 'works' for data-in-motion; it is useless for data-at-
  rest integrity and authenticity checks.

  I have not yet reviewed the tools that application authors will use to
  upload their packages to our distribution servers but note in passing
  that most of these issues are also issues for adding packages to our
  update servers -- packages in flight within our network can be
  corrupted for many reasons, packages on disk can be corrupted for many
  reasons. A signature mechanism can protect against internal network
  faults, storage faults, and provide assurance months or years later
  that an uploaded package was uploaded by someone in control of a
  corresponding private key.

  Thanks

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

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

[Touch-packages] [Bug 1385572] Re: gnome-session not shutting down cleanly

[Pietro Gagliardi (andlabs/pietro10)]

I don't know how much this comment would contribute to this bug but I
can at least confirm that the behavior described here is a possible
reason why this is going on, as judged by my comment to bug 1236749
here: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1236749/comments/77 Specifically, for me the bug only
occurred if I rebooted cleanly, but not if I forced the machine off.

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

Title:
  gnome-session not shutting down cleanly

Status in Ubuntu GNOME:
  New
Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  We have had reports going back to 13.10 that gnome-shell extensions
  are disabled after restart (LP: #1236749), I've only just managed to
  reproduce this and have discovered that gnome-session is not shutting
  down cleanly.

  Basically, X gets shutdown, which causes gnome-shell to abort,
  following this gnome-session tries to respawn gnome-shell which fails
  and due to this failure disables all shell extensions. I don't know
  enough about upstart to really understand what is going on but it
  appears this also affects unity and it just hasnt been noticed since
  there are probably no such side-effects happening there.

  Filing this against upstart since this is not reproducible when using
  systemd init, though it may well be a bug in gnome-session, but
  related to upstart user sessions.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: upstart 1.13.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
  Uname: Linux 3.16.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Oct 25 14:05:24 2014
  InstallationDate: Installed on 2012-09-23 (762 days ago)
  InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha 
amd64(20120922)
  SourcePackage: upstart
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: Session
  UpstartRunningSessionCount: 1
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: init (upstart 1.13.2)

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

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

[Touch-packages] [Bug 1236749] Re: Gnome shell extensions disabled at every startup

[Pietro Gagliardi (andlabs/pietro10)]

The problem with this bug is that it doesn't exhibit itself consistently
or predictably.

On my previous laptop's Ubuntu GNOME 14.10 setup, reboots worked fine
until some point (a month after installing?), at which point this
behavior started happening... but only on a clean reboot. If I killed
power to my laptop by force instead, extensions would stay. (This
probably further confirms the hypothesis in bug 1385572.) The previous
laptop was a Dell Precision M6400 with a Core 2 Duo CPU and Quadro FX
2700M graphics. I forget if I tried nVidia drivers or not.

So far, I have not seen this happen with clean reboots on my current
laptop. It is a Lenovo G60-45 with the following combined CPU/GPU: "AMD
A6-6310 APU with AMD Radeon R4 Graphics". I mainly use the AMD drivers
due to freezing issues with mesa; I forget if this happened with mesa as
well or not. This is still with Ubuntu GNOME 14.10.

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

Title:
  Gnome shell extensions disabled at every startup

Status in Ubuntu GNOME:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  Since gnome-shell 3.10, my extensions are disabled by default at every boot.
  I need to launch Tweak Tool to enable theme by hand every time.

  Both pre-installed extensions ( AlternateTab) and user-installed ones
  (top-icons)

  Step to reproduce :
  Enable an extension in Tweak Tool ( Alternate Tab for example)
  reboot computer,
  open Tweak Tool : Alternate tab is disabled.

  Running on Ubuntu 13.10
  GNOME Shell 3.10.0.1
  gnome-tweak-tool 3.10..0-0ubuntu1-saucy1

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

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

[Touch-packages] [Bug 1413343] [NEW] lxc-create debug output is broken or useless

[anatoly techtonik]

Public bug reported:

Can't create container and debug output doesn't explain anything:

$ lxc-create --logpriority=DEBUG -n buildbox -o here.log
lxc-create: Error creating container buildbox
$ cat here.log 
 lxc-create 1421867190.847 WARN lxc_log - lxc_log_init called with log 
already initialized
 lxc-create 1421867190.847 ERRORlxc_create_ui - Error creating 
container buildbox

I doubt that --logpriority option is processed at all:

$ lxc-create --logpriority=wat -n buildbox -o here.log
lxc-create: Error creating container buildbox

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: lxc 1.0.6-0ubuntu0.1
ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
Uname: Linux 3.13.0-44-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: i386
CurrentDesktop: Unity
Date: Wed Jan 21 21:55:50 2015
InstallationDate: Installed on 2012-03-12 (1045 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
KernLog:
 Jan 21 07:40:13 SONiC kernel: [82266.453659] type=1400 
audit(1421815213.422:96): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=17589 
comm="apparmor_parser"
 Jan 21 07:40:13 SONiC kernel: [82266.453673] type=1400 
audit(1421815213.422:97): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd" pid=17589 comm="apparmor_parser"
 Jan 21 07:40:13 SONiC kernel: [82266.454329] type=1400 
audit(1421815213.422:98): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd" pid=17589 comm="apparmor_parser"
SourcePackage: lxc
UpgradeStatus: Upgraded to trusty on 2014-04-18 (277 days ago)
defaults.conf:
 lxc.network.type = veth
 lxc.network.link = lxcbr0
 lxc.network.flags = up
 lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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


** Tags: apport-bug i386 trusty

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

Title:
  lxc-create debug output is broken or useless

Status in lxc package in Ubuntu:
  New

Bug description:
  Can't create container and debug output doesn't explain anything:

  $ lxc-create --logpriority=DEBUG -n buildbox -o here.log
  lxc-create: Error creating container buildbox
  $ cat here.log 
   lxc-create 1421867190.847 WARN lxc_log - lxc_log_init called with 
log already initialized
   lxc-create 1421867190.847 ERRORlxc_create_ui - Error creating 
container buildbox

  I doubt that --logpriority option is processed at all:

  $ lxc-create --logpriority=wat -n buildbox -o here.log
  lxc-create: Error creating container buildbox

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lxc 1.0.6-0ubuntu0.1
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: i386
  CurrentDesktop: Unity
  Date: Wed Jan 21 21:55:50 2015
  InstallationDate: Installed on 2012-03-12 (1045 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
  KernLog:
   Jan 21 07:40:13 SONiC kernel: [82266.453659] type=1400 
audit(1421815213.422:96): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=17589 
comm="apparmor_parser"
   Jan 21 07:40:13 SONiC kernel: [82266.453673] type=1400 
audit(1421815213.422:97): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd" pid=17589 comm="apparmor_parser"
   Jan 21 07:40:13 SONiC kernel: [82266.454329] type=1400 
audit(1421815213.422:98): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd" pid=17589 comm="apparmor_parser"
  SourcePackage: lxc
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (277 days ago)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

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