date:20160519

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

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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1583879

Title:
  apt-get update hangs indefinitely, appstreamcli using 100% CPU

Status in appstream package in Ubuntu:
  Confirmed

Bug description:
  Just ran `sudo apt-get update`, which is hanging indefinitely after
  the downloads complete, the last CLI output from which is:

  Fetched 733 kB in 1s (399 kB/s)

  Looking at `top` suggests `appstreamcli` is the culprit as it's pegged
  at near 100% CPU usage:

   100  0.1  18:29.02 appstreamcli

  If I kill the hung `sudo apt-get update` process with Control+C, the
  `appstreamcli` process goes away.

  Retrying `sudo apt-get update` has the same result.

  On a whim I also tried `sudo apt update`, but it seems to have the
  same problem. It hangs indefinitely and running it results in an
  `appstreamcli` process consuming 100% CPU.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: appstream 0.9.4-1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May 19 20:53:40 2016
  SourcePackage: appstream
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1579712] Re: Refresh hangs indefinitely, appstreamcli using 100% CPU

2016-05-19 Thread Neil Mayhew

The simplest workaround seems to be to use Ctrl-C when apt update hangs
at the end. It's already done most of the work, and this just aborts the
running of appstreamcli at the end. You can then go ahead and update any
binary packages built from the appstream source package (ie any of
appstream appstream-doc appstream-index gir1.2-appstream libappstream-
dev libappstream3 libappstreamqt-dev libappstreamqt1 that are already
installed). The use of appstreamcli in the postinst shouldn't hang
because the new versions of appstreamcli and libappstream.so.3 will
already be in place.

However, using Ctrl-C is possible only when using the command line. I'm
not sure what happens if someone is using Synaptic or Gnome Software. I
assume it would be necessary to use System Monitor to kill off
appstreamcli. I'm concerned that we could see breakage in a very large
number of Xenial installations, all of which would require manual
intervention to get them unstuck.

The fact that this is happening now, when it hasn't been reported in the
past 3 years, must be due to a subtle change in the execution
environment, maybe due to updates in other shared libraries that
appstreamcli uses. The problem is a result of reading uninitialized
memory, and in the past it must have been pure luck that the memory
always contained zeroes.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1579712

Title:
  Refresh hangs indefinitely, appstreamcli using 100% CPU

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
   * Fixing this bug resolves the issue for people who might experience it.
   * See https://github.com/ximion/appstream/issues/35 for details.

  [Test Case 1]

   * Run `sudo appstreamcli refresh --force`
   * The AppStream cache should be updated, no change in behavior should be 
seen.

  [Test Case 2]

   * In case you were experiencing the almost-infinite hang when running
  `sudo appstreamcli refresh --force`, this issue should be fixed with
  the SRU.

  [Regression Potential]

   * Very low, since this only fixes the decompression code. There
  should be no sideeffects of that (given that the patch itself doesn't
  break anything, which it shouldn't, since it has been tested upstream
  for a while)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
   * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a

  

  /!\ Installing the bugfix from xenial-proposed, without going through APT:
  To install the fixed packages manually, please execute the following commands 
(for amd64, adjust URLs for other architectures):

  ```
  cd /tmp && mkdir asfix
  cd asfix
  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/appstream_0.9.4-1ubuntu1_amd64.deb
  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libappstream3_0.9.4-1ubuntu1_amd64.deb
  sudo dpkg -i libappstream3*.deb
  sudo dpkg -i appstream*.deb
  ```

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

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

[Desktop-packages] [Bug 1579712] Re: Refresh hangs indefinitely, appstreamcli using 100% CPU

2016-05-19 Thread Dennis W.

i had problems today to make "sudo apt update" it don't went away so
that i can got "sudo apt dist-upgrade"

i can terminate appstreamcli in system-monitor but that loading not all
packets

This fix has "repaired" the Problem, i quete the #24

After this working there came any Pakets it wont's to have install, is
that normally and or regulate Updates ?

"Weird, I wonder what happened that many people are experiencing this now...
Removing `/usr/bin/appstreamcli` is fine if you install the fixed package 
afterwards.

To install this manually, please do (for amd64, adjust URLs for other
architectures):

```
cd /tmp && mkdir asfix
cd asfix
wget 
https://launchpad.net/ubuntu/+archive/primary/+files/appstream_0.9.4-1ubuntu1_amd64.deb
wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libappstream3_0.9.4-1ubuntu1_amd64.deb
sudo dpkg -i *.deb
```

This should solve the issue. Please report back if this is fixed, or if
you are still experiencing issues!"

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1579712

Title:
  Refresh hangs indefinitely, appstreamcli using 100% CPU

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
   * Fixing this bug resolves the issue for people who might experience it.
   * See https://github.com/ximion/appstream/issues/35 for details.

  [Test Case 1]

   * Run `sudo appstreamcli refresh --force`
   * The AppStream cache should be updated, no change in behavior should be 
seen.

  [Test Case 2]

   * In case you were experiencing the almost-infinite hang when running
  `sudo appstreamcli refresh --force`, this issue should be fixed with
  the SRU.

  [Regression Potential]

   * Very low, since this only fixes the decompression code. There
  should be no sideeffects of that (given that the patch itself doesn't
  break anything, which it shouldn't, since it has been tested upstream
  for a while)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
   * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a

  

  /!\ Installing the bugfix from xenial-proposed, without going through APT:
  To install the fixed packages manually, please execute the following commands 
(for amd64, adjust URLs for other architectures):

  ```
  cd /tmp && mkdir asfix
  cd asfix
  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/appstream_0.9.4-1ubuntu1_amd64.deb
  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libappstream3_0.9.4-1ubuntu1_amd64.deb
  sudo dpkg -i libappstream3*.deb
  sudo dpkg -i appstream*.deb
  ```

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

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

[Desktop-packages] [Bug 1579712] Re: Refresh hangs indefinitely, appstreamcli using 100% CPU

2016-05-19 Thread Set Hallstrom

Might be completely unrelated, but i noticed most mirrors have this
weird loop:
http://ubuntu.mirror.su.se/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/

i write "most", but I haven't yet found any mirror that hasn't got it.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1579712

Title:
  Refresh hangs indefinitely, appstreamcli using 100% CPU

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
   * Fixing this bug resolves the issue for people who might experience it.
   * See https://github.com/ximion/appstream/issues/35 for details.

  [Test Case 1]

   * Run `sudo appstreamcli refresh --force`
   * The AppStream cache should be updated, no change in behavior should be 
seen.

  [Test Case 2]

   * In case you were experiencing the almost-infinite hang when running
  `sudo appstreamcli refresh --force`, this issue should be fixed with
  the SRU.

  [Regression Potential]

   * Very low, since this only fixes the decompression code. There
  should be no sideeffects of that (given that the patch itself doesn't
  break anything, which it shouldn't, since it has been tested upstream
  for a while)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
   * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a

  

  /!\ Installing the bugfix from xenial-proposed, without going through APT:
  To install the fixed packages manually, please execute the following commands 
(for amd64, adjust URLs for other architectures):

  ```
  cd /tmp && mkdir asfix
  cd asfix
  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/appstream_0.9.4-1ubuntu1_amd64.deb
  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libappstream3_0.9.4-1ubuntu1_amd64.deb
  sudo dpkg -i libappstream3*.deb
  sudo dpkg -i appstream*.deb
  ```

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

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

[Desktop-packages] [Bug 1579712] Re: Refresh hangs indefinitely, appstreamcli using 100% CPU

2016-05-19 Thread Boenadi Agustian

As per Matthias' comment #24, not working for i386

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1579712

Title:
  Refresh hangs indefinitely, appstreamcli using 100% CPU

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
   * Fixing this bug resolves the issue for people who might experience it.
   * See https://github.com/ximion/appstream/issues/35 for details.

  [Test Case 1]

   * Run `sudo appstreamcli refresh --force`
   * The AppStream cache should be updated, no change in behavior should be 
seen.

  [Test Case 2]

   * In case you were experiencing the almost-infinite hang when running
  `sudo appstreamcli refresh --force`, this issue should be fixed with
  the SRU.

  [Regression Potential]

   * Very low, since this only fixes the decompression code. There
  should be no sideeffects of that (given that the patch itself doesn't
  break anything, which it shouldn't, since it has been tested upstream
  for a while)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
   * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a

  

  /!\ Installing the bugfix from xenial-proposed, without going through APT:
  To install the fixed packages manually, please execute the following commands 
(for amd64, adjust URLs for other architectures):

  ```
  cd /tmp && mkdir asfix
  cd asfix
  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/appstream_0.9.4-1ubuntu1_amd64.deb
  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libappstream3_0.9.4-1ubuntu1_amd64.deb
  sudo dpkg -i libappstream3*.deb
  sudo dpkg -i appstream*.deb
  ```

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

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

[Desktop-packages] [Bug 1579712] Re: Refresh hangs indefinitely, appstreamcli using 100% CPU

2016-05-19 Thread Boenadi Agustian

As per Matthias' comment #24, not working for i386 all package for i386
still get stuck and appstreamcli get 100%

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1579712

Title:
  Refresh hangs indefinitely, appstreamcli using 100% CPU

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
   * Fixing this bug resolves the issue for people who might experience it.
   * See https://github.com/ximion/appstream/issues/35 for details.

  [Test Case 1]

   * Run `sudo appstreamcli refresh --force`
   * The AppStream cache should be updated, no change in behavior should be 
seen.

  [Test Case 2]

   * In case you were experiencing the almost-infinite hang when running
  `sudo appstreamcli refresh --force`, this issue should be fixed with
  the SRU.

  [Regression Potential]

   * Very low, since this only fixes the decompression code. There
  should be no sideeffects of that (given that the patch itself doesn't
  break anything, which it shouldn't, since it has been tested upstream
  for a while)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
   * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a

  

  /!\ Installing the bugfix from xenial-proposed, without going through APT:
  To install the fixed packages manually, please execute the following commands 
(for amd64, adjust URLs for other architectures):

  ```
  cd /tmp && mkdir asfix
  cd asfix
  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/appstream_0.9.4-1ubuntu1_amd64.deb
  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libappstream3_0.9.4-1ubuntu1_amd64.deb
  sudo dpkg -i libappstream3*.deb
  sudo dpkg -i appstream*.deb
  ```

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

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

[Desktop-packages] [Bug 1579712] Re: Refresh hangs indefinitely, appstreamcli using 100% CPU

2016-05-19 Thread Edwin Khoo

This bug appears to also affect clean 16.04 installs as of today.
Specifically, the installer gets stuck at "Retrieving file 56 of 56".

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1579712

Title:
  Refresh hangs indefinitely, appstreamcli using 100% CPU

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
   * Fixing this bug resolves the issue for people who might experience it.
   * See https://github.com/ximion/appstream/issues/35 for details.

  [Test Case 1]

   * Run `sudo appstreamcli refresh --force`
   * The AppStream cache should be updated, no change in behavior should be 
seen.

  [Test Case 2]

   * In case you were experiencing the almost-infinite hang when running
  `sudo appstreamcli refresh --force`, this issue should be fixed with
  the SRU.

  [Regression Potential]

   * Very low, since this only fixes the decompression code. There
  should be no sideeffects of that (given that the patch itself doesn't
  break anything, which it shouldn't, since it has been tested upstream
  for a while)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
   * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a

  

  /!\ Installing the bugfix from xenial-proposed, without going through APT:
  To install the fixed packages manually, please execute the following commands 
(for amd64, adjust URLs for other architectures):

  ```
  cd /tmp && mkdir asfix
  cd asfix
  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/appstream_0.9.4-1ubuntu1_amd64.deb
  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libappstream3_0.9.4-1ubuntu1_amd64.deb
  sudo dpkg -i libappstream3*.deb
  sudo dpkg -i appstream*.deb
  ```

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

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

[Desktop-packages] [Bug 1577316] Re: LibreOffice Base Crash when i try to connect to mysql

2016-05-19 Thread Fred Saunier

On Xenial, the problem appears to be solved with LO 5.1.3 -- connection
to database in native MySQL is now stable.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1577316

Title:
  LibreOffice Base Crash when i try to connect to mysql

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  When I try to connect to my mysql database via libreoffice base , this
  one closes it without providing crash report.

  
  lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  apt-cache policy libreoffice-base
  libreoffice-base:
Installé : 1:5.1.2-0ubuntu1
Candidat : 1:5.1.2-0ubuntu1
   
  apt-cache policy libreoffice-mysql-connector 
  libreoffice-mysql-connector:
Installé : 1.0.2+LibO5.1.2-0ubuntu1
Candidat : 1.0.2+LibO5.1.2-0ubuntu1

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

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

[Desktop-packages] [Bug 1583862] Re: apt-get update hangs after hit/get

2016-05-19 Thread Anders Trier Olesen

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

** This bug has been marked a duplicate of bug 1579712
   Refresh hangs indefinitely, appstreamcli using 100% CPU

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1583862

Title:
  apt-get update hangs after hit/get

Status in appstream package in Ubuntu:
  Confirmed

Bug description:
  After typing "sudo apt-get update" the following happens, but then it hangs:
  Hit:1 http://us.archive.ubuntu.com/ubuntu xenial InRelease
  Ign:2 http://dl.google.com/linux/chrome/deb stable InRelease  
 
  Get:3 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [94.5 kB]  
 
  Hit:4 http://dl.google.com/linux/chrome/deb stable Release
 
  Hit:5 http://apt.postgresql.org/pub/repos/apt xenial-pgdg InRelease   
 
  Get:6 http://security.ubuntu.com/ubuntu xenial-security InRelease [94.5 kB]   
 
  Get:7 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease [92.2 
kB] 
  Hit:9 http://ppa.launchpad.net/neovim-ppa/unstable/ubuntu xenial InRelease
 
  Hit:10 https://deb.nodesource.com/node_6.x xenial InRelease   
 
  Fetched 281 kB in 0s (366 kB/s)

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  apt:
Installed: 1.2.10ubuntu1
Candidate: 1.2.10ubuntu1
Version table:
   *** 1.2.10ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.10ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May 19 21:42:52 2016
  InstallationDate: Installed on 2016-04-27 (23 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1579712] Re: Refresh hangs indefinitely, appstreamcli using 100% CPU

2016-05-19 Thread Deep Kumar Halwai

As per Matthias' comment #24, deleting the rm /usr/bin/appstreamcli and
installing the .deb packages worked for me as well.

Thank you Matthias'

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1579712

Title:
  Refresh hangs indefinitely, appstreamcli using 100% CPU

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
   * Fixing this bug resolves the issue for people who might experience it.
   * See https://github.com/ximion/appstream/issues/35 for details.

  [Test Case 1]

   * Run `sudo appstreamcli refresh --force`
   * The AppStream cache should be updated, no change in behavior should be 
seen.

  [Test Case 2]

   * In case you were experiencing the almost-infinite hang when running
  `sudo appstreamcli refresh --force`, this issue should be fixed with
  the SRU.

  [Regression Potential]

   * Very low, since this only fixes the decompression code. There
  should be no sideeffects of that (given that the patch itself doesn't
  break anything, which it shouldn't, since it has been tested upstream
  for a while)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
   * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a

  

  /!\ Installing the bugfix from xenial-proposed, without going through APT:
  To install the fixed packages manually, please execute the following commands 
(for amd64, adjust URLs for other architectures):

  ```
  cd /tmp && mkdir asfix
  cd asfix
  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/appstream_0.9.4-1ubuntu1_amd64.deb
  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libappstream3_0.9.4-1ubuntu1_amd64.deb
  sudo dpkg -i libappstream3*.deb
  sudo dpkg -i appstream*.deb
  ```

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

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

[Desktop-packages] [Bug 1581106] Re: [yakkety regression] lightdm fails to install in a minimal environment

** Branch linked: lp:lightdm

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1581106

Title:
  [yakkety regression] lightdm fails to install in a minimal environment

Status in lightdm package in Ubuntu:
  Fix Committed

Bug description:
  systemd's cmdline-upstart-boot autopkgtest started to fail in yakkety
  [1] due to

  Setting up lightdm (1.19.0-0ubuntu1) ...
  Adding group `lightdm' (GID 116) ...
  Done.
  Adding system user `lightdm' (UID 112) ...
  Adding new user `lightdm' (UID 112) with group `lightdm' ...
  Creating home directory `/var/lib/lightdm' ...
  usermod: no changes
  usermod: no changes
  usermod: no changes
  Adding group `nopasswdlogin' (GID 117) ...
  Done.
  Job for lightdm.service failed because the control process exited with error 
code. See "systemctl status lightdm.service" and "journalctl -xe" for details.
  invoke-rc.d: initscript lightdm, action "start" failed.
  dpkg: error processing package lightdm (--configure):
   subprocess installed post-installation script returned error exit status 1

  This is reproducible in a cloud instance/VM (or a server install, etc)
  with

sudo apt-get install lightdm --no-install-recommends

  $ sudo lightdm -d
  [+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
  [+0.00s] DEBUG: Starting Light Display Manager 1.19.0, UID=0 PID=2262
  [+0.00s] DEBUG: Loading configuration dirs from 
/usr/share/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/50-disable-log-backup.conf
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/local/share/lightdm/lightdm.conf.d
  [+0.02s] DEBUG: Loading configuration dirs from 
/etc/xdg/lightdm/lightdm.conf.d
  [+0.02s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
  [+0.02s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
  [+0.02s] DEBUG: Registered seat module xlocal
  [+0.02s] DEBUG: Registered seat module xremote
  [+0.02s] DEBUG: Registered seat module unity
  [+0.03s] DEBUG: Monitoring logind for seats
  [+0.03s] DEBUG: New seat added from logind: seat0
  [+0.03s] DEBUG: Seat seat0: Loading properties from config section Seat:*
  [+0.03s] DEBUG: Seat seat0: Starting
  [+0.03s] DEBUG: Seat seat0: Creating greeter session
  [+0.04s] DEBUG: Seat seat0: Failed to find session configuration default
  [+0.04s] DEBUG: Seat seat0: Failed to create greeter session
  [+0.04s] DEBUG: Failed to start seat: seat0

  So apparently something in 1.19 changed the handling of seats and now
  fails if there is no seat. That makes automated testing much harder as
  we don't have seats in these environments.

  [1]
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-yakkety/yakkety/amd64/s/systemd/20160512_140212@/log.gz

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: lightdm 1.19.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu3
  Architecture: amd64
  Date: Thu May 12 17:49:55 2016
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   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/1581106/+subscriptions

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

[Desktop-packages] [Bug 1581106] Re: [yakkety regression] lightdm fails to install in a minimal environment

2016-05-19 Thread Robert Ancell

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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1581106

Title:
  [yakkety regression] lightdm fails to install in a minimal environment

Status in lightdm package in Ubuntu:
  Fix Committed

Bug description:
  systemd's cmdline-upstart-boot autopkgtest started to fail in yakkety
  [1] due to

  Setting up lightdm (1.19.0-0ubuntu1) ...
  Adding group `lightdm' (GID 116) ...
  Done.
  Adding system user `lightdm' (UID 112) ...
  Adding new user `lightdm' (UID 112) with group `lightdm' ...
  Creating home directory `/var/lib/lightdm' ...
  usermod: no changes
  usermod: no changes
  usermod: no changes
  Adding group `nopasswdlogin' (GID 117) ...
  Done.
  Job for lightdm.service failed because the control process exited with error 
code. See "systemctl status lightdm.service" and "journalctl -xe" for details.
  invoke-rc.d: initscript lightdm, action "start" failed.
  dpkg: error processing package lightdm (--configure):
   subprocess installed post-installation script returned error exit status 1

  This is reproducible in a cloud instance/VM (or a server install, etc)
  with

sudo apt-get install lightdm --no-install-recommends

  $ sudo lightdm -d
  [+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
  [+0.00s] DEBUG: Starting Light Display Manager 1.19.0, UID=0 PID=2262
  [+0.00s] DEBUG: Loading configuration dirs from 
/usr/share/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/50-disable-log-backup.conf
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/local/share/lightdm/lightdm.conf.d
  [+0.02s] DEBUG: Loading configuration dirs from 
/etc/xdg/lightdm/lightdm.conf.d
  [+0.02s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
  [+0.02s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
  [+0.02s] DEBUG: Registered seat module xlocal
  [+0.02s] DEBUG: Registered seat module xremote
  [+0.02s] DEBUG: Registered seat module unity
  [+0.03s] DEBUG: Monitoring logind for seats
  [+0.03s] DEBUG: New seat added from logind: seat0
  [+0.03s] DEBUG: Seat seat0: Loading properties from config section Seat:*
  [+0.03s] DEBUG: Seat seat0: Starting
  [+0.03s] DEBUG: Seat seat0: Creating greeter session
  [+0.04s] DEBUG: Seat seat0: Failed to find session configuration default
  [+0.04s] DEBUG: Seat seat0: Failed to create greeter session
  [+0.04s] DEBUG: Failed to start seat: seat0

  So apparently something in 1.19 changed the handling of seats and now
  fails if there is no seat. That makes automated testing much harder as
  we don't have seats in these environments.

  [1]
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-yakkety/yakkety/amd64/s/systemd/20160512_140212@/log.gz

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: lightdm 1.19.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu3
  Architecture: amd64
  Date: Thu May 12 17:49:55 2016
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   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/1581106/+subscriptions

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

[Desktop-packages] [Bug 1292990] Re: lightdm overrides dh_installinit in debian/rules and shouldn't

2016-05-19 Thread Robert Ancell

Based on Martins issue I've reverted this change and added a comment.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1292990

Title:
  lightdm overrides dh_installinit in debian/rules and shouldn't

Status in lightdm package in Ubuntu:
  Fix Released

Bug description:
  The debian/rules for lightdm includes the following:

  override_dh_installinit:
  dh_installinit --no-start

  This appears to have been in place since the beginning of the
  package's history, with no reason given.  And the result of this
  override is that if you install lightdm on a running system, lightdm
  will not be automatically started at install time like it should be.

  Please drop this override from the package.

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

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

[Desktop-packages] [Bug 1583861] Re: Keyboard backlight isn't properly restored after idle on systems with hardwired configuration

2016-05-19 Thread Ubuntu Foundations Team Bug Bot

The attachment "upower-always-get-kbd-brightness.debdiff" seems to be a
debdiff.  The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff.  If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1583861

Title:
  Keyboard backlight isn't properly restored after idle on systems with
  hardwired configuration

Status in Dell Sputnik:
  New
Status in Upower:
  Unknown
Status in gnome-settings-daemon package in Ubuntu:
  New
Status in unity-settings-daemon package in Ubuntu:
  New
Status in upower package in Ubuntu:
  New

Bug description:
  In Dell or ThinkPad (for these you need a kernel which includes fix
  for lp:1574498) notebooks with keyboard backlight, the keybindings to
  control the keyboard backlight don't emit any event to the userland,
  about the state change, nor they request userland to change it (as it
  happens in other models which emits KEY_KBDILLUM{UP,DOWN,TOGGLE}
  events), this causes unity/gnome-settings daemon not to restore the
  proper backlight after idle.

  Steps to reproduce:
   0) ensure your keyboard backlight is on, and
   gdbus call --system --dest org.freedesktop.UPower \
    --object-path /org/freedesktop/UPower/KbdBacklight \
    --method org.freedesktop.UPower.KbdBacklight.GetBrightness
  returns a value != from 0. If not, just call the SetBrightness
  method with a positive value, to turn on the backlight.

  Now turn off the keyboard backlight (or set it to another level)
  using the laptop keys, and run:
   gsettings set org.gnome.desktop.session idle-delay 1
  to make things easier to test.

   2) Wait one second and the screensaver should start. Wait the screen to
  be turned off. If you just changed the brightness level at the step above,
  once the screen is turned off, also the keyboard backlight should be 
turned off too.

   3) Now press a key or move the mouse.

  Expected behavior:

   4) The keyboard backlight should be set back to the previous level (so it 
should stay off
  or go back to the level you set before the idle timeout happened).

  Actual behavior:

   5) The backlight is set to the level it had at point 0).

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1583861/+subscriptions

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

[Desktop-packages] [Bug 1583862] Re: apt-get update hangs after hit/get

2016-05-19 Thread Robert Hooker

killing appstream and changing archives apparently fixes it according to
the reddit thread

** Package changed: apt (Ubuntu) => appstream (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1583862

Title:
  apt-get update hangs after hit/get

Status in appstream package in Ubuntu:
  Confirmed

Bug description:
  After typing "sudo apt-get update" the following happens, but then it hangs:
  Hit:1 http://us.archive.ubuntu.com/ubuntu xenial InRelease
  Ign:2 http://dl.google.com/linux/chrome/deb stable InRelease  
 
  Get:3 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [94.5 kB]  
 
  Hit:4 http://dl.google.com/linux/chrome/deb stable Release
 
  Hit:5 http://apt.postgresql.org/pub/repos/apt xenial-pgdg InRelease   
 
  Get:6 http://security.ubuntu.com/ubuntu xenial-security InRelease [94.5 kB]   
 
  Get:7 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease [92.2 
kB] 
  Hit:9 http://ppa.launchpad.net/neovim-ppa/unstable/ubuntu xenial InRelease
 
  Hit:10 https://deb.nodesource.com/node_6.x xenial InRelease   
 
  Fetched 281 kB in 0s (366 kB/s)

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  apt:
Installed: 1.2.10ubuntu1
Candidate: 1.2.10ubuntu1
Version table:
   *** 1.2.10ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.10ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May 19 21:42:52 2016
  InstallationDate: Installed on 2016-04-27 (23 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1583883] Re: lightdm blocks login screen on non-english layout

2016-05-19 Thread Robert Ancell

** Package changed: lightdm (Ubuntu) => unity (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1583883

Title:
  lightdm blocks login screen on non-english layout

Status in unity package in Ubuntu:
  New

Bug description:
  Sometimes lightdm pops up after the sleep mode and proposes its own
  login screen without ability to change keyboard layout. How to fix it?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu May 19 10:41:43 2016
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2016-04-07 (41 days ago)

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

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

[Desktop-packages] [Bug 1571574] Re: 3G (WWAN) icon missing in network-manager-applet

2016-05-19 Thread Pascal Morin

@Sebastien & Aron

The syslog is now included; Can we get a resolution very soon; It is
urgent issue for Dell. If you want more background please let me know by
email or on irc.

Thx.

Pascal

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1571574

Title:
  3G (WWAN) icon missing in network-manager-applet

Status in Network Manager Applet:
  New
Status in OEM Priority Project:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  Incomplete
Status in network-manager-applet source package in Xenial:
  Incomplete

Bug description:
  After establishing a 3G connection, the icon shown in system tray
  should be a 3G indicator to indicate that 3G is connected.

  However, in Xenial there is no 3G icon at all.
  After 3G connection is established, it remains as the previous icon displayed.
  (e.g. 
  If no other connection was established before 3G connection was made, then 
the icon is a "hollow fan shape" after connecting to 3G.
  If wifi was connected before 3G connection was made, then the icon after 3G 
connection shows a wifi icon.)

  network-manager: 1.1.93-0ubuntu3
  OS: Xenial daily (2016 Apr. 15)

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

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

[Desktop-packages] [Bug 1583862] [NEW] apt-get update hangs after hit/get

You have been subscribed to a public bug:

After typing "sudo apt-get update" the following happens, but then it hangs:
Hit:1 http://us.archive.ubuntu.com/ubuntu xenial InRelease
Ign:2 http://dl.google.com/linux/chrome/deb stable InRelease   
Get:3 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [94.5 kB]   
Hit:4 http://dl.google.com/linux/chrome/deb stable Release 
Hit:5 http://apt.postgresql.org/pub/repos/apt xenial-pgdg InRelease
Get:6 http://security.ubuntu.com/ubuntu xenial-security InRelease [94.5 kB]
Get:7 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease [92.2 kB] 
Hit:9 http://ppa.launchpad.net/neovim-ppa/unstable/ubuntu xenial InRelease 
Hit:10 https://deb.nodesource.com/node_6.x xenial InRelease
Fetched 281 kB in 0s (366 kB/s)

Description:Ubuntu 16.04 LTS
Release:16.04

apt:
  Installed: 1.2.10ubuntu1
  Candidate: 1.2.10ubuntu1
  Version table:
 *** 1.2.10ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apt 1.2.10ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Thu May 19 21:42:52 2016
InstallationDate: Installed on 2016-04-27 (23 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial
-- 
apt-get update hangs after hit/get
https://bugs.launchpad.net/bugs/1583862
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to appstream in Ubuntu.

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

[Desktop-packages] [Bug 1579712] Re: Refresh hangs indefinitely, appstreamcli using 100% CPU

2016-05-19 Thread Hélio Nunes

Matthias' #24 workaround works for me. Thank you. But how the amateur,
non-technical, regular user of a !!!LTS!!! release will deal with this
bug? Fixed for me and for (lets see) 300 users... and the others?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1579712

Title:
  Refresh hangs indefinitely, appstreamcli using 100% CPU

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
   * Fixing this bug resolves the issue for people who might experience it.
   * See https://github.com/ximion/appstream/issues/35 for details.

  [Test Case 1]

   * Run `sudo appstreamcli refresh --force`
   * The AppStream cache should be updated, no change in behavior should be 
seen.

  [Test Case 2]

   * In case you were experiencing the almost-infinite hang when running
  `sudo appstreamcli refresh --force`, this issue should be fixed with
  the SRU.

  [Regression Potential]

   * Very low, since this only fixes the decompression code. There
  should be no sideeffects of that (given that the patch itself doesn't
  break anything, which it shouldn't, since it has been tested upstream
  for a while)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
   * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a

  

  /!\ Installing the bugfix from xenial-proposed, without going through APT:
  To install the fixed packages manually, please execute the following commands 
(for amd64, adjust URLs for other architectures):

  ```
  cd /tmp && mkdir asfix
  cd asfix
  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/appstream_0.9.4-1ubuntu1_amd64.deb
  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libappstream3_0.9.4-1ubuntu1_amd64.deb
  sudo dpkg -i libappstream3*.deb
  sudo dpkg -i appstream*.deb
  ```

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

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

[Desktop-packages] [Bug 1320868] Re: "UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 0: invalid start byte" when removing nvidia-current package

2016-05-19 Thread Ying-Chun Liu

I think this bug is being fixed in the upstream already.
https://github.com/tseliot/ubuntu-drivers-common/commit/cee1ac2aaa4ee79b81c154fed282268fbbe7a9a2

We can close this bug with ubuntu-drivers-common (>= 1:0.4.19).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1320868

Title:
  "UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position
  0: invalid start byte" when removing nvidia-current package

Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  $sudo apt-get remove nvidia-current
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Package 'nvidia-current' is not installed, so not removed
  The following package was automatically installed and is no longer required:
linux-image-generic
  Use 'apt-get autoremove' to remove it.
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Setting up nvidia-331 (331.38-0ubuntu7) ...
  INFO:Enable nvidia-331
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
  Traceback (most recent call last):
File "/usr/bin/quirks-handler", line 65, in 
  operation_status = main(options)
File "/usr/bin/quirks-handler", line 44, in main
  quirks = Quirks.quirkapplier.QuirkChecker(options.package_enable, 
path=quirks_path)
File "/usr/lib/python3/dist-packages/Quirks/quirkapplier.py", line 38, in 
__init__
  self._system_info = self.get_system_info()
File "/usr/lib/python3/dist-packages/Quirks/quirkapplier.py", line 64, in 
get_system_info
  return quirk_info.get_dmi_info()
File "/usr/lib/python3/dist-packages/Quirks/quirkinfo.py", line 46, in 
get_dmi_info
  'class', 'dmi', 'id', item)).read().strip()
File "/usr/lib/python3.4/codecs.py", line 313, in decode
  (result, consumed) = self._buffer_decode(data, self.errors, final)
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 0: 
invalid start byte
  dpkg: error processing package nvidia-331 (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   nvidia-331
  E: Sub-process /usr/bin/dpkg returned an error code (1)

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

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

[Desktop-packages] [Bug 1571574] Re: 3G (WWAN) icon missing in network-manager-applet

2016-05-19 Thread Kristin Chuang

Please refer to the attached syslog

** Attachment added: "3g-icon-syslog"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1571574/+attachment/468/+files/3g-icon-syslog

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1571574

Title:
  3G (WWAN) icon missing in network-manager-applet

Status in Network Manager Applet:
  New
Status in OEM Priority Project:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  Incomplete
Status in network-manager-applet source package in Xenial:
  Incomplete

Bug description:
  After establishing a 3G connection, the icon shown in system tray
  should be a 3G indicator to indicate that 3G is connected.

  However, in Xenial there is no 3G icon at all.
  After 3G connection is established, it remains as the previous icon displayed.
  (e.g. 
  If no other connection was established before 3G connection was made, then 
the icon is a "hollow fan shape" after connecting to 3G.
  If wifi was connected before 3G connection was made, then the icon after 3G 
connection shows a wifi icon.)

  network-manager: 1.1.93-0ubuntu3
  OS: Xenial daily (2016 Apr. 15)

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

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

[Desktop-packages] [Bug 1579712] Re: Refresh hangs indefinitely, appstreamcli using 100% CPU

I made the summary less technical, so maybe fewer duplicates of this get 
reported when people go through the bug list. I also added instructions on how 
to fix this immediately without removing packages or moving config files around 
to the bug description, so people who find this bug don't need to read the 
whole thread to get their machines working properly again.
Cheers,
Matthias


** Summary changed:

- Refresh hangs due to strdup on non-NULL terminated string
+ Refresh hangs indefinitely, appstreamcli using 100% CPU

** Description changed:

  [Impact]
  
-  * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
-  * Fixing this bug resolves the issue for people who might experience it.
-  * See https://github.com/ximion/appstream/issues/35 for details.
+  * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
+  * Fixing this bug resolves the issue for people who might experience it.
+  * See https://github.com/ximion/appstream/issues/35 for details.
  
  [Test Case 1]
  
-  * Run `sudo appstreamcli refresh --force`
-  * The AppStream cache should be updated, no change in behavior should be 
seen.
+  * Run `sudo appstreamcli refresh --force`
+  * The AppStream cache should be updated, no change in behavior should be 
seen.
  
  [Test Case 2]
  
-  * In case you were experiencing the almost-infinite hang when running
+  * In case you were experiencing the almost-infinite hang when running
  `sudo appstreamcli refresh --force`, this issue should be fixed with the
  SRU.
  
  [Regression Potential]
  
-  * Very low, since this only fixes the decompression code. There should
+  * Very low, since this only fixes the decompression code. There should
  be no sideeffects of that (given that the patch itself doesn't break
  anything, which it shouldn't, since it has been tested upstream for a
  while)
  
  [Other Info]
  
-  * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
-  * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a
+  * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
+  * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a
+ 
+ 
+ 
+ /!\ Installing the bugfix from xenial-proposed, without going through APT:
+ To install the fixed packages manually, please execute the following commands 
(for amd64, adjust URLs for other architectures):
+ 
+ ```
+ cd /tmp && mkdir asfix
+ cd asfix
+ wget 
https://launchpad.net/ubuntu/+archive/primary/+files/appstream_0.9.4-1ubuntu1_amd64.deb
+ wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libappstream3_0.9.4-1ubuntu1_amd64.deb
+ sudo dpkg -i libappstream3*.deb
+ sudo dpkg -i appstream*.deb
+ ```

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1579712

Title:
  Refresh hangs indefinitely, appstreamcli using 100% CPU

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
   * Fixing this bug resolves the issue for people who might experience it.
   * See https://github.com/ximion/appstream/issues/35 for details.

  [Test Case 1]

   * Run `sudo appstreamcli refresh --force`
   * The AppStream cache should be updated, no change in behavior should be 
seen.

  [Test Case 2]

   * In case you were experiencing the almost-infinite hang when running
  `sudo appstreamcli refresh --force`, this issue should be fixed with
  the SRU.

  [Regression Potential]

   * Very low, since this only fixes the decompression code. There
  should be no sideeffects of that (given that the patch itself doesn't
  break anything, which it shouldn't, since it has been tested upstream
  for a while)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
   * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a

  

  /!\ Installing the bugfix from xenial-proposed, without going

[Desktop-packages] [Bug 1583879] Re: apt-get update hangs indefinitely, appstreamcli using 100% CPU

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

** This bug has been marked a duplicate of bug 1579712
   Refresh hangs due to strdup on non-NULL terminated string

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1583879

Title:
  apt-get update hangs indefinitely, appstreamcli using 100% CPU

Status in appstream package in Ubuntu:
  New

Bug description:
  Just ran `sudo apt-get update`, which is hanging indefinitely after
  the downloads complete, the last CLI output from which is:

  Fetched 733 kB in 1s (399 kB/s)

  Looking at `top` suggests `appstreamcli` is the culprit as it's pegged
  at near 100% CPU usage:

   100  0.1  18:29.02 appstreamcli

  If I kill the hung `sudo apt-get update` process with Control+C, the
  `appstreamcli` process goes away.

  Retrying `sudo apt-get update` has the same result.

  On a whim I also tried `sudo apt update`, but it seems to have the
  same problem. It hangs indefinitely and running it results in an
  `appstreamcli` process consuming 100% CPU.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: appstream 0.9.4-1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May 19 20:53:40 2016
  SourcePackage: appstream
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1536353] Re: [regression] Printer drivers install is broken as lsb package is not available anymore

2016-05-19 Thread Arup

For now following Richard's advice I installed lsb by adding trusty
repository. After that I removed the trusty repo. So far no issues and
printer and printer utility working fine after driver install for my
Epson L800. This seems to be the only viable working solution till
Canonical fixes this.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to system-config-printer in Ubuntu.
https://bugs.launchpad.net/bugs/1536353

Title:
  [regression] Printer drivers install is broken as lsb package is not
  available anymore

Status in cups-filters package in Ubuntu:
  Fix Released
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Fix Committed
Status in system-config-printer package in Ubuntu:
  Invalid

Bug description:
  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's

   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

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

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

[Desktop-packages] [Bug 1579712] Re: Refresh hangs due to strdup on non-NULL terminated string

@dsfkljo322332: This bug affects upgrades via apt as well as dpkg. Gdebi
uses one of those on the back end, not sure which. See comment #34 and
#30 for more details.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1579712

Title:
  Refresh hangs due to strdup on non-NULL terminated string

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
   * Fixing this bug resolves the issue for people who might experience it.
   * See https://github.com/ximion/appstream/issues/35 for details.

  [Test Case 1]

   * Run `sudo appstreamcli refresh --force`
   * The AppStream cache should be updated, no change in behavior should be 
seen.

  [Test Case 2]

   * In case you were experiencing the almost-infinite hang when running
  `sudo appstreamcli refresh --force`, this issue should be fixed with
  the SRU.

  [Regression Potential]

   * Very low, since this only fixes the decompression code. There
  should be no sideeffects of that (given that the patch itself doesn't
  break anything, which it shouldn't, since it has been tested upstream
  for a while)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
   * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a

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

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

[Desktop-packages] [Bug 1579712] Re: Refresh hangs due to strdup on non-NULL terminated string

2016-05-19 Thread Goddard

sudo apt remove appstream works for me, but plasma-discover depends on
it so it is also removed.  Lucky for me I didn't really use that any
way.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1579712

Title:
  Refresh hangs due to strdup on non-NULL terminated string

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
   * Fixing this bug resolves the issue for people who might experience it.
   * See https://github.com/ximion/appstream/issues/35 for details.

  [Test Case 1]

   * Run `sudo appstreamcli refresh --force`
   * The AppStream cache should be updated, no change in behavior should be 
seen.

  [Test Case 2]

   * In case you were experiencing the almost-infinite hang when running
  `sudo appstreamcli refresh --force`, this issue should be fixed with
  the SRU.

  [Regression Potential]

   * Very low, since this only fixes the decompression code. There
  should be no sideeffects of that (given that the patch itself doesn't
  break anything, which it shouldn't, since it has been tested upstream
  for a while)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
   * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a

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

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

[Desktop-packages] [Bug 1583883] [NEW] lightdm blocks login screen on non-english layout

2016-05-19 Thread anatoly techtonik

Public bug reported:

Sometimes lightdm pops up after the sleep mode and proposes its own
login screen without ability to change keyboard layout. How to fix it?

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lightdm 1.18.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu May 19 10:41:43 2016
SourcePackage: lightdm
UpgradeStatus: Upgraded to xenial on 2016-04-07 (41 days ago)

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


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1583883

Title:
  lightdm blocks login screen on non-english layout

Status in lightdm package in Ubuntu:
  New

Bug description:
  Sometimes lightdm pops up after the sleep mode and proposes its own
  login screen without ability to change keyboard layout. How to fix it?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu May 19 10:41:43 2016
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2016-04-07 (41 days ago)

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

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

[Desktop-packages] [Bug 1583879] Re: apt-get update hangs indefinitely, appstreamcli using 100% CPU

2016-05-19 Thread Jason Gerard DeRose

Also, the graphical Ubuntu Software Updater is likewise hanging
indefinitely.

And I've confirmed this on 3 different systems so far.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1583879

Title:
  apt-get update hangs indefinitely, appstreamcli using 100% CPU

Status in appstream package in Ubuntu:
  New

Bug description:
  Just ran `sudo apt-get update`, which is hanging indefinitely after
  the downloads complete, the last CLI output from which is:

  Fetched 733 kB in 1s (399 kB/s)

  Looking at `top` suggests `appstreamcli` is the culprit as it's pegged
  at near 100% CPU usage:

   100  0.1  18:29.02 appstreamcli

  If I kill the hung `sudo apt-get update` process with Control+C, the
  `appstreamcli` process goes away.

  Retrying `sudo apt-get update` has the same result.

  On a whim I also tried `sudo apt update`, but it seems to have the
  same problem. It hangs indefinitely and running it results in an
  `appstreamcli` process consuming 100% CPU.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: appstream 0.9.4-1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May 19 20:53:40 2016
  SourcePackage: appstream
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1583881] [NEW] package texlive-latex-base-doc (not installed) failed to install/upgrade: trying to overwrite '/usr/share/doc/texlive-doc/latex/url/url.tex.gz', which is also in

2016-05-19 Thread Srikanta

Public bug reported:

This is occurred after upgrading to 16.04

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: texlive-latex-base-doc (not installed)
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Thu May 19 11:06:01 2016
ErrorMessage: trying to overwrite 
'/usr/share/doc/texlive-doc/latex/url/url.tex.gz', which is also in package 
texlive-latex-recommended-doc 2013.20140215-1
InstallationDate: Installed on 2015-12-26 (145 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.10ubuntu1
SourcePackage: texlive-base
Title: package texlive-latex-base-doc (not installed) failed to 
install/upgrade: trying to overwrite 
'/usr/share/doc/texlive-doc/latex/url/url.tex.gz', which is also in package 
texlive-latex-recommended-doc 2013.20140215-1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to texlive-base in Ubuntu.
https://bugs.launchpad.net/bugs/1583881

Title:
  package texlive-latex-base-doc (not installed) failed to
  install/upgrade: trying to overwrite '/usr/share/doc/texlive-
  doc/latex/url/url.tex.gz', which is also in package texlive-latex-
  recommended-doc 2013.20140215-1

Status in texlive-base package in Ubuntu:
  New

Bug description:
  This is occurred after upgrading to 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: texlive-latex-base-doc (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu May 19 11:06:01 2016
  ErrorMessage: trying to overwrite 
'/usr/share/doc/texlive-doc/latex/url/url.tex.gz', which is also in package 
texlive-latex-recommended-doc 2013.20140215-1
  InstallationDate: Installed on 2015-12-26 (145 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.10ubuntu1
  SourcePackage: texlive-base
  Title: package texlive-latex-base-doc (not installed) failed to 
install/upgrade: trying to overwrite 
'/usr/share/doc/texlive-doc/latex/url/url.tex.gz', which is also in package 
texlive-latex-recommended-doc 2013.20140215-1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1579712] Re: Refresh hangs due to strdup on non-NULL terminated string

2016-05-19 Thread jowfdoijdfdwfwdf

My bad. I forgot to install libappstream3_0.9.4-1ubuntu1_amd64.deb

installing libappstream3_0.9.4-1ubuntu1_amd64.deb wtih dpkg first did
fix the problem. I think I was using gdebi. Does this bug break gdebi
somehow?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1579712

Title:
  Refresh hangs due to strdup on non-NULL terminated string

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
   * Fixing this bug resolves the issue for people who might experience it.
   * See https://github.com/ximion/appstream/issues/35 for details.

  [Test Case 1]

   * Run `sudo appstreamcli refresh --force`
   * The AppStream cache should be updated, no change in behavior should be 
seen.

  [Test Case 2]

   * In case you were experiencing the almost-infinite hang when running
  `sudo appstreamcli refresh --force`, this issue should be fixed with
  the SRU.

  [Regression Potential]

   * Very low, since this only fixes the decompression code. There
  should be no sideeffects of that (given that the patch itself doesn't
  break anything, which it shouldn't, since it has been tested upstream
  for a while)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
   * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a

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

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

[Desktop-packages] [Bug 1583879] [NEW] apt-get update hangs indefinitely, appstreamcli using 100% CPU

2016-05-19 Thread Jason Gerard DeRose

Public bug reported:

Just ran `sudo apt-get update`, which is hanging indefinitely after the
downloads complete, the last CLI output from which is:

Fetched 733 kB in 1s (399 kB/s)

Looking at `top` suggests `appstreamcli` is the culprit as it's pegged
at near 100% CPU usage:

 100  0.1  18:29.02 appstreamcli

If I kill the hung `sudo apt-get update` process with Control+C, the
`appstreamcli` process goes away.

Retrying `sudo apt-get update` has the same result.

On a whim I also tried `sudo apt update`, but it seems to have the same
problem. It hangs indefinitely and running it results in an
`appstreamcli` process consuming 100% CPU.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: appstream 0.9.4-1
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Thu May 19 20:53:40 2016
SourcePackage: appstream
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1583879

Title:
  apt-get update hangs indefinitely, appstreamcli using 100% CPU

Status in appstream package in Ubuntu:
  New

Bug description:
  Just ran `sudo apt-get update`, which is hanging indefinitely after
  the downloads complete, the last CLI output from which is:

  Fetched 733 kB in 1s (399 kB/s)

  Looking at `top` suggests `appstreamcli` is the culprit as it's pegged
  at near 100% CPU usage:

   100  0.1  18:29.02 appstreamcli

  If I kill the hung `sudo apt-get update` process with Control+C, the
  `appstreamcli` process goes away.

  Retrying `sudo apt-get update` has the same result.

  On a whim I also tried `sudo apt update`, but it seems to have the
  same problem. It hangs indefinitely and running it results in an
  `appstreamcli` process consuming 100% CPU.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: appstream 0.9.4-1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May 19 20:53:40 2016
  SourcePackage: appstream
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1579712] Re: Refresh hangs due to strdup on non-NULL terminated string

2016-05-19 Thread jowfdoijdfdwfwdf

Also hit by this. And unable to manually install the deb, even after rm
/usr/bin/appstreamcli

Preparing to unpack appstream_0.9.4-1ubuntu1_amd64.deb ...
Unpacking appstream (0.9.4-1ubuntu1) over (0.9.4-1ubuntu1) ...
Setting up appstream (0.9.4-1ubuntu1) ...

CPU stuck at 100%

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1579712

Title:
  Refresh hangs due to strdup on non-NULL terminated string

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
   * Fixing this bug resolves the issue for people who might experience it.
   * See https://github.com/ximion/appstream/issues/35 for details.

  [Test Case 1]

   * Run `sudo appstreamcli refresh --force`
   * The AppStream cache should be updated, no change in behavior should be 
seen.

  [Test Case 2]

   * In case you were experiencing the almost-infinite hang when running
  `sudo appstreamcli refresh --force`, this issue should be fixed with
  the SRU.

  [Regression Potential]

   * Very low, since this only fixes the decompression code. There
  should be no sideeffects of that (given that the patch itself doesn't
  break anything, which it shouldn't, since it has been tested upstream
  for a while)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
   * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a

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

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

[Desktop-packages] [Bug 1579712] Re: Refresh hangs due to strdup on non-NULL terminated string

@dsfkljo322332: Are you using dpkg to install the upgrades? Try
upgrading the libappstream3 package first, then the appstream package.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1579712

Title:
  Refresh hangs due to strdup on non-NULL terminated string

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
   * Fixing this bug resolves the issue for people who might experience it.
   * See https://github.com/ximion/appstream/issues/35 for details.

  [Test Case 1]

   * Run `sudo appstreamcli refresh --force`
   * The AppStream cache should be updated, no change in behavior should be 
seen.

  [Test Case 2]

   * In case you were experiencing the almost-infinite hang when running
  `sudo appstreamcli refresh --force`, this issue should be fixed with
  the SRU.

  [Regression Potential]

   * Very low, since this only fixes the decompression code. There
  should be no sideeffects of that (given that the patch itself doesn't
  break anything, which it shouldn't, since it has been tested upstream
  for a while)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
   * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a

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

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

[Desktop-packages] [Bug 1503758] Re: /usr/lib/unity-settings-daemon/unity-settings-daemon:5:XIQueryDevice:xdevice_get_dimensions:input_info_find_size_match:get_mappable_output_info:do_touchscreen_mapp

2016-05-19 Thread Xinxiu Yang

oops, sorry for comment #13, I started from an error version u-s-d
source,  this time I patched the simple patch base on unity-settings-
daemon-14.04.0+14.04.20151012 which we used in Sutton image and tried
again, seems it works fine. the u-s-d works well after change the
resolution with patch https://bugs.launchpad.net/ubuntu/+source/unity-
settings-daemon/+bug/1503758/+attachment/4666128/+files/usd.patch.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1503758

Title:
  /usr/lib/unity-settings-daemon/unity-settings-
  
daemon:5:XIQueryDevice:xdevice_get_dimensions:input_info_find_size_match:get_mappable_output_info:do_touchscreen_mapping

Status in OEM Priority Project:
  New
Status in unity-settings-daemon package in Ubuntu:
  Triaged
Status in unity-settings-daemon package in Fedora:
  Unknown

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

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

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

[Desktop-packages] [Bug 1579712] Re: Refresh hangs due to strdup on non-NULL terminated string

2016-05-19 Thread Goddard

This runs up my CPU on Kubuntu... appstreamcli was using 13% cpu.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1579712

Title:
  Refresh hangs due to strdup on non-NULL terminated string

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
   * Fixing this bug resolves the issue for people who might experience it.
   * See https://github.com/ximion/appstream/issues/35 for details.

  [Test Case 1]

   * Run `sudo appstreamcli refresh --force`
   * The AppStream cache should be updated, no change in behavior should be 
seen.

  [Test Case 2]

   * In case you were experiencing the almost-infinite hang when running
  `sudo appstreamcli refresh --force`, this issue should be fixed with
  the SRU.

  [Regression Potential]

   * Very low, since this only fixes the decompression code. There
  should be no sideeffects of that (given that the patch itself doesn't
  break anything, which it shouldn't, since it has been tested upstream
  for a while)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
   * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a

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

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

[Desktop-packages] [Bug 1583424] Re: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build

2016-05-19 Thread Daniel van Vugt

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

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


** This bug has been marked a duplicate of bug 1574838
   nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build [error: 
code model kernel does not support PIC mode]

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-361 in Ubuntu.
https://bugs.launchpad.net/bugs/1583424

Title:
  nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build

Status in nvidia-graphics-drivers-361 package in Ubuntu:
  New

Bug description:
  Was not able to log into Unity after rebooting. Reverted back to free
  driver.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: nvidia-361 (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  DKMSKernelVersion: 4.4.0-22-generic
  Date: Tue May 17 23:06:14 2016
  DuplicateSignature: 
dkms:nvidia-361:361.42-0ubuntu2:/var/lib/dkms/nvidia-361/361.42/build/nvidia/nv-instance.c:1:0:
 error: code model kernel does not support PIC mode
  InstallationDate: Installed on 2016-05-17 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageVersion: 361.42-0ubuntu2
  RelatedPackageVersions:
   dpkg 1.18.7ubuntu1
   apt  1.3~exp1
  SourcePackage: nvidia-graphics-drivers-361
  Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1583424/+subscriptions

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

[Desktop-packages] [Bug 1547077] Re: Suspend to ram causes some glyphs to draw consistently wrong or even appear blank in gtk/gdk/pango/cairo apps. xterm/xmessage unaffected.

2016-05-19 Thread Christopher M. Penalver

gouri, could you please provide the bugzilla number for the report you
filed?

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1547077

Title:
Suspend to ram causes some glyphs to draw consistently wrong or even
appear blank in gtk/gdk/pango/cairo apps. xterm/xmessage unaffected.

Status in xorg package in Ubuntu:
Triaged

Bug description:
# Summary
* Some glyphs badly drawn at some moments.
* When happens, same glyph drawn on various windows shows same corruption.
* Problem comes and go.

Cannot use nvidia proprietary driver as a workaround (does not work at
all).

# Context
Laptop, using "intel" (or "nouveau" ?) driver.
Expected: all glyphs rendered correctly.
Observed: some glyphs not rendered correctly

* reproducible: sometimes, eventually. Problem comes and go, severity
varies from one glyph (see
2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all
text on screen fully unreadable (see
2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png
)

* *some* glyphs are affected. For example, letter 'a' of a certain
size will be replaced by colored garbage at many places where it
appears (see
2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png
), but other 'a' with different size, italic, bold, etc will be
unaffected.

* in some applications (e.g. xfce whisker menu), some glyphs are
rendered correctly or not depending on the direction of mouse
hovering. See video
2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 .

* in menu of gtk application, some glyphs are "fixed" by opening the
menu, but not all. For example, in xfce4-terminal, letter A of
"Affichage" and its menu content as well as "Aide" is affected.
Opening "Affichage" menu does not fix anything. Opening "Aide" menu
fixes the "A" of "Aide". Changing window size reactivates the bug on
"A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn-
bug.mp4 .

* text under icons on desktop is affected, but shadows are not. See

2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png

# Affected applications
* xfce whisker menu,
* xfce4-terminal (nealy all screenshots)
* firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png
2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png
),
* thunderbird (see
2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ),
* emacs (see
2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png
and subsequent ),
* superswitcher ( a gtk/gdk app)
* *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are
affected.

# Additional information
This looks like a cache corruption somewhere.
On IRC #pango, someone suggested a bug in Intel driver.
Running `xfce4-appearance-settings` and there changing any of:
* antialiasing enable/disable,
* hinting strength,
* subpixel alignment
* or dpi
immediately cures the bug (see
2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png
)

Setting back the exact same parameters immediately reactivates the bug
(see

2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png).

It is believed that keeping any new settings for a while will have the
bug reoccur.

It is not like bug 1536751. That one affects rendering quality of
*all* glyphs, at all times, depending on dpi. This is not the case
here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by
garbage or absent), not always.

---
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: XFCE
DistUpgraded: Fresh install
DistroCodename: xenial
DistroRelease: Ubuntu 16.04
DistroVariant: ubuntu
DkmsStatus: virtualbox, 5.0.14, 4.4.0-8-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
Intel Corporation 4th Gen Core Processor Integrated Graphics Controller
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated
Graphics Controller [1043:177d]
Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:177d]
InstallationDate: Installed on 2016-02-03 (26 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203)
MachineType: ASUSTeK COMPUTER INC. N551JK
Package: xorg 1:7.7+13ubuntu1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-7-generic.efi.signed
root=UUID=1a4f1bb3-67a8-4e9e-ba71-e9a2741c04a8 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu

[Desktop-packages] [Bug 1579712] Re: Refresh hangs due to strdup on non-NULL terminated string

@Brett: When the AppStream cache update is triggered, the APT cache is updated, 
so updates will still be installed. Ideally, the fixed package is shipped via 
x-updates soon, so no more people get trapped.
SRU verification is done at least, and we now have more than enough people 
confirming the bugfix :)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1579712

Title:
  Refresh hangs due to strdup on non-NULL terminated string

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
   * Fixing this bug resolves the issue for people who might experience it.
   * See https://github.com/ximion/appstream/issues/35 for details.

  [Test Case 1]

   * Run `sudo appstreamcli refresh --force`
   * The AppStream cache should be updated, no change in behavior should be 
seen.

  [Test Case 2]

   * In case you were experiencing the almost-infinite hang when running
  `sudo appstreamcli refresh --force`, this issue should be fixed with
  the SRU.

  [Regression Potential]

   * Very low, since this only fixes the decompression code. There
  should be no sideeffects of that (given that the patch itself doesn't
  break anything, which it shouldn't, since it has been tested upstream
  for a while)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
   * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a

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

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

[Desktop-packages] [Bug 1579712] Re: Refresh hangs due to strdup on non-NULL terminated string

2016-05-19 Thread kimr

Today i woke up to my server's cpu fan going at full speed. Puzzled by
this i check my virtualbox machines and notice my ubuntu 16.04
installation has appstream stuck at 100% on one core. This has not
happened before.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1579712

Title:
  Refresh hangs due to strdup on non-NULL terminated string

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
   * Fixing this bug resolves the issue for people who might experience it.
   * See https://github.com/ximion/appstream/issues/35 for details.

  [Test Case 1]

   * Run `sudo appstreamcli refresh --force`
   * The AppStream cache should be updated, no change in behavior should be 
seen.

  [Test Case 2]

   * In case you were experiencing the almost-infinite hang when running
  `sudo appstreamcli refresh --force`, this issue should be fixed with
  the SRU.

  [Regression Potential]

   * Very low, since this only fixes the decompression code. There
  should be no sideeffects of that (given that the patch itself doesn't
  break anything, which it shouldn't, since it has been tested upstream
  for a while)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
   * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a

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

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

[Desktop-packages] [Bug 1583861] Re: Keyboard backlight isn't properly restored after idle on systems with hardwired configuration

** Description changed:

- In Dell or ThinkPad notebooks with keyboard backlight, the keybindings
- to control the keyboard backlight don't emit any event to the userland,
+ In Dell or ThinkPad (for these you need a kernel which includes fix for
+ lp:1574498) notebooks with keyboard backlight, the keybindings to
+ control the keyboard backlight don't emit any event to the userland,
  about the state change, nor they request userland to change it (as it
  happens in other models which emits KEY_KBDILLUM{UP,DOWN,TOGGLE}
  events), this causes unity/gnome-settings daemon not to restore the
  proper backlight after idle.
  
  Steps to reproduce:
-  0) ensure your keyboard backlight is on, and 
-  gdbus call --system --dest org.freedesktop.UPower \
-   --object-path /org/freedesktop/UPower/KbdBacklight \
-   --method org.freedesktop.UPower.KbdBacklight.GetBrightness
- returns a value != from 0. If not, just call the SetBrightness
- method with a positive value, to turn on the backlight.
-
- Now turn off the keyboard backlight (or set it to another level) 
- using the laptop keys, and run:
-  gsettings set org.gnome.desktop.session idle-delay 1
- to make things easier to test.
+  0) ensure your keyboard backlight is on, and
+  gdbus call --system --dest org.freedesktop.UPower \
+   --object-path /org/freedesktop/UPower/KbdBacklight \
+   --method org.freedesktop.UPower.KbdBacklight.GetBrightness
+ returns a value != from 0. If not, just call the SetBrightness
+ method with a positive value, to turn on the backlight.
  
-  2) Wait one second and the screensaver should start. Wait the screen to
- be turned off. If you just changed the brightness level at the step above,
- once the screen is turned off, also the keyboard backlight should be 
turned off too.
+ Now turn off the keyboard backlight (or set it to another level)
+ using the laptop keys, and run:
+  gsettings set org.gnome.desktop.session idle-delay 1
+ to make things easier to test.
  
-  3) Now press a key or move the mouse.
+  2) Wait one second and the screensaver should start. Wait the screen to
+ be turned off. If you just changed the brightness level at the step above,
+ once the screen is turned off, also the keyboard backlight should be 
turned off too.
+ 
+  3) Now press a key or move the mouse.
  
  Expected behavior:
  
-  4) The keyboard backlight should be set back to the previous level (so it 
should stay off
- or go back to the level you set before the idle timeout happened).
+  4) The keyboard backlight should be set back to the previous level (so it 
should stay off
+ or go back to the level you set before the idle timeout happened).
  
  Actual behavior:
  
-  5) The backlight is set to the level it had at point 0).
+  5) The backlight is set to the level it had at point 0).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1583861

Title:
  Keyboard backlight isn't properly restored after idle on systems with
  hardwired configuration

Status in Dell Sputnik:
  New
Status in Upower:
  Unknown
Status in gnome-settings-daemon package in Ubuntu:
  New
Status in unity-settings-daemon package in Ubuntu:
  New
Status in upower package in Ubuntu:
  New

Bug description:
  In Dell or ThinkPad (for these you need a kernel which includes fix
  for lp:1574498) notebooks with keyboard backlight, the keybindings to
  control the keyboard backlight don't emit any event to the userland,
  about the state change, nor they request userland to change it (as it
  happens in other models which emits KEY_KBDILLUM{UP,DOWN,TOGGLE}
  events), this causes unity/gnome-settings daemon not to restore the
  proper backlight after idle.

  Steps to reproduce:
   0) ensure your keyboard backlight is on, and
   gdbus call --system --dest org.freedesktop.UPower \
    --object-path /org/freedesktop/UPower/KbdBacklight \
    --method org.freedesktop.UPower.KbdBacklight.GetBrightness
  returns a value != from 0. If not, just call the SetBrightness
  method with a positive value, to turn on the backlight.

  Now turn off the keyboard backlight (or set it to another level)
  using the laptop keys, and run:
   gsettings set org.gnome.desktop.session idle-delay 1
  to make things easier to test.

   2) Wait one second and the screensaver should start. Wait the screen to
  be turned off. If you just changed the brightness level at the step above,
  once the screen is turned off, also the keyboard backlight should be 
turned off too.

   3) Now press a key or move the mouse.

  Expected behavior:

   4) The keyboard backlight should be set back to the previous level (so it 
should stay off
  or go back to the level you set before the idle timeout happened).

  Actual behavior:

   5) The backlight is set to

[Desktop-packages] [Bug 1510344] Re: Keyboard Backlight Turns on at boot

** Branch unlinked: lp:~3v1n0/unity-settings-daemon/kbd-brightness-
update

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1510344

Title:
  Keyboard Backlight Turns on at boot

Status in Dell Sputnik:
  Confirmed
Status in gnome-settings-daemon:
  Fix Released
Status in One Hundred Papercuts:
  Confirmed
Status in Linux:
  Invalid
Status in unity-settings-daemon package in Ubuntu:
  In Progress
Status in unity-settings-daemon source package in Xenial:
  Fix Committed

Bug description:
  System: Dell XPS 13 9343

  Action: Boot computer

  Expected Behavior: Keyboard backlight would be off when computer is
  booted

  Actual Behavior: Keyboard backlight is on at boot

  This did not happen with Ubuntu 15.04

  There are new files in Ubuntu 15.10 -
  /sys/class/leds/dell::kbd_backlight$

  cat stop_timeout
  60s

   cat start_triggers 
  +keyboard +touchpad

  cat trigger 
  [none] AC-online BAT0-charging-or-full BAT0-charging BAT0-full 
BAT0-charging-blink-full-solid usb-gadget usb-host cpu0 cpu1 cpu2 cpu3 mmc0 
rfkill0

  cat brightness 
  2

  ---

  Unsure if these files are important, but included in the report

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.1.0-2-generic 4.1.0-2.2
  ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3
  Uname: Linux 4.1.0-2-generic x86_64
  ApportVersion: 2.18-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 2488 F pulseaudio
   /dev/snd/controlC0:  ubuntu 2488 F pulseaudio
  CasperVersion: 1.362
  CurrentDesktop: Unity
  Date: Tue Oct 27 01:29:47 2015
  IwConfig:
   enx00249b0981e3  no wireless extensions.
   
   lono wireless extensions.
  LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150730)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --- 
cdrom-detect/try-usb=true noprompt
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-2-generic N/A
   linux-backports-modules-4.1.0-2-generic  N/A
   linux-firmware   1.145
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1510344/+subscriptions

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

[Desktop-packages] [Bug 1583861] Re: Keyboard backlight isn't properly restored after idle on systems with hardwired configuration

** Patch added: "upower-always-get-kbd-brightness.debdiff"
   
https://bugs.launchpad.net/dell-sputnik/+bug/1583861/+attachment/440/+files/upower-always-get-kbd-brightness.debdiff

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1583861

Title:
  Keyboard backlight isn't properly restored after idle on systems with
  hardwired configuration

Status in Dell Sputnik:
  New
Status in Upower:
  Unknown
Status in gnome-settings-daemon package in Ubuntu:
  New
Status in unity-settings-daemon package in Ubuntu:
  New
Status in upower package in Ubuntu:
  New

Bug description:
  In Dell or ThinkPad (for these you need a kernel which includes fix
  for lp:1574498) notebooks with keyboard backlight, the keybindings to
  control the keyboard backlight don't emit any event to the userland,
  about the state change, nor they request userland to change it (as it
  happens in other models which emits KEY_KBDILLUM{UP,DOWN,TOGGLE}
  events), this causes unity/gnome-settings daemon not to restore the
  proper backlight after idle.

  Steps to reproduce:
   0) ensure your keyboard backlight is on, and
   gdbus call --system --dest org.freedesktop.UPower \
    --object-path /org/freedesktop/UPower/KbdBacklight \
    --method org.freedesktop.UPower.KbdBacklight.GetBrightness
  returns a value != from 0. If not, just call the SetBrightness
  method with a positive value, to turn on the backlight.

  Now turn off the keyboard backlight (or set it to another level)
  using the laptop keys, and run:
   gsettings set org.gnome.desktop.session idle-delay 1
  to make things easier to test.

   2) Wait one second and the screensaver should start. Wait the screen to
  be turned off. If you just changed the brightness level at the step above,
  once the screen is turned off, also the keyboard backlight should be 
turned off too.

   3) Now press a key or move the mouse.

  Expected behavior:

   4) The keyboard backlight should be set back to the previous level (so it 
should stay off
  or go back to the level you set before the idle timeout happened).

  Actual behavior:

   5) The backlight is set to the level it had at point 0).

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1583861/+subscriptions

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

[Desktop-packages] [Bug 1583861] Re: Keyboard backlight isn't properly restored after idle on systems with hardwired configuration

** Branch linked: lp:~3v1n0/unity-settings-daemon/kbd-brightness-update

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1583861

Title:
  Keyboard backlight isn't properly restored after idle on systems with
  hardwired configuration

Status in Dell Sputnik:
  New
Status in Upower:
  Unknown
Status in gnome-settings-daemon package in Ubuntu:
  New
Status in unity-settings-daemon package in Ubuntu:
  New
Status in upower package in Ubuntu:
  New

Bug description:
  In Dell or ThinkPad (for these you need a kernel which includes fix
  for lp:1574498) notebooks with keyboard backlight, the keybindings to
  control the keyboard backlight don't emit any event to the userland,
  about the state change, nor they request userland to change it (as it
  happens in other models which emits KEY_KBDILLUM{UP,DOWN,TOGGLE}
  events), this causes unity/gnome-settings daemon not to restore the
  proper backlight after idle.

  Steps to reproduce:
   0) ensure your keyboard backlight is on, and
   gdbus call --system --dest org.freedesktop.UPower \
    --object-path /org/freedesktop/UPower/KbdBacklight \
    --method org.freedesktop.UPower.KbdBacklight.GetBrightness
  returns a value != from 0. If not, just call the SetBrightness
  method with a positive value, to turn on the backlight.

  Now turn off the keyboard backlight (or set it to another level)
  using the laptop keys, and run:
   gsettings set org.gnome.desktop.session idle-delay 1
  to make things easier to test.

   2) Wait one second and the screensaver should start. Wait the screen to
  be turned off. If you just changed the brightness level at the step above,
  once the screen is turned off, also the keyboard backlight should be 
turned off too.

   3) Now press a key or move the mouse.

  Expected behavior:

   4) The keyboard backlight should be set back to the previous level (so it 
should stay off
  or go back to the level you set before the idle timeout happened).

  Actual behavior:

   5) The backlight is set to the level it had at point 0).

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1583861/+subscriptions

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

[Desktop-packages] [Bug 1583845] Re: Can't "apt-get update" - appstreamcli stuck at 100% Processor Utilization

2016-05-19 Thread Dylan

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

** Information type changed from Public Security to Private Security

** Information type changed from Private Security to Public

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1583845

Title:
  Can't "apt-get update" - appstreamcli stuck at 100% Processor
  Utilization

Status in appstream package in Ubuntu:
  Confirmed

Bug description:
  I did a fresh install of Ubuntu 16.04 without being connected to the
  internet because when connected to the internet the install would lock
  up at the point that ubuntu was "Retrieving 56 of 56".

  Installation (without internet) was successful, then I connected to
  the internet and tried to update:

  The update-process seemed to be stuck, so I discovered that the
  command appstreamcli was at 100% processor utilization indefinitely.

  When I kill that process the update fails. This is clearly a bug, but
  hopefully someone can suggest a work-around until it is fixed.

  user@pc:~$ sudo apt-get update
  Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [94.5 kB]
  Hit:2 http://us.archive.ubuntu.com/ubuntu xenial InRelease
  Get:3 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [94.5 kB]
  Get:4 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease [92.2 kB]
  Fetched 281 kB in 0s (387 kB/s)
  Terminated
  Reading package lists... Done
  E: Problem executing scripts APT::Update::Post-Invoke-Success 'if 
/usr/bin/test -w /var/cache/app-info -a -e /usr/bin/appstreamcli; then 
appstreamcli refresh > /dev/null; fi'
  E: Sub-process returned an error code

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: appstream 0.9.4-1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu May 19 19:08:30 2016
  InstallationDate: Installed on 2016-05-19 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: appstream
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1579712] Re: Refresh hangs due to strdup on non-NULL terminated string

I think a high priority is the better fit now, since this - for some
reason - started to hit more users than expected now, and the
manifestations of this bug are very annoying. It doesn't cause data loss
or is a critical security issue though.

** Changed in: appstream (Ubuntu Xenial)
   Importance: Medium => High

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1579712

Title:
  Refresh hangs due to strdup on non-NULL terminated string

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
   * Fixing this bug resolves the issue for people who might experience it.
   * See https://github.com/ximion/appstream/issues/35 for details.

  [Test Case 1]

   * Run `sudo appstreamcli refresh --force`
   * The AppStream cache should be updated, no change in behavior should be 
seen.

  [Test Case 2]

   * In case you were experiencing the almost-infinite hang when running
  `sudo appstreamcli refresh --force`, this issue should be fixed with
  the SRU.

  [Regression Potential]

   * Very low, since this only fixes the decompression code. There
  should be no sideeffects of that (given that the patch itself doesn't
  break anything, which it shouldn't, since it has been tested upstream
  for a while)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
   * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a

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

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

[Desktop-packages] [Bug 1579712] Re: Refresh hangs due to strdup on non-NULL terminated string

2016-05-19 Thread Trent V.

Matthias post #24
worked for me also thank you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1579712

Title:
  Refresh hangs due to strdup on non-NULL terminated string

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
   * Fixing this bug resolves the issue for people who might experience it.
   * See https://github.com/ximion/appstream/issues/35 for details.

  [Test Case 1]

   * Run `sudo appstreamcli refresh --force`
   * The AppStream cache should be updated, no change in behavior should be 
seen.

  [Test Case 2]

   * In case you were experiencing the almost-infinite hang when running
  `sudo appstreamcli refresh --force`, this issue should be fixed with
  the SRU.

  [Regression Potential]

   * Very low, since this only fixes the decompression code. There
  should be no sideeffects of that (given that the patch itself doesn't
  break anything, which it shouldn't, since it has been tested upstream
  for a while)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
   * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a

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

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

[Desktop-packages] [Bug 1583845] Re: Can't "apt-get update" - appstreamcli stuck at 100% Processor Utilization

2016-05-19 Thread Dylan

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

** Information type changed from Public to Public Security

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1583845

Title:
  Can't "apt-get update" - appstreamcli stuck at 100% Processor
  Utilization

Status in appstream package in Ubuntu:
  Confirmed

Bug description:
  I did a fresh install of Ubuntu 16.04 without being connected to the
  internet because when connected to the internet the install would lock
  up at the point that ubuntu was "Retrieving 56 of 56".

  Installation (without internet) was successful, then I connected to
  the internet and tried to update:

  The update-process seemed to be stuck, so I discovered that the
  command appstreamcli was at 100% processor utilization indefinitely.

  When I kill that process the update fails. This is clearly a bug, but
  hopefully someone can suggest a work-around until it is fixed.

  user@pc:~$ sudo apt-get update
  Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [94.5 kB]
  Hit:2 http://us.archive.ubuntu.com/ubuntu xenial InRelease
  Get:3 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [94.5 kB]
  Get:4 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease [92.2 kB]
  Fetched 281 kB in 0s (387 kB/s)
  Terminated
  Reading package lists... Done
  E: Problem executing scripts APT::Update::Post-Invoke-Success 'if 
/usr/bin/test -w /var/cache/app-info -a -e /usr/bin/appstreamcli; then 
appstreamcli refresh > /dev/null; fi'
  E: Sub-process returned an error code

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: appstream 0.9.4-1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu May 19 19:08:30 2016
  InstallationDate: Installed on 2016-05-19 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: appstream
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1579712] Re: Refresh hangs due to strdup on non-NULL terminated string

2016-05-19 Thread Brett Bogert

Folks, Updates had been working fine for me until today (5/19/2016).

I updated my machines last night(all 11 of them) and now all are
experiencing the aforementioned problem with 100% CPU usage from
appstreamcli.

It appears that in my case at least that something applied last
night must be triggering the problem as I have had no problems
with apt update until today.

I was able to "Ctrl C" out of the update command and install 
some updates but have to "assume" that I had gotten them all
since the update command never completed.

I will try and get the above fix applied to at least some of my
machines tomorrow.

How will users be able to apply the fix if they can't get past
the apt update command hanging (other than manual intervention
that is)?

Thanks

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1579712

Title:
  Refresh hangs due to strdup on non-NULL terminated string

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
   * Fixing this bug resolves the issue for people who might experience it.
   * See https://github.com/ximion/appstream/issues/35 for details.

  [Test Case 1]

   * Run `sudo appstreamcli refresh --force`
   * The AppStream cache should be updated, no change in behavior should be 
seen.

  [Test Case 2]

   * In case you were experiencing the almost-infinite hang when running
  `sudo appstreamcli refresh --force`, this issue should be fixed with
  the SRU.

  [Regression Potential]

   * Very low, since this only fixes the decompression code. There
  should be no sideeffects of that (given that the patch itself doesn't
  break anything, which it shouldn't, since it has been tested upstream
  for a while)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
   * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a

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

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

[Desktop-packages] [Bug 1579712] Re: Refresh hangs due to strdup on non-NULL terminated string

In comment #30 I took the procedure from comment #24 and added two
commands to rename appstream's apt config file, but those commands
aren't necessary because they have no effect when appstream is installed
via the `dpkg` command.

The appstream package's postinst file explicitly calls `appstreamcli
refresh-index --force`, so reported in comment #17, the hanging problem
is probably still present even when `dpkg` is used to upgrade the
appstream packages instead of apt. In that case, upgrading the
libappstream3 package *before* the appstream package may avoid the
hanging.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1579712

Title:
  Refresh hangs due to strdup on non-NULL terminated string

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
   * Fixing this bug resolves the issue for people who might experience it.
   * See https://github.com/ximion/appstream/issues/35 for details.

  [Test Case 1]

   * Run `sudo appstreamcli refresh --force`
   * The AppStream cache should be updated, no change in behavior should be 
seen.

  [Test Case 2]

   * In case you were experiencing the almost-infinite hang when running
  `sudo appstreamcli refresh --force`, this issue should be fixed with
  the SRU.

  [Regression Potential]

   * Very low, since this only fixes the decompression code. There
  should be no sideeffects of that (given that the patch itself doesn't
  break anything, which it shouldn't, since it has been tested upstream
  for a while)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
   * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a

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

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

[Desktop-packages] [Bug 1579712] Re: Refresh hangs due to strdup on non-NULL terminated string

2016-05-19 Thread Chuck Burgess

+1 on Matthias' instructions on installing the patches
(https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1579712/comments/24)...
this fixed the issue for me.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1579712

Title:
  Refresh hangs due to strdup on non-NULL terminated string

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
   * Fixing this bug resolves the issue for people who might experience it.
   * See https://github.com/ximion/appstream/issues/35 for details.

  [Test Case 1]

   * Run `sudo appstreamcli refresh --force`
   * The AppStream cache should be updated, no change in behavior should be 
seen.

  [Test Case 2]

   * In case you were experiencing the almost-infinite hang when running
  `sudo appstreamcli refresh --force`, this issue should be fixed with
  the SRU.

  [Regression Potential]

   * Very low, since this only fixes the decompression code. There
  should be no sideeffects of that (given that the patch itself doesn't
  break anything, which it shouldn't, since it has been tested upstream
  for a while)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
   * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a

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

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

[Desktop-packages] [Bug 1583425] Re: nvidia-304 304.131-0ubuntu3: nvidia-304 kernel module failed to build

2016-05-19 Thread Daniel van Vugt

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

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


** This bug has been marked a duplicate of bug 1574838
   nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build [error: 
code model kernel does not support PIC mode]

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1583425

Title:
  nvidia-304 304.131-0ubuntu3: nvidia-304 kernel module failed to build

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  New

Bug description:
  Unable to log into Unity after reboot.  Reverted back to free driver.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: nvidia-304 (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.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
  DKMSKernelVersion: 4.4.0-22-generic
  Date: Wed May 18 02:14:06 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DuplicateSignature: 
dkms:nvidia-304:304.131-0ubuntu3:/var/lib/dkms/nvidia-304/304.131/build/nv.c:1:0:
 error: code model kernel does not support PIC mode
  GraphicsCard:
   NVIDIA Corporation GF110 [GeForce GTX 580] [10de:1080] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GF110 [GeForce GTX 580] [3842:1582]
  InstallationDate: Installed on 2016-05-17 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gigabyte Technology Co., Ltd. GA-890XA-UD3
  PackageVersion: 304.131-0ubuntu3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=08860e9f-0cda-4abf-a1eb-a85f1829befb ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.7ubuntu1
   apt  1.3~exp1
  SourcePackage: nvidia-graphics-drivers-304
  Title: nvidia-304 304.131-0ubuntu3: nvidia-304 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FC
  dmi.board.name: GA-890XA-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFC:bd08/02/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-890XA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-890XA-UD3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-890XA-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.modprobe.d.nvidia-304_hybrid.conf: [deleted]
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.68-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.1-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed May 18 21:11:25 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech USB Gaming Mouse MOUSE, id 8
   inputUSB Keyboard KEYBOARD, id 9
   inputUSB Keyboard KEYBOARD, id 10
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu4
  xserver.video_driver: nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1583425/+subscriptions

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

[Desktop-packages] [Bug 1583845] Re: Can't "apt-get update" - appstreamcli stuck at 100% Processor Utilization

2016-05-19 Thread Chuck Burgess

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

Instructions for installing the patches to test (in Matthias' comment
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1579712/comments/24
on bug #1579712) *did* solve the issue for me.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1583845

Title:
  Can't "apt-get update" - appstreamcli stuck at 100% Processor
  Utilization

Status in appstream package in Ubuntu:
  Confirmed

Bug description:
  I did a fresh install of Ubuntu 16.04 without being connected to the
  internet because when connected to the internet the install would lock
  up at the point that ubuntu was "Retrieving 56 of 56".

  Installation (without internet) was successful, then I connected to
  the internet and tried to update:

  The update-process seemed to be stuck, so I discovered that the
  command appstreamcli was at 100% processor utilization indefinitely.

  When I kill that process the update fails. This is clearly a bug, but
  hopefully someone can suggest a work-around until it is fixed.

  user@pc:~$ sudo apt-get update
  Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [94.5 kB]
  Hit:2 http://us.archive.ubuntu.com/ubuntu xenial InRelease
  Get:3 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [94.5 kB]
  Get:4 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease [92.2 kB]
  Fetched 281 kB in 0s (387 kB/s)
  Terminated
  Reading package lists... Done
  E: Problem executing scripts APT::Update::Post-Invoke-Success 'if 
/usr/bin/test -w /var/cache/app-info -a -e /usr/bin/appstreamcli; then 
appstreamcli refresh > /dev/null; fi'
  E: Sub-process returned an error code

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: appstream 0.9.4-1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu May 19 19:08:30 2016
  InstallationDate: Installed on 2016-05-19 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: appstream
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1583829] Re: aptitude update -> appstreamcli uses 100% cpu

2016-05-19 Thread Trent V.

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

can confirm that purging appstream and then rerunning apt update fixed the 
issue.
version affected: appstream 0.9.4-1

@ #4 - Jacob
I had the same problem, I fixed with the following:

$ ps ax | grep appstream

find what the applications' process id is
usually about 5 numbers long

# use sudo if not root
$ kill -9 

this should bring your cpu back to normal
then:

$ sudo apt purge appstream

then clean up your system with:
$ sudo apt autoremove

if you canceled in the middle of the install and it's asking you to run 'sudo 
dpkg --configure -a'
run the command but once it get stuck on appstream kill it as shown above. dpkg 
will still complete after you've killed appstream. then purge appstream.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1583829

Title:
  aptitude update -> appstreamcli uses 100% cpu

Status in appstream package in Ubuntu:
  Confirmed

Bug description:
  I started aptitude and hit "u" to update package list. It stuck on
  "Loading cache" screen. I checked processes tree and found out
  aptitude was waiting for /usr/bin/appstreamcli which used 100% CPU and
  did nothing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: appstream 0.9.4-1
  Uname: Linux 4.6.0-040600-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May 20 01:52:53 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-05-01 (18 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: appstream
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1579712] Re: Refresh hangs due to strdup on non-NULL terminated string

2016-05-19 Thread Todd Bossaller

I ran the fix Matthias mentioned in post #24 and it fixed my issue.
Thanks

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1579712

Title:
  Refresh hangs due to strdup on non-NULL terminated string

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
   * Fixing this bug resolves the issue for people who might experience it.
   * See https://github.com/ximion/appstream/issues/35 for details.

  [Test Case 1]

   * Run `sudo appstreamcli refresh --force`
   * The AppStream cache should be updated, no change in behavior should be 
seen.

  [Test Case 2]

   * In case you were experiencing the almost-infinite hang when running
  `sudo appstreamcli refresh --force`, this issue should be fixed with
  the SRU.

  [Regression Potential]

   * Very low, since this only fixes the decompression code. There
  should be no sideeffects of that (given that the patch itself doesn't
  break anything, which it shouldn't, since it has been tested upstream
  for a while)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
   * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a

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

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

[Desktop-packages] [Bug 1583845] Re: Can't "apt-get update" - appstreamcli stuck at 100% Processor Utilization

2016-05-19 Thread Todd Bossaller

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

Yes click on the bug link below and check out post #24 for the fix. It
worked for me

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1583845

Title:
  Can't "apt-get update" - appstreamcli stuck at 100% Processor
  Utilization

Status in appstream package in Ubuntu:
  Confirmed

Bug description:
  I did a fresh install of Ubuntu 16.04 without being connected to the
  internet because when connected to the internet the install would lock
  up at the point that ubuntu was "Retrieving 56 of 56".

  Installation (without internet) was successful, then I connected to
  the internet and tried to update:

  The update-process seemed to be stuck, so I discovered that the
  command appstreamcli was at 100% processor utilization indefinitely.

  When I kill that process the update fails. This is clearly a bug, but
  hopefully someone can suggest a work-around until it is fixed.

  user@pc:~$ sudo apt-get update
  Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [94.5 kB]
  Hit:2 http://us.archive.ubuntu.com/ubuntu xenial InRelease
  Get:3 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [94.5 kB]
  Get:4 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease [92.2 kB]
  Fetched 281 kB in 0s (387 kB/s)
  Terminated
  Reading package lists... Done
  E: Problem executing scripts APT::Update::Post-Invoke-Success 'if 
/usr/bin/test -w /var/cache/app-info -a -e /usr/bin/appstreamcli; then 
appstreamcli refresh > /dev/null; fi'
  E: Sub-process returned an error code

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: appstream 0.9.4-1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu May 19 19:08:30 2016
  InstallationDate: Installed on 2016-05-19 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: appstream
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1510344] Re: Keyboard Backlight Turns on at boot

I've moved the part related to idle backlight reset to bug #1583861

** No longer affects: upower (Ubuntu)

** No longer affects: upower (Ubuntu Xenial)

** No longer affects: upower

** Patch removed: "upower-always-get-kbd-brightness.debdiff"
   
https://bugs.launchpad.net/dell-sputnik/+bug/1510344/+attachment/4665009/+files/upower-always-get-kbd-brightness.debdiff

** Patch removed: "0001-Fixed-dell-laptop-keyboard-backlight.patch"
   
https://bugs.launchpad.net/dell-sputnik/+bug/1510344/+attachment/4640489/+files/0001-Fixed-dell-laptop-keyboard-backlight.patch

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1510344

Title:
  Keyboard Backlight Turns on at boot

Status in Dell Sputnik:
  Confirmed
Status in gnome-settings-daemon:
  Fix Released
Status in One Hundred Papercuts:
  Confirmed
Status in Linux:
  Invalid
Status in unity-settings-daemon package in Ubuntu:
  In Progress
Status in unity-settings-daemon source package in Xenial:
  Fix Committed

Bug description:
  System: Dell XPS 13 9343

  Action: Boot computer

  Expected Behavior: Keyboard backlight would be off when computer is
  booted

  Actual Behavior: Keyboard backlight is on at boot

  This did not happen with Ubuntu 15.04

  There are new files in Ubuntu 15.10 -
  /sys/class/leds/dell::kbd_backlight$

  cat stop_timeout
  60s

   cat start_triggers 
  +keyboard +touchpad

  cat trigger 
  [none] AC-online BAT0-charging-or-full BAT0-charging BAT0-full 
BAT0-charging-blink-full-solid usb-gadget usb-host cpu0 cpu1 cpu2 cpu3 mmc0 
rfkill0

  cat brightness 
  2

  ---

  Unsure if these files are important, but included in the report

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.1.0-2-generic 4.1.0-2.2
  ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3
  Uname: Linux 4.1.0-2-generic x86_64
  ApportVersion: 2.18-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 2488 F pulseaudio
   /dev/snd/controlC0:  ubuntu 2488 F pulseaudio
  CasperVersion: 1.362
  CurrentDesktop: Unity
  Date: Tue Oct 27 01:29:47 2015
  IwConfig:
   enx00249b0981e3  no wireless extensions.
   
   lono wireless extensions.
  LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150730)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --- 
cdrom-detect/try-usb=true noprompt
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-2-generic N/A
   linux-backports-modules-4.1.0-2-generic  N/A
   linux-firmware   1.145
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1510344/+subscriptions

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

[Desktop-packages] [Bug 1583861] [NEW] Keyboard backlight isn't properly restored after idle on systems with hardwired configuration

Public bug reported:

In Dell or ThinkPad notebooks with keyboard backlight, the keybindings
to control the keyboard backlight don't emit any event to the userland,
about the state change, nor they request userland to change it (as it
happens in other models which emits KEY_KBDILLUM{UP,DOWN,TOGGLE}
events), this causes unity/gnome-settings daemon not to restore the
proper backlight after idle.

Steps to reproduce:
 0) ensure your keyboard backlight is on, and 
 gdbus call --system --dest org.freedesktop.UPower \
  --object-path /org/freedesktop/UPower/KbdBacklight \
  --method org.freedesktop.UPower.KbdBacklight.GetBrightness
returns a value != from 0. If not, just call the SetBrightness
method with a positive value, to turn on the backlight.
   
Now turn off the keyboard backlight (or set it to another level) 
using the laptop keys, and run:
 gsettings set org.gnome.desktop.session idle-delay 1
to make things easier to test.

 2) Wait one second and the screensaver should start. Wait the screen to
be turned off. If you just changed the brightness level at the step above,
once the screen is turned off, also the keyboard backlight should be turned 
off too.

 3) Now press a key or move the mouse.

Expected behavior:

 4) The keyboard backlight should be set back to the previous level (so it 
should stay off
or go back to the level you set before the idle timeout happened).

Actual behavior:

 5) The backlight is set to the level it had at point 0).

** Affects: dell-sputnik
 Importance: Undecided
 Status: New

** Affects: upower
 Importance: Unknown
 Status: Unknown

** Affects: gnome-settings-daemon (Ubuntu)
 Importance: Medium
 Status: New

** Affects: unity-settings-daemon (Ubuntu)
 Importance: Medium
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: New

** Affects: upower (Ubuntu)
 Importance: Medium
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: New

** Bug watch added: freedesktop.org Bugzilla #95457
   https://bugs.freedesktop.org/show_bug.cgi?id=95457

** Also affects: upower via
   https://bugs.freedesktop.org/show_bug.cgi?id=95457
   Importance: Unknown
   Status: Unknown

** Also affects: gnome-settings-daemon (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: unity-settings-daemon (Ubuntu)
   Importance: Undecided
   Status: New

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

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

** Changed in: unity-settings-daemon (Ubuntu)
   Importance: Undecided => Medium

** Changed in: gnome-settings-daemon (Ubuntu)
   Importance: Undecided => Medium

** Changed in: upower (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: unity-settings-daemon (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Summary changed:

- Keyboard backlight isn't properly reset after idle on systems with hardwired 
configuration
+ Keyboard backlight isn't properly restored after idle on systems with 
hardwired configuration

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1583861

Title:
  Keyboard backlight isn't properly restored after idle on systems with
  hardwired configuration

Status in Dell Sputnik:
  New
Status in Upower:
  Unknown
Status in gnome-settings-daemon package in Ubuntu:
  New
Status in unity-settings-daemon package in Ubuntu:
  New
Status in upower package in Ubuntu:
  New

Bug description:
  In Dell or ThinkPad notebooks with keyboard backlight, the keybindings
  to control the keyboard backlight don't emit any event to the
  userland, about the state change, nor they request userland to change
  it (as it happens in other models which emits
  KEY_KBDILLUM{UP,DOWN,TOGGLE} events), this causes unity/gnome-settings
  daemon not to restore the proper backlight after idle.

  Steps to reproduce:
   0) ensure your keyboard backlight is on, and 
   gdbus call --system --dest org.freedesktop.UPower \
--object-path /org/freedesktop/UPower/KbdBacklight \
--method org.freedesktop.UPower.KbdBacklight.GetBrightness
  returns a value != from 0. If not, just call the SetBrightness
  method with a positive value, to turn on the backlight.
 
  Now turn off the keyboard backlight (or set it to another level) 
  using the laptop keys, and run:
   gsettings set org.gnome.desktop.session idle-delay 1
  to make things easier to test.

   2) Wait one second and the screensaver should start. Wait the screen to
  be turned off. If you just changed the brightness level at the step above,
  once the screen is turned off, also the keyboard backlight should be 
turned off too.

   3) Now press a key or move the mouse.

  Expected behavior:

   4) The

[Desktop-packages] [Bug 1579712] Re: Refresh hangs due to strdup on non-NULL terminated string

@ximion: I missed that. After upgrading libappstream3 from -proposed,
everything works fine. Thanks.

The reason I warned against removing the binary is because it's a bad
practice in general, even though in this particular problem scenario the
removed binary gets restored when its package is upgraded. Package-
managed files should only be removed as a last resort when there isn't a
better/safer workaround that won't potentially leave any part of the
system in a broken or inconsistent state at any point in time. In this
case, a safe workaround does exist, which is to disable appstream's apt
config in the canonically-prescribed manner: appending ".disabled" to
the config's filename.

So the complete procedure to fix this safely would be:

$ sudo mv /etc/apt/apt.conf.d/50appstream 
/etc/apt/apt.conf.d/50appstream.disabled
$ cd /tmp && mkdir asfix
$ cd asfix
$ wget 
https://launchpad.net/ubuntu/+archive/primary/+files/appstream_0.9.4-1ubuntu1_amd64.deb
$ wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libappstream3_0.9.4-1ubuntu1_amd64.deb
$ sudo dpkg -i *.deb
$ sudo mv /etc/apt/apt.conf.d/50appstream.disabled 
/etc/apt/apt.conf.d/50appstream

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1579712

Title:
  Refresh hangs due to strdup on non-NULL terminated string

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
   * Fixing this bug resolves the issue for people who might experience it.
   * See https://github.com/ximion/appstream/issues/35 for details.

  [Test Case 1]

   * Run `sudo appstreamcli refresh --force`
   * The AppStream cache should be updated, no change in behavior should be 
seen.

  [Test Case 2]

   * In case you were experiencing the almost-infinite hang when running
  `sudo appstreamcli refresh --force`, this issue should be fixed with
  the SRU.

  [Regression Potential]

   * Very low, since this only fixes the decompression code. There
  should be no sideeffects of that (given that the patch itself doesn't
  break anything, which it shouldn't, since it has been tested upstream
  for a while)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
   * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a

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

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

[Desktop-packages] [Bug 1579712] Re: Refresh hangs due to strdup on non-NULL terminated string

Thanks. "Medium" importance for this bug? This seems like the most
critical bug I've ever encountered, considering that if I had left my
laptop alone to "finish updating" it might have melted and caused a
forest fire before I got back :)

Yeah, I think this one deserves a critical status; the fix needs to be
in the main repo ASAP.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1579712

Title:
  Refresh hangs due to strdup on non-NULL terminated string

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
   * Fixing this bug resolves the issue for people who might experience it.
   * See https://github.com/ximion/appstream/issues/35 for details.

  [Test Case 1]

   * Run `sudo appstreamcli refresh --force`
   * The AppStream cache should be updated, no change in behavior should be 
seen.

  [Test Case 2]

   * In case you were experiencing the almost-infinite hang when running
  `sudo appstreamcli refresh --force`, this issue should be fixed with
  the SRU.

  [Regression Potential]

   * Very low, since this only fixes the decompression code. There
  should be no sideeffects of that (given that the patch itself doesn't
  break anything, which it shouldn't, since it has been tested upstream
  for a while)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
   * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a

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

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

[Desktop-packages] [Bug 1574745] Re: Missing symlinks to match locales

2016-05-19 Thread Gunnar Hjalmarsson

I noticed a few worrying lo-dicts bugs at Debian. Some testing on Ubuntu re
:

$ dpkg-query -W hunspell-es myspell-es
hunspell-es 1:5.1.0-1ubuntu2
myspell-es  1.11-11
$ sudo apt install hunspell-es
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Suggested packages:
  hunspell
The following packages will be upgraded:
  hunspell-es
1 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B/242 kB of archives.
After this operation, 80,9 kB of additional disk space will be used.
(Reading database ... 307265 files and directories currently installed.)
Preparing to unpack .../hunspell-es_1%3a5.1.3-1_all.deb ...
Unpacking hunspell-es (1:5.1.3-1) over (1:5.1.0-1ubuntu2) ...
dpkg: error processing archive 
/var/cache/apt/archives/hunspell-es_1%3a5.1.3-1_all.deb (--unpack):
 trying to overwrite '/usr/share/hunspell/es_ES.aff', which is also in package 
myspell-es 1.11-11
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/hunspell-es_1%3a5.1.3-1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
$ sudo apt upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  hunspell-es myspell-es
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
$ sudo apt full-upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages will be REMOVED:
  hunspell-es
The following packages will be upgraded:
  myspell-es
1 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Need to get 201 kB of archives.
After this operation, 1 202 kB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.
$ 

Guess that's something we could live with, but
 and 
appear to be more tricky. Changing back to "verification-needed" for
now.

@Mattia, would appreciate your help to consider this SRU once again.
Right now I feel there is a need to add a couple of Breaks/Replaces.

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

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

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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice-dictionaries in Ubuntu.
https://bugs.launchpad.net/bugs/1574745

Title:
  Missing symlinks to match locales

Status in libreoffice-dictionaries package in Ubuntu:
  Fix Released
Status in libreoffice-dictionaries source package in Xenial:
  Fix Committed
Status in libreoffice-dictionaries package in Debian:
  Fix Released

Bug description:
  [Impact]

  Dictionaries like

  /usr/share/hunspell/es_ANY.aff
  /usr/share/hunspell/es_ANY.dic

  and

  /usr/share/hyphen/hyph_sv.dic

  are not recognized by LibreOffice, since their names don't include
  country codes. The proposed uploads in this PPA:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/lo-dicts-symlinks

  renames such files, and also adds symlinks in some cases for locales
  with other country codes but the 'main' locale for a language.

  [Test Case]

  Example:

  * Install the Swedish language via Language Support

  * Start libreoffice with a Swedish locale
LC_CTYPE=sv_SE.UTF-8 libreoffice --writer

  * Find that hyphenation is not available

  [Regression Potential]

  There is a drawback with this fix: For e.g. Spanish and Arabic users
  the symlinks will add items in the spellcheck menus of other
  applications but LibreOffice, where it would have worked without those
  symlinks. OTOH, this is the way it has been handled in Ubuntu up to
  15.10, so the fix basically restores the previous behavior.

  Other than that, the regression risk is low. This is only about files
  (including symlinks) in the /usr/share/{hunspell,hyphen,mythes}
  directories with limited affect on the system.

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

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

[Desktop-packages] [Bug 1534501] Re: dnsmasq error logs fill up storage drive memory

2016-05-19 Thread Steve Langasek

This appears to be a conflict between network-manager's integration with
dnsmasq-base, and the dnsmasq package.

If there isn't a specific reason for the dnsmasq package to be installed
on your system, the straightforward workaround is to remove dnsmasq with
'apt purge dnsmasq'.

** Changed in: resolvconf (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: rsyslog (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  dnsmasq error logs fill up storage drive memory

Status in dnsmasq package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Invalid
Status in rsyslog package in Ubuntu:
  Invalid

Bug description:
  snippet of logs.

  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30416]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30416]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
child quit unexpectedly; refreshing DNS
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: starting 
dnsmasq...
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq not available 
on the bus, can't update servers.
  Jan 15 00:28:24 localhost NetworkManager[1211]:  [1452846504.397836] 
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: 
Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such 
name
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30429]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30429]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
child quit unexpectedly; refreshing DNS
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: starting 
dnsmasq...
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq not available 
on the bus, can't update servers.
  Jan 15 00:28:24 localhost NetworkManager[1211]:  [1452846504.407691] 
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: 
Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such 
name
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30442]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30442]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
child quit unexpectedly; refreshing DNS
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: starting 
dnsmasq...
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq not available 
on the bus, can't update servers.
  Jan 15 00:28:24 localhost NetworkManager[1211]:  [1452846504.419365] 
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: 
Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such 
name
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for

[Desktop-packages] [Bug 1576780] Re: Needs to implement the full DEP-11 icon spec for compatibility with 3rd-party repos

** Changed in: appstream-glib (Ubuntu)
 Assignee: (unassigned) => Matthias Klumpp (ximion)

** Changed in: appstream-glib (Ubuntu Xenial)
Milestone: None => xenial-updates

** Changed in: appstream-glib (Ubuntu)
Milestone: xenial-updates => None

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream-glib in Ubuntu.
https://bugs.launchpad.net/bugs/1576780

Title:
  Needs to implement the full DEP-11 icon spec for compatibility with
  3rd-party repos

Status in appstream-glib package in Ubuntu:
  Fix Released
Status in appstream-glib source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The AppStream YAML spec describes a way to include width/height properties 
in cached-icon metadata, which isn't forward-compatible to the old spec.
   * asglib doesn't implement the full spec in the release present in Xenial, 
so it ignores cached icons with size info, as well as it doesn't support 
several features present in the spec, e.g. the remote icon type.
   * This leads to AppStream components from 3rd-party repos/PPAs not showing 
up in GNOME Software, since asglib is unable to find icons if they use a more 
recent version of the spec.
   * The attched patch fixes this.

  [Test Case 1]

   * Close all instances of GNOME Software (also the background daemon!)
   * Launch GNOME Software again: All apps should be present, you should notice 
no change.

  [Test Case 2]

   * Close all instances of GNOME Software (also the background daemon!)
   * Get new-style metadata, e.g. from Elementary or Debian[1], or simply add 
the SIL repo which is shipping that metadata now: http://packages.sil.org/ 
(that would be the easiest way to test)
   * Launch GNOME Software again: All apps should be present, including the 
3rd-party ones (search for "FieldWorks").

  [1]: ftp://ftp.debian.org/debian/dists/stretch/main/dep11/

  [Regression Potential]

   * This is adding a missing feature, restoring compatibility with 3rd-
  party repos. The existing data should be parsed as before, so I don't
  see much regression potential ("Test Case 1" needs to work)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/hughsie/appstream-glib/commit/628e3cfb1c62c3177d6decd86102217f2546e0a2
   * The fix is also present in Debian.

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

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

[Desktop-packages] [Bug 1579712] Re: Refresh hangs due to strdup on non-NULL terminated string

@Lonnie: this is the same bug. Install the package via dpkg as described
in post #24, that should solve the 100% CPU issue too - the issue
manifests itself in some very interesting ways sometimes.


** Changed in: appstream (Ubuntu)
 Assignee: (unassigned) => Matthias Klumpp (ximion)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1579712

Title:
  Refresh hangs due to strdup on non-NULL terminated string

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
   * Fixing this bug resolves the issue for people who might experience it.
   * See https://github.com/ximion/appstream/issues/35 for details.

  [Test Case 1]

   * Run `sudo appstreamcli refresh --force`
   * The AppStream cache should be updated, no change in behavior should be 
seen.

  [Test Case 2]

   * In case you were experiencing the almost-infinite hang when running
  `sudo appstreamcli refresh --force`, this issue should be fixed with
  the SRU.

  [Regression Potential]

   * Very low, since this only fixes the decompression code. There
  should be no sideeffects of that (given that the patch itself doesn't
  break anything, which it shouldn't, since it has been tested upstream
  for a while)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
   * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a

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

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

[Desktop-packages] [Bug 1579712] Re: Refresh hangs due to strdup on non-NULL terminated string

2016-05-19 Thread Mariano Marcelo Panizzo

Updated appstream & libappstream3 to version 0.9.4-1ubuntu1, and
libappstream-glib8 to 0.5.13-1ubuntu1 just in case... Fixed for me.
Thanks you!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1579712

Title:
  Refresh hangs due to strdup on non-NULL terminated string

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
   * Fixing this bug resolves the issue for people who might experience it.
   * See https://github.com/ximion/appstream/issues/35 for details.

  [Test Case 1]

   * Run `sudo appstreamcli refresh --force`
   * The AppStream cache should be updated, no change in behavior should be 
seen.

  [Test Case 2]

   * In case you were experiencing the almost-infinite hang when running
  `sudo appstreamcli refresh --force`, this issue should be fixed with
  the SRU.

  [Regression Potential]

   * Very low, since this only fixes the decompression code. There
  should be no sideeffects of that (given that the patch itself doesn't
  break anything, which it shouldn't, since it has been tested upstream
  for a while)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
   * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a

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

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

[Desktop-packages] [Bug 1579712] Re: Refresh hangs due to strdup on non-NULL terminated string

I tried to update after a fresh install and could not get past the appstreamcli 
infinite 100% processor utilization:
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1583845

My laptop got almost smoking hot before I finally killed the
appstreamcli process!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1579712

Title:
  Refresh hangs due to strdup on non-NULL terminated string

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
   * Fixing this bug resolves the issue for people who might experience it.
   * See https://github.com/ximion/appstream/issues/35 for details.

  [Test Case 1]

   * Run `sudo appstreamcli refresh --force`
   * The AppStream cache should be updated, no change in behavior should be 
seen.

  [Test Case 2]

   * In case you were experiencing the almost-infinite hang when running
  `sudo appstreamcli refresh --force`, this issue should be fixed with
  the SRU.

  [Regression Potential]

   * Very low, since this only fixes the decompression code. There
  should be no sideeffects of that (given that the patch itself doesn't
  break anything, which it shouldn't, since it has been tested upstream
  for a while)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
   * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a

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

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

[Desktop-packages] [Bug 1583845] Re: Can't "apt-get update" - appstreamcli stuck at 100% Processor Utilization

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

Yes, this is already fixed in proposed-updates.
A more complete fix is in Yakkety, but the one in x-p-u will do the job just 
fine (see the bug report this one is a duplicate of for details).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1583845

Title:
  Can't "apt-get update" - appstreamcli stuck at 100% Processor
  Utilization

Status in appstream package in Ubuntu:
  Confirmed

Bug description:
  I did a fresh install of Ubuntu 16.04 without being connected to the
  internet because when connected to the internet the install would lock
  up at the point that ubuntu was "Retrieving 56 of 56".

  Installation (without internet) was successful, then I connected to
  the internet and tried to update:

  The update-process seemed to be stuck, so I discovered that the
  command appstreamcli was at 100% processor utilization indefinitely.

  When I kill that process the update fails. This is clearly a bug, but
  hopefully someone can suggest a work-around until it is fixed.

  user@pc:~$ sudo apt-get update
  Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [94.5 kB]
  Hit:2 http://us.archive.ubuntu.com/ubuntu xenial InRelease
  Get:3 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [94.5 kB]
  Get:4 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease [92.2 kB]
  Fetched 281 kB in 0s (387 kB/s)
  Terminated
  Reading package lists... Done
  E: Problem executing scripts APT::Update::Post-Invoke-Success 'if 
/usr/bin/test -w /var/cache/app-info -a -e /usr/bin/appstreamcli; then 
appstreamcli refresh > /dev/null; fi'
  E: Sub-process returned an error code

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: appstream 0.9.4-1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu May 19 19:08:30 2016
  InstallationDate: Installed on 2016-05-19 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: appstream
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1579712] Re: Refresh hangs due to strdup on non-NULL terminated string

2016-05-19 Thread Tomas Caram

Mathias. 
Downloading and installing deb fixed it for me. Thanks!.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1579712

Title:
  Refresh hangs due to strdup on non-NULL terminated string

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
   * Fixing this bug resolves the issue for people who might experience it.
   * See https://github.com/ximion/appstream/issues/35 for details.

  [Test Case 1]

   * Run `sudo appstreamcli refresh --force`
   * The AppStream cache should be updated, no change in behavior should be 
seen.

  [Test Case 2]

   * In case you were experiencing the almost-infinite hang when running
  `sudo appstreamcli refresh --force`, this issue should be fixed with
  the SRU.

  [Regression Potential]

   * Very low, since this only fixes the decompression code. There
  should be no sideeffects of that (given that the patch itself doesn't
  break anything, which it shouldn't, since it has been tested upstream
  for a while)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
   * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a

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

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

[Desktop-packages] [Bug 1583845] Re: Can't "apt-get update" - appstreamcli stuck at 100% Processor Utilization

2016-05-19 Thread rot13

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

I noticed the same problem on a fresh 16.04 install. I booted it again
few days later, and noticed "appstreamcli refresh" process using 100%
cpu. Running strace on it doesn't show any activity. Gdb shows that it
seems to be looping in as_yamldata_parse_distro_data ():

(gdb) bt
#0  0x7eff42d03c4c in as_yamldata_parse_distro_data ()
   from /usr/lib/x86_64-linux-gnu/libappstream.so.3
#1  0x7eff42d05537 in as_metadata_parse_yaml ()
   from /usr/lib/x86_64-linux-gnu/libappstream.so.3
#2  0x7eff42d05c55 in as_metadata_parse_file ()
   from /usr/lib/x86_64-linux-gnu/libappstream.so.3
#3  0x7eff42d08d49 in as_data_pool_update ()
   from /usr/lib/x86_64-linux-gnu/libappstream.so.3
#4  0x7eff42cfe272 in as_cache_builder_refresh ()
   from /usr/lib/x86_64-linux-gnu/libappstream.so.3
#5  0x004049de in ascli_refresh_cache ()
#6  0x00403ceb in as_client_run ()
#7  0x7eff4292c830 in __libc_start_main (main=0x403490 , argc=2, 
argv=0x7ffc131f67c8, init=, fini=, 
rtld_fini=, stack_end=0x7ffc131f67b8)
at ../csu/libc-start.c:291
#8  0x00403519 in _start ()

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1583845

Title:
  Can't "apt-get update" - appstreamcli stuck at 100% Processor
  Utilization

Status in appstream package in Ubuntu:
  Confirmed

Bug description:
  I did a fresh install of Ubuntu 16.04 without being connected to the
  internet because when connected to the internet the install would lock
  up at the point that ubuntu was "Retrieving 56 of 56".

  Installation (without internet) was successful, then I connected to
  the internet and tried to update:

  The update-process seemed to be stuck, so I discovered that the
  command appstreamcli was at 100% processor utilization indefinitely.

  When I kill that process the update fails. This is clearly a bug, but
  hopefully someone can suggest a work-around until it is fixed.

  user@pc:~$ sudo apt-get update
  Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [94.5 kB]
  Hit:2 http://us.archive.ubuntu.com/ubuntu xenial InRelease
  Get:3 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [94.5 kB]
  Get:4 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease [92.2 kB]
  Fetched 281 kB in 0s (387 kB/s)
  Terminated
  Reading package lists... Done
  E: Problem executing scripts APT::Update::Post-Invoke-Success 'if 
/usr/bin/test -w /var/cache/app-info -a -e /usr/bin/appstreamcli; then 
appstreamcli refresh > /dev/null; fi'
  E: Sub-process returned an error code

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: appstream 0.9.4-1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu May 19 19:08:30 2016
  InstallationDate: Installed on 2016-05-19 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: appstream
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1579712] Re: Refresh hangs due to strdup on non-NULL terminated string

Weird, I wonder what happened that many people are experiencing this now...
Removing `/usr/bin/appstreamcli` is fine if you install the fixed package 
afterwards.

To install this manually, please do (for amd64, adjust URLs for other
architectures):

```
cd /tmp && mkdir asfix
cd asfix
wget 
https://launchpad.net/ubuntu/+archive/primary/+files/appstream_0.9.4-1ubuntu1_amd64.deb
wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libappstream3_0.9.4-1ubuntu1_amd64.deb
sudo dpkg -i *.deb
```

This should solve the issue. Please report back if this is fixed, or if
you are still experiencing issues!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1579712

Title:
  Refresh hangs due to strdup on non-NULL terminated string

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
   * Fixing this bug resolves the issue for people who might experience it.
   * See https://github.com/ximion/appstream/issues/35 for details.

  [Test Case 1]

   * Run `sudo appstreamcli refresh --force`
   * The AppStream cache should be updated, no change in behavior should be 
seen.

  [Test Case 2]

   * In case you were experiencing the almost-infinite hang when running
  `sudo appstreamcli refresh --force`, this issue should be fixed with
  the SRU.

  [Regression Potential]

   * Very low, since this only fixes the decompression code. There
  should be no sideeffects of that (given that the patch itself doesn't
  break anything, which it shouldn't, since it has been tested upstream
  for a while)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
   * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a

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

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

[Desktop-packages] [Bug 1579712] Re: Refresh hangs due to strdup on non-NULL terminated string

@John Wang: Did you also update libappstream3? Because that's where the
bug actually is ;-)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1579712

Title:
  Refresh hangs due to strdup on non-NULL terminated string

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
   * Fixing this bug resolves the issue for people who might experience it.
   * See https://github.com/ximion/appstream/issues/35 for details.

  [Test Case 1]

   * Run `sudo appstreamcli refresh --force`
   * The AppStream cache should be updated, no change in behavior should be 
seen.

  [Test Case 2]

   * In case you were experiencing the almost-infinite hang when running
  `sudo appstreamcli refresh --force`, this issue should be fixed with
  the SRU.

  [Regression Potential]

   * Very low, since this only fixes the decompression code. There
  should be no sideeffects of that (given that the patch itself doesn't
  break anything, which it shouldn't, since it has been tested upstream
  for a while)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
   * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a

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

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

[Desktop-packages] [Bug 1583845] Re: Can't "apt-get update" - appstreamcli stuck at 100% Processor Utilization

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

** This bug has been marked a duplicate of bug 1579712
   Refresh hangs due to strdup on non-NULL terminated string

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1583845

Title:
  Can't "apt-get update" - appstreamcli stuck at 100% Processor
  Utilization

Status in appstream package in Ubuntu:
  Confirmed

Bug description:
  I did a fresh install of Ubuntu 16.04 without being connected to the
  internet because when connected to the internet the install would lock
  up at the point that ubuntu was "Retrieving 56 of 56".

  Installation (without internet) was successful, then I connected to
  the internet and tried to update:

  The update-process seemed to be stuck, so I discovered that the
  command appstreamcli was at 100% processor utilization indefinitely.

  When I kill that process the update fails. This is clearly a bug, but
  hopefully someone can suggest a work-around until it is fixed.

  user@pc:~$ sudo apt-get update
  Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [94.5 kB]
  Hit:2 http://us.archive.ubuntu.com/ubuntu xenial InRelease
  Get:3 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [94.5 kB]
  Get:4 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease [92.2 kB]
  Fetched 281 kB in 0s (387 kB/s)
  Terminated
  Reading package lists... Done
  E: Problem executing scripts APT::Update::Post-Invoke-Success 'if 
/usr/bin/test -w /var/cache/app-info -a -e /usr/bin/appstreamcli; then 
appstreamcli refresh > /dev/null; fi'
  E: Sub-process returned an error code

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: appstream 0.9.4-1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu May 19 19:08:30 2016
  InstallationDate: Installed on 2016-05-19 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: appstream
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1583845] Re: Can't "apt-get update" - appstreamcli stuck at 100% Processor Utilization

2016-05-19 Thread Jan Claeys

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

An strace of the appstreamcli process while it's stuck at 100% CPU shows
nothing at all, so it looks like it got stuck in a loop doing
"something" that needs no syscalls...

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1583845

Title:
  Can't "apt-get update" - appstreamcli stuck at 100% Processor
  Utilization

Status in appstream package in Ubuntu:
  Confirmed

Bug description:
  I did a fresh install of Ubuntu 16.04 without being connected to the
  internet because when connected to the internet the install would lock
  up at the point that ubuntu was "Retrieving 56 of 56".

  Installation (without internet) was successful, then I connected to
  the internet and tried to update:

  The update-process seemed to be stuck, so I discovered that the
  command appstreamcli was at 100% processor utilization indefinitely.

  When I kill that process the update fails. This is clearly a bug, but
  hopefully someone can suggest a work-around until it is fixed.

  user@pc:~$ sudo apt-get update
  Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [94.5 kB]
  Hit:2 http://us.archive.ubuntu.com/ubuntu xenial InRelease
  Get:3 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [94.5 kB]
  Get:4 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease [92.2 kB]
  Fetched 281 kB in 0s (387 kB/s)
  Terminated
  Reading package lists... Done
  E: Problem executing scripts APT::Update::Post-Invoke-Success 'if 
/usr/bin/test -w /var/cache/app-info -a -e /usr/bin/appstreamcli; then 
appstreamcli refresh > /dev/null; fi'
  E: Sub-process returned an error code

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: appstream 0.9.4-1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu May 19 19:08:30 2016
  InstallationDate: Installed on 2016-05-19 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: appstream
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1579712] Re: Refresh hangs due to strdup on non-NULL terminated string

Okay, I've successfully upgraded to appstream 0.9.4-1ubuntu1 from the
-proposed repo, but subsequent `sudo apt-get update` invocations still
hang on appstreamcli. I have no idea what to do now.

@ludentico: Yes, sorry, I was in a hurry and didn't include full paths.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1579712

Title:
  Refresh hangs due to strdup on non-NULL terminated string

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
   * Fixing this bug resolves the issue for people who might experience it.
   * See https://github.com/ximion/appstream/issues/35 for details.

  [Test Case 1]

   * Run `sudo appstreamcli refresh --force`
   * The AppStream cache should be updated, no change in behavior should be 
seen.

  [Test Case 2]

   * In case you were experiencing the almost-infinite hang when running
  `sudo appstreamcli refresh --force`, this issue should be fixed with
  the SRU.

  [Regression Potential]

   * Very low, since this only fixes the decompression code. There
  should be no sideeffects of that (given that the patch itself doesn't
  break anything, which it shouldn't, since it has been tested upstream
  for a while)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
   * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a

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

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

[Desktop-packages] [Bug 1579712] Re: Refresh hangs due to strdup on non-NULL terminated string

2016-05-19 Thread Eduardo

@johnwang

I guess you meant

$ sudo mv /etc/apt/apt.conf.d/50appstream
/etc/apt/apt.conf.d/50appstream.disabled

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1579712

Title:
  Refresh hangs due to strdup on non-NULL terminated string

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
   * Fixing this bug resolves the issue for people who might experience it.
   * See https://github.com/ximion/appstream/issues/35 for details.

  [Test Case 1]

   * Run `sudo appstreamcli refresh --force`
   * The AppStream cache should be updated, no change in behavior should be 
seen.

  [Test Case 2]

   * In case you were experiencing the almost-infinite hang when running
  `sudo appstreamcli refresh --force`, this issue should be fixed with
  the SRU.

  [Regression Potential]

   * Very low, since this only fixes the decompression code. There
  should be no sideeffects of that (given that the patch itself doesn't
  break anything, which it shouldn't, since it has been tested upstream
  for a while)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
   * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a

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

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

[Desktop-packages] [Bug 1583845] Re: Can't "apt-get update" - appstreamcli stuck at 100% Processor Utilization

2016-05-19 Thread Jan Claeys

I have the same problem, and it happens with both apt-get and synaptic
when I try to update the list of packages.

It has nothing to do with installing without an internet connection, as
for me this just started happening tonight (it worked fine before).

A "workaround" is to remove the appstream package, which also removes
the GNOME/Ubuntu Software package (the GUI software installer), which is
fine for me (I never use those anyway), but probably not for "regular"
users...

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1583845

Title:
  Can't "apt-get update" - appstreamcli stuck at 100% Processor
  Utilization

Status in appstream package in Ubuntu:
  Confirmed

Bug description:
  I did a fresh install of Ubuntu 16.04 without being connected to the
  internet because when connected to the internet the install would lock
  up at the point that ubuntu was "Retrieving 56 of 56".

  Installation (without internet) was successful, then I connected to
  the internet and tried to update:

  The update-process seemed to be stuck, so I discovered that the
  command appstreamcli was at 100% processor utilization indefinitely.

  When I kill that process the update fails. This is clearly a bug, but
  hopefully someone can suggest a work-around until it is fixed.

  user@pc:~$ sudo apt-get update
  Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [94.5 kB]
  Hit:2 http://us.archive.ubuntu.com/ubuntu xenial InRelease
  Get:3 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [94.5 kB]
  Get:4 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease [92.2 kB]
  Fetched 281 kB in 0s (387 kB/s)
  Terminated
  Reading package lists... Done
  E: Problem executing scripts APT::Update::Post-Invoke-Success 'if 
/usr/bin/test -w /var/cache/app-info -a -e /usr/bin/appstreamcli; then 
appstreamcli refresh > /dev/null; fi'
  E: Sub-process returned an error code

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: appstream 0.9.4-1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu May 19 19:08:30 2016
  InstallationDate: Installed on 2016-05-19 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: appstream
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1583845] Re: Can't "apt-get update" - appstreamcli stuck at 100% Processor Utilization

** Description changed:

  I did a fresh install of Ubuntu 16.04 without being connected to the
  internet because when connected to the internet the install would lock
  up at the point that ubuntu was "Retrieving 56 of 56".
  
- Installation (without internet) was successful, then I connected to the 
internet and tried to update:
- sudo apt-get update
+ Installation (without internet) was successful, then I connected to the
+ internet and tried to update:
  
- The update-process seemed to be stuck, so I discovered that the command
- appstreamcli was at 100% processor utilization indefinitely.
+ user@pc:~$ sudo apt-get update
+ Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [94.5 kB]
+ Hit:2 http://us.archive.ubuntu.com/ubuntu xenial InRelease
+ Get:3 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [94.5 kB]  
  
+ Get:4 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease [92.2 
kB]   
+ Fetched 281 kB in 0s (387 kB/s)
+ Terminated
+ Reading package lists... Done
+ E: Problem executing scripts APT::Update::Post-Invoke-Success 'if 
/usr/bin/test -w /var/cache/app-info -a -e /usr/bin/appstreamcli; then 
appstreamcli refresh > /dev/null; fi'
+ E: Sub-process returned an error code
+ 
+ 
+ The update-process seemed to be stuck, so I discovered that the command 
appstreamcli was at 100% processor utilization indefinitely.
  
  When I kill that process the update fails. This is clearly a bug, but
  hopefully someone can suggest a work-around until it is fixed.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: appstream 0.9.4-1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu May 19 19:08:30 2016
  InstallationDate: Installed on 2016-05-19 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
-  LANGUAGE=en_US
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_US
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: appstream
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  I did a fresh install of Ubuntu 16.04 without being connected to the
  internet because when connected to the internet the install would lock
  up at the point that ubuntu was "Retrieving 56 of 56".
  
  Installation (without internet) was successful, then I connected to the
  internet and tried to update:
  
+ The update-process seemed to be stuck, so I discovered that the command
+ appstreamcli was at 100% processor utilization indefinitely.
+ 
+ When I kill that process the update fails. This is clearly a bug, but
+ hopefully someone can suggest a work-around until it is fixed.
+ 
  user@pc:~$ sudo apt-get update
  Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [94.5 kB]
  Hit:2 http://us.archive.ubuntu.com/ubuntu xenial InRelease
- Get:3 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [94.5 kB]  
  
- Get:4 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease [92.2 
kB]   
- Fetched 281 kB in 0s (387 kB/s)
+ Get:3 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [94.5 kB]
+ Get:4 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease [92.2 kB]
+ Fetched 281 kB in 0s (387 kB/s)
  Terminated
  Reading package lists... Done
  E: Problem executing scripts APT::Update::Post-Invoke-Success 'if 
/usr/bin/test -w /var/cache/app-info -a -e /usr/bin/appstreamcli; then 
appstreamcli refresh > /dev/null; fi'
  E: Sub-process returned an error code
  
- 
- The update-process seemed to be stuck, so I discovered that the command 
appstreamcli was at 100% processor utilization indefinitely.
- 
- When I kill that process the update fails. This is clearly a bug, but
- hopefully someone can suggest a work-around until it is fixed.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: appstream 0.9.4-1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu May 19 19:08:30 2016
  InstallationDate: Installed on 2016-05-19 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: appstream
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1583845

Title:
  Can't "apt-get update" - appstreamcli stuck at 100% Processor
  Utilization

Status in appstream package in Ubuntu:

[Desktop-packages] [Bug 1579712] Re: Refresh hangs due to strdup on non-NULL terminated string

2016-05-19 Thread strav

Disabled all my repositories by commenting out everything in
/etc/apt/sources.list and moving everything out of
/etc/apt/sources.list.d; it did the trick: could update appstream from
proposed repository. Thanks!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1579712

Title:
  Refresh hangs due to strdup on non-NULL terminated string

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
   * Fixing this bug resolves the issue for people who might experience it.
   * See https://github.com/ximion/appstream/issues/35 for details.

  [Test Case 1]

   * Run `sudo appstreamcli refresh --force`
   * The AppStream cache should be updated, no change in behavior should be 
seen.

  [Test Case 2]

   * In case you were experiencing the almost-infinite hang when running
  `sudo appstreamcli refresh --force`, this issue should be fixed with
  the SRU.

  [Regression Potential]

   * Very low, since this only fixes the decompression code. There
  should be no sideeffects of that (given that the patch itself doesn't
  break anything, which it shouldn't, since it has been tested upstream
  for a while)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
   * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a

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

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

[Desktop-packages] [Bug 1579712] Re: Refresh hangs due to strdup on non-NULL terminated string

That last command should have been:

$ sudo mv 50appstream.disabled 50appstream

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1579712

Title:
  Refresh hangs due to strdup on non-NULL terminated string

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
   * Fixing this bug resolves the issue for people who might experience it.
   * See https://github.com/ximion/appstream/issues/35 for details.

  [Test Case 1]

   * Run `sudo appstreamcli refresh --force`
   * The AppStream cache should be updated, no change in behavior should be 
seen.

  [Test Case 2]

   * In case you were experiencing the almost-infinite hang when running
  `sudo appstreamcli refresh --force`, this issue should be fixed with
  the SRU.

  [Regression Potential]

   * Very low, since this only fixes the decompression code. There
  should be no sideeffects of that (given that the patch itself doesn't
  break anything, which it shouldn't, since it has been tested upstream
  for a while)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
   * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a

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

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

[Desktop-packages] [Bug 1579712] Re: Refresh hangs due to strdup on non-NULL terminated string

@ludentico: Never `rm` files without also removing the package they
belong to.

I discovered a workaround:

$ sudo mv 50appstream 50appstream.disabled
$ sudo apt-get update
$ ... [do what you need here] ...
$ sudo 50appstream.disabled 50appstream

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1579712

Title:
  Refresh hangs due to strdup on non-NULL terminated string

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
   * Fixing this bug resolves the issue for people who might experience it.
   * See https://github.com/ximion/appstream/issues/35 for details.

  [Test Case 1]

   * Run `sudo appstreamcli refresh --force`
   * The AppStream cache should be updated, no change in behavior should be 
seen.

  [Test Case 2]

   * In case you were experiencing the almost-infinite hang when running
  `sudo appstreamcli refresh --force`, this issue should be fixed with
  the SRU.

  [Regression Potential]

   * Very low, since this only fixes the decompression code. There
  should be no sideeffects of that (given that the patch itself doesn't
  break anything, which it shouldn't, since it has been tested upstream
  for a while)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
   * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a

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

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

[Desktop-packages] [Bug 1554023] Re: Perform an apt update if there is no appstream available

I wonder if I'm suffering from this issue. Please take a look at the bug I 
submitted:
https://bugs.launchpad.net/bugs/1583845

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1554023

Title:
  Perform an apt update if there is no appstream available

Status in gnome-software package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Fix Released

Bug description:
  appstream's IndexTarget doesn't take effect until the first 'apt
  update' after it is installed. This means you get no installed
  software after first installing g-s until you update again.

  I tried to ask apt's developers if they could see a way to fix this
  but on first reply they deny there is a problem at all.

http://comments.gmane.org/gmane.linux.debian.apt.devel/30085

  So I think we have to workaround the problem somehow. First strawman:
  have gnome-software do an 'update' on first launch if it finds no
  appstream metadata and /etc/apt/apt.conf.d/50appstream is installed.

  We also need to fix this in livecd-rootfs for new installs. I guess
  there we can add a hook to do an update as part of the build.

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

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

[Desktop-packages] [Bug 1583845] Re: Can't "apt-get update" - appstreamcli stuck at 100% Processor Utilization

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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1583845

Title:
  Can't "apt-get update" - appstreamcli stuck at 100% Processor
  Utilization

Status in appstream package in Ubuntu:
  Confirmed

Bug description:
  I did a fresh install of Ubuntu 16.04 without being connected to the
  internet because when connected to the internet the install would lock
  up at the point that ubuntu was "Retrieving 56 of 56".

  Installation (without internet) was successful, then I connected to the 
internet and tried to update:
  sudo apt-get update

  The update-process seemed to be stuck, so I discovered that the
  command appstreamcli was at 100% processor utilization indefinitely.

  When I kill that process the update fails. This is clearly a bug, but
  hopefully someone can suggest a work-around until it is fixed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: appstream 0.9.4-1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu May 19 19:08:30 2016
  InstallationDate: Installed on 2016-05-19 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: appstream
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1583847] [NEW] /usr/bin/transmission-gtk:11:tr_isTorrent:tr_torrentInfo:tr_torrentHasMetadata:tr_cpHasAll:tr_cpGetStatus

2016-05-19 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding transmission.  This problem was most recently seen with
version 2.84-3ubuntu3, the problem page at
https://errors.ubuntu.com/problem/04e2e595aafce2a75194c528743ccb125a9a
contains more details.

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


** Tags: kylin-14.10 kylin-15.04 saucy trusty utopic vivid wily xenial

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to transmission in Ubuntu.
https://bugs.launchpad.net/bugs/1583847

Title:
  /usr/bin/transmission-
  
gtk:11:tr_isTorrent:tr_torrentInfo:tr_torrentHasMetadata:tr_cpHasAll:tr_cpGetStatus

Status in transmission package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding transmission.  This problem was most recently seen with
  version 2.84-3ubuntu3, the problem page at
  https://errors.ubuntu.com/problem/04e2e595aafce2a75194c528743ccb125a9a
  contains more details.

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

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

[Desktop-packages] [Bug 1059185] Re: bluetooth-wizard doesn't find any devices

2016-05-19 Thread Rolf Leggewie

Konrad, that's premature.  This problem was reported for example against
trusty which until very recently was the latest LTS.  Please stop
closing tickets just because they are old.  You can always ask if people
are still affected by this problem and then close the ticket if there is
no response.

** Changed in: bluez (Ubuntu)
   Status: Invalid => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-bluetooth in Ubuntu.
https://bugs.launchpad.net/bugs/1059185

Title:
  bluetooth-wizard doesn't find any devices

Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  I have just upgrade to Quantal from Precise.
  I have a bluetooth usb dongle, that lets me use my bluetooth keyboard and 
mouse. They worked without problems before the upgrade, but now they don't. I 
removed them and tried to add them again, but the bluetooth-wizard is stuck 
searching for devices, and doesn't find any.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: gnome-bluetooth 3.6.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Uname: Linux 3.5.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.5.3-0ubuntu1
  Architecture: amd64
  Date: Sun Sep 30 11:45:37 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: gnome-bluetooth
  UpgradeStatus: Upgraded to quantal on 2012-09-29 (0 days ago)

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

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

[Desktop-packages] [Bug 1582670] Re: Add auto-detect and -installation routine to sound configuration

2016-05-19 Thread Andrea Azzarone

** Also affects: unity-control-center (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: unity (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1582670

Title:
  Add auto-detect and -installation routine to sound configuration

Status in unity-control-center package in Ubuntu:
  New

Bug description:
  Sudden absence of a audio output device(s) after updates or
  misconfiguration is a quite popular error in many Ubuntu versions. The
  sound configuration panel in unity doesn't offer any support to
  automatically detect sound hardware and install necessary drivers. I'd
  be nice if it did including the following functions:

- Selection of backend. There's `alsa` and `jack` and possibly more and no 
reason to bother Ubuntu users with that except for one page in a guided dialog.
- Auto-detection of hardware. Although non-deterministic because of "cheap" 
hardware which doesn't identify itself correctly as audio hardware, there 
should be a page in a guided dialog allowing selection for correctly identified 
hardware (including eventual workarounds for detection).
- detection of necessary drivers and support for choice if there's more 
than one available

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: openafs
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: »/apps/compiz-1/general/screen0/options/active_plugins« wurde 
kein Wert zugewiesen
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue May 17 13:29:30 2016
  DistUpgraded: 2016-03-14 15:43:39,246 DEBUG enabling apt cron job
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-22-generic, x86_64: installed
   openafs, 1.6.15, 4.4.0-22-generic, x86_64: installed
   vboxhost, 5.0.20, 4.4.0-22-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3904]
  InstallationDate: Installed on 2015-12-12 (156 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20221
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro 
rootflags=subvol=ubuntu-main-root
  SourcePackage: unity
  UpgradeStatus: Upgraded to xenial on 2016-03-14 (63 days ago)
  dmi.bios.date: 07/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 71CN51WW(V1.21)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Z500 Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch:
  dmi.product.name: 20221
  dmi.product.version: Lenovo IdeaPad Z500 Touch
  dmi.sys.vendor: LENOVO
  upstart.unity-panel-service-lockscreen.log:
   (unity-panel-service:31881): GLib-CRITICAL **: Source ID 4294967295 was not 
found when attempting to remove it
   
   (unity-panel-service:5623): GLib-CRITICAL **: Source ID 4294967295 was not 
found when attempting to remove it
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue May 17 12:10:01 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5557 
   vendor CMN
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Desktop-packages] [Bug 1579712] Re: Refresh hangs due to strdup on non-NULL terminated string

2016-05-19 Thread Eduardo

Removing appstreamcli seems to do the trick. I'm not aware of side
effects

sudo rm /usr/bin/appstreamcli

Source: http://trastetes.blogspot.com/2016/02/solucion-al-error-e-then-
appstreamcli.html

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1579712

Title:
  Refresh hangs due to strdup on non-NULL terminated string

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
   * Fixing this bug resolves the issue for people who might experience it.
   * See https://github.com/ximion/appstream/issues/35 for details.

  [Test Case 1]

   * Run `sudo appstreamcli refresh --force`
   * The AppStream cache should be updated, no change in behavior should be 
seen.

  [Test Case 2]

   * In case you were experiencing the almost-infinite hang when running
  `sudo appstreamcli refresh --force`, this issue should be fixed with
  the SRU.

  [Regression Potential]

   * Very low, since this only fixes the decompression code. There
  should be no sideeffects of that (given that the patch itself doesn't
  break anything, which it shouldn't, since it has been tested upstream
  for a while)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
   * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a

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

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

[Desktop-packages] [Bug 1582433] Re: Dash does not handle .desktop files correctly if there are hyphens in the directory path

2016-05-19 Thread Andrea Azzarone

** No longer affects: unity (Ubuntu)

** Branch linked: lp:~azzar1/unity-lens-applications/lp-1582433

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-lens-applications in Ubuntu.
Matching subscriptions: dp-unity-lens-music
https://bugs.launchpad.net/bugs/1582433

Title:
  Dash does not handle .desktop files correctly if there are hyphens in
  the directory path

Status in unity-lens-applications package in Ubuntu:
  In Progress

Bug description:
  The Unity dash can fail to display the icon or title from a .desktop
  file correctly if it resides under a directory containing a hyphen
  character.

  As an example (on my 16.04 machine):

  $ cat << EOF > test.desktop
  [Desktop Entry]
  Name=Hyphen test
  Exec=/bin/true
  Type=Application
  Icon=/usr/share/icons/suru/apps/256/dash.png
  EOF

  $ chmod +x test.desktop
  $ mkdir ~/.local/share/applications/hyphen-test
  $ mv test.desktop ~/.local/share/applications/hyphen-test/

  Now, open the dash and search for "hyphen". On my machine, I see the
  correct icon but no title is displayed underneath.

  $ mv ~/.local/share/applications/hyphen-test
  ~/.local/share/applications/hyphen

  Searching for "hyphen" in the dash now shows an entry with the correct
  icon and title (but also still shows the defunct previous entry
  without title).

  The effect of the hyphenated path seems variable. Some apps show the
  wrong icon, some have a missing title, some have both errors.

  The problem only seems to be with hyphens in the directories. Hyphens
  in the file itself are fine. See the screenshot - Might and Magic 4&5
  has had a desktop file installed under a subdirectory with a hyphen,
  whereas Heroes of Might and Magic has a desktop file in the root
  directory but contains a hyphen in the filename. The latter is shown
  correctly, but the desktop files in the former directory are not shown
  properly.

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

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

[Desktop-packages] [Bug 1579712] Re: Refresh hangs due to strdup on non-NULL terminated string

2016-05-19 Thread Eduardo

Neither can I install any update, even after disabling third-party
repositories.

appstreamcli hangs refreshing with 100% cpu use

apt update hangs after 'Fetched XXX kb in Xs (XXX kb/s)'

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1579712

Title:
  Refresh hangs due to strdup on non-NULL terminated string

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
   * Fixing this bug resolves the issue for people who might experience it.
   * See https://github.com/ximion/appstream/issues/35 for details.

  [Test Case 1]

   * Run `sudo appstreamcli refresh --force`
   * The AppStream cache should be updated, no change in behavior should be 
seen.

  [Test Case 2]

   * In case you were experiencing the almost-infinite hang when running
  `sudo appstreamcli refresh --force`, this issue should be fixed with
  the SRU.

  [Regression Potential]

   * Very low, since this only fixes the decompression code. There
  should be no sideeffects of that (given that the patch itself doesn't
  break anything, which it shouldn't, since it has been tested upstream
  for a while)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
   * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a

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

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

[Desktop-packages] [Bug 1579712] Re: Refresh hangs due to strdup on non-NULL terminated string

2016-05-19 Thread strav

Peter, the package can be found at:
https://launchpad.net/ubuntu/+source/appstream/0.9.4-1ubuntu1 (as
previously posted) but I'm kinda at a loss here: dpkg -i launches
appstreamcli when setting up the package which results in me not being
able to install it so far.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1579712

Title:
  Refresh hangs due to strdup on non-NULL terminated string

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
   * Fixing this bug resolves the issue for people who might experience it.
   * See https://github.com/ximion/appstream/issues/35 for details.

  [Test Case 1]

   * Run `sudo appstreamcli refresh --force`
   * The AppStream cache should be updated, no change in behavior should be 
seen.

  [Test Case 2]

   * In case you were experiencing the almost-infinite hang when running
  `sudo appstreamcli refresh --force`, this issue should be fixed with
  the SRU.

  [Regression Potential]

   * Very low, since this only fixes the decompression code. There
  should be no sideeffects of that (given that the patch itself doesn't
  break anything, which it shouldn't, since it has been tested upstream
  for a while)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
   * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a

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

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

[Desktop-packages] [Bug 1583845] [NEW] Can't "apt-get update" - appstreamcli stuck at 100% Processor Utilization

Public bug reported:

I did a fresh install of Ubuntu 16.04 without being connected to the
internet because when connected to the internet the install would lock
up at the point that ubuntu was "Retrieving 56 of 56".

Installation (without internet) was successful, then I connected to the 
internet and tried to update:
sudo apt-get update

The update-process seemed to be stuck, so I discovered that the command
appstreamcli was at 100% processor utilization indefinitely.

When I kill that process the update fails. This is clearly a bug, but
hopefully someone can suggest a work-around until it is fixed.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: appstream 0.9.4-1
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Thu May 19 19:08:30 2016
InstallationDate: Installed on 2016-05-19 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcEnviron:
 LANGUAGE=en_US
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: appstream
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1583845

Title:
  Can't "apt-get update" - appstreamcli stuck at 100% Processor
  Utilization

Status in appstream package in Ubuntu:
  New

Bug description:
  I did a fresh install of Ubuntu 16.04 without being connected to the
  internet because when connected to the internet the install would lock
  up at the point that ubuntu was "Retrieving 56 of 56".

  Installation (without internet) was successful, then I connected to the 
internet and tried to update:
  sudo apt-get update

  The update-process seemed to be stuck, so I discovered that the
  command appstreamcli was at 100% processor utilization indefinitely.

  When I kill that process the update fails. This is clearly a bug, but
  hopefully someone can suggest a work-around until it is fixed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: appstream 0.9.4-1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu May 19 19:08:30 2016
  InstallationDate: Installed on 2016-05-19 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: appstream
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1573685] Re: Security fixes from 50.0.2661.75 and 50.0.2661.94

2016-05-19 Thread pcworld

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1573685

Title:
  Security fixes from 50.0.2661.75 and 50.0.2661.94

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  Security fixes from 50.0.2661.75 and 50.0.2661.94 (some of them were
  classified as "High" severity by the Chromium development team, i.e.
  "allow an attacker to execute code in the context of, or otherwise
  impersonate other origins") should be either backported to the
  respective Chromium versions in all current desktop-supported releases
  of Ubuntu, or the repositories should be updated to include the new
  version of Chromium.

  Information on the new releases can be found at:
  http://googlechromereleases.blogspot.de/2016/04/stable-channel-
  update_13.html http://googlechromereleases.blogspot.de/2016/04/stable-
  channel-update_28.html

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

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

[Desktop-packages] [Bug 1579712] Re: Refresh hangs due to strdup on non-NULL terminated string

@pgbennett

I'm not sure how to discover which particular repo is causing
appstreamcli to hang, so you could try disabling *all* your third party
repos then update. Or disable them one-by-one, but that could be
tedious.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1579712

Title:
  Refresh hangs due to strdup on non-NULL terminated string

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
   * Fixing this bug resolves the issue for people who might experience it.
   * See https://github.com/ximion/appstream/issues/35 for details.

  [Test Case 1]

   * Run `sudo appstreamcli refresh --force`
   * The AppStream cache should be updated, no change in behavior should be 
seen.

  [Test Case 2]

   * In case you were experiencing the almost-infinite hang when running
  `sudo appstreamcli refresh --force`, this issue should be fixed with
  the SRU.

  [Regression Potential]

   * Very low, since this only fixes the decompression code. There
  should be no sideeffects of that (given that the patch itself doesn't
  break anything, which it shouldn't, since it has been tested upstream
  for a while)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
   * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a

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

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

[Desktop-packages] [Bug 1579712] Re: Refresh hangs due to strdup on non-NULL terminated string

2016-05-19 Thread Jacob Taylor

I have appstream 0.9.4-1 installed and every time it is run
(automatically, not by me) it spikes cpu to 100%. I cannot even purge
and reinstall it, because it is run during the setup phase (to force a
new index) which pegs the cpu. Is 0.9.4-1 supposed to be ~= 0.9.6 of
upstream?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1579712

Title:
  Refresh hangs due to strdup on non-NULL terminated string

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
   * Fixing this bug resolves the issue for people who might experience it.
   * See https://github.com/ximion/appstream/issues/35 for details.

  [Test Case 1]

   * Run `sudo appstreamcli refresh --force`
   * The AppStream cache should be updated, no change in behavior should be 
seen.

  [Test Case 2]

   * In case you were experiencing the almost-infinite hang when running
  `sudo appstreamcli refresh --force`, this issue should be fixed with
  the SRU.

  [Regression Potential]

   * Very low, since this only fixes the decompression code. There
  should be no sideeffects of that (given that the patch itself doesn't
  break anything, which it shouldn't, since it has been tested upstream
  for a while)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
   * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a

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

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

[Desktop-packages] [Bug 1583783] Re: package firefox 46.0+build5-0ubuntu0.14.04.2 failed to install/upgrade: cannot copy extracted data for './usr/lib/firefox/libxul.so' to '/usr/lib/firefox/libxul.so

2016-05-19 Thread Ubuntu Foundations Team Bug Bot

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to install a particular package.  Please execute the following
command, as it will clear your package cache, in a terminal:

sudo apt-get clean

Then try performing the update again.  This will likely resolve your
issue, but the failure could be caused by filesystem or memory
corruption.  So please also run a fsck on your filesystem(s) and a
memory test.  Thanks in advance!

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

** Tags added: corrupted-package

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1583783

Title:
  package firefox 46.0+build5-0ubuntu0.14.04.2 failed to
  install/upgrade: cannot copy extracted data for
  './usr/lib/firefox/libxul.so' to '/usr/lib/firefox/libxul.so.dpkg-
  new': unexpected end of file or stream

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  The system actualisation did not go through. Maybe the file ist
  corrupt.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: firefox 46.0+build5-0ubuntu0.14.04.2
  ProcVersionSignature: Ubuntu 4.2.0-36.42~14.04.1-generic 4.2.8-ckt8
  Uname: Linux 4.2.0-36-generic i686
  AddonCompatCheckDisabled: False
  ApportVersion: 2.14.1-0ubuntu3.20
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thomas 1651 F pulseaudio
   /dev/snd/seq:timidity   2058 F timidity
  BuildID: 20160425115337
  CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 'iw'
  Channel: Unavailable
  Date: Thu May 19 22:18:39 2016
  DuplicateSignature: package:firefox:46.0+build5-0ubuntu0.14.04.2:cannot copy 
extracted data for './usr/lib/firefox/libxul.so' to 
'/usr/lib/firefox/libxul.so.dpkg-new': unexpected end of file or stream
  ErrorMessage: cannot copy extracted data for './usr/lib/firefox/libxul.so' to 
'/usr/lib/firefox/libxul.so.dpkg-new': unexpected end of file or stream
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-02-21 (88 days ago)
  InstallationMedia: Lubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  IpRoute:
   default via 192.168.178.1 dev eth0  proto static 
   192.168.178.0/24 dev eth0  proto kernel  scope link  src 192.168.178.20  
metric 1
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NoProfiles: True
  PciNetwork:
   
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.6
   apt  1.0.1ubuntu2.14
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Title: package firefox 46.0+build5-0ubuntu0.14.04.2 failed to 
install/upgrade: cannot copy extracted data for './usr/lib/firefox/libxul.so' 
to '/usr/lib/firefox/libxul.so.dpkg-new': unexpected end of file or stream
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/21/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: N68-S
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd09/21/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-S:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Desktop-packages] [Bug 1579712] Re: Refresh hangs due to strdup on non-NULL terminated string

2016-05-19 Thread Grant

Like Peter in #11, I cannot enable proposed because appstreamcli is
hanging on every single run. Any invocation of appstreamcli or apt
update gets stuck.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1579712

Title:
  Refresh hangs due to strdup on non-NULL terminated string

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
   * Fixing this bug resolves the issue for people who might experience it.
   * See https://github.com/ximion/appstream/issues/35 for details.

  [Test Case 1]

   * Run `sudo appstreamcli refresh --force`
   * The AppStream cache should be updated, no change in behavior should be 
seen.

  [Test Case 2]

   * In case you were experiencing the almost-infinite hang when running
  `sudo appstreamcli refresh --force`, this issue should be fixed with
  the SRU.

  [Regression Potential]

   * Very low, since this only fixes the decompression code. There
  should be no sideeffects of that (given that the patch itself doesn't
  break anything, which it shouldn't, since it has been tested upstream
  for a while)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
   * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a

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

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

[Desktop-packages] [Bug 1579712] Re: Refresh hangs due to strdup on non-NULL terminated string

2016-05-19 Thread Peter Bennett

Can somebody post a URL where I can download the proposed package
directly as I cannot install it using apt-get, which hangs because of
this bug. I am using amd64 xenial.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1579712

Title:
  Refresh hangs due to strdup on non-NULL terminated string

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * The cache refresh is blocked on a strdup on a non-NULL-terminated string 
in some very rare occasions (very rare because this bug is present for almost 
3y without a single report).
   * Fixing this bug resolves the issue for people who might experience it.
   * See https://github.com/ximion/appstream/issues/35 for details.

  [Test Case 1]

   * Run `sudo appstreamcli refresh --force`
   * The AppStream cache should be updated, no change in behavior should be 
seen.

  [Test Case 2]

   * In case you were experiencing the almost-infinite hang when running
  `sudo appstreamcli refresh --force`, this issue should be fixed with
  the SRU.

  [Regression Potential]

   * Very low, since this only fixes the decompression code. There
  should be no sideeffects of that (given that the patch itself doesn't
  break anything, which it shouldn't, since it has been tested upstream
  for a while)

  [Other Info]

   * This fix has been applied upstream: 
https://github.com/ximion/appstream/commit/f33c520c37e2ba51d92402220250b8d501a2bf43
   * A smaller version of the patch (one-liner) is available, at the expense of 
not having reduced memory usage: 
https://github.com/ximion/appstream/commit/378941787d3584b3eb31a6ebe40e0aacc10e180a

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

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

[Desktop-packages] [Bug 1565265] Re: Wifi disabled after resume from suspend on Dell Latitude E7450

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

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  Wifi disabled after resume from suspend on Dell Latitude E7450

Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager package in Fedora:
  New

Bug description:
  Steps to reproduce:
  1) Connect to network via wifi
  2) Suspend your notebook
  3) Resume from suspend - wifi will be disabled and you have to turn wifi 
manually

  HW: Dell Latitude E7450

  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  network-manager:
Instalovaná verze: 1.0.4-0ubuntu10
Kandidát:  1.0.4-0ubuntu10
Tabulka verzí:
   *** 1.0.4-0ubuntu10 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  What happened: wifi is turned off after resume from suspend.
  Expected: wifi should be on after resume from suspend.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.0.4-0ubuntu10
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.370
  CurrentDesktop: Unity
  Date: Sat Apr  2 12:05:05 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160401)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL  AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH 
   Petrikovi   fc08f65c-260b-43b9-ae5d-df784e87ffd2  802-11-wireless  
1459598679  So 2. duben 2016, 12:04:39 UTC  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  no  --  -- -- 
 
   Wired connection 1  62835f6a-985f-4f05-afa3-e0fe1f31de93  802-3-ethernet   
1459598635  So 2. duben 2016, 12:03:55 UTC  yes  0 
no/org/freedesktop/NetworkManager/Settings/0  no  --  -- --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH 
   eno1ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
   wlp2s0  wifi  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
   lo  loopback  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/1565265/+subscriptions

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

[Desktop-packages] [Bug 1583830] Re: appstreamcli process consuming 100% CPU, even after reboot