date:20150123

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

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

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

Title:
  Race condition at user login

Status in modemmanager package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: modemmanager

  unr 10.10 netbook i386
  patchlvl 26.03.11

  If a user login to the system, first modemmanager aks for the 3g pin. 
Theirafter networkmanager fires up, it has the pin in the keyring but to late 
for authentification.  So the user has to enter the 3g pin every time.
  Affects unr10.10, lubuntu 10.10 and has worked well in both 10.04 releases. 
This is a race condition.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: modemmanager 0.4+git.20100809t153145.be28089-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.35-28.49-genusername 2.6.35.11
  Uname: Linux 2.6.35-28-generic i686
  Architecture: i386
  Date: Sat Mar 26 11:18:16 2011
  EcryptfsInUse: Yes
  ProcEnviron:
   LANG=de_DE.utf8
   SHELL=/bin/bash
  SourcePackage: modemmanager

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

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

[Touch-packages] [Bug 1399595] Re: systemd is activating swap twice

2015-01-23 Thread Tom H

Thanks again for looking into this.

systemd-gpt-auto-generator output attached.

$ cat /etc/fstab 
# filesystem   mountpoint type options   dump pass
# sda1
UUID=6151-AFD6/boot/efi   vfat defaults  01
# sda2
UUID=b51ee688-137c-47ec-9635-b69434b4e1f8 /   ext4 defaults  01
# sda3
UUID=73d341f1-eedc-43fc-9e53-ba4194dae3fb noneswap sw00

(Until your post yesterday, I've had sda3 commented out.)


** Attachment added: "result2.tar"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1399595/+attachment/4304111/+files/result2.tar

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

Title:
  systemd is activating swap twice

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  systemd is activating swap twice, via its sda name and its uuid.

  It looks like it's because two swap units are being generated.

  
  # journalctl | grep swap | grep -v unit_create_cgroups
  Dec 05 04:30:40 yoga.lenovo systemd[1]: Activating swap Swap Partition...
  Dec 05 04:30:40 yoga.lenovo systemd[1]: Activating swap 
/dev/disk/by-uuid/73d341f1-eedc-43fc-9e53-ba4194dae3fb...
  Dec 05 04:30:40 yoga.lenovo swapon[396]: swapon: 
/dev/disk/by-uuid/73d341f1-eedc-43fc-9e53-ba4194dae3fb: swapon failed: Device 
or resource busy
  Dec 05 04:30:40 yoga.lenovo systemd[1]: 
dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap swap 
process exited, code=exited status=255
  Dec 05 04:30:40 yoga.lenovo systemd[1]: Failed to activate swap 
/dev/disk/by-uuid/73d341f1-eedc-43fc-9e53-ba4194dae3fb.
  Dec 05 04:30:40 yoga.lenovo systemd[1]: Unit 
dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap 
entered failed state.
  Dec 05 04:30:40 yoga.lenovo systemd[1]: Activated swap Swap Partition.
  Dec 05 04:30:40 yoga.lenovo kernel: Adding 8298492k swap on /dev/sda3.  
Priority:-1 extents:1 across:8298492k SSFS

  
  # systemctl status dev-sda3.swap 
  ● dev-sda3.swap - Swap Partition
 Loaded: loaded (/run/systemd/generator.late/dev-sda3.swap)
 Active: active since Fri 2014-12-05 04:30:40 EST; 27min ago
   What: /dev/sda3
   Docs: man:systemd-gpt-auto-generator(8)
Process: 395 ExecActivate=/sbin/swapon /dev/sda3 (code=exited, 
status=0/SUCCESS)

  Dec 05 04:30:40 yoga.lenovo systemd[1]: Activating swap Swap Partition...
  Dec 05 04:30:40 yoga.lenovo systemd[1]: Activated swap Swap Partition.

  
  # systemctl status 
dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap
  ● dev-disk-byx2duuid-73d341f1x2deedcx2d43fcx2d9e53x2dba4194dae3fb.swap - 
/dev/disk/byx2duuid/73d341f1x2deedcx2d43fcx2d9e53x2dba4194dae3fb
 Loaded: loaded
 Active: inactive (dead)
   What: /dev/disk/byx2duuid/73d341f1x2deedcx2d43fcx2d9e53x2dba4194dae3fb

  
  # swapon -s
  Filename  TypeSizeUsedPriority
  /dev/sda3 partition   8298492 0   
-1

  
  # blkid /dev/sda3
  /dev/sda3: UUID="73d341f1-eedc-43fc-9e53-ba4194dae3fb" TYPE="swap" 
PARTUUID="63a48c8a-8c88-482c-9577-50060d5afcb0"

  
  # find /run -name "*73d341f1*"
  
/run/systemd/generator/swap.target.wants/dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap
  
/run/systemd/generator/dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap
  /run/udev/links/\x2fdisk\x2fby-uuid\x2f73d341f1-eedc-43fc-9e53-ba4194dae3fb

  
  # find /run -name "*sda3*"
  /run/systemd/generator.late/swap.target.wants/dev-sda3.swap
  /run/systemd/generator.late/dev-sda3.swap

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 217-3ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: No such file 
or directory
  Date: Fri Dec  5 04:51:30 2014
  MachineType: LENOVO 20266
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic 
root=UUID=b51ee688-137c-47ec-9635-b69434b4e1f8 ro init=/lib/systemd/systemd 
ipv6.disable_ipv6=1
  SourcePackage: systemd
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN35WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN35WW:bd03/25/2014:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr319000

[Touch-packages] [Bug 1413791] Re: Full Left swipe does not come back to app scope after having searched an app

2015-01-23 Thread Albert Astals Cid

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

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

Title:
  Full Left swipe does not come back to app scope after having searched
  an app

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

Bug description:
  device nexus 4 mako

  os Ubuntu 15.04 (r73)

  I love the left swipe, being able to go back to the main menu by doing a full 
swipe to the left is great.
  However my list of apps has considerably increased \o/ and i usually search 
them via the search button and this is where the problem lies. A full left 
swipe does not bring me back to the main menu but to the  last searched app if 
i opened my app through the search menu

  As an example
  Step 1 go to apps scope on main menu
  step 2 search music app via the search button ( type music)
  step 3 open music app
  step 4 do a full left swippe

  I should expect to being brought back to app scope.
  ==> Full left swipe brings me back to results of step 2

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

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

[Touch-packages] [Bug 1413909] [NEW] [photos] tend to scroll to top-left corner when pinch-zooming on an image

2015-01-23 Thread Sebastien Bacher

Public bug reported:

(reported first as bug #1413300 which stated it being an unity8 issue)

Using rtm 204 on krillin
- go to the photos lens
- click on an image
- pinch somewhere in the image to zoom

often the view scrolls to the top-left rather than staying on the part
you zoomed

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

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

Title:
   [photos] tend to scroll to top-left corner when pinch-zooming on an
  image

Status in unity8 package in Ubuntu:
  New

Bug description:
  (reported first as bug #1413300 which stated it being an unity8 issue)

  Using rtm 204 on krillin
  - go to the photos lens
  - click on an image
  - pinch somewhere in the image to zoom

  often the view scrolls to the top-left rather than staying on the part
  you zoomed

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

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

[Touch-packages] [Bug 1399595] Re: systemd is activating swap twice

Thanks for the additional data, that helps a lot. I'll forward this to
upstream now. I have an idea how to fix that, but I'd like to discuss it
upstream first.

> (Until your post yesterday, I've had sda3 commented out.)

Was that only in response to that bug? It would be weird if that bug
would still happen even if you have swap commented out in /etc/fstab --
that would mean the fstab generator wouldn't recognize comments or so.
Can you confirm that this is not the case?

Thanks!

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

** Changed in: systemd (Ubuntu)
   Status: Incomplete => Triaged

** Summary changed:

- systemd is activating swap twice
+ systemd is activating swap twice, through both fstab and gpt generators

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

Title:
  systemd is activating swap twice, through both fstab and gpt
  generators

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  systemd is activating swap twice, via its sda name and its uuid.

  It looks like it's because two swap units are being generated.

  
  # journalctl | grep swap | grep -v unit_create_cgroups
  Dec 05 04:30:40 yoga.lenovo systemd[1]: Activating swap Swap Partition...
  Dec 05 04:30:40 yoga.lenovo systemd[1]: Activating swap 
/dev/disk/by-uuid/73d341f1-eedc-43fc-9e53-ba4194dae3fb...
  Dec 05 04:30:40 yoga.lenovo swapon[396]: swapon: 
/dev/disk/by-uuid/73d341f1-eedc-43fc-9e53-ba4194dae3fb: swapon failed: Device 
or resource busy
  Dec 05 04:30:40 yoga.lenovo systemd[1]: 
dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap swap 
process exited, code=exited status=255
  Dec 05 04:30:40 yoga.lenovo systemd[1]: Failed to activate swap 
/dev/disk/by-uuid/73d341f1-eedc-43fc-9e53-ba4194dae3fb.
  Dec 05 04:30:40 yoga.lenovo systemd[1]: Unit 
dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap 
entered failed state.
  Dec 05 04:30:40 yoga.lenovo systemd[1]: Activated swap Swap Partition.
  Dec 05 04:30:40 yoga.lenovo kernel: Adding 8298492k swap on /dev/sda3.  
Priority:-1 extents:1 across:8298492k SSFS

  
  # systemctl status dev-sda3.swap 
  ● dev-sda3.swap - Swap Partition
 Loaded: loaded (/run/systemd/generator.late/dev-sda3.swap)
 Active: active since Fri 2014-12-05 04:30:40 EST; 27min ago
   What: /dev/sda3
   Docs: man:systemd-gpt-auto-generator(8)
Process: 395 ExecActivate=/sbin/swapon /dev/sda3 (code=exited, 
status=0/SUCCESS)

  Dec 05 04:30:40 yoga.lenovo systemd[1]: Activating swap Swap Partition...
  Dec 05 04:30:40 yoga.lenovo systemd[1]: Activated swap Swap Partition.

  
  # systemctl status 
dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap
  ● dev-disk-byx2duuid-73d341f1x2deedcx2d43fcx2d9e53x2dba4194dae3fb.swap - 
/dev/disk/byx2duuid/73d341f1x2deedcx2d43fcx2d9e53x2dba4194dae3fb
 Loaded: loaded
 Active: inactive (dead)
   What: /dev/disk/byx2duuid/73d341f1x2deedcx2d43fcx2d9e53x2dba4194dae3fb

  
  # swapon -s
  Filename  TypeSizeUsedPriority
  /dev/sda3 partition   8298492 0   
-1

  
  # blkid /dev/sda3
  /dev/sda3: UUID="73d341f1-eedc-43fc-9e53-ba4194dae3fb" TYPE="swap" 
PARTUUID="63a48c8a-8c88-482c-9577-50060d5afcb0"

  
  # find /run -name "*73d341f1*"
  
/run/systemd/generator/swap.target.wants/dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap
  
/run/systemd/generator/dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap
  /run/udev/links/\x2fdisk\x2fby-uuid\x2f73d341f1-eedc-43fc-9e53-ba4194dae3fb

  
  # find /run -name "*sda3*"
  /run/systemd/generator.late/swap.target.wants/dev-sda3.swap
  /run/systemd/generator.late/dev-sda3.swap

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 217-3ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: No such file 
or directory
  Date: Fri Dec  5 04:51:30 2014
  MachineType: LENOVO 20266
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic 
root=UUID=b51ee688-137c-47ec-9635-b69434b4e1f8 ro init=/lib/systemd/systemd 
ipv6.disable_ipv6=1
  SourcePackage: systemd
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN35WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENO

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

Sorry, misunderstanding. I restored the previous tags, which seem to be
correct.

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

-- 
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 1399595] Re: systemd is activating swap twice, through both fstab and gpt generators

Forwarded to http://lists.freedesktop.org/archives/systemd-
devel/2015-January/027314.html

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

Title:
  systemd is activating swap twice, through both fstab and gpt
  generators

Status in systemd package in Ubuntu:
  Triaged
Status in systemd package in Debian:
  Unknown

Bug description:
  systemd is activating swap twice, via its sda name and its uuid.

  It looks like it's because two swap units are being generated.

  
  # journalctl | grep swap | grep -v unit_create_cgroups
  Dec 05 04:30:40 yoga.lenovo systemd[1]: Activating swap Swap Partition...
  Dec 05 04:30:40 yoga.lenovo systemd[1]: Activating swap 
/dev/disk/by-uuid/73d341f1-eedc-43fc-9e53-ba4194dae3fb...
  Dec 05 04:30:40 yoga.lenovo swapon[396]: swapon: 
/dev/disk/by-uuid/73d341f1-eedc-43fc-9e53-ba4194dae3fb: swapon failed: Device 
or resource busy
  Dec 05 04:30:40 yoga.lenovo systemd[1]: 
dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap swap 
process exited, code=exited status=255
  Dec 05 04:30:40 yoga.lenovo systemd[1]: Failed to activate swap 
/dev/disk/by-uuid/73d341f1-eedc-43fc-9e53-ba4194dae3fb.
  Dec 05 04:30:40 yoga.lenovo systemd[1]: Unit 
dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap 
entered failed state.
  Dec 05 04:30:40 yoga.lenovo systemd[1]: Activated swap Swap Partition.
  Dec 05 04:30:40 yoga.lenovo kernel: Adding 8298492k swap on /dev/sda3.  
Priority:-1 extents:1 across:8298492k SSFS

  
  # systemctl status dev-sda3.swap 
  ● dev-sda3.swap - Swap Partition
 Loaded: loaded (/run/systemd/generator.late/dev-sda3.swap)
 Active: active since Fri 2014-12-05 04:30:40 EST; 27min ago
   What: /dev/sda3
   Docs: man:systemd-gpt-auto-generator(8)
Process: 395 ExecActivate=/sbin/swapon /dev/sda3 (code=exited, 
status=0/SUCCESS)

  Dec 05 04:30:40 yoga.lenovo systemd[1]: Activating swap Swap Partition...
  Dec 05 04:30:40 yoga.lenovo systemd[1]: Activated swap Swap Partition.

  
  # systemctl status 
dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap
  ● dev-disk-byx2duuid-73d341f1x2deedcx2d43fcx2d9e53x2dba4194dae3fb.swap - 
/dev/disk/byx2duuid/73d341f1x2deedcx2d43fcx2d9e53x2dba4194dae3fb
 Loaded: loaded
 Active: inactive (dead)
   What: /dev/disk/byx2duuid/73d341f1x2deedcx2d43fcx2d9e53x2dba4194dae3fb

  
  # swapon -s
  Filename  TypeSizeUsedPriority
  /dev/sda3 partition   8298492 0   
-1

  
  # blkid /dev/sda3
  /dev/sda3: UUID="73d341f1-eedc-43fc-9e53-ba4194dae3fb" TYPE="swap" 
PARTUUID="63a48c8a-8c88-482c-9577-50060d5afcb0"

  
  # find /run -name "*73d341f1*"
  
/run/systemd/generator/swap.target.wants/dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap
  
/run/systemd/generator/dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap
  /run/udev/links/\x2fdisk\x2fby-uuid\x2f73d341f1-eedc-43fc-9e53-ba4194dae3fb

  
  # find /run -name "*sda3*"
  /run/systemd/generator.late/swap.target.wants/dev-sda3.swap
  /run/systemd/generator.late/dev-sda3.swap

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 217-3ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: No such file 
or directory
  Date: Fri Dec  5 04:51:30 2014
  MachineType: LENOVO 20266
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic 
root=UUID=b51ee688-137c-47ec-9635-b69434b4e1f8 ro init=/lib/systemd/systemd 
ipv6.disable_ipv6=1
  SourcePackage: systemd
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN35WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN35WW:bd03/25/2014:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.systemd.journald.conf: 2014-10-17T14:43:13.493155

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

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

[Touch-packages] [Bug 1399595] Re: systemd is activating swap twice, through both fstab and gpt generators

2015-01-23 Thread Tom H

Yes. I commented out sda3 in order to suppress the errors. (Swap was
mounted nonetheless.)

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

Title:
  systemd is activating swap twice, through both fstab and gpt
  generators

Status in systemd package in Ubuntu:
  Triaged
Status in systemd package in Debian:
  Unknown

Bug description:
  systemd is activating swap twice, via its sda name and its uuid.

  It looks like it's because two swap units are being generated.

  
  # journalctl | grep swap | grep -v unit_create_cgroups
  Dec 05 04:30:40 yoga.lenovo systemd[1]: Activating swap Swap Partition...
  Dec 05 04:30:40 yoga.lenovo systemd[1]: Activating swap 
/dev/disk/by-uuid/73d341f1-eedc-43fc-9e53-ba4194dae3fb...
  Dec 05 04:30:40 yoga.lenovo swapon[396]: swapon: 
/dev/disk/by-uuid/73d341f1-eedc-43fc-9e53-ba4194dae3fb: swapon failed: Device 
or resource busy
  Dec 05 04:30:40 yoga.lenovo systemd[1]: 
dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap swap 
process exited, code=exited status=255
  Dec 05 04:30:40 yoga.lenovo systemd[1]: Failed to activate swap 
/dev/disk/by-uuid/73d341f1-eedc-43fc-9e53-ba4194dae3fb.
  Dec 05 04:30:40 yoga.lenovo systemd[1]: Unit 
dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap 
entered failed state.
  Dec 05 04:30:40 yoga.lenovo systemd[1]: Activated swap Swap Partition.
  Dec 05 04:30:40 yoga.lenovo kernel: Adding 8298492k swap on /dev/sda3.  
Priority:-1 extents:1 across:8298492k SSFS

  
  # systemctl status dev-sda3.swap 
  ● dev-sda3.swap - Swap Partition
 Loaded: loaded (/run/systemd/generator.late/dev-sda3.swap)
 Active: active since Fri 2014-12-05 04:30:40 EST; 27min ago
   What: /dev/sda3
   Docs: man:systemd-gpt-auto-generator(8)
Process: 395 ExecActivate=/sbin/swapon /dev/sda3 (code=exited, 
status=0/SUCCESS)

  Dec 05 04:30:40 yoga.lenovo systemd[1]: Activating swap Swap Partition...
  Dec 05 04:30:40 yoga.lenovo systemd[1]: Activated swap Swap Partition.

  
  # systemctl status 
dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap
  ● dev-disk-byx2duuid-73d341f1x2deedcx2d43fcx2d9e53x2dba4194dae3fb.swap - 
/dev/disk/byx2duuid/73d341f1x2deedcx2d43fcx2d9e53x2dba4194dae3fb
 Loaded: loaded
 Active: inactive (dead)
   What: /dev/disk/byx2duuid/73d341f1x2deedcx2d43fcx2d9e53x2dba4194dae3fb

  
  # swapon -s
  Filename  TypeSizeUsedPriority
  /dev/sda3 partition   8298492 0   
-1

  
  # blkid /dev/sda3
  /dev/sda3: UUID="73d341f1-eedc-43fc-9e53-ba4194dae3fb" TYPE="swap" 
PARTUUID="63a48c8a-8c88-482c-9577-50060d5afcb0"

  
  # find /run -name "*73d341f1*"
  
/run/systemd/generator/swap.target.wants/dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap
  
/run/systemd/generator/dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap
  /run/udev/links/\x2fdisk\x2fby-uuid\x2f73d341f1-eedc-43fc-9e53-ba4194dae3fb

  
  # find /run -name "*sda3*"
  /run/systemd/generator.late/swap.target.wants/dev-sda3.swap
  /run/systemd/generator.late/dev-sda3.swap

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 217-3ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: No such file 
or directory
  Date: Fri Dec  5 04:51:30 2014
  MachineType: LENOVO 20266
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic 
root=UUID=b51ee688-137c-47ec-9635-b69434b4e1f8 ro init=/lib/systemd/systemd 
ipv6.disable_ipv6=1
  SourcePackage: systemd
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN35WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN35WW:bd03/25/2014:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.systemd.journald.conf: 2014-10-17T14:43:13.493155

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

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

[Touch-packages] [Bug 1413922] [NEW] lxc unprivileged containers broken

2015-01-23 Thread James Hunt

Public bug reported:

Seems to be due to 1.1.0~rc1-0ubuntu1 landing?

$ lxc-start -n trusty --logfile /tmp/lxc.log --logpriority debug
lxc-start: lxc_start.c: main: 345 The container failed to start.
lxc-start: lxc_start.c: main: 347 To get more details, run the container in 
foreground mode.
lxc-start: lxc_start.c: main: 349 Additional information can be obtained by 
setting the --logfile and --logpriority options.

lxc.log attached.

On a related note, it seems that the dep8 tests I originally wrote for
lxc [1] have been replaced to call lxc's own test suite. However,
whereas these new tests are somehow passing in jenkins [2], I belied the
crude tests in [1] would have caught this issue as they actually call
the command-line tools users run.

Could we maybe bring back [1] and run both sets of tests to avoid such a
regression in future?

[1] - 
https://code.launchpad.net/~jamesodhunt/ubuntu/raring/lxc/dep-8-tests/+merge/157938
[2] - 
https://jenkins.qa.ubuntu.com/view/Vivid/view/AutoPkgTest/job/vivid-adt-lxc/ARCH=amd64,label=adt/

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: lxc 1.1.0~rc1-0ubuntu1
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
CurrentDesktop: Unity
Date: Fri Jan 23 09:15:29 2015
InstallationDate: Installed on 2014-04-11 (286 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140409)
SourcePackage: lxc
UpgradeStatus: Upgraded to vivid on 2014-05-08 (259 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: amd64 apparmor apport-bug vivid

** Attachment added: "lxc.log"
   https://bugs.launchpad.net/bugs/1413922/+attachment/4304130/+files/lxc.log

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

Title:
  lxc unprivileged containers broken

Status in lxc package in Ubuntu:
  New

Bug description:
  Seems to be due to 1.1.0~rc1-0ubuntu1 landing?

  $ lxc-start -n trusty --logfile /tmp/lxc.log --logpriority debug
  lxc-start: lxc_start.c: main: 345 The container failed to start.
  lxc-start: lxc_start.c: main: 347 To get more details, run the container in 
foreground mode.
  lxc-start: lxc_start.c: main: 349 Additional information can be obtained by 
setting the --logfile and --logpriority options.

  lxc.log attached.

  On a related note, it seems that the dep8 tests I originally wrote for
  lxc [1] have been replaced to call lxc's own test suite. However,
  whereas these new tests are somehow passing in jenkins [2], I belied
  the crude tests in [1] would have caught this issue as they actually
  call the command-line tools users run.

  Could we maybe bring back [1] and run both sets of tests to avoid such
  a regression in future?

  [1] - 
https://code.launchpad.net/~jamesodhunt/ubuntu/raring/lxc/dep-8-tests/+merge/157938
  [2] - 
https://jenkins.qa.ubuntu.com/view/Vivid/view/AutoPkgTest/job/vivid-adt-lxc/ARCH=amd64,label=adt/

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lxc 1.1.0~rc1-0ubuntu1
  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
  CurrentDesktop: Unity
  Date: Fri Jan 23 09:15:29 2015
  InstallationDate: Installed on 2014-04-11 (286 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140409)
  SourcePackage: lxc
  UpgradeStatus: Upgraded to vivid on 2014-05-08 (259 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/1413922/+subscriptions

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

[Touch-packages] [Bug 1399595] Re: systemd is activating swap twice, through both fstab and gpt generators

** Bug watch added: Debian Bug tracker #772182
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772182

** Also affects: systemd (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772182
   Importance: Unknown
   Status: Unknown

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

Title:
  systemd is activating swap twice, through both fstab and gpt
  generators

Status in systemd package in Ubuntu:
  Triaged
Status in systemd package in Debian:
  Unknown

Bug description:
  systemd is activating swap twice, via its sda name and its uuid.

  It looks like it's because two swap units are being generated.

  
  # journalctl | grep swap | grep -v unit_create_cgroups
  Dec 05 04:30:40 yoga.lenovo systemd[1]: Activating swap Swap Partition...
  Dec 05 04:30:40 yoga.lenovo systemd[1]: Activating swap 
/dev/disk/by-uuid/73d341f1-eedc-43fc-9e53-ba4194dae3fb...
  Dec 05 04:30:40 yoga.lenovo swapon[396]: swapon: 
/dev/disk/by-uuid/73d341f1-eedc-43fc-9e53-ba4194dae3fb: swapon failed: Device 
or resource busy
  Dec 05 04:30:40 yoga.lenovo systemd[1]: 
dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap swap 
process exited, code=exited status=255
  Dec 05 04:30:40 yoga.lenovo systemd[1]: Failed to activate swap 
/dev/disk/by-uuid/73d341f1-eedc-43fc-9e53-ba4194dae3fb.
  Dec 05 04:30:40 yoga.lenovo systemd[1]: Unit 
dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap 
entered failed state.
  Dec 05 04:30:40 yoga.lenovo systemd[1]: Activated swap Swap Partition.
  Dec 05 04:30:40 yoga.lenovo kernel: Adding 8298492k swap on /dev/sda3.  
Priority:-1 extents:1 across:8298492k SSFS

  
  # systemctl status dev-sda3.swap 
  ● dev-sda3.swap - Swap Partition
 Loaded: loaded (/run/systemd/generator.late/dev-sda3.swap)
 Active: active since Fri 2014-12-05 04:30:40 EST; 27min ago
   What: /dev/sda3
   Docs: man:systemd-gpt-auto-generator(8)
Process: 395 ExecActivate=/sbin/swapon /dev/sda3 (code=exited, 
status=0/SUCCESS)

  Dec 05 04:30:40 yoga.lenovo systemd[1]: Activating swap Swap Partition...
  Dec 05 04:30:40 yoga.lenovo systemd[1]: Activated swap Swap Partition.

  
  # systemctl status 
dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap
  ● dev-disk-byx2duuid-73d341f1x2deedcx2d43fcx2d9e53x2dba4194dae3fb.swap - 
/dev/disk/byx2duuid/73d341f1x2deedcx2d43fcx2d9e53x2dba4194dae3fb
 Loaded: loaded
 Active: inactive (dead)
   What: /dev/disk/byx2duuid/73d341f1x2deedcx2d43fcx2d9e53x2dba4194dae3fb

  
  # swapon -s
  Filename  TypeSizeUsedPriority
  /dev/sda3 partition   8298492 0   
-1

  
  # blkid /dev/sda3
  /dev/sda3: UUID="73d341f1-eedc-43fc-9e53-ba4194dae3fb" TYPE="swap" 
PARTUUID="63a48c8a-8c88-482c-9577-50060d5afcb0"

  
  # find /run -name "*73d341f1*"
  
/run/systemd/generator/swap.target.wants/dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap
  
/run/systemd/generator/dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap
  /run/udev/links/\x2fdisk\x2fby-uuid\x2f73d341f1-eedc-43fc-9e53-ba4194dae3fb

  
  # find /run -name "*sda3*"
  /run/systemd/generator.late/swap.target.wants/dev-sda3.swap
  /run/systemd/generator.late/dev-sda3.swap

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 217-3ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: No such file 
or directory
  Date: Fri Dec  5 04:51:30 2014
  MachineType: LENOVO 20266
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic 
root=UUID=b51ee688-137c-47ec-9635-b69434b4e1f8 ro init=/lib/systemd/systemd 
ipv6.disable_ipv6=1
  SourcePackage: systemd
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN35WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN35WW:bd03/25/2014:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.systemd.journald.conf: 2014-10-17T14:43:13.493155

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

[Touch-packages] [Bug 1407723] Re: Text cursor/selection handles too small and confusing

2015-01-23 Thread Christian Dywan

** Branch linked: lp:~ubuntu-sdk-team/ubuntu-ui-
toolkit/textHandlerCleanUpRTM

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

Title:
  Text cursor/selection handles too small and confusing

Status in the base for Ubuntu mobile products:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu RTM:
  Confirmed

Bug description:
  It is still very difficult to reliably select text in text fields and
  areas, the handles are tiny and even if you manage to target them,
  you'll cover the text you operate on with your finger.

  It is also very difficult to distinguish between moving the cursor and
  selecting text.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: qtdeclarative5-ubuntu-ui-toolkit-plugin 
1.1.1364+15.04.20141209-0ubuntu2
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.15-0ubuntu3
  Architecture: armhf
  Date: Mon Jan  5 16:25:22 2015
  InstallationDate: Installed on 2014-12-18 (18 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20141218-020204)
  SourcePackage: ubuntu-ui-toolkit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1391335] Re: TextArea cursor does not regard font size

2015-01-23 Thread Christian Dywan

** Branch linked: lp:~ubuntu-sdk-team/ubuntu-ui-
toolkit/textHandlerCleanUpRTM

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

Title:
  TextArea cursor does not regard font size

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  Set this html text to a TextArea:

  
  fsdf fsd fsd

  move the cursor between the different sized text elements.

  Actual:
  The cursor stays the same

  Expected:
  The cursor should scale with the text size

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

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

[Touch-packages] [Bug 1373918] Re: Address bar text can get overwritten if page loads whilst editing

2015-01-23 Thread Olivier Tilloy

** Changed in: webbrowser-app
 Assignee: Michael Sheldon (michael-sheldon) => Olivier Tilloy (osomon)

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

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

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

Title:
  Address bar text can get overwritten if page loads whilst editing

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Web Browser App:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Confirmed
Status in webbrowser-app package in Ubuntu RTM:
  Confirmed

Bug description:
  Steps to reproduce

  1. Start loading a new page

  2. Whilst loading edit the address bar, replacing the text with
  something new

  3. Wait for original page to finish loading

  Expected result

  Text the user entered should be preserved

  Actual result

  When the page starts to load the address bar text gets replaced with
  the new URL.

  
  This is easiest to see on slow connections as the change happens early in the 
loading process.

  I suspect this could be fixed by checking that addressbar.state isn't
  "editing" in AddressBar's onActualUrlChanged handler.

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

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

[Touch-packages] [Bug 1413931] [NEW] Link to 1006156, Plantronics USB headset steals mouse input

2015-01-23 Thread Rob Parnell

Public bug reported:

I was told to run this command in
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-
evdev/+bug/1006156/comments/19

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
Uname: Linux 3.13.0-44-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Fri Jan 23 09:33:45 2015
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0402] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Fujitsu Technology Solutions Device [1734:11e7]
InstallationDate: Installed on 2015-01-20 (2 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: FUJITSU ESPRIMO E420
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic.efi.signed 
root=UUID=79af3484-110a-432b-ba69-088c3fe132ea ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/24/2014
dmi.bios.vendor: FUJITSU // American Megatrends Inc.
dmi.bios.version: V4.6.5.4 R1.25.0 for D3230-A1x
dmi.board.name: D3230-A1
dmi.board.vendor: FUJITSU
dmi.board.version: S26361-D3230-A1
dmi.chassis.type: 3
dmi.chassis.vendor: FUJITSU
dmi.chassis.version: C$PD02
dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV4.6.5.4R1.25.0forD3230-A1x:bd06/24/2014:svnFUJITSU:pnESPRIMOE420:pvr:rvnFUJITSU:rnD3230-A1:rvrS26361-D3230-A1:cvnFUJITSU:ct3:cvrC$PD02:
dmi.product.name: ESPRIMO E420
dmi.sys.vendor: FUJITSU
version.compiz: compiz 1:0.9.11.3+14.04.20141104-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.56-1~ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.3
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Fri Jan 23 09:23:44 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   49361 
 vendor PHL
xserver.version: 2:1.15.1-0ubuntu2.6

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


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

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

Title:
  Link to 1006156, Plantronics USB headset steals mouse input

Status in xorg package in Ubuntu:
  New

Bug description:
  I was told to run this command in
  https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-
  evdev/+bug/1006156/comments/19

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Jan 23 09:33:45 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0402] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Fujitsu Technology Solutions Device [1734:11e7]
  InstallationDate: Installed on 2015-01-20 (2 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: FUJITSU ESPRIMO E420
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic.efi.signed 
root=UUID=79af3484-110a-432b-ba69-088c3fe132ea ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/24/2014
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V4.6.5.4 R1.25.0 for D3230-A1x
  dmi.board.name: D3230-A1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3230-A1

[Touch-packages] [Bug 1413929] [NEW] switching monitors scrambles windows on virtual desktops

2015-01-23 Thread Roland Bock

Public bug reported:

I am using my laptop in two ways: stand-alone and connected to an
external monitor with a different resolution. I have configured 6
virtual workspaces (3 horizontal, times  2 vertical).

Each time I switch from one to the other (which is about 5 times a day),
windows are moved to other workspaces. This is highly annoying since I
keep like to keep certain windows in certain workspaces.

Not only are windows moved, also the Window-spread (super-w) is confused
and shows windows which are not on the current workspace. Also switching
from window to window (alt-tab) can make windows be moved to another
workspace sporadically.

All this tends to stabilize once I move some windows back to where they
belong, but when I switch monitors again or hibernate: Bam! Chaos again.


I'll have to try other window managers. As of now, this is pretty much unusable 
for me.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.3+14.04.20140826-0ubuntu1
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
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Fri Jan 23 10:29:15 2015
InstallationDate: Installed on 2015-01-16 (6 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

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

Title:
  switching monitors scrambles windows on virtual desktops

Status in unity package in Ubuntu:
  New

Bug description:
  I am using my laptop in two ways: stand-alone and connected to an
  external monitor with a different resolution. I have configured 6
  virtual workspaces (3 horizontal, times  2 vertical).

  Each time I switch from one to the other (which is about 5 times a
  day), windows are moved to other workspaces. This is highly annoying
  since I keep like to keep certain windows in certain workspaces.

  Not only are windows moved, also the Window-spread (super-w) is
  confused and shows windows which are not on the current workspace.
  Also switching from window to window (alt-tab) can make windows be
  moved to another workspace sporadically.

  All this tends to stabilize once I move some windows back to where
  they belong, but when I switch monitors again or hibernate: Bam! Chaos
  again.

  
  I'll have to try other window managers. As of now, this is pretty much 
unusable for me.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.3+14.04.20140826-0ubuntu1
  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Jan 23 10:29:15 2015
  InstallationDate: Installed on 2015-01-16 (6 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  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/1413929/+subscriptions

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

[Touch-packages] [Bug 1413927] Re: lxc_cgmanager_enter: 694 call to cgmanager_move_pid_sync failed: invalid requestUser container fails to start:

The lxcsyslog.txt attachment might be worth a look though, there are
several cgmanager errors there. "vivid-systemd" is the name of my system
container (standard vivid plus apt install systemd-sysv).

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

Title:
  lxc_cgmanager_enter: 694 call to cgmanager_move_pid_sync failed:
  invalid requestUser container fails to start:

Status in lxc package in Ubuntu:
  New

Bug description:
  I wanted to test the new lxc with lxcfs. A system container (with
  upstart or systemd) works perfectly well now (great!), but user
  containers regressed:

  $ lxc-create -n v1 -t download -- -d ubuntu -r vivid -a amd64
  $ lxc-start -n v1  -F 
  lxc-start: cgmanager.c: lxc_cgmanager_enter: 694 call to 
cgmanager_move_pid_sync failed: invalid request
  lxc-start: start.c: __lxc_start: 1099 failed to spawn 'v1'
  lxc-start: lxc_start.c: main: 345 The container failed to start.

  My host is running systemd, but cgmanager is running (i. e. it's not
  bug 1400394, I enabled cgmanager.service).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lxc 1.1.0~rc1-0ubuntu1
  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
  CurrentDesktop: Unity
  Date: Fri Jan 23 10:35:55 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-11-20 (63 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141119)
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx
  lxc.conf: lxc.lxcpath = /srv/lxc

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

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

[Touch-packages] [Bug 1413927] Re: lxc_cgmanager_enter: 694 call to cgmanager_move_pid_sync failed: invalid requestUser container fails to start:

I suppose the user container runs upstart (from the template), as that's
still the ubuntu vivid default. But I have a feeling it's not even
getting that far; when I start with --logfile /dev/stdout --logpriority
debug it all just seems to be early setup:

$ lxc-start -n v1 --logfile /dev/stdout --logpriority debug  -F 
  lxc-start 1422005786.443 INFO lxc_start_ui - lxc_start.c:main:265 - 
using rcfile /home/martin/.local/share/lxc/v1/config
  lxc-start 1422005786.444 WARN lxc_confile - 
confile.c:config_pivotdir:1776 - lxc.pivotdir is ignored.  It will soon become 
an error.
  lxc-start 1422005786.445 INFO lxc_confile - 
confile.c:config_idmap:1384 - read uid map: type u nsid 0 hostid 10 range 
65536
  lxc-start 1422005786.445 INFO lxc_confile - 
confile.c:config_idmap:1384 - read uid map: type g nsid 0 hostid 10 range 
65536
  lxc-start 1422005786.445 WARN lxc_log - log.c:lxc_log_init:316 - 
lxc_log_init called with log already initialized
  lxc-start 1422005786.446 WARN lxc_cgmanager - cgmanager.c:cgm_get:963 
- do_cgm_get exited with error
  lxc-start 1422005786.447 INFO lxc_lsm - lsm/lsm.c:lsm_init:48 - LSM 
security driver AppArmor
  lxc-start 1422005786.447 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:298 - processing: .reject_force_umount  # comment 
this to allow umount -f;  not recommended.
  lxc-start 1422005786.447 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:371 - Adding non-compat rule for reject_force_umount 
action 0
  lxc-start 1422005786.447 INFO lxc_seccomp - 
seccomp.c:do_resolve_add_rule:192 - Setting seccomp rule to reject force umounts

  lxc-start 1422005786.447 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:382 - Adding compat rule for reject_force_umount 
action 0
  lxc-start 1422005786.447 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:390 - Adding non-compat rule bc nr1 == nr2 (-1, -1)
  lxc-start 1422005786.447 INFO lxc_seccomp - 
seccomp.c:do_resolve_add_rule:192 - Setting seccomp rule to reject force umounts

  lxc-start 1422005786.447 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:298 - processing: .[all].
  lxc-start 1422005786.447 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:298 - processing: .kexec_load errno 1.
  lxc-start 1422005786.447 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:371 - Adding non-compat rule for kexec_load action 
327681
  lxc-start 1422005786.447 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:382 - Adding compat rule for kexec_load action 327681
  lxc-start 1422005786.447 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:395 - Really adding compat rule bc nr1 == nr2 (283, 
246)
  lxc-start 1422005786.447 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:298 - processing: .open_by_handle_at errno 1.
  lxc-start 1422005786.447 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:371 - Adding non-compat rule for open_by_handle_at 
action 327681
  lxc-start 1422005786.447 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:382 - Adding compat rule for open_by_handle_at action 
327681
  lxc-start 1422005786.447 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:395 - Really adding compat rule bc nr1 == nr2 (342, 
304)
  lxc-start 1422005786.447 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:298 - processing: .init_module errno 1.
  lxc-start 1422005786.447 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:371 - Adding non-compat rule for init_module action 
327681
  lxc-start 1422005786.447 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:382 - Adding compat rule for init_module action 327681
  lxc-start 1422005786.447 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:395 - Really adding compat rule bc nr1 == nr2 (128, 
175)
  lxc-start 1422005786.447 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:298 - processing: .finit_module errno 1.
  lxc-start 1422005786.448 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:371 - Adding non-compat rule for finit_module action 
327681
  lxc-start 1422005786.448 WARN lxc_seccomp - 
seccomp.c:do_resolve_add_rule:209 - Seccomp: got negative # for syscall: 
finit_module
  lxc-start 1422005786.448 WARN lxc_seccomp - 
seccomp.c:do_resolve_add_rule:210 - This syscall will NOT be blacklisted
  lxc-start 1422005786.448 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:382 - Adding compat rule for finit_module action 
327681
  lxc-start 1422005786.448 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:390 - Adding non-compat rule bc nr1 == nr2 (-10085, 
-10085)
  lxc-start 1422005786.448 WARN lxc_seccomp - 
seccomp.c:do_resolve_add_rule:209 - Seccomp: got negative # for syscall: 
finit_module
  lxc-start 1422005786.448 WARN lxc_seccomp - 
seccomp.c:do_resolve_add_rule:210 - This syscall will NOT be blacklisted
  lxc-start 1422005786.448 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:298 - processin

[Touch-packages] [Bug 1413927] [NEW] lxc_cgmanager_enter: 694 call to cgmanager_move_pid_sync failed: invalid requestUser container fails to start:

Public bug reported:

I wanted to test the new lxc with lxcfs. A system container (with
upstart or systemd) works perfectly well now (great!), but user
containers regressed:

$ lxc-create -n v1 -t download -- -d ubuntu -r vivid -a amd64
$ lxc-start -n v1  -F 
lxc-start: cgmanager.c: lxc_cgmanager_enter: 694 call to 
cgmanager_move_pid_sync failed: invalid request
lxc-start: start.c: __lxc_start: 1099 failed to spawn 'v1'
lxc-start: lxc_start.c: main: 345 The container failed to start.

My host is running systemd, but cgmanager is running (i. e. it's not bug
1400394, I enabled cgmanager.service).

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: lxc 1.1.0~rc1-0ubuntu1
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
CurrentDesktop: Unity
Date: Fri Jan 23 10:35:55 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-11-20 (63 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141119)
SourcePackage: lxc
UpgradeStatus: No upgrade log present (probably fresh install)
defaults.conf:
 lxc.network.type = veth
 lxc.network.link = lxcbr0
 lxc.network.flags = up
 lxc.network.hwaddr = 00:16:3e:xx:xx:xx
lxc.conf: lxc.lxcpath = /srv/lxc

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


** Tags: amd64 apparmor apport-bug vivid

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

Title:
  lxc_cgmanager_enter: 694 call to cgmanager_move_pid_sync failed:
  invalid requestUser container fails to start:

Status in lxc package in Ubuntu:
  New

Bug description:
  I wanted to test the new lxc with lxcfs. A system container (with
  upstart or systemd) works perfectly well now (great!), but user
  containers regressed:

  $ lxc-create -n v1 -t download -- -d ubuntu -r vivid -a amd64
  $ lxc-start -n v1  -F 
  lxc-start: cgmanager.c: lxc_cgmanager_enter: 694 call to 
cgmanager_move_pid_sync failed: invalid request
  lxc-start: start.c: __lxc_start: 1099 failed to spawn 'v1'
  lxc-start: lxc_start.c: main: 345 The container failed to start.

  My host is running systemd, but cgmanager is running (i. e. it's not
  bug 1400394, I enabled cgmanager.service).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lxc 1.1.0~rc1-0ubuntu1
  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
  CurrentDesktop: Unity
  Date: Fri Jan 23 10:35:55 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-11-20 (63 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141119)
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx
  lxc.conf: lxc.lxcpath = /srv/lxc

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

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

[Touch-packages] [Bug 1408644] Re: App namespace move to appname.devname

2015-01-23 Thread Daniel Holbach

With the above bug fixed and a qtcreator-plugin-ubuntu backport on the
way, we need to figure out which parts of the docs need updating.

On the list are:

 - https://developer.ubuntu.com/publish/packaging-click-apps/
 - https://developer.ubuntu.com/apps/platform/guides/app-confinement/
 - https://developer.ubuntu.com/publish/

Anything else?

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

Title:
  App namespace move to appname.devname

Status in tools to review click packages:
  Fix Released
Status in Developer registration portal:
  Fix Released
Status in Ubuntu App Developer site:
  Triaged
Status in click package in Ubuntu:
  Invalid
Status in qtcreator-plugin-ubuntu package in Ubuntu:
  Fix Released

Bug description:
  Soon app namespaces will be

 appname.devname

  plus official apps which will be just   appname  .

  The old reverse domain namespaces (com.ubuntu.developer.<...>) will
  stay around for a while for old apps.

  This bug tracks the effort of moving our infrastructure, docs and
  tools over.

To manage notifications about this bug go to:
https://bugs.launchpad.net/click-reviewers-tools/+bug/1408644/+subscriptions

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

[Touch-packages] [Bug 1412465] Re: Enable support for Kilo Cloud Archive

2015-01-23 Thread James Page

Tested OK from proposed on trusty.

** 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 software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1412465

Title:
  Enable support for Kilo Cloud Archive

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Trusty:
  Fix Committed
Status in software-properties source package in Vivid:
  Fix Released

Bug description:
  Impact:
  End users have to manually enable the kilo cloud archive pockets.

  Test case:
  sudo add-apt-repository cloud-archive:kilo
  sudo add-apt-repository cloud-archive:kilo-proposed

  Regression potential:
  Limited - just a data item addition

  Original bug report:
  That time of the cycle:

    add-apt-repository cloud-archive:kilo

  should work on 14.04 only.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: python-software-properties (not installed)
  ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
  Uname: Linux 3.18.0-8-generic x86_64
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jan 19 14:31:23 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-11-25 (55 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141124)
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1408644] Re: App namespace move to appname.devname

2015-01-23 Thread Daniel Holbach

https://developer.ubuntu.com/apps/sdk/tutorials/creating-an-sdk-app-
project/

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

Title:
  App namespace move to appname.devname

Status in tools to review click packages:
  Fix Released
Status in Developer registration portal:
  Fix Released
Status in Ubuntu App Developer site:
  Triaged
Status in click package in Ubuntu:
  Invalid
Status in qtcreator-plugin-ubuntu package in Ubuntu:
  Fix Released

Bug description:
  Soon app namespaces will be

 appname.devname

  plus official apps which will be just   appname  .

  The old reverse domain namespaces (com.ubuntu.developer.<...>) will
  stay around for a while for old apps.

  This bug tracks the effort of moving our infrastructure, docs and
  tools over.

To manage notifications about this bug go to:
https://bugs.launchpad.net/click-reviewers-tools/+bug/1408644/+subscriptions

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

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

2015-01-23 Thread Oliver Grawert

setting the android-tools task to a realistic value, the remaining bit
is a corner case for normal users and is already shielded from doing any
damage by the fact that we do an fsck on every boot now.

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

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

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

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

Status in the base for Ubuntu mobile products:
  New
Status in android package in Ubuntu:
  Fix Released
Status in android-tools package in Ubuntu:
  In Progress
Status in initramfs-tools-ubuntu-touch package in Ubuntu:
  Fix Released
Status in linux-mako package in Ubuntu:
  Confirmed
Status in android package in Ubuntu RTM:
  Fix Released
Status in android-tools package in Ubuntu RTM:
  In Progress
Status in initramfs-tools-ubuntu-touch package in Ubuntu RTM:
  Fix Released
Status in linux-mako package in Ubuntu RTM:
  Confirmed

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

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

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

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

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

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

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

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

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

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

  $ adb push ./aa-corruption.tar.gz /tmp
  $ adb shell
  phablet@ubuntu-phablet:~$ cd /tmp
  phablet@ubuntu-phablet:~$ tar -zxvf ./aa-corruption.tar.gz
  phablet@ubuntu-phablet:~$ sudo mount -o remount,rw /
  phablet@ubuntu-phablet:~$ sudo cp ./aa-corruption/etc/sudoers.d/phablet
  /etc/sudoers.d/
  phablet@ubuntu-phablet:~$ sudo mount -o remount,ro /
  phablet@ubuntu-phablet:~$ sudo cp -a ./aa-corruption/home/bug /home
  phablet@ubuntu-phablet:~$ exit
  $ cd ./aa-corruption
  $ ./test-from-host.sh
  ...

  The old script is still in place. Simply adjust ./test-from-host.sh to have:
  testscript=/home/bug/test.sh
  #testscript=/home/bug/test-with-true.sh"

  The kernel team has verified the above reproducer and symptoms.

  Related bugs:
  * bug 1371771
  * bug 1371765
  * bug 1377338

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

Re: [Touch-packages] [Bug 1373221] Re: guvcview crashed with SIGSEGV in get_ctrl_by_id()

2015-01-23 Thread Paulo Assis

Hi,
What do you mean by "hang up" ?
Does the control window becomes unresponsive?

>From the logs all I notice is that the capture ring buffer gets full,
this usually means frames are not being encoded fast enough. Guvcview
tries to compensate for this, by reducing the frame rate.
Also the matroska muxer caches audio frames so that matching audio and
video packets are stored in the same cluster.
In this case for some reason video frames are not being fed to the
muxer, so audio keeps filling the cache.
Have you tried reducing the resolution, or fps?
You should also test with different codecs and with the avi muxer,
also maybe with audio disabled, just to check if it makes any
difference.

Regards,
Paulo

2015-01-22 21:34 GMT+00:00 vedavata :
>> please upgrade to version 2.0.1, you can use one of the following ppa:
>> stable: https://launchpad.net/~pj-assis/+archive/ubuntu/ppa
>
> This helped!
> Thank you very much!
>
> But... with this version 2.0.1, when video size became 2 GB, guvcview
> hung up... :-(
>
> # guvcview
> V4L2_CORE: (UVCIOC_CTRL_MAP) Error: No such file or directory
> ** (guvcview:15514): WARNING **: Couldn't connect to accessibility bus: 
> Failed to connect to socket /tmp/dbus-Grv3g4WwxK: Connection refused
> V4L2_CORE: VIDIOC_S_EXT_CTRLS for multiple controls failed (error -1)
> V4L2_CORE: using VIDIOC_S_CTRL for user class controls
> V4L2_CORE: control(0x0098091a) "White Balance Temperature" failed to set 
> (error -1)
> V4L2_CORE: VIDIOC_S_EXT_CTRLS for multiple controls failed (error -1)
> V4L2_CORE: using VIDIOC_S_EXT_CTRLS on single controls for class: 0x009a
> V4L2_CORE: control(0x009a0902) "Exposure (Absolute)" failed to set (error -1)
> GUVCVIEW: error setting spin value
> (guvcview:15514): GLib-GObject-CRITICAL **: g_value_set_object: assertion 
> 'G_VALUE_HOLDS_OBJECT (value)' failed
> GUVCVIEW: (status) saving video to /media/ntfs2/guvc/guvc-video-1.mkv
> ENCODER: add stream 0 to stream list
> ENCODER: add stream 1 to stream list
> ENCODER: (matroska) add seekhead entry 0 (max 10)
> ENCODER: (matroska) add seekhead entry 1 (max 10)
> AUDIO: Pulseaudio pa_stream_get_latency() failed
> [...]
> ENCODER: (matroska) packet buffer [81] is in use: flushing cached data
> ENCODER: video ring buffer full - dropping frame
> AUDIO: write buffer(23) is still in use - dropping data
>
> What can be the reason?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1373221
>
> Title:
>   guvcview crashed with SIGSEGV in get_ctrl_by_id()
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/guvcview/+bug/1373221/+subscriptions

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

Title:
  guvcview crashed with SIGSEGV in get_ctrl_by_id()

Status in GTK uvc viewer:
  Confirmed
Status in One Hundred Papercuts:
  Triaged
Status in libv4l v4l-utils:
  Confirmed
Status in guvcview package in Ubuntu:
  Triaged
Status in v4l-utils package in Ubuntu:
  Triaged

Bug description:
  HOW TO REPRODUCE:
  - Launch guvcview

  EXPECTED BEHAVIOUR:
  - The application to start normally.

  REAL BEHAVIOUR:
  - The application crashes.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: guvcview 1.7.3-1.1build2
  ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3
  Uname: Linux 3.16.0-17-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Sep 24 06:35:20 2014
  ExecutablePath: /usr/bin/guvcview
  InstallationDate: Installed on 2013-05-21 (490 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  ProcCmdline: guvcview
  SegvAnalysis:
   Segfault happened at: 0x42d970:  mov0x0,%eax
   PC (0x0042d970) ok
   source "0x0" (0x) not located in a known VMA region (needed readable 
region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: guvcview
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   __libc_start_main (main=0x409920, argc=1, argv=0x7fff32c34208, 
init=, fini=, rtld_fini=, 
stack_end=0x7fff32c341f8) at libc-start.c:287
  Title: guvcview crashed with SIGSEGV in __libc_start_main()
  UpgradeStatus: Upgraded to utopic on 2014-09-24 (0 days ago)
  UserGroups: adm lpadmin sambashare sudo

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

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

[Touch-packages] [Bug 1408644] Re: App namespace move to appname.devname

2015-01-23 Thread David Callé

** Changed in: developer-ubuntu-com
 Assignee: (unassigned) => David Callé (davidc3)

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

Title:
  App namespace move to appname.devname

Status in tools to review click packages:
  Fix Released
Status in Developer registration portal:
  Fix Released
Status in Ubuntu App Developer site:
  Triaged
Status in click package in Ubuntu:
  Invalid
Status in qtcreator-plugin-ubuntu package in Ubuntu:
  Fix Released

Bug description:
  Soon app namespaces will be

 appname.devname

  plus official apps which will be just   appname  .

  The old reverse domain namespaces (com.ubuntu.developer.<...>) will
  stay around for a while for old apps.

  This bug tracks the effort of moving our infrastructure, docs and
  tools over.

To manage notifications about this bug go to:
https://bugs.launchpad.net/click-reviewers-tools/+bug/1408644/+subscriptions

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

[Touch-packages] [Bug 116453] Re: evince can not find ü in attached PDF

2015-01-23 Thread hdante

I understand now. In this case, if über is searched, the reasonable easy
solution is to match uber.

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

Title:
  evince can not find ü in attached PDF

Status in Poppler:
  Confirmed
Status in poppler package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: evince

  1) lsb_release -rd
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04

  2) apt-cache policy evince
  evince:
Installed: 3.14.1-0ubuntu1
Candidate: 3.14.1-0ubuntu1
Version table:
   *** 3.14.1-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status
   
  3) What is expected to happen with the attached document is when one searches 
for:
  über

  it is found:
  
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/116453/+attachment/102979/+files/example.pdf

  4) What happens instead is it does not return any matches.

  WORKAROUND: Use the built-in PDF viewer+search with chromium-browser
  or chrome (doesn't work in Firefox).

  apt-cache policy chromium-browser
  chromium-browser:
Installed: 39.0.2171.65-0ubuntu0.14.04.1.1064
Candidate: 39.0.2171.65-0ubuntu0.14.04.1.1064
Version table:
   *** 39.0.2171.65-0ubuntu0.14.04.1.1064 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/universe 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   34.0.1847.116-0ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 
Packages

  apt-cache policy google-chrome-stable:i386
  google-chrome-stable:i386:
Installed: 39.0.2171.95-1
Candidate: 39.0.2171.95-1
Version table:
   *** 39.0.2171.95-1 0
  500 http://dl.google.com/linux/chrome/deb/ stable/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  Architecture: i386
  Date: Wed May 23 18:22:27 2007
  DistroRelease: Ubuntu 7.04
  ExecutablePath: /usr/bin/evince
  Package: evince 0.8.1-0ubuntu1
  PackageArchitecture: i386
  ProcEnviron:
   LANGUAGE=en_US:en
   
PATH=~/local/bin:~/local/lib:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  Uname: Linux copper 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 
i686 GNU/Linux

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

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

[Touch-packages] [Bug 1411112] Re: systemd-journal: Failed to join audit multicast group: Operation not permitted

I just booted the current devel-proposed, and it works fine there:

$ snappy versions
Part Tag   Installed  Available  Fingerprint Active  
ubuntu-core  edge  251-  718fc709559b0b  *   

I also tried this with rev 219:

sudo ubuntu-device-flash --verbose --revision=219 core
--output=/tmp/snappy219.img  --developer-mode --channel=ubuntu-core
/devel-proposed

But this still works -- "sudo journalctl" shows me the logs, and neither
dmesg, nor /var/log/, nor the journal mention "multicast". What kind of
snappy system did you use, if not a VM one from ubuntu-device-flash? Do
you still remember if you modified anything  there?

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

Title:
  systemd-journal: Failed to join audit multicast group: Operation not
  permitted

Status in systemd package in Ubuntu:
  New

Bug description:
  After upgrading a snappy system from 211 to 219, I'm seeing the
  following errors at boot:

  [   88.772405] systemd-journald[704]: Failed to join audit multicast group: 
Operation not permitted
  [   88.777304] systemd[1]: Started User Manager for UID 1000.
  [   88.778311] systemd[1]: systemd-journald.service: main process exited, 
code=exited, status=1/FAILURE
  [   88.778667] systemd[1]: Failed to start Journal Service.

  I've confirmed that a rollback to 211 fixes the problem.

  This makes it impossible to debug changes to snappy itself, since
  snappy logs to syslog which is only available via journalctl.

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

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

[Touch-packages] [Bug 1373918] Re: Address bar text can get overwritten if page loads whilst editing

2015-01-23 Thread Olivier Tilloy

** Changed in: webbrowser-app
   Status: Confirmed => In Progress

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

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

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

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

Title:
  Address bar text can get overwritten if page loads whilst editing

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Web Browser App:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu RTM:
  Confirmed

Bug description:
  Steps to reproduce

  1. Start loading a new page

  2. Whilst loading edit the address bar, replacing the text with
  something new

  3. Wait for original page to finish loading

  Expected result

  Text the user entered should be preserved

  Actual result

  When the page starts to load the address bar text gets replaced with
  the new URL.

  
  This is easiest to see on slow connections as the change happens early in the 
loading process.

  I suspect this could be fixed by checking that addressbar.state isn't
  "editing" in AddressBar's onActualUrlChanged handler.

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

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

[Touch-packages] [Bug 1373918] Re: Address bar text can get overwritten if page loads whilst editing

** Branch linked: lp:~osomon/webbrowser-app/editing-while-loading

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

Title:
  Address bar text can get overwritten if page loads whilst editing

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Web Browser App:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu RTM:
  Confirmed

Bug description:
  Steps to reproduce

  1. Start loading a new page

  2. Whilst loading edit the address bar, replacing the text with
  something new

  3. Wait for original page to finish loading

  Expected result

  Text the user entered should be preserved

  Actual result

  When the page starts to load the address bar text gets replaced with
  the new URL.

  
  This is easiest to see on slow connections as the change happens early in the 
loading process.

  I suspect this could be fixed by checking that addressbar.state isn't
  "editing" in AddressBar's onActualUrlChanged handler.

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

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

[Touch-packages] [Bug 1349336] Re: Track position information is not available

2015-01-23 Thread Matthew Paul Thomas

** Changed in: indicator-sound (Ubuntu)
   Status: Opinion => Invalid

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

Title:
  Track position information is not available

Status in indicator-sound package in Ubuntu:
  Invalid

Bug description:
  Indicator menu should be able to show current position within a track.

  Ref:
  
https://docs.google.com/a/canonical.com/document/d/1OyHUg_uUfmhDNa-9UrMc1tZ_eH_99PEU_V2l1YFA1UY/edit#

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

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

[Touch-packages] [Bug 1408323] Re: Weirdness when /home is full

2015-01-23 Thread Albert Astals Cid

I tried with qtmir demo shell and demo client and everything is fine
with the home folder full so it may seem to point to something in unity8
itself

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

Title:
  Weirdness when /home is full

Status in unity8 package in Ubuntu:
  New

Bug description:
  I happened to fill my /home to 100% in my Nexus4 under vivid.

  At that point the screen locker shows up but you can not unlock it
  (there seems to be no animation)

  Also the same happens with the indicators bar, and the indicators are
  empty.

  It is my undestandin that it shouldn't matter how much you fill /home
  that the basic functions of the phone should still work

  Can reproduce on Nexus4+rtm
  Can reproduce on krillin+vivid (took a while though)
  Could not reproduce on krillin+rtm

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

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

[Touch-packages] [Bug 1365102] Re: Enabling SLI on NVIDIA "tested" drivers causes 14.04 artifacts and freeze of desktop environment forcing manual system reset.

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

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

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

Title:
  Enabling SLI on NVIDIA "tested" drivers causes 14.04 artifacts and
  freeze of desktop environment forcing manual system reset.

Status in NVIDIA Drivers Ubuntu:
  New
Status in nvidia-graphics-drivers package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  If SLI is enabled, there are many flickering artifacts and double
  images (especially tooltips).  Eventually, the desktop environment
  locks up completely and the computer needs a forced manual reset.  I
  needed to disable SLI as soon as possible and restart in order to get
  out of the constant freezing and artifacts.

  This issue was not present in 12.04 but became immediately present the
  first time using 14.04 on the same computer.  I know my hardware is
  not the problem because my video cards work perfectly fine in Windows
  8 and I have seen other identical reports about NVIDIA SLI issues
  causing the exact same problems in 14.04.

  Bug report and logs below are taken from when SLI is disabled and
  system is working perfectly fine.  I wish I could capture logs and bug
  report while bug is occurring, but the system is too unstable and
  unusable to allow me to submit a bug report while the bug is
  occurring.

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

  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Sep  3 13:28:21 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-35-generic, x86_64: installed
   nvidia-331, 331.38, 3.13.0-35-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GF110 [GeForce GTX 580] [10de:1080] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: eVga.com. Corp. Device [3842:1582]
   NVIDIA Corporation GF110 [GeForce GTX 580] [10de:1080] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: eVga.com. Corp. Device [3842:1582]
  InstallationDate: Installed on 2014-09-03 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: MSI MS-7681
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-35-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.8
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P67A-GD55 (MS-7681)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0/2.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/2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.8:bd02/14/2011:svnMSI:pnMS-7681:pvr1.0/2.0:rvnMSI:rnP67A-GD55(MS-7681):rvr1.0/2.0:cvnMSI:ct3:cvr1.0/2.0:
  dmi.product.name: MS-7681
  dmi.product.version: 1.0/2.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.nvidia-graphics-drivers: nvidia-grap

[Touch-packages] [Bug 1365102] Re: Enabling SLI on NVIDIA "tested" drivers causes 14.04 artifacts and freeze of desktop environment forcing manual system reset.

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

** Changed in: nvidia-graphics-drivers (Ubuntu)
   Status: New => Confirmed

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

Title:
  Enabling SLI on NVIDIA "tested" drivers causes 14.04 artifacts and
  freeze of desktop environment forcing manual system reset.

Status in NVIDIA Drivers Ubuntu:
  New
Status in nvidia-graphics-drivers package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  If SLI is enabled, there are many flickering artifacts and double
  images (especially tooltips).  Eventually, the desktop environment
  locks up completely and the computer needs a forced manual reset.  I
  needed to disable SLI as soon as possible and restart in order to get
  out of the constant freezing and artifacts.

  This issue was not present in 12.04 but became immediately present the
  first time using 14.04 on the same computer.  I know my hardware is
  not the problem because my video cards work perfectly fine in Windows
  8 and I have seen other identical reports about NVIDIA SLI issues
  causing the exact same problems in 14.04.

  Bug report and logs below are taken from when SLI is disabled and
  system is working perfectly fine.  I wish I could capture logs and bug
  report while bug is occurring, but the system is too unstable and
  unusable to allow me to submit a bug report while the bug is
  occurring.

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

  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Sep  3 13:28:21 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-35-generic, x86_64: installed
   nvidia-331, 331.38, 3.13.0-35-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GF110 [GeForce GTX 580] [10de:1080] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: eVga.com. Corp. Device [3842:1582]
   NVIDIA Corporation GF110 [GeForce GTX 580] [10de:1080] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: eVga.com. Corp. Device [3842:1582]
  InstallationDate: Installed on 2014-09-03 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: MSI MS-7681
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-35-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.8
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P67A-GD55 (MS-7681)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0/2.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/2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.8:bd02/14/2011:svnMSI:pnMS-7681:pvr1.0/2.0:rvnMSI:rnP67A-GD55(MS-7681):rvr1.0/2.0:cvnMSI:ct3:cvr1.0/2.0:
  dmi.product.name: MS-7681
  dmi.product.version: 1.0/2.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.nvidia-graphics-d

[Touch-packages] [Bug 1411112] Re: systemd-journal: Failed to join audit multicast group: Operation not permitted

I installed 211 with

  sudo ubuntu-device-flash --verbose --revision=211 core
--output=/tmp/snappy211.img  --developer-mode --channel=ubuntu-core
/devel-proposed

booted it, then run "snappy update". There doesn't seem to be a
parameter to specify the version, so I can't upgrade to 219; it starts
to upgrade straight to 251:

$ sudo snappy versions
Part Tag   Installed  Available  Fingerprint Active  
ubuntu-core  edge  211251441933324acfd9  *   

However, "snappy update" has spun at "applying [/]" for over half an
hour now. Once it finally succeeds, I'll test the behaviour on the
upgraded image again.

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

Title:
  systemd-journal: Failed to join audit multicast group: Operation not
  permitted

Status in systemd package in Ubuntu:
  New

Bug description:
  After upgrading a snappy system from 211 to 219, I'm seeing the
  following errors at boot:

  [   88.772405] systemd-journald[704]: Failed to join audit multicast group: 
Operation not permitted
  [   88.777304] systemd[1]: Started User Manager for UID 1000.
  [   88.778311] systemd[1]: systemd-journald.service: main process exited, 
code=exited, status=1/FAILURE
  [   88.778667] systemd[1]: Failed to start Journal Service.

  I've confirmed that a rollback to 211 fixes the problem.

  This makes it impossible to debug changes to snappy itself, since
  snappy logs to syslog which is only available via journalctl.

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

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

[Touch-packages] [Bug 1385302] Re: Recorded videos don't show up in Videos scope

2015-01-23 Thread Ricardo Salveti

** No longer affects: libhybris

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

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

Title:
  Recorded videos don't show up in Videos scope

Status in Camera App:
  Invalid
Status in the base for Ubuntu mobile products:
  New
Status in mediascanner2 package in Ubuntu:
  Invalid
Status in qtubuntu-camera package in Ubuntu:
  In Progress
Status in unity-scope-mediascanner package in Ubuntu:
  Invalid

Bug description:
  File handles for recorded videos are left open until the camera app exits.
  This means they don't get detected by mediascanner (which waits for the file 
to finish being written) until you close the camera app, and presumably the 
operating system just closes all the handles.

  The impact is that your recorded videos won't show up anywhere that
  uses mediascanner (specifically the Videos scope).

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

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

[Touch-packages] [Bug 1365102] Re: Enabling SLI on NVIDIA "tested" drivers causes 14.04 artifacts and freeze of desktop environment forcing manual system reset.

2015-01-23 Thread Dmitry-a-durnev

I also confirm this on ubuntu 14.10/unity and latest nvidia 346.35
drivers(2x GTX 970). I experience massive artifacts when option SLI is
"on" or "afr"/"sfr".

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

Title:
  Enabling SLI on NVIDIA "tested" drivers causes 14.04 artifacts and
  freeze of desktop environment forcing manual system reset.

Status in NVIDIA Drivers Ubuntu:
  New
Status in nvidia-graphics-drivers package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  If SLI is enabled, there are many flickering artifacts and double
  images (especially tooltips).  Eventually, the desktop environment
  locks up completely and the computer needs a forced manual reset.  I
  needed to disable SLI as soon as possible and restart in order to get
  out of the constant freezing and artifacts.

  This issue was not present in 12.04 but became immediately present the
  first time using 14.04 on the same computer.  I know my hardware is
  not the problem because my video cards work perfectly fine in Windows
  8 and I have seen other identical reports about NVIDIA SLI issues
  causing the exact same problems in 14.04.

  Bug report and logs below are taken from when SLI is disabled and
  system is working perfectly fine.  I wish I could capture logs and bug
  report while bug is occurring, but the system is too unstable and
  unusable to allow me to submit a bug report while the bug is
  occurring.

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

  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Sep  3 13:28:21 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-35-generic, x86_64: installed
   nvidia-331, 331.38, 3.13.0-35-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GF110 [GeForce GTX 580] [10de:1080] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: eVga.com. Corp. Device [3842:1582]
   NVIDIA Corporation GF110 [GeForce GTX 580] [10de:1080] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: eVga.com. Corp. Device [3842:1582]
  InstallationDate: Installed on 2014-09-03 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: MSI MS-7681
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-35-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.8
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P67A-GD55 (MS-7681)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0/2.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/2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.8:bd02/14/2011:svnMSI:pnMS-7681:pvr1.0/2.0:rvnMSI:rnP67A-GD55(MS-7681):rvr1.0/2.0:cvnMSI:ct3:cvr1.0/2.0:
  dmi.product.name: MS-7681
  dmi.product.version: 1.0/2.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.nvidia-gr

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

2015-01-23 Thread dess

Ubuntu 14.10 Utopic (clean install): Just got the window (classic way:
updates became available), can keep it for while in case further testing
needed.

The session was locked (login screen) when "update-manager" was spawned.
Multiple workspaces enabled.

@3v1n0 , comment #24

Since "gdbus" command failed to give xid, I've got Windows Id's by the
PID of the following process:

$ ps aux | grep update-manager
user 29081  0.0  0.8 631432 82812 ?SNl  07:45   0:08 
/usr/bin/python3 /usr/bin/update-manager --no-update --no-focus-on-map

There are two of them, attaching output of "xprop" and "xwininfo" here.

** Attachment added: "xprop-xwininfo.tar.bz2"
   
https://bugs.launchpad.net/unity/+bug/1003950/+attachment/4304207/+files/xprop-xwininfo.tar.bz2

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

Title:
  launcher does not show minimized update manager while clicked

Status in Compiz:
  New
Status in Accelerated Xorg driver for nVidia cards:
  New
Status in Unity:
  Fix Released
Status in Unity 5.0 series:
  Fix Released
Status in Unity 6.0 series:
  Fix Released
Status in binary-driver-fglrx package in Ubuntu:
  New
Status in intel-linux-graphics-installer package in Ubuntu:
  New
Status in unity package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  New
Status in binary-driver-fglrx source package in Precise:
  New
Status in intel-linux-graphics-installer source package in Precise:
  New
Status in unity source package in Precise:
  Fix Released
Status in update-manager source package in Precise:
  Confirmed
Status in xserver-xorg-video-nouveau source package in Precise:
  New
Status in binary-driver-fglrx source package in Quantal:
  New
Status in intel-linux-graphics-installer source package in Quantal:
  New
Status in unity source package in Quantal:
  Fix Released
Status in update-manager source package in Quantal:
  Won't Fix
Status in xserver-xorg-video-nouveau source package in Quantal:
  New

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

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

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

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

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

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

[Touch-packages] [Bug 1394211] Re: Download complete dialog is shown untranslated

This bug was fixed in the package content-hub - 0.0+15.04.20150122~rtm-
0ubuntu1

---
content-hub (0.0+15.04.20150122~rtm-0ubuntu1) 14.09; urgency=low

  [ Ken VanDine ]
  * Fixed conflict with nih-dbus and our own i18n wrapper (LP: #1394211)
 -- Ubuntu daily releaseThu, 22 Jan 2015 
20:28:14 +

** Changed in: content-hub (Ubuntu RTM)
   Status: Fix Committed => Fix Released

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

Title:
  Download complete dialog is shown untranslated

Status in the base for Ubuntu mobile products:
  Confirmed
Status in content-hub package in Ubuntu:
  Fix Released
Status in content-hub package in Ubuntu RTM:
  Fix Released

Bug description:
  Test case.
  - Switch the phone to Spanish.
  - Open webbrowser-app
  - Go to http://apod.nasa.gov/
  - Tap on the image to open the popup
  - Select to download the image.
  - Choose Gallery app.

  Expected result.
  - The "Download complete" must be displayed in Spanish.

  Actual result.
  - It's displayed in English.

  content-hub.mo contains the translation "Descarga completada". Seems
  like an issue with the locale domain.

  current build number: 165
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed

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

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

[Touch-packages] [Bug 1411112] Re: systemd-journal: Failed to join audit multicast group: Operation not permitted

I'm running the complete image on tmpfs so it shoudl be lightning fast.
Michael says that the upgrader has crashed, so I can't test an upgrade
from 211 to 251. Does it happen to work for you? Did you still see this
on current images? If so, do you get any apparmor violations or similar?

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

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

Title:
  systemd-journal: Failed to join audit multicast group: Operation not
  permitted

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  After upgrading a snappy system from 211 to 219, I'm seeing the
  following errors at boot:

  [   88.772405] systemd-journald[704]: Failed to join audit multicast group: 
Operation not permitted
  [   88.777304] systemd[1]: Started User Manager for UID 1000.
  [   88.778311] systemd[1]: systemd-journald.service: main process exited, 
code=exited, status=1/FAILURE
  [   88.778667] systemd[1]: Failed to start Journal Service.

  I've confirmed that a rollback to 211 fixes the problem.

  This makes it impossible to debug changes to snappy itself, since
  snappy logs to syslog which is only available via journalctl.

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

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

[Touch-packages] [Bug 1409995] Re: Queries to remote scopes time out

** Branch linked: lp:ubuntu/vivid-proposed/unity-scopes-api

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

Title:
  Queries to remote scopes time out

Status in the base for Ubuntu mobile products:
  In Progress
Status in unity-scopes-api package in Ubuntu:
  In Progress

Bug description:
  I'm seeing this on Mako, image #63, devel-proposed.

  Periodically, the music scope fails to return any results, leaving a
  blank screen.

  Looking through the log files, I'm seeing tons of messages such as
  this:

  [2015-01-13 01:33:27.056262] INFO: SSRegistry: 
SmartScopesClient.get_remote_scopes(): GET 
https://dash.ubuntu.com/smartscopes/v2/remote-scopes?locale=en_US
  [2015-01-13 01:33:27.057239] ERROR: SSRegistry: 
SmartScopesClient.get_remote_scopes(): failed to read /custom/partner-id: 
unity::FileException: cannot open "/custom/partner-id": No such file or 
directory (errno = 2)
  [2015-01-13 01:33:46.996259] ERROR: SSRegistry: 
SmartScopesClient.get_remote_scopes(): Failed to retrieve remote scopes from 
uri: https://dash.ubuntu.com/smartscopes/v2/remote-scopes: 
unity::ResourceException: Request timed out: 
https://dash.ubuntu.com/smartscopes/v2/remote-scopes?locale=en_US

  The request times out even though the remote end works fine. (Easy to
  confirm by pasting the same URL into the browser.)

  As an aside, the error about /custom/partner-id isn't an error: if the
  file doesn't exist (errno = 2), we should say nothing. That'll get rid
  of a lot of noise.

  In addition, when I run a query, I see all queries to remote scopes
  fail (see attached trace).

  I'm not familiar with the code. Looking through, I noticed this:

  HttpResponseHandle::SPtr response = 
http_client_->get(remote_scopes_uri.str(), [&response_str](std::string const& 
replyLine) {
  response_str += replyLine; // accumulate all reply lines
  }, headers);
  response->get();

  Following this through, it appears that response_str is being appended
  to from a different thread without any lock. That looks like it's
  wrong to me. But that doesn't explain the timeout exception that is
  thrown from response->get().

  I suspect a race condition somewhere because, occasionally, I get a
  query that works.

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

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

[Touch-packages] [Bug 1387163] Re: 'Show Desktop' on launcher crashes compiz for any Gtk-Headerbar app when using any third party Gtk(3.12) theme (Utopic/Vivid)

2015-01-23 Thread Khurshid Alam

I can now reproduce this with Gtk-3.14 on Vivid as well.

** Summary changed:

- 'Show Desktop' on launcher crashes compiz for any Gtk-Headerbar app when 
using any third party Gtk(3.12) theme (Utopic/Vivid)
+ 'Show Desktop' on launcher crashes compiz for any Gtk-Headerbar app when 
using any third party Gtk(3.12/3.14) theme (Utopic/Vivid)

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

Title:
  'Show Desktop' on launcher crashes compiz for any Gtk-Headerbar app
  when using any third party Gtk(3.12/3.14) theme (Utopic/Vivid)

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

Bug description:
  This is happening for any gtk-3.12 theme which has proper support for
  gtk-headerbar.

  How to reproduce on Utopic:

  1. sudo apt-get install Numix
  2. sudo apt-get install gnome-tweak-tool
  3. change Gtk theme to Numix
  4. Open any app with Gtk-Headerbar (& NOT directly patched by Ubuntu) like 
gnome-tweak-tool, gnome-system-log
  2. enable show-desktop on unity launcher
  3. Click on show-desktop first time. it will show desktop.
  4. Click on it again, it crashes compiz & sometimes does not recover from it. 
Users have to fallback to TTY  & force restart lightdm.

  The problem also occurs for any headerbar app from Gnom3 ppa (for
  example gnome-contacts, baobab, gnome-maps).

  Attached crash file from /var/crash/compiz.

  Note: Compiz on other desktop shell/session works relatively well. For
  example in Gnome-Flashback-Compiz session it doesn't happen.

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

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

2015-01-23 Thread Manuel de la Peña

** Branch linked: lp:~mandel/ubuntu-system-settings/check-hash

-- 
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 1330770] Re: click packages rely upon tls for integrity and authenticity

** Branch linked: lp:~mandel/ubuntu-download-manager/check-hash

-- 
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 1353855] Re: Explicit g++ 4.9 dependency breaks cross-building

** Branch linked: lp:ubuntu/vivid-proposed/unity-scopes-api

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

Title:
  Explicit g++ 4.9 dependency breaks cross-building

Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Fix Released
Status in unity-scopes-api package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  With the new explicit g++ 4.9 dependency apt falls over when trying to
  install cross-dependencies for e.g. Mir:

  The following packages have unmet dependencies:
   g++-4.9:armhf : Depends: gcc-4.9:armhf (= 4.9.1-4ubuntu3) but it is not 
going to be installed
  E: Build-dependencies for sbuild-build-depends-mir-dummy could not be 
satisfied.

  This means cross-building doesn't work for any packages that have that
  dependency added. We were told it's going to be fine due to 4.9
  becoming default, but it is now, and the situation remains.

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

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

[Touch-packages] [Bug 1326816] Re: Replace QNetwork with net-cpp

** Branch linked: lp:ubuntu/vivid-proposed/unity-scopes-api

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

Title:
  Replace QNetwork with net-cpp

Status in unity-scopes-api package in Ubuntu:
  In Progress

Bug description:
  There really is no need for us to over complicate unity-scopes-api by
  dragging Qt into the mix, when we have a cleaner pure C++ solution
  available: net-cpp.

  We should replace the use of QNetwork with net-cpp, hence removing our
  dependency on Qt all together.

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

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

[Touch-packages] [Bug 1390393] Re: It's too easy to trigger a volume notification when taking a screenshot

2015-01-23 Thread Chloe Johnson

** Description changed:

  On Mako, I'm unable to take a screenshot (Vol up + Vol down) without
- changing the volume, which would be fine if there wasn't a notification
- appearing on the screenshot.
+ changing the volume, which causes a notification to appear on the
+ screenshot, and changes the volume when taking a screenshot.

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

Title:
  It's too easy to trigger a volume notification when taking a
  screenshot

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

Bug description:
  On Mako, I'm unable to take a screenshot (Vol up + Vol down) without
  changing the volume, which causes a notification to appear on the
  screenshot, and changes the volume when taking a screenshot.

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

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

[Touch-packages] [Bug 1399595] Re: systemd is activating swap twice, through both fstab and gpt generators

2015-01-23 Thread Bug Watch Updater

** Changed in: systemd (Debian)
   Status: Unknown => Confirmed

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

Title:
  systemd is activating swap twice, through both fstab and gpt
  generators

Status in systemd package in Ubuntu:
  Triaged
Status in systemd package in Debian:
  Confirmed

Bug description:
  systemd is activating swap twice, via its sda name and its uuid.

  It looks like it's because two swap units are being generated.

  
  # journalctl | grep swap | grep -v unit_create_cgroups
  Dec 05 04:30:40 yoga.lenovo systemd[1]: Activating swap Swap Partition...
  Dec 05 04:30:40 yoga.lenovo systemd[1]: Activating swap 
/dev/disk/by-uuid/73d341f1-eedc-43fc-9e53-ba4194dae3fb...
  Dec 05 04:30:40 yoga.lenovo swapon[396]: swapon: 
/dev/disk/by-uuid/73d341f1-eedc-43fc-9e53-ba4194dae3fb: swapon failed: Device 
or resource busy
  Dec 05 04:30:40 yoga.lenovo systemd[1]: 
dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap swap 
process exited, code=exited status=255
  Dec 05 04:30:40 yoga.lenovo systemd[1]: Failed to activate swap 
/dev/disk/by-uuid/73d341f1-eedc-43fc-9e53-ba4194dae3fb.
  Dec 05 04:30:40 yoga.lenovo systemd[1]: Unit 
dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap 
entered failed state.
  Dec 05 04:30:40 yoga.lenovo systemd[1]: Activated swap Swap Partition.
  Dec 05 04:30:40 yoga.lenovo kernel: Adding 8298492k swap on /dev/sda3.  
Priority:-1 extents:1 across:8298492k SSFS

  
  # systemctl status dev-sda3.swap 
  ● dev-sda3.swap - Swap Partition
 Loaded: loaded (/run/systemd/generator.late/dev-sda3.swap)
 Active: active since Fri 2014-12-05 04:30:40 EST; 27min ago
   What: /dev/sda3
   Docs: man:systemd-gpt-auto-generator(8)
Process: 395 ExecActivate=/sbin/swapon /dev/sda3 (code=exited, 
status=0/SUCCESS)

  Dec 05 04:30:40 yoga.lenovo systemd[1]: Activating swap Swap Partition...
  Dec 05 04:30:40 yoga.lenovo systemd[1]: Activated swap Swap Partition.

  
  # systemctl status 
dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap
  ● dev-disk-byx2duuid-73d341f1x2deedcx2d43fcx2d9e53x2dba4194dae3fb.swap - 
/dev/disk/byx2duuid/73d341f1x2deedcx2d43fcx2d9e53x2dba4194dae3fb
 Loaded: loaded
 Active: inactive (dead)
   What: /dev/disk/byx2duuid/73d341f1x2deedcx2d43fcx2d9e53x2dba4194dae3fb

  
  # swapon -s
  Filename  TypeSizeUsedPriority
  /dev/sda3 partition   8298492 0   
-1

  
  # blkid /dev/sda3
  /dev/sda3: UUID="73d341f1-eedc-43fc-9e53-ba4194dae3fb" TYPE="swap" 
PARTUUID="63a48c8a-8c88-482c-9577-50060d5afcb0"

  
  # find /run -name "*73d341f1*"
  
/run/systemd/generator/swap.target.wants/dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap
  
/run/systemd/generator/dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap
  /run/udev/links/\x2fdisk\x2fby-uuid\x2f73d341f1-eedc-43fc-9e53-ba4194dae3fb

  
  # find /run -name "*sda3*"
  /run/systemd/generator.late/swap.target.wants/dev-sda3.swap
  /run/systemd/generator.late/dev-sda3.swap

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 217-3ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: No such file 
or directory
  Date: Fri Dec  5 04:51:30 2014
  MachineType: LENOVO 20266
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic 
root=UUID=b51ee688-137c-47ec-9635-b69434b4e1f8 ro init=/lib/systemd/systemd 
ipv6.disable_ipv6=1
  SourcePackage: systemd
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN35WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN35WW:bd03/25/2014:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.systemd.journald.conf: 2014-10-17T14:43:13.493155

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

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

[Touch-packages] [Bug 1397963] Re: [SIM PIN] + [passcode] screens too similar

2015-01-23 Thread Matthew Paul Thomas

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

** Tags added: rtm14

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

Title:
  [SIM PIN] + [passcode] screens too similar

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

Bug description:
  The SIM PIN and lockscreen dialogs for passcode are too similar to one
  another, I repeatedly end up putting my passcode as SIM PIN, this
  could lead to locking your SIM card.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.01+15.04.20141125.2-0ubuntu1
  Uname: Linux 3.18.0-031800rc4-generic x86_64
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Dec  1 12:28:06 2014
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1413963] [NEW] network manager cannot configure pptp VPN

You have been subscribed to a public bug:

Release: vivid (fresh install)
Packages:
network-manager 0.9.8.8-0ubuntu34
network-manager-pptp 0.9.8.2-1ubuntu2
network-manager-pptp-gnome 0.9.8.2-1ubuntu2

After installing network-manager-pptp-gnome, it is not possible to add a
PPTP VPN from the networkmanager GUI.


What I expected to happen:

Network -> Add Network Connection -> VPN -> Select PPTP and
configure with GUI

What happened:

Network -> Add Network Connection -> VPN
pptp is not listed as a possible VPN type. Cannot graphically configure VPN.

Possible cause:

Copying an existing VPN configuration to /etc/NetworkManager/system-
connections results in a VPN which does work. The option to add a new
one is possibly because of a missing file:

/etc/NetworkManager/VPN/nm-pptp-service.name includes:

[GNOME]
properties=/usr/lib/NetworkManager/libnm-pptp-properties

which does not exist after installing the above packages.

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

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

-- 
network manager cannot configure pptp VPN
https://bugs.launchpad.net/bugs/1413963
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to network-manager 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 1409995] Re: Queries to remote scopes time out

This bug was fixed in the package unity-scopes-api -
0.6.11+15.04.20150121.2-0ubuntu1

---
unity-scopes-api (0.6.11+15.04.20150121.2-0ubuntu1) vivid; urgency=low

  [ Ubuntu daily release ]
  * debian/libunity-scopes3.symbols: auto-update to released version

  [ thomas-voss ]
  * Switch from QNetwork to net-cpp (LP: #1326816, #1409995)

  [ Michał Sawicz ]
  * Depend on :native version of g++ to allow cross-compiling to work.
Also run `wrap-and-sort -at` (LP: #1353855)

  [ Marcus Tomlinson ]
  * Switch from QNetwork to net-cpp (LP: #1326816, #1409995)

  [ Michi Henning ]
  * Added utility subdir to header tests.
  * Bunch of miscellaneous fixes:

  [ James Henstridge ]
  * Expose the deserialize() static method on FilterBase and FilterState
for use by the Go bindings.
 -- Ubuntu daily releaseWed, 21 Jan 2015 
12:46:41 +

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

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

Title:
  Queries to remote scopes time out

Status in the base for Ubuntu mobile products:
  In Progress
Status in unity-scopes-api package in Ubuntu:
  Fix Released

Bug description:
  I'm seeing this on Mako, image #63, devel-proposed.

  Periodically, the music scope fails to return any results, leaving a
  blank screen.

  Looking through the log files, I'm seeing tons of messages such as
  this:

  [2015-01-13 01:33:27.056262] INFO: SSRegistry: 
SmartScopesClient.get_remote_scopes(): GET 
https://dash.ubuntu.com/smartscopes/v2/remote-scopes?locale=en_US
  [2015-01-13 01:33:27.057239] ERROR: SSRegistry: 
SmartScopesClient.get_remote_scopes(): failed to read /custom/partner-id: 
unity::FileException: cannot open "/custom/partner-id": No such file or 
directory (errno = 2)
  [2015-01-13 01:33:46.996259] ERROR: SSRegistry: 
SmartScopesClient.get_remote_scopes(): Failed to retrieve remote scopes from 
uri: https://dash.ubuntu.com/smartscopes/v2/remote-scopes: 
unity::ResourceException: Request timed out: 
https://dash.ubuntu.com/smartscopes/v2/remote-scopes?locale=en_US

  The request times out even though the remote end works fine. (Easy to
  confirm by pasting the same URL into the browser.)

  As an aside, the error about /custom/partner-id isn't an error: if the
  file doesn't exist (errno = 2), we should say nothing. That'll get rid
  of a lot of noise.

  In addition, when I run a query, I see all queries to remote scopes
  fail (see attached trace).

  I'm not familiar with the code. Looking through, I noticed this:

  HttpResponseHandle::SPtr response = 
http_client_->get(remote_scopes_uri.str(), [&response_str](std::string const& 
replyLine) {
  response_str += replyLine; // accumulate all reply lines
  }, headers);
  response->get();

  Following this through, it appears that response_str is being appended
  to from a different thread without any lock. That looks like it's
  wrong to me. But that doesn't explain the timeout exception that is
  thrown from response->get().

  I suspect a race condition somewhere because, occasionally, I get a
  query that works.

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

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

[Touch-packages] [Bug 1411714] Re: indicator-network not functioning after modems reboot

2015-01-23 Thread Antti Kaijanmäki

** Branch linked: lp:~unity-api-team/indicator-network/lp1411714-14.09

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

Title:
  indicator-network not functioning after modems reboot

Status in the base for Ubuntu mobile products:
  Confirmed
Status in indicator-network package in Ubuntu:
  In Progress
Status in network-manager package in Ubuntu:
  Invalid
Status in ofono package in Ubuntu:
  Invalid

Bug description:
  1) The release of Ubuntu
  current build number: 75
  device name: krillin
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-01-16 13:56:36
  version version: 75
  version ubuntu: 20150116
  version device: 20150113-9cccefe
  version custom: 20150116

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  Using libqofono-0.70, ofono 1.12.bzr6882+15.04.20141126-0ubuntu1 which 
deviates from the default

  3) What you expected to happen
  After the modems rebooted, I expected the network indicator to function 
normally

  4) What happened instead

  The network indicator's WI-Fi and Flight Mode switches are reverted
  after a tap/click.

  In the network indicator both SIMs are listed as Disconnected.

  Sometimes I see a cog: http://i.imgur.com/bAwAB71.png

  5) Steps to reproduce

  On a dual SIM device, alternate between running
  /usr/share/ofono/scripts/set-3g-slot /ril_0 and
  /usr/share/ofono/scripts/set-3g-slot /ril_1

  This is the output of ofono/scripts/list-modems: 
http://pastebin.ubuntu.com/9762092/
  wlan0 has gone away, see output of $ ifconfig -a: 
http://pastebin.ubuntu.com/9762104/

  This appears in the network-manager.log:
  http://pastebin.ubuntu.com/9762128/

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: indicator-network 0.5.1+15.04.20141216-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: armhf
  Date: Fri Jan 16 16:16:33 2015
  InstallationDate: Installed on 2015-01-16 (0 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150116-020204)
  SourcePackage: indicator-network
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1326816] Re: Replace QNetwork with net-cpp

This bug was fixed in the package unity-scopes-api -
0.6.11+15.04.20150121.2-0ubuntu1

---
unity-scopes-api (0.6.11+15.04.20150121.2-0ubuntu1) vivid; urgency=low

  [ Ubuntu daily release ]
  * debian/libunity-scopes3.symbols: auto-update to released version

  [ thomas-voss ]
  * Switch from QNetwork to net-cpp (LP: #1326816, #1409995)

  [ Michał Sawicz ]
  * Depend on :native version of g++ to allow cross-compiling to work.
Also run `wrap-and-sort -at` (LP: #1353855)

  [ Marcus Tomlinson ]
  * Switch from QNetwork to net-cpp (LP: #1326816, #1409995)

  [ Michi Henning ]
  * Added utility subdir to header tests.
  * Bunch of miscellaneous fixes:

  [ James Henstridge ]
  * Expose the deserialize() static method on FilterBase and FilterState
for use by the Go bindings.
 -- Ubuntu daily releaseWed, 21 Jan 2015 
12:46:41 +

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

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

Title:
  Replace QNetwork with net-cpp

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

Bug description:
  There really is no need for us to over complicate unity-scopes-api by
  dragging Qt into the mix, when we have a cleaner pure C++ solution
  available: net-cpp.

  We should replace the use of QNetwork with net-cpp, hence removing our
  dependency on Qt all together.

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

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

[Touch-packages] [Bug 1397963] Re: [SIM PIN] + [passcode] screens too similar

2015-01-23 Thread Matthew Paul Thomas

** Changed in: ubuntu-ux
 Assignee: Olga Kemmet (olga-kemmet) => Matthew Paul Thomas (mpt)

** Description changed:

+ unity8 8.01+15.04.20141125.2-0ubuntu1, Ubuntu 15.04
+ 
  The SIM PIN and lockscreen dialogs for passcode are too similar to one
  another, I repeatedly end up putting my passcode as SIM PIN, this could
  lead to locking your SIM card.
  
- ProblemType: Bug
- DistroRelease: Ubuntu 15.04
- Package: unity8 8.01+15.04.20141125.2-0ubuntu1
- Uname: Linux 3.18.0-031800rc4-generic x86_64
- ApportVersion: 2.14.7-0ubuntu10
- Architecture: amd64
- CurrentDesktop: Unity
- Date: Mon Dec  1 12:28:06 2014
- SourcePackage: unity8
- UpgradeStatus: No upgrade log present (probably fresh install)
+ Fixing this might also fix bug 1387207.

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

Title:
  [SIM PIN] + [passcode] screens too similar

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

Bug description:
  unity8 8.01+15.04.20141125.2-0ubuntu1, Ubuntu 15.04

  The SIM PIN and lockscreen dialogs for passcode are too similar to one
  another, I repeatedly end up putting my passcode as SIM PIN, this
  could lead to locking your SIM card.

  Fixing this might also fix bug 1387207.

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

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

[Touch-packages] [Bug 1353855] Re: Explicit g++ 4.9 dependency breaks cross-building

This bug was fixed in the package unity-scopes-api -
0.6.11+15.04.20150121.2-0ubuntu1

---
unity-scopes-api (0.6.11+15.04.20150121.2-0ubuntu1) vivid; urgency=low

  [ Ubuntu daily release ]
  * debian/libunity-scopes3.symbols: auto-update to released version

  [ thomas-voss ]
  * Switch from QNetwork to net-cpp (LP: #1326816, #1409995)

  [ Michał Sawicz ]
  * Depend on :native version of g++ to allow cross-compiling to work.
Also run `wrap-and-sort -at` (LP: #1353855)

  [ Marcus Tomlinson ]
  * Switch from QNetwork to net-cpp (LP: #1326816, #1409995)

  [ Michi Henning ]
  * Added utility subdir to header tests.
  * Bunch of miscellaneous fixes:

  [ James Henstridge ]
  * Expose the deserialize() static method on FilterBase and FilterState
for use by the Go bindings.
 -- Ubuntu daily releaseWed, 21 Jan 2015 
12:46:41 +

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

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

Title:
  Explicit g++ 4.9 dependency breaks cross-building

Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Fix Released
Status in unity-scopes-api package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  With the new explicit g++ 4.9 dependency apt falls over when trying to
  install cross-dependencies for e.g. Mir:

  The following packages have unmet dependencies:
   g++-4.9:armhf : Depends: gcc-4.9:armhf (= 4.9.1-4ubuntu3) but it is not 
going to be installed
  E: Build-dependencies for sbuild-build-depends-mir-dummy could not be 
satisfied.

  This means cross-building doesn't work for any packages that have that
  dependency added. We were told it's going to be fine due to 4.9
  becoming default, but it is now, and the situation remains.

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

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

[Touch-packages] [Bug 1408323] Re: Weirdness when /home is full

2015-01-23 Thread Albert Astals Cid

I added some debug, the release of the finger is detected, the animation
is started (i.e. onStarted is called) but never finished

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

Title:
  Weirdness when /home is full

Status in unity8 package in Ubuntu:
  New

Bug description:
  I happened to fill my /home to 100% in my Nexus4 under vivid.

  At that point the screen locker shows up but you can not unlock it
  (there seems to be no animation)

  Also the same happens with the indicators bar, and the indicators are
  empty.

  It is my undestandin that it shouldn't matter how much you fill /home
  that the basic functions of the phone should still work

  Can reproduce on Nexus4+rtm
  Can reproduce on krillin+vivid (took a while though)
  Could not reproduce on krillin+rtm

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

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

[Touch-packages] [Bug 1413963] [NEW] network manager cannot configure pptp VPN

2015-01-23 Thread Gordon Ball

Public bug reported:

Release: vivid (fresh install)
Packages:
network-manager 0.9.8.8-0ubuntu34
network-manager-pptp 0.9.8.2-1ubuntu2
network-manager-pptp-gnome 0.9.8.2-1ubuntu2

After installing network-manager-pptp-gnome, it is not possible to add a
PPTP VPN from the networkmanager GUI.


What I expected to happen:

Network -> Add Network Connection -> VPN -> Select PPTP and
configure with GUI

What happened:

Network -> Add Network Connection -> VPN
pptp is not listed as a possible VPN type. Cannot graphically configure VPN.

Possible cause:

Copying an existing VPN configuration to /etc/NetworkManager/system-
connections results in a VPN which does work. The option to add a new
one is possibly because of a missing file:

/etc/NetworkManager/VPN/nm-pptp-service.name includes:

[GNOME]
properties=/usr/lib/NetworkManager/libnm-pptp-properties

which does not exist after installing the above packages.

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

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

** Also affects: network-manager-pptp (Ubuntu)
   Importance: Undecided
   Status: New

** Package changed: gnome-control-center (Ubuntu) => network-manager
(Ubuntu)

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

Title:
  network manager cannot configure pptp VPN

Status in network-manager package in Ubuntu:
  New
Status in network-manager-pptp package in Ubuntu:
  New

Bug description:
  Release: vivid (fresh install)
  Packages:
  network-manager 0.9.8.8-0ubuntu34
  network-manager-pptp 0.9.8.2-1ubuntu2
  network-manager-pptp-gnome 0.9.8.2-1ubuntu2

  After installing network-manager-pptp-gnome, it is not possible to add
  a PPTP VPN from the networkmanager GUI.


  What I expected to happen:

  Network -> Add Network Connection -> VPN -> Select PPTP and
  configure with GUI

  What happened:

  Network -> Add Network Connection -> VPN
  pptp is not listed as a possible VPN type. Cannot graphically configure 
VPN.

  Possible cause:

  Copying an existing VPN configuration to /etc/NetworkManager
  /system-connections results in a VPN which does work. The option to
  add a new one is possibly because of a missing file:

  /etc/NetworkManager/VPN/nm-pptp-service.name includes:
  
  [GNOME]
  properties=/usr/lib/NetworkManager/libnm-pptp-properties

  which does not exist after installing the above packages.

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

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

[Touch-packages] [Bug 1413965] [NEW] Repeated Flickering

2015-01-23 Thread Anuraag Aithal

Public bug reported:

I recently installed Ubuntu 14.10x64 in my computer, and the 346.22 driver for 
my GT 610. After that, the screen is repeatedly flickering in Firefox. I tried 
reinstalling the driver, but when I shut down the X-server - "sudo lightdm 
stop" the desktop GUI reappears. Being a very unexperienced user of Ubuntu, its 
hard for me to explain exactly wat's happening. The driver is not coming in the 
startup too. I followed the steps mentioned in ubuntu forums for uninstalling, 
but it mentions that the driver is not installed.
UBUNTU VERSION: 14.10 UTOPIC UNICORN
DRIVER VERSION: 346.22

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: xorg 1:7.7+7ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
Uname: Linux 3.16.0-29-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  346.22  Tue Dec  2 10:50:01 
PST 2014
 GCC version:  gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6)
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
Date: Fri Jan 23 16:58:23 2015
DistUpgraded: Fresh install
DistroCodename: utopic
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation GF119 [GeForce GT 610] [10de:104a] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ZOTAC International (MCO) Ltd. Device [19da:6222]
InstallationDate: Installed on 2015-01-14 (8 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical 
Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-29-generic 
root=UUID=c55df18c-9c08-48f9-8767-b58c46c21880 ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
XorgLogOld:
 
dmi.bios.date: 11/14/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.30
dmi.board.name: N68-VS3 FX
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.30:bd11/14/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-VS3FX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
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.2-0ubuntu0.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2
xserver.bootTime: Fri Jan 23 15:42:06 2015
xserver.configfile: /etc/X11/xorg.conf
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputUSB Optical MouseMOUSE, id 8
 inputAT Translated Set 2 keyboard KEYBOARD, id 9
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.16.0-1ubuntu1.2

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


** Tags: amd64 apport-bug possible-manual-nvidia-install ubuntu utopic

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

Title:
  Repeated Flickering

Status in xorg package in Ubuntu:
  New

Bug description:
  I recently installed Ubuntu 14.10x64 in my computer, and the 346.22 driver 
for my GT 610. After that, the screen is repeatedly flickering in Firefox. I 
tried reinstalling the driver, but when I shut down the X-server - "sudo 
lightdm stop" the desktop GUI reappears. Being a very unexperienced user of 
Ubuntu, its hard for me to explain exactly wat's happening. The driver is not 
coming in the startup too. I followed the steps mentioned in ubuntu forums for 
uninstalling, but it mentions that the driver is not installed.
  UBUNTU VERSION: 14.10 UTOPIC UNICORN
  DRIVER VERSION: 346.22

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
  Uname: Linux 3.16.0-29-generic x86_64
  NonfreeKernelModu

[Touch-packages] [Bug 1413722] [NEW] Sound applet has visual glitches

You have been subscribed to a public bug:

I have to click further right than I should to increase the sound. It
seems to register the mouse as being somewhere other than where it is.
Here is a video:

http://youtu.be/QPcLfGQZ7Y8

** Affects: elementaryos
 Importance: Undecided
 Status: New

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

-- 
Sound applet has visual glitches
https://bugs.launchpad.net/bugs/1413722
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to indicator-sound 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 1376240] Re: [dialer] pressing power button should silence incoming call

2015-01-23 Thread Olga Kemmet

I think this bug is only partially fixed. An incoming call is not
silenced by tapping the power button, however the screen goes dark first
and users don't know if the call continues "ringing". Switching the
screen off gives the impression that the call was declined.

The desired solution is: press the power button and silence/mute call. 
Second press: screen goes dark. 

As per comment #10

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

Title:
  [dialer] pressing power button should silence incoming call

Status in the base for Ubuntu mobile products:
  Fix Released
Status in Telephony Service:
  In Progress
Status in Ubuntu UX bugs:
  Fix Committed
Status in Unity System Compositor:
  In Progress
Status in telephony-service package in Ubuntu:
  Fix Released
Status in unity-system-compositor package in Ubuntu:
  Confirmed
Status in telephony-service package in Ubuntu RTM:
  Fix Released

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

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

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

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

[Touch-packages] [Bug 1397963] Re: [SIM PIN] + [passcode] screens too similar

2015-01-23 Thread Olga Kemmet

** Tags added: ota-2

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

Title:
  [SIM PIN] + [passcode] screens too similar

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

Bug description:
  unity8 8.01+15.04.20141125.2-0ubuntu1, Ubuntu 15.04

  The SIM PIN and lockscreen dialogs for passcode are too similar to one
  another, I repeatedly end up putting my passcode as SIM PIN, this
  could lead to locking your SIM card.

  Fixing this might also fix bug 1387207.

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

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

[Touch-packages] [Bug 1413722] Re: Sound applet has visual glitches

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

In the meantime, you can work-around the bug by using the scroll wheel
while having the mouse pointer over the slider.

** Project changed: wingpanel => indicator-sound (Ubuntu)

** Summary changed:

- Sound applet has visual glitches
+ Sound indicator slider has visual glitches

** This bug has been marked a duplicate of bug 1344990
   Volume control jumps back and forth

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

Title:
  Sound indicator slider has visual glitches

Status in elementary OS:
  New
Status in indicator-sound package in Ubuntu:
  New

Bug description:
  I have to click further right than I should to increase the sound. It
  seems to register the mouse as being somewhere other than where it is.
  Here is a video:

  http://youtu.be/QPcLfGQZ7Y8

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

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

[Touch-packages] [Bug 1344990] Re: Volume control jumps back and forth

** No longer affects: unity (Ubuntu)

** Changed in: indicator-sound (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  Volume control jumps back and forth

Status in Sound Menu:
  New
Status in Unity:
  Invalid
Status in indicator-sound package in Ubuntu:
  Triaged

Bug description:
  Steps to reproduce:

  1) Listen to music via Audacious
  2) Open volume control from Unity's panel
  3) Try to change the volume

  What happens:

  - The volume control doesn't follow mouse properly and jumps back and
  forth

  What should happen:

  - The obvious thing

  I believe this is regression as didn't notice anything weird in 13.10
  with exactly same setup.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.2+14.04.20140714-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sat Jul 19 19:51:32 2014
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1344990] Re: Volume control jumps back and forth

2015-01-23 Thread Lars Uebernickel

** Branch linked: lp:~larsu/ido/fix-volume-slider

** Project changed: indicator-sound => ido

** Changed in: ido
   Status: New => Fix Committed

** Changed in: ido
 Assignee: (unassigned) => Lars Uebernickel (larsu)

** Package changed: indicator-sound (Ubuntu) => ido (Ubuntu)

** Changed in: ido (Ubuntu)
 Assignee: Ted Gould (ted) => Lars Uebernickel (larsu)

** Changed in: ido (Ubuntu)
   Status: Triaged => Invalid

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

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

Title:
  Volume control jumps back and forth

Status in Indicator Display Objects:
  Fix Committed
Status in Unity:
  Invalid
Status in ido package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:

  1) Listen to music via Audacious
  2) Open volume control from Unity's panel
  3) Try to change the volume

  What happens:

  - The volume control doesn't follow mouse properly and jumps back and
  forth

  What should happen:

  - The obvious thing

  I believe this is regression as didn't notice anything weird in 13.10
  with exactly same setup.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.2+14.04.20140714-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sat Jul 19 19:51:32 2014
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1409266] Re: OR dependency cron || systemd-cron

2015-01-23 Thread Alexandre Detiste

Hi Martin,

As member of upstream team; I've ran out of ideas or bugs to solve for
now.

You may add yourself as uploader and upload  to experimental or unstable what 
is now ready on Alioth
to let it mature further. (I guess only unstable does trickle to Ubuntu) 

http://anonscm.debian.org/cgit/collab-maint/systemd-cron.git/

You may also remove Michael Stapelberg from uploaders, on his request:
http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/2014-December/005181.html

Sandra:
for now, ubuntu-minimal still depends on upstart that conflicts with 
systemd-sysv;
this needs to be changed first.

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

Title:
  OR dependency cron || systemd-cron

Status in ubuntu-meta package in Ubuntu:
  Won't Fix

Bug description:
  the package "ubuntu-standard" has a dependency to "cron" for 15.04,
  with systemd this should be changed to an 'or' dependency cron OR
  systemd-cron. because right now, when you wanna switch to systemd-
  cron:

  LANG=C sudo apt-get install systemd-cron  
   :(
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following extra packages will be installed:
systemd-sysv
  The following packages will be REMOVED:
anacron cron ubuntu-minimal ubuntu-standard upstart ureadahead
  The following NEW packages will be installed:
systemd-cron systemd-sysv
  0 upgraded, 2 newly installed, 6 to remove and 0 not upgraded.

  it tries to remove the ubuntu basics wich can lead to a nonworking
  system after some upgrades later.

  Please change it this way

  (the system works with systemd-cron)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubuntu-standard 1.327
  ProcVersionSignature: Ubuntu 3.18.0-8.9-lowlatency 3.18.1
  Uname: Linux 3.18.0-8-lowlatency x86_64
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Jan 10 14:12:16 2015
  InstallationDate: Installed on 2014-10-23 (79 days ago)
  InstallationMedia: Kubuntu-Plasma-5 14.10 "Utopic Unicorn" - Release amd64 
(20141022)
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1377370] Re: ubuntu-desktop should depend on ibus-gtk

2015-01-23 Thread Michael Blennerhassett

** Tags added: vivid

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

Title:
  ubuntu-desktop should depend on ibus-gtk

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Note that ubuntu-desktop depends on ibus-gtk3 already.

  Looking at /usr/share/im-config/data/21-ibus.rc
  GTK_IM_MODULE is only set to ibus if both gtk-2.0 and gtk-3.0 ibus modules 
are present.  Otherwise it's set to xim.

  If GTK_IM_MODULE=xim and ibus is running, then various bugs happen
  like LP: #1374721 and LP: #1375742.

  Installing ibus-gtk makes those problems go away.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: ubuntu-desktop 1.327
  ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3
  Uname: Linux 3.16.0-20-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Oct  4 13:49:55 2014
  InstallationDate: Installed on 2014-09-03 (30 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140902)
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1374721] Re: ibus-daemon uses 100% CPU when using gnome-calculator

2015-01-23 Thread Michael Blennerhassett

** Tags added: vivid

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

Title:
  ibus-daemon uses 100% CPU when using gnome-calculator

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:

  1. Open gnome-calculator
  2. Enter 3*7
  3. Notice that ibus-daemon and ibus-x11 are using 100+% CPU

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: ibus 1.5.8-2ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3
  Uname: Linux 3.16.0-18-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Sep 27 20:32:05 2014
  InstallationDate: Installed on 2014-09-03 (24 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140902)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1411171] Re: Repeating alarms appear disabled in clock app after it went off once

** Branch linked: lp:~charlesk/indicator-datetime/lp-1411171-strengthen-
recurrence-rule-test

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

Title:
  Repeating alarms appear disabled in clock app after it went off once

Status in the base for Ubuntu mobile products:
  Fix Released
Status in Clock application for Ubuntu devices:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  In Progress
Status in indicator-datetime package in Ubuntu RTM:
  Fix Released

Bug description:
  krillin #198

  Repeating alarm is disabled after the first time it goes off.

  Test Case:
  1. Setup a repeating alarm (everyday from Monday to Friday for example) and 
enable it
  2. Close the clock app
  3. Wait until it goes off
  4. Dismiss it (and wait maybe 1 min or 2 so indicator is updated with next 
occurrence)
  5. Resume the device
  6. Launch the clock app
  7. Go the alarms and verify the status of the alarm

  Actual Result:
  The alarm is disabled but it shows in the indicator.
  The next and next-next occurrences of the alarm are scheduled correctly. 

  Expected Result
  Alarm is still enabled.

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

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

[Touch-packages] [Bug 1413982] [NEW] Tethering via USB is an impossibly painful task

2015-01-23 Thread Ken Sharp

Public bug reported:

What I want to do is incredibly simple:

- I have my computer connected to eth1 which has internet access. This
works fine.

- I want to connect another network to usb0, not permanently - when I
need to use it, and use this for Internet access while remaining
connected to eth1 as there are resources I still want to access on that
network.

This appears to be impossible via the Network Manager applet. There is
no logical sense to the routes chosen at all and editing the routes is
even more of a mystery.

Still working on it, I'll update if I can figure out a way around this
disaster.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: network-manager 0.9.4.0-0ubuntu4.4.2
ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12
Uname: Linux 3.11.0-26-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu17.8
Architecture: i386
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not 
found.
Date: Fri Jan 23 11:26:30 2015
IpRoute:
 default via 192.168.0.254 dev eth1  proto static
 169.254.0.0/16 dev eth1  scope link  metric 1000
 192.168.0.0/24 dev eth1  proto kernel  scope link  src 192.168.0.13  metric 1
 192.168.42.0/24 dev usb0  proto kernel  scope link  src 192.168.42.37  metric 1
IwConfig:
 lono wireless extensions.

 eth1  no wireless extensions.

 usb0  no wireless extensions.
MarkForUpload: True
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
RfKill:

SourcePackage: network-manager
UpgradeStatus: Upgraded to precise on 2014-12-07 (46 days ago)
nmcli-con:
 NAME  UUID   TYPE  
TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH
 Wired connection 2e02cf14b-492a-443f-9767-7b1a7e716f65   
802-3-ethernet1422012303   Fri 23 Jan 2015 11:25:03 GMT   yes   
no /org/freedesktop/NetworkManager/Settings/1
 Wired connection 1a7eb3b41-0730-4393-beec-dd11610b1ee5   
802-3-ethernet1422012303   Fri 23 Jan 2015 11:25:03 GMT   yes   
no /org/freedesktop/NetworkManager/Settings/0
nmcli-dev:
 DEVICE TYPE  STATE DBUS-PATH
 usb0   802-3-ethernetconnected 
/org/freedesktop/NetworkManager/Devices/1
 eth1   802-3-ethernetconnected 
/org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   WIFI  
 WWAN-HARDWARE   WWAN
 running 0.9.4.0connected   enabled   enabled 
enabledenabled disabled

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


** Tags: apport-bug i386 package-from-proposed precise

** Description changed:

  What I want to do is incredibly simple:
  
- I have my computer connected to eth1 which has internet access. This works 
fine.
- I want to connect another network to usb0, not permanently - when I need to 
use it, and use this for Internet access while remaining connected to eth1 as 
there are resources I still want to access on that network.
+ - I have my computer connected to eth1 which has internet access. This
+ works fine.
+ 
+ - I want to connect another network to usb0, not permanently - when I
+ need to use it, and use this for Internet access while remaining
+ connected to eth1 as there are resources I still want to access on that
+ network.
  
  This appears to be impossible via the Network Manager applet. There is
  no logical sense to the routes chosen at all and editing the routes is
  even more of a mystery.
  
  Still working on it, I'll update if I can figure out a way around this
  disaster.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: network-manager 0.9.4.0-0ubuntu4.4.2
  ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12
  Uname: Linux 3.11.0-26-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: i386
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Fri Jan 23 11:26:30 2015
  IpRoute:
-  default via 192.168.0.254 dev eth1  proto static 
-  169.254.0.0/16 dev eth1  scope link  metric 1000 
-  192.168.0.0/24 dev eth1  proto kernel  scope link  src 192.168.0.13  metric 
1 
-  192.168.42.0/24 dev usb0  proto kernel  scope link  src 192.168.42.37  
metric 1
+  default via 192.168.0.254 dev eth1  proto static
+  169.254.0.0/16 dev eth1  scope link  metric 1000
+  192.168.0.0/24 dev eth1  proto kernel  scope link  src 192.168.0.13  metric 1
+  192.168.42.0/24 dev usb0  proto kernel  scope link  src 192.168.42.37  
metric 1
  IwConfig:
-  lono wireless extensions.
-  
-  eth1  no wireless extensions.
-  
-  usb0  no wireless extensions.
+  lono wi

[Touch-packages] [Bug 1413790] Re: It's possible to bypasss lockscreen if user is in nopasswdlogin group.

2015-01-23 Thread Marc Deslauriers

In fact, the User Accounts applet in the Settings allows creating a user
with no password by putting it in the nopasswdlogin group, but as soon
as the screen lock comes up, the user is unable to unlock the screen.

So the screen lock definitely needs to honour the nopasswdlogin group,
and this is a bug with no real security implications.

** Information type changed from Private Security to Public

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

Title:
  It's possible to bypasss lockscreen if user is in nopasswdlogin group.

Status in Light Display Manager:
  New
Status in Unity:
  In Progress
Status in lightdm package in Ubuntu:
  New
Status in unity package in Ubuntu:
  In Progress

Bug description:
  Lightdm should not emit logind "unlock" signal when the user is not
  prompted for a password. This can lead to a security issue:

  # Log-in (unity session).
  # Add the current user to nopasswdlogin group.
  # Lock the sessions.
  # Session indicator->Switch account...
  # "Login" in again.

  Expected behavior:
  The lockscreen is still active.

  Current behavior:
  The session in unlocked.

  We could workaround the issue directly in unity, but IMHO would be
  cleaner to avoid that lightdm is emitting the logind signal.

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

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

[Touch-packages] [Bug 1326816] Re: Replace QNetwork with net-cpp

2015-01-23 Thread Marcus Tomlinson

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

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

** Changed in: unity-scopes-api (Ubuntu RTM)
 Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson)

** No longer affects: unity-scopes-api (Ubuntu RTM)

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

Title:
  Replace QNetwork with net-cpp

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

Bug description:
  There really is no need for us to over complicate unity-scopes-api by
  dragging Qt into the mix, when we have a cleaner pure C++ solution
  available: net-cpp.

  We should replace the use of QNetwork with net-cpp, hence removing our
  dependency on Qt all together.

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

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

[Touch-packages] [Bug 1343962] Re: Sound slider moves itself randomly when scrolling or moving sound pointer

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

** This bug has been marked a duplicate of bug 1344990
   Volume control jumps back and forth

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

Title:
  Sound slider moves itself randomly when scrolling or moving sound
  pointer

Status in indicator-sound package in Ubuntu:
  Confirmed

Bug description:
  I've described this bug in details at askubuntu.com ::
  http://askubuntu.com/questions/499268/strange-bug-with-sound-slider

  In brief:
  1) Problem caused by installation of Ubuntu-SDK
  2) Removing Ubuntu-SDK didn't fix the problem
  3) This problem occurs only with desktop sound slider (notification slider). 
In Ubuntu sound settings, everything is fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ActionStates: ({'next.vlc.desktop': (true, signature '', @av []), 'mute': 
(true, '', []), 'phone-settings': (true, '', []), 'mic-volume': (true, 
'', [<0.1183929443359375>]), 'scroll': (true, 'i', []), 
'play-playlist.spotify.desktop': (true, 's', []), 'vlc.desktop': (true, '', 
[<{'running': , 'state': <'Paused'>}>]), 'desktop-settings': (true, '', 
[]), 'previous.vlc.desktop': (true, '', []), 'play-playlist.vlc.desktop': 
(true, 's', []), 'spotify.desktop': (true, '', [<{'running': , 'state': 
<'Paused'>}>]), 'volume': (true, 'i', [<0.51992553710937495>]), 
'play.spotify.desktop': (true, '', [<'Paused'>]), 'previous.spotify.desktop': 
(true, '', []), 'root': (true, '', [<{'title': <'Dźwięk'>, 'accessible-desc': 
<'Głośność (51%)'>, 'icon': <('themed', <['audio-volume-medium-panel', 
'audio-volume-medium', 'audio-volume', 'audio']>)>, 'visible': }>]), 
'next.spotify.desktop': (true, '', []), 'play.vlc.desktop': (true, '', 
[<'Paused'>])},)
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jul 18 12:28:16 2014
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
  InstallationDate: Installed on 2014-04-17 (91 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=pl
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  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/1343962/+subscriptions

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

[Touch-packages] [Bug 1284325] Re: Volume slider don't follow pointer position

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

** This bug has been marked a duplicate of bug 1344990
   Volume control jumps back and forth

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

Title:
  Volume slider don't follow pointer position

Status in ido package in Ubuntu:
  Triaged

Bug description:
  Hi
  TESTCASE:
  In a live environment, open the unity control center and try to slightly move 
the volume regulation, it won't follow the pointer position, see attached 
screencast.
  This is not reproducible on VM, on other regulations sliders are following 
the pointer as expected to be
  My best regards
  Fabio

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140220.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb 24 22:06:05 2014
  EcryptfsInUse: Yes
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_unity-control-center:
   activity-log-manager   0.9.7-0ubuntu10
   deja-dup   29.5-0ubuntu2
   gnome-control-center   1:3.6.3-0ubuntu50
   gnome-control-center-unity 1.3+14.04.20140117-0ubuntu1

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

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

[Touch-packages] [Bug 1334809] Re: Sound indicator controller is buggy, if you are dragging it using mouse

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

** This bug is no longer a duplicate of bug 1284325
   Volume slider don't follow pointer position
** This bug has been marked a duplicate of bug 1344990
   Volume control jumps back and forth

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

Title:
  Sound indicator controller is buggy, if you are dragging it using
  mouse

Status in ido package in Ubuntu:
  New

Bug description:
  Video demo http://youtu.be/m3jeok2aOP4

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

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

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

2015-01-23 Thread Cs-gon

Are there any news regarding this problem?

>From my point of view, the problem should be clear. The upstream
(Debian) changes, that were introduced in the 1.69ubuntu1.1 version,
don't work together with the (Ubuntu) postinst script, which causes the
empty /etc/resolv.conf during installation, and then subsequent
installation steps fail.

So the postinst script needs to be fixed, so network installations are
possible again.

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

Title:
  resolvconf 1.69ubuntu1.1 breaks network install

Status in resolvconf package in Ubuntu:
  New

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

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

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

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

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

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

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

[Touch-packages] [Bug 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

2015-01-23 Thread Thomas Strehl

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-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 the base for Ubuntu mobile products:
  New
Status in unity-scopes-api package in Ubuntu:
  Fix Committed
Status in unity-scopes-api package in Ubuntu RTM:
  In Progress

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/canonical-devices-system-image/+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 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

2015-01-23 Thread Marcus Tomlinson

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

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

** Changed in: unity-scopes-api (Ubuntu RTM)
 Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson)

** Branch linked: lp:~marcustomlinson/unity-scopes-api/lp-1410125-rtm

-- 
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 the base for Ubuntu mobile products:
  New
Status in unity-scopes-api package in Ubuntu:
  Fix Committed
Status in unity-scopes-api package in Ubuntu RTM:
  In Progress

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/canonical-devices-system-image/+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 1409995] Re: Queries to remote scopes time out

2015-01-23 Thread Marcus Tomlinson

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

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

** Changed in: unity-scopes-api (Ubuntu RTM)
 Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson)

** Branch linked: lp:~marcustomlinson/net-cpp/fix_ppc_timeout-rtm

** Branch linked: lp:~marcustomlinson/unity-scopes-api/switch-to-net-
cpp-rtm

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

Title:
  Queries to remote scopes time out

Status in the base for Ubuntu mobile products:
  In Progress
Status in unity-scopes-api package in Ubuntu:
  Fix Released
Status in unity-scopes-api package in Ubuntu RTM:
  In Progress

Bug description:
  I'm seeing this on Mako, image #63, devel-proposed.

  Periodically, the music scope fails to return any results, leaving a
  blank screen.

  Looking through the log files, I'm seeing tons of messages such as
  this:

  [2015-01-13 01:33:27.056262] INFO: SSRegistry: 
SmartScopesClient.get_remote_scopes(): GET 
https://dash.ubuntu.com/smartscopes/v2/remote-scopes?locale=en_US
  [2015-01-13 01:33:27.057239] ERROR: SSRegistry: 
SmartScopesClient.get_remote_scopes(): failed to read /custom/partner-id: 
unity::FileException: cannot open "/custom/partner-id": No such file or 
directory (errno = 2)
  [2015-01-13 01:33:46.996259] ERROR: SSRegistry: 
SmartScopesClient.get_remote_scopes(): Failed to retrieve remote scopes from 
uri: https://dash.ubuntu.com/smartscopes/v2/remote-scopes: 
unity::ResourceException: Request timed out: 
https://dash.ubuntu.com/smartscopes/v2/remote-scopes?locale=en_US

  The request times out even though the remote end works fine. (Easy to
  confirm by pasting the same URL into the browser.)

  As an aside, the error about /custom/partner-id isn't an error: if the
  file doesn't exist (errno = 2), we should say nothing. That'll get rid
  of a lot of noise.

  In addition, when I run a query, I see all queries to remote scopes
  fail (see attached trace).

  I'm not familiar with the code. Looking through, I noticed this:

  HttpResponseHandle::SPtr response = 
http_client_->get(remote_scopes_uri.str(), [&response_str](std::string const& 
replyLine) {
  response_str += replyLine; // accumulate all reply lines
  }, headers);
  response->get();

  Following this through, it appears that response_str is being appended
  to from a different thread without any lock. That looks like it's
  wrong to me. But that doesn't explain the timeout exception that is
  thrown from response->get().

  I suspect a race condition somewhere because, occasionally, I get a
  query that works.

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

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

[Touch-packages] [Bug 1247105] [NEW] Combobox scroll arrows are not integrated with system theme

You have been subscribed to a public bug:

I feel this is better explained with images:
 - http://i.imgur.com/M1hUW09.png
 - http://i.imgur.com/KgLKnBK.png

Notice the completely "wrong" style of the little up/down arrows.

How to reproduce:
 1. Find a combobox with a lot of elements
 2. Position the window near the screen border
 3. Activate the combobox

Ubuntu 13.10, Ambiance theme.

** Affects: hundredpapercuts
 Importance: Undecided
 Status: Confirmed

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


** Tags: ui
-- 
Combobox scroll arrows are not integrated with system theme
https://bugs.launchpad.net/bugs/1247105
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to ubuntu-themes 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 1315659] Re: Some widget have black background

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

** This bug has been marked a duplicate of bug 1367764
   Themes using overlay scrollbars have to set explicitly set backgrounds on 
all scrollable widgets

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

Title:
  Some widget have black background

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  You can see the problem in Glade when opening the Menu Editor > Hierarchy tab.
  I am using the default Ambiance theme and the Faenza icon set.

  Overlay scrollbars are on on my system.
  When starting an app from MonoDevelop which disables overlay scrollbars there 
is no issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: light-themes 14.04+14.04.20140410-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat May  3 14:11:03 2014
  InstallationDate: Installed on 2014-04-18 (14 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1286397] Re: Window background is black

Seems fixed in Vivid (3.14).

** No longer affects: ubuntu-themes (Ubuntu)

** Changed in: gnome-font-viewer (Ubuntu)
   Status: New => Fix Released

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

Title:
  Window background is black

Status in gnome-font-viewer package in Ubuntu:
  Fix Released

Bug description:
  The window is black. The font thumbnails are also black. The "all
  fonts" view is less than helpful. Luckily the single font page itself
  is dark-grey on black, so that's not invisible. :)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-font-viewer 3.8.0-1build1
  ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
  Uname: Linux 3.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar  1 01:05:11 2014
  InstallationDate: Installed on 2012-03-15 (715 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: gnome-font-viewer
  UpgradeStatus: Upgraded to trusty on 2014-01-22 (37 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1286397/+subscriptions

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

[Touch-packages] [Bug 1344990] Re: Volume control jumps back and forth

2015-01-23 Thread Ubuntu QA Website

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1344990

** Tags added: iso-testing

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

Title:
  Volume control jumps back and forth

Status in Indicator Display Objects:
  Fix Committed
Status in Unity:
  Invalid
Status in ido package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:

  1) Listen to music via Audacious
  2) Open volume control from Unity's panel
  3) Try to change the volume

  What happens:

  - The volume control doesn't follow mouse properly and jumps back and
  forth

  What should happen:

  - The obvious thing

  I believe this is regression as didn't notice anything weird in 13.10
  with exactly same setup.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.2+14.04.20140714-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sat Jul 19 19:51:32 2014
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1407709] Re: Google Maps and Here Maps should handle custom intent:// URLs

2015-01-23 Thread Alexandre Abreu

** Branch linked: lp:~abreu-alexandre/webbrowser-app/intent

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

Title:
  Google Maps and Here Maps should handle custom intent:// URLs

Status in the base for Ubuntu mobile products:
  Confirmed
Status in The Webapps-core project:
  In Progress
Status in Web Browser App:
  In Progress
Status in url-dispatcher package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Confirmed
Status in url-dispatcher package in Ubuntu RTM:
  In Progress
Status in webbrowser-app package in Ubuntu RTM:
  Confirmed

Bug description:
  ubuntu-rtm image 184

  The maps apps in the system should register and respond to appropriate
  urls from the browser (not sure of the format, map:// or directions://
  - need to check)

  Steps to reproduce:
  1) open browser
  2) type "Asai Belmont MA" in the url bar and press enter
  3) this will do a google search for the resturant
  4) click on the "Directions" button

  Expected result:
  - One of the maps apps should open displaying directions for the resturant

  Actual results:
  - no app is launched

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

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

[Touch-packages] [Bug 1396166] Re: [webapps-container] Stops prematurely for all default webapp on desktop

2015-01-23 Thread Alexandre Abreu

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

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

Title:
  [webapps-container] Stops prematurely for all default webapp on
  desktop

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

Bug description:
  In Vivid, the container now fails to properly lookup webapps and
  exists prematurely when no homepage is provided (which is the case for
  default installed webapps).

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

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

[Touch-packages] [Bug 1247105] Re: Combobox scroll arrows are not integrated with system theme

** No longer affects: ubuntu-themes (Ubuntu)

** Project changed: ubuntu-themes => ubuntu-themes (Ubuntu)

** Changed in: ubuntu-themes (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: ubuntu-themes (Ubuntu)
   Importance: Undecided => Medium

** Changed in: hundredpapercuts
   Status: Confirmed => Triaged

** Changed in: hundredpapercuts
   Importance: Undecided => Medium

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

Title:
  Combobox scroll arrows are not integrated with system theme

Status in One Hundred Papercuts:
  Triaged
Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  I feel this is better explained with images:
   - http://i.imgur.com/M1hUW09.png
   - http://i.imgur.com/KgLKnBK.png

  Notice the completely "wrong" style of the little up/down arrows.

  How to reproduce:
   1. Find a combobox with a lot of elements
   2. Position the window near the screen border
   3. Activate the combobox

  Ubuntu 13.10, Ambiance theme.

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

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

[Touch-packages] [Bug 1377653] Re: HDMI sound output not detected / NVIDIA optimus laptop

2015-01-23 Thread kirby_33

Hello, I don't know if my message can help somebody, but i have a similar
problem with my laptop (MSI GT60 2PE dominator 3K).
I don't have found a solution and I am not able to explain the real problem...
However I have a workaround.

My laptop use a dual boot with Ubuntu 14.04 and Windows 8.1 and I have
an optimus configuration for my video card (Intel/NVIDIA)

First I will start by explain the procedure to reproduce the bug.
At the begining, I am on linux with my NVIDIA card activated. If I connect an
hdmi cable, there is no problem. I just need to select the hdmi audio device
with Pulseaudio. However the video and the sound works fine with the hdmi
output!

Now I remove the hdmi cable and I shutdown my computer.
I reboot now using Windows 8.1 (without HDMI cable!!)

I reboot again on ubuntu. But now, if I connect again the HDMI cable, the video
works but there is no sound.
The audio device is not detected. I can switch on the intel card and come back
on the NVIDIA but it the same.
I can reinstall the nvidia driver, reinstall pulseaudio, reboot But
nothing works!! The hdmi audio device has disapeared!!!

The only one solution is to reboot on windows 8.1. I connect the hdmi
cable, I check the sound works (on windows) and I shutdown the computer.

Now if i reboot on linux the audio device is back!!! :)

This is just a workaround, but it is not a solution... :(

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

Title:
HDMI sound output not detected / NVIDIA optimus laptop

Status in alsa-driver package in Ubuntu:
Confirmed

Bug description:
Hi,

not sure if this is an alsa or nvidia/nouveau bug.
HDMI audio output doesn't appear in sound settings output panel.
Audio works well on internal speakers, but it seems there is no way to make
it output to hdmi...

The laptop has optimus NVIDIA+Intel.
The behaviour is the same with nouveau or nvidia proprietary driver.

Please let me know if further testing is required

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
Uname: Linux 3.13.0-36-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: sam2295 F pulseaudio
CurrentDesktop: Unity
CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission
denied
Date: Sun Oct 5 17:05:35 2014
InstallationDate: Installed on 2014-04-21 (166 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/02/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N56VZ.215
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: N56VZ
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrN56VZ.215:bd11/02/2012:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: N56VZ
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1385302] Re: Recorded videos don't show up in Videos scope

2015-01-23 Thread Jim Hodapp

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

Title:
  Recorded videos don't show up in Videos scope

Status in Camera App:
  Invalid
Status in the base for Ubuntu mobile products:
  New
Status in mediascanner2 package in Ubuntu:
  Invalid
Status in qtubuntu-camera package in Ubuntu:
  Fix Committed
Status in unity-scope-mediascanner package in Ubuntu:
  Invalid

Bug description:
  File handles for recorded videos are left open until the camera app exits.
  This means they don't get detected by mediascanner (which waits for the file 
to finish being written) until you close the camera app, and presumably the 
operating system just closes all the handles.

  The impact is that your recorded videos won't show up anywhere that
  uses mediascanner (specifically the Videos scope).

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

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

[Touch-packages] [Bug 1404702] Re: selected radio button is not visible in WebKit 2.6 in Ambiance

** No longer affects: epiphany-browser (Ubuntu)

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

Title:
  selected radio button is not visible in WebKit 2.6 in Ambiance

Status in ubuntu-themes package in Ubuntu:
  New
Status in webkit2gtk package in Ubuntu:
  New

Bug description:
  I'm running WebKit 2.6.2 on Ubuntu 15.04 (Vivid).

  With this version of WebKit, a selected radio button looks exactly
  like an unselected radio button in the Ambiance theme.  You can see
  this, for example, if you run Epiphany and visit
  http://www.w3schools.com/HTML/tryit.asp?filename=tryhtml_radio, or any
  other web page with radio buttons.

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

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

[Touch-packages] [Bug 1413989] [NEW] g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.

2015-01-23 Thread dino99

Public bug reported:

was logged into /var/log/x-0-greeter.log

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: lightdm 1.13.1-0ubuntu2
ProcVersionSignature: Ubuntu 3.19.0-2.2-generic 3.19.0-rc4
Uname: Linux 3.19.0-2-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.15.1-0ubuntu2
Architecture: i386
CurrentDesktop: GNOME
Date: Fri Jan 23 14:00:52 2015
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug i386 third-party-packages vivid

** Attachment added: "x-0-greeter.log"
   
https://bugs.launchpad.net/bugs/1413989/+attachment/4304284/+files/x-0-greeter.log

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

Title:
  g_dbus_connection_real_closed: Remote peer vanished with error:
  Underlying GIOStream returned 0 bytes on an async read (g-io-error-
  quark, 0). Exiting.

Status in lightdm package in Ubuntu:
  New

Bug description:
  was logged into /var/log/x-0-greeter.log

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lightdm 1.13.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-2.2-generic 3.19.0-rc4
  Uname: Linux 3.19.0-2-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Fri Jan 23 14:00:52 2015
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1368525] Re: /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service:*** Error in `/usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service': dou

2015-01-23 Thread Jean-Baptiste Lallement

I had this crash this morning with ubuntu-rtm/14.09-proposed krillin
209. Crash file attached.

** Changed in: indicator-network (Ubuntu)
   Status: Incomplete => Confirmed

** Attachment added: 
"_usr_lib_arm-linux-gnueabihf_indicator-network_indicator-network-service.32011.crash"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1368525/+attachment/4304293/+files/_usr_lib_arm-linux-gnueabihf_indicator-network_indicator-network-service.32011.crash

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

Title:
  /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-
  service:*** Error in `/usr/lib/arm-linux-gnueabihf/indicator-network
  /indicator-network-service': double free or corruption (fasttop): ADDR
  ***

Status in indicator-network package in Ubuntu:
  Confirmed

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

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

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

[Touch-packages] [Bug 1377653] Re: HDMI sound output not detected / NVIDIA optimus laptop

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

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  HDMI sound output not detected / NVIDIA optimus laptop

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  not sure if this is an alsa or nvidia/nouveau bug.
  HDMI audio output doesn't appear in sound settings output panel.
  Audio works well on internal speakers, but it seems there is no way to make 
it output to hdmi...

  The laptop has optimus NVIDIA+Intel.
  The behaviour is the same with nouveau or nvidia proprietary driver.

  Please let me know if further testing is required

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sam2295 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Sun Oct  5 17:05:35 2014
  InstallationDate: Installed on 2014-04-21 (166 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/02/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N56VZ.215
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N56VZ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN56VZ.215:bd11/02/2012:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N56VZ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1275633] Re: Header bar appearance inconsistent with other applications (is not black under Ambiance)

Newer epiphany doesn’t have this problem anymore.

** Changed in: epiphany-browser (Ubuntu)
   Status: Triaged => Fix Released

** No longer affects: ubuntu-themes (Ubuntu)

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

Title:
  Header bar appearance inconsistent with other applications (is not
  black under Ambiance)

Status in epiphany-browser package in Ubuntu:
  Fix Released

Bug description:
  Other applications in Ubuntu using the default Ambiance theme use a
  black header bar, but Epiphany Web Browser does not.

  Screenshot attached compares the header bar in Epiphany versus Evince.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: epiphany-browser 3.10.3-0ubuntu2
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb  3 15:16:30 2014
  InstallationDate: Installed on 2013-12-30 (34 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131229)
  SourcePackage: epiphany-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/1275633/+subscriptions

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

[Touch-packages] [Bug 1413997] [NEW] package gconf2 3.2.6-2ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139

2015-01-23 Thread Domingo Bernardo

Public bug reported:

it simply stopped during the upgrade

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: gconf2 3.2.6-2ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
Uname: Linux 3.13.0-36-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.14.7-0ubuntu8.1
Architecture: i386
Date: Thu Jan 22 12:26:14 2015
DuplicateSignature: package:gconf2:3.2.6-2ubuntu1:subprocess installed 
post-installation script returned error exit status 139
ErrorMessage: subprocess installed post-installation script returned error exit 
status 139
InstallationDate: Installed on 2014-09-05 (139 days ago)
InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2)
SourcePackage: gconf
Title: package gconf2 3.2.6-2ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 139
UpgradeStatus: Upgraded to utopic on 2015-01-22 (0 days ago)

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


** Tags: apport-package i386 utopic

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

Title:
  package gconf2 3.2.6-2ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 139

Status in gconf package in Ubuntu:
  New

Bug description:
  it simply stopped during the upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: gconf2 3.2.6-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: i386
  Date: Thu Jan 22 12:26:14 2015
  DuplicateSignature: package:gconf2:3.2.6-2ubuntu1:subprocess installed 
post-installation script returned error exit status 139
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 139
  InstallationDate: Installed on 2014-09-05 (139 days ago)
  InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  SourcePackage: gconf
  Title: package gconf2 3.2.6-2ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 139
  UpgradeStatus: Upgraded to utopic on 2015-01-22 (0 days ago)

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

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

[Touch-packages] [Bug 1413997] Re: package gconf2 3.2.6-2ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139

2015-01-23 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package gconf2 3.2.6-2ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 139

Status in gconf package in Ubuntu:
  New

Bug description:
  it simply stopped during the upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: gconf2 3.2.6-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: i386
  Date: Thu Jan 22 12:26:14 2015
  DuplicateSignature: package:gconf2:3.2.6-2ubuntu1:subprocess installed 
post-installation script returned error exit status 139
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 139
  InstallationDate: Installed on 2014-09-05 (139 days ago)
  InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  SourcePackage: gconf
  Title: package gconf2 3.2.6-2ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 139
  UpgradeStatus: Upgraded to utopic on 2015-01-22 (0 days ago)

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

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

[Touch-packages] [Bug 1244285] Re: Date/time sometimes doesn’t appear in menu bar, settings greyed out (Ubuntu 13.10, 14.04, 14.10)

2015-01-23 Thread janot

** Summary changed:

- Date/time sometimes doesn’t appear in menu bar, settings greyed out (Ubuntu 
13.10, 14.04)
+ Date/time sometimes doesn’t appear in menu bar, settings greyed out (Ubuntu 
13.10, 14.04, 14.10)

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

Title:
  Date/time sometimes doesn’t appear in menu bar, settings greyed out
  (Ubuntu 13.10, 14.04, 14.10)

Status in One Hundred Papercuts:
  Triaged
Status in The Date and Time Indicator:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Triaged

Bug description:
  it does not happen often, and when it happens, just a log out and re-
  log in is enough to restore it.

  http://askubuntu.com/questions/357266/how-to-show-time-in-
  ubuntu-13-10/357280

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

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

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

2015-01-23 Thread Pat McGowan

marking resolved for purposes of this project

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

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

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

Status in the base for Ubuntu mobile products:
  Fix Released
Status in android package in Ubuntu:
  Fix Released
Status in android-tools package in Ubuntu:
  In Progress
Status in initramfs-tools-ubuntu-touch package in Ubuntu:
  Fix Released
Status in linux-mako package in Ubuntu:
  Confirmed
Status in android package in Ubuntu RTM:
  Fix Released
Status in android-tools package in Ubuntu RTM:
  In Progress
Status in initramfs-tools-ubuntu-touch package in Ubuntu RTM:
  Fix Released
Status in linux-mako package in Ubuntu RTM:
  Confirmed

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

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

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

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

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

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

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

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

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

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

  $ adb push ./aa-corruption.tar.gz /tmp
  $ adb shell
  phablet@ubuntu-phablet:~$ cd /tmp
  phablet@ubuntu-phablet:~$ tar -zxvf ./aa-corruption.tar.gz
  phablet@ubuntu-phablet:~$ sudo mount -o remount,rw /
  phablet@ubuntu-phablet:~$ sudo cp ./aa-corruption/etc/sudoers.d/phablet
  /etc/sudoers.d/
  phablet@ubuntu-phablet:~$ sudo mount -o remount,ro /
  phablet@ubuntu-phablet:~$ sudo cp -a ./aa-corruption/home/bug /home
  phablet@ubuntu-phablet:~$ exit
  $ cd ./aa-corruption
  $ ./test-from-host.sh
  ...

  The old script is still in place. Simply adjust ./test-from-host.sh to have:
  testscript=/home/bug/test.sh
  #testscript=/home/bug/test-with-true.sh"

  The kernel team has verified the above reproducer and symptoms.

  Related bugs:
  * bug 1371771
  * bug 1371765
  * bug 1377338

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

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

[Touch-packages] [Bug 1271704] Re: Screen Flickering and display problems

2015-01-23 Thread Jose Luis Rivitti

The problem persistis in Ubuntu 14.10.
Now, after some lock screen, it returns with gray and green.
I took a print screen and a photo of the screen.


** Attachment added: "Issue photo"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1271704/+attachment/4304349/+files/IMG_20150123_113842.jpg

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

Title:
  Screen Flickering and display problems

Status in xorg package in Ubuntu:
  Fix Released

Bug description:
  Same Bug #1249468.
  Toshiba Satellite S75-A7334, i7-4700MQ.
  Ubuntu 13.10

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Jan 22 17:53:20 2014
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Device [1179:fa82]
  InstallationDate: Installed on 2014-01-21 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: TOSHIBA Satellite S75-A
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-15-generic.efi.signed 
root=UUID=77175de3-8261-4605-82db-9b3e72a5b62e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/23/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.30
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.30:bd09/23/2013:svnTOSHIBA:pnSatelliteS75-A:pvrPSKNAU-00R04Y:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite S75-A
  dmi.product.version: PSKNAU-00R04Y
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Wed Jan 22 17:31:23 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   20555 
   vendor SEC
  xserver.version: 2:1.14.5-1ubuntu2~saucy1

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

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

[Touch-packages] [Bug 1219644] Re: Account plugins should be made confinable by apparmor

2015-01-23 Thread Alberto Mardegan

** Changed in: ubuntu-system-settings-online-accounts
   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/1219644

Title:
  Account plugins should be made confinable by apparmor

Status in tools to review click packages:
  Confirmed
Status in Online Accounts setup for Ubuntu Touch:
  Fix Released
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Fix Released

Bug description:
  With the current implementation, the QML files for account plugins are
  executed by the Online Accounts QML applet which in turn is executed
  within the System Settings process, which probably means that
  malicious account plugins could control everything that the System
  Settings process can (like entering/exiting the flight mode).

  Account plugins (or the Online Accounts applet itself) should probably
  be run in a separate process, which could then be assigned a stricter
  confinement with apparmor.

To manage notifications about this bug go to:
https://bugs.launchpad.net/click-reviewers-tools/+bug/1219644/+subscriptions

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

[Touch-packages] [Bug 1411112] Re: systemd-journal: Failed to join audit multicast group: Operation not permitted