[Touch-packages] [Bug 1527416] Re: Unexpected change in "df /"output

2016-01-07 Thread Marc Tamsky
I'd like to take back my earlier comment.

It all starts in https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=653073

In 14.04.3, the final straw for me is the transition from coreutils
8.21-1ubuntu5.2 to coreutils 8.21-1ubuntu5.3.

In my case, there is an enabling requirement:  grub must pass root=UUID
= to the kernel at boot time.

I can restore the "correct" output from `df /` if I first uncomment
GRUB_DISABLE_LINUX_UUID=true in `/etc/default/grub`, followed by running
`update-grub`, and reboot.  This type of change may not work for
everyone, as some folks may be relying on UUIDs for consistent volume
identification.  Ymmv.

It would be nice if `df /` could run `readlink -f` on the filesystem in
column one, perhaps as a flag or ENV variable, but that's a separate
story.


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

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

Title:
  Unexpected change in "df /"output

Status in coreutils package in Ubuntu:
  Confirmed

Bug description:
  An unexpected change in the output of "df /" has happened in either
  coreutils 8.21-1ubuntu5.3 or 8.21-1ubuntu5.2.

  After doing updates on a number of servers today, the output of "df /"
  has changed. It now shows the full device path, including uuid of the
  device, instead of just the "generic" device.

  For example, on an updated server with coreutils 8.21-1ubuntu5.3:
  # df /
  Filesystem 1K-blocksUsed 
Available Use% Mounted on
  /dev/disk/by-uuid/----   8115168 3542936   
4136956  47% /

  On a server with coreutils 8.21-1ubuntu5.1:
  # df /
  Filesystem 1K-blocksUsed Available Use% Mounted on
  /dev/xvda1   8115168 4260144   3419748  56% /

  This makes scripts or other processes (monitoring scripts to report
  available disk space, for example) that rely on a standard filesystem
  name across numerous servers break, as each server will have a
  different disk UUID.

  Oddly, attached volumes (non-root volumes) don't exhibit the behaviour, and 
continue to show the "generic" device:
  # df /media/ebs1
  Filesystem 1K-blocks  Used Available Use% Mounted on
  /dev/xvdf  104806400 43260 104763140   1% /media/ebs1

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

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

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


[Touch-packages] [Bug 1523900] Re: Buffer leak during repeated mirscreencasts causes server to be killed

2016-01-07 Thread Launchpad Bug Tracker
** Branch linked: lp:~cemil-azizoglu/mir/fix-1523900

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

Title:
  Buffer leak during repeated mirscreencasts causes server to be killed

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

Bug description:
  Nexus 4 running latest stable image -

  current build number: 25
  device name: mako
  channel: ubuntu-touch/stable/ubuntu
  last update: 2015-12-08 11:53:16
  version version: 25
  version ubuntu: 20151118.2
  version tag: OTA-8
  version device: 20150911
  version custom: 20151118.2

  I'm running the following command to capture a screenshot of a running
  app, the unity shell, the splash screen when apps load etc.

adb shell mirscreencast -m /var/run/mir_socket  -n1

  I'm doing this in a script, across many hundreds of apps, so I'm doing
  it a lot. I'm seeing my script get wedged fairly often with errors
  such as this one:-

  [1449575031.562843]  MirConnectionAPI: Caught exception at client 
library boundary (in release): 
/build/mir-AHj2eT/mir-0.17.1+15.04.20151105.1/src/client/rpc/stream_socket_transport.cpp(168):
 Throw in function virtual void 
mir::client::rpc::StreamSocketTransport::send_message(const 
std::vector&, const std::vector&)
  Dynamic exception type: 
N5boost16exception_detail10clone_implINS0_19error_info_injectorIN3mir25socket_disconnected_errorE
  std::exception::what: Failed to send message to server: Broken pipe

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

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


[Touch-packages] [Bug 523896] Re: useradd: cannot lock /etc/passwd; try again later.

2016-01-07 Thread Seth Arnold
Barki, sudo rm -f /etc/gshadow.lock ; sudo apt-get install -f

Thanks

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

Title:
  useradd: cannot lock /etc/passwd; try again later.

Status in shadow package in Ubuntu:
  Fix Released
Status in shadow source package in Precise:
  Fix Released
Status in shadow source package in Quantal:
  Fix Released

Bug description:
  Binary package hint: postfix

  Ubuntu 9.10, via Update Manager.

  SOLUTION:

  Look for /etc/group.lock, /etc/passwd.lock and /etc/shadow.lock files
  and remove them.

  Be careful to only remove the files ending in 'lock' or else you might
  damage your system.

  Please do not add comments just containing "Me too", instead please provide 
any information that could indicate why the files were locked:
   * the list of locked files:
  ls /etc/passwd.lock /etc/shadow.lock /etc/group.lock /etc/gshadow.lock

   * check the /var/log/auth.log for any message that could indicate the
  failure of any other tool (prior to the failure which reported the
  locked file)

   * any abnormal operation on the machine (reset, shutdown while the
  computer is still running)

  == SRU template ==

  [IMPACT]

   * Locked files prevent adding/removing/modifying system users & groups
   * This can result in failure to upgrade/remove packages that use system user 
names
   * The applied fix is to clear the locks on booting.

  [TESTCASE]

   * $ sudo touch /etc/passwd.lock
   * $ sudo adduser testing523896
   * FAIL
   * Upgrade to new package
   * $ sudo adduser testing523896
   * FAIL
   * $ sudo reboot (or shutdown & poweron machine in any other way)
   * $ sudo adduser testing523896
   * PASS

   * Also you can touch the locks, check that they are there and run `$
  sudo start passwd` to clear them.

  [Regression Potential]

   * We are adding an extra job which will always run at boot, which will have 
a tiny impact  on boot performance
   
   * The new job can be mis-used directly via `$ sudo start passwd`, but root 
user could clear the locks in the exact same way as well, before introducing 
this upstart job.

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

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


[Touch-packages] [Bug 1527546] Re: Crash when having multiple QQuickViews in a row

2016-01-07 Thread Launchpad Bug Tracker
** Branch linked: lp:~zsombi/ubuntu-ui-toolkit/fixDefaultTheme

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

Title:
  Crash when having multiple QQuickViews in a row

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  This crash has started with Qt 5.5.1 that is more strict with sharing
  objects between qml engines.

  My guess it is something wrong with the theming engine that seems to
  be a singleton for all qml engines.

  When running the example that i will attach with

  QV4_FORCE_INTERPRETER=1 QV4_MM_AGGRESSIVE_GC=1 ./borrame3

  in xenial i get

  $ QV4_FORCE_INTERPRETER=1 QV4_MM_AGGRESSIVE_GC=1 ./borrame3 
  A
  B
  QMetaProperty::read: Unable to handle unregistered datatype 
'PaletteValues_QMLTYPE_2*' for property 'Palette_QMLTYPE_3::selected'
  QMetaProperty::read: Unable to handle unregistered datatype 
'PaletteValues_QMLTYPE_2*' for property 'Palette_QMLTYPE_3::selected'
  QMetaProperty::read: Unable to handle unregistered datatype 
'PaletteValues_QMLTYPE_2*' for property 'Palette_QMLTYPE_3::selected'
  Segmentation fault

  while vivid+overlay (has qt 5.4) gets me
  A
  B
  C

  the backtrace of the crash in Xenial is
  http://paste.ubuntu.com/14086991/

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

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


[Touch-packages] [Bug 1389759] Re: Tutorial on theming

2016-01-07 Thread Zsombor Egri
The tutorial has been released with sub-theming support.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Triaged => 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/1389759

Title:
  Tutorial on theming

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released

Bug description:
  We need a tutorial on how to create your own theme that is based on
  the default theme, overriding small things like the colors, and show
  how to use a different theme in your own apps.

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

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


[Touch-packages] [Bug 1455916] Re: [Dell Inspiron N5110] Xorg unexpectedly crashed

2016-01-07 Thread Christopher M. Penalver
green5, it will help immensely if you filed a new report with Ubuntu via a 
terminal:
ubuntu-bug xorg

Please ensure you have the package xdiagnose installed, and that you
click the Yes button for attaching additional debugging information.

Also, please feel free to subscribe me to it.

For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.

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

Title:
  [Dell Inspiron N5110] Xorg unexpectedly crashed

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Xorg unexpectedly crashed bringing down down metacity and gnome-flashback too.
  This is the relevant section from the system logs:
  May 17 15:09:05 ultra-d gnome-session[1514]: Window manager warning: Log 
level 6: The program 'metacity' received an X Window System error.
  May 17 15:09:05 ultra-d gnome-session[1514]: This probably reflects a bug in 
the program.
  May 17 15:09:05 ultra-d gnome-session[1514]: The error was 'BadRegion 
(invalid Region parameter)'.
  May 17 15:09:05 ultra-d gnome-session[1514]: (Details: serial 508727326 
error_code 140 request_code 138 (XFIXES) minor_code 12)
  May 17 15:09:05 ultra-d gnome-session[1514]: (Note to programmers: normally, 
X errors are reported asynchronously;
  May 17 15:09:05 ultra-d gnome-session[1514]: that is, you will receive the 
error a while after causing it.
  May 17 15:09:05 ultra-d gnome-session[1514]: To debug your program, run it 
with the GDK_SYNCHRONIZE environment
  May 17 15:09:05 ultra-d gnome-session[1514]: variable to change this 
behavior. You can then get a meaningful
  May 17 15:09:05 ultra-d gnome-session[1514]: backtrace from your debugger if 
you break on the gdk_x_error() function.)
  May 17 15:09:05 ultra-d kernel: [276368.790571] traps: metacity[1688] trap 
int3 ip:7fb31d5d9d00 sp:7ffc0f98c740 error:0
  May 17 15:09:19 ultra-d gnome-session[1514]: gnome-session[1514]: WARNING: 
Child process 1688 was already dead.
  May 17 15:09:19 ultra-d gnome-session[1514]: WARNING: Child process 1688 was 
already dead.
  May 17 15:09:19 ultra-d gnome-session[1514]: gnome-session[1514]: WARNING: 
Application 'metacity.desktop' killed by signal 5
  May 17 15:09:19 ultra-d gnome-session[1514]: WARNING: Application 
'metacity.desktop' killed by signal 5
  May 17 15:09:19 ultra-d gnome-session[1514]: gnome-session[1514]: WARNING: 
App 'metacity.desktop' respawning too quickly
  May 17 15:09:19 ultra-d gnome-session[1514]: WARNING: App 'metacity.desktop' 
respawning too quickly
  May 17 15:09:19 ultra-d gnome-session[1514]: Unrecoverable failure in 
required component metacity.desktop
  May 17 15:09:19 ultra-d gnome-session[1514]: gnome-session[1514]: CRITICAL: 
We failed, but the fail whale is dead. Sorry
  May 17 15:09:19 ultra-d gnome-session[1514]: CRITICAL: We failed, but the 
fail whale is dead. Sorry
  May 17 15:09:20 ultra-d gnome-session[1514]: ICE default IO error handler 
doing an exit(), pid = 17669, errno = 11

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun May 17 15:56:28 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.26, 3.19.0-15-generic, x86_64: installed
   virtualbox, 4.3.26, 3.19.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:04ca]
   Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M 
Series] [1002:6760] (rev ff) (prog-if ff)
  MachineType: Dell Inc. Inspiron N5110
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic 
root=/dev/mapper/system_vg-root_lv ro cryptdevice=/dev/sda2:system_crypt quiet 
splash vt.handoff=7
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0FTJWD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A11
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd08/03/2012:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn0FTJWD:rvrA11:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron N5110
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  versio

[Touch-packages] [Bug 1527416] Re: Unexpected change in "df /"output

2016-01-07 Thread Marc Tamsky
Probably caused by the thoughtless changes that have been upstreamed in
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1432871

How could the difference between:

vagrant@vagrant-ubuntu-trusty-64:~$ df /
Filesystem 1K-blocksUsed 
Available Use% Mounted on
/dev/disk/by-uuid/3af531bb-7c15-4e60-b23f-4853c47ccc91  41251136 1356000  
38159224   4% /

and

vagrant@vagrant-ubuntu-trusty-64:~$ df | grep /$
/dev/sda1   41251136   1356000  38159224   4% /

not be a bug?

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

Title:
  Unexpected change in "df /"output

Status in coreutils package in Ubuntu:
  Confirmed

Bug description:
  An unexpected change in the output of "df /" has happened in either
  coreutils 8.21-1ubuntu5.3 or 8.21-1ubuntu5.2.

  After doing updates on a number of servers today, the output of "df /"
  has changed. It now shows the full device path, including uuid of the
  device, instead of just the "generic" device.

  For example, on an updated server with coreutils 8.21-1ubuntu5.3:
  # df /
  Filesystem 1K-blocksUsed 
Available Use% Mounted on
  /dev/disk/by-uuid/----   8115168 3542936   
4136956  47% /

  On a server with coreutils 8.21-1ubuntu5.1:
  # df /
  Filesystem 1K-blocksUsed Available Use% Mounted on
  /dev/xvda1   8115168 4260144   3419748  56% /

  This makes scripts or other processes (monitoring scripts to report
  available disk space, for example) that rely on a standard filesystem
  name across numerous servers break, as each server will have a
  different disk UUID.

  Oddly, attached volumes (non-root volumes) don't exhibit the behaviour, and 
continue to show the "generic" device:
  # df /media/ebs1
  Filesystem 1K-blocks  Used Available Use% Mounted on
  /dev/xvdf  104806400 43260 104763140   1% /media/ebs1

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

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

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


[Touch-packages] [Bug 1510276] Re: console-setup font ignored on boot

2016-01-07 Thread Serhiy Zahoriya
*** This bug is a duplicate of bug 657551 ***
https://bugs.launchpad.net/bugs/657551

** This bug has been marked a duplicate of bug 657551
   console-setup doesn't start

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

Title:
  console-setup font ignored on boot

Status in console-setup package in Ubuntu:
  New

Bug description:
  Since cyrillic characters are not supported by the default font I
  tried to run

  # dpkg-reconfigure console-setup

  to change the font. It worked but only until the reboot. After
  rebooting I have to manually run setupcon or add it to rc.local or
  somewhere to make the adequate font appear.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: console-setup 1.108ubuntu9
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Oct 26 22:35:03 2015
  PackageArchitecture: all
  SourcePackage: console-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 657551] Re: console-setup doesn't start

2016-01-07 Thread Serhiy Zahoriya
Worked after changing /etc/default/console-setup to

CHARMAP="UTF-8"
CODESET="Uni2"
FONTFACE="Fixed"
FONTSIZE="16"

, then unzipping the font file (don't remember where I've read that it
helps):

cd /etc/console-setup
sudo gunzip -k Uni2-Fixed16.psf.gz
sudo update-initramfs -u

** Changed in: console-setup (Ubuntu)
 Assignee: Krittika (krittika-kalra) => (unassigned)

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

Title:
  console-setup doesn't start

Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: console-setup

  On startup console-setup doesn't startup and I have wrong font on my console 
- it doesn't display Cyrillic.
  When I try to start it by hand I get:
  xxx@xxx:~/$ sudo service console-setup start
  console-setup stop/waiting

  When I do dpkg-reconfigure I get console font loaded until next reboot.
  I have all maveric, recently updated from 10.04. All updates installed 
regularly.
  Please let me know if I can provide any more information.
  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: console-setup 1.34ubuntu15
  ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic i686
  Architecture: i386
  Date: Sun Oct 10 01:29:48 2010
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=ru_RU:ru:en_GB:en
   PATH=(custom, user)
   LANG=ru_RU.utf8
   SHELL=/bin/bash
  SourcePackage: console-setup

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

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


[Touch-packages] [Bug 873495] Re: LightDM fails to start after nvidia-current or nvidia-current-updates are installed (upstart job issue)

2016-01-07 Thread Launchpad Bug Tracker
[Expired for lightdm (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  LightDM fails to start after nvidia-current or nvidia-current-updates
  are installed (upstart job issue)

Status in Light Display Manager:
  Incomplete
Status in lightdm package in Ubuntu:
  Expired
Status in lightdm source package in Precise:
  Incomplete

Bug description:
  Occurs reliably on fast Sandy Bridge hardware with a fast GPU - GTX
  485M, GTX 560M or GTX 580M.

  Appears to be a race condition. LightDM attempts to start before
  /dev/nvidiactrl is created. As a workaround add "sleep 1 && service
  lightdm start" to /etc/rc.local to start the service.

  ### This workaround is insufficient. Some users have reported that
  their systems do not start after initial user setup. Deleting the
  contents of /var/run/dbus/* resolves the issue in these cases. ###

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: xorg 1:7.6+7ubuntu7
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  280.13  Wed Jul 27 16:53:56 
PDT 2011
   GCC version:  gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3)
  .tmp.unity.support.test.0:

  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,regex,snap,animation,resize,place,vpswitch,mousepoll,workarounds,gnomecompat,compiztoolbox,move,grid,imgpng,wall,fade,expo,session,unitymtgrabhandles,ezoom,scale,unityshell]
  CompositorRunning: compiz
  Date: Thu Oct 13 11:05:18 2011
  DistUpgraded: Fresh install
  DistroCodename: oneiric
  DistroVariant: ubuntu
  DkmsStatus: nvidia-current, 280.13, 3.0.0-12-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   nVidia Corporation Device [10de:0e31] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer Device [1558:5102]
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  JockeyStatus:
   xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, 
Enabled, In use)
   xorg:nvidia_current_updates - NVIDIA accelerated graphics driver 
(post-release updates) (Proprietary, Disabled, Not in use)
  MachineType: System76, Inc. Serval Professional
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic 
root=UUID=79434c5f-d3ca-4224-98f2-06e7b36fbe32 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
    Identifier  "Default Device"
    Option  "NoLogo""True"
   EndSection
  dmi.bios.date: 01/18/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.4
  dmi.board.asset.tag: Not Applicable
  dmi.board.name: Serval Professional
  dmi.board.vendor: System76, Inc.
  dmi.board.version: serp7
  dmi.chassis.asset.tag: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: serp7
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd01/18/2011:svnSystem76,Inc.:pnServalProfessional:pvrserp7:rvnSystem76,Inc.:rnServalProfessional:rvrserp7:cvnSystem76,Inc.:ct10:cvrserp7:
  dmi.product.name: Serval Professional
  dmi.product.version: serp7
  dmi.sys.vendor: System76, Inc.
  version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu3
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.26-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20110811.g93fc084-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20110411+8378443-1

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

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

[Touch-packages] [Bug 1511145] Re: compiz freeze

2016-01-07 Thread Launchpad Bug Tracker
[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/1511145

Title:
  compiz freeze

Status in xorg package in Ubuntu:
  Expired

Bug description:
  How to reproduce :
  1. launch an application
  2. minimize this application
  3. window application freeze
  4. must press the start button to minimize the window
  5. then the window is minimized and the menu "reboot, exit..." appears.
  6. this doesn't happen if there's at least another window and doesn't depend 
on the application (nautilus, firefox...).

  I should notice that I had this problem with 15.04.
  Moreover since 15.04 no icon and folder appear on the desktop (even if the 
desktop folder is not empty) and I can't change the wallpaper.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu4
  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 Oct 28 23:57:29 2015
  DistUpgraded: 2015-10-27 22:25:24,838 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 3.19.0-31-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.2.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:1993]
  InstallationDate: Installed on 2015-01-17 (284 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: Hewlett-Packard HP ProBook 650 G1
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=f43d5be4-5856-42c6-b202-cae43ab131c8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to wily on 2015-10-27 (1 days ago)
  dmi.bios.date: 04/29/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L77 Ver. 01.05
  dmi.board.name: 1993
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.38
  dmi.chassis.asset.tag: 5CG424HY3K
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL77Ver.01.05:bd04/29/2014:svnHewlett-Packard:pnHPProBook650G1:pvrA3009DD10303:rvnHewlett-Packard:rn1993:rvrKBCVersion16.38:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 650 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Thu Oct 29 00:49:00 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 992 
   vendor LGD
  xserver.version: 2:1.17.2-1ubuntu9

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

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


[Touch-packages] [Bug 1514091] Re: xorg faults

2016-01-07 Thread Launchpad Bug Tracker
[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/1514091

Title:
  xorg faults

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Found using xdiagnose.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27
  Uname: Linux 3.13.0-66-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.93  Wed Aug 19 16:49:15 
PDT 2015
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04)
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  Date: Sat Nov  7 17:36:05 2015
  DistUpgraded: 2014-09-27 13:42:13,227 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DpkgLog:
   
  GraphicsCard:
   Subsystem: ASUSTeK Computer Inc. P8H77-I Motherboard [1043:84ca]
   NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:2871]
  InstallationDate: Installed on 2014-02-24 (621 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-66-generic 
root=UUID=28478695-9e82-4e38-abd8-57343c56b0a2 ro
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2014-09-27 (406 days ago)
  XorgConf:
   Section "Device"
Identifier  "Default Device"
Option  "NoLogo""True"
   EndSection
  dmi.bios.date: 04/18/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0401
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V LE PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0401:bd04/18/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLEPLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.5
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sat Nov  7 12:36:15 2015
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.1-0ubuntu2.7

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

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


[Touch-packages] [Bug 1514157] Re: [S550CB, Realtek ALC270, Black Headphone Out, Right] No sound at all when i connect my earphones

2016-01-07 Thread Launchpad Bug Tracker
[Expired for alsa-driver (Ubuntu) because there has been no activity for
60 days.]

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [S550CB, Realtek ALC270, Black Headphone Out, Right] No sound at all
  when i connect my earphones

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  My speaker is working good and when i plug in my headphone in audio
  jack I cannot hear any sound. I have tried everything online but
  nothing worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-31.36~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pardhu 1942 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Nov  8 01:58:27 2015
  InstallationDate: Installed on 2015-10-17 (22 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pardhu 1942 F pulseaudio
  Symptom_Jack: Black Headphone Out, Right
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [S550CB, Realtek ALC270, Black Headphone Out, Right] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/18/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: S550CB.202
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: S550CB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrS550CB.202:bd03/18/2013:svnASUSTeKCOMPUTERINC.:pnS550CB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnS550CB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: S550CB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2015-11-08T01:36:34.274653

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

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


[Touch-packages] [Bug 1513699] Re: Light DM creates login loop

2016-01-07 Thread Launchpad Bug Tracker
[Expired for lightdm (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Light DM creates login loop

Status in lightdm package in Ubuntu:
  Expired

Bug description:
  After updating Ubuntu, I restarted the computer. The Light DM Display
  screen came up.  I thought nothing of it until I tried logging in.
  Instead of logging in, it would go black for a second and bring me to
  the login page again.  I've tried all sorts of commands from online
  Ubuntu support groups. Nothing has worked. My laptop is 5 yrs old, so
  I don't know if it's telling me it's dead.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lightdm 1.14.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.16.0-34.47-generic 3.16.7-ckt8
  Uname: Linux 3.16.0-34-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  Date: Thu Nov  5 20:38:03 2015
  InstallationDate: Installed on 2014-03-18 (598 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1527416] Re: Unexpected change in "df /"output

2016-01-07 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Unexpected change in "df /"output

Status in coreutils package in Ubuntu:
  Confirmed

Bug description:
  An unexpected change in the output of "df /" has happened in either
  coreutils 8.21-1ubuntu5.3 or 8.21-1ubuntu5.2.

  After doing updates on a number of servers today, the output of "df /"
  has changed. It now shows the full device path, including uuid of the
  device, instead of just the "generic" device.

  For example, on an updated server with coreutils 8.21-1ubuntu5.3:
  # df /
  Filesystem 1K-blocksUsed 
Available Use% Mounted on
  /dev/disk/by-uuid/----   8115168 3542936   
4136956  47% /

  On a server with coreutils 8.21-1ubuntu5.1:
  # df /
  Filesystem 1K-blocksUsed Available Use% Mounted on
  /dev/xvda1   8115168 4260144   3419748  56% /

  This makes scripts or other processes (monitoring scripts to report
  available disk space, for example) that rely on a standard filesystem
  name across numerous servers break, as each server will have a
  different disk UUID.

  Oddly, attached volumes (non-root volumes) don't exhibit the behaviour, and 
continue to show the "generic" device:
  # df /media/ebs1
  Filesystem 1K-blocks  Used Available Use% Mounted on
  /dev/xvdf  104806400 43260 104763140   1% /media/ebs1

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

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

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


[Touch-packages] [Bug 1528886] Re: Checking for updates never finishes

2016-01-07 Thread Lorn Potter
Seems this did not totally fix this, it will still hang at 'checking' if
I switch off wifi and then quickly check for updates, but will work if I
press back and then check again.

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

Title:
  Checking for updates never finishes

Status in Canonical System Image:
  Confirmed
Status in connectivity-api package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu RTM:
  Confirmed

Bug description:
  Tested on krillin with SIM and data enabled
  OTA 8.5 stable channel
  Also Arale on proposed 201

  Ensure phone has latest updates installed
  Check for update on Wifi and it reports software is up to date
  Turn off wifi and go to updates panel again
  Note that the indicator shows and active 3G data connection
  Checking for updates ... is shown and I see one of 3 results

  In all cases the log reports:

  2015-12-23 15:34:19,394 - WARNING - void
  UpdatePlugin::Network::checkForNewVersions(QHash&)

  2015-12-23 15:44:56,007 - WARNING - Reply is not valid.

  In some instances I see this but not all, this is logged when the phone locks 
and resumes
  2015-12-23 15:36:18,625 - WARNING - QObject::killTimer: Timers cannot be 
stopped from another thread
  2015-12-23 15:36:18,625 - WARNING - QObject::startTimer: Timers cannot be 
started from another thread

  One time I saw
  Connect to the Internet ...

  In anther case it displayed this after around 5 mins when I did not allow the 
phone to turn off:
  Software is up to date

  In all other cases Checking for updates never finished

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

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


[Touch-packages] [Bug 1532073] [NEW] package ifupdown 0.7.54ubuntu2 failed to install/upgrade: попытка перезаписать «/lib/systemd/system/ifup@.service», который уже имеется в пакете systemd 228+upstre

2016-01-07 Thread Сергей
Public bug reported:

fucked решето

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: ifupdown 0.7.54ubuntu2
ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
Uname: Linux 4.3.0-2-generic x86_64
ApportVersion: 2.19.3-0ubuntu2
Architecture: amd64
Date: Fri Jan  8 03:30:37 2016
ErrorMessage: попытка перезаписать «/lib/systemd/system/ifup@.service», который 
уже имеется в пакете systemd 228+upstream20151219-0.ubuntu
InstallationDate: Installed on 2015-10-23 (76 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
RelatedPackageVersions:
 dpkg 1.18.3ubuntu1
 apt  1.1.10
SourcePackage: ifupdown
Title: package ifupdown 0.7.54ubuntu2 failed to install/upgrade: попытка 
перезаписать «/lib/systemd/system/ifup@.service», который уже имеется в пакете 
systemd 228+upstream20151219-0.ubuntu
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package third-party-packages xenial

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

Title:
  package ifupdown 0.7.54ubuntu2 failed to install/upgrade: попытка
  перезаписать «/lib/systemd/system/ifup@.service», который уже имеется
  в пакете systemd 228+upstream20151219-0.ubuntu

Status in ifupdown package in Ubuntu:
  New

Bug description:
  fucked решето

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ifupdown 0.7.54ubuntu2
  ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
  Uname: Linux 4.3.0-2-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  Date: Fri Jan  8 03:30:37 2016
  ErrorMessage: попытка перезаписать «/lib/systemd/system/ifup@.service», 
который уже имеется в пакете systemd 228+upstream20151219-0.ubuntu
  InstallationDate: Installed on 2015-10-23 (76 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.3ubuntu1
   apt  1.1.10
  SourcePackage: ifupdown
  Title: package ifupdown 0.7.54ubuntu2 failed to install/upgrade: попытка 
перезаписать «/lib/systemd/system/ifup@.service», который уже имеется в пакете 
systemd 228+upstream20151219-0.ubuntu
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1528886] Re: Checking for updates never finishes

2016-01-07 Thread Lorn Potter
This seems to be working now as expected (usinglanding-032) without the
'connect to the internet to check for updates'

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

Title:
  Checking for updates never finishes

Status in Canonical System Image:
  Confirmed
Status in connectivity-api package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu RTM:
  Confirmed

Bug description:
  Tested on krillin with SIM and data enabled
  OTA 8.5 stable channel
  Also Arale on proposed 201

  Ensure phone has latest updates installed
  Check for update on Wifi and it reports software is up to date
  Turn off wifi and go to updates panel again
  Note that the indicator shows and active 3G data connection
  Checking for updates ... is shown and I see one of 3 results

  In all cases the log reports:

  2015-12-23 15:34:19,394 - WARNING - void
  UpdatePlugin::Network::checkForNewVersions(QHash&)

  2015-12-23 15:44:56,007 - WARNING - Reply is not valid.

  In some instances I see this but not all, this is logged when the phone locks 
and resumes
  2015-12-23 15:36:18,625 - WARNING - QObject::killTimer: Timers cannot be 
stopped from another thread
  2015-12-23 15:36:18,625 - WARNING - QObject::startTimer: Timers cannot be 
started from another thread

  One time I saw
  Connect to the Internet ...

  In anther case it displayed this after around 5 mins when I did not allow the 
phone to turn off:
  Software is up to date

  In all other cases Checking for updates never finished

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

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


[Touch-packages] [Bug 1532067] [NEW] package linux-image-extra-4.3.0-5-generic 4.3.0-5.16 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

2016-01-07 Thread Tr4sK
*** This bug is a duplicate of bug 1531331 ***
https://bugs.launchpad.net/bugs/1531331

Public bug reported:

Upgrading from 15.10 to 16.04

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-extra-4.3.0-5-generic 4.3.0-5.16
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.19.3-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   tr4sk  1674 F...m pulseaudio
 /dev/snd/controlC0:  tr4sk  1674 F pulseaudio
 /dev/snd/controlC1:  tr4sk  1674 F pulseaudio
Date: Fri Jan  8 03:45:44 2016
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
HibernationDevice: RESUME=UUID=7516a760-f58c-48b2-a74e-5bcc3ea2bdb9
InstallationDate: Installed on 2016-01-06 (1 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
IwConfig:
 enp2s0no wireless extensions.
 
 lono wireless extensions.
MachineType: MSI MS-7982
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc N/A
RfKill:
 
SourcePackage: initramfs-tools
Title: package linux-image-extra-4.3.0-5-generic 4.3.0-5.16 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev'
UpgradeStatus: Upgraded to xenial on 2016-01-08 (0 days ago)
dmi.bios.date: 09/10/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3.30
dmi.board.asset.tag: Default string
dmi.board.name: B150M PRO-VDH (MS-7982)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.30:bd09/10/2015:svnMSI:pnMS-7982:pvr1.0:rvnMSI:rnB150MPRO-VDH(MS-7982):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.name: MS-7982
dmi.product.version: 1.0
dmi.sys.vendor: MSI

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check xenial

** This bug has been marked a duplicate of bug 1531331
   package linux-image-4.3.0-5-generic:amd64 4.3.0-5.16 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2

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

Title:
  package linux-image-extra-4.3.0-5-generic 4.3.0-5.16 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Upgrading from 15.10 to 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.3.0-5-generic 4.3.0-5.16
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   tr4sk  1674 F...m pulseaudio
   /dev/snd/controlC0:  tr4sk  1674 F pulseaudio
   /dev/snd/controlC1:  tr4sk  1674 F pulseaudio
  Date: Fri Jan  8 03:45:44 2016
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  HibernationDevice: RESUME=UUID=7516a760-f58c-48b2-a74e-5bcc3ea2bdb9
  InstallationDate: Installed on 2016-01-06 (1 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7982
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.3.0-5-generic 4.3.0-5.16 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev'
  UpgradeStatus: Upgraded to xenial on 2016-01-08 (0 days ago)
  dmi.bios.date: 09/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.30
  dmi.board.asset.tag: Default string
  dmi.board.name: B150M PRO-VDH (MS-7982)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.ven

[Touch-packages] [Bug 1528886] Re: Checking for updates never finishes

2016-01-07 Thread Lorn Potter
I tested landing-032 and system-settings at least does not hang at
'checking for updates' when on mobile data (it now checks and when it
completes says 'connect to the internet to check for updates')


landing-032 contains needed fixes in QtNetworkAccessManager (including this 
bug), and would be present with any bearer plugin without them.

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

Title:
  Checking for updates never finishes

Status in Canonical System Image:
  Confirmed
Status in connectivity-api package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu RTM:
  Confirmed

Bug description:
  Tested on krillin with SIM and data enabled
  OTA 8.5 stable channel
  Also Arale on proposed 201

  Ensure phone has latest updates installed
  Check for update on Wifi and it reports software is up to date
  Turn off wifi and go to updates panel again
  Note that the indicator shows and active 3G data connection
  Checking for updates ... is shown and I see one of 3 results

  In all cases the log reports:

  2015-12-23 15:34:19,394 - WARNING - void
  UpdatePlugin::Network::checkForNewVersions(QHash&)

  2015-12-23 15:44:56,007 - WARNING - Reply is not valid.

  In some instances I see this but not all, this is logged when the phone locks 
and resumes
  2015-12-23 15:36:18,625 - WARNING - QObject::killTimer: Timers cannot be 
stopped from another thread
  2015-12-23 15:36:18,625 - WARNING - QObject::startTimer: Timers cannot be 
started from another thread

  One time I saw
  Connect to the Internet ...

  In anther case it displayed this after around 5 mins when I did not allow the 
phone to turn off:
  Software is up to date

  In all other cases Checking for updates never finished

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

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


[Touch-packages] [Bug 1532062] [NEW] Drives mistakenly reported as removable

2016-01-07 Thread Robert Clark
Public bug reported:

I have multiple servers which report their drives are removable, even
though the drives are the main drives in the device (/dev/sda, /dev/sdb,
etc). One of such machines (an IBM system x3650 M1) I have pulled a
report from lsblk and lshw below and included them. These are configured
using the RAID controller that came with the machine. I can provide any
other information needed. I am seeing the same on a HP proliant DL100
g2. In this case the removable tag is triggering a problem with curtin
since curtin currently refuses to install to drives reported as
removable by lsblk.

output of: lsblk -l
NAME MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda8:01   100G  0 disk 
sda1   8:11   100G  0 part /
sdb8:16   1 173.2G  0 disk 
sdb1   8:17   1 172.2G  0 part /var/lib/ceph/osd/ceph-0
sdb2   8:18   1  1023M  0 part 
sr0   11:01  1024M  0 rom  

output of: sudo lshw -class disk
  *-disk:0
   description: SCSI Disk
   physical id: 0.0.0
   bus info: scsi@2:0.0.0
   logical name: /dev/sda
   size: 99GiB (107GB)
   capabilities: partitioned partitioned:dos
   configuration: sectorsize=512
  *-disk:1
   description: SCSI Disk
   physical id: 0.1.0
   bus info: scsi@2:0.1.0
   logical name: /dev/sdb
   size: 173GiB (186GB)
   capabilities: gpt-1.00 partitioned partitioned:gpt
   configuration: guid=66a282c8-da87-4502-902d-ce5c7b4da275 sectorsize=512
  *-disk:2 UNCLAIMED
   description: SCSI Disk
   physical id: 1.0.0
   bus info: scsi@2:1.0.0
  *-disk:3 UNCLAIMED
   description: SCSI Disk
   physical id: 1.1.0
   bus info: scsi@2:1.1.0
  *-cdrom
   description: DVD reader
   product: UJDA780 DVD/CDRW
   vendor: MATSHITA
   physical id: 0.0.0
   bus info: scsi@1:0.0.0
   logical name: /dev/cdrom
   logical name: /dev/sr0
   version: CA21
   capabilities: removable audio cd-r cd-rw dvd
   configuration: ansiversion=5 status=nodisc

** Affects: util-linux (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Drives mistakenly reported as removable

Status in util-linux package in Ubuntu:
  New

Bug description:
  I have multiple servers which report their drives are removable, even
  though the drives are the main drives in the device (/dev/sda,
  /dev/sdb, etc). One of such machines (an IBM system x3650 M1) I have
  pulled a report from lsblk and lshw below and included them. These are
  configured using the RAID controller that came with the machine. I can
  provide any other information needed. I am seeing the same on a HP
  proliant DL100 g2. In this case the removable tag is triggering a
  problem with curtin since curtin currently refuses to install to
  drives reported as removable by lsblk.

  output of: lsblk -l
  NAME MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
  sda8:01   100G  0 disk 
  sda1   8:11   100G  0 part /
  sdb8:16   1 173.2G  0 disk 
  sdb1   8:17   1 172.2G  0 part /var/lib/ceph/osd/ceph-0
  sdb2   8:18   1  1023M  0 part 
  sr0   11:01  1024M  0 rom  

  output of: sudo lshw -class disk
*-disk:0
 description: SCSI Disk
 physical id: 0.0.0
 bus info: scsi@2:0.0.0
 logical name: /dev/sda
 size: 99GiB (107GB)
 capabilities: partitioned partitioned:dos
 configuration: sectorsize=512
*-disk:1
 description: SCSI Disk
 physical id: 0.1.0
 bus info: scsi@2:0.1.0
 logical name: /dev/sdb
 size: 173GiB (186GB)
 capabilities: gpt-1.00 partitioned partitioned:gpt
 configuration: guid=66a282c8-da87-4502-902d-ce5c7b4da275 sectorsize=512
*-disk:2 UNCLAIMED
 description: SCSI Disk
 physical id: 1.0.0
 bus info: scsi@2:1.0.0
*-disk:3 UNCLAIMED
 description: SCSI Disk
 physical id: 1.1.0
 bus info: scsi@2:1.1.0
*-cdrom
 description: DVD reader
 product: UJDA780 DVD/CDRW
 vendor: MATSHITA
 physical id: 0.0.0
 bus info: scsi@1:0.0.0
 logical name: /dev/cdrom
 logical name: /dev/sr0
 version: CA21
 capabilities: removable audio cd-r cd-rw dvd
 configuration: ansiversion=5 status=nodisc

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

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


[Touch-packages] [Bug 523896] Re: useradd: cannot lock /etc/passwd; try again later.

2016-01-07 Thread Barki Mustapha
barki@ninja-network:~$ sudo apt-get update
sudo: unable to resolve host ninja-network
[sudo] password for barki: 
Ign http://dl.google.com stable InRelease
Ign http://ppa.launchpad.net wily InRelease
Hit http://dl.google.com stable Release.gpg
Ign http://archive.canonical.com trusty InRelease  
Hit http://archive.ubuntu.com wily InRelease   
Get:1 http://ppa.launchpad.net wily InRelease [15.4 kB]
Hit http://dl.google.com stable Release
Hit http://archive.canonical.com trusty Release.gpg
Get:2 http://archive.ubuntu.com wily-updates InRelease [64.4 kB]   
Hit http://ppa.launchpad.net wily InRelease
Hit http://archive.canonical.com trusty Release
Hit http://ppa.launchpad.net wily InRelease
Ign http://ppa.launchpad.net wily Release.gpg  
Get:3 http://ppa.launchpad.net wily/main Sources [582 B]   
Get:4 http://ppa.launchpad.net wily/main amd64 Packages [839 B]
Get:5 http://ppa.launchpad.net wily/main i386 Packages [839 B] 
Hit http://dl.google.com stable/main amd64 Packages
Hit http://archive.ubuntu.com wily-backports InRelease 
Get:6 http://ppa.launchpad.net wily/main Translation-en [396 B]
Hit http://dl.google.com stable/main i386 Packages 
Get:7 http://archive.ubuntu.com wily-security InRelease [64.4 kB]  
Hit http://archive.canonical.com trusty/partner Sources
Get:8 http://ppa.launchpad.net wily/main Translation-en [133 B]
Get:9 http://archive.ubuntu.com wily-proposed InRelease [218 kB]   
Hit http://archive.canonical.com trusty/partner amd64 Packages 
Hit http://archive.canonical.com trusty/partner i386 Packages  
Ign http://dl.google.com stable/main Translation-en_US 
Ign http://dl.google.com stable/main Translation-en
Ign http://archive.canonical.com trusty/partner Translation-en 
Ign http://ppa.launchpad.net wily Release  
Hit http://ppa.launchpad.net wily/main Sources 
Hit http://ppa.launchpad.net wily/main amd64 Packages  
Hit http://ppa.launchpad.net wily/main i386 Packages   
Hit http://ppa.launchpad.net wily/main Sources 
Hit http://ppa.launchpad.net wily/main amd64 Packages  
Hit http://ppa.launchpad.net wily/main i386 Packages   
Hit http://ppa.launchpad.net wily/main Translation-en  
Ign http://ppa.launchpad.net wily/main Translation-en  
Get:10 http://archive.ubuntu.com wily-updates/main Sources [41.4 kB]   
Ign http://toolbelt.heroku.com ./ InRelease
Get:11 http://archive.ubuntu.com wily-updates/universe Sources [11.2 kB]   
Err http://ppa.launchpad.net wily/main Sources 
  404  Not Found
Err http://ppa.launchpad.net wily/main amd64 Packages  
  404  Not Found
Get:12 http://archive.ubuntu.com wily-updates/multiverse Sources [1,913 B] 
Hit http://toolbelt.heroku.com ./ Release.gpg  
Err http://ppa.launchpad.net wily/main i386 Packages   
  404  Not Found
Get:13 http://archive.ubuntu.com wily-updates/restricted Sources [3,741 B] 
Ign http://ppa.launchpad.net wily/main Translation-en_US   
Ign http://ppa.launchpad.net wily/main Translation-en  
Get:14 http://archive.ubuntu.com wily-updates/main amd64 Packages [111 kB] 
Hit http://toolbelt.heroku.com ./ Release  
Get:15 http://archive.ubuntu.com wily-updates/restricted amd64 Packages [13.3 
kB]
Get:16 http://archive.ubuntu.com wily-updates/universe amd64 Packages [50.5 kB]
Get:17 http://archive.ubuntu.com wily-updates/multiverse amd64 Packages [5,856 
B]
Hit http://toolbelt.heroku.com ./ Packages 
Get:18 http://archive.ubuntu.com wily-updates/main i386 Packages [108 kB]  
Get:19 http://archive.ubuntu.com wily-updates/restricted i386 Packages [13.4 kB]
Get:20 http://archive.ubuntu.com wily-updates/universe i386 Packages [48.5 kB] 
Get:21 http://archive.ubuntu.com wily-updates/multiverse i386 Packages [6,064 B]
Ign http://toolbelt.heroku.com ./ Translation-en_US
Ign http://toolbelt.heroku.com ./ Translation-en

[Touch-packages] [Bug 1531787] Re: USC crash (error: Cannot access memory at address ...) at usc::SystemCompositor::run (this=0xbfb4a914) at src/system_compositor.cpp:129

2016-01-07 Thread Daniel van Vugt
75 instances and counting of this crash on errors.ubuntu.com.
Interesting to see they're all xenial desktops (amd64 or i386).

** Summary changed:

- 
/usr/sbin/unity-system-compositor:11:get_adjusted_ptr:__cxxabiv1::__gxx_personality_v0:_Unwind_RaiseException:_Unwind_Resume_or_Rethrow:__cxxabiv1::__cxa_rethrow
+ USC crash (error: Cannot access memory at address ...) at 
usc::SystemCompositor::run (this=0xbfb4a914) at src/system_compositor.cpp:129

** Also affects: unity-system-compositor
   Importance: Undecided
   Status: New

** Changed in: unity-system-compositor
   Importance: Undecided => Critical

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

Title:
  USC crash (error: Cannot access memory at address ...) at
  usc::SystemCompositor::run (this=0xbfb4a914) at
  src/system_compositor.cpp:129

Status in Unity System Compositor:
  New
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity-system-compositor.  This problem was most recently
  seen with version 0.2.0+16.04.20151222.1-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/d4b27439a92b91952fee0b16b8251e2b6aa65208
  contains more details.

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

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


[Touch-packages] [Bug 1517597] Re: [regression] mouse pointer support on emulator is broken

2016-01-07 Thread Daniel van Vugt
** Changed in: mir
 Assignee: (unassigned) => Andreas Pokorny (andreas-pokorny)

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

Title:
  [regression] mouse pointer support on emulator is broken

Status in Canonical System Image:
  Incomplete
Status in Mir:
  Confirmed
Status in Mir 0.18 series:
  Confirmed
Status in android package in Ubuntu:
  New
Status in mir package in Ubuntu:
  Confirmed
Status in phablet-tools package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu RTM:
  Confirmed

Bug description:
  STEPS:
  1. Flash with sudo ubuntu-emulator create --channel ubuntu-touch/rc/ubuntu 
rc-test
  2. Wait for it to build
  3. Run with ubuntu-emulator run rc-test
  4. Starts up but the mouse never moves meaning you can't leave the first page 
of the welcome wizard

  EXPECTED:
  I expect the emulator cursor to follow the mouse cursor and be able to click 
on things

  ACTUAL:
  Emulator cursors stay in the top left preventing movement.

  As noted below F6 toggles the input mode.
  The pointer movement is quite slow and jerky.
  You also can no longer initiate an edge swipe even in trackball mode.

  This is a major regression from how the emulator used to perform.

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

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


[Touch-packages] [Bug 1247216] Re: Support for XMPP

2016-01-07 Thread Ruben Maes
Note that at the time of writing the wish for an XMPP client on the uApp
Explorer wishlist
(https://uappexplorer.com/wishlist/5679333d8ee27f8ebbfe9570) has 28
upvotes and no downvotes, which is not that bad.

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

Title:
  Support for XMPP

Status in messaging-app package in Ubuntu:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Triaged

Bug description:
  Hi All,

  basically there are three things that block me to move to Ubuntu
  Touch. A missing spotify app (already in developement :) ), a missing
  mail app (planned for 14.04 :)  ) and finally a missing IM app --
  especially for XMPP.

  Thusly, I propose adding support for XMPP to the messaging-app. It
  already uses telepathy so we should be able to add this functionality.
  I would also be willing to work on this if somebody points me out
  where to start.

  I guess we would have to break this down into several work packages:
  setting up accounts, online/offline handling of friends, choosing
  protocols when composing a message etc. But first I would like to get
  some feedback if you would be okay with such a feature. Maybe it is
  already planned?

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

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


[Touch-packages] [Bug 1285850] Re: interuppting lxc-clone can destroy source container

2016-01-07 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 lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1285850

Title:
  interuppting lxc-clone can destroy source container

Status in lxc:
  Triaged
Status in lxc package in Ubuntu:
  New
Status in lxc source package in Vivid:
  New
Status in lxc source package in Wily:
  New
Status in lxc source package in Xenial:
  New

Bug description:
  ubuntu 13.10, i'm currently scripting lxc-clone to create a dozen
  containers on demand, but if i ctrl-c interuppt the operation, i've
  seen a few cases where it will destroy the source container (using
  snapshots and btrfs)

  $ lxc-clone -s precise-subvolume target-1 -- -S ~/.ssh/id_dsa.pub
  ctrl-c

  the source container's rootfs directory goes missing, and only a
  rootfs.hold file remains in place.

  btrfs subvolume list shows nothing for the missing container rootfs as
  well.

  lxc-version -> 1.0.0.alpha1

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

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


[Touch-packages] [Bug 1529079] Re: Can't start virtual machines after upgrade to Xenial

2016-01-07 Thread RussianNeuroMancer
> > I can add systemd package as affected package again?
> Yes I think that's fair, though it's more likely a bug in libvirt's use of 
> systemd-machined.

Okay, I added systemd package as affected.

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

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

Title:
  Can't start virtual machines after upgrade to Xenial

Status in libvirt package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Can't start virtual machines after upgrade to Xenial.

  On Ubuntu Server 16.04:
  # virsh start testserver
  Cannot set property Before, or unknown property.

  On Kubuntu 16.04:
  Cannot set property Before, or unknown property.
  Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in 
cb_wrapper
  callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/create.py", line 1873, in 
do_install
  guest.start_install(meter=meter)
File "/usr/share/virt-manager/virtinst/guest.py", line 414, in start_install
  noboot)
File "/usr/share/virt-manager/virtinst/guest.py", line 478, in _create_guest
  dom = self.conn.createLinux(start_xml or final_xml, 0)
File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3585, in 
createLinux
  if ret is None:raise libvirtError('virDomainCreateLinux() failed', 
conn=self)
  libvirtError: Cannot set property Before, or unknown property.

  At this moment there is no libvirt or systemd-related error messages in 
syslog when this error appear on the screen (or virsh output). Both systems was 
upgraded from 15.10.
  --- 
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  Package: libvirt (not installed)
  ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.3.3-040303-generic 
root=UUID=a100d974-72cf-44ad-acf8-6ec060b773dd ro rootflags=subvol=@Xenial 
quiet nomdmonddf nomdmonisw
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  Tags:  xenial
  Uname: Linux 4.3.3-040303-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  modified.conffile..etc.libvirt.qemu.networks.default.xml: [modified]
  mtime.conffile..etc.libvirt.qemu.networks.default.xml: 
2015-02-27T11:49:59.773560

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

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


[Touch-packages] [Bug 1524093] Re: dhclient operates on incorrect interface

2016-01-07 Thread Tessa Lau
FYI if anyone is also affected by this bug, I was able to find a
workaround. See the last comment by idallen here:

http://ubuntuforums.org/showthread.php?t=1431860&p=12313662#post12313662

Essentially you want to do this:

* Remove all references to interfaces from the /etc/dhcp/dhclient.conf file
* Create separate configuration files for each interface with the options 
specific to each interface
* In the /etc/network/interfaces file, mark all DHCP interfaces as "manual" 
instead of "dhcp"
* Add a line to /etc/network/interfaces for each DHCP interface to manually 
bring it up using a command line that explicitly specifies its config file

For example, this is one of the stanzas in my /e/n/i file:

allow-hotplug lte0
iface lte0 inet manual
up dhclient -1 -v -cf /etc/dhcp/dhclient-lte0.conf -pf /run/dhclient.lte0.pid 
-lf /var/lib/dhcp/dhclient.lte0.leases lte0
down dhclient -r -cf /etc/dhcp/dhclient-lte0.conf -lf 
/var/lib/dhcp/dhclient.lte0.leases lte0

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

Title:
  dhclient operates on incorrect interface

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  I have a system with two internet connections, both configured using
  DHCP. They are specified in /etc/network/interfaces roughly as
  follows:

  iface lte0 inet dhcp
  iface wlan0 inet dhcp
  wpa-ssid 
  wpa-psk 

  I also have defined custom options for each interface in the
  /etc/dhcp/dhclient.conf file:

  interface "lte0" {
send host-name "hostA";
  }
  interface "wlan0" {
send host-name "hostB";
  }

  When I do "ifup wlan0", the wrong interface is brought up:

  Listening on LPF/lte0/94:b9:b4:18:e5:ce
  Sending on   LPF/lte0/94:b9:b4:18:e5:ce
  Listening on LPF/wlan0/00:26:b6:e1:7c:64
  Sending on   LPF/wlan0/00:26:b6:e1:7c:64
  Sending on   Socket/fallback
  DHCPDISCOVER on lte0 to 255.255.255.255 port 67 interval 3 (xid=0xbb4b7c57)
  DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3 (xid=0xbf50be57)
  DHCPREQUEST of 100.70.63.250 on lte0 to 255.255.255.255 port 67 
(xid=0x577c4bbb)
  DHCPOFFER of 100.70.63.250 from 100.70.63.1
  DHCPACK of 100.70.63.250 from 100.70.63.1
  bound to 100.70.63.250 -- renewal in 270090 seconds.

  Similarly, if I do "ifdown wlan0", both interfaces are released:

  Listening on LPF/lte0/94:b9:b4:18:e5:ce
  Sending on   LPF/lte0/94:b9:b4:18:e5:ce
  Listening on LPF/wlan0/00:26:b6:e1:7c:64
  Sending on   LPF/wlan0/00:26:b6:e1:7c:64
  Sending on   Socket/fallback
  DHCPRELEASE on lte0 to 100.70.63.1 port 67 (xid=0x2f4f2125)
  DHCPRELEASE on wlan0 to 10.78.56.254 port 67 (xid=0x15a5a)

  I expect that ifup/ifdown only operates on the interface specified on
  the command line. Instead they are operating on other interfaces that
  I did not want them to touch.

  I believe the problem is related to this statement in the dhclient man page:
 It is also possible to specify interfaces by name in the dhclient.conf 
file.   If interfaces are  specified  in  this  way,
 then  the client will only configure interfaces that are either 
specified in the configuration file or on the command line,
 and will ignore all other interfaces.

  So it's reading all interfaces from the configuration file and adding
  them to the command line interfaces, and operating on all such
  interfaces. If I remove the interface stanzas from the
  /etc/dhcp/dhclient.conf file, then everything works as expected.

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

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


[Touch-packages] [Bug 1442837] Re: "ifdown wlan0" brings down multiple interfaces, not just the specified one

2016-01-07 Thread Tessa Lau
I've discovered that this is actually a bug (or badly designed
"feature") in the isc-dhcp package.

I upstreamed the bug here: https://bugs.launchpad.net/ubuntu/+source
/isc-dhcp/+bug/1524093

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

Title:
  "ifdown wlan0" brings down multiple interfaces, not just the specified
  one

Status in ifupdown package in Ubuntu:
  New

Bug description:
  I have a server with multiple internet connections using several
  different network interfaces (e.g. wlan0 for wireless and lte0 for an
  LTE dongle). Both are configured in /etc/network/interfaces to use
  DHCP like so:

  allow-hotplug lte0
  iface lte0 inet dhcp

  iface wlan0 inet dhcp
  wpa-ssid MY_NETWORK
  wpa-psk 
  wpa-driver nl80211
  wpa-key-mgmt WPA-PSK

  If both interfaces are up and I try to bring just one of them down
  using "ifdown wlan0" I would expect the other interface to remain up.
  However, this actually brings down both interfaces and does a DHCP
  release on both.

  % sudo ifdown wlan0
  Internet Systems Consortium DHCP Client 4.2.4
  Copyright 2004-2012 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/

  Listening on LPF/lte0/94:b9:b4:0a:c6:e0
  Sending on   LPF/lte0/94:b9:b4:0a:c6:e0
  Listening on LPF/wlan0/80:86:f2:b1:c3:3f
  Sending on   LPF/wlan0/80:86:f2:b1:c3:3f
  Sending on   Socket/fallback
  DHCPRELEASE on lte0 to 100.79.128.1 port 67 (xid=0x33b5bd5b)
  Connection closed.

  This is actually catastrophic for us since we are connecting to the
  server via the lte0 interface, and we have just shut down our access
  route to the server.

  This seems like a bug in ifdown, where it is bringing down the wrong
  interface despite what I told it to do on the command line.

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

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


[Touch-packages] [Bug 1285850] Re: interuppting lxc-clone can destroy source container

2016-01-07 Thread Serge Hallyn
Should also need fix in trusty-backports

The fix will come in 1.1.6.


** Also affects: lxc (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: lxc (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: lxc (Ubuntu Vivid)
   Importance: Undecided
   Status: New

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

Title:
  interuppting lxc-clone can destroy source container

Status in lxc:
  Triaged
Status in lxc package in Ubuntu:
  New
Status in lxc source package in Vivid:
  New
Status in lxc source package in Wily:
  New
Status in lxc source package in Xenial:
  New

Bug description:
  ubuntu 13.10, i'm currently scripting lxc-clone to create a dozen
  containers on demand, but if i ctrl-c interuppt the operation, i've
  seen a few cases where it will destroy the source container (using
  snapshots and btrfs)

  $ lxc-clone -s precise-subvolume target-1 -- -S ~/.ssh/id_dsa.pub
  ctrl-c

  the source container's rootfs directory goes missing, and only a
  rootfs.hold file remains in place.

  btrfs subvolume list shows nothing for the missing container rootfs as
  well.

  lxc-version -> 1.0.0.alpha1

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

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


[Touch-packages] [Bug 1285850] Re: interuppting lxc-clone can destroy source container

2016-01-07 Thread Serge Hallyn
This was fixed by commit 5eea90e8505d9f336bb28379d8575be159fdd2e1, it
was github issue http://github.com/lxc/lxc/issues/694.

It needs to be SRUd somewhat urgently.


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

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

Title:
  interuppting lxc-clone can destroy source container

Status in lxc:
  Triaged
Status in lxc package in Ubuntu:
  New
Status in lxc source package in Vivid:
  New
Status in lxc source package in Wily:
  New
Status in lxc source package in Xenial:
  New

Bug description:
  ubuntu 13.10, i'm currently scripting lxc-clone to create a dozen
  containers on demand, but if i ctrl-c interuppt the operation, i've
  seen a few cases where it will destroy the source container (using
  snapshots and btrfs)

  $ lxc-clone -s precise-subvolume target-1 -- -S ~/.ssh/id_dsa.pub
  ctrl-c

  the source container's rootfs directory goes missing, and only a
  rootfs.hold file remains in place.

  btrfs subvolume list shows nothing for the missing container rootfs as
  well.

  lxc-version -> 1.0.0.alpha1

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

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


[Touch-packages] [Bug 1524093] Re: dhclient operates on incorrect interface

2016-01-07 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: isc-dhcp (Ubuntu)
   Status: New => Confirmed

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

Title:
  dhclient operates on incorrect interface

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  I have a system with two internet connections, both configured using
  DHCP. They are specified in /etc/network/interfaces roughly as
  follows:

  iface lte0 inet dhcp
  iface wlan0 inet dhcp
  wpa-ssid 
  wpa-psk 

  I also have defined custom options for each interface in the
  /etc/dhcp/dhclient.conf file:

  interface "lte0" {
send host-name "hostA";
  }
  interface "wlan0" {
send host-name "hostB";
  }

  When I do "ifup wlan0", the wrong interface is brought up:

  Listening on LPF/lte0/94:b9:b4:18:e5:ce
  Sending on   LPF/lte0/94:b9:b4:18:e5:ce
  Listening on LPF/wlan0/00:26:b6:e1:7c:64
  Sending on   LPF/wlan0/00:26:b6:e1:7c:64
  Sending on   Socket/fallback
  DHCPDISCOVER on lte0 to 255.255.255.255 port 67 interval 3 (xid=0xbb4b7c57)
  DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3 (xid=0xbf50be57)
  DHCPREQUEST of 100.70.63.250 on lte0 to 255.255.255.255 port 67 
(xid=0x577c4bbb)
  DHCPOFFER of 100.70.63.250 from 100.70.63.1
  DHCPACK of 100.70.63.250 from 100.70.63.1
  bound to 100.70.63.250 -- renewal in 270090 seconds.

  Similarly, if I do "ifdown wlan0", both interfaces are released:

  Listening on LPF/lte0/94:b9:b4:18:e5:ce
  Sending on   LPF/lte0/94:b9:b4:18:e5:ce
  Listening on LPF/wlan0/00:26:b6:e1:7c:64
  Sending on   LPF/wlan0/00:26:b6:e1:7c:64
  Sending on   Socket/fallback
  DHCPRELEASE on lte0 to 100.70.63.1 port 67 (xid=0x2f4f2125)
  DHCPRELEASE on wlan0 to 10.78.56.254 port 67 (xid=0x15a5a)

  I expect that ifup/ifdown only operates on the interface specified on
  the command line. Instead they are operating on other interfaces that
  I did not want them to touch.

  I believe the problem is related to this statement in the dhclient man page:
 It is also possible to specify interfaces by name in the dhclient.conf 
file.   If interfaces are  specified  in  this  way,
 then  the client will only configure interfaces that are either 
specified in the configuration file or on the command line,
 and will ignore all other interfaces.

  So it's reading all interfaces from the configuration file and adding
  them to the command line interfaces, and operating on all such
  interfaces. If I remove the interface stanzas from the
  /etc/dhcp/dhclient.conf file, then everything works as expected.

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

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


[Touch-packages] [Bug 1532007] Re: libvirt's apparmor policy prevents starting domain with hugepage-backed memory store

2016-01-07 Thread Seth Arnold
** Changed in: libvirt (Ubuntu)
   Status: Incomplete => Confirmed

** Changed in: apparmor (Ubuntu)
   Status: Incomplete => 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/1532007

Title:
  libvirt's apparmor policy prevents starting domain with hugepage-
  backed memory store

Status in apparmor package in Ubuntu:
  Confirmed
Status in libvirt package in Ubuntu:
  Confirmed

Bug description:
  ---Problem Description---
  After enabling hugepages, unable to start a domain with hugepage-packed 
memory store:

  ~# virsh start ubuntu-14_04
  error: Failed to start domain ubuntu-14_04
  error: internal error: process exited while connecting to monitor: 
2015-07-10T14:26:04.627101Z qemu-system-ppc64le: unable to create backing store 
for hugepages: Permission denied

  ---uname output---
  Linux cipipeln 3.19.0-21-generic #21-Ubuntu SMP Sun Jun 14 19:33:37 UTC 2015 
ppc64le ppc64le ppc64le GNU/Linux
   
   
  ---Steps to Reproduce---
  1. set the sysctl setting for hugepages to 5000
  2. enable huge pages in /etc/default/qemu-kvm
  3. restart qemu-kvm
  4. restart libvirt 
  5. add to guest xml (using virsh edit)
  
 
  
  6. virsh define ubuntu-14_04.xml
  7. virsh start ubuntu-14_04

  
  # grep Huge /proc/meminfo 
  AnonHugePages: 0 kB
  HugePages_Total:5000
  HugePages_Free: 5000
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:  16384 kB

  # cat /etc/default/qemu-kvm 
  # To disable qemu-kvm's page merging feature, set KSM_ENABLED=0 and
  # sudo restart qemu-kvm
  KSM_ENABLED=1
  SLEEP_MILLISECS=200
  # To load the vhost_net module, which in some cases can speed up
  # network performance, set VHOST_NET_ENABLED to 1.
  VHOST_NET_ENABLED=1

  # Set this to 1 if you want hugepages to be available to kvm under
  # /run/hugepages/kvm
  KVM_HUGEPAGES=1

  ==
  File permissions on the hugepages mount dir:

  root@cipipeln:~# ls -lah /dev | grep hugep
  drwxr-xr-x  3 root root   0 Jun 16 12:39 hugepages
  root@cipipeln:~# ls -lah /dev/hugepages/
  total 0
  drwxr-xr-x  3 root root0 Jun 16 12:39 .
  drwxr-xr-x 18 root root 4.9K Jul  8 11:03 ..
  drwxr-xr-x  3 root root0 Jun 16 12:39 libvirt
  root@cipipeln:~# ls -lah /dev/hugepages/libvirt/
  total 0
  drwxr-xr-x 3 root root 0 Jun 16 12:39 .
  drwxr-xr-x 3 root root 0 Jun 16 12:39 ..
  drwxr-xr-x 2 libvirt-qemu kvm  0 Jul  9 18:34 qemu

  ==

  # sysctl -a | grep huge
  vm.hugepages_treat_as_movable = 0
  vm.hugetlb_shm_group = 0
  vm.nr_hugepages = 5000
  vm.nr_hugepages_mempolicy = 5000
  vm.nr_overcommit_hugepages = 0

  ==

  I was able to confirm that running qemu-kvm stand-alone was allocated
  4 hugepages (The number of free huge pages decreased by 4).

  ==
  I also tried:
  - sysctl -w vm.hugetlb_shm_group=X where X was the user id for libvirt, and 
then tried the group id for the kvm group
  - disabling apparmor
  - chmod -R 777 /dev/hugepages
   
  Hi Christy, Are you using apparmor for any specific reason ? If you can 
switch to selinux, it would be convinient for me to debug as I am very 
comfortable with selinux. The issue I see is qemu is not able to create a 
temporary file in /dev/hugepages/libvirt/qemu/qemu_back_mem.ppc_spapr.ram.XXX.

  Can you disable that and try Or confirm if the /dev/hugepages
  directory has relaxed security? I tried relaxing a bit and failed as I
  dont know apparmor well.

  Thanks,
  Shiva

  == Comment: #8 - Christy L. Norman Perez  - 2016-01-07 
11:33:19 ==
  (In reply to comment #7)
  > Hi Christy, Are you using apparmor for any specific reason ? If you can
  > switch to selinux, it would be convinient for me to debug as I am very
  > comfortable with selinux. The issue I see is qemu is not able to create a
  > temporary file in
  > /dev/hugepages/libvirt/qemu/qemu_back_mem.ppc_spapr.ram.XXX.

  Nope, not using apparmor for any reason aside from the fact that it's
  default on Ubuntu.

  > 
  > Can you disable that and try Or confirm if the /dev/hugepages directory has
  > relaxed security? I tried relaxing a bit and failed as I dont know apparmor
  > well. 

  I can't believe I didn't look into this before, but it does look like an 
apparmor issue:
  Jan 07 11:17:17 humphrey kernel: audit: type=1400 audit(1452183437.308:281): 
apparmor="DENIED" operation="mknod" 
profile="libvirt-be593664-727a-4905-bdb8-2eb7ccf85700

  So, here's what I did to get this to work:
  root@humphrey:~# aa-complain 
/etc/apparmor.d/libvirt/libvirt-be593664-727a-4905-bdb8-2eb7ccf85700
  Setting /etc/apparmor.d/libvirt/libvirt-be593664-727a-4905-bdb8-2eb7ccf85700 
to complain mode.

  root@humphrey:~# virsh start bz127508
  Domain bz127508 started

  > 
  > Thanks,
  > Shiva

  I think we should reroute this to apparmor, mirror to Ubuntu, and
  request an updated apparmor policy. This change should be done for
  14.

Re: [Touch-packages] [Bug 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space

2016-01-07 Thread Doug McNutt
Very helpful Mr. Ager-Wick

Its strange that partitions show up as /boot under, somehow under /dev/sda1.
I guess that makes sence but I also have a disk reported as
/dev/sdb1   /media/kit/UNTITLED
which is actually a portable disk tied in by USB connections. (kit is 
another user)
/dev/null/ is about my level of usage for /dev at all. I shall work on that.
Is there, perhaps, something wrong with reporting usage that start with 
/dev?
/dev/dm-0, or perhaps dm-O, shows 143G size and 72G used  and I have no 
idea where or what it's used for. It sounds like I might have a problem 
there.
Currently:
/dev/sda1   236M  144M   80M  65% /boot
which will be OK for a while but I had no idea that it was a partition 
rather than a simple directory. There is a real directory /div/ which 
could also be handling it within the system. I assumed that while 
deleting older entries and it worked with simple rm commands.

On 01/06/2016 09:33 AM, Ronny Ager-Wick wrote:
> @dmcnutt /boot is usually a separate partition, byt default around
> 250MB, which is way too small. Use command "df" to see how much space
> you have left on each partition. if /boot is nearly full, it doesn't
> help if / has loads of space.
>

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

Title:
  update-initramfs should produce a more helpful error when there isn't
  enough  free space

Status in initramfs-tools:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: initramfs-tools

  When generating a new initramfs there is no check for available free
  space, subsequently its possible for update-initramfs to fail due to a
  lack of free space.  This is resulting in package installation
  failures for initramfs-tools.  For example:

  Setting up initramfs-tools (0.98.8ubuntu3) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools ...
  update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic
  dpkg: error processing initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1

  WORKAROUND:

  Remove unused kernels using computer janitor (not in repositories for
  14.04 or later) or manually free space on your partition containing
  the /boot file system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/798414/+subscriptions

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


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

2016-01-07 Thread bugproxy
--- Comment From clnpe...@us.ibm.com 2016-01-07 23:03 EDT---
That was the only one, actually.

I just recreated it just to make sure, so these have a later timestamp:

Jan 07 17:55:48 humphrey audit[71908]: AVC apparmor="DENIED" operation="mknod" 
profile="libvirt-be593664-727a-4905-bdb8-2eb7ccf85700" 
name="/dev/hugepages/libvirt/qemu/qemu_back_mem.ppc_spapr.ram.Aejg6t" pid=71908 
comm="qemu-system-ppc" requested_mask="c" denied_mask="c" fsuid=109 ouid=109
Jan 07 17:55:48 humphrey kernel: audit: type=1400 audit(1452207348.544:338): 
apparmor="DENIED" operation="mknod" 
profile="libvirt-be593664-727a-4905-bdb8-2eb7ccf85700" 
name="/dev/hugepages/libvirt/qemu/qemu_back_mem.ppc_spapr.ram.Aejg6t" pid=71908 
comm="qemu-system-ppc" requested_mask="c" denied_mask="c" fsuid=109 ouid=109

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

Title:
  libvirt's apparmor policy prevents starting domain with hugepage-
  backed memory store

Status in apparmor package in Ubuntu:
  Incomplete
Status in libvirt package in Ubuntu:
  Incomplete

Bug description:
  ---Problem Description---
  After enabling hugepages, unable to start a domain with hugepage-packed 
memory store:

  ~# virsh start ubuntu-14_04
  error: Failed to start domain ubuntu-14_04
  error: internal error: process exited while connecting to monitor: 
2015-07-10T14:26:04.627101Z qemu-system-ppc64le: unable to create backing store 
for hugepages: Permission denied

  ---uname output---
  Linux cipipeln 3.19.0-21-generic #21-Ubuntu SMP Sun Jun 14 19:33:37 UTC 2015 
ppc64le ppc64le ppc64le GNU/Linux
   
   
  ---Steps to Reproduce---
  1. set the sysctl setting for hugepages to 5000
  2. enable huge pages in /etc/default/qemu-kvm
  3. restart qemu-kvm
  4. restart libvirt 
  5. add to guest xml (using virsh edit)
  
 
  
  6. virsh define ubuntu-14_04.xml
  7. virsh start ubuntu-14_04

  
  # grep Huge /proc/meminfo 
  AnonHugePages: 0 kB
  HugePages_Total:5000
  HugePages_Free: 5000
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:  16384 kB

  # cat /etc/default/qemu-kvm 
  # To disable qemu-kvm's page merging feature, set KSM_ENABLED=0 and
  # sudo restart qemu-kvm
  KSM_ENABLED=1
  SLEEP_MILLISECS=200
  # To load the vhost_net module, which in some cases can speed up
  # network performance, set VHOST_NET_ENABLED to 1.
  VHOST_NET_ENABLED=1

  # Set this to 1 if you want hugepages to be available to kvm under
  # /run/hugepages/kvm
  KVM_HUGEPAGES=1

  ==
  File permissions on the hugepages mount dir:

  root@cipipeln:~# ls -lah /dev | grep hugep
  drwxr-xr-x  3 root root   0 Jun 16 12:39 hugepages
  root@cipipeln:~# ls -lah /dev/hugepages/
  total 0
  drwxr-xr-x  3 root root0 Jun 16 12:39 .
  drwxr-xr-x 18 root root 4.9K Jul  8 11:03 ..
  drwxr-xr-x  3 root root0 Jun 16 12:39 libvirt
  root@cipipeln:~# ls -lah /dev/hugepages/libvirt/
  total 0
  drwxr-xr-x 3 root root 0 Jun 16 12:39 .
  drwxr-xr-x 3 root root 0 Jun 16 12:39 ..
  drwxr-xr-x 2 libvirt-qemu kvm  0 Jul  9 18:34 qemu

  ==

  # sysctl -a | grep huge
  vm.hugepages_treat_as_movable = 0
  vm.hugetlb_shm_group = 0
  vm.nr_hugepages = 5000
  vm.nr_hugepages_mempolicy = 5000
  vm.nr_overcommit_hugepages = 0

  ==

  I was able to confirm that running qemu-kvm stand-alone was allocated
  4 hugepages (The number of free huge pages decreased by 4).

  ==
  I also tried:
  - sysctl -w vm.hugetlb_shm_group=X where X was the user id for libvirt, and 
then tried the group id for the kvm group
  - disabling apparmor
  - chmod -R 777 /dev/hugepages
   
  Hi Christy, Are you using apparmor for any specific reason ? If you can 
switch to selinux, it would be convinient for me to debug as I am very 
comfortable with selinux. The issue I see is qemu is not able to create a 
temporary file in /dev/hugepages/libvirt/qemu/qemu_back_mem.ppc_spapr.ram.XXX.

  Can you disable that and try Or confirm if the /dev/hugepages
  directory has relaxed security? I tried relaxing a bit and failed as I
  dont know apparmor well.

  Thanks,
  Shiva

  == Comment: #8 - Christy L. Norman Perez  - 2016-01-07 
11:33:19 ==
  (In reply to comment #7)
  > Hi Christy, Are you using apparmor for any specific reason ? If you can
  > switch to selinux, it would be convinient for me to debug as I am very
  > comfortable with selinux. The issue I see is qemu is not able to create a
  > temporary file in
  > /dev/hugepages/libvirt/qemu/qemu_back_mem.ppc_spapr.ram.XXX.

  Nope, not using apparmor for any reason aside from the fact that it's
  default on Ubuntu.

  > 
  > Can you disable that and try Or confirm if the /dev/hugepages directory has
  > relaxed security? I tried relaxing a bit and failed as I dont know apparmor
  > well. 

  I can't believe I didn't look into this before, but it does look like an 
apparmor issu

[Touch-packages] [Bug 1532007] Re: libvirt's apparmor policy prevents starting domain with hugepage-backed memory store

2016-01-07 Thread Seth Arnold
Christy, can you please include the full relevant DENIED lines from your
logs so that we can best determine which rules need to be added to the
libvirt profiles?

Thanks

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

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

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

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

Title:
  libvirt's apparmor policy prevents starting domain with hugepage-
  backed memory store

Status in apparmor package in Ubuntu:
  Incomplete
Status in libvirt package in Ubuntu:
  Incomplete

Bug description:
  ---Problem Description---
  After enabling hugepages, unable to start a domain with hugepage-packed 
memory store:

  ~# virsh start ubuntu-14_04
  error: Failed to start domain ubuntu-14_04
  error: internal error: process exited while connecting to monitor: 
2015-07-10T14:26:04.627101Z qemu-system-ppc64le: unable to create backing store 
for hugepages: Permission denied

  ---uname output---
  Linux cipipeln 3.19.0-21-generic #21-Ubuntu SMP Sun Jun 14 19:33:37 UTC 2015 
ppc64le ppc64le ppc64le GNU/Linux
   
   
  ---Steps to Reproduce---
  1. set the sysctl setting for hugepages to 5000
  2. enable huge pages in /etc/default/qemu-kvm
  3. restart qemu-kvm
  4. restart libvirt 
  5. add to guest xml (using virsh edit)
  
 
  
  6. virsh define ubuntu-14_04.xml
  7. virsh start ubuntu-14_04

  
  # grep Huge /proc/meminfo 
  AnonHugePages: 0 kB
  HugePages_Total:5000
  HugePages_Free: 5000
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:  16384 kB

  # cat /etc/default/qemu-kvm 
  # To disable qemu-kvm's page merging feature, set KSM_ENABLED=0 and
  # sudo restart qemu-kvm
  KSM_ENABLED=1
  SLEEP_MILLISECS=200
  # To load the vhost_net module, which in some cases can speed up
  # network performance, set VHOST_NET_ENABLED to 1.
  VHOST_NET_ENABLED=1

  # Set this to 1 if you want hugepages to be available to kvm under
  # /run/hugepages/kvm
  KVM_HUGEPAGES=1

  ==
  File permissions on the hugepages mount dir:

  root@cipipeln:~# ls -lah /dev | grep hugep
  drwxr-xr-x  3 root root   0 Jun 16 12:39 hugepages
  root@cipipeln:~# ls -lah /dev/hugepages/
  total 0
  drwxr-xr-x  3 root root0 Jun 16 12:39 .
  drwxr-xr-x 18 root root 4.9K Jul  8 11:03 ..
  drwxr-xr-x  3 root root0 Jun 16 12:39 libvirt
  root@cipipeln:~# ls -lah /dev/hugepages/libvirt/
  total 0
  drwxr-xr-x 3 root root 0 Jun 16 12:39 .
  drwxr-xr-x 3 root root 0 Jun 16 12:39 ..
  drwxr-xr-x 2 libvirt-qemu kvm  0 Jul  9 18:34 qemu

  ==

  # sysctl -a | grep huge
  vm.hugepages_treat_as_movable = 0
  vm.hugetlb_shm_group = 0
  vm.nr_hugepages = 5000
  vm.nr_hugepages_mempolicy = 5000
  vm.nr_overcommit_hugepages = 0

  ==

  I was able to confirm that running qemu-kvm stand-alone was allocated
  4 hugepages (The number of free huge pages decreased by 4).

  ==
  I also tried:
  - sysctl -w vm.hugetlb_shm_group=X where X was the user id for libvirt, and 
then tried the group id for the kvm group
  - disabling apparmor
  - chmod -R 777 /dev/hugepages
   
  Hi Christy, Are you using apparmor for any specific reason ? If you can 
switch to selinux, it would be convinient for me to debug as I am very 
comfortable with selinux. The issue I see is qemu is not able to create a 
temporary file in /dev/hugepages/libvirt/qemu/qemu_back_mem.ppc_spapr.ram.XXX.

  Can you disable that and try Or confirm if the /dev/hugepages
  directory has relaxed security? I tried relaxing a bit and failed as I
  dont know apparmor well.

  Thanks,
  Shiva

  == Comment: #8 - Christy L. Norman Perez  - 2016-01-07 
11:33:19 ==
  (In reply to comment #7)
  > Hi Christy, Are you using apparmor for any specific reason ? If you can
  > switch to selinux, it would be convinient for me to debug as I am very
  > comfortable with selinux. The issue I see is qemu is not able to create a
  > temporary file in
  > /dev/hugepages/libvirt/qemu/qemu_back_mem.ppc_spapr.ram.XXX.

  Nope, not using apparmor for any reason aside from the fact that it's
  default on Ubuntu.

  > 
  > Can you disable that and try Or confirm if the /dev/hugepages directory has
  > relaxed security? I tried relaxing a bit and failed as I dont know apparmor
  > well. 

  I can't believe I didn't look into this before, but it does look like an 
apparmor issue:
  Jan 07 11:17:17 humphrey kernel: audit: type=1400 audit(1452183437.308:281): 
apparmor="DENIED" operation="mknod" 
profile="libvirt-be593664-727a-4905-bdb8-2eb7ccf85700

  So, here's what I did to get this to work:
  root@humphrey:~# aa-complain 
/etc/apparmor.d/libvirt/libvirt-be593664-727a-4905-bdb8-2eb7ccf85700
  Setting /etc/apparmor.d/libvirt/libvirt-be593664-727a-4905-bdb8-2eb7ccf85700 
to complain mode

[Touch-packages] [Bug 1532017] [NEW] No option to suspend when power critically low; hibernate option greyed out

2016-01-07 Thread Teo
Public bug reported:

(no idea whether this is the right package)

In Power Settings, under "on battery" and "when power is critically
low", the only available option is "Power Off". The "Hibernate" option
is greyed out, and the option "Suspend" doesn't even exist, which is
completely stupid.

Maybe hibernation is greyed out for the same reason why it's not available in 
the shutdown menu, that is, because it's unreliable as hell.
Besides the fact that it's about time to fix it, given we have already reached 
W in the alphabet of versions, anyway, since most of the time it works, the 
option should be available with a warning that it may fail to resume, rather 
than completely unavailable.

Regarding the "Suspend" option, it's simply stupid that it's not
available. I know, suspend requires a minimum amount of power. But the
solution to that is pretty obvious: if the selected choice is to
suspend, then use a slightly higher threshold for triggering suspension.
And if while suspended the power goes below the lower critical threshold
for keeping suspension, then it should wake up and hibernate, or turn
off (there should be an additional option for this).

I remember a few versions ago the option to suspend on low power did
exist, and what happened was that the system started to suspend,
immediately wake up, suspend again, and so on forever until the power
was too low and it just hard-powered off. Now, I understand that was
pathetic, but the new behavior is no solution. Also this proves that
waking up when power reaches critical level while suspended is possible.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: powermgmt-base 1.31+nmu1
ProcVersionSignature: Ubuntu 3.19.0-43.49-generic 3.19.8-ckt10
Uname: Linux 3.19.0-43-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.17.2-0ubuntu1.8
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Jan  7 23:31:53 2016
Dependencies:

InstallationDate: Installed on 2013-10-11 (818 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
PackageArchitecture: all
SourcePackage: powermgmt-base
UpgradeStatus: Upgraded to vivid on 2015-08-15 (145 days ago)

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


** Tags: amd64 apport-bug vivid

** Attachment added: "Screenshot from 2016-01-07 23:34:13.png"
   
https://bugs.launchpad.net/bugs/1532017/+attachment/4545898/+files/Screenshot%20from%202016-01-07%2023%3A34%3A13.png

** Description changed:

  (no idea whether this is the right package)
  
  In Power Settings, under "on battery" and "when power is critically
  low", the only available option is "Power Off". The "Hibernate" option
  is greyed out, and the option "Suspend" doesn't even exist, which is
  completely stupid.
  
- Maybe hibernation is greyed out for the same reason why it's not available in 
the shutdown menu, that is, because it's unreliable as hell. 
+ Maybe hibernation is greyed out for the same reason why it's not available in 
the shutdown menu, that is, because it's unreliable as hell.
  Besides the fact that it's about time to fix it, given we have already 
reached W in the alphabet of versions, anyway, since most of the time it works, 
the option should be available with a warning that it may fail to resume, 
rather than completely unavailable.
  
  Regarding the "Suspend" option, it's simply stupid that it's not
  available. I know, suspend requires a minimum amount of power. But the
  solution to that is pretty obvious: if the selected choice is to
  suspend, then use a slightly higher threshold for triggering suspension.
  And if while suspended the power goes below the lower critical threshold
  for keeping suspension, then it should wake up and hibernate, or turn
  off (there should be an additional option for this).
  
  I remember a few versions ago the option to suspend on low power did
  exist, and what happened was that the system started to suspend,
  immediately wake up, suspend again, and so on forever until the power
  was too low and it just hard-powered off. Now, I understand that was
- pathetic, but the new behavior is no solution.
+ pathetic, but the new behavior is no solution. Also this proves that
+ waking up when power reaches critical level while suspended is possible.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: powermgmt-base 1.31+nmu1
  ProcVersionSignature: Ubuntu 3.19.0-43.49-generic 3.19.8-ckt10
  Uname: Linux 3.19.0-43-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jan  7 23:31:53 2016
  Dependencies:
-  
+ 
  InstallationDate: Installed on 2013-10-11 (818 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  SourcePackage: powermgmt-base
  UpgradeStatus: Upgraded to vivid on 2015-08-15 (145 days ago)

-- 
You received this bug notification because you are a member of Ubuntu

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

2016-01-07 Thread bugproxy
--- Comment From cha...@us.ibm.com 2016-01-07 22:36 EDT---
Some clarification is in order. The host was running 15.04 and the client that 
was to be started (but failed due to the policy on the host) was using 14.04. 
14.04 was not used as the host and it is unknown whether or not it has the same 
issue.

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

Title:
  libvirt's apparmor policy prevents starting domain with hugepage-
  backed memory store

Status in apparmor package in Ubuntu:
  Incomplete

Bug description:
  ---Problem Description---
  After enabling hugepages, unable to start a domain with hugepage-packed 
memory store:

  ~# virsh start ubuntu-14_04
  error: Failed to start domain ubuntu-14_04
  error: internal error: process exited while connecting to monitor: 
2015-07-10T14:26:04.627101Z qemu-system-ppc64le: unable to create backing store 
for hugepages: Permission denied

  ---uname output---
  Linux cipipeln 3.19.0-21-generic #21-Ubuntu SMP Sun Jun 14 19:33:37 UTC 2015 
ppc64le ppc64le ppc64le GNU/Linux
   
   
  ---Steps to Reproduce---
  1. set the sysctl setting for hugepages to 5000
  2. enable huge pages in /etc/default/qemu-kvm
  3. restart qemu-kvm
  4. restart libvirt 
  5. add to guest xml (using virsh edit)
  
 
  
  6. virsh define ubuntu-14_04.xml
  7. virsh start ubuntu-14_04

  
  # grep Huge /proc/meminfo 
  AnonHugePages: 0 kB
  HugePages_Total:5000
  HugePages_Free: 5000
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:  16384 kB

  # cat /etc/default/qemu-kvm 
  # To disable qemu-kvm's page merging feature, set KSM_ENABLED=0 and
  # sudo restart qemu-kvm
  KSM_ENABLED=1
  SLEEP_MILLISECS=200
  # To load the vhost_net module, which in some cases can speed up
  # network performance, set VHOST_NET_ENABLED to 1.
  VHOST_NET_ENABLED=1

  # Set this to 1 if you want hugepages to be available to kvm under
  # /run/hugepages/kvm
  KVM_HUGEPAGES=1

  ==
  File permissions on the hugepages mount dir:

  root@cipipeln:~# ls -lah /dev | grep hugep
  drwxr-xr-x  3 root root   0 Jun 16 12:39 hugepages
  root@cipipeln:~# ls -lah /dev/hugepages/
  total 0
  drwxr-xr-x  3 root root0 Jun 16 12:39 .
  drwxr-xr-x 18 root root 4.9K Jul  8 11:03 ..
  drwxr-xr-x  3 root root0 Jun 16 12:39 libvirt
  root@cipipeln:~# ls -lah /dev/hugepages/libvirt/
  total 0
  drwxr-xr-x 3 root root 0 Jun 16 12:39 .
  drwxr-xr-x 3 root root 0 Jun 16 12:39 ..
  drwxr-xr-x 2 libvirt-qemu kvm  0 Jul  9 18:34 qemu

  ==

  # sysctl -a | grep huge
  vm.hugepages_treat_as_movable = 0
  vm.hugetlb_shm_group = 0
  vm.nr_hugepages = 5000
  vm.nr_hugepages_mempolicy = 5000
  vm.nr_overcommit_hugepages = 0

  ==

  I was able to confirm that running qemu-kvm stand-alone was allocated
  4 hugepages (The number of free huge pages decreased by 4).

  ==
  I also tried:
  - sysctl -w vm.hugetlb_shm_group=X where X was the user id for libvirt, and 
then tried the group id for the kvm group
  - disabling apparmor
  - chmod -R 777 /dev/hugepages
   
  Hi Christy, Are you using apparmor for any specific reason ? If you can 
switch to selinux, it would be convinient for me to debug as I am very 
comfortable with selinux. The issue I see is qemu is not able to create a 
temporary file in /dev/hugepages/libvirt/qemu/qemu_back_mem.ppc_spapr.ram.XXX.

  Can you disable that and try Or confirm if the /dev/hugepages
  directory has relaxed security? I tried relaxing a bit and failed as I
  dont know apparmor well.

  Thanks,
  Shiva

  == Comment: #8 - Christy L. Norman Perez  - 2016-01-07 
11:33:19 ==
  (In reply to comment #7)
  > Hi Christy, Are you using apparmor for any specific reason ? If you can
  > switch to selinux, it would be convinient for me to debug as I am very
  > comfortable with selinux. The issue I see is qemu is not able to create a
  > temporary file in
  > /dev/hugepages/libvirt/qemu/qemu_back_mem.ppc_spapr.ram.XXX.

  Nope, not using apparmor for any reason aside from the fact that it's
  default on Ubuntu.

  > 
  > Can you disable that and try Or confirm if the /dev/hugepages directory has
  > relaxed security? I tried relaxing a bit and failed as I dont know apparmor
  > well. 

  I can't believe I didn't look into this before, but it does look like an 
apparmor issue:
  Jan 07 11:17:17 humphrey kernel: audit: type=1400 audit(1452183437.308:281): 
apparmor="DENIED" operation="mknod" 
profile="libvirt-be593664-727a-4905-bdb8-2eb7ccf85700

  So, here's what I did to get this to work:
  root@humphrey:~# aa-complain 
/etc/apparmor.d/libvirt/libvirt-be593664-727a-4905-bdb8-2eb7ccf85700
  Setting /etc/apparmor.d/libvirt/libvirt-be593664-727a-4905-bdb8-2eb7ccf85700 
to complain mode.

  root@humphrey:~# virsh start bz127508
  Domain bz127508 started

  > 
  > Thanks,
  > Shiva

  I think we should 

[Touch-packages] [Bug 1532007] Re: libvirt's apparmor policy prevents starting domain with hugepage-backed memory store

2016-01-07 Thread Luciano Chavez
** Package changed: ubuntu => apparmor (Ubuntu)

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

Title:
  libvirt's apparmor policy prevents starting domain with hugepage-
  backed memory store

Status in apparmor package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  After enabling hugepages, unable to start a domain with hugepage-packed 
memory store:

  ~# virsh start ubuntu-14_04
  error: Failed to start domain ubuntu-14_04
  error: internal error: process exited while connecting to monitor: 
2015-07-10T14:26:04.627101Z qemu-system-ppc64le: unable to create backing store 
for hugepages: Permission denied

  ---uname output---
  Linux cipipeln 3.19.0-21-generic #21-Ubuntu SMP Sun Jun 14 19:33:37 UTC 2015 
ppc64le ppc64le ppc64le GNU/Linux
   
   
  ---Steps to Reproduce---
  1. set the sysctl setting for hugepages to 5000
  2. enable huge pages in /etc/default/qemu-kvm
  3. restart qemu-kvm
  4. restart libvirt 
  5. add to guest xml (using virsh edit)
  
 
  
  6. virsh define ubuntu-14_04.xml
  7. virsh start ubuntu-14_04

  
  # grep Huge /proc/meminfo 
  AnonHugePages: 0 kB
  HugePages_Total:5000
  HugePages_Free: 5000
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:  16384 kB

  # cat /etc/default/qemu-kvm 
  # To disable qemu-kvm's page merging feature, set KSM_ENABLED=0 and
  # sudo restart qemu-kvm
  KSM_ENABLED=1
  SLEEP_MILLISECS=200
  # To load the vhost_net module, which in some cases can speed up
  # network performance, set VHOST_NET_ENABLED to 1.
  VHOST_NET_ENABLED=1

  # Set this to 1 if you want hugepages to be available to kvm under
  # /run/hugepages/kvm
  KVM_HUGEPAGES=1

  ==
  File permissions on the hugepages mount dir:

  root@cipipeln:~# ls -lah /dev | grep hugep
  drwxr-xr-x  3 root root   0 Jun 16 12:39 hugepages
  root@cipipeln:~# ls -lah /dev/hugepages/
  total 0
  drwxr-xr-x  3 root root0 Jun 16 12:39 .
  drwxr-xr-x 18 root root 4.9K Jul  8 11:03 ..
  drwxr-xr-x  3 root root0 Jun 16 12:39 libvirt
  root@cipipeln:~# ls -lah /dev/hugepages/libvirt/
  total 0
  drwxr-xr-x 3 root root 0 Jun 16 12:39 .
  drwxr-xr-x 3 root root 0 Jun 16 12:39 ..
  drwxr-xr-x 2 libvirt-qemu kvm  0 Jul  9 18:34 qemu

  ==

  # sysctl -a | grep huge
  vm.hugepages_treat_as_movable = 0
  vm.hugetlb_shm_group = 0
  vm.nr_hugepages = 5000
  vm.nr_hugepages_mempolicy = 5000
  vm.nr_overcommit_hugepages = 0

  ==

  I was able to confirm that running qemu-kvm stand-alone was allocated
  4 hugepages (The number of free huge pages decreased by 4).

  ==
  I also tried:
  - sysctl -w vm.hugetlb_shm_group=X where X was the user id for libvirt, and 
then tried the group id for the kvm group
  - disabling apparmor
  - chmod -R 777 /dev/hugepages
   
  Hi Christy, Are you using apparmor for any specific reason ? If you can 
switch to selinux, it would be convinient for me to debug as I am very 
comfortable with selinux. The issue I see is qemu is not able to create a 
temporary file in /dev/hugepages/libvirt/qemu/qemu_back_mem.ppc_spapr.ram.XXX.

  Can you disable that and try Or confirm if the /dev/hugepages
  directory has relaxed security? I tried relaxing a bit and failed as I
  dont know apparmor well.

  Thanks,
  Shiva

  == Comment: #8 - Christy L. Norman Perez  - 2016-01-07 
11:33:19 ==
  (In reply to comment #7)
  > Hi Christy, Are you using apparmor for any specific reason ? If you can
  > switch to selinux, it would be convinient for me to debug as I am very
  > comfortable with selinux. The issue I see is qemu is not able to create a
  > temporary file in
  > /dev/hugepages/libvirt/qemu/qemu_back_mem.ppc_spapr.ram.XXX.

  Nope, not using apparmor for any reason aside from the fact that it's
  default on Ubuntu.

  > 
  > Can you disable that and try Or confirm if the /dev/hugepages directory has
  > relaxed security? I tried relaxing a bit and failed as I dont know apparmor
  > well. 

  I can't believe I didn't look into this before, but it does look like an 
apparmor issue:
  Jan 07 11:17:17 humphrey kernel: audit: type=1400 audit(1452183437.308:281): 
apparmor="DENIED" operation="mknod" 
profile="libvirt-be593664-727a-4905-bdb8-2eb7ccf85700

  So, here's what I did to get this to work:
  root@humphrey:~# aa-complain 
/etc/apparmor.d/libvirt/libvirt-be593664-727a-4905-bdb8-2eb7ccf85700
  Setting /etc/apparmor.d/libvirt/libvirt-be593664-727a-4905-bdb8-2eb7ccf85700 
to complain mode.

  root@humphrey:~# virsh start bz127508
  Domain bz127508 started

  > 
  > Thanks,
  > Shiva

  I think we should reroute this to apparmor, mirror to Ubuntu, and
  request an updated apparmor policy. This change should be done for
  14.04 and applicable releases after.

  Thanks for the suggestion, Shiva!

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

[Touch-packages] [Bug 164640]

2016-01-07 Thread Zhou Yi Chao
I am trying to enable subpixel rendering on poppler and I found my
rendering result is suboptimal.  After gdbing into cairo, I am surprise
that cairo is still using the legacy filter as the "default".  To the
the situation even worse, cairo removed the interfaces to set the
lcdfiler (cairo_font_options_set_lcd_filter) because "they are too
specific to FreeType".

Well, maybe that is true.  But now how can I use the real Freetype
default filter (FIR5) in the newest cairo without pathcing it?  I think
maybe manually set a FcPattern is OK but I really do not want to
learn/invoke/rely Fontconfig just for setting a filter that should be
default.

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

Title:
  Build Firefox 3 against a subpixel-patched cairo

Status in Fontconfig:
  Fix Released
Status in libcairo:
  Confirmed
Status in fontconfig package in Ubuntu:
  Fix Released
Status in libcairo package in Ubuntu:
  Fix Released
Status in xulrunner-1.9 package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: firefox-3.0

  In Ubuntu 7.10 and newer, Firefox 3.0 looks out of place with subpixel
  rendering enabled, due to the fact that it uses an unpatched, bundled
  version of Cairo.

  The patch should be ported to Cairo 1.5 and applied in the firefox-3.0
  package.

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

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


[Touch-packages] [Bug 1532007] [NEW] libvirt's apparmor policy prevents starting domain with hugepage-backed memory store

2016-01-07 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

---Problem Description---
After enabling hugepages, unable to start a domain with hugepage-packed memory 
store:

~# virsh start ubuntu-14_04
error: Failed to start domain ubuntu-14_04
error: internal error: process exited while connecting to monitor: 
2015-07-10T14:26:04.627101Z qemu-system-ppc64le: unable to create backing store 
for hugepages: Permission denied
  
---uname output---
Linux cipipeln 3.19.0-21-generic #21-Ubuntu SMP Sun Jun 14 19:33:37 UTC 2015 
ppc64le ppc64le ppc64le GNU/Linux
 
 
---Steps to Reproduce---
1. set the sysctl setting for hugepages to 5000
2. enable huge pages in /etc/default/qemu-kvm
3. restart qemu-kvm
4. restart libvirt 
5. add to guest xml (using virsh edit)

   

6. virsh define ubuntu-14_04.xml
7. virsh start ubuntu-14_04


# grep Huge /proc/meminfo 
AnonHugePages: 0 kB
HugePages_Total:5000
HugePages_Free: 5000
HugePages_Rsvd:0
HugePages_Surp:0
Hugepagesize:  16384 kB

# cat /etc/default/qemu-kvm 
# To disable qemu-kvm's page merging feature, set KSM_ENABLED=0 and
# sudo restart qemu-kvm
KSM_ENABLED=1
SLEEP_MILLISECS=200
# To load the vhost_net module, which in some cases can speed up
# network performance, set VHOST_NET_ENABLED to 1.
VHOST_NET_ENABLED=1

# Set this to 1 if you want hugepages to be available to kvm under
# /run/hugepages/kvm
KVM_HUGEPAGES=1

==
File permissions on the hugepages mount dir:

root@cipipeln:~# ls -lah /dev | grep hugep
drwxr-xr-x  3 root root   0 Jun 16 12:39 hugepages
root@cipipeln:~# ls -lah /dev/hugepages/
total 0
drwxr-xr-x  3 root root0 Jun 16 12:39 .
drwxr-xr-x 18 root root 4.9K Jul  8 11:03 ..
drwxr-xr-x  3 root root0 Jun 16 12:39 libvirt
root@cipipeln:~# ls -lah /dev/hugepages/libvirt/
total 0
drwxr-xr-x 3 root root 0 Jun 16 12:39 .
drwxr-xr-x 3 root root 0 Jun 16 12:39 ..
drwxr-xr-x 2 libvirt-qemu kvm  0 Jul  9 18:34 qemu

==

# sysctl -a | grep huge
vm.hugepages_treat_as_movable = 0
vm.hugetlb_shm_group = 0
vm.nr_hugepages = 5000
vm.nr_hugepages_mempolicy = 5000
vm.nr_overcommit_hugepages = 0

==

I was able to confirm that running qemu-kvm stand-alone was allocated 4
hugepages (The number of free huge pages decreased by 4).

==
I also tried:
- sysctl -w vm.hugetlb_shm_group=X where X was the user id for libvirt, and 
then tried the group id for the kvm group
- disabling apparmor
- chmod -R 777 /dev/hugepages
 
Hi Christy, Are you using apparmor for any specific reason ? If you can switch 
to selinux, it would be convinient for me to debug as I am very comfortable 
with selinux. The issue I see is qemu is not able to create a temporary file in 
/dev/hugepages/libvirt/qemu/qemu_back_mem.ppc_spapr.ram.XXX.

Can you disable that and try Or confirm if the /dev/hugepages directory
has relaxed security? I tried relaxing a bit and failed as I dont know
apparmor well.

Thanks,
Shiva

== Comment: #8 - Christy L. Norman Perez  - 2016-01-07 
11:33:19 ==
(In reply to comment #7)
> Hi Christy, Are you using apparmor for any specific reason ? If you can
> switch to selinux, it would be convinient for me to debug as I am very
> comfortable with selinux. The issue I see is qemu is not able to create a
> temporary file in
> /dev/hugepages/libvirt/qemu/qemu_back_mem.ppc_spapr.ram.XXX.

Nope, not using apparmor for any reason aside from the fact that it's
default on Ubuntu.

> 
> Can you disable that and try Or confirm if the /dev/hugepages directory has
> relaxed security? I tried relaxing a bit and failed as I dont know apparmor
> well. 

I can't believe I didn't look into this before, but it does look like an 
apparmor issue:
Jan 07 11:17:17 humphrey kernel: audit: type=1400 audit(1452183437.308:281): 
apparmor="DENIED" operation="mknod" 
profile="libvirt-be593664-727a-4905-bdb8-2eb7ccf85700

So, here's what I did to get this to work:
root@humphrey:~# aa-complain 
/etc/apparmor.d/libvirt/libvirt-be593664-727a-4905-bdb8-2eb7ccf85700
Setting /etc/apparmor.d/libvirt/libvirt-be593664-727a-4905-bdb8-2eb7ccf85700 to 
complain mode.

root@humphrey:~# virsh start bz127508
Domain bz127508 started

> 
> Thanks,
> Shiva

I think we should reroute this to apparmor, mirror to Ubuntu, and
request an updated apparmor policy. This change should be done for 14.04
and applicable releases after.

Thanks for the suggestion, Shiva!

** Affects: apparmor (Ubuntu)
 Importance: Undecided
 Assignee: Taco Screen team (taco-screen-team)
 Status: New


** Tags: architecture-ppc64le bugnameltc-127508 severity-high 
targetmilestone-inin1504
-- 
libvirt's apparmor policy prevents starting domain with hugepage-backed memory 
store
https://bugs.launchpad.net/bugs/1532007
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to apparmor in Ubuntu.

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

[Touch-packages] [Bug 1339778] Re: Plugging in Logitech H340 USB headset breaks mouse click behaviour

2016-01-07 Thread Izz Noland
Can this please be re-opened?  I have started experiencing the exact
same issue with the exact same headset.

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

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

Title:
  Plugging in Logitech H340 USB headset breaks mouse click behaviour

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu: 14.04 LTS
  xorg: 1:7.7+1ubuntu8

  Expected: Mouse behaviour should be unaffected when a USB headset is
  plugged in.

  What happened instead:

  When a Logitech H340 USB headset is plugged in the mouse stops
  behaving correctly. The primary button appears to be down all the
  time. Programs fail to respond to clicks from the mouse (so the
  window-focus cannot be changed). The tracking of  X-Y coordinates
  seems to be fine. (The information reported by "ubuntu-bug xorg" was
  collected with the headset plugged in.)

  I tested this behaviour with Firefox, GNOME Terminal, and Nautilus as
  the primary window. In the case of Nautilus the icon under the mouse
  cursor is selected, and moves with the mouse cursor. In the case of
  the other two programs text is selected when the mouse moves.

  I see the same behaviour when the mouse (a Logitec also) is unplugged
  and the inbuilt trackpad is used to move the mouse cursor. For
  completeness I unplugged the mouse and keyboard, so the headset was
  the only device connected to the external USB ports and I saw the same
  behaviour, with the primary button appearing to be down.

  This problem appears to be similar to the issue reported with the Logitech 
G930 headset. However, the H340 is a comparatively simple headset as it is 
wired and lacks any volume buttons, nor does it have a mute.
  
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1155819

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,workarounds,scale,expo,ezoom]
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Wed Jul  9 08:41:54 2014
  DistUpgraded: 2014-07-06 17:47:29,838 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.10, 3.11.0-24-generic, x86_64: installed
   virtualbox, 4.3.10, 3.13.0-30-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:1657]
   Advanced Micro Devices, Inc. [AMD/ATI] Whistler [Radeon HD 6730M/6770M/7690M 
XT] [1002:6740] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2011-08-15 (1059 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic 
root=UUID=1a802fd8-d29f-436f-9a48-75d174a47c13 ro acpi_osi=Linux quiet splash 
acpi_backlight=vendor vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2014-07-07 (2 days ago)
  dmi.bios.date: 10/05/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.1B
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1657
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 10.31
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1B:bd10/05/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr05951024471020100:rvnHewlett-Packard:rn1657:rvr10.31:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.version: 05951024471020100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Tue Jul  

[Touch-packages] [Bug 1337873] Re: Precise, Trusty, Utopic - ifupdown initialization problems caused by race condition

2016-01-07 Thread Brian Murray
Hello Rafael, or anyone else affected,

Accepted ifenslave into trusty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/ifenslave/2.4ubuntu1.2 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: ifenslave (Ubuntu Trusty)
   Status: In Progress => Fix Committed

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

Title:
  Precise, Trusty, Utopic - ifupdown initialization problems caused by
  race condition

Status in ifenslave package in Ubuntu:
  Fix Released
Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifenslave source package in Precise:
  Won't Fix
Status in ifupdown source package in Precise:
  Won't Fix
Status in ifenslave source package in Trusty:
  Fix Committed
Status in ifupdown source package in Trusty:
  Fix Committed
Status in ifenslave source package in Vivid:
  Fix Released
Status in ifupdown source package in Vivid:
  Won't Fix
Status in ifenslave source package in Wily:
  Fix Released
Status in ifupdown source package in Wily:
  In Progress
Status in ifupdown package in Debian:
  New

Bug description:
  [Impact]

   * Lack of proper synchronization in ifupdown causes a race condition
  resulting in occasional incorrect network interface initialization
  (e.g. in bonding case - wrong bonding settings, network unavailable
  because slave<->master interfaces initialization order was wrong

   * This is very annoying in case of large deployments (e.g. when
  bringing up 1000 machines it is almost guaranteed that at least a few
  of them will end up with network down).

   * It has been fixed by introducing hierarchical and per-interface
  locking mechanism ensuring the right order (along with the correct
  order in the /e/n/interfaces file) of initialization

  [Test Case]

   1. Create a VM with bonding configured with at least 2 slave interfaces.
   2. Reboot.
   3. If all interfaces are up - go to 2.

  [Regression Potential]

   * This change has been introduced upstream in Debian.
   * It does not require any config changes to existing installations.

  [Other Info]

  Original bug description:

  * please consider my bonding examples are using eth1 and eth2 as slave
   interfaces.

  ifupdown some race conditions explained bellow. ifenslave does not
  behave well with sysv networking and upstart network-interface scripts
  running together.

  
  case 1)
  (a) ifup eth0 (b) ifup -a for eth0
  -
  1-1. Lock ifstate.lock file.
    1-1. Wait for locking ifstate.lock
    file.
  1-2. Read ifstate file to check
   the target NIC.
  1-3. close(=release) ifstate.lock
   file.
  1-4. Judge that the target NIC
   isn't processed.
    1-2. Read ifstate file to check
     the target NIC.
    1-3. close(=release) ifstate.lock
     file.
    1-4. Judge that the target NIC
     isn't processed.
  2. Lock and update ifstate file.
     Release the lock.
    2. Lock and update ifstate file.
   Release the lock.
  !!!

  to be explained

  !!!
  case 2)
  (a) ifenslave of eth0  (b) ifenslave of eth0
  --
  3. Execute ifenslave of eth0.  3. Execute ifenslave of eth0.
  4. Link down the target NIC.
  5. Write NIC id to
     /sys/class/net/bond0/bonding
     /slaves then NIC gets up
    4. Link down the target NIC.
    5. Fails to write NIC id to
   /sys/class/net/bond0/bonding/
   slaves it is already written.
  !!!

  #

   My setup:

  root@provisioned:~# cat

[Touch-packages] [Bug 1337873] Re: Precise, Trusty, Utopic - ifupdown initialization problems caused by race condition

2016-01-07 Thread Brian Murray
Hello Rafael, or anyone else affected,

Accepted ifupdown into trusty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/ifupdown/0.7.47.2ubuntu4.2 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: ifupdown (Ubuntu Trusty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

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

Title:
  Precise, Trusty, Utopic - ifupdown initialization problems caused by
  race condition

Status in ifenslave package in Ubuntu:
  Fix Released
Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifenslave source package in Precise:
  Won't Fix
Status in ifupdown source package in Precise:
  Won't Fix
Status in ifenslave source package in Trusty:
  Fix Committed
Status in ifupdown source package in Trusty:
  Fix Committed
Status in ifenslave source package in Vivid:
  Fix Released
Status in ifupdown source package in Vivid:
  Won't Fix
Status in ifenslave source package in Wily:
  Fix Released
Status in ifupdown source package in Wily:
  In Progress
Status in ifupdown package in Debian:
  New

Bug description:
  [Impact]

   * Lack of proper synchronization in ifupdown causes a race condition
  resulting in occasional incorrect network interface initialization
  (e.g. in bonding case - wrong bonding settings, network unavailable
  because slave<->master interfaces initialization order was wrong

   * This is very annoying in case of large deployments (e.g. when
  bringing up 1000 machines it is almost guaranteed that at least a few
  of them will end up with network down).

   * It has been fixed by introducing hierarchical and per-interface
  locking mechanism ensuring the right order (along with the correct
  order in the /e/n/interfaces file) of initialization

  [Test Case]

   1. Create a VM with bonding configured with at least 2 slave interfaces.
   2. Reboot.
   3. If all interfaces are up - go to 2.

  [Regression Potential]

   * This change has been introduced upstream in Debian.
   * It does not require any config changes to existing installations.

  [Other Info]

  Original bug description:

  * please consider my bonding examples are using eth1 and eth2 as slave
   interfaces.

  ifupdown some race conditions explained bellow. ifenslave does not
  behave well with sysv networking and upstart network-interface scripts
  running together.

  
  case 1)
  (a) ifup eth0 (b) ifup -a for eth0
  -
  1-1. Lock ifstate.lock file.
    1-1. Wait for locking ifstate.lock
    file.
  1-2. Read ifstate file to check
   the target NIC.
  1-3. close(=release) ifstate.lock
   file.
  1-4. Judge that the target NIC
   isn't processed.
    1-2. Read ifstate file to check
     the target NIC.
    1-3. close(=release) ifstate.lock
     file.
    1-4. Judge that the target NIC
     isn't processed.
  2. Lock and update ifstate file.
     Release the lock.
    2. Lock and update ifstate file.
   Release the lock.
  !!!

  to be explained

  !!!
  case 2)
  (a) ifenslave of eth0  (b) ifenslave of eth0
  --
  3. Execute ifenslave of eth0.  3. Execute ifenslave of eth0.
  4. Link down the target NIC.
  5. Write NIC id to
     /sys/class/net/bond0/bonding
     /slaves then NIC gets up
    4. Link down the target NIC.
    5. Fails to write NIC id to
   /sys/class/net/bond0/bonding/
   slaves it is already written.
  !!!

  #

  ###

[Touch-packages] [Bug 1531925] Re: bluetoothd crash with BTLE keyboard

2016-01-07 Thread Pat McGowan
** Attachment added: "bluetoothd.log"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1531925/+attachment/4545874/+files/bluetoothd.log

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

Title:
  bluetoothd crash with BTLE keyboard

Status in bluez package in Ubuntu:
  New

Bug description:
  Trying to pair this device and bluetoothd crashed on my Wily laptop
  and the N4 running latest proposed

  build number: 107
  device name: mako
  channel: ubuntu-touch/rc-proposed/ubuntu-pd
  last update: 2016-01-07 11:30:20
  version version: 107
  version ubuntu: 20160107
  version device: 20150911
  version custom: 20150929-2-vivid

  
  The device is a Logitech keyboard with an integrated trackpad.

  Device DF:08:A9:A0:13:91
   Name: K830
   Alias: K830
   Appearance: 0x03c1
   Icon: input-keyboard
   Paired: no
   Trusted: no
   Blocked: no
   Connected: no
   LegacyPairing: no
   UUID: Human Interface Device(1812--1000-8000-00805f9b34fb)
   RSSI: -43

  The device would come and go in the devices list from bluetoothctl
  A manual scan would bring it back
  I then tried to manually pair and it failed with
  Failed to pair: org.freedesktop.DBus.Error.NoReply

  On the latop dmesg reports
  [357895.395029] traps: bluetoothd[790] general protection ip:56419e2c0306 
sp:7ffefd2b6760 error:0 in bluetoothd[56419e217000+105000]

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

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


[Touch-packages] [Bug 1531268] Re: Wizard does not change user password if one is pre-set

2016-01-07 Thread Michael Terry
** Changed in: unity8 (Ubuntu)
   Status: Incomplete => In Progress

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

Title:
  Wizard does not change user password if one is pre-set

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Whatever is selected (swipe, passcode, password) during the wizard is
  not set and the default code of  is required

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

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


[Touch-packages] [Bug 1531989] [NEW] MAKEFILE_LIST no longer correct

2016-01-07 Thread James
Public bug reported:

the version of make has what appears to be a broken for the
MAKEFILE_LIST macro.

This is commonly used to get the currently loaded makefile.

However for some reason in this distribution the variable is not
behaving as it should be.

>From https://www.gnu.org/software/make/manual/html_node/Special-
Variables.html

MAKEFILE_LIST

Contains the name of each makefile that is parsed by make, in the
order in which it was parsed. The name is appended just before make
begins to parse the makefile. Thus, if the first thing a makefile does
is examine the last word in this variable, it will be the name of the
current makefile. Once the current makefile has used include, however,
the last word will be the just-included makefile.

However in the attached program you can see a use that this is violated.
The "ZZZfiles" definition has been set in wibble.mk which occurs before
the include statement that includes another.mk  however another.mk is in
the variable as shown when the variable is printed.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: make 4.0-8.2
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Jan  7 20:50:15 2016
Dependencies:
 gcc-5-base 5.2.1-22ubuntu2
 libc6 2.21-0ubuntu4
 libgcc1 1:5.2.1-22ubuntu2
InstallationDate: Installed on 2015-11-24 (44 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: make-dfsg
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: make-dfsg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug wily

** Attachment added: "setup demonstrating the issue"
   
https://bugs.launchpad.net/bugs/1531989/+attachment/4545859/+files/make_bug.tar.gz

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

Title:
  MAKEFILE_LIST no longer correct

Status in make-dfsg package in Ubuntu:
  New

Bug description:
  the version of make has what appears to be a broken for the
  MAKEFILE_LIST macro.

  This is commonly used to get the currently loaded makefile.

  However for some reason in this distribution the variable is not
  behaving as it should be.

  From https://www.gnu.org/software/make/manual/html_node/Special-
  Variables.html

  MAKEFILE_LIST

  Contains the name of each makefile that is parsed by make, in the
  order in which it was parsed. The name is appended just before make
  begins to parse the makefile. Thus, if the first thing a makefile does
  is examine the last word in this variable, it will be the name of the
  current makefile. Once the current makefile has used include, however,
  the last word will be the just-included makefile.

  However in the attached program you can see a use that this is
  violated.  The "ZZZfiles" definition has been set in wibble.mk which
  occurs before the include statement that includes another.mk  however
  another.mk is in the variable as shown when the variable is printed.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: make 4.0-8.2
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jan  7 20:50:15 2016
  Dependencies:
   gcc-5-base 5.2.1-22ubuntu2
   libc6 2.21-0ubuntu4
   libgcc1 1:5.2.1-22ubuntu2
  InstallationDate: Installed on 2015-11-24 (44 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: make-dfsg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1440608] Re: /etc/kernel/postinst.d/apt-auto-removal wants to remove all kernels except the latest one

2016-01-07 Thread Jarno Suni
cavsfan, why didn't you just use "sudo apt-get autoremove --purge" to
purge the extra kernel? Anyway, it is odd  that the system required
image packages to be removed before header packages.

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

Title:
  /etc/kernel/postinst.d/apt-auto-removal wants to remove all kernels
  except the latest one

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  After installing a 3rd kernel currently 3.19.0-12-generic, the
  /etc/apt/apt.conf.d/01autoremove-kernels file looks normal listing the
  3.19.0-11-generic and 3.19.0-12-generic with 3.19.0-10-generic listed
  to be autoremoved. But once autoremove is completed the machine
  requests to be rebooted and at that time the /etc/apt/apt.conf.d
  /01autoremove-kernels file lists the 3.19.0-12-generic and
  3.19.0-10-generic kernels. So upon rebooting the 3.19.0-11-generic is
  requested to be autoremoved leaving only one kernel the latest one
  3.19.0-12-generic.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: apt 1.0.9.7ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Apr  5 17:03:01 2015
  InstallationDate: Installed on 2015-04-02 (3 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Beta amd64 (20150401)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1531268] Re: Wizard does not change user password if one is pre-set

2016-01-07 Thread Launchpad Bug Tracker
** Branch linked: lp:~mterry/unity8/skip-wizard-password-if-set

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

Title:
  Wizard does not change user password if one is pre-set

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Whatever is selected (swipe, passcode, password) during the wizard is
  not set and the default code of  is required

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

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


[Touch-packages] [Bug 1531804] Re: [desktop] Browser crashes when downloading a file

2016-01-07 Thread Michael Sheldon
** Branch linked: lp:~michael-sheldon/ubuntu-download-
manager/fix-1531888

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

Title:
  [desktop] Browser crashes when downloading a file

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

   - on a desktop setup (xenial from the repositories, or wily from
  https://launchpad.net/~osomon/+archive/ubuntu/webbrowser-app), with
  qtdeclarative5-ubuntu-content1 and qtdeclarative5-ubuntu-download-
  manager0.1 installed, run webbrowser-app, point it to a page that has
  a link to e.g. a PDF document (e.g. https://help.ubuntu.com/), and
  click that link

  Expected result: the file is downloaded

  Current result: crash with the following stacktrace:

  #0  QDBusAbstractInterface::asyncCallWithArgumentList (this=0x0, method=..., 
args=...)
  at qdbusabstractinterface.cpp:501
  #1  0x7fffc448a70a in ?? () from 
/usr/lib/x86_64-linux-gnu/libubuntu-download-manager-client.so.1
  #2  0x7fffb2b28717 in 
Ubuntu::DownloadManager::SingleDownload::setAllowMobileDownload(bool) ()
 from 
/usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/DownloadManager/libUbuntuDownloadManager.so
  #3  0x7fffb2b2ad64 in 
Ubuntu::DownloadManager::SingleDownload::bindDownload(Ubuntu::DownloadManager::Download*)
 ()
 from 
/usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/DownloadManager/libUbuntuDownloadManager.so
  #4  0x7682f617 in QtPrivate::QSlotObjectBase::call (a=0x7fffd370, 
r=0x2fc02d0, this=)
  at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
  #5  QMetaObject::activate (sender=0x30d4010, signalOffset=, 
local_signal_index=, 
  argv=) at kernel/qobject.cpp:3702
  #6  0x7fffc44b3def in 
Ubuntu::DownloadManager::Manager::downloadCreated(Ubuntu::DownloadManager::Download*)
 ()
 from /usr/lib/x86_64-linux-gnu/libubuntu-download-manager-client.so.1
  #7  0x7fffc44af328 in ?? () from 
/usr/lib/x86_64-linux-gnu/libubuntu-download-manager-client.so.1
  #8  0x7682f617 in QtPrivate::QSlotObjectBase::call (a=0x7fffd630, 
r=0x30ccef0, this=)
  at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
  #9  QMetaObject::activate (sender=0x30ccef0, signalOffset=, 
  local_signal_index=local_signal_index@entry=0, 
argv=argv@entry=0x7fffd630) at kernel/qobject.cpp:3702
  #10 0x7682ff87 in QMetaObject::activate (sender=, 
  m=m@entry=0x7fffec80d680 , 
  local_signal_index=local_signal_index@entry=0, 
argv=argv@entry=0x7fffd630) at kernel/qobject.cpp:3582
  #11 0x7fffec7f110f in QDBusPendingCallWatcher::finished (this=, _t1=0x30ccef0)
  at .moc/moc_qdbuspendingcall.cpp:147
  #12 0x7fffec7f2815 in QDBusPendingCallWatcherPrivate::_q_finished 
(this=)
  at qdbuspendingcall.cpp:487
  #13 QDBusPendingCallWatcher::qt_static_metacall (_o=, 
_c=, _id=, 
  _a=) at .moc/moc_qdbuspendingcall.cpp:79
  #14 0x76830651 in QObject::event (this=0x30ccef0, e=) 
at kernel/qobject.cpp:1245
  #15 0x778b1b8c in QApplicationPrivate::notify_helper 
(this=this@entry=0x6eece0, 
  receiver=receiver@entry=0x30ccef0, e=e@entry=0x2cfcd40) at 
kernel/qapplication.cpp:3720
  #16 0x778b7230 in QApplication::notify (this=0x7fffdc60, 
receiver=0x30ccef0, e=0x2cfcd40)
  at kernel/qapplication.cpp:3503
  #17 0x767fef1b in QCoreApplication::notifyInternal 
(this=0x7fffdc60, receiver=0x30ccef0, 
  event=event@entry=0x2cfcd40) at kernel/qcoreapplication.cpp:935
  #18 0x76801057 in QCoreApplication::sendEvent (event=0x2cfcd40, 
receiver=)
  at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:228
  #19 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, 
event_type=event_type@entry=0, data=0x6eee50)
  at kernel/qcoreapplication.cpp:1552
  #20 0x76801588 in QCoreApplication::sendPostedEvents 
(receiver=receiver@entry=0x0, event_type=event_type@entry=0)
  at kernel/qcoreapplication.cpp:1410
  #21 0x76855e73 in postEventSourceDispatch (s=0x7e95c0) at 
kernel/qeventdispatcher_glib.cpp:271
  #22 0x751dbff7 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #23 0x751dc250 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #24 0x751dc2fc in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #25 0x7685627f in QEventDispatcherGlib::processEvents (this=0x802be0, 
flags=...) at kernel/qeventdispatcher_glib.cpp:418
  #26 0x767fc75a in QEventLoop::exec (this=this@entry=0x7fffdbb0, 
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
  #27 0x768042cc in QCoreApplication::exec () at 
kernel/qcoreapplication.cpp:1188
  #28 0x00466908 in BrowserApplication::run() ()
  #29 0x0045b8dd in main ()

To manage notific

[Touch-packages] [Bug 1531964] [NEW] Unable to unlock cryptsetup with external keyboard when using MODULES=dep

2016-01-07 Thread Simon Déziel
Public bug reported:

In order to unlock my root FS using an external keyboard I need to add
the following:

 hid_generic
 mac_hid
 usbhid

to /etc/initramfs-tools/modules. Otherwise, only the laptop's built-in
keyboard works.

In LP: #229732, this was fixed by loading a few modules in the panic
function. It seems the list of module could be augmented.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: initramfs-tools 0.120ubuntu6
ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
Uname: Linux 4.3.0-5-generic x86_64
ApportVersion: 2.19.3-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Jan  7 14:08:51 2016
PackageArchitecture: all
SourcePackage: initramfs-tools
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  Unable to unlock cryptsetup with external keyboard when using
  MODULES=dep

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  In order to unlock my root FS using an external keyboard I need to add
  the following:

   hid_generic
   mac_hid
   usbhid

  to /etc/initramfs-tools/modules. Otherwise, only the laptop's built-in
  keyboard works.

  In LP: #229732, this was fixed by loading a few modules in the panic
  function. It seems the list of module could be augmented.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.120ubuntu6
  ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
  Uname: Linux 4.3.0-5-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jan  7 14:08:51 2016
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1530371] Re: Number of unread messages within icon

2016-01-07 Thread Pat McGowan
** Changed in: canonical-devices-system-image
   Importance: Undecided => Wishlist

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Bill Filler (bfiller)

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

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

Title:
  Number of unread messages within icon

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  New
Status in messaging-app package in Ubuntu:
  New

Bug description:
  It would be nice to display the total number of unread messages within
  the icon (like the telegram app does).

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

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


[Touch-packages] [Bug 1529452] Re: Gallery app asks for same image multiple times at different sizes

2016-01-07 Thread Pat McGowan
** Changed in: canonical-devices-system-image
   Importance: Undecided => High

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

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Bill Filler (bfiller)

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

Title:
  Gallery app asks for same image multiple times at different sizes

Status in Canonical System Image:
  Confirmed
Status in gallery-app package in Ubuntu:
  New
Status in thumbnailer package in Ubuntu:
  Triaged

Bug description:
  I'm seeing this with image 342 from rc-proposed.

  When starting the gallery app with around 300 photos in my Pictures
  folder, I just noticed the request sequence shown below. Note that all
  requests are for the same image and are issued pretty much all at
  once. (There is about half a second elapsed time between the first and
  the last request.) The requests keep changing the size only, starting
  at 342 and working their way down to 216. This is supremely
  inefficient because each of the requests results in a separate scaling
  operation. In addition, each of these requests ends up in the cache on
  disk, so this behavior really hammers the battery and reduces cache
  efficiency.

  thumbnailer-service: [09:25:36.825] "thumbnail: 
/home/phablet/Pictures/com.ubuntu.camera/image20151227_091023042.jpg (342,342): 
0.044376 sec (MISS)"
  thumbnailer-service: [09:25:36.899] "thumbnail: 
/home/phablet/Pictures/com.ubuntu.camera/image20151227_091023042.jpg (341,341): 
0.020540 sec (MISS)"
  thumbnailer-service: [09:25:36.942] "thumbnail: 
/home/phablet/Pictures/com.ubuntu.camera/image20151227_091023042.jpg (340,340): 
0.034030 sec (MISS)"
  thumbnailer-service: [09:25:37.068] "thumbnail: 
/home/phablet/Pictures/com.ubuntu.camera/image20151227_091023042.jpg (338,338): 
0.143506 sec (MISS)"
  thumbnailer-service: [09:25:37.095] "thumbnail: 
/home/phablet/Pictures/com.ubuntu.camera/image20151227_091023042.jpg (335,335): 
0.154219 sec (MISS)"
  thumbnailer-service: [09:25:37.126] "thumbnail: 
/home/phablet/Pictures/com.ubuntu.camera/image20151227_091023042.jpg (332,332): 
0.162185 sec (MISS)"
  thumbnailer-service: [09:25:37.145] "thumbnail: 
/home/phablet/Pictures/com.ubuntu.camera/image20151227_091023042.jpg (326,326): 
0.172134 sec (MISS)"
  thumbnailer-service: [09:25:37.167] "thumbnail: 
/home/phablet/Pictures/com.ubuntu.camera/image20151227_091023042.jpg (318,318): 
0.177231 sec (MISS)"
  thumbnailer-service: [09:25:37.188] "thumbnail: 
/home/phablet/Pictures/com.ubuntu.camera/image20151227_091023042.jpg (307,307): 
0.181870 sec (MISS)"
  thumbnailer-service: [09:25:37.205] "thumbnail: 
/home/phablet/Pictures/com.ubuntu.camera/image20151227_091023042.jpg (292,292): 
0.182084 sec (MISS)"
  thumbnailer-service: [09:25:37.223] "thumbnail: 
/home/phablet/Pictures/com.ubuntu.camera/image20151227_091023042.jpg (273,292): 
0.183793 sec (MISS)"
  thumbnailer-service: [09:25:37.238] "thumbnail: 
/home/phablet/Pictures/com.ubuntu.camera/image20151227_091023042.jpg (273,273): 
0.198290 sec (MISS)"
  thumbnailer-service: [09:25:37.369] "thumbnail: 
/home/phablet/Pictures/com.ubuntu.camera/image20151227_091023042.jpg (250,273): 
0.313627 sec (MISS)"
  thumbnailer-service: [09:25:37.391] "thumbnail: 
/home/phablet/Pictures/com.ubuntu.camera/image20151227_091023042.jpg (250,250): 
0.334533 sec (MISS)"
  thumbnailer-service: [09:25:37.402] "thumbnail: 
/home/phablet/Pictures/com.ubuntu.camera/image20151227_091023042.jpg (218,218): 
0.317747 sec (MISS)"
  thumbnailer-service: [09:25:37.405] "thumbnail: 
/home/phablet/Pictures/com.ubuntu.camera/image20151227_091023042.jpg (216,216): 
0.310605 sec (HIT)"

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

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


[Touch-packages] [Bug 1270189] Re: Ubuntu Touch devices are using cellular DNS servers over wifi connection

2016-01-07 Thread Lorn Potter
Is there any reason to keep both connections active at the same time?

Obviously it needs to be able to connect to mobile data when wifi is
connected for HERE/agps, but I think it just needs to download satellite
data once (I could be wrong it might need to keep downloading this data)

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

Title:
  Ubuntu Touch devices are using cellular DNS servers over wifi
  connection

Status in Canonical System Image:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu RTM:
  New

Bug description:
  On my Nexus 4, build 121 with TMobile, when I am on wifi, I correctly
  get a 192.168 ip and DNS entries for this network (on wlan0) -- fine.
  When I am in range of cellular data, I get an ip address from TMobile
  and am given DNS entries that aren't on the same network as the
  TMobile ip address (on rmnet_usb0). The problem is, the DNS entries
  from TMobile are preferred over the ones from the wifi network such
  that while wlan0 is correctly setup as the default route, DNS queries
  are being made to the TMobile DNS servers over wlan0 because there are
  no explicit routes to these servers. This is problematic because the
  remote DNS server may not respond to queries coming from out of
  network or site policy may disallow the use of foreign DNS servers--
  both of which result in slow (or possibly failing) DNS queries since
  the cellular DNS is checked first. Also, where it did work, these
  queries could incur charges when the user is intending to use only
  wifi. In the case of (at least) TMobile, this could be a security
  concern because the well-known TMobile DNS servers are on the private
  '10.' network, which opens the possibility for a rogue DNS server to
  be on the private wifi network with this ip address.

  This could be fixed in (at least) four ways:
   1) when on wifi, don't merge the DNS servers on cellular networks at all 
which forces the device to use the ones available on the site (wlan0). This is 
guaranteed to not incur changes
   2) when on wifi, merge the DNS server from the cellular network, but add 
them after the ones on the wifi network. This will try the site's DNS first and 
only if they fail, fallback to the cellular DNS. This may incur charges under 
certain circumstances
   3) add an explicit route to the cellular DNS servers through rmnet_usb0. 
This will bypass the site DNS with all queries going through cellular DNS. This 
will incur charges and would make the device unable to resolve site-local names.
   4) same as '2', but also add explicit routes for the cellular name servers. 
This should only incur charges if wifi DNS fails

  I think '3' is out. '2' and '4' seems most intuitive (with '4' perhaps
  most correct). '1' seems also ok.

  # netstat -rn
  Kernel IP routing table
  Destination Gateway Genmask Flags   MSS Window  irtt Iface
  0.0.0.0 192.168.x.1 0.0.0.0 UG0 0  0 wlan0
  100.152.35.128  0.0.0.0 255.255.255.252 U 0 0  0 
rmnet_usb0
  192.168.x.0 0.0.0.0 255.255.255.0   U 0 0  0 wlan0

   Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]:  Auto-activating 
connection '/310260575949457/context1'.
  Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]:  Activation 
(/ril_0) starting connection '/310260575949457/context1'
  Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]:  (/ril_0): device 
state change: disconnected -> prepare (reason 'none') [30 40 0]
  Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]:  Activation 
(/ril_0) Stage 1 of 5 (Device Prepare) scheduled...
  Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]:  Activation 
(/ril_0) Stage 1 of 5 (Device Prepare) started...
  Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]:  Activation 
(/ril_0) Stage 1 of 5 (Device Prepare) complete.
  Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]:  (/ril_0): IPv4 
static configuration:
  Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]:address 
100.152.35.130/30
  Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]:DNS 10.177.0.34
  Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]:DNS 
10.168.183.116
  Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]:  Activation 
(/ril_0) Stage 2 of 5 (Device Configure) scheduled...
  Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]:  Activation 
(/ril_0) Stage 2 of 5 (Device Configure) starting...
  Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]:  (/ril_0): device 
state change: prepare -> config (reason 'none') [40 50 0]
  Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]:  Activation 
(/ril_0) Stage 2 of 5 (Device Configure) successful.
  Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]:  Activation 
(/ril_0) Stage 3 of 5 (IP Configure Sta

[Touch-packages] [Bug 1531118] Re: Cannot reinstall a previously uninstalled application

2016-01-07 Thread Pat McGowan
** Changed in: canonical-devices-system-image
   Status: Confirmed => In Progress

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

Title:
  Cannot reinstall a previously uninstalled application

Status in Canonical System Image:
  In Progress
Status in ubuntu-download-manager package in Ubuntu:
  In Progress
Status in unity-scope-click package in Ubuntu:
  Invalid

Bug description:
  current build number: 221
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en

  Test Case:
  1. Go to the app store, and install an app (I install sudoku from Sylvain 
Becker)
  2. Upon installation, go to the app scope, and verify that the app is 
installed
  3. Long press the app icon to go to the app details, and tap on 'uninstall'
  4. Verify that the app no longer appear in the app scope
  5. Go to the app store again, select the same app and try to re-install it.

  Expected Result
  The button 'Install' is displayed and the app can be installed

  Actual Result
  The button is labelled '0%' and is not clickable. The app cannot be 
resintalled.
  The state is cleared after a reboot and the app can be installed.

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

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


[Touch-packages] [Bug 1531913] Re: Fallback image not shown when no image specified

2016-01-07 Thread Pat McGowan
** Changed in: canonical-devices-system-image
   Importance: Undecided => Medium

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

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Michał Sawicz (saviq)

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

Title:
  Fallback image not shown when no image specified

Status in Canonical System Image:
  Confirmed
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  In fixing bug #1520631 in unity-scope-click, as the store server will
  start allowing uploads with no icon specified, it was discovered that
  Unity8 is not showing the fallback when we do not include the artwork.
  Instead, it is only shown if we specify invalid artwork. This seems
  wrong, and instead I would think the fallback would be displayed
  whenever no other artwork is provided.

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

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


[Touch-packages] [Bug 1529815] Re: InfiniBand DHCP flow with PRA and DHCP relay not working

2016-01-07 Thread David Duffey
Actually, In #5 said this feature was added in isc v5, but that is not correct. 
 Current upstream doesn't have broadcast flag settings.

https://source.isc.org/cgi-bin/gitweb.cgi?p=dhcp.git;a=summary

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

Title:
  InfiniBand DHCP flow with PRA and DHCP relay not working

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  
  DHCP client is sending discover with Unicast type request for the offer, in 
this configuration of IB to ETH through a relay we need the type to be 
broadcast.

  The issue is that when using dhclient from the client on Ubuntu (and only on 
Ubuntu) with MOFED or inbox driver, we see that that DHCP server offers in 
unicast instead of broadcast. It seems there is no way to correct this from the 
client side using dhclient configuration file.
  this issue exist even when we use always-broadcast statement in configuration 
file.

  in other vendors we see that discover request type is broadcast.
  attached pcap files from working (other vendor) and not working (Ubuntu) 
clients.

  
  DHCP CLIENT (IPoIB) 
  Ubuntu 14.04  kernel 3.13.0-74
  Mellanox OFED 3.1-1.0.3 or inbox driver
  isc-dhcp-client  4.2.4-7ubuntu12.3

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

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


[Touch-packages] [Bug 1531340] Re: Launcher quick list arrow can be poorly aligned at top of screen

2016-01-07 Thread Launchpad Bug Tracker
** Branch linked: lp:~mzanetti/unity8/launcher_folded_quicklist

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

Title:
  Launcher quick list arrow can be poorly aligned at top of screen

Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Steps to reproduce:
  1) Fill the launcher with enough icons that the top one is slightly angled 
(doesn't fully fit on screen)
  2) Press and hold on that top icon

  You'll see a quick list menu come up, but it's arrow won't fit to the
  popup correctly, because the icon is angled.  Screenshot attached.

  current build number: 203
  device name: mako
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-01-05 08:49:01
  version version: 203
  version ubuntu: 20160105
  version device: 20150911
  version custom: mako-1.1

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

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


[Touch-packages] [Bug 1530807] Re: Bluetooth cannot be activated.

2016-01-07 Thread Dubstar_04
I can confirm this affects rc proposed r332.

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

Title:
  Bluetooth cannot be activated.

Status in Canonical System Image:
  Confirmed
Status in indicator-bluetooth package in Ubuntu:
  New

Bug description:
  Using RC proposed 04/01/2016 bluetooth cannot be enabled.

  Tested on a nexus 7.

  Expected behavior:
  Bluetooth slider is moved to on
  Bluetooth activates
  Available devices appear in the list

  Experienced behavior: 
  Bluetooth slider is moved to on
  Activity spinners appear 
  Bluetooth slider moves to off.

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

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


[Touch-packages] [Bug 1531913] Re: Fallback image not shown when no image specified

2016-01-07 Thread Rodney Dawes
Specifying a blank artwork is still possible, and still not sensible.
One can always specify a 1x1 transparent image as the artwork for
intentionally blank space. :)

We don't detect that we are sending an empty image. We just specify the
fallback and expect it to work as a fallback should. If a fallback is
not shown when no artwork is passed, then it's not a fallback. If it's
the image to be shown when there is an error loading the image, then the
API is wrong, because developers might want to show something else in
case of error, so that it's known there was an error. Changing the scope
to do the work would mean duplicating code and logic. Why should we have
to specify the image that we want to fall back to, in two completely
different ways, in the same code?

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

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

Title:
  Fallback image not shown when no image specified

Status in Canonical System Image:
  New
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  In fixing bug #1520631 in unity-scope-click, as the store server will
  start allowing uploads with no icon specified, it was discovered that
  Unity8 is not showing the fallback when we do not include the artwork.
  Instead, it is only shown if we specify invalid artwork. This seems
  wrong, and instead I would think the fallback would be displayed
  whenever no other artwork is provided.

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

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


[Touch-packages] [Bug 1518411] Re: "Maximum number of clients reached", new in Ubuntu 15.10

2016-01-07 Thread Jonathan Kamens
It's a script I wrote myself. I would be happy to share it if that would
be useful.

I do not understand why you marked this issue invalid.

Surely you are not meaning to suggest that it is invalid for users to
write their own tools which periodically change the desktop background
using the interfaces that are provided for doing exactly that?

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

Title:
  "Maximum number of clients reached", new in Ubuntu 15.10

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  In my newly upgraded (from 15.04) Ubuntu 15.10 system, after I've been
  logged in for a while I can no longer open new windows and instead get
  a "Maximum number of clients reached" error.

  This did not happen in 15.04.

  I ran "lsof" on the X server and did not see an excessive number of
  open file descriptors. I ran it again on a newly restarted X server
  and the number of open file descriptors looked about the same.

  I also ran "xlsclients" when the X server was reporting "Maximum
  number of clients reached" and the list of clients looked correct and
  reasonable (and there were less than 30 of them).

  I am happy to collect any additional logs or debugging information to
  help track this down. I don't know where to look further.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Nov 20 13:00:09 2015
  DistUpgraded: 2015-11-17 11:59:09,835 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.4, 3.19.0-33-generic, x86_64: installed
   virtualbox, 5.0.4, 4.2.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Crystal Well Integrated Graphics Controller [8086:0d26] 
(rev 08) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Device [1558:7410]
  MachineType: System76, Inc. Galago UltraPro
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic 
root=UUID=821f94aa-97e2-4384-8494-9f510a75877b ro i915.disable_power_well=0 
quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to wily on 2015-11-17 (3 days ago)
  dmi.bios.date: 12/12/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W740SU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/12/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: Galago UltraPro
  dmi.product.version: galu1
  dmi.sys.vendor: System76, Inc.
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Fri Nov 20 12:51:23 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9
  xserver.video_driver: intel

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

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


[Touch-packages] [Bug 1531928] [NEW] [Xenial] root=PARTUUID= is not recognized as valid syntax.

2016-01-07 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

As per kernel source init/do_mounts.c root=PARTUUID= is acceptable 
format to pass root= option on command line to boot a system. But due to a bug 
in initramfs-tools this syntax does not work 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801154

/*
 *  Convert a name into device number.  We accept the following variants:
 *
 *  1)  device number in hexadecimal represents itself
 * no leading 0x, for example b302.
 *  2) /dev/nfs represents Root_NFS (0xff)
 *  3) /dev/ represents the device number of disk
 *  4) /dev/ represents the device number
 * of partition - device number of disk plus the partition number
 *  5) /dev/p - same as the above, that form is
 * used when disk name of partitioned disk ends on a digit.
 *  6) PARTUUID=00112233-4455-6677-8899-AABBCCDDEEFF representing the
 * unique id of a partition if the partition table provides it.
 * The UUID may be either an EFI/GPT UUID, or refer to an MSDOS
 * partition using the format -PP, where  is a zero-
 * filled hex representation of the 32-bit "NT disk signature", and PP
 * is a zero-filled hex representation of the 1-based partition number.
 *  7) PARTUUID=/PARTNROFF= to select a partition in relation to
 * a partition with a known unique id.
 *  8) : major and minor number of the device separated by
 * a colon.
 *

Please merge the patch from debian in xenial to support PARTUUID in
initramfs.

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Assignee: Andy Whitcroft (apw)
 Status: In Progress

-- 
[Xenial] root=PARTUUID=  is not recognized as valid syntax.
https://bugs.launchpad.net/bugs/1531928
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to initramfs-tools 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 1531925] Re: bluetoothd crash with BTLE keyboard

2016-01-07 Thread Pat McGowan
** Description changed:

  Trying to pair this device and bluetoothd crashed on my Wily laptop and
  the N4 running latest proposed
+ 
+ build number: 107
+ device name: mako
+ channel: ubuntu-touch/rc-proposed/ubuntu-pd
+ last update: 2016-01-07 11:30:20
+ version version: 107
+ version ubuntu: 20160107
+ version device: 20150911
+ version custom: 20150929-2-vivid
+ 
  
  The device is a Logitech keyboard with an integrated trackpad.
  
  Device DF:08:A9:A0:13:91
   Name: K830
   Alias: K830
   Appearance: 0x03c1
   Icon: input-keyboard
   Paired: no
   Trusted: no
   Blocked: no
   Connected: no
   LegacyPairing: no
   UUID: Human Interface Device(1812--1000-8000-00805f9b34fb)
   RSSI: -43
  
  The device would come and go in the devices list from bluetoothctl
  A manual scan would bring it back
  I then tried to manually pair and it failed with
  Failed to pair: org.freedesktop.DBus.Error.NoReply
  
  On the latop dmesg reports
  [357895.395029] traps: bluetoothd[790] general protection ip:56419e2c0306 
sp:7ffefd2b6760 error:0 in bluetoothd[56419e217000+105000]

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

Title:
  bluetoothd crash with BTLE keyboard

Status in bluez package in Ubuntu:
  New

Bug description:
  Trying to pair this device and bluetoothd crashed on my Wily laptop
  and the N4 running latest proposed

  build number: 107
  device name: mako
  channel: ubuntu-touch/rc-proposed/ubuntu-pd
  last update: 2016-01-07 11:30:20
  version version: 107
  version ubuntu: 20160107
  version device: 20150911
  version custom: 20150929-2-vivid

  
  The device is a Logitech keyboard with an integrated trackpad.

  Device DF:08:A9:A0:13:91
   Name: K830
   Alias: K830
   Appearance: 0x03c1
   Icon: input-keyboard
   Paired: no
   Trusted: no
   Blocked: no
   Connected: no
   LegacyPairing: no
   UUID: Human Interface Device(1812--1000-8000-00805f9b34fb)
   RSSI: -43

  The device would come and go in the devices list from bluetoothctl
  A manual scan would bring it back
  I then tried to manually pair and it failed with
  Failed to pair: org.freedesktop.DBus.Error.NoReply

  On the latop dmesg reports
  [357895.395029] traps: bluetoothd[790] general protection ip:56419e2c0306 
sp:7ffefd2b6760 error:0 in bluetoothd[56419e217000+105000]

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

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


[Touch-packages] [Bug 1520887] Re: Workaround Ubuntu 15.10. Network manager applet cannot stably activate mobile broadband using 4G USB modem ZTE MF820D.

2016-01-07 Thread Alberto Salvia Novella
** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Workaround Ubuntu 15.10. Network manager applet cannot stably activate
  mobile broadband using 4G USB modem ZTE MF820D.

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I use Ubuntu 15.10, I have done a fresh install formerly using 14.04
  on the same hardware setup.

  If I boot Ubuntu from power-off, then I must sometimes enter the PIN-
  code for the mobile broadband SIM-card, I also get prompted for my
  password (to make changes to the mobile broadband device); however,
  most of the time only my password is needed, and the saved PIN-code is
  used.

  After entering my password the 4G-USB-modem gets green light for
  establishing an 4G (or 3G) connection, but it is impossible to connect
  to the 4G-internet from the desktop drop down menu of network manager
  at this stage; I get an error message: "(Translated from Swedish-
  Activate connection failure) Creating object for path
  '/org/freedesktop/NetworkManager/ActiveConnection/1' failed in libnm-
  glib."

  (I have set up this 4G-internet-connention with help from the network-
  manager wizard, using defaults, except turning off roaming and setting
  "allow all users to connect.")

  However, if I choose to reboot without power-off, the green light on
  the USB-modem stays on during the reboot (keeps 4G-connected I
  presume), then it is possible to connect to internet from the drop
  down menu, most of the time. Some times I also had to deactivate-
  activate mobile broadband from the drop down menu before internet
  connection could be established.

  It is also not possible to edit the connections of the mobile broadband in 
the network manager applet; I get an error message: "(Translated from 
Swedish-Error initiating editor) settings/nm-settings-connection.c.955 - 
Connection didn't have requested setting 'ppp'".
  Editing the wifi-connection works just fine.

  Regards

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: network-manager 1.0.4-0ubuntu5.1
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Nov 29 07:44:12 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 95.192.135.45 dev wwx0eb79c89dc58  proto static  metric 750
   95.192.135.44/30 dev wwx0eb79c89dc58  proto kernel  scope link  src 
95.192.135.46  metric 750
   169.254.0.0/16 dev wwx0eb79c89dc58  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   LANGUAGE=sv
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICETYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH
   cdc-wdm1  gsm   connected /org/freedesktop/NetworkManager/Devices/3  
Telia Telia 4G  d851a986-be40-488b-9f96-36d2c9387b57  
/org/freedesktop/NetworkManager/ActiveConnection/5
   wlp3s0wifi  disconnected  /org/freedesktop/NetworkManager/Devices/2  
--  ----
   enp4s0ethernet  unavailable   /org/freedesktop/NetworkManager/Devices/1  
--  ----
   loloopback  unmanaged /org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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


[Touch-packages] [Bug 1525320] Re: Aquaris E4.5 can't connect with car [Skoda Fabia] using bluetooth

2016-01-07 Thread Kevin Bradley
Is this a duplicate of #1435040?

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

Title:
  Aquaris E4.5 can't connect with car [Skoda Fabia] using bluetooth

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Aquaris E4.5 Can't connect with my car (new skoda fabia 2015) with
  bluetooth.

  Error is:

  "Could not connect with Aquaris E4.5 Ubuntu Edition"

  
  Let me know if I can help in some way..thanks!

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

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


[Touch-packages] [Bug 1531571] Re: package ifupdown 0.7.54ubuntu2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

2016-01-07 Thread Alberto Salvia Novella
** Changed in: ifupdown (Ubuntu)
   Importance: Undecided => High

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

Title:
  package ifupdown 0.7.54ubuntu2 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 1

Status in ifupdown package in Ubuntu:
  Confirmed

Bug description:
  Was brought here by apt-get. Can't give much more information about
  this.. bug..?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ifupdown 0.7.54ubuntu2
  ProcVersionSignature: Ubuntu 4.3.0-2.11-lowlatency 4.3.0
  Uname: Linux 4.3.0-2-lowlatency x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  Date: Wed Jan  6 18:54:18 2016
  DuplicateSignature:
   De-configuring udev (228-2ubuntu1) ...
   /var/lib/dpkg/info/udev.prerm called with unknown argument 'deconfigure'
   dpkg: error processing archive 
/var/cache/apt/archives/ifupdown_0.8.5ubuntu1_amd64.deb (--unpack):
subprocess installed pre-removal script returned error exit status 1
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2015-09-08 (119 days ago)
  InstallationMedia: Ubuntu-Studio 15.10 "Wily Werewolf" - Alpha amd64 
(20150906)
  RelatedPackageVersions:
   dpkg 1.18.3ubuntu1
   apt  1.1.10
  SourcePackage: ifupdown
  Title: package ifupdown 0.7.54ubuntu2 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2015-11-22 (44 days ago)

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

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


[Touch-packages] [Bug 1531913] Re: Fallback image not shown when no image specified

2016-01-07 Thread Michał Sawicz
** Changed in: unity8 (Ubuntu)
   Status: New => Triaged

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

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Albert Astals Cid (aacid)

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

Title:
  Fallback image not shown when no image specified

Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  In fixing bug #1520631 in unity-scope-click, as the store server will
  start allowing uploads with no icon specified, it was discovered that
  Unity8 is not showing the fallback when we do not include the artwork.
  Instead, it is only shown if we specify invalid artwork. This seems
  wrong, and instead I would think the fallback would be displayed
  whenever no other artwork is provided.

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

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


[Touch-packages] [Bug 1529815] Re: InfiniBand DHCP flow with PRA and DHCP relay not working

2016-01-07 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: isc-dhcp (Ubuntu)
   Status: New => Confirmed

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

Title:
  InfiniBand DHCP flow with PRA and DHCP relay not working

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  
  DHCP client is sending discover with Unicast type request for the offer, in 
this configuration of IB to ETH through a relay we need the type to be 
broadcast.

  The issue is that when using dhclient from the client on Ubuntu (and only on 
Ubuntu) with MOFED or inbox driver, we see that that DHCP server offers in 
unicast instead of broadcast. It seems there is no way to correct this from the 
client side using dhclient configuration file.
  this issue exist even when we use always-broadcast statement in configuration 
file.

  in other vendors we see that discover request type is broadcast.
  attached pcap files from working (other vendor) and not working (Ubuntu) 
clients.

  
  DHCP CLIENT (IPoIB) 
  Ubuntu 14.04  kernel 3.13.0-74
  Mellanox OFED 3.1-1.0.3 or inbox driver
  isc-dhcp-client  4.2.4-7ubuntu12.3

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

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


[Touch-packages] [Bug 1531913] Re: Fallback image not shown when no image specified

2016-01-07 Thread Albert Astals Cid
Doing that will make it not possible to actually specify a blank artwork
if we ever want one. -> if we specify a fallback image

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

Title:
  Fallback image not shown when no image specified

Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  In fixing bug #1520631 in unity-scope-click, as the store server will
  start allowing uploads with no icon specified, it was discovered that
  Unity8 is not showing the fallback when we do not include the artwork.
  Instead, it is only shown if we specify invalid artwork. This seems
  wrong, and instead I would think the fallback would be displayed
  whenever no other artwork is provided.

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

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


[Touch-packages] [Bug 1531913] Re: Fallback image not shown when no image specified

2016-01-07 Thread Albert Astals Cid
Doing that will make it not possible to actually specify a blank artwork
if we ever want one.

Whether that is useful or not I don't know :D

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

Title:
  Fallback image not shown when no image specified

Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  In fixing bug #1520631 in unity-scope-click, as the store server will
  start allowing uploads with no icon specified, it was discovered that
  Unity8 is not showing the fallback when we do not include the artwork.
  Instead, it is only shown if we specify invalid artwork. This seems
  wrong, and instead I would think the fallback would be displayed
  whenever no other artwork is provided.

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

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


[Touch-packages] [Bug 1531901] Re: Notifications disappear after reboot

2016-01-07 Thread Michael Zanetti
*** This bug is a duplicate of bug 1388189 ***
https://bugs.launchpad.net/bugs/1388189

** This bug has been marked a duplicate of bug 1388189
   [Notifications] retain notifications that the user has not acted on

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

Title:
  Notifications disappear after reboot

Status in unity-notifications package in Ubuntu:
  New

Bug description:
  Krillin, rc-proposed, r219

  Notifications indicator gets emptied at every reboot.

  Reproducibility: 100%

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

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


[Touch-packages] [Bug 1531909] [NEW] package keyboard-configuration 1.108ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-01-07 Thread Adam Kuśmierz
Public bug reported:

xxx

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: keyboard-configuration 1.108ubuntu5
Uname: Linux 3.10.23--std-ipv6-64-vps x86_64
ApportVersion: 2.17.2-0ubuntu1.8
Architecture: amd64
Date: Thu Jan  7 17:13:18 2016
DuplicateSignature: package:keyboard-configuration:1.108ubuntu5:subprocess 
installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2014-10-23 (441 days ago)
InstallationMedia:
 
Keyboard:
 XKBMODEL="pc105"
 XKBLAYOUT="us"
 XKBVARIANT="altgr-intl"
 XKBOPTIONS=""
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.17.25ubuntu1.1
 apt  1.0.9.7ubuntu4.2
SourcePackage: console-setup
Title: package keyboard-configuration 1.108ubuntu5 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to vivid on 2016-01-07 (0 days ago)

** Affects: console-setup (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check vivid

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

Title:
  package keyboard-configuration 1.108ubuntu5 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in console-setup package in Ubuntu:
  New

Bug description:
  xxx

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: keyboard-configuration 1.108ubuntu5
  Uname: Linux 3.10.23--std-ipv6-64-vps x86_64
  ApportVersion: 2.17.2-0ubuntu1.8
  Architecture: amd64
  Date: Thu Jan  7 17:13:18 2016
  DuplicateSignature: package:keyboard-configuration:1.108ubuntu5:subprocess 
installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2014-10-23 (441 days ago)
  InstallationMedia:
   
  Keyboard:
   XKBMODEL="pc105"
   XKBLAYOUT="us"
   XKBVARIANT="altgr-intl"
   XKBOPTIONS=""
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1.1
   apt  1.0.9.7ubuntu4.2
  SourcePackage: console-setup
  Title: package keyboard-configuration 1.108ubuntu5 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to vivid on 2016-01-07 (0 days ago)

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

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


[Touch-packages] [Bug 1531677] [NEW] Live CD dosen't shutdown

2016-01-07 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Shutting down or restarting from the live CD installer ("Install Ubuntu" in 
GRUB) doesn't work.
It gets to the part where it says "Please remove the installation medium, then 
press ENTER:", but when I do that, the screen just flashes black for a second, 
and then it returns to the same screen, and sits their with the progress bar 
moving and nothing happening. If I hit Ctrl+Alt+D at this point it gives me a 
log with the following at the bottom:

Starting Power-Off.
[FAILED] Failed to start Power-Off.
See 'systemctl status systemd-poweroff.service' for details.
[DEPEND] Dependency failed for Power-Off.

This does not happen with the "Try Ubuntu" option.
Tested on Xenial Daily (5/1/16) amd64.

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


** Tags: bot-comment xenial
-- 
Live CD dosen't shutdown
https://bugs.launchpad.net/bugs/1531677
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd 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 1347788] Re: find crashed when current working directory is not readable and -exec or -execdir used

2016-01-07 Thread Dave Chiluk
Findutils just released a new blessed stable version 4.6.0

http://savannah.gnu.org/bugs/?46438

What are the chances of getting this included into xenial?

** Bug watch added: GNU Savannah Bug Tracker #46438
   http://savannah.gnu.org/bugs/?46438

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

Title:
  find crashed when current working directory is not readable and -exec
  or -execdir used

Status in findutils package in Ubuntu:
  Confirmed
Status in findutils source package in Xenial:
  Confirmed

Bug description:
  bug is similar to https://savannah.gnu.org/bugs/?15384 but for current
  directory (when it not readable or not executable)

  steps to reproduce

  DIR=`mktemp -d`
  cd $DIR
  mkdir -p 1/1 2
  cd 2
  find $DIR/1 -type d -exec echo {} \;
  find $DIR/1 -type d -execdir echo {} \;

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: findutils 4.4.2-7
  Uname: Linux 3.15.4-031504-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Jul 23 20:17:19 2014
  Dependencies:
   gcc-4.9-base 4.9-20140406-0ubuntu1
   libc6 2.19-0ubuntu6
   libgcc1 1:4.9-20140406-0ubuntu1
   multiarch-support 2.19-0ubuntu6
  InstallationDate: Installed on 2014-04-24 (89 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: findutils
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Dependencies:
   gcc-4.9-base 4.9-20140406-0ubuntu1
   libc6 2.19-0ubuntu6
   libgcc1 1:4.9-20140406-0ubuntu1
   multiarch-support 2.19-0ubuntu6
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-04-24 (89 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Package: findutils 4.4.2-7
  PackageArchitecture: amd64
  Tags:  trusty
  Uname: Linux 3.15.4-031504-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Touch-packages] [Bug 1531901] [NEW] Notifications disappear after reboot

2016-01-07 Thread Andrea Bernabei
Public bug reported:

Krillin, rc-proposed, r219

Notifications indicator gets emptied at every reboot.

Reproducibility: 100%

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

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

Title:
  Notifications disappear after reboot

Status in unity-notifications package in Ubuntu:
  New

Bug description:
  Krillin, rc-proposed, r219

  Notifications indicator gets emptied at every reboot.

  Reproducibility: 100%

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

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


[Touch-packages] [Bug 1531893] [NEW] bottom edge bet stuck if you click outside it while dragging

2016-01-07 Thread Renato Araujo Oliveira Filho
Public bug reported:


1 - Start to reveal the bottom edge
2 - While you still dragging it, click outside it
(with another finger without release the current one).

Expected:
Nothing happen

Current:
 bottom edge page get stuck on the middle of the screen.

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  bottom edge bet stuck if you click outside it while dragging

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  
  1 - Start to reveal the bottom edge
  2 - While you still dragging it, click outside it
  (with another finger without release the current one).

  Expected:
  Nothing happen

  Current:
   bottom edge page get stuck on the middle of the screen.

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

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


[Touch-packages] [Bug 1531656] Re: /usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:boost::

2016-01-07 Thread Rodney Dawes
** No longer affects: unity-scopes-api (Ubuntu)

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

Title:
  /usr/lib/arm-linux-gnueabihf/unity-
  
scopes/scoperunner:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:boost::throw_exception

Status in unity-scope-click package in Ubuntu:
  New

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

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

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


[Touch-packages] [Bug 1032690] Re: couldn't find RGB GLX visual or fbconfig

2016-01-07 Thread anatoly techtonik
"cant start GNOME" looks like a particular problem with particular
system. Is it still actual to keep this open?

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

Title:
  couldn't find RGB GLX visual or fbconfig

Status in mesa package in Ubuntu:
  New

Bug description:
  Hi

  I have some troubles with nvidia and GLX

  here is the log:
  Error: couldn't find RGB GLX visual or fbconfig
  Xlib:  extension "GLX" missing on display ":0".
  Xlib:  extension "GLX" missing on display ":0".
  Xlib:  extension "GLX" missing on display ":0".
  Xlib:  extension "GLX" missing on display ":0".
  Xlib:  extension "GLX" missing on display ":0".

  After the last update I cant start GNOME.

  Please help

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

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


[Touch-packages] [Bug 1477838] Re: [MX4] Crackling sound after playing audio and suspended

2016-01-07 Thread Jean-Baptiste Lallement
** Description changed:

  The Meizu MX4 is doing a weird "tic tic tic..." after receive a
  notification (from telegram, mail...) and it's suspended.
  
  --
  
  When I press the screen lock button on the MX4 shortly after playing
  music or ending a phone call I hear a radio/fuzzy distorted noise coming
  from the phone. To make it stop I need to unlock and lock the screen
  again but this is not ideal.
  
  -
  
  When the screen is locked and the playing song is finished and waiting
  for a stopped signal, MX4 will do a weird lower sound.
  
  -
  
- How to reproduce (Note this does not always work, the phone needs to be
- in some specific state yet to be determined)
+ TEST CASE (Thanks to Kamikaze)
+ 1. Boot the device and wait until is suspends (black screen)
+ 2. ssh to the device
+ 3. Run from the command line:
+   $ aplay /usr/share/sounds/alsa/Front_Left.wav
+ 4. Repeat step 3 until you reproduce the issue (3 to 5 times)
+ 
+ 
+ --- Original Case ---
+ How to reproduce (Note this does not always work, the phone needs to be in 
some specific state yet to be determined)
  
  Ensure MX4 is not plugged into USB
  Call the MX4 and hear the ringtone
  Dismiss the call
  Push the power button to turn off the screen
  Tick Tick Tick
  Push the power button to turn on the screen
  hissing
  Push the power button to turn off the screen
  Tick Tick Tick
  etc
  
  It will not clear until you play another sound
  Does not happen in silent mode of course

** Description changed:

  The Meizu MX4 is doing a weird "tic tic tic..." after receive a
  notification (from telegram, mail...) and it's suspended.
  
  --
  
  When I press the screen lock button on the MX4 shortly after playing
  music or ending a phone call I hear a radio/fuzzy distorted noise coming
  from the phone. To make it stop I need to unlock and lock the screen
  again but this is not ideal.
  
  -
  
  When the screen is locked and the playing song is finished and waiting
  for a stopped signal, MX4 will do a weird lower sound.
  
  -
  
  TEST CASE (Thanks to Kamikaze)
- 1. Boot the device and wait until is suspends (black screen)
+ 1. Boot the device and wait until it suspends (black screen)
  2. ssh to the device
  3. Run from the command line:
-   $ aplay /usr/share/sounds/alsa/Front_Left.wav
+   $ aplay /usr/share/sounds/alsa/Front_Left.wav
  4. Repeat step 3 until you reproduce the issue (3 to 5 times)
- 
  
  --- Original Case ---
  How to reproduce (Note this does not always work, the phone needs to be in 
some specific state yet to be determined)
  
  Ensure MX4 is not plugged into USB
  Call the MX4 and hear the ringtone
  Dismiss the call
  Push the power button to turn off the screen
  Tick Tick Tick
  Push the power button to turn on the screen
  hissing
  Push the power button to turn off the screen
  Tick Tick Tick
  etc
  
  It will not clear until you play another sound
  Does not happen in silent mode of course

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

Title:
  [MX4] Crackling sound after playing audio and suspended

Status in Canonical System Image:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The Meizu MX4 is doing a weird "tic tic tic..." after receive a
  notification (from telegram, mail...) and it's suspended.

  --

  When I press the screen lock button on the MX4 shortly after playing
  music or ending a phone call I hear a radio/fuzzy distorted noise
  coming from the phone. To make it stop I need to unlock and lock the
  screen again but this is not ideal.

  -

  When the screen is locked and the playing song is finished and waiting
  for a stopped signal, MX4 will do a weird lower sound.

  -

  TEST CASE (Thanks to Kamikaze)
  1. Boot the device and wait until it suspends (black screen)
  2. ssh to the device
  3. Run from the command line:
    $ aplay /usr/share/sounds/alsa/Front_Left.wav
  4. Repeat step 3 until you reproduce the issue (3 to 5 times)

  --- Original Case ---
  How to reproduce (Note this does not always work, the phone needs to be in 
some specific state yet to be determined)

  Ensure MX4 is not plugged into USB
  Call the MX4 and hear the ringtone
  Dismiss the call
  Push the power button to turn off the screen
  Tick Tick Tick
  Push the power button to turn on the screen
  hissing
  Push the power button to turn off the screen
  Tick Tick Tick
  etc

  It will not clear until you play another sound
  Does not happen in silent mode of course

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

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

[Touch-packages] [Bug 1531871] Re: Page header showing two div lines when using adaptive layout

2016-01-07 Thread Launchpad Bug Tracker
** Branch linked: lp:~tpeeters/ubuntu-ui-toolkit/fixDoubleLine

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

Title:
  Page header showing two div lines when using adaptive layout

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

Bug description:
  Two div lines appear on the header when the page is inside an
  AdaptiveLayout.

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

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


[Touch-packages] [Bug 1529903] Re: Blank message in a group sms

2016-01-07 Thread Jean-Baptiste Lallement
** Changed in: canonical-devices-system-image
   Status: Confirmed => Fix Committed

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

Title:
  Blank message in a group sms

Status in Canonical System Image:
  Fix Committed
Status in telepathy-ofono package in Ubuntu:
  Confirmed
Status in telephony-service package in Ubuntu:
  Fix Released

Bug description:
  MX4 running 201

  Received an incoming text to an existing group
  A notification was shown and added to the indicator
  The message content was empty as was the contact info
  Other members in the group received the SMS properly and subsequent messages 
were displayed correctly.
  There is no entry shown in the messaging app
  There is no crash file

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

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


[Touch-packages] [Bug 1524131] Re: /usr/bin/mediaplayer-app:11:__memcpy_neon:std::char_traits:std::basic_streambuf:std::basic_streambuf:std::__ostream_write

2016-01-07 Thread Jean-Baptiste Lallement
Setting to critical as the app cannot be relaunched until apport is done
wroting the crash file when is it enabled.

** Changed in: canonical-devices-system-image
   Importance: High => Critical

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

Title:
  /usr/bin/mediaplayer-
  
app:11:__memcpy_neon:std::char_traits:std::basic_streambuf:std::basic_streambuf:std::__ostream_write

Status in Canonical System Image:
  Confirmed
Status in dbus-cpp package in Ubuntu:
  New
Status in mediaplayer-app package in Ubuntu:
  New

Bug description:
  Top 3 over the past week on errors.u.c. mediaplayer has not been
  updated for a while and the frequency increased significantly around
  mid-december, probably due to a change in an underlying component
  (gstreamer has been updated on Dec. 12th or it could be the major dbus
  match rules changes as the stacktrace would suggest)

  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding mediaplayer-app.  This problem was most recently seen with
  version 0.20.5+15.04.20150701-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/a649a8d64746c3cce478208950c51611a06323cb
  contains more details.

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

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


[Touch-packages] [Bug 1529903] Re: Blank message in a group sms

2016-01-07 Thread Launchpad Bug Tracker
This bug was fixed in the package telephony-service -
0.1+16.04.20160105-0ubuntu1

---
telephony-service (0.1+16.04.20160105-0ubuntu1) xenial; urgency=medium

  [ CI Train Bot ]
  * Resync trunk. added: po/ne.po

  [ Tiago Salem Herrmann ]
  * Update mms flag so telephony-service-indicator can correctly manage
attachments. (LP: #1529903)

 -- Bill Filler   Tue, 05 Jan 2016 17:18:22
+

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

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

Title:
  Blank message in a group sms

Status in Canonical System Image:
  Confirmed
Status in telepathy-ofono package in Ubuntu:
  Confirmed
Status in telephony-service package in Ubuntu:
  Fix Released

Bug description:
  MX4 running 201

  Received an incoming text to an existing group
  A notification was shown and added to the indicator
  The message content was empty as was the contact info
  Other members in the group received the SMS properly and subsequent messages 
were displayed correctly.
  There is no entry shown in the messaging app
  There is no crash file

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

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


[Touch-packages] [Bug 1531860] [NEW] Mouse lagging and leaving a trail on laptop and external monitors

2016-01-07 Thread Steve Kroon
Public bug reported:

I have a Dell Latitude laptop with Optimus, connected to an external
monitor over DVI via a docking station.

Moving the mouse on my external monitor leaves a number of mouse pointer
icons which disappear after a short time, but hang around long enough to
make a short trail.  When the mouse pointer is on the laptop screen, it
flickers to such an extent that sometimes it becomes just about
invisible.

I have no idea which package this is for, unfortunately.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30
Uname: Linux 3.13.0-74-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,mousepoll,grid,snap,regex,wall,animation,place,move,resize,gnomecompat,imgpng,vpswitch,workarounds,unitymtgrabhandles,fade,expo,session,scale,ezoom,unityshell]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Thu Jan  7 15:30:03 2016
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.7, 3.13.0-74-generic, x86_64: installed
 virtualbox, 4.3.34, 3.13.0-68-generic, x86_64: installed
 virtualbox, 4.3.34, 3.13.0-70-generic, x86_64: installed
 virtualbox, 4.3.34, 3.13.0-71-generic, x86_64: installed
 virtualbox, 4.3.34, 3.13.0-74-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0494]
 NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA 
controller])
   Subsystem: Dell Device [1028:1494]
InstallationDate: Installed on 2015-06-23 (198 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: Dell Inc. Latitude E6520
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-74-generic 
root=UUID=ddefc523-a43d-4094-aa6b-b4dee85a7fbe ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/18/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 0J4TFW
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0J4TFW:rvrA01:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6520
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.5
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.5
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Thu Jan  7 07:37:15 2016
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 NOUVEAU(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.15.1-0ubuntu2.7

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

Title:
  Mouse lagging and leaving a trail on laptop and external monitors

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a Dell Latitude laptop with Optimus, connected to an external
  monitor over DVI via a docking station.

  Moving the mouse on my external monitor leaves a number of mouse
  pointer icons which disappear after a short time, but hang around long
  enough to make a short trail.  When the mouse pointer is on the laptop
  screen, it flickers to such an extent that sometimes it becomes just
  about invisible.

  I have no idea which package this is for, unfortunately.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30
  Uname: Linux 3.13.0-74-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detect

[Touch-packages] [Bug 1531604] Re: Missing package dependency for Ubuntu.Thumbnailer

2016-01-07 Thread Arthur Mello
** Changed in: gallery-app (Ubuntu)
   Status: New => In Progress

** Changed in: gallery-app (Ubuntu)
 Assignee: (unassigned) => Arthur Mello (artmello)

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

Title:
  Missing package dependency for Ubuntu.Thumbnailer

Status in gallery-app package in Ubuntu:
  In Progress

Bug description:
  System:
  Ubuntu Xenial desktop

  Steps to reproduce the issue:
  $ sudo apt-get install gallery-app
  $ gallery-app

  Expected outcome:
  Gallery runs normally.

  Actual outcome:
  You get a blank screen and the following error is printed on the terminal:
  """
  file:///usr/share/gallery-app/rc/qml/MainScreen.qml:221:21: Type 
PhotosOverview unavailable
  file:///usr/share/gallery-app/rc/qml/PhotosOverview.qml:71:5: Type MediaGrid 
unavailable
  file:///usr/share/gallery-app/rc/qml/Components/MediaGrid.qml:19:1: module 
"Ubuntu.Thumbnailer" is not installed
  """

  The following command solved the problem:
  $ sudo apt-get install qml-module-ubuntu-thumbnailer0.1

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

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


[Touch-packages] [Bug 1531604] Re: Missing package dependency for Ubuntu.Thumbnailer

2016-01-07 Thread Launchpad Bug Tracker
** Branch linked: lp:~artmello/gallery-app/gallery-app-fix_1531604

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

Title:
  Missing package dependency for Ubuntu.Thumbnailer

Status in gallery-app package in Ubuntu:
  In Progress

Bug description:
  System:
  Ubuntu Xenial desktop

  Steps to reproduce the issue:
  $ sudo apt-get install gallery-app
  $ gallery-app

  Expected outcome:
  Gallery runs normally.

  Actual outcome:
  You get a blank screen and the following error is printed on the terminal:
  """
  file:///usr/share/gallery-app/rc/qml/MainScreen.qml:221:21: Type 
PhotosOverview unavailable
  file:///usr/share/gallery-app/rc/qml/PhotosOverview.qml:71:5: Type MediaGrid 
unavailable
  file:///usr/share/gallery-app/rc/qml/Components/MediaGrid.qml:19:1: module 
"Ubuntu.Thumbnailer" is not installed
  """

  The following command solved the problem:
  $ sudo apt-get install qml-module-ubuntu-thumbnailer0.1

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

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


[Touch-packages] [Bug 1531583] Re: Webbrowser-app losing saved state upon restart

2016-01-07 Thread Olivier Tilloy
Michael, when the crash happens, the entire app is taken down, right? not just 
the renderer process for the current tab?
What happens then? Is the app automatically relaunched?
If not, can you have a look at the contents of 
$HOME/.local/share/webbrowser-app/session.json (and session.json.lock)? Maybe 
share them with me privately (they may contain sensitive data).
Also, is there a crash file under /var/crash? Can you share it here?

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

Title:
  Webbrowser-app losing saved state upon restart

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  I've noticed that lately on my rc-proposed dogfood mako that sometimes
  webbrowser-app will be OOM (or crash?) and restarted but lose all its
  previous tabs.  Which is super annoying.

  I told myself I'd leave it alone next time it happened and grab the
  logs.  Here they are.  Nothing super jumped out at me.

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

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


[Touch-packages] [Bug 1531845] Re: Xorg freeze

2016-01-07 Thread Xtien
** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1531845/+attachment/4545571/+files/dmesg.txt

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  I have multiple freezes per day, since a couple of months. I have gone
  back to Ubuntu 14.04, 15.04, same result. I have bought a new graphics
  card (went from GEforce460 to GEforce970), no change. I have a new cpu
  and motherboard, same result.

  What I see is that in System Monitor, CPU2 or CPU3 (there's 12, only 2 or 3 
go to 100% during freeze) goes to 100% and stays there for 5 or more minutes. 
All other CPUs are at less than 5%. In the "processes" tab no processes use 
significant CPU. But when I go to a shell (ctrl-alt-F2) and type "top", I see 
Xorg taking ~50% CPU and 2.4% memory. 
  I can trigger this by starting Android Studio. Sometimes it happens in Gedit 
loading a large file, or in a shell window. I tried different versions of AS, 
different versions of Gradle, tried Oracle java instead of openjdk, no change.  
Most of the times, Firefox also freezes after a short while, then everything 
freezes. The freeze does stop, after a maximum of 15 minutes. Sometimes, I need 
to do a hard reboot. 

  First time I saw this "one cpu at 100%" was in August of 2014, which may be 
when I first used Android Studio and Gradle. Unfortunately, going back to 
Eclipse and ant is not an option. 
  This takes about an hour of my time every day, so I'm willing to put a lot of 
effort in solving this.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
  Uname: Linux 4.2.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  352.63  Sat Nov  7 21:25:42 
PST 2015
   GCC version:  gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2)
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  BootLog:
   
  CurrentDesktop: Unity
  Date: Thu Jan  7 13:12:34 2016
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Since before I upgraded
  GraphicsCard:
   NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:3205]
  InstallationDate: Installed on 2015-12-13 (24 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: MSI MS-7881
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-23-generic.efi.signed 
root=UUID=eea1d4c7-5f21-40a5-b73d-fed6b0a48f69 ro noprompt persistent quiet 
splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/20/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.70
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X99S XPOWER AC (MS-7881)
  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.:bvr1.70:bd03/20/2015:svnMSI:pnMS-7881:pvr1.0:rvnMSI:rnX99SXPOWERAC(MS-7881):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7881
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Thu Jan  7 13:11:54 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech USB Optical Mouse MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.

[Touch-packages] [Bug 1528297] Re: libvpx FTBFS with gcc 5.3 on armhf

2016-01-07 Thread Olivier Tilloy
Bug reported upstream:
https://bugs.chromium.org/p/webm/issues/detail?id=1126.

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

Title:
  libvpx FTBFS with gcc 5.3 on armhf

Status in firefox package in Ubuntu:
  New
Status in gcc-5 package in Ubuntu:
  New
Status in libvpx package in Ubuntu:
  New
Status in oxide-qt package in Ubuntu:
  Fix Released

Bug description:
  (originally reported as bug #1527741)

  Trying to build libvpx from source in an up-to-date xenial arhmf
  environment, with gcc 5.3.1, fails with the following error:

  gcc  -marm -Wall -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -march=armv6 -DNDEBUG -O2 -fPIC -U_FORTIFY_SOURCE 
-D_FORTIFY_SOURCE=0 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -Wall 
-Wdeclaration-after-statement -Wdisabled-optimization -Wpointer-arith 
-Wtype-limits -Wcast-qual -Wvla -Wimplicit-function-declaration -Wuninitialized 
-Wunused-variable -Wunused-but-set-variable -Wno-unused-function -I. 
-I"/tmp/libvpx-1.4.0" -c -o vp8/common/treecoder.c.o 
/tmp/libvpx-1.4.0/vp8/common/treecoder.c
  /tmp/libvpx-1.4.0/vp8/common/treecoder.c: In function 'tree2tok':
  /tmp/libvpx-1.4.0/vp8/common/treecoder.c:32:9: error: invalid use of array 
with unspecified bounds
   const vp8_tree_index j = t[i++];
   ^
  /tmp/libvpx-1.4.0/vp8/common/treecoder.c:32:34: warning: initialization makes 
integer from pointer without a cast [-Wint-conversion]
   const vp8_tree_index j = t[i++];
^
  /tmp/libvpx-1.4.0/vp8/common/treecoder.c: In function 'branch_counts':
  /tmp/libvpx-1.4.0/vp8/common/treecoder.c:96:13: error: invalid use of array 
with unspecified bounds
   i = tree[ i + b];
   ^
  /tmp/libvpx-1.4.0/vp8/common/treecoder.c:96:15: warning: assignment makes 
integer from pointer without a cast [-Wint-conversion]
   i = tree[ i + b];
 ^
  Makefile:148: recipe for target 'vp8/common/treecoder.c.o' failed

  
  I’m attaching a full build log. This is reproducible both on a porter box and 
in a armhf chroot.

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

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


[Touch-packages] [Bug 1531824] Re: Xorg freeze

2016-01-07 Thread Phill
** Attachment added: "i915_error_state taken from the terminal during a freeze."
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1531824/+attachment/4545516/+files/i915_error_state

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Symptoms:

  * Video is frozen.

  Observations:

  * Mouse moves normally.
  * There is no hard-disc activity.
  * Once  minute or so the video will respond like it's doing so a frame at a 
time.
  * Pressing CTRL+ALT+F6 and then waiting a minute or so puts you into a 
terminal.
  * Text terminals work normally without any problems.
  * Pressing ALT+F7 from a text terminal puts you into either black frozen 
screen or a frozen graphical display.
  * Restarting LightDM doesn't resolve the problem, it shows the login screen 
and freezes.

  When does it occur:

  * More often than not on or immediately after resume from suspend.
  * Occasionally, but not very often, during normal use.
  * It occurs several times a week, usually after several hours of suspend.

  It started a few months ago.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-57.77~14.04.1-generic 3.16.7-ckt20
  Uname: Linux 3.16.0-57-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  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: Thu Jan  7 11:29:40 2016
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.34, 3.16.0-56-generic, x86_64: installed
   virtualbox, 4.3.34, 3.16.0-57-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e22] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8276]
 Subsystem: ASUSTeK Computer Inc. Device [1043:8276]
  InstallationDate: Installed on 2015-07-13 (177 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: System manufacturer V-P5G45
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-57-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0405
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: V-P5G45
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0405:bd05/18/2009:svnSystemmanufacturer:pnV-P5G45:pvrSystemVersion:rvnASUSTeKComputerINC.:rnV-P5G45:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: V-P5G45
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  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: Thu Jan  7 11:11:57 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   41085 
   vendor DEL
  xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

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

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


[Touch-packages] [Bug 1531824] Re: Xorg freeze

2016-01-07 Thread Phill
** Attachment added: "Xorg.0.log taken from the terminal during a freeze."
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1531824/+attachment/4545515/+files/Xorg.0.log

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Symptoms:

  * Video is frozen.

  Observations:

  * Mouse moves normally.
  * There is no hard-disc activity.
  * Once  minute or so the video will respond like it's doing so a frame at a 
time.
  * Pressing CTRL+ALT+F6 and then waiting a minute or so puts you into a 
terminal.
  * Text terminals work normally without any problems.
  * Pressing ALT+F7 from a text terminal puts you into either black frozen 
screen or a frozen graphical display.
  * Restarting LightDM doesn't resolve the problem, it shows the login screen 
and freezes.

  When does it occur:

  * More often than not on or immediately after resume from suspend.
  * Occasionally, but not very often, during normal use.
  * It occurs several times a week, usually after several hours of suspend.

  It started a few months ago.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-57.77~14.04.1-generic 3.16.7-ckt20
  Uname: Linux 3.16.0-57-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  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: Thu Jan  7 11:29:40 2016
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.34, 3.16.0-56-generic, x86_64: installed
   virtualbox, 4.3.34, 3.16.0-57-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e22] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8276]
 Subsystem: ASUSTeK Computer Inc. Device [1043:8276]
  InstallationDate: Installed on 2015-07-13 (177 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: System manufacturer V-P5G45
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-57-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0405
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: V-P5G45
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0405:bd05/18/2009:svnSystemmanufacturer:pnV-P5G45:pvrSystemVersion:rvnASUSTeKComputerINC.:rnV-P5G45:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: V-P5G45
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  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: Thu Jan  7 11:11:57 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   41085 
   vendor DEL
  xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

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

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


[Touch-packages] [Bug 1531824] [NEW] Xorg freeze

2016-01-07 Thread Phill
Public bug reported:

Symptoms:

* Video is frozen.

Observations:

* Mouse moves normally.
* There is no hard-disc activity.
* Once  minute or so the video will respond like it's doing so a frame at a 
time.
* Pressing CTRL+ALT+F6 and then waiting a minute or so puts you into a terminal.
* Text terminals work normally without any problems.
* Pressing ALT+F7 from a text terminal puts you into either black frozen screen 
or a frozen graphical display.
* Restarting LightDM doesn't resolve the problem, it shows the login screen and 
freezes.

When does it occur:

* More often than not on or immediately after resume from suspend.
* Occasionally, but not very often, during normal use.
* It occurs several times a week, usually after several hours of suspend.

It started a few months ago.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.16.0-57.77~14.04.1-generic 3.16.7-ckt20
Uname: Linux 3.16.0-57-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.19
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: Thu Jan  7 11:29:40 2016
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 4.3.34, 3.16.0-56-generic, x86_64: installed
 virtualbox, 4.3.34, 3.16.0-57-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a week
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Since a couple weeks or more
GraphicsCard:
 Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e22] 
(rev 03) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:8276]
   Subsystem: ASUSTeK Computer Inc. Device [1043:8276]
InstallationDate: Installed on 2015-07-13 (177 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
MachineType: System manufacturer V-P5G45
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-57-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/18/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0405
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: V-P5G45
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0405:bd05/18/2009:svnSystemmanufacturer:pnV-P5G45:pvrSystemVersion:rvnASUSTeKComputerINC.:rnV-P5G45:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: V-P5G45
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
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: Thu Jan  7 11:11:57 2016
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   41085 
 vendor DEL
xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

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


** Tags: amd64 apport-bug compiz-0.9 freeze 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/1531824

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Symptoms:

  * Video is frozen.

  Observations:

  * Mouse moves normally.
  * There is no hard-disc activity.
  * Once  minute or so the video will respond like it's doing so a frame at a 
time.
  * Pressing CTRL+ALT+F6 and then waiting a minute or so puts you into a 
terminal.
  * Text terminals work normally without any problems.
  * Pressing ALT+F7 from a text terminal puts you into either black frozen 
screen or a frozen graphical display.
  * Restarting LightDM doesn't resolve the problem, it shows the login screen 
and freezes.

  When does it occur:

  * More often than not on or immediately after resume from suspend.
  * Occasionally, but not very often, during normal use.
  * It oc

[Touch-packages] [Bug 1531817] Re: import statements broken in uitk documentation

2016-01-07 Thread Andrea Bernabei
that line is automatically generated.

I believe this is happening because of http://bazaar.launchpad.net
/~ubuntu-sdk-team/ubuntu-ui-toolkit/staging/view/head:/documentation
/ubuntu-ui-toolkit-common.qdocconf#L32

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

Title:
  import statements broken in uitk documentation

Status in Client Developer Experience:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  It says:

  Since 1.3
  Import statement: 1.2

  http://i.imgur.com/KZMpObN.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-developer-experience/+bug/1531817/+subscriptions

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


[Touch-packages] [Bug 1531815] [NEW] Syntax highlighting broken for UbuntuShape

2016-01-07 Thread Michael Zanetti
Public bug reported:

Syntax highlighting not working for UbuntuShape, and with that also no
code completion for it:

http://i.imgur.com/sh3aogD.png

** Affects: canonical-developer-experience
 Importance: Undecided
 Status: New

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: ubuntu-ui-toolkit
   Importance: Undecided
   Status: New

** Project changed: ubuntu-ui-toolkit => ubuntu-ui-toolkit (Ubuntu)

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

Title:
  Syntax highlighting broken for UbuntuShape

Status in Client Developer Experience:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  Syntax highlighting not working for UbuntuShape, and with that also no
  code completion for it:

  http://i.imgur.com/sh3aogD.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-developer-experience/+bug/1531815/+subscriptions

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


[Touch-packages] [Bug 1531817] [NEW] import statements broken in uitk documentation

2016-01-07 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

It says:

Since 1.3
Import statement: 1.2

http://i.imgur.com/KZMpObN.png

** Affects: canonical-developer-experience
 Importance: Undecided
 Status: New

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Undecided
 Status: New

-- 
import statements broken in uitk documentation
https://bugs.launchpad.net/bugs/1531817
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to ubuntu-ui-toolkit 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 1531807] Re: Option rfc3442-classless-static-routes doesn't work anymore?

2016-01-07 Thread sokoow
never mind, it was missing option rfc3442-classless-static-routes code
121 = array of integer 8; in the config, sorry :)

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

Title:
  Option rfc3442-classless-static-routes doesn't work anymore?

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  I'm getting problems after upgrading to 4.3.1, seems like  rfc3442
  -classless-static-routes option doesn't seem to be parsed correctly
  anymore ? Is this by design? Also, I can't find any mention of it in
  4.3.1's source code.

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

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


[Touch-packages] [Bug 1531807] Re: Option rfc3442-classless-static-routes doesn't work anymore?

2016-01-07 Thread sokoow
line 21: unknown option dhcp.rfc3442-classless-static-routes

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

Title:
  Option rfc3442-classless-static-routes doesn't work anymore?

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  I'm getting problems after upgrading to 4.3.1, seems like  rfc3442
  -classless-static-routes option doesn't seem to be parsed correctly
  anymore ? Is this by design? Also, I can't find any mention of it in
  4.3.1's source code.

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

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


[Touch-packages] [Bug 1531808] [NEW] plugin info broken for Ubuntu.Components

2016-01-07 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

import Ubuntu.Components gives this error:

http://i.imgur.com/kgSxmDG.png

** Affects: canonical-developer-experience
 Importance: Undecided
 Status: New

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Undecided
 Status: New

-- 
plugin info broken for Ubuntu.Components
https://bugs.launchpad.net/bugs/1531808
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to ubuntu-ui-toolkit 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 1531804] [NEW] [desktop] Browser crashes when downloading a file

2016-01-07 Thread Olivier Tilloy
Public bug reported:

Steps to reproduce:

 - on a desktop setup (xenial from the repositories, or wily from
https://launchpad.net/~osomon/+archive/ubuntu/webbrowser-app), with
qtdeclarative5-ubuntu-content1 and qtdeclarative5-ubuntu-download-
manager0.1 installed, run webbrowser-app, point it to a page that has a
link to e.g. a PDF document (e.g. https://help.ubuntu.com/), and click
that link

Expected result: the file is downloaded

Current result: crash with the following stacktrace:

#0  QDBusAbstractInterface::asyncCallWithArgumentList (this=0x0, method=..., 
args=...)
at qdbusabstractinterface.cpp:501
#1  0x7fffc448a70a in ?? () from 
/usr/lib/x86_64-linux-gnu/libubuntu-download-manager-client.so.1
#2  0x7fffb2b28717 in 
Ubuntu::DownloadManager::SingleDownload::setAllowMobileDownload(bool) ()
   from 
/usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/DownloadManager/libUbuntuDownloadManager.so
#3  0x7fffb2b2ad64 in 
Ubuntu::DownloadManager::SingleDownload::bindDownload(Ubuntu::DownloadManager::Download*)
 ()
   from 
/usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/DownloadManager/libUbuntuDownloadManager.so
#4  0x7682f617 in QtPrivate::QSlotObjectBase::call (a=0x7fffd370, 
r=0x2fc02d0, this=)
at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#5  QMetaObject::activate (sender=0x30d4010, signalOffset=, 
local_signal_index=, 
argv=) at kernel/qobject.cpp:3702
#6  0x7fffc44b3def in 
Ubuntu::DownloadManager::Manager::downloadCreated(Ubuntu::DownloadManager::Download*)
 ()
   from /usr/lib/x86_64-linux-gnu/libubuntu-download-manager-client.so.1
#7  0x7fffc44af328 in ?? () from 
/usr/lib/x86_64-linux-gnu/libubuntu-download-manager-client.so.1
#8  0x7682f617 in QtPrivate::QSlotObjectBase::call (a=0x7fffd630, 
r=0x30ccef0, this=)
at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#9  QMetaObject::activate (sender=0x30ccef0, signalOffset=, 
local_signal_index=local_signal_index@entry=0, 
argv=argv@entry=0x7fffd630) at kernel/qobject.cpp:3702
#10 0x7682ff87 in QMetaObject::activate (sender=, 
m=m@entry=0x7fffec80d680 , 
local_signal_index=local_signal_index@entry=0, 
argv=argv@entry=0x7fffd630) at kernel/qobject.cpp:3582
#11 0x7fffec7f110f in QDBusPendingCallWatcher::finished (this=, _t1=0x30ccef0)
at .moc/moc_qdbuspendingcall.cpp:147
#12 0x7fffec7f2815 in QDBusPendingCallWatcherPrivate::_q_finished 
(this=)
at qdbuspendingcall.cpp:487
#13 QDBusPendingCallWatcher::qt_static_metacall (_o=, 
_c=, _id=, 
_a=) at .moc/moc_qdbuspendingcall.cpp:79
#14 0x76830651 in QObject::event (this=0x30ccef0, e=) at 
kernel/qobject.cpp:1245
#15 0x778b1b8c in QApplicationPrivate::notify_helper 
(this=this@entry=0x6eece0, 
receiver=receiver@entry=0x30ccef0, e=e@entry=0x2cfcd40) at 
kernel/qapplication.cpp:3720
#16 0x778b7230 in QApplication::notify (this=0x7fffdc60, 
receiver=0x30ccef0, e=0x2cfcd40)
at kernel/qapplication.cpp:3503
#17 0x767fef1b in QCoreApplication::notifyInternal 
(this=0x7fffdc60, receiver=0x30ccef0, 
event=event@entry=0x2cfcd40) at kernel/qcoreapplication.cpp:935
#18 0x76801057 in QCoreApplication::sendEvent (event=0x2cfcd40, 
receiver=)
at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:228
#19 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, 
event_type=event_type@entry=0, data=0x6eee50)
at kernel/qcoreapplication.cpp:1552
#20 0x76801588 in QCoreApplication::sendPostedEvents 
(receiver=receiver@entry=0x0, event_type=event_type@entry=0)
at kernel/qcoreapplication.cpp:1410
#21 0x76855e73 in postEventSourceDispatch (s=0x7e95c0) at 
kernel/qeventdispatcher_glib.cpp:271
#22 0x751dbff7 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x751dc250 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x751dc2fc in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x7685627f in QEventDispatcherGlib::processEvents (this=0x802be0, 
flags=...) at kernel/qeventdispatcher_glib.cpp:418
#26 0x767fc75a in QEventLoop::exec (this=this@entry=0x7fffdbb0, 
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#27 0x768042cc in QCoreApplication::exec () at 
kernel/qcoreapplication.cpp:1188
#28 0x00466908 in BrowserApplication::run() ()
#29 0x0045b8dd in main ()

** Affects: webbrowser-app (Ubuntu)
 Importance: Critical
 Assignee: Michael Sheldon (michael-sheldon)
 Status: New

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

Title:
  [desktop] Browser crashes when downloading a file

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

   - on a desktop setup (xenial

[Touch-packages] [Bug 1531685] Re: package ifupdown 0.8.5ubuntu1 failed to install/upgrade: Unterprozess installiertes pre-removal-Skript gab den Fehlerwert 1 zurück

2016-01-07 Thread Martin Pitt
** Changed in: ifupdown (Ubuntu)
   Status: In Progress => Fix Committed

** Changed in: ifupdown (Ubuntu)
Milestone: None => ubuntu-16.01

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

Title:
  package ifupdown 0.8.5ubuntu1 failed to install/upgrade: Unterprozess
  installiertes pre-removal-Skript gab den Fehlerwert 1 zurück

Status in ifupdown package in Ubuntu:
  Fix Committed
Status in ifupdown package in Debian:
  Unknown

Bug description:
  iz happend after a partly system upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ifupdown 0.8.5ubuntu1
  ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
  Uname: Linux 4.3.0-5-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  Date: Tue Jan  5 18:06:39 2016
  ErrorMessage: Unterprozess installiertes pre-removal-Skript gab den 
Fehlerwert 1 zurück
  InstallationDate: Installed on 2015-11-28 (39 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151128)
  RelatedPackageVersions:
   dpkg 1.18.3ubuntu1
   apt  1.1.10
  SourcePackage: ifupdown
  Title: package ifupdown 0.8.5ubuntu1 failed to install/upgrade: Unterprozess 
installiertes pre-removal-Skript gab den Fehlerwert 1 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


  1   2   >