date:20150318

You have been subscribed to a public bug:

I installed Lubuntu 15.04 Vervet (Live image 2015-01-09) as a Manual
installation (choosing "Something else...") to install the test Lubuntu
alongside a machine that already has Ubuntu 14.04 LTS and Windows 7.

After installation, Lubuntu was mistakenly listed as "Ubuntu" in the
GRUB menu. The existing Ubuntu installation, which had formerly been
labeled as "Ubuntu" was now (accurately) labeled as Ubuntu 14.04.

To reproduce:

Install Lubuntu alongside other existing operating systems using the
"Something else..." option and configuring your partitions in the
ubiquity installer.

Expected result:

Grub lists your new installation as "Lubuntu" and the other operating
systems as their correct names.

Actual result:

Grub lists my new lubuntu installation as "Ubuntu" (only) and the other
operating systems correctly (for me, Ubuntu 14.04.1 LTS and Windows 7).

Hardware profile: https://gist.github.com/e4e4d9d3e41ccf5c27c7

** Affects: lsb (Ubuntu)
 Importance: Wishlist
 Status: Opinion


** Tags: iso-testing ubiquity-2.21.3 vivid
-- 
GRUB shows "Ubuntu" rather than flavor name
https://bugs.launchpad.net/bugs/1409209
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to lsb 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 1433879] Re: package libavcodec-extra 6:9.18-0ubuntu0.14.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting c

** Tags removed: need-duplicate-check

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

Title:
  package libavcodec-extra 6:9.18-0ubuntu0.14.04.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in libav package in Ubuntu:
  New

Bug description:
  I have no idea

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libavcodec-extra 6:9.18-0ubuntu0.14.04.1
  ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
  Uname: Linux 3.13.0-48-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: amd64
  Date: Thu Mar 19 06:27:41 2015
  DuplicateSignature: package:libavcodec-extra:6:9.18-0ubuntu0.14.04.1:package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2014-04-24 (328 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  PackageArchitecture: all
  SourcePackage: libav
  SystemImageInfo: Error: [Errno 2] No such file or directory: 
'system-image-cli'
  Title: package libavcodec-extra 6:9.18-0ubuntu0.14.04.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to trusty on 2014-04-28 (324 days ago)

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

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

[Touch-packages] [Bug 1433879] Re: package libavcodec-extra 6:9.18-0ubuntu0.14.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting c

2015-03-18 Thread Seth Arnold

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

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

Title:
  package libavcodec-extra 6:9.18-0ubuntu0.14.04.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in libav package in Ubuntu:
  New

Bug description:
  I have no idea

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libavcodec-extra 6:9.18-0ubuntu0.14.04.1
  ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
  Uname: Linux 3.13.0-48-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: amd64
  Date: Thu Mar 19 06:27:41 2015
  DuplicateSignature: package:libavcodec-extra:6:9.18-0ubuntu0.14.04.1:package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2014-04-24 (328 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  PackageArchitecture: all
  SourcePackage: libav
  SystemImageInfo: Error: [Errno 2] No such file or directory: 
'system-image-cli'
  Title: package libavcodec-extra 6:9.18-0ubuntu0.14.04.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to trusty on 2014-04-28 (324 days ago)

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

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

[Touch-packages] [Bug 1420556] Comment bridged from LTC Bugzilla

2015-03-18 Thread bugproxy

--- Comment From helle...@us.ibm.com 2015-03-19 04:55 EDT---
This is interesting, as this is exactly the behavior you get when debugging in 
gdb, and you've made changes in your code, and your breakpoints are now out of 
sync with your code.  (because you've added or removed lines)  It seem like the 
problem almost certainly has to be that the testsuite has some hard-code 
breakpoints, and these are out of sync with one or more files of the actual 
source code.

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

Title:
  gdb source tests are failing in Ubuntu 15.04

Status in gdb package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  gdb source tests are failing in Ubuntu 15.04
   
  ---uname output---
  Linux ubuntu 3.18.0-12-generic #13-Ubuntu SMP Thu Jan 29 13:44:26 UTC 2015 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = P8 

  ---Steps to Reproduce---
  Install a Power VM LPAR with Ubuntu 15.04 ISO.
  Then install gdb source and build and execute the same.

  root@ubuntu:~# apt-get source gdb
  root@ubuntu:~# cd gdb-7.8.2/
  root@ubuntu:~/gdb-7.8.2# dpkg-buildpackage -b

  === gdb Summary ===

  # of expected passes25147
  # of unexpected failures280
  # of unexpected successes   2
  # of expected failures  66
  # of unknown successes  1
  # of known failures 59
  # of unresolved testcases   11
  # of untested testcases 21
  # of unsupported tests  99
  /root/gdb-7.8.2/build/objdir/gdb/testsuite/../../gdb/gdb version  
7.8.2-0ubuntu1) -nw -nx -data-directory 
/root/gdb-7.8.2/build/objdir/gdb/testsuite/../data-directory

  Package: gdb-7.8.2-0ubuntu1

  I've reproduced the tests and looking at gdb.log, noticed that for
  some reason breakpoints for main() are being hit in an unexpected
  place and this is causing a lot of testcase failures. Also, this
  problem happens only when using gcc 4.9 (Ubuntu 15.04 default); it's
  not reproducible on gcc 4.8 or 5. This is still being investigated.

  Moreover, in the gdb.python/python.exp specifically, there is this
  commit 55cfb2c4c8accd5031fd7c8167988fc4624e847c from upstream gdb that
  fixes the testcase, removing 19 of the unexpected failures.

  I've created this testcase that exemplifies the issue with the
  'breakpoint main' hit the unexpected place:

  ubuntu@ubuntu:~$ cat array.c
  int main (void)
  {
int array[1];

return 0;
  }
  ubuntu@ubuntu:~$ gcc array.c -g -o array-4.9
  ubuntu@ubuntu:~$ gdb -q ./array-4.9 -ex 'break main' -ex run
  Reading symbols from ./array-4.9...done.
  Breakpoint 1 at 0x160c: file array.c, line 3.
  Starting program: /home/ubuntu/array-4.9 

  Breakpoint 1, main () at array.c:3
  3   {
  (gdb) 

  While with gcc-4.8, gdb stops at the expected place:

  ubuntu@ubuntu:~$ gcc-4.8 array.c -g -o array-4.8
  ubuntu@ubuntu:~$ gdb -q ./array-4.8 -ex 'break main' -ex run
  Reading symbols from ./array-4.8...done.
  Breakpoint 1 at 0x15a0: file array.c, line 6.
  Starting program: /home/ubuntu/array-4.8 

  Breakpoint 1, main () at array.c:6
  6 return 0;
  (gdb) 

  Comparing the assembly output generated by both gcc's, we can also
  notice a repeated '.loc 1 3 0' in the code that seems to cause this
  misplaced breakpoint:

  ubuntu@ubuntu:~$ gcc array.c -g -o array-4.9.s -S
  ubuntu@ubuntu:~$ cat array-4.9.s
  (...)
  main:   
  .LFB0:
  .file 1 "array.c"
  .loc 1 3 0
  .cfi_startproc
  0:  addis 2,12,.TOC.-0b@ha
  addi 2,2,.TOC.-0b@l
  .localentry main,.-main
  mflr 0
  std 0,16(1)
  std 31,-8(1)
  stdu 1,-64(1)
  .cfi_def_cfa_offset 64
  .cfi_offset 65, 16
  .cfi_offset 31, -8
  mr 31,1
  .cfi_def_cfa_register 31
  .loc 1 3 0  <-- repeated .loc
  ld 9,-28688(13)
  std 9,40(31)
  li 9,0
  .loc 1 6 0
  li 9,0
  .loc 1 7 0
  mr 3,9   
  ld 10,40(31)
  ld 9,-28688(13)
  cmpld 7,10,9
  li 10,0  
  li 9,0   
  beq 7,.L3
  bl __stack_chk_fail
  nop
  .L3:
  (...)

  If this additional .loc is removed, gdb is able to hit the breakpoint at the 
correct place.
  Moreover, it might be worth mentioning that this additional .loc doesn't 
appear on gcc-5 output too, where this breakpoint issue is not reproducible as 
well.

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

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

[Touch-packages] [Bug 1300557] Re: Screen resolution no longer works

2015-03-18 Thread Jeroen T. Vermeulen

The version that was installed on March 31 was 3.13.0.20.24.  The
version I uninstalled right after that was 3.13.0.18.38.

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

Title:
  Screen resolution no longer works

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  My display's native resolution is 2560×1440 pixels.  Prior to, I
  think, Saucy I could only reach this resolution by adding it using
  xrandr, and then calling xrandr on boot/login to select that
  resolution.  The Display preferences did not show any higher options
  than 1920×1200.

  In Saucy, the native resolution just worked, and I could stop using
  xrandr.  It also worked in Trusty in the alpha releases, up to (and I
  think including) beta-1.  But today (this is not an April's fool, is
  it?) I rebooted after an upgrade, and found myself back in 1920×1200.
  Again, the Display preferences list that resolution as the highest
  possible.  But this time, attempts to ‘xrandr --addmode’ my native
  resolution failed.

  The error message wasn't very helpful; I'll try to reproduce it later
  but it throws my display into yet a lower resolution that's hard to
  work with.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14-0ubuntu1
  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: Tue Apr  1 09:59:00 2014
  DistUpgraded: 2014-01-22 17:01:10,909 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
  InstallationDate: Installed on 2013-08-03 (240 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic 
root=UUID=12085c8d-328f-4c75-a04c-184c592f61ee ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to trusty on 2014-01-22 (68 days ago)
  dmi.bios.date: 05/16/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-D3HP-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd05/16/2013:svnGigabyteTechnologyCo.,Ltd.:pnZ87-D3HP:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87-D3HP-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z87-D3HP
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Apr  1 09:52:36 2014
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16510
   vendor DEL
  xserver.version: 2:1.15.0-1ubuntu7

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

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

[Touch-packages] [Bug 1391422] Re: GeForce 820M running very hot in Ubuntu

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

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

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

Title:
  GeForce 820M running very hot in Ubuntu

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Ubuntu release: Ubuntu 14.10
  Wine: 1:1.6.2-0ubuntu6
  GPU: Intel HD 4000+Nvidia GeForce 820M
  Nvidia drivers: nvidia-331-updates

  Expected behaviour: GPU temperature should not be excessively high
  when running OpenGL games.

  What happens: The GPU temperature gets very high when running OpenGL games. 
For example, running "The Talos Principle Public Beta" from Steam in Ubuntu the 
GPU temperature will go up to 95-98C but running the same in Windows 8.1 (on 
the same laptop)  the temperature stays below 80.
  The same thing happens when running other games and games in wine.

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

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

[Touch-packages] [Bug 1432829] Re: resolvconf not updated correctly for interfaces configured in initramfs

2015-03-18 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  resolvconf not updated correctly for interfaces configured in
  initramfs

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  maas images utilize cloud-initramfs-dyn-netconf . The way this works is 
basically:
   * /etc/network/interfaces in image is a link to 
../../run/network/dynamic-interfaces
   * kernel command line 'ip=' convince the initramfs to bring up networking 
using 'ipconfig'
     example: ip=maas-enlist:BOOTIF
   * ipconfig writes files in /run/net-*.conf for each interface it configures.
   * cloud-initramfs-dyn-netconf module writes /run/network/dyanmic-interfaces 
based on /run/net-*.conf files that 'ipconfig' creates.

  end result is that after the move to real root,
  /etc/network/interfaces should be a symlink to /run/ that ends up
  having something like this:

   | ## This file is generated by cloud-initramfs-dyn-netconf
   | auto lo
   | iface lo inet loopback
   | manual eth0
   | iface eth0 inet dhcp
   | dns-nameservers 192.168.64.3
   | dns-search maas

  resolvconf seems not to be working as well as it should be.  In vivid
  (now using systemd), I have only the resolvconf header in the file.

   in all other supported ubuntu releases, doing the above results in 
functional resolv.conf via resolv.conf. Seen here from trusty:
   | # Dynamic resolv.conf(5) file for glibc resolver(3) generated by 
resolvconf(8)
   | # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
   | nameserver 192.168.64.3

  Related Bugs:
   *  bug 1432821: something deleting /run/network after during boot

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: resolvconf 1.69ubuntu1.1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  Date: Mon Mar 16 20:42:24 2015
  PackageArchitecture: all
  ProcEnviron:
   TERM=vt102
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: resolvconf
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1433855] Re: package e2fsprogs 1.42.9-3ubuntu1 failed to install/upgrade: subprocess dpkg-split returned error exit status 2

2015-03-18 Thread Ubuntu Foundations Team Bug Bot

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

** Changed in: e2fsprogs (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  package e2fsprogs 1.42.9-3ubuntu1 failed to install/upgrade:
  subprocess dpkg-split returned error exit status 2

Status in e2fsprogs package in Ubuntu:
  Invalid

Bug description:
  Fiz a atualização a tarde.
  Perdi o sistema.
  Formatei e instalei tudo de novo.
  Agora vai dar o mesmo problema e provavelmente vou ter que formatar tudo de 
novo.
  Por favor, corrijam essa atualização.

  Obrigado!
  Abraços.
  Felipe

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: e2fsprogs 1.42.9-3ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  Date: Wed Mar 18 23:06:32 2015
  DuplicateSignature: package:e2fsprogs:1.42.9-3ubuntu1:subprocess dpkg-split 
returned error exit status 2
  ErrorMessage: subprocess dpkg-split returned error exit status 2
  InstallationDate: Installed on 2015-03-18 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: e2fsprogs
  Title: package e2fsprogs 1.42.9-3ubuntu1 failed to install/upgrade: 
subprocess dpkg-split returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1396213] Re: LVM VG is not activated during system boot

2015-03-18 Thread MegaBrutal

Now I have some more info about this. What actually makes the VG
activation so long is that I have a snapshot. Activating the snapshot
takes very long, and bringing up the entire VG takes about 5 minutes.
This wouldn't be such a big problem, as I could just patiently wait for
the activation (with rootdelay). But I think the problem is that
something kills vgchange before it could finish bringing up all VGs. I
had the fortune to boot a developmental Vivid, and I've seen some
'watershed' messages stating that 'vgchange' was killed because it was
taking "too long". If we'd let 'vgchange' to finish properly, I had the
2nd VG, which contains my root FS.

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

Title:
  LVM VG is not activated during system boot

Status in One Hundred Papercuts:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  Hi all,

  I open this report based on the linked conversation I had on the linux-lvm 
mailing list, and the Ask Ubuntu question I posted regarding this case.
  https://www.redhat.com/archives/linux-lvm/2014-November/msg00023.html
  https://www.redhat.com/archives/linux-lvm/2014-November/msg00024.html
  
http://askubuntu.com/questions/542656/lvm-vg-is-not-activated-during-system-boot

  I have 2 VGs on my system, and for some reason, only one of them gets
  activated during the initrd boot sequence, which doesn't have my root
  LV, so my boot sequence halts with an initrd prompt.

  When I get to the initrd BusyBox prompt, I can see my LVs are inactive
  with "lvm lvscan" – then, "lvm vgchange -ay" brings them online. The
  boot sequence continues as I exit the BusyBox prompt. The expected
  behaviour would be that both VGs should activate automatically.

  On LVM mailing list, I've been advised it may be a problem with Ubuntu
  initrd scripts, hence I report this problem here. (I'm not sure if I'm
  reporting it to the correct place by assigning it to "linux", but I
  didn't find a package directly related to the initrd only, so I
  assumed initrd scripts are maintained by the kernel team. If you think
  it's an error, and know the correct package, please reassign!) Our
  suspicion is, initrd prematurely issues "vgchange -ay" before all the
  PVs come online. This makes sense.

  I already tried to set the "rootdelay" kernel parameter to make initrd
  wait longer for the boot LV to come up, but it didn't work. Note
  however, it worked with previous kernel versions.

  The problem came up when I upgraded to Utopic, and got kernel 
vmlinuz-3.16.0-23-generic. When I boot with the old kernel from Trusty 
(vmlinuz-3.13.0-37-generic), it works fine.
  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.16.0-23-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC1D2p', '/dev/snd/pcmC1D1c', '/dev/snd/pcmC1D0c', 
'/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/timer'] failed with exit 
code 1:
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  Card1.Amixer.info: Error: [Errno 2] No such file or directory
  Card1.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=/dev/mapper/vmhost--vg-vmhost--swap0
  InstallationDate: Installed on 2013-12-06 (354 days ago)
  InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 
(20131016)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: WinFast 6150M2MA
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-23-generic 
root=/dev/mapper/hostname--vg-hostname--rootfs ro rootflags=subvol=@ 
rootdelay=300
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-23-generic N/A
   linux-backports-modules-3.16.0-23-generic  N/A
   linux-firmware 1.138
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  utopic utopic
  Uname: Linux 3.16.0-23-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: Upgraded to utopic on 2014-10-28 (28 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 01/19/2008
  dmi.bios.ve

[Touch-packages] [Bug 1429938] Re: reboot does not return under systemd

2015-03-18 Thread Jason Gerard DeRose

I reworked the description as my original assessment was quite off.

But after more thought, I think this behavior change is something that
really needs mentioning in the Vivid releases notes.

After all, the perceived "correct" behavior of a system strongly tends
toward what the actual behavior has been historically.

Yet one of these kids is clearly not like the other :D

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

Title:
  reboot does not return under systemd

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  If you send a shutdown or reboot command over SSH to a Trusty or
  Utopic host, the command will consistently finish successfully prior
  to the SSH connection being closed, meaning your SSH client will exit
  with a return-code of zero:

  For example:

  $ ssh root@myhost shutdown -h now
  $ echo $?
  0

  Or

  $ ssh root@myhost reboot
  $ echo $?
  0

  However, on Vivid now that the switch-over to systemd has happened,
  running the same consistently results in the abrupt closure of the SSH
  connection prior to the command finishing, meaning your SSH client
  will exit with a return-code of 255:

  $ ssh root@my_vivid_host shutdown -h now
  Connection to localhost closed by remote host.
  $ echo $?
  255

  Although in retrospect is was a bit naive for me to rely on this
  (actually quite fragile) behavior, it had at least been consistent in
  Ubuntu for some time (back to at least Raring from my personal
  experience, but likely back even farther).

  This isn't technically a systemd bug, but I still think it's something
  worth mentioning in the release notes as I bet I'm not the only person
  who built some "clever" hacks around the previous behavior :P

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

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

[Touch-packages] [Bug 1429938] Re: reboot does not return under systemd

2015-03-18 Thread Jason Gerard DeRose

** Description changed:

- On Trusty and Utopic, when you run `apt-get remove openssh-server` over
- an SSH connection, your existing SSH connection remains open, so it's
- possible to run additional commands afterward.
+ If you send a shutdown or reboot command over SSH to a Trusty or Utopic
+ host, the command will consistently finish successfully prior to the SSH
+ connection being closed, meaning your SSH client will exit with a
+ return-code of zero:
  
- However, on Vivid now that the switch to systemd has been made,  `apt-
- get remove openssh-server` closes the existing SSH connection
- immediately, causing your SSH client to exit with a non-zero status. I
- have a hunch there's a lot of automation tooling out there that relies
- on the old behavior.
+ For example:
  
- For what it's worth, this change breaks the internal image mastering
- tools that System76 uses. Prior to exporting an image tarball, I spin up
- a golden VM with qemu, rysnc a script to it, and then execute this
- script over SSH.
+ $ ssh root@myhost shutdown -h now
+ $ echo $?
+ 0
  
- The important step is that I need to remove openssh-server prior to
- shutting down the VM, so these scripts always end with something like
- this:
+ Or
  
- apt-get -y purge openssh-server ssh-import-id
- apt-get -y autoremove
- shutdown -h now
+ $ ssh root@myhost reboot
+ $ echo $?
+ 0
  
- As far as I can tell, this behavior change will likewise be a problem
- when running `do-release-upgrade` on a remote server over SSH. Or more
- generally, anytime you run "apt-get upgrade/dist-upgrade" via SSH, it
- seems this would be a problem whenever the openssh-server package
- happens to be updated.
+ However, on Vivid now that the switch-over to systemd has happened,
+ running the same consistently results in the abrupt closure of the SSH
+ connection prior to the command finishing, meaning your SSH client will
+ exit with a return-code of 255:
+ 
+ $ ssh root@my_vivid_host shutdown -h now
+ Connection to localhost closed by remote host.
+ $ echo $?
+ 255
+ 
+ Although in retrospect is was a bit naive for me to rely on this
+ (actually quite fragile) behavior, it had at least been consistent in
+ Ubuntu for some time (back to at least Raring from my personal
+ experience, but likely back even farther).
+ 
+ This isn't technically a systemd bug, but I still think it's something
+ worth mentioning in the release notes as I bet I'm not the only person
+ who built some "clever" hacks around the previous behavior :P

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

Title:
  reboot does not return under systemd

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  If you send a shutdown or reboot command over SSH to a Trusty or
  Utopic host, the command will consistently finish successfully prior
  to the SSH connection being closed, meaning your SSH client will exit
  with a return-code of zero:

  For example:

  $ ssh root@myhost shutdown -h now
  $ echo $?
  0

  Or

  $ ssh root@myhost reboot
  $ echo $?
  0

  However, on Vivid now that the switch-over to systemd has happened,
  running the same consistently results in the abrupt closure of the SSH
  connection prior to the command finishing, meaning your SSH client
  will exit with a return-code of 255:

  $ ssh root@my_vivid_host shutdown -h now
  Connection to localhost closed by remote host.
  $ echo $?
  255

  Although in retrospect is was a bit naive for me to rely on this
  (actually quite fragile) behavior, it had at least been consistent in
  Ubuntu for some time (back to at least Raring from my personal
  experience, but likely back even farther).

  This isn't technically a systemd bug, but I still think it's something
  worth mentioning in the release notes as I bet I'm not the only person
  who built some "clever" hacks around the previous behavior :P

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

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

[Touch-packages] [Bug 1433858] [NEW] Mouse cursor flickering when using two graphics cards

2015-03-18 Thread Jonathan Wang

Public bug reported:

See bug #1278223

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.16.0-31.43~14.04.1-generic 3.16.7-ckt5
Uname: Linux 3.16.0-31-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.7
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 Mar 18 22:40:10 2015
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus: virtualbox, 4.3.10, 3.16.0-31-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7821]
 Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850] 
[1002:6819] (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:042c]
InstallationDate: Installed on 2015-02-24 (22 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
MachineType: MSI MS-7821
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic 
root=UUID=cb3bd3ad-4c60-460e-8982-45ab28abdaf2 ro nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/10/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V2.5
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97-G45 GAMING (MS-7821)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.5:bd11/10/2014:svnMSI:pnMS-7821:pvr1.0:rvnMSI:rnZ97-G45GAMING(MS-7821):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.name: MS-7821
dmi.product.version: 1.0
dmi.sys.vendor: MSI
version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.56-1~ubuntu2
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Wed Mar 18 14:17:36 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.16.0-1ubuntu1.2~trusty2
xserver.video_driver: radeon

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


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

** Summary changed:

- Flickering when using two graphics cards
+ Mouse cursor flickering when using two graphics cards

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

Title:
  Mouse cursor flickering when using two graphics cards

Status in xorg package in Ubuntu:
  New

Bug description:
  See bug #1278223

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-31.43~14.04.1-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.7
  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 Mar 18 22:40:10 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.3.10, 3.16.0-31-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7821]
   Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850] 
[1002:6819] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:042c]
  InstallationDate: Installed on 2015-02-24 (22 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: MSI MS-7821
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic 
root=UUID=cb3bd3ad-4c60-460e-8982-45ab28abdaf2 ro nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/10/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-G45 GAMING (MS-7821)
  dmi.board.vendor: MSI
  dmi.board.versi

[Touch-packages] [Bug 1433860] [NEW] computer info

2015-03-18 Thread darren

Public bug reported:

i can live boot ubuntu but cannot install.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
CasperVersion: 1.340
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Thu Mar 19 02:44:51 2015
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Toshiba America Info Systems Device [1179:fa20]
LiveMediaBuild: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
MachineType: TOSHIBA Satellite C55t-A
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed cdrom-detect/try-usb=true persistent noprompt 
floppy.allowed_drive_mask=0 ignore_uuid boot=casper quiet splash --
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/12/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 1.10
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: MP
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.10:bd04/12/2013:svnTOSHIBA:pnSatelliteC55t-A:pvrPSCF6U-01T00D:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: Satellite C55t-A
dmi.product.version: PSCF6U-01T00D
dmi.sys.vendor: TOSHIBA
version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.56-1~ubuntu2
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Wed Mar 18 18:11:14 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   16711 
 vendor SDC
xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

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

Title:
  computer info

Status in xorg package in Ubuntu:
  New

Bug description:
  i can live boot ubuntu but cannot install.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CasperVersion: 1.340
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Mar 19 02:44:51 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Device [1179:fa20]
  LiveMediaBuild: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
  MachineType: TOSHIBA Satellite C55t-A
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed cdrom-detect/try-usb=true persistent noprompt 
floppy.allowed_drive_mask=0 ignore_uuid boot=casper quiet splash --
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.10
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: MP
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr

[Touch-packages] [Bug 1278223] Re: Mouse Flickering after adding 3rd Monitor

2015-03-18 Thread Jonathan Wang

Same problem.

00:02.0 Display controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller (rev 06)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Pitcairn PRO [Radeon HD 7850]

Flickering on the two monitors connected to the AMD/ATI, no flickering
on the integrated.

ubuntu-bug report filed under #1433858

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

Title:
  Mouse Flickering after adding 3rd Monitor

Status in xorg package in Ubuntu:
  Incomplete
Status in xorg package in Fedora:
  Unknown

Bug description:
  My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse
  flickers (or blinks) when the cursor is on monitors one or two, but
  not 3.

  Monitor 1: 1440 x 900 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor
  Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor

  Here's the video card that feeds my laptop's native monitor, monitor 2
  (hdmi).

  lspci | grep 'VGA\|Display'
  00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)
  00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)

  The 3rd Monitor is powered through a Display Link certified SIIG USB
  2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but
  it is a sticker on back of the device):

  lsusb -tv
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
  |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M

  dmesg
  [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee
  [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [1.688351] usb 2-1: Product: VGA Display Adapter
  [1.688353] usb 2-1: Manufacturer: DisplayLink
  [1.688356] usb 2-1: SerialNumber: 119785

  Additionally, unity-control-center crashes sometimes after I "Restore
  previous settings", after selecting a resolution too high. This
  freezed my laptop, requiring a hard reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.1-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb  9 18:43:13 2014
  InstallationDate: Installed on 2014-02-02 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1433855] Re: package e2fsprogs 1.42.9-3ubuntu1 failed to install/upgrade: subprocess dpkg-split returned error exit status 2

** Tags removed: need-duplicate-check

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

Title:
  package e2fsprogs 1.42.9-3ubuntu1 failed to install/upgrade:
  subprocess dpkg-split returned error exit status 2

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  Fiz a atualização a tarde.
  Perdi o sistema.
  Formatei e instalei tudo de novo.
  Agora vai dar o mesmo problema e provavelmente vou ter que formatar tudo de 
novo.
  Por favor, corrijam essa atualização.

  Obrigado!
  Abraços.
  Felipe

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: e2fsprogs 1.42.9-3ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  Date: Wed Mar 18 23:06:32 2015
  DuplicateSignature: package:e2fsprogs:1.42.9-3ubuntu1:subprocess dpkg-split 
returned error exit status 2
  ErrorMessage: subprocess dpkg-split returned error exit status 2
  InstallationDate: Installed on 2015-03-18 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: e2fsprogs
  Title: package e2fsprogs 1.42.9-3ubuntu1 failed to install/upgrade: 
subprocess dpkg-split returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1433855] [NEW] package e2fsprogs 1.42.9-3ubuntu1 failed to install/upgrade: subprocess dpkg-split returned error exit status 2

2015-03-18 Thread Felipe Doná de Siqueira

Public bug reported:

Fiz a atualização a tarde.
Perdi o sistema.
Formatei e instalei tudo de novo.
Agora vai dar o mesmo problema e provavelmente vou ter que formatar tudo de 
novo.
Por favor, corrijam essa atualização.

Obrigado!
Abraços.
Felipe

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: e2fsprogs 1.42.9-3ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
Date: Wed Mar 18 23:06:32 2015
DuplicateSignature: package:e2fsprogs:1.42.9-3ubuntu1:subprocess dpkg-split 
returned error exit status 2
ErrorMessage: subprocess dpkg-split returned error exit status 2
InstallationDate: Installed on 2015-03-18 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
SourcePackage: e2fsprogs
Title: package e2fsprogs 1.42.9-3ubuntu1 failed to install/upgrade: subprocess 
dpkg-split returned error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package trusty

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

Title:
  package e2fsprogs 1.42.9-3ubuntu1 failed to install/upgrade:
  subprocess dpkg-split returned error exit status 2

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  Fiz a atualização a tarde.
  Perdi o sistema.
  Formatei e instalei tudo de novo.
  Agora vai dar o mesmo problema e provavelmente vou ter que formatar tudo de 
novo.
  Por favor, corrijam essa atualização.

  Obrigado!
  Abraços.
  Felipe

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: e2fsprogs 1.42.9-3ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  Date: Wed Mar 18 23:06:32 2015
  DuplicateSignature: package:e2fsprogs:1.42.9-3ubuntu1:subprocess dpkg-split 
returned error exit status 2
  ErrorMessage: subprocess dpkg-split returned error exit status 2
  InstallationDate: Installed on 2015-03-18 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: e2fsprogs
  Title: package e2fsprogs 1.42.9-3ubuntu1 failed to install/upgrade: 
subprocess dpkg-split returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1431107] Re: ordering cycles with early boot rcS scripts with inappropriate rc2.d links

2015-03-18 Thread Daniel Serpell

I have the same problem with udev,  screen-cleanup and udev-finish

 daniel@daniel-vaio:~$ grep Default-Start.*S /etc/rc[0-9].d/S0*
 /etc/rc2.d/S01udev:# Default-Start: S
 /etc/rc2.d/S02screen-cleanup:# Default-Start: S
 /etc/rc2.d/S02udev-finish:# Default-Start: S
 /etc/rc3.d/S01udev:# Default-Start: S
 /etc/rc3.d/S02screen-cleanup:# Default-Start: S
 /etc/rc3.d/S02udev-finish:# Default-Start: S
 /etc/rc4.d/S01udev:# Default-Start: S
 /etc/rc4.d/S02screen-cleanup:# Default-Start: S
 /etc/rc4.d/S02udev-finish:# Default-Start: S
 /etc/rc5.d/S01udev:# Default-Start: S
 /etc/rc5.d/S02screen-cleanup:# Default-Start: S
 /etc/rc5.d/S02udev-finish:# Default-Start: S

My system sometimes boots ok, sometimes pymouth keeps using CPU after
boot, sometimes NetworManagers can't run dnsmasq.

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

Title:
  ordering cycles with early boot rcS scripts with inappropriate rc2.d
  links

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  After switching to systemd, the AppArmor service often fails to start
  on boot.  This seems to happen at least 50% of the times I turn on the
  system.  If I attempt to start the process again after the system is
  otherwise finished booting, it works fine.  I also have another system
  with the same software configuration but a much slower storage system
  (HDD instead of SSD) which never suffers from this problem, so I think
  it is probably a race condition.  If I do "systemctl status apparmor",
  I get the following output:

  michael@mamarley-laptop:~$ sudo systemctl status apparmor
  ● apparmor.service - LSB: AppArmor initialization
 Loaded: loaded (/etc/init.d/apparmor)
 Active: failed (Result: exit-code) since Wed 2015-03-11 21:25:44 EDT; 1min 
5s ago
   Docs: man:systemd-sysv-generator(8)
Process: 237 ExecStart=/etc/init.d/apparmor start (code=exited, status=123)

  Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
  Mar 11 21:25:44 mamarley-laptop apparmor[237]: mkstemp: Read-only file system
  Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
  Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  Mar 11 21:25:44 mamarley-laptop systemd[1]: apparmor.service: control process 
exited, code=exited status=123
  Mar 11 21:25:44 mamarley-laptop apparmor[237]: ...fail!
  Mar 11 21:25:44 mamarley-laptop systemd[1]: Failed to start LSB: AppArmor 
initialization.
  Mar 11 21:25:44 mamarley-laptop systemd[1]: Unit apparmor.service entered 
failed state.
  Mar 11 21:25:44 mamarley-laptop systemd[1]: apparmor.service failed.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu5
  ProcVersionSignature: Ubuntu 3.19.0-9.9-lowlatency 3.19.1
  Uname: Linux 3.19.0-9-lowlatency x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 11 21:30:08 2015
  InstallationDate: Installed on 2014-06-01 (283 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.1)
  MachineType: LENOVO 2359CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-lowlatency 
root=UUID=1f7829ef-ffb8-4182-ac92-40d613ea78c9 ro elevator=deadline 
intel_pstate=enable "acpi_osi=Windows 2012"
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/21/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G4ETA2WW (2.62 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2359CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG4ETA2WW(2.62):bd08/21/2014:svnLENOVO:pn2359CTO:pvrThinkPadT530:rvnLENOVO:rn2359CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2359CTO
  dmi.product.version: ThinkPad T530
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1417581] Re: USC - mouse cursor on AMD graphics is drawing incorrectly

** Also affects: mir/0.12
   Importance: Undecided
   Status: New

** Changed in: mir/0.12
Milestone: None => 0.12.1

** Changed in: mir/0.12
   Status: New => Triaged

** Changed in: mir/0.12
   Importance: Undecided => High

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

Title:
  USC - mouse cursor on AMD graphics is drawing incorrectly

Status in Mir:
  Fix Committed
Status in Mir 0.12 series:
  Triaged
Status in mesa package in Ubuntu:
  New
Status in mir package in Ubuntu:
  Triaged

Bug description:
  I've a Lenovo Flex 2 14D, which has an AMD APU.

  In Unity-System-Compositor, the mouse cursor does not draw correctly.

  See previous version of this bug for visuals:
  https://bugs.launchpad.net/mir/+bug/1391975

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

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

[Touch-packages] [Bug 1428402] Re: ProtobufResponder::send_response_result race

** Also affects: mir/0.12
   Importance: Undecided
   Status: New

** Changed in: mir/0.12
Milestone: None => 0.12.1

** Changed in: mir/0.12
   Status: New => Triaged

** Changed in: mir/0.12
   Importance: Undecided => High

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

Title:
  ProtobufResponder::send_response_result race

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

Bug description:
  ProtobufResponder::send_response_result member must be protected as
  multiple threads call ProtobufResponder::send_response

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

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

[Touch-packages] [Bug 1240909] Re: [performance] Restore support for double-buffering by default

** Also affects: mir/0.12
   Importance: Undecided
   Status: New

** Changed in: mir/0.12
Milestone: None => 0.12.1

** Changed in: mir/0.12
   Status: New => Triaged

** Changed in: mir/0.12
   Importance: Undecided => High

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

Title:
  [performance] Restore support for double-buffering by default

Status in Mir:
  Fix Committed
Status in Mir 0.12 series:
  Triaged
Status in Mir 0.5 series:
  Won't Fix
Status in mir package in Ubuntu:
  Triaged

Bug description:
  We really should restore support for double-buffering where possible.
  Presently we're on triple-buffering all the time.

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

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

[Touch-packages] [Bug 1418569] Re: mir_demo_server doesn't emit hover_exit events

** Also affects: mir/0.12
   Importance: Undecided
   Status: New

** Changed in: mir/0.12
Milestone: None => 0.12.1

** Changed in: mir/0.12
   Status: New => Triaged

** Changed in: mir/0.12
   Importance: Undecided => High

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

Title:
  mir_demo_server doesn't emit hover_exit events

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

Bug description:
  The demo server doesn't emit hover_exit events when the pointer leaves
  a surface. It only happens when you switch away from the VT it is
  running on.

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

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

[Touch-packages] [Bug 1413211] Re: [regression] mali, powervr locks up with around the introduction or removal of a third overlay

** Also affects: mir/0.12
   Importance: Undecided
   Status: New

** Changed in: mir/0.12
Milestone: None => 0.12.1

** Changed in: mir/0.12
   Status: New => Triaged

** Changed in: mir/0.12
   Importance: Undecided => High

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

Title:
  [regression] mali, powervr locks up with around the introduction or
  removal of a third overlay

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

Bug description:
  To reproduce:
  Run mir_demo_server with overlays enabled and 3 onscreen surfaces. It will 
lock up within a few iterations of introducing and removing the 3rd surface.

  Should not affect the current stack (as we always have <= 2 surfaces)

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

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

[Touch-packages] [Bug 1427976] Re: SessionMediator locks mutexes in one thread and unlocks them in another

** Also affects: mir/0.12
   Importance: Undecided
   Status: New

** Changed in: mir/0.12
Milestone: None => 0.12.1

** Changed in: mir/0.12
   Status: New => Triaged

** Changed in: mir/0.12
   Importance: Undecided => High

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

Title:
  SessionMediator locks mutexes in one thread and unlocks them in
  another

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

Bug description:
  SessionMediator locks mutexes in one thread and unlocks them in
  another thread during create_surface or exchange_buffer. This can
  cause undefined behavior:

  http://www.cplusplus.com/reference/mutex/mutex/unlock/

  "If the mutex is not currently locked by the calling thread, it causes
  undefined behavior."

  This may potentially be the root cause of  a hang (wait handle never
  signals) seen when creating/destroying menu surfaces while a parent
  does swap_buffers.

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

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

[Touch-packages] [Bug 1425307] Re: [regression] Exception when running phablet-screenshot (mako/vivid 110) [std::exception::what: Attempt to set swap interval on screencast is invalid]

** Also affects: mir/0.12
   Importance: Undecided
   Status: New

** Changed in: mir/0.12
Milestone: None => 0.12.1

** Changed in: mir/0.12
   Status: New => Triaged

** Changed in: mir/0.12
   Importance: Undecided => High

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

Title:
  [regression] Exception when running phablet-screenshot (mako/vivid
  110) [std::exception::what: Attempt to set swap interval on screencast
  is invalid]

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

Bug description:
  current build number: 110
  device name: mako
  channel: ubuntu-touch/vivid-proposed
  last update: 2015-02-24 22:35:35
  version version: 110
  version ubuntu: 20150224
  version device: 20150210
  version custom: 20150224

  rsalveti@evasys:~$ phablet-screenshot /tmp/foo.png
  I: Dumping fb0 ...
  [1424817826.846470] Loader: Loading modules from: 
/usr/lib/arm-linux-gnueabihf/mir/client-platform/
  [1424817826.847569] Loader: Loading module: 
/usr/lib/arm-linux-gnueabihf/mir/client-platform/mesa.so
  [1424817826.848393] Loader: Loading module: 
/usr/lib/arm-linux-gnueabihf/mir/client-platform/android.so
  [1424817826.849583] Loader: Loading module: 
/usr/lib/arm-linux-gnueabihf/mir/client-platform/dummy.so
  [1424817826.944654]  mircommon: Caught exception at Mir/EGL driver 
boundary (in setSwapInterval): 
/build/buildd/mir-0.11.0+15.04.20150209.1/src/client/buffer_stream.cpp(283): 
Throw in function virtual void 
mir::client::BufferStream::request_and_wait_for_configure(MirSurfaceAttrib, int)
  Dynamic exception type: 
N5boost16exception_detail10clone_implINS0_19error_info_injectorISt11logic_error
  std::exception::what: Attempt to set swap interval on screencast is invalid

  3004 KB/s (3932160 bytes in 1.278s)
  I: Done

  phablet-tools - 1.1+15.04.20150218-0ubuntu1

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

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

[Touch-packages] [Bug 1433330] Re: Some protobuf Closure objects can access dead objects

** Also affects: mir/0.12
   Importance: Undecided
   Status: New

** Changed in: mir/0.12
Milestone: None => 0.12.1

** Changed in: mir/0.12
   Status: New => Triaged

** Changed in: mir/0.12
   Importance: Undecided => High

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

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

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

Title:
  Some protobuf Closure objects can access dead objects

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

Bug description:
  ProtobufMessageProcessor::dispatch will create a protobuf closure
  object that references the ProtobufMessageProcessor "this" pointer.

  The closure/callback object may be invoked by a different thread (e.g.
  SessionMediator::exchange_buffer). Since there's no protection there
  can be a race between dropping a connection (which destroys the
  ProtoBufMessageProcessor) and the callback being invoked by a
  compositor thread.

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

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

[Touch-packages] [Bug 1433761] Re: apt-key and add-apt-repository don't honor Acquire::http::Proxy

2015-03-18 Thread Maarten

See also: https://bugs.launchpad.net/maas/+bug/1257082

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

Title:
  apt-key and add-apt-repository don't honor Acquire::http::Proxy

Status in software-properties package in Ubuntu:
  New

Bug description:
  When setting the proxy server globally on the system for the APT
  package manager, add-apt-repository ignores the setting. This issue is
  present on all versions of Debian that I have tested.

  # cat /etc/apt/apt.conf.d/80proxy 
  Acquire::http::proxy "http://w.x.y.z:/";;

  # apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 5A9A06AEF9CB8DB0
  Executing: gpg --ignore-time-conflict --no-options --no-default-keyring 
--homedir /tmp/tmp.TIa517Kcw8 --no-auto-check-trustdb --trust-model always 
--keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyring 
/etc/apt/trusted.gpg.d/debian-archive-squeeze-automatic.gpg --keyring 
/etc/apt/trusted.gpg.d/debian-archive-squeeze-stable.gpg --keyring 
/etc/apt/trusted.gpg.d/debian-archive-wheezy-automatic.gpg --keyring 
/etc/apt/trusted.gpg.d/debian-archive-wheezy-stable.gpg --keyring 
/etc/apt/trusted.gpg.d/saltstack-salt.gpg --keyserver keyserver.ubuntu.com 
--recv-keys 5A9A06AEF9CB8DB0
  gpg: requesting key F9CB8DB0 from hkp server keyserver.ubuntu.com
  gpg: keyserver timed out
  gpg: keyserver receive failed: keyserver error

  This has serious repercussions. Unattended installs such as juju,
  maas, etc are all affected for anyone who is working behind a proxy.
  This is the case for most enterprise environments where such maas and
  juju setups will be tested out, and as such has great repercussions
  for Canonical as a viable supplier of OpenStack environments: if your
  product fails to install, you're not going to get the business.

  Considering that:

  * The setting to use already exists in /etc/apt/apt.conf and that all other 
tools use this correctly
  * The serious impact of this issue for downstream projects and Debian usage 
in the enterprise
  * The long time this issue has been standing and has affected people

  I suggest that this either

  1) be fixed, or
  2) the apt-key and add-apt-repository programs are renamed so that it is made 
clear they are not part of the APT suite of programs and therefor cannot be 
trusted to behave as if they were part of APT.

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

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

[Touch-packages] [Bug 1427654] Re: FFE: switch system init to systemd [not touch] in 15.04

See also bug 1399766.  I guess the question is whether having a non-
systemd installation is going to be supported and I hope the answer will
be yes.

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

Title:
  FFE: switch system init to systemd [not touch] in 15.04

Status in init-system-helpers package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in init-system-helpers source package in Vivid:
  Fix Released
Status in ubuntu-meta source package in Vivid:
  Fix Released

Bug description:
  As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411
  -systemd-migration we aimed for switching the system (not session)
  init from upstart to systemd this cycle. As this was by and large a
  1.2 man show, this took a little longer. One of the remaining blockers
  for switching the default was to fix NFS (bug 1312976) which is now
  ready to be uploaded. There is also juju (bug 1409639, landed upstream
  now) and maas (bug 1423613, scheduled), but for those we can work
  around missing systemd support by installing upstart on instances.

  We are a few days past feature freeze now, bug Steve and I discussed
  last week, and we still want to aim for switching the default in
  vivid. To be clear, this will affect Ubuntu desktop/server/cloud and
  the flavours like Kubuntu, but *NOT* ubuntu-touch. Migration to
  systemd is blocked on touch (too old kernels, some unported jobs), and
  was not scheduled for vivid. For that we need to ensure to keep
  upstart on Touch (there is a work item on the spec).

  I know from at least Kubuntu and Ubuntu GNOME that they are pushing
  for switching to systemd. We should get an ack from the others
  (Lubuntu/Xubuntu/MATE) before doing the switch; but quite a lot of
  vivid users are running systemd already, and I believe we shook out
  the worst bugs now.

  So if/once the release team generally agrees, these are the things
  which need to  happen before switching:

    * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) - DONE
    * Land NFS (bug 1312976) - DONE
    * Ensure Touch keeps upstart (bug 1428026) - DONE

  Operationally, the switch is merely to change s/upstart/systemd-sysv/
  in the seeds, i. e. flip the dependency in ubuntu-minimal. I did that
  in https://launchpad.net/~pitti/+archive/ubuntu/systemd, fixed
  ureadahead, and verified that upgrades from trusty and utopic cleanly
  upgrade to vivid+PPA with removing upstart and installing systemd-
  sysv.

  Around that time I will send a mail to ubuntu-devel-announce@ to warn
  about the impending switch, and give some pointers how to boot with
  upstart (from grub menu or reinstalling upstart), how to debug
  boot/shutdown issues, etc.

  Contingency plan: This will trigger wider testing, and most certainly
  uncover more integration issues. I'll try to keep up with them, but if
  we get to a point where we find that there are too many/too serious
  regressions, we can flip the seed back to upstart and get back to the
  situation today.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1427654/+subscriptions

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

[Touch-packages] [Bug 1399766] Re: ubuntu-minimal should depend on "either upstart or systemd"

I believe this is in ubuntu-standard now -> bug 1427654

** Changed in: ubuntu-meta (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  ubuntu-minimal should depend on "either upstart or systemd"

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  It seems to me, that "ubuntu-minimal" metapackage should depend on
  "either systemd or upstart", because both of them are completely
  usable, but now if I remove upstart, ubuntu-miminal is also removed
  and it can cause some problems with packages to be autoremoved.

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

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

[Touch-packages] [Bug 1427654] Re: FFE: switch system init to systemd [not touch] in 15.04

would it be possible to have ubuntu-standard depend on "systemd|upstart"
instead of systemd only?  I'd like to avoid systemd while having ubuntu-
standard installed for a fully supported system.

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

Title:
  FFE: switch system init to systemd [not touch] in 15.04

Status in init-system-helpers package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in init-system-helpers source package in Vivid:
  Fix Released
Status in ubuntu-meta source package in Vivid:
  Fix Released

Bug description:
  As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411
  -systemd-migration we aimed for switching the system (not session)
  init from upstart to systemd this cycle. As this was by and large a
  1.2 man show, this took a little longer. One of the remaining blockers
  for switching the default was to fix NFS (bug 1312976) which is now
  ready to be uploaded. There is also juju (bug 1409639, landed upstream
  now) and maas (bug 1423613, scheduled), but for those we can work
  around missing systemd support by installing upstart on instances.

  We are a few days past feature freeze now, bug Steve and I discussed
  last week, and we still want to aim for switching the default in
  vivid. To be clear, this will affect Ubuntu desktop/server/cloud and
  the flavours like Kubuntu, but *NOT* ubuntu-touch. Migration to
  systemd is blocked on touch (too old kernels, some unported jobs), and
  was not scheduled for vivid. For that we need to ensure to keep
  upstart on Touch (there is a work item on the spec).

  I know from at least Kubuntu and Ubuntu GNOME that they are pushing
  for switching to systemd. We should get an ack from the others
  (Lubuntu/Xubuntu/MATE) before doing the switch; but quite a lot of
  vivid users are running systemd already, and I believe we shook out
  the worst bugs now.

  So if/once the release team generally agrees, these are the things
  which need to  happen before switching:

    * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) - DONE
    * Land NFS (bug 1312976) - DONE
    * Ensure Touch keeps upstart (bug 1428026) - DONE

  Operationally, the switch is merely to change s/upstart/systemd-sysv/
  in the seeds, i. e. flip the dependency in ubuntu-minimal. I did that
  in https://launchpad.net/~pitti/+archive/ubuntu/systemd, fixed
  ureadahead, and verified that upgrades from trusty and utopic cleanly
  upgrade to vivid+PPA with removing upstart and installing systemd-
  sysv.

  Around that time I will send a mail to ubuntu-devel-announce@ to warn
  about the impending switch, and give some pointers how to boot with
  upstart (from grub menu or reinstalling upstart), how to debug
  boot/shutdown issues, etc.

  Contingency plan: This will trigger wider testing, and most certainly
  uncover more integration issues. I'll try to keep up with them, but if
  we get to a point where we find that there are too many/too serious
  regressions, we can flip the seed back to upstart and get back to the
  situation today.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1427654/+subscriptions

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

[Touch-packages] [Bug 1399766] Re: ubuntu-minimal should depend on "either upstart or systemd"

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

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Confirmed

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

Title:
  ubuntu-minimal should depend on "either upstart or systemd"

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  It seems to me, that "ubuntu-minimal" metapackage should depend on
  "either systemd or upstart", because both of them are completely
  usable, but now if I remove upstart, ubuntu-miminal is also removed
  and it can cause some problems with packages to be autoremoved.

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

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

[Touch-packages] [Bug 1429938] Re: reboot does not return under systemd

** Tags added: regression-release

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

Title:
  reboot does not return under systemd

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  On Trusty and Utopic, when you run `apt-get remove openssh-server`
  over an SSH connection, your existing SSH connection remains open, so
  it's possible to run additional commands afterward.

  However, on Vivid now that the switch to systemd has been made,  `apt-
  get remove openssh-server` closes the existing SSH connection
  immediately, causing your SSH client to exit with a non-zero status. I
  have a hunch there's a lot of automation tooling out there that relies
  on the old behavior.

  For what it's worth, this change breaks the internal image mastering
  tools that System76 uses. Prior to exporting an image tarball, I spin
  up a golden VM with qemu, rysnc a script to it, and then execute this
  script over SSH.

  The important step is that I need to remove openssh-server prior to
  shutting down the VM, so these scripts always end with something like
  this:

  apt-get -y purge openssh-server ssh-import-id
  apt-get -y autoremove
  shutdown -h now

  As far as I can tell, this behavior change will likewise be a problem
  when running `do-release-upgrade` on a remote server over SSH. Or more
  generally, anytime you run "apt-get upgrade/dist-upgrade" via SSH, it
  seems this would be a problem whenever the openssh-server package
  happens to be updated.

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

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

[Touch-packages] [Bug 1354180] Re: Regression: Ctrl+Alt+T doesn't open a terminal

as of now, the shortcut seems to be working correctly

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

Title:
  Regression: Ctrl+Alt+T doesn't open a terminal

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

Bug description:
  Not sure Unity is the package.

  Ctrl+Alt+T used to be the keyboard shortcut for opening a new terminal
  window (whether or not one was already open).

  It doesn't work any more.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.2+14.04.20140714-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-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: Thu Aug  7 23:12:06 2014
  InstallationDate: Installed on 2013-10-11 (300 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-05-24 (75 days ago)

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

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

[Touch-packages] [Bug 1314780] Re: Full screen between xorg and VMWare-Workstation

2015-03-18 Thread mitchell486

@xlash911, the only workaround I found was to simply navigate to the
full screen VMWare window, click, press CTRL+ALT which made it select
OUT of the window, then click in again. It was a trivial step and really
became like a second nature since I used CTRL+ALT to navigate my
workspaces anyway. I hope this helps and sorry I don't have a better
answer.

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

Title:
Full screen between xorg and VMWare-Workstation

Status in xorg package in Ubuntu:
Confirmed

Bug description:
This is a minor bug that seems to be a conflict between xorg and
VMWare Workstation 9 in Ubuntu 14.04. It seems most noticeable and
prevalent with dual monitors. This issue was not present in 12.04. The
taskbar at the top of the screen that is always present seems to give
issues with full screen VMWare. In 12.04, it would stay at the top for
a bit and then go away if you clicked anywhere in the full screen
window. With 14.04, it doesn't show up at all anymore but it is still
"there". It is a ghost of it and then will be a selectable option. If
you click in the full screen window anywhere, the taskbar does not
show at the top, but it is still selectable as an option. The "focus"
does not go to the full screen. You can do things in there as long as
the thing you are trying to do doesn't reside at the top of the screen
where it would be the taskbar. Once you select the "top of the screen
where the taskbar should be, this makes the VMWare window the active
window in xorg, it then goes on top of the taskbar again. This is a
major inconvenience bug because when you try to select anything in the
top right while the taskbar is still "on top" of the full screen
without appearing to be on top, it will select either the calendar or
power settings or anything up in the top right.

Attached are screenshots as the process happens.

Step 1. Click on the screen which ISN'T FULL SCREEN VMWARE.
Step 2. Click anywhere in full screen VMWare window except top where taskbar
resides. Taskbar is hidden but still "on top".
Step 3. Click where taskbar is in right corner and it will overtake the full
screen window. You can select date, power, english, etc..
Step 4. Click anywhere else at very top of screen, taskbar will then go away
and VMWare fullscreen will work properly.

EDIT: Apparently I have been calling the bar at the top the wrong
name. It's MenuBar. The Ubuntu MenuBar is not playing well with
fullscreen VMWare Workstation. It also doesn't show up for using File,
Edit, etc...

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CompizPlugins:
[core,composite,opengl,compiztoolbox,decor,resize,mousepoll,regex,gnomecompat,imgpng,place,wall,snap,animation,grid,unitymtgrabhandles,move,fade,vpswitch,expo,session,workarounds,ezoom,scale,unityshell]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed Apr 30 10:47:50 2014
DistUpgraded: 2014-04-28 18:43:58,883 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166]
(rev 09) (prog-if 00 [VGA controller])
Subsystem: Lenovo Device [17aa:21f6]
InstallationDate: Installed on 2013-06-07 (327 days ago)
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64
(20130213)
MachineType: LENOVO 2392ARU
ProcEnviron:
LANGUAGE=en_US
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic
root=UUID=2abc73fb-99e8-4973-8796-c8fb273307bb ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to trusty on 2014-04-28 (1 days ago)
dmi.bios.date: 02/22/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: G4ET93WW (2.53 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2392ARU
dmi.board.vendor: LENOVO
dmi.board.version: Win8 Pro DPK TPG
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvrG4ET93WW(2.53):bd02/22/2013:svnLENOVO:pn2392ARU:pvrThinkPadT530:rvnLENOVO:rn2392ARU:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2392ARU
dmi.product.version: ThinkPad T530
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1

[Touch-packages] [Bug 1432829] Re: resolvconf not updated correctly for interfaces configured in initramfs

2015-03-18 Thread Scott Moser

** Patch added: "proposed fix"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432829/+attachment/4349395/+files/lp-1432829.diff

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

Title:
  resolvconf not updated correctly for interfaces configured in
  initramfs

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  maas images utilize cloud-initramfs-dyn-netconf . The way this works is 
basically:
   * /etc/network/interfaces in image is a link to 
../../run/network/dynamic-interfaces
   * kernel command line 'ip=' convince the initramfs to bring up networking 
using 'ipconfig'
     example: ip=maas-enlist:BOOTIF
   * ipconfig writes files in /run/net-*.conf for each interface it configures.
   * cloud-initramfs-dyn-netconf module writes /run/network/dyanmic-interfaces 
based on /run/net-*.conf files that 'ipconfig' creates.

  end result is that after the move to real root,
  /etc/network/interfaces should be a symlink to /run/ that ends up
  having something like this:

   | ## This file is generated by cloud-initramfs-dyn-netconf
   | auto lo
   | iface lo inet loopback
   | manual eth0
   | iface eth0 inet dhcp
   | dns-nameservers 192.168.64.3
   | dns-search maas

  resolvconf seems not to be working as well as it should be.  In vivid
  (now using systemd), I have only the resolvconf header in the file.

   in all other supported ubuntu releases, doing the above results in 
functional resolv.conf via resolv.conf. Seen here from trusty:
   | # Dynamic resolv.conf(5) file for glibc resolver(3) generated by 
resolvconf(8)
   | # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
   | nameserver 192.168.64.3

  Related Bugs:
   *  bug 1432821: something deleting /run/network after during boot

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: resolvconf 1.69ubuntu1.1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  Date: Mon Mar 16 20:42:24 2015
  PackageArchitecture: all
  ProcEnviron:
   TERM=vt102
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: resolvconf
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1432829] Re: resolvconf not updated correctly for interfaces configured in initramfs

2015-03-18 Thread Scott Moser

I've made this affect systemd as that is where I have the fix for it.
I could fix in open-iscsi as it was in upstart, but I think adding general 
infrastructure that considers open-iscsi is more sane than open-iscsi playing 
around with tricking ifupdown.


** Package changed: resolvconf (Ubuntu) => systemd (Ubuntu)

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

** Changed in: systemd (Ubuntu)
   Status: New => 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/1432829

Title:
  resolvconf not updated correctly for interfaces configured in
  initramfs

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  maas images utilize cloud-initramfs-dyn-netconf . The way this works is 
basically:
   * /etc/network/interfaces in image is a link to 
../../run/network/dynamic-interfaces
   * kernel command line 'ip=' convince the initramfs to bring up networking 
using 'ipconfig'
     example: ip=maas-enlist:BOOTIF
   * ipconfig writes files in /run/net-*.conf for each interface it configures.
   * cloud-initramfs-dyn-netconf module writes /run/network/dyanmic-interfaces 
based on /run/net-*.conf files that 'ipconfig' creates.

  end result is that after the move to real root,
  /etc/network/interfaces should be a symlink to /run/ that ends up
  having something like this:

   | ## This file is generated by cloud-initramfs-dyn-netconf
   | auto lo
   | iface lo inet loopback
   | manual eth0
   | iface eth0 inet dhcp
   | dns-nameservers 192.168.64.3
   | dns-search maas

  resolvconf seems not to be working as well as it should be.  In vivid
  (now using systemd), I have only the resolvconf header in the file.

   in all other supported ubuntu releases, doing the above results in 
functional resolv.conf via resolv.conf. Seen here from trusty:
   | # Dynamic resolv.conf(5) file for glibc resolver(3) generated by 
resolvconf(8)
   | # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
   | nameserver 192.168.64.3

  Related Bugs:
   *  bug 1432821: something deleting /run/network after during boot

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: resolvconf 1.69ubuntu1.1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  Date: Mon Mar 16 20:42:24 2015
  PackageArchitecture: all
  ProcEnviron:
   TERM=vt102
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: resolvconf
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1372254] Re: New Event in Calendar app not scheduled for the correct time zone.

2015-03-18 Thread Kunal Parmar

** Branch linked: lp:~renatofilho/qtorganizer5-eds/fix-1311165

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

Title:
  New Event in Calendar app not scheduled for the correct time zone.

Status in Calendar application for Ubuntu devices:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Invalid

Bug description:
  Phone - LGE Nexus 4
  OS Version - Ubuntu 14.10 (r48)
  Time zone - America/Los Angeles - UTC-7
  Steps to reproduce: 
  Calendar view is for the month.
  1 - select 'New Event' in the calendar app
  2 - enter event information, set the date as the current date (21-Sep-2014)
  3 - enter a start time = 21:30
  4 - enter an end time = 22:30
  5 - use 'Personal' calendar
  6 - save the event
  An event is created for 'Tomorrow at 4:30 am', not 21:30 for the current date

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

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

[Touch-packages] [Bug 1433829] [NEW] apparmor fails to compile deny link rules

2015-03-18 Thread John Johansen

Public bug reported:

The apparmor_parser fails to compile deny rules with only link
permissions.

  Eg.
 deny /f l,
 deny l /f,
 deny link /f -> /d,

  Will all fail to compile with the following assert

apparmor_parser: aare_rules.cc:99: Node* convert_file_perms(int,
uint32_t, uint32_t, bool): Assertion `perms != 0' failed.

** Affects: apparmor
 Importance: Undecided
 Status: Confirmed

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

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

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

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

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

Title:
  apparmor fails to compile deny link rules

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

Bug description:
  The apparmor_parser fails to compile deny rules with only link
  permissions.

Eg.
   deny /f l,
   deny l /f,
   deny link /f -> /d,

Will all fail to compile with the following assert

  apparmor_parser: aare_rules.cc:99: Node* convert_file_perms(int,
  uint32_t, uint32_t, bool): Assertion `perms != 0' failed.

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

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

[Touch-packages] [Bug 1069964] Re: Unable to mount Blank CD-R disc. Location is already mounted.

2015-03-18 Thread Erick Brunzell

Actually a variant of this still exists in Ubuntu GNOME Vivid (as of
20150318) the difference being that, instead of getting the "already
mounted" warning as you do in a flashback session, in a GNOME Shell
session if you click the close button on the Open with CD/DVD creator or
Eject notification as soon as it closes it pops right back up until you
click it a second time.

I haven't checked the flashback session in Vivid yet but I will in the
next few days. I suspect that more than one process is attempting to
handle this, one being Nautilus . I'm clueless what the
other might be.

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

Title:
  Unable to mount Blank CD-R disc. Location is already mounted.

Status in OEM Priority Project:
  New
Status in glib2.0 package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  This error message comes up, while still able to burn, read/write etc. It 
occurs in quantal when inserting a CD/DVD into the drive, but it did not happen 
in precice.
  Screenshot:
  http://i47.tinypic.com/4v0aj6.png

  Burner: LG HL-DT-ST DVDRAM GH24NS90

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: gnome-settings-daemon 3.4.2-0ubuntu14
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  Date: Mon Oct 22 19:50:35 2012
  ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-fallback-mount-helper
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1069964/+subscriptions

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

[Touch-packages] [Bug 1428571] Re: Software Update - mysql-apt-config - can't continue

2015-03-18 Thread Goran Pedic

I've managed to resolve this issue by removing mysql-apt-config.

My /var/log/dpkg.log said:
2015-03-18 16:02:41 startup packages configure
2015-03-18 16:02:41 configure mysql-apt-config:all 0.3.3-1ubuntu14.04 
2015-03-18 16:02:41 status half-configured mysql-apt-config:all 
0.3.3-1ubuntu14.04

mysql-apt-config was half-configured (because I had to kill it) so I couldn't 
use apt-get because it would just tell me to:
'sudo dpkg --configure -a' (which would not work)

I first tried to remove mysql-apt-config using (don't do this, a better 
solution is offered in the linked thread bellow):
sudo dpkg --remove --force-remove-reinstreq mysql-apt-config

as I couldn't use apt-get or aptitude, but this just managed to bork up
my system somewhat as I couldn't properly update or re-install mysql,
but at least I was able to use apt-get/aptitude now.

On trying to reinstall mysql-server-5.6:
dpkg: error processing archive 
/var/cache/apt/archives/mysql-client-5.6_5.6.19-0ubuntu0.14.04.1_amd64.deb 
(--unpack):
 trying to overwrite '/usr/share/man/man1/mysql_config_editor.1.gz', which is 
also in package libmysqlclient-dev 5.6.23-1ubuntu14.04
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Processing triggers for man-db (2.6.7.1-1) ...
Errors were encountered while processing:
 /var/cache/apt/archives/mysql-client-5.6_5.6.19-0ubuntu0.14.04.1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:
Setting up mysql-client-core-5.6 (5.6.19-0ubuntu0.14.04.1) ...
dpkg: dependency problems prevent configuration of mysql-server-5.6:
 mysql-server-5.6 depends on mysql-client-5.6 (>= 5.6.19-0ubuntu0.14.04.1); 
however:
  Package mysql-client-5.6 is not installed.

dpkg: error processing package mysql-server-5.6 (--configure):
 dependency problems - leaving unconfigured
Setting up mysql-common-5.6 (5.6.19-0ubuntu0.14.04.1) ...
Setting up mysql-server-core-5.6 (5.6.19-0ubuntu0.14.04.1) ...
Errors were encountered while processing:
 mysql-server-5.6


THE SOLUTION:
Finally the accepted answer here helped me resolve the issue for good:
https://stackoverflow.com/questions/27154067/could-not-select-ok-in-mysql-apt-config-ubuntu-14-04

If you need to reinstall mysql-server you may want to purge mysql-
common, it doesn't seem to get removed automatically along with mysql-
server/client, this was also giving me some issues.

I've removed mysql-apt-config from my system (it doesn't seem to be
really needed, and I hope this will help avoid a similar situation in
the future), reinstalled msyql-server-5.6 and everything is working fine
now, but I don't really get the point of all this, why would I ever want
to choose between mysql 5.6 and 5.7-dmr if I explicitly installed 5.6.
There should be a separate package for 5.7 for imho.

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

Title:
  Software Update - mysql-apt-config - can't continue

Status in debconf package in Ubuntu:
  Confirmed

Bug description:
  Upon running software updater today, it's tried to update mysql-apt-
  config, and running that has popped up a debconf choice screen (see
  attached).

  However selecting any of the options, pressing the "Forward" button
  does absolutely nothing. Can't close the window, can't continue, it's
  just stuck like that.

  I bet if I restart the machine everything will end up in a broken
  state too! :D

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: debconf 1.5.53ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar  5 09:53:44 2015
  ExecutablePath: /usr/bin/debconf-communicate
  InstallationDate: Installed on 2013-07-31 (581 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  InterpreterPath: /usr/bin/perl
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_GB.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   LANGUAGE=en_GB:en
  SourcePackage: debconf
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 955193] Re: Menu bar - add option for the global menu to make it always visible

** Description changed:

+ [ Impact ]
  
- 1) In System Settings/Appearance/Behavior ( see section 2.2 of 
http://tinyurl.com/7c7nofq ), the "Application Menu" options should be 
"Integrated in menu bar and hidden" (default) and "Integrated in menu bar and 
visible"
+ [Test Case]
  
- 2) If "Integrated in menu bar and visible" is selected, the menus should
- always be shown, in exactly the same manner they are currently displayed
- when the pointer is moved over the menu bar.
+ (1) enable menus in the window title bar System Settings > Appearance > 
Behavior > Show the menus for a window > In the menu bar
+ (2) run "gsettings set com.canonical.Unity always-show-menus true" in a 
terminal
+ (3) move the mouse around between windows
+ 
+ The menus should remain displayed
+ 
+ [Regression Potential]
+ 
+ Any change to the menu functionality has the potential to cause
+ volunteer functionality in menu behaviour.
+ 
+ [Other Info]
+ 
+ The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu "Vivid
+ Vervet" dev release where it has been in production use for some time
+ with no apparent regression.

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

Title:
  Menu bar - add option for the global menu to make it always visible

Status in Ayatana Design:
  Triaged
Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  New

Bug description:
  [ Impact ]

  [Test Case]

  (1) enable menus in the window title bar System Settings > Appearance > 
Behavior > Show the menus for a window > In the menu bar
  (2) run "gsettings set com.canonical.Unity always-show-menus true" in a 
terminal
  (3) move the mouse around between windows

  The menus should remain displayed

  [Regression Potential]

  Any change to the menu functionality has the potential to cause
  volunteer functionality in menu behaviour.

  [Other Info]

  The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu "Vivid
  Vervet" dev release where it has been in production use for some time
  with no apparent regression.

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

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

[Touch-packages] [Bug 1432882] Re: libclang1 has wrong standard include paths

2015-03-18 Thread Corentin SCHREIBER

Sorry for the flood of message. I just want to report that the issue can
be fixed temporarilly by adding this missing include path manually using
the command line option: -isystem /usr/include/clang/3.4/include

Note that the usual "-I /usr/include/clang/3.4/include" will not work,
since the GCC headers will be found first.

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

Title:
  libclang1 has wrong standard include paths

Status in llvm-toolchain-3.4 package in Ubuntu:
  New

Bug description:
  Bug affects all versions of libclang1 I could test (3.3, 3.4 and 3.5).
  The precise version of libclang I have is 1:3.4-1ubuntu3.
  Running Ubuntu 14.04 (Linux Mint 17.1).

  When building a minimal libclang program (refgen.cpp, attached) and using the 
"-print-search-dirs" command line argument to output the standard header search 
directories, libclang outputs the following:
  programs: =:/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../x86_64-linux-gnu/bin
  libraries: 
=../lib/clang/3.4:/usr/lib/gcc/x86_64-linux-gnu/4.8:/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu:/lib/x86_64-linux-gnu:/lib/../lib64:/usr/lib/x86_64-linux-gnu:/usr/lib/gcc/x86_64-linux-gnu/4.8/../../..:/lib:/usr/lib

  Notice the leading "../lib/clang/3.4" in "libraries", which does not
  make any sense and is likely missing part of the path. Notice also the
  leading ":" in "programs", which probably doesn't hurt, but looks
  suspicious.

  For reference, running clang (3.4) with the same command line argument 
outputs:
  programs: 
=/usr/bin:/usr/bin/../lib/gcc/x86_64-linux-gnu/4.8/../../../../x86_64-linux-gnu/bin
  libraries: 
=/usr/bin/../lib/clang/3.4:/usr/bin/../lib/gcc/x86_64-linux-gnu/4.8:/usr/bin/../lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu:/lib/x86_64-linux-gnu:/lib/../lib64:/usr/lib/x86_64-linux-gnu:/usr/bin/../lib/gcc/x86_64-linux-gnu/4.8/../../..:/lib:/usr/lib

  One can see here that the leading "/usr/bin/" has probably been
  stripped somehow from the "programs" and "libraries" search paths in
  libclang1.

  The end result is that libclang1 does not find clang's standard headers, and 
falls back to using GCC's, which it does not support.
  In my case, this means that if I try to parse even the simplest of files 
(test.cpp, attached) with this libclang1 and C++11 support enabled, the parsing 
fails because libclang1 is failing to understand GCC's SSE intrinsics in 
/usr/lib/gcc/x86_64-linux-gnu/4.8/include/ia32intrin.h, generating lots of 
errors:
  /usr/lib/gcc/x86_64-linux-gnu/4.8/include/ia32intrin.h:41:10: error: use of 
undeclared identifier '__builtin_ia32_bsrsi'
  /usr/lib/gcc/x86_64-linux-gnu/4.8/include/ia32intrin.h:89:10: error: use of 
undeclared identifier '__builtin_ia32_rdpmc'
  /usr/lib/gcc/x86_64-linux-gnu/4.8/include/ia32intrin.h:97:10: error: use of 
undeclared identifier '__builtin_ia32_rdtsc'
  /usr/lib/gcc/x86_64-linux-gnu/4.8/include/ia32intrin.h:105:10: error: use of 
undeclared identifier '__builtin_ia32_rdtscp'
  /usr/lib/gcc/x86_64-linux-gnu/4.8/include/ia32intrin.h:113:10: error: use of 
undeclared identifier '__builtin_ia32_rolqi'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.4/+bug/1432882/+subscriptions

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

[Touch-packages] [Bug 1390562] Re: Moving the mouse out from the decoration hides the LIMs when Alt is pressed

** Description changed:

+ [Impact]
+ 
+ Pressing the Alt key while a locally integrated menu is open causes the
+ menu to hide.
+ 
+ [Test Case]
+ 
  Prerequisite: from Appearance -> Behavior -> Set menu visible in window
  titlebar
  
  1. Open a window with menus
  2. Press and keep pressed the Alt key
  3. Menus will show
  4. Move the mouse over the window decoration
  5. Move the mouse out from the window decoration
  
- Actual behavior:
+ Incorrect behavior:
  6. Menus hides, also if the Alt key is pressed.
  
  Expected:
  6. Menus should stay visible until the Alt key is released.
+ 
+ [Regression Potential]
+ 
+ Additional incorrect menu behaviour may be introduced.
+ 
+ [Other Info]
+ 
+ The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu "Vivid
+ Vervet" dev release where it has been in use for some time without
+ apparent regression.

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

Title:
  Moving the mouse out from the decoration hides the LIMs when Alt is
  pressed

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

Bug description:
  [Impact]

  Pressing the Alt key while a locally integrated menu is open causes
  the menu to hide.

  [Test Case]

  Prerequisite: from Appearance -> Behavior -> Set menu visible in
  window titlebar

  1. Open a window with menus
  2. Press and keep pressed the Alt key
  3. Menus will show
  4. Move the mouse over the window decoration
  5. Move the mouse out from the window decoration

  Incorrect behavior:
  6. Menus hides, also if the Alt key is pressed.

  Expected:
  6. Menus should stay visible until the Alt key is released.

  [Regression Potential]

  Additional incorrect menu behaviour may be introduced.

  [Other Info]

  The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu "Vivid
  Vervet" dev release where it has been in use for some time without
  apparent regression.

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

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

[Touch-packages] [Bug 1433330] Re: Some protobuf Closure objects can access dead objects

2015-03-18 Thread PS Jenkins bot

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

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

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

Title:
  Some protobuf Closure objects can access dead objects

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

Bug description:
  ProtobufMessageProcessor::dispatch will create a protobuf closure
  object that references the ProtobufMessageProcessor "this" pointer.

  The closure/callback object may be invoked by a different thread (e.g.
  SessionMediator::exchange_buffer). Since there's no protection there
  can be a race between dropping a connection (which destroys the
  ProtoBufMessageProcessor) and the callback being invoked by a
  compositor thread.

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

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

[Touch-packages] [Bug 1427359] Re: ubuntu-device-flash fails to flash image once it reboots into recovery mode

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

** Changed in: android-tools (Ubuntu)
   Status: New => Confirmed

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

Title:
  ubuntu-device-flash fails to flash image once it reboots into recovery
  mode

Status in android-tools package in Ubuntu:
  Confirmed

Bug description:
  Running Ubuntu Trusty 14.04 and the latest packages from the android-
  tools PPA: https://launchpad.net/~phablet-team/+archive/ubuntu/tools

  1. Try to flash a krillin device via: ubuntu-device-flash touch 
--channel=ubuntu-touch/ubuntu-rtm/14.09
  2. Observe that at the time of this bug, RTM image 19 is downloaded and 
pushed to the phone successfully.
  3. u-d-f reboots the phone into recovery mode and you see the Ubuntu logo 
spinning.
  4. u-d-f complains that it failed to enter recovery after about 60 seconds.

  See the log output for more details. [1]

  
  [1] http://pastebin.ubuntu.com/10505648/

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

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

[Touch-packages] [Bug 1432882] Re: libclang1 has wrong standard include paths

2015-03-18 Thread Corentin SCHREIBER

I could spot the difference between the two versions. It can be seen by running:
./refgen test.cpp -std=c++11 -v

With the ubuntu libclang, the output I get is (stripped to the essential bits):
Selected GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.8
ignoring nonexistent directory 
"/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../include/c++/4.8/x86_64-linux-gnu"
ignoring nonexistent directory "../lib/clang/3.4/include"
ignoring nonexistent directory "/include"
#include "..." search starts here:
#include <...> search starts here:
 /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../include/c++/4.8
 /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../include/c++/4.8/backward
 /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../include/x86_64-linux-gnu/c++/4.8
 /usr/local/include
 /usr/lib/gcc/x86_64-linux-gnu/4.8/include
 /usr/include/x86_64-linux-gnu
 /usr/include
End of search list.

However, with the PPA libclang, the output is:
Selected GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.8
ignoring nonexistent directory 
"/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../include/c++/4.8/x86_64-linux-gnu"
ignoring nonexistent directory "../lib/clang/3.4.2/include"
ignoring nonexistent directory "/include"
#include "..." search starts here:
#include <...> search starts here:
 /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../include/c++/4.8
 /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../include/c++/4.8/backward
 /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../include/x86_64-linux-gnu/c++/4.8
 /usr/include/clang/3.4.2/include
 /usr/local/include
 /usr/lib/gcc/x86_64-linux-gnu/4.8/include
 /usr/include/x86_64-linux-gnu
 /usr/include
End of search list.

It is essentially identical, except that the PPA version has one additional 
line that makes it all work:
 /usr/include/clang/3.4.2/include

Now where this line came from, or why was it removed in the official
ubuntu version, I have no clue... I will contact the author of the PPA
to see if he could help.

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

Title:
  libclang1 has wrong standard include paths

Status in llvm-toolchain-3.4 package in Ubuntu:
  New

Bug description:
  Bug affects all versions of libclang1 I could test (3.3, 3.4 and 3.5).
  The precise version of libclang I have is 1:3.4-1ubuntu3.
  Running Ubuntu 14.04 (Linux Mint 17.1).

  When building a minimal libclang program (refgen.cpp, attached) and using the 
"-print-search-dirs" command line argument to output the standard header search 
directories, libclang outputs the following:
  programs: =:/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../x86_64-linux-gnu/bin
  libraries: 
=../lib/clang/3.4:/usr/lib/gcc/x86_64-linux-gnu/4.8:/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu:/lib/x86_64-linux-gnu:/lib/../lib64:/usr/lib/x86_64-linux-gnu:/usr/lib/gcc/x86_64-linux-gnu/4.8/../../..:/lib:/usr/lib

  Notice the leading "../lib/clang/3.4" in "libraries", which does not
  make any sense and is likely missing part of the path. Notice also the
  leading ":" in "programs", which probably doesn't hurt, but looks
  suspicious.

  For reference, running clang (3.4) with the same command line argument 
outputs:
  programs: 
=/usr/bin:/usr/bin/../lib/gcc/x86_64-linux-gnu/4.8/../../../../x86_64-linux-gnu/bin
  libraries: 
=/usr/bin/../lib/clang/3.4:/usr/bin/../lib/gcc/x86_64-linux-gnu/4.8:/usr/bin/../lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu:/lib/x86_64-linux-gnu:/lib/../lib64:/usr/lib/x86_64-linux-gnu:/usr/bin/../lib/gcc/x86_64-linux-gnu/4.8/../../..:/lib:/usr/lib

  One can see here that the leading "/usr/bin/" has probably been
  stripped somehow from the "programs" and "libraries" search paths in
  libclang1.

  The end result is that libclang1 does not find clang's standard headers, and 
falls back to using GCC's, which it does not support.
  In my case, this means that if I try to parse even the simplest of files 
(test.cpp, attached) with this libclang1 and C++11 support enabled, the parsing 
fails because libclang1 is failing to understand GCC's SSE intrinsics in 
/usr/lib/gcc/x86_64-linux-gnu/4.8/include/ia32intrin.h, generating lots of 
errors:
  /usr/lib/gcc/x86_64-linux-gnu/4.8/include/ia32intrin.h:41:10: error: use of 
undeclared identifier '__builtin_ia32_bsrsi'
  /usr/lib/gcc/x86_64-linux-gnu/4.8/include/ia32intrin.h:89:10: error: use of 
undeclared identifier '__builtin_ia32_rdpmc'
  /usr/lib/gcc/x86_64-linux-gnu/4.8/include/ia32intrin.h:97:10: error: use of 
undeclared identifier '__builtin_ia32_rdtsc'
  /usr/lib/gcc/x86_64-linux-gnu/4.8/include/ia32intrin.h:105:10: error: use of 
undeclared identifier '__builtin_ia32_rdtscp'
  /usr/lib/gcc/x86_64-linux-gnu/4.8/include/ia32intrin.h:113:10: error: use of 
undeclared identifier '__builtin_ia32_rolqi'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.4

[Touch-packages] [Bug 1427708] Re: indicator-sound-service crashed with g_error("Unable to get session bus")

2015-03-18 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/1427708

** Tags added: iso-testing

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

Title:
  indicator-sound-service crashed with g_error("Unable to get session
  bus")

Status in indicator-sound package in Ubuntu:
  Fix Released

Bug description:
  none

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: indicator-sound 12.10.2+15.04.20150227.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Mar  3 12:31:56 2015
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
  InstallationDate: Installed on 2014-10-24 (130 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=es_UY:es
   XDG_RUNTIME_DIR=
   LANG=es_UY.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: indicator-sound
  StacktraceTop: main ()
  Title: indicator-sound-service crashed with signal 5 in main()
  UpgradeStatus: Upgraded to vivid on 2015-01-05 (56 days ago)
  UserGroups:

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

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

[Touch-packages] [Bug 1390562] Re: Moving the mouse out from the decoration hides the LIMs when Alt is pressed

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

** Changed in: unity (Ubuntu Trusty)
   Importance: Undecided => Low

** Changed in: unity (Ubuntu Trusty)
 Assignee: (unassigned) => Stephen M. Webb (bregma)

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

Title:
  Moving the mouse out from the decoration hides the LIMs when Alt is
  pressed

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

Bug description:
  Prerequisite: from Appearance -> Behavior -> Set menu visible in
  window titlebar

  1. Open a window with menus
  2. Press and keep pressed the Alt key
  3. Menus will show
  4. Move the mouse over the window decoration
  5. Move the mouse out from the window decoration

  Actual behavior:
  6. Menus hides, also if the Alt key is pressed.

  Expected:
  6. Menus should stay visible until the Alt key is released.

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

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

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

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

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

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1433811/+attachment/4349324/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1433811/+attachment/4349326/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1433811/+attachment/4349327/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1433811/+attachment/4349328/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1433811/+attachment/4349329/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1433811/+attachment/4349330/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1433811/+attachment/4349331/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1428950

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

Status in tracker package in Ubuntu:
  New

Bug description:
  I rebooted

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: tracker-extract 1.2.5-0ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Wed Mar 18 18:20:44 2015
  ExecutablePath: /usr/lib/tracker/tracker-extract
  InstallationDate: Installed on 2015-02-28 (18 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Alpha amd64 (20150227)
  ProcCmdline: /usr/lib/tracker/tracker-extract
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  Signal: 6
  SourcePackage: tracker
  StacktraceTop:
   g_malloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_strdup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstlibav.so
   av_log () from /usr/lib/x86_64-linux-gnu/libavutil.so.54
   ?? () from /usr/lib/x86_64-linux-gnu/libavcodec.so.56
  Title: tracker-extract crashed with SIGABRT in g_malloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1312137] Re: Local menus broken for Qt apps after opening dialog

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

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

** Changed in: unity (Ubuntu Trusty)
 Assignee: (unassigned) => Stephen M. Webb (bregma)

** Description changed:

+ [Impact]
+ 
  I have selected to have window menus in the window's title bar. This
  works great, except for Qt apps. After selecting a menu item in a Qt app
- that produces a dialog, the menu is no longer accessible. e.g.
+ that produces a dialog, the menu is no longer accessible.  The only way
+ to get the menu back, is to switch to another window, and then back to
+ the affected app.
+ 
+ [Test Case]
  
  1. Start qtcreator
  2. Resize window so that it is not maximised
  3. Select 'Help' -> 'About Qt Creator'
  4. Dismiss 'About Qt Creator' dialog
- 5. Move mouse over window titlebar -> menu is no longer shown.
+ 5. Move mouse over window titlebar.
  
- The only way to get the menu back, is to switch to another window, and
- then back to the affected app.
+ [Regression Potential]
  
- Note: This does not seem to affect the 'File' dialog from QtCreator -
- I'm assuming this is because it loads the Gtk file dialog.
+ It's possible other menu interaction bugs may have been introduced.
+ 
+ [Other Info]
+ 
+ The fix for Ubuntu 14.04 LTS was cherry-picked from the Ubuntu "Vivid
+ Vervet" dev release where it has been in production use for some time
+ without apparent regression.

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

Title:
  Local menus broken for Qt apps after opening dialog

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

Bug description:
  [Impact]

  I have selected to have window menus in the window's title bar. This
  works great, except for Qt apps. After selecting a menu item in a Qt
  app that produces a dialog, the menu is no longer accessible.  The
  only way to get the menu back, is to switch to another window, and
  then back to the affected app.

  [Test Case]

  1. Start qtcreator
  2. Resize window so that it is not maximised
  3. Select 'Help' -> 'About Qt Creator'
  4. Dismiss 'About Qt Creator' dialog
  5. Move mouse over window titlebar.

  [Regression Potential]

  It's possible other menu interaction bugs may have been introduced.

  [Other Info]

  The fix for Ubuntu 14.04 LTS was cherry-picked from the Ubuntu "Vivid
  Vervet" dev release where it has been in production use for some time
  without apparent regression.

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

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

[Touch-packages] [Bug 1302955] Re: upstart user session leaks all the dbus events it receives

** Description changed:

- Easiest way to see this:
+ [Impact]
+ 
+ The unity-panel-service process has been caching D-Bus messages sent
+ from upstart, effectively leaking memory.  The solution replaces the
+ offending code with a single upstart event emission.
+ 
+ [Test Case]
+ 
  0. Make sure there is a user session job with a dbus rule (eg 
unity-greeter-session-broadcast)
  1. Install and run system-load-indicator (indicator-multiload)
  2. Set the update interval to 100ms
  3. Now watch the memory use of init --user increase by 100kb per second
  4. Also open up upstart-monitor to see all the dbus messages being sent
  
+ [Regression Potential]
  
- ProblemType: Bug
- DistroRelease: Ubuntu 14.04
- Package: upstart 1.12.1-0ubuntu1
- ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
- Uname: Linux 3.13.0-22-generic x86_64
- ApportVersion: 2.14-0ubuntu1
- Architecture: amd64
- CurrentDesktop: Unity
- Date: Sat Apr  5 18:17:40 2014
- InstallationDate: Installed on 2013-06-22 (287 days ago)
- InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130621)
- SourcePackage: upstart
- UpgradeStatus: Upgraded to trusty on 2013-12-05 (120 days ago)
- UpstartBugCategory: Session
- UpstartRunningSessionCount: 1
- UpstartRunningSessionVersion: init (upstart 1.12.1)
- UpstartRunningSystemVersion: init (upstart 1.12.1)
+ Some kind of hidden functionality depending on upstart events sent
+ through D-Bus to the unity-panel-service may have become disconnected.
+ Unlikely.
+ 
+ [Other Info]
+ 
+ The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu "Vivid
+ Vervet" dev release where it has been in regular use for some time
+ without apparent regression.

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

Title:
  upstart user session leaks all the dbus events it receives

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

Bug description:
  [Impact]

  The unity-panel-service process has been caching D-Bus messages sent
  from upstart, effectively leaking memory.  The solution replaces the
  offending code with a single upstart event emission.

  [Test Case]

  0. Make sure there is a user session job with a dbus rule (eg 
unity-greeter-session-broadcast)
  1. Install and run system-load-indicator (indicator-multiload)
  2. Set the update interval to 100ms
  3. Now watch the memory use of init --user increase by 100kb per second
  4. Also open up upstart-monitor to see all the dbus messages being sent

  [Regression Potential]

  Some kind of hidden functionality depending on upstart events sent
  through D-Bus to the unity-panel-service may have become disconnected.
  Unlikely.

  [Other Info]

  The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu "Vivid
  Vervet" dev release where it has been in regular use for some time
  without apparent regression.

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

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

[Touch-packages] [Bug 1302955] Re: upstart user session leaks all the dbus events it receives

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

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

** Changed in: unity (Ubuntu Trusty)
 Assignee: (unassigned) => Stephen M. Webb (bregma)

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

Title:
  upstart user session leaks all the dbus events it receives

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

Bug description:
  Easiest way to see this:
  0. Make sure there is a user session job with a dbus rule (eg 
unity-greeter-session-broadcast)
  1. Install and run system-load-indicator (indicator-multiload)
  2. Set the update interval to 100ms
  3. Now watch the memory use of init --user increase by 100kb per second
  4. Also open up upstart-monitor to see all the dbus messages being sent

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: upstart 1.12.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
  Uname: Linux 3.13.0-22-generic x86_64
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr  5 18:17:40 2014
  InstallationDate: Installed on 2013-06-22 (287 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130621)
  SourcePackage: upstart
  UpgradeStatus: Upgraded to trusty on 2013-12-05 (120 days ago)
  UpstartBugCategory: Session
  UpstartRunningSessionCount: 1
  UpstartRunningSessionVersion: init (upstart 1.12.1)
  UpstartRunningSystemVersion: init (upstart 1.12.1)

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

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

[Touch-packages] [Bug 601555] Re: Error: Directory NikonPreview, entry 0xb3b2 has invalid size 3115890614*1; skipping entry.

2015-03-18 Thread Tomas Pospisek

@ariel: I *think* it'd more effective to report the problem upstream @
http://www.gimp.org/bugs/ together with a photo image that can
demonstrate the problem.

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

Title:
  Error: Directory NikonPreview, entry 0xb3b2 has invalid size
  3115890614*1; skipping entry.

Status in The GNU Image Manipulation Program (GIMP):
  Unknown
Status in exiv2 package in Ubuntu:
  Fix Released
Status in exiv2 package in Debian:
  Fix Released

Bug description:
  Binary package hint: exiv2

  When I start digikam from the command line, it bombs it with
  (thousands?) of messages like:

  [...]
  Warning: Directory NikonPreview, entry 0xb3b2 has unknown Exif (TIFF) type 
46516; setting type size 1.
  Error: Directory NikonPreview, entry 0xb3b2 has invalid size 3115890614*1; 
skipping entry.
  [...]
  Error: Offset of directory NikonPreview, entry 0x00c4 is out of bounds: 
Offset = 0x01010101; truncating the entry
  Warning: Directory NikonPreview, entry 0x0504 has unknown Exif (TIFF) type 
1798; setting type size 1.
  [...]

  According to http://mail.kde.org/pipermail/digikam-
  users/2009-July/007947.html

  It's a problem of libexiv2
  *t

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: libexiv2-6 0.19-1
  ProcVersionSignature: Ubuntu 2.6.31-21.59-generic
  Uname: Linux 2.6.31-21-generic x86_64
  Architecture: amd64
  Date: Sun Jul  4 11:08:10 2010
  ProcEnviron:
   LANGUAGE=de_CH:de
   PATH=(custom, user)
   LANG=de_CH.utf8
   SHELL=/bin/bash
  SourcePackage: exiv2

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

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

[Touch-packages] [Bug 1298021] Re: Google Chrome (not chromium) won't start in guest session

2015-03-18 Thread Jamie Strandboge

Eric, this bug is closed and was fixed for the original bug. Can you
file a new bug using 'ubuntu-bug apparmor' after you see the issue?
Thanks.

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

Title:
  Google Chrome (not chromium) won't start in guest session

Status in lightdm package in Ubuntu:
  Fix Released

Bug description:
  Related, but not a dupe of bug 577919
  Install Google Chrome (not chromium) and switch to a guest session
  Start chrome from a terminal
  See the following error:-

  "Failed to move to new PID namespace: Operation not permitted"

  I see these apparmor denials:-

  [Tue Mar 25 12:51:46 2014] type=1400 audit(1395861131.882:541): 
apparmor="DENIED" operation="capable" 
profile="/usr/lib/lightdm/lightdm-guest-session" pid=30034 
comm="chrome-sandbox" capability=21  capname="sys_admin"
  [Tue Mar 25 12:52:13 2014] type=1400 audit(1395861159.510:542): 
apparmor="DENIED" operation="open" 
profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/30062/oom_score_adj" pid=30062 comm="chrome" requested_mask="wc" 
denied_mask="wc" fsuid=130 ouid=130

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.9.13-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
  Uname: Linux 3.13.0-19-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar 26 19:08:04 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-06-29 (634 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to trusty on 2014-01-20 (65 days ago)

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

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

[Touch-packages] [Bug 1374942] Re: compiz crashed with signal 5 in _XReply() from unity::decoration::ForceQuitDialog::ForceQuitDialog

Attaching the test script to use to reproduce the problem or test the
solution.

** Description changed:

- Unkown cause.
+ [Impact]

- ProblemType: Crash
- DistroRelease: Ubuntu 14.10
- Package: unity 7.3.1+14.10.20140915-0ubuntu1
- 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: Sun Sep 28 16:19:49 2014
- ExecutablePath: /usr/bin/compiz
- InstallationDate: Installed on 2014-09-03 (25 days ago)
- InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140902)
- ProcCmdline: compiz
- ProcEnviron:
- PATH=(custom, no user)
- LANGUAGE=en_AU:en
- XDG_RUNTIME_DIR=
- LANG=en_AU.UTF-8
- SHELL=/bin/bash
- Signal: 5
- SourcePackage: unity
- StacktraceTop:
- ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
- _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
- XGetWindowProperty () from /usr/lib/x86_64-linux-gnu/libX11.so.6
- XGetClassHint () from /usr/lib/x86_64-linux-gnu/libX11.so.6
- ?? () from /usr/lib/compiz/libunityshell.so
- Title: compiz crashed with signal 5 in _XReply()
- UpgradeStatus: No upgrade log present (probably fresh install)
- UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ An invalid line of code would occasionally cause Unity to crash.
+
+ [Test Case]
+
+ (1) Download and run the attached Python script test-1374942 to create a
candidate application.
+ (2) Press the close button and wait for the Force Quit dialog to come up.
+ (3) Choose the "Force Quit" button.
+
+ The desktop shell should not crash.
+
+ [Regression Potential]
+
+ The fix for this bug involves converting an integer into a string and
+ appending it to an error message instead of adding the integer value to
+ the address of the error message. There is unlikely to be a regression
+ from this.
+
+ [Other Info]
+
+ The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu "Vivid
+ Vervet" dev release where it has been under daily use for some time
+ without apparent regressioon.

** Attachment added: "Test script "test-1374942""

https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1374942/+attachment/4349322/+files/test-1374942

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

Title:
compiz crashed with signal 5 in _XReply() from
unity::decoration::ForceQuitDialog::ForceQuitDialog

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

Bug description:
[Impact]

An invalid line of code would occasionally cause Unity to crash.

[Test Case]

(1) Download and run the attached Python script test-1374942 to create a
candidate application.
(2) Press the close button and wait for the Force Quit dialog to come up.
(3) Choose the "Force Quit" button.

The desktop shell should not crash.

[Regression Potential]

The fix for this bug involves converting an integer into a string and
appending it to an error message instead of adding the integer value
to the address of the error message. There is unlikely to be a
regression from this.

[Other Info]

The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu "Vivid
Vervet" dev release where it has been under daily use for some time
without apparent regressioon.

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

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

[Touch-packages] [Bug 1419294] Re: Apparmor chromium profile denies loading policies

2015-03-18 Thread Jamie Strandboge

** Changed in: apparmor (Ubuntu)
 Assignee: (unassigned) => Steve Beattie (sbeattie)

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

Title:
  Apparmor chromium profile denies loading policies

Status in apparmor package in Ubuntu:
  Triaged

Bug description:
  Profiles in /etc/chromium-browser/policies/managed or /etc/chromium-
  browser/policies/recommended are ignored when using the apparmor
  profile.

  Syslog excerpt:

  Feb  7 17:10:11 ubuntu kernel: [23893.781721] audit: type=1400
  audit(1423325411.004:109): apparmor="DENIED" operation="open"
  profile="/usr/lib/chromium-browser/chromium-browser" name="/etc
  /chromium-browser/policies/managed/policy.json" pid=16928
  comm="Chrome_FileThre" requested_mask="r" denied_mask="r" fsuid=1000
  ouid=0

  How to test:

  Create a file policy.json in /etc/chromium-browser/policies/managed
  containing:

  {
"RestoreOnStartup": 1
  }

  start the browser and type in "about:policy". Normally you should see
  the policy being listed there, which is currently not the case because
  apparmor denies the reading the policy file.

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

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

[Touch-packages] [Bug 1432882] Re: libclang1 has wrong standard include paths

2015-03-18 Thread Corentin SCHREIBER

(sorry, I meant of course "trusty", not "lucid", in the above post)

I confirm that the libclang from the above PPA (1:3.4.2-debian13trusty1)
does work correctly in trusty. In other words, when I compile the
example programs attached to this bug report with the libclang from this
PPA, the errors about ia32intrin.h are gone and parsing is fully
functional. I don't know if this is due to 1) a more recent upstream
libclang version (3.4.2 vs 3.4), 2) a more recent debian base, or 3)
tweaks specific to this PPA.

If someone familiar with the debian/ubuntu build system could take a look at 
the source of this PPA:
https://github.com/hATrayflood/llvm-ppa

... and compare to what is done for the official ubuntu packages, that would be 
great. I have tried myself, but the thing is so complex and globally unknown to 
me that I am completely lost. From what I could gather, it seems that the 
maintainer of the PPA actually has made a few modifications to the original 
debian packages, as can be seen from this diff file:
https://github.com/hATrayflood/llvm-ppa/blob/master/trusty/llvm-toolchain-3.4/debian.diff

Also, can someone else actually reproduce this issue on their side?

NB: Using the PPA libclang, the builtin search directories are similar to the 
original ubuntu version. So that lead was a dead end. Here is the output of 
-print-search-dirs:
programs: =:/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../x86_64-linux-gnu/bin
libraries: 
=../lib/clang/3.4.2:/usr/lib/gcc/x86_64-linux-gnu/4.8:/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu:/lib/x86_64-linux-gnu:/lib/../lib64:/usr/lib/x86_64-linux-gnu:/usr/lib/gcc/x86_64-linux-gnu/4.8/../../..:/lib:/usr/lib

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

Title:
  libclang1 has wrong standard include paths

Status in llvm-toolchain-3.4 package in Ubuntu:
  New

Bug description:
  Bug affects all versions of libclang1 I could test (3.3, 3.4 and 3.5).
  The precise version of libclang I have is 1:3.4-1ubuntu3.
  Running Ubuntu 14.04 (Linux Mint 17.1).

  When building a minimal libclang program (refgen.cpp, attached) and using the 
"-print-search-dirs" command line argument to output the standard header search 
directories, libclang outputs the following:
  programs: =:/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../x86_64-linux-gnu/bin
  libraries: 
=../lib/clang/3.4:/usr/lib/gcc/x86_64-linux-gnu/4.8:/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu:/lib/x86_64-linux-gnu:/lib/../lib64:/usr/lib/x86_64-linux-gnu:/usr/lib/gcc/x86_64-linux-gnu/4.8/../../..:/lib:/usr/lib

  Notice the leading "../lib/clang/3.4" in "libraries", which does not
  make any sense and is likely missing part of the path. Notice also the
  leading ":" in "programs", which probably doesn't hurt, but looks
  suspicious.

  For reference, running clang (3.4) with the same command line argument 
outputs:
  programs: 
=/usr/bin:/usr/bin/../lib/gcc/x86_64-linux-gnu/4.8/../../../../x86_64-linux-gnu/bin
  libraries: 
=/usr/bin/../lib/clang/3.4:/usr/bin/../lib/gcc/x86_64-linux-gnu/4.8:/usr/bin/../lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu:/lib/x86_64-linux-gnu:/lib/../lib64:/usr/lib/x86_64-linux-gnu:/usr/bin/../lib/gcc/x86_64-linux-gnu/4.8/../../..:/lib:/usr/lib

  One can see here that the leading "/usr/bin/" has probably been
  stripped somehow from the "programs" and "libraries" search paths in
  libclang1.

  The end result is that libclang1 does not find clang's standard headers, and 
falls back to using GCC's, which it does not support.
  In my case, this means that if I try to parse even the simplest of files 
(test.cpp, attached) with this libclang1 and C++11 support enabled, the parsing 
fails because libclang1 is failing to understand GCC's SSE intrinsics in 
/usr/lib/gcc/x86_64-linux-gnu/4.8/include/ia32intrin.h, generating lots of 
errors:
  /usr/lib/gcc/x86_64-linux-gnu/4.8/include/ia32intrin.h:41:10: error: use of 
undeclared identifier '__builtin_ia32_bsrsi'
  /usr/lib/gcc/x86_64-linux-gnu/4.8/include/ia32intrin.h:89:10: error: use of 
undeclared identifier '__builtin_ia32_rdpmc'
  /usr/lib/gcc/x86_64-linux-gnu/4.8/include/ia32intrin.h:97:10: error: use of 
undeclared identifier '__builtin_ia32_rdtsc'
  /usr/lib/gcc/x86_64-linux-gnu/4.8/include/ia32intrin.h:105:10: error: use of 
undeclared identifier '__builtin_ia32_rdtscp'
  /usr/lib/gcc/x86_64-linux-gnu/4.8/include/ia32intrin.h:113:10: error: use of 
undeclared identifier '__builtin_ia32_rolqi'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.4/+bug/1432882/+subscriptions

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

[Touch-packages] [Bug 1433806] [NEW] Sync exiv2 0.24-4.1 (main) from Debian unstable (main)

2015-03-18 Thread Artur Rona

Public bug reported:

Please sync exiv2 0.24-4.1 (main) from Debian unstable (main)

Explanation of the Ubuntu delta and why it can be dropped:
  * SECURITY UPDATE: denial of service via buffer overflow
- debian/patches/CVE-2014-9449.patch: fix overflow in
  src/riffvideo.cpp.
- CVE-2014-9449

CVE-2014-9449 is already fixed in Debian.

Changelog entries since current vivid version 0.24-4ubuntu1:

exiv2 (0.24-4.1) unstable; urgency=medium

  * Non-maintainer upload.
  * Add CVE-2014-9449.patch patch.
CVE-2014-9449: buffer overflow in RiffVideo::infoTagsHandler
Thanks to Klaus Ethgen  (Closes: #773846)

 -- Salvatore Bonaccorso   Wed, 07 Jan 2015 20:25:48
+0100

** Affects: exiv2 (Ubuntu)
 Importance: Wishlist
 Status: New

** Changed in: exiv2 (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Sync exiv2 0.24-4.1 (main) from Debian unstable (main)

Status in exiv2 package in Ubuntu:
  New

Bug description:
  Please sync exiv2 0.24-4.1 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* SECURITY UPDATE: denial of service via buffer overflow
  - debian/patches/CVE-2014-9449.patch: fix overflow in
src/riffvideo.cpp.
  - CVE-2014-9449

  CVE-2014-9449 is already fixed in Debian.

  Changelog entries since current vivid version 0.24-4ubuntu1:

  exiv2 (0.24-4.1) unstable; urgency=medium

* Non-maintainer upload.
* Add CVE-2014-9449.patch patch.
  CVE-2014-9449: buffer overflow in RiffVideo::infoTagsHandler
  Thanks to Klaus Ethgen  (Closes: #773846)

   -- Salvatore Bonaccorso   Wed, 07 Jan 2015
  20:25:48 +0100

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

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

[Touch-packages] [Bug 1417650] Re: Pointer motion and crossing events are missing

This bug was fixed in the package qtmir - 0.4.4+15.04.20150318-0ubuntu1

---
qtmir (0.4.4+15.04.20150318-0ubuntu1) vivid; urgency=medium

  [ Daniel d'Andrada ]
  * Port to the new MirEvent API and add support for pointer events.
(LP: #1417650, #1392716)

  [ Gerry Boland ]
  * Refactor wakelock handling. Lifecycle exempt apps now release
wakelock when shell tries to suspend them (LP: #1423787)

  [ Robert Carr ]
  * Port to the new MirEvent API and add support for pointer events.
(LP: #1417650, #1392716)
 -- CI Train BotWed, 18 Mar 2015 10:12:22 +

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

Title:
  Pointer motion and crossing events are missing

Status in Mir:
  Fix Released
Status in Qt integration with the Mir display server:
  In Progress
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Unity 8 doesn't seem to emit events for when the pointer enters or
  leaves a window, or when the pointer moves around inside a window. It
  does seem to emit the needed motion events when the mouse is dragged
  though.

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

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

[Touch-packages] [Bug 1427708] Re: indicator-sound-service crashed with g_error("Unable to get session bus")

** Summary changed:

- indicator-sound-service crashed with g_error("Unable to get session bus: No 
se puede conectar: Conexi\303\263n rehusada")
+ indicator-sound-service crashed with g_error("Unable to get session bus")

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

Title:
  indicator-sound-service crashed with g_error("Unable to get session
  bus")

Status in indicator-sound package in Ubuntu:
  Fix Released

Bug description:
  none

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: indicator-sound 12.10.2+15.04.20150227.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Mar  3 12:31:56 2015
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
  InstallationDate: Installed on 2014-10-24 (130 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=es_UY:es
   XDG_RUNTIME_DIR=
   LANG=es_UY.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: indicator-sound
  StacktraceTop: main ()
  Title: indicator-sound-service crashed with signal 5 in main()
  UpgradeStatus: Upgraded to vivid on 2015-01-05 (56 days ago)
  UserGroups:

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

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

[Touch-packages] [Bug 1429664] Re: indicator-sound-service crashed with signal 5 in main()

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

** This bug has been marked a duplicate of bug 1427708
   indicator-sound-service crashed with g_error("Unable to get session bus: No 
se puede conectar: Conexi\303\263n rehusada")

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

Title:
  indicator-sound-service crashed with signal 5 in main()

Status in indicator-sound package in Ubuntu:
  New

Bug description:
  i just upgrade ubuntu 14.10 to 15.04 and shows me a notificacion that
  saids system has dected a problem all the time

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: indicator-sound 12.10.2+15.04.20150227.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  Date: Tue Mar  3 21:59:54 2015
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
  InstallationDate: Installed on 2015-01-27 (40 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=es_PR:es
   XDG_RUNTIME_DIR=
   LANG=es_PR.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: indicator-sound
  StacktraceTop: main ()
  Title: indicator-sound-service crashed with signal 5 in main()
  UpgradeStatus: Upgraded to vivid on 2015-03-03 (4 days ago)
  UserGroups:

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

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

[Touch-packages] [Bug 1433797] Re: qmlplugindump crashed with SIGABRT in oxide::qt::WebViewAdapter::context()

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

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

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1433797/+attachment/4349301/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1433797/+attachment/4349303/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1433797/+attachment/4349304/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1433797/+attachment/4349305/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1433797/+attachment/4349306/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1433797/+attachment/4349307/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1433797/+attachment/4349308/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1419616
   qmlplugindump crashed with SIGABRT in oxide::WebView::GetBrowserContext()

** Tags removed: need-amd64-retrace

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

Title:
  qmlplugindump crashed with SIGABRT in
  oxide::qt::WebViewAdapter::context()

Status in qtdeclarative-opensource-src package in Ubuntu:
  New

Bug description:
  I was building and running a simple qml app in Ubuntu-SDK when
  confronted by the crash dialog. I didn't notice any problem myself.
  The messages in the "General Messages" pane of qt creator were:

  [21:12:22] ii click-reviewers-tools 0.24-0~407~ubuntu15.04.1

  Warnings while parsing QML type information of 
/usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components:
  Failed to parse 
'/usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/plugins.qmltypes'.
  Error: 
/usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/plugins.qmltypes:1001:19: 
Expected string literal to contain 'Package/Name major.minor' or 'Name 
major.minor'.
  /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/plugins.qmltypes:1002:36: 
Expected array literal with only number literal members.
  /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/plugins.qmltypes:1020:19: 
Expected string literal to contain 'Package/Name major.minor' or 'Name 
major.minor'.
  /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/plugins.qmltypes:1021:36: 
Expected array literal with only number literal members.
  /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/plugins.qmltypes:1030:19: 
Expected string literal to contain 'Package/Name major.minor' or 'Name 
major.minor'.
  /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/plugins.qmltypes:1031:36: 
Expected array literal with only number literal members.
  /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/plugins.qmltypes:1039:19: 
Expected string literal to contain 'Package/Name major.minor' or 'Name 
major.minor'.
  /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/plugins.qmltypes:1040:36: 
Expected array literal with only number literal members.
  /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/plugins.qmltypes:1057:19: 
Expected string literal to contain 'Package/Name major.minor' or 'Name 
major.minor'.
  /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/plugins.qmltypes:1058:36: 
Expected array literal with only number literal members.

  Warnings while parsing QML type information of 
/usr/lib/x86_64-linux-gnu/qt5/qml/QtMultimedia:
  Failed to parse 
'/usr/lib/x86_64-linux-gnu/qt5/qml/QtMultimedia/plugins.qmltypes'.
  Error: /usr/lib/x86_64-linux-gnu/qt5/qml/QtMultimedia/plugins.qmltypes:0:0: 
Expected a single import.

  Warnings while parsing QML type information of 
/usr/lib/x86_64-linux-gnu/unity8/qml/Dash:
  Failed to parse '/usr/lib/x86_64-linux-gnu/unity8/qml/Dash/Dash.qmltypes'.
  Error: /usr/lib/x86_64-linux-gnu/unity8/qml/Dash/Dash.qmltypes:102:19: 
Expected string literal to contain 'Package/Name major.minor' or 'Name 
major.minor'.
  /usr/lib/x86_64-linux-gnu/unity8/qml/Dash/Dash.qmltypes:103:36: Expected 
array literal with only number literal members.

  QML module does not contain information about components contained in
  plugins.

  Module path: /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Settings/Menus
  See "Using QML Modules with Plugins" in the documentation.

  Automatic type

[Touch-packages] [Bug 1433797] [NEW] qmlplugindump crashed with SIGABRT in oxide::qt::WebViewAdapter::context()

2015-03-18 Thread Neil McPhail

Public bug reported:

I was building and running a simple qml app in Ubuntu-SDK when
confronted by the crash dialog. I didn't notice any problem myself. The
messages in the "General Messages" pane of qt creator were:

[21:12:22] ii click-reviewers-tools 0.24-0~407~ubuntu15.04.1

Warnings while parsing QML type information of 
/usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components:
Failed to parse 
'/usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/plugins.qmltypes'.
Error: 
/usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/plugins.qmltypes:1001:19: 
Expected string literal to contain 'Package/Name major.minor' or 'Name 
major.minor'.
/usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/plugins.qmltypes:1002:36: 
Expected array literal with only number literal members.
/usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/plugins.qmltypes:1020:19: 
Expected string literal to contain 'Package/Name major.minor' or 'Name 
major.minor'.
/usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/plugins.qmltypes:1021:36: 
Expected array literal with only number literal members.
/usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/plugins.qmltypes:1030:19: 
Expected string literal to contain 'Package/Name major.minor' or 'Name 
major.minor'.
/usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/plugins.qmltypes:1031:36: 
Expected array literal with only number literal members.
/usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/plugins.qmltypes:1039:19: 
Expected string literal to contain 'Package/Name major.minor' or 'Name 
major.minor'.
/usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/plugins.qmltypes:1040:36: 
Expected array literal with only number literal members.
/usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/plugins.qmltypes:1057:19: 
Expected string literal to contain 'Package/Name major.minor' or 'Name 
major.minor'.
/usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/plugins.qmltypes:1058:36: 
Expected array literal with only number literal members.

Warnings while parsing QML type information of 
/usr/lib/x86_64-linux-gnu/qt5/qml/QtMultimedia:
Failed to parse 
'/usr/lib/x86_64-linux-gnu/qt5/qml/QtMultimedia/plugins.qmltypes'.
Error: /usr/lib/x86_64-linux-gnu/qt5/qml/QtMultimedia/plugins.qmltypes:0:0: 
Expected a single import.

Warnings while parsing QML type information of 
/usr/lib/x86_64-linux-gnu/unity8/qml/Dash:
Failed to parse '/usr/lib/x86_64-linux-gnu/unity8/qml/Dash/Dash.qmltypes'.
Error: /usr/lib/x86_64-linux-gnu/unity8/qml/Dash/Dash.qmltypes:102:19: Expected 
string literal to contain 'Package/Name major.minor' or 'Name major.minor'.
/usr/lib/x86_64-linux-gnu/unity8/qml/Dash/Dash.qmltypes:103:36: Expected array 
literal with only number literal members.

QML module does not contain information about components contained in
plugins.

Module path: /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Settings/Menus
See "Using QML Modules with Plugins" in the documentation.

Automatic type dump of QML module failed.
Errors:
"/usr/lib/x86_64-linux-gnu/qt5/bin/qmlplugindump" returned exit code 3.
Arguments: --path /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Settings/Menus
QQmlComponent: Component is not ready


QML module does not contain information about components contained in plugins.

Module path: /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Content
See "Using QML Modules with Plugins" in the documentation.

Automatic type dump of QML module failed.
Errors:
"/usr/lib/x86_64-linux-gnu/qt5/bin/qmlplugindump" returned exit code 3.
Arguments: --path /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Content
QQmlComponent: Component is not ready


QML module does not contain information about components contained in plugins.

Module path: /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Web
See "Using QML Modules with Plugins" in the documentation.

Automatic type dump of QML module failed.
Errors:
"/usr/lib/x86_64-linux-gnu/qt5/bin/qmlplugindump" returned exit code 3.
Arguments: --path /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Web
QQmlComponent: Component is not ready


QML module does not contain information about components contained in plugins.

Module path: /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/Extras/Browser
See "Using QML Modules with Plugins" in the documentation.

Automatic type dump of QML module failed.
Errors:
"/usr/lib/x86_64-linux-gnu/qt5/bin/qmlplugindump" returned exit code 3.
Arguments: --path 
/usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/Extras/Browser
QQmlComponent: Component is not ready


QML module does not contain information about components contained in plugins.

Module path: /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Telephony/PhoneNumber
See "Using QML Modules with Plugins" in the documentation.

Automatic type dump of QML module failed.
Errors:
"/usr/lib/x86_64-linux-gnu/qt5/bin/qmlplugindump" returned exit code 3.
Arguments: --path /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Telephony/PhoneNumber
QQmlComponent: Component is not ready


QML module does not contain information about components co

[Touch-packages] [Bug 1374942] Re: compiz crashed with signal 5 in _XReply() from unity::decoration::ForceQuitDialog::ForceQuitDialog

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

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

** Changed in: unity (Ubuntu Trusty)
 Assignee: (unassigned) => Stephen M. Webb (bregma)

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

Title:
  compiz crashed with signal 5 in _XReply() from
  unity::decoration::ForceQuitDialog::ForceQuitDialog

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

Bug description:
  Unkown cause.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: unity 7.3.1+14.10.20140915-0ubuntu1
  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: Sun Sep 28 16:19:49 2014
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2014-09-03 (25 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140902)
  ProcCmdline: compiz
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=en_AU:en
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: unity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XGetWindowProperty () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XGetClassHint () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/compiz/libunityshell.so
  Title: compiz crashed with signal 5 in _XReply()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1066157] Re: dash +orca does not speak the names of application icons

** Description changed:

- using orca and navigating around the dash with the keyboard I hear the
- names of videos, shopping results, files and folders, application
- suggestions from the software centre, but not the very most important
- thing in the dash - applications installed that I might want to run.
+ [Impact]
+ Screen reader support for dynamic content in the Dash is enabled.
+ 
+ [Test Case]
+ 
+ (1) Enable Screen Reader (System Settings > Universal Access > Screen Reader)
+ (2) Press Super + A to bring up the Applications lens of the Dash
+ (3) Navigate displayed content
+ (4) Choose an application for preview
+ (5) Press Esc until the Dash is closed, repeat steps 2 to 4
+ 
+ You should hear the application description and preview description.
+ 
+ [Regression Potential]
+ 
+ Some new code deals with processing pointers:  the usual problem
+ potential of dealing with pointers in C code applies.
+ 
+ [Other Info]
+ 
+ This patch for Ubuntu 14.04 LTS was cherry picked from the Ubuntu "Vivid
+ Vervet" dev release where it has been in public use for some time
+ without apparent regression.

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

Title:
  dash +orca does not speak the names of application icons

Status in OEM Priority Project:
  New
Status in Unity:
  Fix Committed
Status in Unity 5.0 series:
  New
Status in Unity 6.0 series:
  Won't Fix
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  In Progress

Bug description:
  [Impact]
  Screen reader support for dynamic content in the Dash is enabled.

  [Test Case]

  (1) Enable Screen Reader (System Settings > Universal Access > Screen Reader)
  (2) Press Super + A to bring up the Applications lens of the Dash
  (3) Navigate displayed content
  (4) Choose an application for preview
  (5) Press Esc until the Dash is closed, repeat steps 2 to 4

  You should hear the application description and preview description.

  [Regression Potential]

  Some new code deals with processing pointers:  the usual problem
  potential of dealing with pointers in C code applies.

  [Other Info]

  This patch for Ubuntu 14.04 LTS was cherry picked from the Ubuntu
  "Vivid Vervet" dev release where it has been in public use for some
  time without apparent regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1066157/+subscriptions

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

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

** Changed in: indicator-datetime (Ubuntu)
   Importance: Undecided => Medium

** Changed in: indicator-datetime (Ubuntu)
   Status: New => Confirmed

** Changed in: indicator-datetime (Ubuntu)
 Assignee: (unassigned) => Charles Kerr (charlesk)

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

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

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

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

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

  ---

  Desired solution:

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

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

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

[Touch-packages] [Bug 1433787] [NEW] rsync corrupts systematically jpg files when copying from jmtpfs

2015-03-18 Thread David Andel

Public bug reported:

rsync corrupts systematically jpg files when copying from jmtpfs
I am filing the bug with rsync because neither cp nor scp show the problem. 
They copy the images just fine. Therefore I assume it is not a problem of 
jmtpfs.
When I want to view the jpg files after a copy with rsync I get the following 
error: "Error interpreting JPEG image file (Application transferred too few 
scanlines)".
Rsync runs through though and does not output any error nor warning.

root@kimera:~# lsb_release -rd
Description:Ubuntu 14.10
Release:14.10

root@kimera:~# apt-cache policy rsync
rsync:
  Installed: 3.1.1-2
  Candidate: 3.1.1-2
  Version table:
 *** 3.1.1-2 0
500 http://ch.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: rsync 3.1.1-2
ProcVersionSignature: Ubuntu 3.16.0-31.43-generic 3.16.7-ckt5
Uname: Linux 3.16.0-31-generic x86_64
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
CurrentDesktop: LXDE
Date: Wed Mar 18 21:47:32 2015
InstallationDate: Installed on 2015-01-14 (63 days ago)
InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
SourcePackage: rsync
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug utopic

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

Title:
  rsync corrupts systematically jpg files when copying from jmtpfs

Status in rsync package in Ubuntu:
  New

Bug description:
  rsync corrupts systematically jpg files when copying from jmtpfs
  I am filing the bug with rsync because neither cp nor scp show the problem. 
They copy the images just fine. Therefore I assume it is not a problem of 
jmtpfs.
  When I want to view the jpg files after a copy with rsync I get the following 
error: "Error interpreting JPEG image file (Application transferred too few 
scanlines)".
  Rsync runs through though and does not output any error nor warning.

  root@kimera:~# lsb_release -rd
  Description:  Ubuntu 14.10
  Release:  14.10

  root@kimera:~# apt-cache policy rsync
  rsync:
Installed: 3.1.1-2
Candidate: 3.1.1-2
Version table:
   *** 3.1.1-2 0
  500 http://ch.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: rsync 3.1.1-2
  ProcVersionSignature: Ubuntu 3.16.0-31.43-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Mar 18 21:47:32 2015
  InstallationDate: Installed on 2015-01-14 (63 days ago)
  InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1066157] Re: dash +orca does not speak the names of application icons

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

** Changed in: unity (Ubuntu Trusty)
 Assignee: (unassigned) => Stephen M. Webb (bregma)

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

Title:
  dash +orca does not speak the names of application icons

Status in OEM Priority Project:
  New
Status in Unity:
  Fix Committed
Status in Unity 5.0 series:
  New
Status in Unity 6.0 series:
  Won't Fix
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  In Progress

Bug description:
  [Impact]
  Screen reader support for dynamic content in the Dash is enabled.

  [Test Case]

  (1) Enable Screen Reader (System Settings > Universal Access > Screen Reader)
  (2) Press Super + A to bring up the Applications lens of the Dash
  (3) Navigate displayed content
  (4) Choose an application for preview
  (5) Press Esc until the Dash is closed, repeat steps 2 to 4

  You should hear the application description and preview description.

  [Regression Potential]

  Some new code deals with processing pointers:  the usual problem
  potential of dealing with pointers in C code applies.

  [Other Info]

  This patch for Ubuntu 14.04 LTS was cherry picked from the Ubuntu
  "Vivid Vervet" dev release where it has been in public use for some
  time without apparent regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1066157/+subscriptions

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

[Touch-packages] [Bug 1365557] Re: Multiple alarms set at the same time trigger the screen to nolonger blank

Marking as invalid in datetime, this was a refcount error for the force-
screen-on resource in unity-system-compositor

** Changed in: indicator-datetime
   Status: Confirmed => Invalid

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

Title:
  Multiple alarms set at the same time trigger the screen to nolonger
  blank

Status in The Date and Time Indicator:
  Invalid
Status in Unity System Compositor:
  Fix Released
Status in unity-system-compositor package in Ubuntu:
  Fix Released

Bug description:
  STEPS:
  1. Open the clock app
  2. Swipe up from the bottom
  3. Add at least two alarms for the same time
  4. Let the screen blank and wait for the alarms to go off
  5. Dismiss the alarms from the woken phone
  6. Wait for more than a minute

  EXPECTATION:
  I expect the screen to reblank after a minute

  ACTUAL:
  The phone remains awake.

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

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

[Touch-packages] [Bug 1433761] Re: apt-key and add-apt-repository don't honor Acquire::http::Proxy

2015-03-18 Thread Adam Stokes

** Tags added: cloud-installer

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

Title:
  apt-key and add-apt-repository don't honor Acquire::http::Proxy

Status in software-properties package in Ubuntu:
  New

Bug description:
  When setting the proxy server globally on the system for the APT
  package manager, add-apt-repository ignores the setting. This issue is
  present on all versions of Debian that I have tested.

  # cat /etc/apt/apt.conf.d/80proxy 
  Acquire::http::proxy "http://w.x.y.z:/";;

  # apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 5A9A06AEF9CB8DB0
  Executing: gpg --ignore-time-conflict --no-options --no-default-keyring 
--homedir /tmp/tmp.TIa517Kcw8 --no-auto-check-trustdb --trust-model always 
--keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyring 
/etc/apt/trusted.gpg.d/debian-archive-squeeze-automatic.gpg --keyring 
/etc/apt/trusted.gpg.d/debian-archive-squeeze-stable.gpg --keyring 
/etc/apt/trusted.gpg.d/debian-archive-wheezy-automatic.gpg --keyring 
/etc/apt/trusted.gpg.d/debian-archive-wheezy-stable.gpg --keyring 
/etc/apt/trusted.gpg.d/saltstack-salt.gpg --keyserver keyserver.ubuntu.com 
--recv-keys 5A9A06AEF9CB8DB0
  gpg: requesting key F9CB8DB0 from hkp server keyserver.ubuntu.com
  gpg: keyserver timed out
  gpg: keyserver receive failed: keyserver error

  This has serious repercussions. Unattended installs such as juju,
  maas, etc are all affected for anyone who is working behind a proxy.
  This is the case for most enterprise environments where such maas and
  juju setups will be tested out, and as such has great repercussions
  for Canonical as a viable supplier of OpenStack environments: if your
  product fails to install, you're not going to get the business.

  Considering that:

  * The setting to use already exists in /etc/apt/apt.conf and that all other 
tools use this correctly
  * The serious impact of this issue for downstream projects and Debian usage 
in the enterprise
  * The long time this issue has been standing and has affected people

  I suggest that this either

  1) be fixed, or
  2) the apt-key and add-apt-repository programs are renamed so that it is made 
clear they are not part of the APT suite of programs and therefor cannot be 
trusted to behave as if they were part of APT.

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

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

[Touch-packages] [Bug 1425155] Re: totem 3.14's OSD looks bad in Ambiance

2015-03-18 Thread Gunnar Hjalmarsson

Can't see any problem, neither from a docs nor a translation POV. UIFe
granted.

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

Title:
  totem 3.14's OSD looks bad in Ambiance

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  In our theme, totem's OSD (player controls) doesn't look very nice.
  It's not really styled.

  Fixing this involves only changes to css files, and in there only
  adding rules for the .osd style class (and sub widgets).

  Rationale for including this after UI freeze: it's really quite ugly
  and it's hard to discern the overlay widgets from the video as they
  are missing a background. Please see the attached screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: totem 3.14.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Feb 24 16:01:38 2015
  InstallationDate: Installed on 2012-10-07 (869 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  SourcePackage: totem
  UpgradeStatus: Upgraded to vivid on 2013-05-07 (658 days ago)

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

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

[Touch-packages] [Bug 1417650] Re: Pointer motion and crossing events are missing

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

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

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

Title:
  Pointer motion and crossing events are missing

Status in Mir:
  Fix Released
Status in Qt integration with the Mir display server:
  In Progress
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Unity 8 doesn't seem to emit events for when the pointer enters or
  leaves a window, or when the pointer moves around inside a window. It
  does seem to emit the needed motion events when the mouse is dragged
  though.

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

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

[Touch-packages] [Bug 1429163] Re: Autopilot tests are compatible with py2

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

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

Title:
  Autopilot tests are compatible with py2

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

Bug description:
  The autopilot suite of tests and helpers in the toolkit is compatible
  with py2.

  We should drop the py2 support to simplify the code and to avoid all
  the py2 requirements that get installed when we want to run any test.

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

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

[Touch-packages] [Bug 1376565] Re: GNOME apps with headerbars look out of place in Unity

2015-03-18 Thread Gunnar Hjalmarsson

This doesn't affect the desktop guide. Reasonable change from a
translation POV as well. UIFe granted.

** Changed in: ubuntu-themes (Ubuntu)
   Status: Incomplete => New

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

Title:
  GNOME apps with headerbars look out of place in Unity

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  On ubuntu 14.10 gnome-system-log has the new headerbars (look at the 
screenshot).
  It should look like all other ubuntu applications.

  Fixing this entails changing the style of header bars in css files and
  adding new icons which are used for the window buttons (close,
  minimize, maximize, restore). "window-close-symbolic" is also used on
  tab widgets in some applications, such as gnome-terminal and gedit.
  Those look slightly different with the change.

  Rationale for including this after UI freeze: more than anticipated
  GNOME applications in the archive got updated to use a header bar
  instead of a traditional title bar. We've patched default
  applications, but there's a lot of apps left (for example, gnome-
  system-logs, devhelp, gnome-font-viewer). Making them look a bit more
  consistent with other apps is desirable, as they look very much out of
  place now.

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

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

[Touch-packages] [Bug 1417967] Re: Tablet: Dash flashes if double tapping outside open indicators

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

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

Title:
  Tablet: Dash flashes if double tapping outside open indicators

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  How to reproduce:
   * Be on tablet
   * Be in Dash with no app open
   * Open indicators
   * Double press very fast outside the indicators (over the greyed-out area)
   * See how the dash flashes to black for a split second

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

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

[Touch-packages] [Bug 1425737] Re: Wizard can potentially wait forever on a buggy page

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

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

Title:
  Wizard can potentially wait forever on a buggy page

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  If a wizard page never reports that it's ready to answer the question
  "should I skip this page?", the wizard will wait forever until it gets
  the answer.  Meanwhile, the user is presented with an empty page.

  We experienced this in vivid with ofono bug 1419675.  libqofono
  wouldn't report that SIM2 was done initializing.  So we'd just keep
  waiting.

  To reduce the severity of future similar bugs, the wizard should have
  a sensible timeout.  So at least the user can continue.

  == Original bug ==

  After selecting a language, sometimes I'm left with a blank page.  I
  never see the next screen, which lets me pick my password.

  When this happened, I was running krillin, on vivid image 122.  I had
  a SIM in slot 2, but none in slot 1.  I've NOT been able to reproduce
  with a SIM in slot 1 instead of slot 2, which seems relevant.

  After reproducing many times, it will sometimes stop happening.  But
  after an image flash, it is rather reliable for a while.

  I've looked into this a bit on the wizard side.  It turns out that
  libqofono is never replying that the second SIM slot is "ready" which
  means it has finished initializing it.

  Now, the wizard probably should timeout waiting for that to be true.
  But libqofono should also provide that info.

  current build number: 122
  device name: krillin
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-02-25 21:42:40
  version version: 122
  version ubuntu: 20150225
  version device: 20150210-95b6a9f
  version custom: 20150225

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

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

[Touch-packages] [Bug 1410915] Re: com.ubuntu.touch.system rotation-lock can't be changed by the checkbox in indicators

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

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

Title:
  com.ubuntu.touch.system rotation-lock can't be changed by the checkbox
  in indicators

Status in the base for Ubuntu mobile products:
  Fix Released
Status in indicator-display package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  New

Bug description:
  When we turo on/off the checkbox for rotation lock in indicators. 
  The gsettings com.ubuntu.touch.system rotation-lock didn't change.

  How to reproduce: 
  1. open the Indicator Rotation page.
  2. click the checkbox to turn on/off the rotation lock.
  When doing 2. Use phablet-shell to go into the phone. And use "gsettings get 
com.ubuntu.touch.system rotation-lock". It always print out false.

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

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

[Touch-packages] [Bug 1341681] Re: Autopilot tests should stop using deprecated emulators module

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

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

Title:
  Autopilot tests should stop using deprecated emulators module

Status in Dialer app for Ubuntu Touch:
  In Progress
Status in Dropping Letters:
  New
Status in Music application for Ubuntu devices:
  Fix Released
Status in Notes App:
  New
Status in Ubuntu Reminders app:
  Fix Released
Status in Sudoku game for Ubuntu Touch:
  New
Status in Calculator application for Ubuntu devices:
  Fix Released
Status in Calendar application for Ubuntu devices:
  Fix Released
Status in Clock application for Ubuntu devices:
  Fix Released
Status in Document Viewer application for Ubuntu devices:
  New
Status in File Manager application for Ubuntu devices:
  Fix Released
Status in RSS Feed Reader application for Ubuntu devices:
  Incomplete
Status in Terminal application for Ubuntu devices:
  Fix Released
Status in Weather application for Ubuntu devices:
  Incomplete
Status in dialer-app package in Ubuntu:
  Fix Released
Status in reminders-app package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Autopilot tests should stop using deprecated emulators module. Instead
  the new custom_proxy_objects modules should be used and called
  directly.

  Please note until https://bugs.launchpad.net/ubuntu-ui-
  toolkit/+bug/1341679 is fixed, the deprecation warning will still
  appear.

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

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

[Touch-packages] [Bug 1425161] Re: [Wizard] SIM PIN page before language selection

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

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

Title:
  [Wizard] SIM PIN page before language selection

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Test case.
  - Flash the device with devel-proposed channel (Vivid).
  - Go to the wizard.

  Expected result.
  - Language selection is presented first.

  Actual result.
  - SIM PIN page is presented in English. Language selection should be first.

  current build number: 121
  device name: krillin
  channel: ubuntu-touch/devel-proposed

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

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

[Touch-packages] [Bug 1430233] Re: Launching/stopping an unpinned app has a 2s delay

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

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

Title:
  Launching/stopping an unpinned app has a 2s delay

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

Bug description:
  Steps:
  - start an app you have not pinned to launcher

  Expected:
  - splash screen shown immediately

  Current:
  - there's a 1-2s delay

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.02+15.04.20150302-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar 10 10:55:09 2015
  SourcePackage: unity8
  SystemImageInfo:
   current build number: 0
   device name: 
   channel: daily
   last update: Unknown
  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/1430233/+subscriptions

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

[Touch-packages] [Bug 1431497] Re: Add translator comments where applicable

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

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

Title:
  Add translator comments where applicable

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Could you add translator comments to the two following strings?
  Without context, translators can't know if they are verbs or nouns,
  resulting in possible translation errors.

  "Lock"
  qml/Components/Dialogs.qml:90 
  https://translations.launchpad.net/unity8/trunk/+pots/unity8/gd/10/+translate

  "Shutdown"
   qml/Components/Dialogs.qml:127 
  https://translations.launchpad.net/unity8/trunk/+pots/unity8/gd/16/+translate

  Thanks!

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

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

[Touch-packages] [Bug 1425087] Re: Launcher re-ordering became laggy

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

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

Title:
  Launcher re-ordering became laggy

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

Bug description:
  image 121 vivid-proposed on krillin

  1. try to re-order the launcher icon order

  What happens:
  the icon does not get reordered instantly, rather they hang on screen for a 
bit. 

  attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.02+15.04.20150216.1-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: armhf
  Date: Tue Feb 24 18:53:38 2015
  InstallationDate: Installed on 2015-02-24 (0 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150224-020204)
  SourcePackage: unity8
  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/1425087/+subscriptions

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

[Touch-packages] [Bug 1396817] Re: Device locked timer doesn't decrease if the screen is off

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

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

Title:
  Device locked timer doesn't decrease if the screen is off

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  I'm on RTM #9

  Way to reproduce:
  - Unplug phone from charger / PC
  - Insert 5 wrong PIN
  - The phone says the device is locked for 5 minutes
  - Turn off the screen
  - Go to drink a coffe
  - Return 5 minutes later
  - Turn on the screen

  What I expect:
  - I'm able to insert my pin and use my phone

  What happens:
  - The phone says the device is locked for 5 minutes

  After some tries, I'm pretty sure the timer goes down only if the
  screen is on

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

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

[Touch-packages] [Bug 1307559] Re: Window decorations not drawn on external monitor

2015-03-18 Thread Stefan Skotte

Actually I just installed the Numix Gtk theme - and now it works. Even
with 1.5 vs 1.0 pixel scaling between the monitors.

Appears to be a scaling issue with the images used for
close/maximize/minimize in the default ubuntu theme.

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

Title:
  Window decorations not drawn on external monitor

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

Bug description:
  Window decorations (close / minimize / maximize buttons) do not draw
  on the external monitor on a laptop with external display. Windows on
  the laptop display are not affected.

  UI scale on the built-in display is 1.25; it's 1.0 on the external
  display. I am not sure if this is relevant.

  To reproduce:
  1) Plug in an external monitor to a laptop; ensure that it is running in 
extended display mode
  2) Launch an application such as the terminal
  3) The terminal launches on the laptop's built-in display. Observe the window 
decorations draw as expected
  4) Drag the terminal window to the second display

  Expected results;
  The terminal window is drawn on the extended display

  Actual results:
  The terminal window is drawn on the extended display but the close, minimize, 
and maximize buttons are missing.

  The problem happens on windows from all applications I've tried
  (firefox, terminal, emacs, thunderbird)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140411-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Apr 14 10:56:46 2014
  DistUpgraded: 2014-02-12 13:40:42,704 DEBUG enabling apt cron job
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 14.03.01, 3.13.0-23-generic, x86_64: installed
   fwts-efi-runtime-dkms, 14.03.01, 3.13.0-24-generic, x86_64: installed
   virtualbox, 4.3.10, 3.13.0-23-generic, x86_64: installed
   virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:060a]
  InstallationDate: Installed on 2013-12-02 (132 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130203-13:50
  MachineType: Dell Inc. XPS13 9333
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=0b9db31c-747b-40ad-bbbd-13a9a29caece ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-02-12 (60 days ago)
  dmi.bios.date: 11/11/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.name: 0GFTRT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd11/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Apr 14 08:54:29 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4933 
   vendor CMN
  xserver.version: 2:1.15.0-1ubuntu7

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

-- 
Mailing list: https://launchpad.net/~

[Touch-packages] [Bug 1315434] Re: Mouse with no time remaining estimate showing in preference to battery being charged

2015-03-18 Thread asmoore82

I could not easily find this workaround from a google search so
documenting it here:

Typical "use with caution" notice, may cause a (small) rift in the
space-time continuum, etc.

Edit /lib/udev/rules.d/95-upower-csr.rules (with sudo), comment out
(with #) the last set of lines at the bottom so that it's left like
this:

# Unifying HID++ devices
#SUBSYSTEM!="hid", GOTO="up_unifying_end"
#ATTRS{idVendor}=="046d", ENV{UPOWER_VENDOR}="Logitech, Inc."
#ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c52b", 
DRIVER=="logitech-djdevice", ENV{UPOWER_BATTERY_TYPE}="unifying"
#ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c532", 
DRIVER=="logitech-djdevice", ENV{UPOWER_BATTERY_TYPE}="unifying"
#ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c52f", 
ENV{UPOWER_BATTERY_TYPE}="lg-wireless"
LABEL="up_unifying_end"

^Everything commented out but that last LABEL.

On the next reboot, UPower will completely ignore these Unifying
devices!

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

Title:
  Mouse with no time remaining estimate showing in preference to battery
  being charged

Status in indicator-power package in Ubuntu:
  In Progress

Bug description:
  When my laptop battery is in a charging state, but is not fully
  charged, I expect it to be displayed in preference to my mouse, which
  has no time remaining estimate.

  The spec here:

  https://wiki.ubuntu.com/Power

  says:

  "If anything is discharging, the menu title should represent the
  component (not battery, but component) that is estimated to lose power
  first. For example, if your notebook battery is estimated to discharge
  in 1 hour 47 minutes, and your wireless mouse battery is estimated to
  discharge in 27 minutes, the menu title should represent the mouse. "

  but there doesn't seem to be any guideline to what happens when a
  battery is being charged.

  I suggest the time remaining to charge a battery should be displayed
  in preference to the power level in a wireless mouse.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-power 12.10.6+14.04.20140411-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May  2 11:50:36 2014
  InstallationDate: Installed on 2013-11-26 (156 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: indicator-power
  UpgradeStatus: Upgraded to trusty on 2014-01-17 (104 days ago)

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

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

[Touch-packages] [Bug 1433557] Re: systemd-udev-settle.service failes, 3min boot delay

2015-03-18 Thread Seth Arnold

** Tags added: systemd-boot

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

Title:
  systemd-udev-settle.service failes, 3min boot delay

Status in dbus package in Ubuntu:
  New

Bug description:
  During boot, systemd-udev-settle.service failes causing a 3min boot
  delay.

  Journal report this:
  > root@alice:~# journalctl -u systemd-udev-settle
  > -- Logs begin at Wed 2015-03-18 12:38:16 CET, end at Wed 2015-03-18 
12:47:32 CET. --
  > Mar 18 12:38:16 alice systemd[1]: Starting udev Wait for Complete Device 
Initialization...
  > Mar 18 12:41:16 alice systemd[1]: systemd-udev-settle.service start 
operation timed out. Terminating.
  > Mar 18 12:41:16 alice systemd[1]: Failed to start udev Wait for Complete 
Device Initialization.
  > Mar 18 12:41:16 alice systemd[1]: Unit systemd-udev-settle.service entered 
failed state.
  > Mar 18 12:41:16 alice systemd[1]: systemd-udev-settle.service failed.
  > Mar 18 12:41:17 alice systemd[1]: Starting udev Wait for Complete Device 
Initialization...
  > Mar 18 12:41:18 alice systemd[1]: Started udev Wait for Complete Device 
Initialization.

  The dmesg output arround that time is:

  > [8.537560] Adding 16723964k swap on /dev/sda4.  Priority:-1 extents:1 
across:16723964k FS
  > [9.559871] input: ST LIS3LV02DL Accelerometer as 
/devices/platform/lis3lv02d/input/input23
  > [  189.205551] Bluetooth: Core ver 2.20
  > [  189.205565] NET: Registered protocol family 31

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: dbus 1.8.12-1ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Mar 18 12:51:08 2015
  SourcePackage: dbus
  UpgradeStatus: Upgraded to vivid on 2015-03-02 (15 days ago)

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

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

[Touch-packages] [Bug 1327692] Re: package libssl1.0.0 1.0.1f-1ubuntu2.2 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libssl1.0.0/changelog.Debian.gz', which is different from

2015-03-18 Thread Seth Arnold

How did you get to the situation of installing 14.10 OpenSSL packages by
hand over the 12.04 LTS packages? Why would you do this? Why would you
also do them piecemeal instead of upgrading all the replaced packages
simultaneously?

Thanks


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

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

Title:
  package libssl1.0.0 1.0.1f-1ubuntu2.2 failed to install/upgrade:
  trying to overwrite shared
  '/usr/share/doc/libssl1.0.0/changelog.Debian.gz', which is different
  from other instances of package libssl1.0.0:i386

Status in openssl package in Ubuntu:
  Incomplete

Bug description:
  Broken Packages Problem

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libssl1.0.0 1.0.1f-1ubuntu2.2
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: sep3_10 pax apwr3_1
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  Date: Sat Jun  7 17:26:33 2014
  DpkgTerminalLog:
   Preparing to unpack .../libssl1.0.0_1.0.1f-1ubuntu2.2_i386.deb ...
   Unpacking libssl1.0.0:i386 (1.0.1f-1ubuntu2.2) over (1.0.1f-1ubuntu2.1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libssl1.0.0_1.0.1f-1ubuntu2.2_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libssl1.0.0/changelog.Debian.gz', which is different from other 
instances of package libssl1.0.0:i386
  DuplicateSignature: package:libssl1.0.0:1.0.1f-1ubuntu2.2:trying to overwrite 
shared '/usr/share/doc/libssl1.0.0/changelog.Debian.gz', which is different 
from other instances of package libssl1.0.0:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libssl1.0.0/changelog.Debian.gz', which is different from other 
instances of package libssl1.0.0:i386
  InstallationDate: Installed on 2014-05-26 (12 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: openssl
  Title: package libssl1.0.0 1.0.1f-1ubuntu2.2 failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libssl1.0.0/changelog.Debian.gz', 
which is different from other instances of package libssl1.0.0:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1431698] Re: Test verification should be split

This bug was fixed in the package ubuntu-ui-toolkit -
1.2.1450+15.04.20150318-0ubuntu1

---
ubuntu-ui-toolkit (1.2.1450+15.04.20150318-0ubuntu1) vivid; urgency=medium

  [ Timo Jyrinki ]
  * Clean QML cache after updating package, before reboot. LP: #1431228

  [ Zoltán Balogh ]
  * Improved test plan script. Fixes LP: #1430201

  [ Christian Dywan ]
  * New text handler visuals and improved behavior.
Fixes LP: #1391335, LP: #1407723, LP: #1415548
  * Split off test verification and run it once only for 'make check'.
Fixes LP: #1431698
  * Tweak assert_discard_popover to work better with textfield in header.
Fixes LP: #1432611

  [ Tim Peeters ]
  * Make the filenames for header and navigation tests consistent and
split up the big tabbed header.qml into multiple smaller test files.
Fixes LP: #1429838

  [ Loïc Molinari ]
  * Optimized Slider and ProgressBar components. Switched to the native
UbuntuShapeOverlay instead of PartialColorizeUbuntuShape to render
the progression in the Slider and ProgressBar components. The
rendering is now faster since it removes an FBO indirection and
enables batching by the QtQtuick renderer.
Fixes LP: #1398370, LP: #1427169
  * Added a dedicated overlay shape. Made use of the new UbuntuShape
architecture to create an extended shape with efficient overlay
rendering. Fixes LP: #1396170
  * Removed misleading statement from UbuntuShape documentation.
Fixes LP: #1430198
  * Renamed the overlayGeometry property to overlayRect. The
overlayGeometry being of type QRect, using overlayRect instead
makes it more precise, less generic. Fixes LP: #1430278
  * Converted sourceOpacity from float to qreal. Respect the same
guideline QtQuick items use to expose floating-point properties.
That doesn't break the QML API since there's no precision loss
from single to double precision, the cast is implicit.
Fixes LP: #1430267
  * Fixed embedded QML code snippets indentation. Fixes LP: #1430274

  [ Florian Boucault ]
  * CheckBox: apply clipping to the Ubuntu shape and not to the CheckBox
itself so that the tick never overflows. Fixes LP: #1430191

  [ Daniel Holbach ]
  * A number of links changed on design.ubuntu.com - let's make sure
they're fixed in our docs. Fixes LP: #1428051

  [ CI Train Bot ]
  * New rebuild forced.
 -- CI Train BotWed, 18 Mar 2015 12:23:35 +

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Test verification should be split

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released

Bug description:
  Split off test verification and run it once only for 'make check'.

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

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

[Touch-packages] [Bug 1431228] Re: Clean QML cache after updating package, before reboot.

This bug was fixed in the package ubuntu-ui-toolkit -
1.2.1450+15.04.20150318-0ubuntu1

---
ubuntu-ui-toolkit (1.2.1450+15.04.20150318-0ubuntu1) vivid; urgency=medium

  [ Timo Jyrinki ]
  * Clean QML cache after updating package, before reboot. LP: #1431228

  [ Zoltán Balogh ]
  * Improved test plan script. Fixes LP: #1430201

  [ Christian Dywan ]
  * New text handler visuals and improved behavior.
Fixes LP: #1391335, LP: #1407723, LP: #1415548
  * Split off test verification and run it once only for 'make check'.
Fixes LP: #1431698
  * Tweak assert_discard_popover to work better with textfield in header.
Fixes LP: #1432611

  [ Tim Peeters ]
  * Make the filenames for header and navigation tests consistent and
split up the big tabbed header.qml into multiple smaller test files.
Fixes LP: #1429838

  [ Loïc Molinari ]
  * Optimized Slider and ProgressBar components. Switched to the native
UbuntuShapeOverlay instead of PartialColorizeUbuntuShape to render
the progression in the Slider and ProgressBar components. The
rendering is now faster since it removes an FBO indirection and
enables batching by the QtQtuick renderer.
Fixes LP: #1398370, LP: #1427169
  * Added a dedicated overlay shape. Made use of the new UbuntuShape
architecture to create an extended shape with efficient overlay
rendering. Fixes LP: #1396170
  * Removed misleading statement from UbuntuShape documentation.
Fixes LP: #1430198
  * Renamed the overlayGeometry property to overlayRect. The
overlayGeometry being of type QRect, using overlayRect instead
makes it more precise, less generic. Fixes LP: #1430278
  * Converted sourceOpacity from float to qreal. Respect the same
guideline QtQuick items use to expose floating-point properties.
That doesn't break the QML API since there's no precision loss
from single to double precision, the cast is implicit.
Fixes LP: #1430267
  * Fixed embedded QML code snippets indentation. Fixes LP: #1430274

  [ Florian Boucault ]
  * CheckBox: apply clipping to the Ubuntu shape and not to the CheckBox
itself so that the tick never overflows. Fixes LP: #1430191

  [ Daniel Holbach ]
  * A number of links changed on design.ubuntu.com - let's make sure
they're fixed in our docs. Fixes LP: #1428051

  [ CI Train Bot ]
  * New rebuild forced.
 -- CI Train BotWed, 18 Mar 2015 12:23:35 +

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Clean QML cache after updating package, before reboot.

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released

Bug description:
  When the UITK test plan script is executed the  QML cache shopuld be
  cleaned after updating package, before reboot.

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

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

[Touch-packages] [Bug 1427169] Re: Bevel effect broken on ProgressBar

This bug was fixed in the package ubuntu-ui-toolkit -
1.2.1450+15.04.20150318-0ubuntu1

---
ubuntu-ui-toolkit (1.2.1450+15.04.20150318-0ubuntu1) vivid; urgency=medium

  [ Timo Jyrinki ]
  * Clean QML cache after updating package, before reboot. LP: #1431228

  [ Zoltán Balogh ]
  * Improved test plan script. Fixes LP: #1430201

  [ Christian Dywan ]
  * New text handler visuals and improved behavior.
Fixes LP: #1391335, LP: #1407723, LP: #1415548
  * Split off test verification and run it once only for 'make check'.
Fixes LP: #1431698
  * Tweak assert_discard_popover to work better with textfield in header.
Fixes LP: #1432611

  [ Tim Peeters ]
  * Make the filenames for header and navigation tests consistent and
split up the big tabbed header.qml into multiple smaller test files.
Fixes LP: #1429838

  [ Loïc Molinari ]
  * Optimized Slider and ProgressBar components. Switched to the native
UbuntuShapeOverlay instead of PartialColorizeUbuntuShape to render
the progression in the Slider and ProgressBar components. The
rendering is now faster since it removes an FBO indirection and
enables batching by the QtQtuick renderer.
Fixes LP: #1398370, LP: #1427169
  * Added a dedicated overlay shape. Made use of the new UbuntuShape
architecture to create an extended shape with efficient overlay
rendering. Fixes LP: #1396170
  * Removed misleading statement from UbuntuShape documentation.
Fixes LP: #1430198
  * Renamed the overlayGeometry property to overlayRect. The
overlayGeometry being of type QRect, using overlayRect instead
makes it more precise, less generic. Fixes LP: #1430278
  * Converted sourceOpacity from float to qreal. Respect the same
guideline QtQuick items use to expose floating-point properties.
That doesn't break the QML API since there's no precision loss
from single to double precision, the cast is implicit.
Fixes LP: #1430267
  * Fixed embedded QML code snippets indentation. Fixes LP: #1430274

  [ Florian Boucault ]
  * CheckBox: apply clipping to the Ubuntu shape and not to the CheckBox
itself so that the tick never overflows. Fixes LP: #1430191

  [ Daniel Holbach ]
  * A number of links changed on design.ubuntu.com - let's make sure
they're fixed in our docs. Fixes LP: #1428051

  [ CI Train Bot ]
  * New rebuild forced.
 -- CI Train BotWed, 18 Mar 2015 12:23:35 +

** Changed in: ubuntu-ui-toolkit (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 ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1427169

Title:
  Bevel effect broken on ProgressBar

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released

Bug description:
  The white bevel effect on the bottom of the UbuntuShape doesn't appear
  in the ProgressBar. It clearly appears when the theme background is
  dark as visible on the attached snapshot.

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

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

[Touch-packages] [Bug 1398370] Re: Replace PartialColorizeUbuntuShape.qml by a native solution

This bug was fixed in the package ubuntu-ui-toolkit -
1.2.1450+15.04.20150318-0ubuntu1

---
ubuntu-ui-toolkit (1.2.1450+15.04.20150318-0ubuntu1) vivid; urgency=medium

  [ Timo Jyrinki ]
  * Clean QML cache after updating package, before reboot. LP: #1431228

  [ Zoltán Balogh ]
  * Improved test plan script. Fixes LP: #1430201

  [ Christian Dywan ]
  * New text handler visuals and improved behavior.
Fixes LP: #1391335, LP: #1407723, LP: #1415548
  * Split off test verification and run it once only for 'make check'.
Fixes LP: #1431698
  * Tweak assert_discard_popover to work better with textfield in header.
Fixes LP: #1432611

  [ Tim Peeters ]
  * Make the filenames for header and navigation tests consistent and
split up the big tabbed header.qml into multiple smaller test files.
Fixes LP: #1429838

  [ Loïc Molinari ]
  * Optimized Slider and ProgressBar components. Switched to the native
UbuntuShapeOverlay instead of PartialColorizeUbuntuShape to render
the progression in the Slider and ProgressBar components. The
rendering is now faster since it removes an FBO indirection and
enables batching by the QtQtuick renderer.
Fixes LP: #1398370, LP: #1427169
  * Added a dedicated overlay shape. Made use of the new UbuntuShape
architecture to create an extended shape with efficient overlay
rendering. Fixes LP: #1396170
  * Removed misleading statement from UbuntuShape documentation.
Fixes LP: #1430198
  * Renamed the overlayGeometry property to overlayRect. The
overlayGeometry being of type QRect, using overlayRect instead
makes it more precise, less generic. Fixes LP: #1430278
  * Converted sourceOpacity from float to qreal. Respect the same
guideline QtQuick items use to expose floating-point properties.
That doesn't break the QML API since there's no precision loss
from single to double precision, the cast is implicit.
Fixes LP: #1430267
  * Fixed embedded QML code snippets indentation. Fixes LP: #1430274

  [ Florian Boucault ]
  * CheckBox: apply clipping to the Ubuntu shape and not to the CheckBox
itself so that the tick never overflows. Fixes LP: #1430191

  [ Daniel Holbach ]
  * A number of links changed on design.ubuntu.com - let's make sure
they're fixed in our docs. Fixes LP: #1428051

  [ CI Train Bot ]
  * New rebuild forced.
 -- CI Train BotWed, 18 Mar 2015 12:23:35 +

** Changed in: ubuntu-ui-toolkit (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 ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1398370

Title:
  Replace PartialColorizeUbuntuShape.qml by a native solution

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released

Bug description:
  PartialColorizeUbuntuShape.qml is used by the Slider and the
  ProgressBar. It implies a slow FBO indirection and prevents batching
  in the QtQuick renderer. It should be replaced by a native solution to
  improve rendering speed.

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

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

[Touch-packages] [Bug 1430278] Re: [UbuntuShapeOverlay] Rename overlayGeometry to overlayRect

This bug was fixed in the package ubuntu-ui-toolkit -
1.2.1450+15.04.20150318-0ubuntu1

---
ubuntu-ui-toolkit (1.2.1450+15.04.20150318-0ubuntu1) vivid; urgency=medium

  [ Timo Jyrinki ]
  * Clean QML cache after updating package, before reboot. LP: #1431228

  [ Zoltán Balogh ]
  * Improved test plan script. Fixes LP: #1430201

  [ Christian Dywan ]
  * New text handler visuals and improved behavior.
Fixes LP: #1391335, LP: #1407723, LP: #1415548
  * Split off test verification and run it once only for 'make check'.
Fixes LP: #1431698
  * Tweak assert_discard_popover to work better with textfield in header.
Fixes LP: #1432611

  [ Tim Peeters ]
  * Make the filenames for header and navigation tests consistent and
split up the big tabbed header.qml into multiple smaller test files.
Fixes LP: #1429838

  [ Loïc Molinari ]
  * Optimized Slider and ProgressBar components. Switched to the native
UbuntuShapeOverlay instead of PartialColorizeUbuntuShape to render
the progression in the Slider and ProgressBar components. The
rendering is now faster since it removes an FBO indirection and
enables batching by the QtQtuick renderer.
Fixes LP: #1398370, LP: #1427169
  * Added a dedicated overlay shape. Made use of the new UbuntuShape
architecture to create an extended shape with efficient overlay
rendering. Fixes LP: #1396170
  * Removed misleading statement from UbuntuShape documentation.
Fixes LP: #1430198
  * Renamed the overlayGeometry property to overlayRect. The
overlayGeometry being of type QRect, using overlayRect instead
makes it more precise, less generic. Fixes LP: #1430278
  * Converted sourceOpacity from float to qreal. Respect the same
guideline QtQuick items use to expose floating-point properties.
That doesn't break the QML API since there's no precision loss
from single to double precision, the cast is implicit.
Fixes LP: #1430267
  * Fixed embedded QML code snippets indentation. Fixes LP: #1430274

  [ Florian Boucault ]
  * CheckBox: apply clipping to the Ubuntu shape and not to the CheckBox
itself so that the tick never overflows. Fixes LP: #1430191

  [ Daniel Holbach ]
  * A number of links changed on design.ubuntu.com - let's make sure
they're fixed in our docs. Fixes LP: #1428051

  [ CI Train Bot ]
  * New rebuild forced.
 -- CI Train BotWed, 18 Mar 2015 12:23:35 +

** Changed in: ubuntu-ui-toolkit (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 ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1430278

Title:
  [UbuntuShapeOverlay] Rename overlayGeometry to overlayRect

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released

Bug description:
  The UbuntuShapeOverlay has a property name "overlayGeometry" with type
  QRect, it would be better to rename it to "overlayRect" to define its
  nature more clearly.

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

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

[Touch-packages] [Bug 1430198] Re: Misleading Ubuntu Shape documentation

This bug was fixed in the package ubuntu-ui-toolkit -
1.2.1450+15.04.20150318-0ubuntu1

---
ubuntu-ui-toolkit (1.2.1450+15.04.20150318-0ubuntu1) vivid; urgency=medium

  [ Timo Jyrinki ]
  * Clean QML cache after updating package, before reboot. LP: #1431228

  [ Zoltán Balogh ]
  * Improved test plan script. Fixes LP: #1430201

  [ Christian Dywan ]
  * New text handler visuals and improved behavior.
Fixes LP: #1391335, LP: #1407723, LP: #1415548
  * Split off test verification and run it once only for 'make check'.
Fixes LP: #1431698
  * Tweak assert_discard_popover to work better with textfield in header.
Fixes LP: #1432611

  [ Tim Peeters ]
  * Make the filenames for header and navigation tests consistent and
split up the big tabbed header.qml into multiple smaller test files.
Fixes LP: #1429838

  [ Loïc Molinari ]
  * Optimized Slider and ProgressBar components. Switched to the native
UbuntuShapeOverlay instead of PartialColorizeUbuntuShape to render
the progression in the Slider and ProgressBar components. The
rendering is now faster since it removes an FBO indirection and
enables batching by the QtQtuick renderer.
Fixes LP: #1398370, LP: #1427169
  * Added a dedicated overlay shape. Made use of the new UbuntuShape
architecture to create an extended shape with efficient overlay
rendering. Fixes LP: #1396170
  * Removed misleading statement from UbuntuShape documentation.
Fixes LP: #1430198
  * Renamed the overlayGeometry property to overlayRect. The
overlayGeometry being of type QRect, using overlayRect instead
makes it more precise, less generic. Fixes LP: #1430278
  * Converted sourceOpacity from float to qreal. Respect the same
guideline QtQuick items use to expose floating-point properties.
That doesn't break the QML API since there's no precision loss
from single to double precision, the cast is implicit.
Fixes LP: #1430267
  * Fixed embedded QML code snippets indentation. Fixes LP: #1430274

  [ Florian Boucault ]
  * CheckBox: apply clipping to the Ubuntu shape and not to the CheckBox
itself so that the tick never overflows. Fixes LP: #1430191

  [ Daniel Holbach ]
  * A number of links changed on design.ubuntu.com - let's make sure
they're fixed in our docs. Fixes LP: #1428051

  [ CI Train Bot ]
  * New rebuild forced.
 -- CI Train BotWed, 18 Mar 2015 12:23:35 +

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Misleading Ubuntu Shape documentation

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released

Bug description:
  The statement in the UbuntuShape documentation is misleading.

  It says that  UbuntuShape.Repeat is not supported yet when in fact it
  is supported.

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

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

[Touch-packages] [Bug 1430191] Re: Checkbox does not clip the tick mark

This bug was fixed in the package ubuntu-ui-toolkit -
1.2.1450+15.04.20150318-0ubuntu1

---
ubuntu-ui-toolkit (1.2.1450+15.04.20150318-0ubuntu1) vivid; urgency=medium

  [ Timo Jyrinki ]
  * Clean QML cache after updating package, before reboot. LP: #1431228

  [ Zoltán Balogh ]
  * Improved test plan script. Fixes LP: #1430201

  [ Christian Dywan ]
  * New text handler visuals and improved behavior.
Fixes LP: #1391335, LP: #1407723, LP: #1415548
  * Split off test verification and run it once only for 'make check'.
Fixes LP: #1431698
  * Tweak assert_discard_popover to work better with textfield in header.
Fixes LP: #1432611

  [ Tim Peeters ]
  * Make the filenames for header and navigation tests consistent and
split up the big tabbed header.qml into multiple smaller test files.
Fixes LP: #1429838

  [ Loïc Molinari ]
  * Optimized Slider and ProgressBar components. Switched to the native
UbuntuShapeOverlay instead of PartialColorizeUbuntuShape to render
the progression in the Slider and ProgressBar components. The
rendering is now faster since it removes an FBO indirection and
enables batching by the QtQtuick renderer.
Fixes LP: #1398370, LP: #1427169
  * Added a dedicated overlay shape. Made use of the new UbuntuShape
architecture to create an extended shape with efficient overlay
rendering. Fixes LP: #1396170
  * Removed misleading statement from UbuntuShape documentation.
Fixes LP: #1430198
  * Renamed the overlayGeometry property to overlayRect. The
overlayGeometry being of type QRect, using overlayRect instead
makes it more precise, less generic. Fixes LP: #1430278
  * Converted sourceOpacity from float to qreal. Respect the same
guideline QtQuick items use to expose floating-point properties.
That doesn't break the QML API since there's no precision loss
from single to double precision, the cast is implicit.
Fixes LP: #1430267
  * Fixed embedded QML code snippets indentation. Fixes LP: #1430274

  [ Florian Boucault ]
  * CheckBox: apply clipping to the Ubuntu shape and not to the CheckBox
itself so that the tick never overflows. Fixes LP: #1430191

  [ Daniel Holbach ]
  * A number of links changed on design.ubuntu.com - let's make sure
they're fixed in our docs. Fixes LP: #1428051

  [ CI Train Bot ]
  * New rebuild forced.
 -- CI Train BotWed, 18 Mar 2015 12:23:35 +

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Checkbox does not clip the tick mark

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released

Bug description:
  When CheckBox is resized to be smaller than the default size, it does
  not clip the tick mark.

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

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

[Touch-packages] [Bug 1430274] Re: [UbuntuShape] Bad indentation of embedded QML code snippets

This bug was fixed in the package ubuntu-ui-toolkit -
1.2.1450+15.04.20150318-0ubuntu1

---
ubuntu-ui-toolkit (1.2.1450+15.04.20150318-0ubuntu1) vivid; urgency=medium

  [ Timo Jyrinki ]
  * Clean QML cache after updating package, before reboot. LP: #1431228

  [ Zoltán Balogh ]
  * Improved test plan script. Fixes LP: #1430201

  [ Christian Dywan ]
  * New text handler visuals and improved behavior.
Fixes LP: #1391335, LP: #1407723, LP: #1415548
  * Split off test verification and run it once only for 'make check'.
Fixes LP: #1431698
  * Tweak assert_discard_popover to work better with textfield in header.
Fixes LP: #1432611

  [ Tim Peeters ]
  * Make the filenames for header and navigation tests consistent and
split up the big tabbed header.qml into multiple smaller test files.
Fixes LP: #1429838

  [ Loïc Molinari ]
  * Optimized Slider and ProgressBar components. Switched to the native
UbuntuShapeOverlay instead of PartialColorizeUbuntuShape to render
the progression in the Slider and ProgressBar components. The
rendering is now faster since it removes an FBO indirection and
enables batching by the QtQtuick renderer.
Fixes LP: #1398370, LP: #1427169
  * Added a dedicated overlay shape. Made use of the new UbuntuShape
architecture to create an extended shape with efficient overlay
rendering. Fixes LP: #1396170
  * Removed misleading statement from UbuntuShape documentation.
Fixes LP: #1430198
  * Renamed the overlayGeometry property to overlayRect. The
overlayGeometry being of type QRect, using overlayRect instead
makes it more precise, less generic. Fixes LP: #1430278
  * Converted sourceOpacity from float to qreal. Respect the same
guideline QtQuick items use to expose floating-point properties.
That doesn't break the QML API since there's no precision loss
from single to double precision, the cast is implicit.
Fixes LP: #1430267
  * Fixed embedded QML code snippets indentation. Fixes LP: #1430274

  [ Florian Boucault ]
  * CheckBox: apply clipping to the Ubuntu shape and not to the CheckBox
itself so that the tick never overflows. Fixes LP: #1430191

  [ Daniel Holbach ]
  * A number of links changed on design.ubuntu.com - let's make sure
they're fixed in our docs. Fixes LP: #1428051

  [ CI Train Bot ]
  * New rebuild forced.
 -- CI Train BotWed, 18 Mar 2015 12:23:35 +

** Changed in: ubuntu-ui-toolkit (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 ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1430274

Title:
  [UbuntuShape] Bad indentation of embedded QML code snippets

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released

Bug description:
  The UbuntuShape items' doc have a superfluous level of indentation for
  their embeded QML code snippets.

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

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

[Touch-packages] [Bug 1314653] Re: sysvinit: default cpufreq governor to powersave for intel-pstate driver

2015-03-18 Thread Philipp Kern

Package in -proposed looks good to me.

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

Title:
  sysvinit: default cpufreq governor to powersave for intel-pstate
  driver

Status in sysvinit package in Ubuntu:
  Fix Released
Status in sysvinit source package in Trusty:
  Fix Committed
Status in sysvinit source package in Utopic:
  Fix Released

Bug description:
  When defaulting to the intel-pstate driver, there are only a couple of
  cpufreq governors available, none of which are handled in the
  /etc/init.d/ondemand script.

  Since this driver is meant to be used for power saving, it seems wrong
  to leave the system in the kernel default configured "performance"
  governor after boot, so I think it is pertinent to set this to
  "powersave" if it is the only suitable non-power hungry governor
  available.

  How to reproduce:

  1. enable the intel_pstate driver on a recent Intel machine
  (Sandybridge or above)

  edit /etc/default/grub, modify the following:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_pstate=enable"

  and run:

  sudo update-grub

  and reboot.

  2. login

  3. wait at least 60 seconds for /etc/init.d/ondemand to complete

  check out the default cpufreq governor, you will see it is still set
  to the boot default of "performance":

  cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor

  With the attached fix the system will boot into a less aggressive
  cpufreq governor.

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

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

[Touch-packages] [Bug 1430201] Re: UITK test plan script needs improvement