date:20161024

Hello Bryan,

After installing the -proposed version the error presented on this bug
is not reproducible anymore and the guest starts correctly.

You can follow the reproduction steps that I added to the bug's
description.

Without -proposed:

$ sudo virsh destroy guest1
Domain guest1 destroyed

$ sudo virsh start guest1

error: Failed to start domain guest1
error: internal error: missing IFLA_VF_INFO in netlink response

With proposed:

root@bronzor:/home/ubuntu# start libvirt-bin
libvirt-bin start/running, process 31492

root@bronzor:/home/ubuntu# virsh start guest1
Domain guest1 started


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

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

Title:
   libnl should be updated to support up to 63 VFs per single PF

Status in libnl3 package in Ubuntu:
  Fix Released
Status in libnl3 source package in Precise:
  New
Status in libnl3 source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  libnl can only enable up to 30 VFs even if the PF supports up to 63
  VFs in an Openstack SRIOV configuration.

  As already documented in https://bugs.launchpad.net/mos/+bug/1501738
  there is a bug in the default libnl library release installed on
  Ubuntu 14.04.4.

  When trying to enable a guest with more than 30 VFs attached, the
  following error is returned:

  error: Failed to start domain guest1
  error: internal error: missing IFLA_VF_INFO in netlink response

  [Test Case]

   1) Edit /etc/default/grub.

  GRUB_CMDLINE_LINUX="intel_iommu=on ixgbe.max_vfs=63"

   2) Update grub and reboot the machine.

  $ sudo update-grub

   3) Check that the virtual functions are available.

  $ sudo lspci|grep -i eth | grep -i virtual | wc -l
  126

   4) Create a KVM guest.

  $ sudo uvt-kvm create guest1 release=trusty

   5) List the VF devices.

  $ sudo lspci|grep -i eth | grep -i virtual | awk '{print $1}' | sed
  's/\:/\_/g' | sed 's/\./\_/g' > devices.txt

   6) Get the libvirt node device.

  $ sudo for device in $(cat ./devices.txt); do virsh nodedev-list |
  grep $device; done > pci_devices.txt

   7) Generate the XML config for each device.

  $ sudo mkdir devices && for d in $(cat pci_devices.txt); do virsh
  nodedev-dumpxml $d > devices/$d.xml; done

   8) Save and Run the following script.
  (http://pastebin.ubuntu.com/23374186/)

  $ sudo python generate-interfaces.py |grep address | wc -l

   9) Finally attach the devices to the guest.

  $ sudo for i in $(seq 0 63); do virsh attach-device guest1 
./interfaces/$i.xml --config; done
  Device attached successfully
  [...]

  Device attached successfully
  Device attached successfully

   10) Then destroy/start the guest again, at this point the error is
  reproduced.

  $ sudo virsh destroy guest1
  Domain guest1 destroyed

  $ sudo virsh start guest1

  error: Failed to start domain guest1
  error: internal error: missing IFLA_VF_INFO in netlink response

  [Regression Potential]

   * None identified.

  [Other Info]

   * Redhat Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1040626

   * A workaround is to install a newer library release.

  $ wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-3-200_3.2.24-2_amd64.deb
  $ wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-genl-3-200_3.2.24-2_amd64.deb
  $ wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-route-3-200_3.2.24-2_amd64.deb
  $ dpkg -i libnl-3-200_3.2.24-2_amd64.deb
  $ dpkg -i libnl-genl-3-200_3.2.24-2_amd64.deb
  $ dpkg -i libnl-route-3-200_3.2.24-2_amd64.deb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1567578/+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 1636355] [NEW] In lirc 0.9.4, lircd-uinput.service fails to start because the lircd-uinput executable is not installed

2016-10-24 Thread Michael Marley

Public bug reported:

The title says it all.

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

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

Title:
  In lirc 0.9.4, lircd-uinput.service fails to start because the lircd-
  uinput executable is not installed

Status in lirc package in Ubuntu:
  New

Bug description:
  The title says it all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1636355/+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 1636353] [NEW] In lirc 0.9.4, irexec.service fails to start because the irexec executable is in /usr/bin/, not /usr/sbin/

2016-10-24 Thread Michael Marley

Public bug reported:

Either the file needs to be moved to /usr/sbin/ or the
/lib/systemd/system/irexec.service needs to be updated to point to
/usr/bin/irexec instead.

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

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

Title:
  In lirc 0.9.4, irexec.service fails to start because the irexec
  executable is in /usr/bin/, not /usr/sbin/

Status in lirc package in Ubuntu:
  New

Bug description:
  Either the file needs to be moved to /usr/sbin/ or the
  /lib/systemd/system/irexec.service needs to be updated to point to
  /usr/bin/irexec instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1636353/+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 1626135] Re: not create when create schedule to use google account

This sounds like a known problem with Google authentication. Here is the
GNOME bug:

https://bugzilla.gnome.org/show_bug.cgi?id=771547

As a workaround, you can try restarting your computer.

** Changed in: gnome-calendar (Ubuntu)
   Status: Incomplete => Triaged

** Bug watch added: GNOME Bug Tracker #771547
   https://bugzilla.gnome.org/show_bug.cgi?id=771547

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

Title:
  not create when create schedule  to use google account

Status in gnome-calendar package in Ubuntu:
  Triaged

Bug description:
  not create when create schedule  in calendar with google account, but
  can create schedule when create by calendar without google account
  (for example default calendar "個人" displayed in Japanese )

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1626135/+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 1633053] Re: gnome-calendar 3.20.4 inoperable after update on 13 October 2016

Taking a blind guess because there's so little information here. Maybe
this is related to the recent troubles with Google authentication.

https://bugzilla.gnome.org/show_bug.cgi?id=771547

Are you using Unity or GNOME or some other desktop?
Was your calendar in sync with Google Calendar before?

As a workaround, please try restarting your computer.

** Bug watch added: GNOME Bug Tracker #771547
   https://bugzilla.gnome.org/show_bug.cgi?id=771547

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

Title:
  gnome-calendar 3.20.4 inoperable after update on 13 October 2016

Status in gnome-calendar package in Ubuntu:
  Incomplete

Bug description:
  Calendar 3.20.4 has no data showing.  It is a blank calendar.  All my
  data seems to be erased.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1633053/+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 1636348] [NEW] package liblirc-client0 (not installed) failed to install/upgrade: tentando sobrescrever '/usr/lib/x86_64-linux-gnu/liblirc_client.so.0', que também está no paco

2016-10-24 Thread Weiller

Public bug reported:

weiller@weiller-MS-7641:~$ lsb_release -rd
Description:Ubuntu Zesty Zapus (development branch)
Release:17.04

weiller@weiller-MS-7641:~$ apt-cache policy liblirc-client0 
liblirc-client0:
  Instalado: (nenhum)
  Candidato: 0.9.4c-1
  Tabela de versão:
 0.9.4c-1 500
500 http://cz.archive.ubuntu.com/ubuntu zesty-proposed/main amd64 
Packages
500 http://ubuntu.c3sl.ufpr.br/ubuntu zesty-proposed/main amd64 Packages

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: liblirc-client0 (not installed)
ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
Uname: Linux 4.8.0-27-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Mon Oct 24 23:49:56 2016
ErrorMessage: tentando sobrescrever 
'/usr/lib/x86_64-linux-gnu/liblirc_client.so.0', que também está no pacote 
liblircclient0:amd64 0.9.0-0ubuntu6
InstallationDate: Installed on 2016-02-11 (256 days ago)
InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.1
SourcePackage: lirc
Title: package liblirc-client0 (not installed) failed to install/upgrade: 
tentando sobrescrever '/usr/lib/x86_64-linux-gnu/liblirc_client.so.0', que 
também está no pacote liblircclient0:amd64 0.9.0-0ubuntu6
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package zesty

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

Title:
  package liblirc-client0 (not installed) failed to install/upgrade:
  tentando sobrescrever '/usr/lib/x86_64-linux-gnu/liblirc_client.so.0',
  que também está no pacote liblircclient0:amd64 0.9.0-0ubuntu6

Status in lirc package in Ubuntu:
  New

Bug description:
  weiller@weiller-MS-7641:~$ lsb_release -rd
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04

  weiller@weiller-MS-7641:~$ apt-cache policy liblirc-client0 
  liblirc-client0:
Instalado: (nenhum)
Candidato: 0.9.4c-1
Tabela de versão:
   0.9.4c-1 500
  500 http://cz.archive.ubuntu.com/ubuntu zesty-proposed/main amd64 
Packages
  500 http://ubuntu.c3sl.ufpr.br/ubuntu zesty-proposed/main amd64 
Packages

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: liblirc-client0 (not installed)
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Mon Oct 24 23:49:56 2016
  ErrorMessage: tentando sobrescrever 
'/usr/lib/x86_64-linux-gnu/liblirc_client.so.0', que também está no pacote 
liblircclient0:amd64 0.9.0-0ubuntu6
  InstallationDate: Installed on 2016-02-11 (256 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: lirc
  Title: package liblirc-client0 (not installed) failed to install/upgrade: 
tentando sobrescrever '/usr/lib/x86_64-linux-gnu/liblirc_client.so.0', que 
também está no pacote liblircclient0:amd64 0.9.0-0ubuntu6
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1636348/+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 1574810] Re: Highlighting and output showing issues on 16.04

** Changed in: gnome-terminal
   Status: Incomplete => Invalid

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

Title:
  Highlighting and output showing issues on 16.04

Status in GNOME Terminal:
  Invalid
Status in Ubuntu GNOME:
  New
Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  I have noticed that on Ubuntu GNOME 16.04 with GNOME 3.20 that often
  when I execute a command although the cursor goes to the right place
  and still blinks as it should the output is not shown until I press
  Enter once more:

  gnome-terminal_16-04_Execute_Invisible_Output_Issue.png

  gnome-terminal_16-04_Execute_Shown_Output_Issue.png

  I have also noticed that often when clicking and dragging to select
  text though when I copy and paste it somewhere else I can see that all
  the text was really selected, it doesn't show all the text to be
  selected (it is normally much more extreme with many more lines
  missing the highlighting than shown here though):

  gnome-terminal_16-04_Highlighting_Issue1.png

  I have also noticed that if I select text but then move my mouse the
  other way some of the text doesn't get unselected as it should:

  gnome-terminal_16-04_Highlighting_Issue2.png

  Don't let the fact that the screenshots are from my Ubuntu (Unity)
  16.04 VM confuse you though, the same happens on my GNOME one, I just
  had my Unity one open at the time when I wanted to take the
  sreenshots.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-terminal/+bug/1574810/+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 1590204] Re: [SRU] Update to bug fix release 3.8.4 in Trusty

** Changed in: gnome-contacts (Ubuntu)
   Importance: Undecided => Low

** Changed in: gnome-contacts (Ubuntu)
   Status: New => Fix Released

** Also affects: gnome-contacts (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: gnome-contacts (Ubuntu Trusty)
   Importance: Undecided => Low

** Changed in: gnome-contacts (Ubuntu Trusty)
   Status: New => Triaged

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

** Changed in: gnome-contacts (Ubuntu Trusty)
   Importance: Low => Medium

** Changed in: gnome-contacts (Ubuntu)
   Importance: Low => Medium

** Changed in: ubuntu-gnome
   Importance: Undecided => Medium

** Changed in: ubuntu-gnome
   Status: New => Triaged

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

Title:
  [SRU] Update to bug fix release 3.8.4 in Trusty

Status in Ubuntu GNOME:
  Triaged
Status in gnome-contacts package in Ubuntu:
  Fix Released
Status in gnome-contacts source package in Trusty:
  Triaged

Bug description:
  Impact
  ---
  Missing text input box for Address field (LP: #1249947)

  https://git.gnome.org/browse/gnome-contacts/tree/NEWS?h=gnome-3-8
  * Fixed New Contact dialog address field issue

  Test case
  --
  1. Install gnome-contact from trusty-proposed
  2. Add a New Contact
  3. See the text input box for the Address field

  Regression potential
  
  Low, as the fix is small

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1590204/+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 1631398] Re: package account-plugin-google 0.13+16.10.20160831-0ubuntu1 failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf

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

** Changed in: account-plugins (Ubuntu)
   Status: New => Confirmed

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

Title:
  package account-plugin-google 0.13+16.10.20160831-0ubuntu1 failed to
  install/upgrade: trying to overwrite '/etc/signon-ui/webkit-
  options.d/accounts.google.com.conf', which is also in package
  kaccounts-providers 4:16.04.3-0ubuntu1

Status in account-plugins package in Ubuntu:
  Confirmed

Bug description:
  hi my frends

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: account-plugin-google 0.13+16.10.20160831-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
  Uname: Linux 4.8.0-19-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Fri Oct  7 07:55:35 2016
  DuplicateSignature:
   package:account-plugin-google:0.13+16.10.20160831-0ubuntu1
   Unpacking account-plugin-google (0.13+16.10.20160929.1-0ubuntu1) over 
(0.13+16.10.20160831-0ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-V6mfaf/03-account-plugin-google_0.13+16.10.20160929.1-0ubuntu1_all.deb
 (--unpack):
trying to overwrite 
'/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in 
package kaccounts-providers 4:16.04.3-0ubuntu1
  ErrorMessage: trying to overwrite 
'/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in 
package kaccounts-providers 4:16.04.3-0ubuntu1
  InstallationDate: Installed on 2016-02-11 (239 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: account-plugins
  Title: package account-plugin-google 0.13+16.10.20160831-0ubuntu1 failed to 
install/upgrade: trying to overwrite 
'/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in 
package kaccounts-providers 4:16.04.3-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.signon-ui.webkit-options.d.accounts.google.com.conf: 
2016-07-02T19:13:58

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1631398/+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 1632023] Re: Update epiphany to 3.22.1

** Also affects: epiphany-browser (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Changed in: epiphany-browser (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: epiphany-browser (Ubuntu Yakkety)
   Importance: Undecided => Low

** Changed in: epiphany-browser (Ubuntu Yakkety)
   Status: New => Confirmed

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

Title:
  Update epiphany to 3.22.1

Status in epiphany-browser package in Ubuntu:
  Fix Released
Status in epiphany-browser source package in Yakkety:
  Confirmed

Bug description:
  Impact
  ==

  I think I'll wait for the new version of webkit2gtk for this so that
  we can build against the new version for "free".

  https://git.gnome.org/browse/epiphany/log/?h=gnome-3-22
  https://git.gnome.org/browse/epiphany/tree/NEWS?h=gnome-3-22

  Test Case
  =

  Regression Potential
  

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: epiphany-browser 3.22.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 10 12:25:08 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-11 (59 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160811)
  SourcePackage: epiphany-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/1632023/+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 1615408] Re: Theming issues with yakkety gnome-calculator in Unity

Hmm, I don't have the extra Mode menu when I run gnome-calculator from
the Unity Dash but I do see it when I run gnome-calculator from a
terminal.

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

Title:
  Theming issues with yakkety gnome-calculator in Unity

Status in gnome-calculator package in Ubuntu:
  Confirmed

Bug description:
  There are some UI problems with yakkety's gnome-calculator. I'm
  attaching a screenshot taken with yesterday's daily live Ubuntu image.

  1. The title bar says 'gnome-calculator' but it should say Calculator
  2. The Mode menu has an ugly light-colored border around it instead of being 
integrated into either the title bar (like gnome-calculator 3.18.3 in Ubuntu 
16.04 LTS) or in to Unity's menu bar.

  These issues affect both gnome-calculator 1:3.20.1-0ubuntu1 and
  1:3.21.90-0ubuntu1 but do not affect 1:3.18.3-0ubuntu1 on yakkety.

  I think this was caused by the refresh of
  debian/patches/git_no_headerbars_in_unity.patch in the 3.20 update.

  Screenshots attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1615408/+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 1633408] Re: 3.22.0 wont allow cut&paste in history pane

** Changed in: gnome-calculator (Ubuntu)
   Importance: Undecided => Low

** Changed in: gnome-calculator (Ubuntu)
   Status: Confirmed => Triaged

** Tags added: regression-release

** Also affects: gnome-calculator via
   https://bugzilla.gnome.org/show_bug.cgi?id=773445
   Importance: Unknown
   Status: Unknown

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

Title:
  3.22.0 wont allow cut&paste in history pane

Status in GNOME Calculator:
  Unknown
Status in gnome-calculator package in Ubuntu:
  Triaged

Bug description:
  The calculator's history, in 3.22.0  is now non-selected-able, in 3.18.x this 
use to be possible was the change  intentional?
  If not can the change be reverted.

  
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-03-01 (227 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: gnome-calculator 1:3.22.0-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Tags:  yakkety
  Uname: Linux 4.8.0-22-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev pulse pulse-access sambashare 
sudo vboxusers video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-calculator/+bug/1633408/+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 1631191] Re: Display backlight won't turn on after screen timeout

2016-10-24 Thread James Uanhoro

Same issue here with Oryx Pro 2 (oryp2) i7-6700HQ with 1070.

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

Title:
  Display backlight won't turn on after screen timeout

Status in nvidia-graphics-drivers-367 package in Ubuntu:
  Confirmed

Bug description:
  Using nVidia driver 367.44 on Skylake Intel Processors, with 1000
  series graphics, the backlight won't turn on after turned off by gnome
  session idle delay (org.gnome.desktop.session idle-delay). or by `xset
  dpms force off`

  Resume from suspend is unaffected.

  This is on a clean install of 16.10 with the 367.44 nVidia driver.
  This is a regression from the 367.35 driver.  367.48 and 370.28 also
  exhibit this behavior.

  This is confirmed on the following hardware:

  Oryx Pro 2 (oryp2) i7-6700HQ with 1070
  Serval 10 (serw10) i7-6700 with 1060
  Bonobo 11 (bonw11) i7-6700K with dual 1070

  Steps to reproduce:

  1. Install a fresh image of Yakkety and 367.44 from the graphics driver 
team's PPA.
  2. Log in to Unity shell
  3. Lock screen and wait for dimming.
  4. Move the mouse to 'resume'
  5. The screen will turn on, but the backlight is still off

  The current workaround:

  1. Hit tty1 (Ctrl+Alt+F1)
  2. Hit tty7 (Ctrl+Alt+F7)

  This will bring Unity back to life.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nvidia-367 367.44-0ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
  Uname: Linux 4.8.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Oct  6 16:17:11 2016
  SourcePackage: nvidia-graphics-drivers-367
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1631191/+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 1636331] [NEW] /usr/lib/gvfs/gvfsd-gphoto2:* Error in `/usr/lib/gvfs/gvfsd-gphoto2': double free or corruption (out): ADDR *

2016-10-24 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gvfs.  This problem was most recently seen with package version 
1.28.2-1ubuntu1~16.04.1, the problem page at 
https://errors.ubuntu.com/problem/fd60f29c3808ae046116830fc049fe9de57aab67 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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


** Tags: kylin-15.04 raring saucy utopic vivid wily xenial

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

Title:
  /usr/lib/gvfs/gvfsd-gphoto2:*** Error in `/usr/lib/gvfs/gvfsd-
  gphoto2': double free or corruption (out): ADDR ***

Status in gvfs package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gvfs.  This problem was most recently seen with package version 
1.28.2-1ubuntu1~16.04.1, the problem page at 
https://errors.ubuntu.com/problem/fd60f29c3808ae046116830fc049fe9de57aab67 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1636331/+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 1636320] Re: package liblirc-client0 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/liblirc_client.so.0', which is also in package li

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

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

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

Title:
  package liblirc-client0 (not installed) failed to install/upgrade:
  trying to overwrite '/usr/lib/x86_64-linux-gnu/liblirc_client.so.0',
  which is also in package liblircclient0:amd64 0.9.0-0ubuntu6

Status in lirc package in Ubuntu:
  Confirmed

Bug description:
  Selecting previously unselected package liblirc-client0:amd64.
  Preparing to unpack .../44-liblirc-client0_0.9.4c-1_amd64.deb ...
  Unpacking liblirc-client0:amd64 (0.9.4c-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-LJoo1m/44-liblirc-client0_0.9.4c-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/liblirc_client.so.0', which 
is also in package liblircclient0:amd64 0.9.0-0ubuntu6
  Preparing to unpack .../45-liblircclient0_0.9.4c-1_amd64.deb ...
  Unpacking liblircclient0 (0.9.4c-1) over (0.9.0-0ubuntu6) ...

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: liblirc-client0 (not installed)
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Mon Oct 24 18:29:50 2016
  DuplicateSignature:
   package:liblirc-client0:(not installed)
   Unpacking liblirc-client0:amd64 (0.9.4c-1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-LJoo1m/44-liblirc-client0_0.9.4c-1_amd64.deb (--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/liblirc_client.so.0', which 
is also in package liblircclient0:amd64 0.9.0-0ubuntu6
  ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/liblirc_client.so.0', which is also in package 
liblircclient0:amd64 0.9.0-0ubuntu6
  InstallationDate: Installed on 2016-02-19 (248 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: lirc
  Title: package liblirc-client0 (not installed) failed to install/upgrade: 
trying to overwrite '/usr/lib/x86_64-linux-gnu/liblirc_client.so.0', which is 
also in package liblircclient0:amd64 0.9.0-0ubuntu6
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1636320/+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 1633408] Re: 3.22.0 wont allow cut&paste in history pane

2016-10-24 Thread bojam

https://bugzilla.gnome.org/show_bug.cgi?id=773445

** Bug watch added: GNOME Bug Tracker #773445
   https://bugzilla.gnome.org/show_bug.cgi?id=773445

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

Title:
  3.22.0 wont allow cut&paste in history pane

Status in gnome-calculator package in Ubuntu:
  Confirmed

Bug description:
  The calculator's history, in 3.22.0  is now non-selected-able, in 3.18.x this 
use to be possible was the change  intentional?
  If not can the change be reverted.

  
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-03-01 (227 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: gnome-calculator 1:3.22.0-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Tags:  yakkety
  Uname: Linux 4.8.0-22-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev pulse pulse-access sambashare 
sudo vboxusers video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1633408/+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 1635967] Re: Inkscape does not start in ubuntu 16.10

2016-10-24 Thread Sadi Yumuşak

It does persist after restarting (or doing "sudo ldconfig" in that terminal)
And creating symlinks named "/usr/lib/libgdkmm-2.4.so.1" and 
"/usr/lib/libgtkmm-2.4.so.1" to the existing 
"/usr/lib/x86_64-linux-gnu/libgdkmm-3.0.so.1" and 
"/usr/lib/x86_64-linux-gnu/libgtkmm-3.0.so.1" implies that there are actually 
underlying dependency problems which somehow didn't prevent my installation 
using terminal command "sudo apt-get inkscape -y"

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

Title:
  Inkscape does not start in ubuntu 16.10

Status in Inkscape:
  Incomplete
Status in inkscape package in Ubuntu:
  New

Bug description:
  Just upgraded to Ubuntu 16.10 with inkscape 0.91-11 installed from
  official repositories.

  Unfortunately Inkscape fails to start - with the following error
  message in Terminal:

  error while loading shared libraries: libgtkmm-2.4.so.1: cannot open
  shared object file: No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/1635967/+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 1636320] [NEW] package liblirc-client0 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/liblirc_client.so.0', which is also in package

2016-10-24 Thread Anders Kaseorg

Public bug reported:

Selecting previously unselected package liblirc-client0:amd64.
Preparing to unpack .../44-liblirc-client0_0.9.4c-1_amd64.deb ...
Unpacking liblirc-client0:amd64 (0.9.4c-1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-LJoo1m/44-liblirc-client0_0.9.4c-1_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/liblirc_client.so.0', which is 
also in package liblircclient0:amd64 0.9.0-0ubuntu6
Preparing to unpack .../45-liblircclient0_0.9.4c-1_amd64.deb ...
Unpacking liblircclient0 (0.9.4c-1) over (0.9.0-0ubuntu6) ...

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: liblirc-client0 (not installed)
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
NonfreeKernelModules: openafs
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Mon Oct 24 18:29:50 2016
DuplicateSignature:
 package:liblirc-client0:(not installed)
 Unpacking liblirc-client0:amd64 (0.9.4c-1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-LJoo1m/44-liblirc-client0_0.9.4c-1_amd64.deb (--unpack):
  trying to overwrite '/usr/lib/x86_64-linux-gnu/liblirc_client.so.0', which is 
also in package liblircclient0:amd64 0.9.0-0ubuntu6
ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/liblirc_client.so.0', which is also in package 
liblircclient0:amd64 0.9.0-0ubuntu6
InstallationDate: Installed on 2016-02-19 (248 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.1
SourcePackage: lirc
Title: package liblirc-client0 (not installed) failed to install/upgrade: 
trying to overwrite '/usr/lib/x86_64-linux-gnu/liblirc_client.so.0', which is 
also in package liblircclient0:amd64 0.9.0-0ubuntu6
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package need-duplicate-check package-conflict zesty

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

Title:
  package liblirc-client0 (not installed) failed to install/upgrade:
  trying to overwrite '/usr/lib/x86_64-linux-gnu/liblirc_client.so.0',
  which is also in package liblircclient0:amd64 0.9.0-0ubuntu6

Status in lirc package in Ubuntu:
  New

Bug description:
  Selecting previously unselected package liblirc-client0:amd64.
  Preparing to unpack .../44-liblirc-client0_0.9.4c-1_amd64.deb ...
  Unpacking liblirc-client0:amd64 (0.9.4c-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-LJoo1m/44-liblirc-client0_0.9.4c-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/liblirc_client.so.0', which 
is also in package liblircclient0:amd64 0.9.0-0ubuntu6
  Preparing to unpack .../45-liblircclient0_0.9.4c-1_amd64.deb ...
  Unpacking liblircclient0 (0.9.4c-1) over (0.9.0-0ubuntu6) ...

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: liblirc-client0 (not installed)
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Mon Oct 24 18:29:50 2016
  DuplicateSignature:
   package:liblirc-client0:(not installed)
   Unpacking liblirc-client0:amd64 (0.9.4c-1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-LJoo1m/44-liblirc-client0_0.9.4c-1_amd64.deb (--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/liblirc_client.so.0', which 
is also in package liblircclient0:amd64 0.9.0-0ubuntu6
  ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/liblirc_client.so.0', which is also in package 
liblircclient0:amd64 0.9.0-0ubuntu6
  InstallationDate: Installed on 2016-02-19 (248 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: lirc
  Title: package liblirc-client0 (not installed) failed to install/upgrade: 
trying to overwrite '/usr/lib/x86_64-linux-gnu/liblirc_client.so.0', which is 
also in package liblircclient0:amd64 0.9.0-0ubuntu6
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1636320/+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 1567578] Re: libnl should be updated to support up to 63 VFs per single PF

2016-10-24 Thread Mathew Hodson

** Description changed:

- [Description]
+ [Impact]
  
- Ubuntu 14.04.4 and SRIOV settings.
+ libnl can only enable up to 30 VFs even if the PF supports up to 63 VFs
+ in an Openstack SRIOV configuration.
  
  As already documented in https://bugs.launchpad.net/mos/+bug/1501738
  there is a bug in the default libnl library release installed on Ubuntu
- 14.04.4
+ 14.04.4.
  
  When trying to enable a guest with more than 30 VFs attached, the
  following error is returned:
  
  error: Failed to start domain guest1
  error: internal error: missing IFLA_VF_INFO in netlink response
  
- [Impact]
- 
- The library release is the 3.2.21-1 the bug is impacting on the maximum
- VFs number that can be enabled (up to 30) even if the PF supports up to
- 63 VFs in an Openstack SRIOV configuration
- 
  [Test Case]
  
- The sequence to reproduce this bug is:
- 
- 1) Edit /etc/default/grub
+  1) Edit /etc/default/grub.
  
  GRUB_CMDLINE_LINUX="intel_iommu=on ixgbe.max_vfs=63"
  
- 2) $ sudo update-grub
+  2) Update grub and reboot the machine.
  
- ### Reboot the machine.
+ $ sudo update-grub
  
- 3) Check that the virtual functions are available:
+  3) Check that the virtual functions are available.
  
  $ sudo lspci|grep -i eth | grep -i virtual | wc -l
  126
  
- 4) Create a KVM guest
+  4) Create a KVM guest.
  
  $ sudo uvt-kvm create guest1 release=trusty
  
- 5) List the VF devices :
+  5) List the VF devices.
  
  $ sudo lspci|grep -i eth | grep -i virtual | awk '{print $1}' | sed
  's/\:/\_/g' | sed 's/\./\_/g' > devices.txt
  
- 6) Get the libvirt node device:
+  6) Get the libvirt node device.
  
  $ sudo for device in $(cat ./devices.txt); do virsh nodedev-list | grep
  $device; done > pci_devices.txt
  
- 7) Generate the XML config for each device:
+  7) Generate the XML config for each device.
  
  $ sudo mkdir devices && for d in $(cat pci_devices.txt); do virsh
  nodedev-dumpxml $d > devices/$d.xml; done
  
- 8) Save and Run the following script
+  8) Save and Run the following script.
  (http://pastebin.ubuntu.com/23374186/)
  
  $ sudo python generate-interfaces.py |grep address | wc -l
  
- 9) Finally attach the devices to the guest.
+  9) Finally attach the devices to the guest.
  
  $ sudo for i in $(seq 0 63); do virsh attach-device guest1 
./interfaces/$i.xml --config; done
  Device attached successfully
  [...]
  
  Device attached successfully
  Device attached successfully
  
- 10) Then destroy/start the guest again, at this point the error is
+  10) Then destroy/start the guest again, at this point the error is
  reproduced.
  
  $ sudo virsh destroy guest1
  Domain guest1 destroyed
  
  $ sudo virsh start guest1
  
  error: Failed to start domain guest1
  error: internal error: missing IFLA_VF_INFO in netlink response
  
-  * detailed instructions how to reproduce the bug
- 
-  * these should allow someone who is not familiar with the affected
-package to reproduce the bug and verify that the updated package fixes
-the problem.
- 
  [Regression Potential]
  
-  ** None identified.
+  * None identified.
  
  [Other Info]
  
- - Redhat Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1040626
+  * Redhat Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1040626
  
- [Workaround]
+  * A workaround is to install a newer library release.
  
- The workaround is to install a newer library release, the 3.2.24-2:
- 
- wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-3-200_3.2.24-2_amd64.deb
- wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-genl-3-200_3.2.24-2_amd64.deb
- wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-route-3-200_3.2.24-2_amd64.deb
- dpkg -i libnl-3-200_3.2.24-2_amd64.deb
- dpkg -i libnl-genl-3-200_3.2.24-2_amd64.deb
- dpkg -i libnl-route-3-200_3.2.24-2_amd64.deb
+ $ wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-3-200_3.2.24-2_amd64.deb
+ $ wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-genl-3-200_3.2.24-2_amd64.deb
+ $ wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-route-3-200_3.2.24-2_amd64.deb
+ $ dpkg -i libnl-3-200_3.2.24-2_amd64.deb
+ $ dpkg -i libnl-genl-3-200_3.2.24-2_amd64.deb
+ $ dpkg -i libnl-route-3-200_3.2.24-2_amd64.deb

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

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

Title:
   libnl should be updated to support up to 63 VFs per single PF

Status in libnl3 package in Ubuntu:
  Fix Released
Status in libnl3 source package in Precise:
  New
Status in libnl3 source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  libnl can only enable up to 30 VFs even if the PF supports up to 63
  VFs in an Openstack SRIOV configuration.

  As already documented in https://bugs.launchpad.net/mos/+bug/1501738
  there is a bug in the default libnl library release installed on

[Desktop-packages] [Bug 797485] Re: SRU: Status Bar Covers File Name at Bottom

2016-10-24 Thread David Imiri

I see the tooltip there as completely unnecessary. Your selected file is
already highlighted in color. What's the point, and what's the delay
just stripping it out?

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

Title:
  SRU: Status Bar Covers File Name at Bottom

Status in Nautilus:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Released
Status in nautilus source package in Xenial:
  In Progress

Bug description:
  [Impact]

  If using Nautilus without a status bar the selected item title
  'floats' at the bottom of the file listing.

  If you choose the last file item in a list this 'floating' title
  prevents you seeing the actual title making editing
  difficult/impossible. This issue is also present in icon view if you
  have an even number of files on the bottom row it becomes difficult to
  rename the last file as the status bar covers the text area.

  [Test Case]

  Using Ubuntu 16.04.1 open the file manager, click "Home", enable list
  view and resize the file manager window so that the contents of the
  home directory just fit vertically and horizontally. Select the last
  item in the file listing and then move the mouse slowly from left to
  right and back again several time. You will see the floating status
  bar will jump from left to right, obscuring details of the selected
  item.

  After the patched nautilus package is installed, performing the same
  test will result on the floating status bar being hidden when the
  mouse hovers over it.

  [Regression Potential]

  None. This patch has been adapted from the following upstream commit:

  * https://git.gnome.org/browse/nautilus/commit/?id=e66d3ca

  Packages have been built in a PPA and tested for regressions.

  [ Other Info ]

  Binary package hint: nautilus

  The following possible solutions were considered:

  * Give the file list a bottom margin of the height of the status bar.
  * Move status bar to the left side when working with files in that corner.
  * Do not show status bar while renaming.
  * Hide the floating bars when hovering over part of the selection.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/797485/+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 797485] Re: SRU: Status Bar Covers File Name at Bottom

2016-10-24 Thread David Imiri

Thank you for working on this! It was first reported in 2011 ~ I'm
trying to tell everyone Ubuntu is a mature OS, this is a maddening daily
problem...

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

Title:
  SRU: Status Bar Covers File Name at Bottom

Status in Nautilus:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Released
Status in nautilus source package in Xenial:
  In Progress

Bug description:
  [Impact]

  If using Nautilus without a status bar the selected item title
  'floats' at the bottom of the file listing.

  If you choose the last file item in a list this 'floating' title
  prevents you seeing the actual title making editing
  difficult/impossible. This issue is also present in icon view if you
  have an even number of files on the bottom row it becomes difficult to
  rename the last file as the status bar covers the text area.

  [Test Case]

  Using Ubuntu 16.04.1 open the file manager, click "Home", enable list
  view and resize the file manager window so that the contents of the
  home directory just fit vertically and horizontally. Select the last
  item in the file listing and then move the mouse slowly from left to
  right and back again several time. You will see the floating status
  bar will jump from left to right, obscuring details of the selected
  item.

  After the patched nautilus package is installed, performing the same
  test will result on the floating status bar being hidden when the
  mouse hovers over it.

  [Regression Potential]

  None. This patch has been adapted from the following upstream commit:

  * https://git.gnome.org/browse/nautilus/commit/?id=e66d3ca

  Packages have been built in a PPA and tested for regressions.

  [ Other Info ]

  Binary package hint: nautilus

  The following possible solutions were considered:

  * Give the file list a bottom margin of the height of the status bar.
  * Move status bar to the left side when working with files in that corner.
  * Do not show status bar while renaming.
  * Hide the floating bars when hovering over part of the selection.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/797485/+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 1635856] Re: cupsd 2.2.0-2 crashed with SIGABRT in __malloc_assert()

2016-10-24 Thread Till Kamppeter

The backslashes were caused by a bug in cups-browsed (package cups-
filters) which I have already fixed before release of 16.10. So after
once removing these entries manually, they should not show up again and
show the crash should not occur again.

But in general, CUPS has no sufficien protection against too long
info/description strings. This should get reported as upstream bug on
http://www.cups.org/.

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

Title:
  cupsd 2.2.0-2 crashed with SIGABRT in __malloc_assert()

Status in cups package in Ubuntu:
  New

Bug description:
  I am unable to print after a smooth upgrade from 16.04 to 16.10, as
  the cupsd service would not start. The installed version of cups-
  daemon is 2.2.0-2.  I am using Ubuntu release 16.10.

  
  Syslog shows:

  Oct 22 18:36:46 mcarro-ThinkPad-X1-Carbon-3rd cupsd[20036]: cupsd:
  malloc.c:2880: mremap_chunk: Assertion `((size + offset) & (GLRO
  (dl_pagesize) - 1)) == 0' failed.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: cups-daemon 2.2.0-2
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CrashCounter: 1
  Date: Sat Oct 22 09:35:50 2016
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2015-06-15 (495 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad 
file descriptor
  MachineType: LENOVO 20BSCTO1WW
  Papersize: a4
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic.efi.signed 
root=UUID=b5bda038-97c0-40f3-b9ba-67c06b05ae03 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic.efi.signed 
root=UUID=b5bda038-97c0-40f3-b9ba-67c06b05ae03 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: cups
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0x7f62b27fa308 "((size + offset) 
& (GLRO (dl_pagesize) - 1)) == 0", file=file@entry=0x7f62b27f6e2e "malloc.c", 
line=line@entry=2880, function=function@entry=0x7f62b27fae28 <__func__.11331> 
"mremap_chunk") at malloc.c:301
   mremap_chunk (p=p@entry=0x5653d935dab0, new_size=new_size@entry=8288) at 
malloc.c:2880
   __GI___libc_realloc (oldmem=0x5653d935dac0, bytes=8275) at malloc.c:3060
   cupsFilePrintf () from /usr/lib/x86_64-linux-gnu/libcups.so.2
   ?? ()
  Title: cupsd crashed with SIGABRT in __malloc_assert()
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (7 days ago)
  UserGroups:
   
  dmi.bios.date: 05/08/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET29W (1.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET29W(1.07):bd05/08/2015:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BSCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1635856/+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 1449112] Re: can't move files to trash without any owner/permission issues

2016-10-24 Thread Sadi Yumuşak

Unfortunately the problem has got worse in Ubuntu 16.10 with Nautilus
3.20.3: nothing can be moved to the "Rubbish Bin" anywhere in an NTFS
partition on the hard disk now (the reason given for this is "Unable to
find or create wastebasket directory" and manually creating such a
directory leads to nothing) although no such problem exists for
removable media such as USB hard disks :(

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

Title:
  can't move files to trash without any owner/permission issues

Status in Nautilus:
  Unknown
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  This is something that wouldn't happen before upgrading from Ubuntu
  14.10 / Nautilus 3.10 to Ubuntu 15.04 / Nautilus 3.14:

  I have a proper HOME partition and most User folders there (Documents,
  Downloads, Music, Pictures, Videos) are merely SYMLINKS to folders
  with the same names in a DATA partition which is mounted automatically
  at startup with proper options in fstab.

  Now -- unlike before -- when I attempt to delete an item in one of
  these folders after I open it via the SYMLINK I get the message "...
  can't be put in the trash. Do you want to delete it immediately?"
  although it is immediately moved to the Trash after I open the folder
  via the Data partition in the sidebar. (Naturally there are no such
  problems with items in other (real) items in my Home folder.

  Nautilus now seems confused about / not knowing where to move the item
  in question; to the Trash folder in the Home partition (symlink
  location) or the Data partition (real item location).

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1449112/+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

Re: [Desktop-packages] [Bug 1623654] Re: simple scan does not recognize the drivers

2016-10-24 Thread Fred Hooper

can you help me fix it?

-Original Message-
From: Brian Murray 
To: fredbaby 
Sent: Fri, Sep 16, 2016 2:20 pm
Subject: [Bug 1623654] Re: simple scan does not recognize the drivers

** Package changed: ubuntu-release-upgrader (Ubuntu) => simple-scan
(Ubuntu)

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1623654

Title:
  simple scan does not recognize the drivers

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

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

Title:
  simple scan does not recognize the drivers

Status in simple-scan package in Ubuntu:
  New

Bug description:
  simple scan worked fine with my printer/scanner - Samsung M2070FW
  beforw my upgrade to 16.07 now the printer works but the scanner does
  not.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.16
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Wed Sep 14 16:32:05 2016
  InstallationDate: Installed on 2014-11-25 (659 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to xenial on 2016-08-04 (41 days ago)
  VarLogDistupgradeApttermlog: Error: [Errno 13] Permission denied: 
'/var/log/dist-upgrade/apt-term.log'
  VarLogDistupgradeTermlog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1623654/+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 1582986] Re: NetworkManager service does not start during bootup

2016-10-24 Thread anairamzap

I can confirm I'm getting this error too. Althou it seems to be a bit random I 
can confirm I didn't get it in Ubuntu 12.04. 
I wish I could be more precise but I can't tell if this is something caused by 
other process... so I can't tell if started happening on 16.04 or after 
installing some package.

Ubuntu 16.04
3.13.0-92-generic
NetworkManager --version: 1.2.2

Here I paste some interesting lines from dmesg:

-
[   19.350616] systemd[1]: network-online.target: Found ordering cycle on 
network-online.target/start
[   19.350623] systemd[1]: network-online.target: Found dependency on 
NetworkManager-wait-online.service/start
[   19.350628] systemd[1]: network-online.target: Found dependency on 
NetworkManager.service/start
[   19.350631] systemd[1]: network-online.target: Found dependency on 
basic.target/start
[   19.350634] systemd[1]: network-online.target: Found dependency on 
sockets.target/start
[   19.350638] systemd[1]: network-online.target: Found dependency on 
uuidd.socket/start
[   19.350641] systemd[1]: network-online.target: Found dependency on 
sysinit.target/start
[   19.350645] systemd[1]: network-online.target: Found dependency on 
firestarter.service/start
[   19.350648] systemd[1]: network-online.target: Found dependency on 
network-online.target/start
[   19.350654] systemd[1]: network-online.target: Breaking ordering cycle by 
deleting job NetworkManager-wait-online.service/start
[   19.350659] systemd[1]: NetworkManager-wait-online.service: Job 
NetworkManager-wait-online.service/start deleted to break ordering cycle 
starting with network-online.target/start
[   19.350750] systemd[1]: network.target: Found ordering cycle on 
network.target/start
[   19.350754] systemd[1]: network.target: Found dependency on 
NetworkManager.service/start
[   19.350758] systemd[1]: network.target: Found dependency on 
basic.target/start
[   19.350762] systemd[1]: network.target: Found dependency on 
sockets.target/start
[   19.350765] systemd[1]: network.target: Found dependency on 
uuidd.socket/start
[   19.350768] systemd[1]: network.target: Found dependency on 
sysinit.target/start
[   19.350771] systemd[1]: network.target: Found dependency on 
firestarter.service/start
[   19.350775] systemd[1]: network.target: Found dependency on 
network-online.target/start
[   19.350778] systemd[1]: network.target: Found dependency on 
network.target/start
[   19.350781] systemd[1]: network.target: Breaking ordering cycle by deleting 
job NetworkManager.service/start
[   19.350785] systemd[1]: NetworkManager.service: Job 
NetworkManager.service/start deleted to break ordering cycle starting with 
network.target/start
-

I'm not sure if the problem is in NetworkManager service itself or if
there is any other service messing around and causing these "ordering
cycles" which seems to end killing the NetworkManager process.

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

Title:
  NetworkManager service does not start during bootup

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 4.4.0-22
  systemd 229-4
  network-manager 1.1.93
  network-manager-gnome 1.2.0

  Multiple services and targets are deleted by systemd to "break
  ordering cycle" (cf. boot.log), but NetworkManager is the only one of
  them (network.target,rpcbind,sysinit.target,open-iscsi.service,remote-
  fs-pre.target,iscsid.service,zfs-fuse.service - cf. their respective
  logs) which is not started after bootup:

  sudo systemctl status NetworkManager.service
  ● NetworkManager.service - Network Manager
 Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: enabled)
 Active: inactive (dead)

  May 18 05:00:10 samsung-ubuntu systemd[1]: NetworkManager.service: Job
  NetworkManager.service/verify-active deleted to break ordering cycle
  starting with network.target/start

  Attachments:
  ---
  - journalctl -l -b0 --system _COMM=systemd > boot.log
  - systemctl -l status rpcbind  > rpcbind.log
  - systemctl -l status network.target  > network.target.txt
  - systemctl -l status remote-fs-pre.target  > remote-fs-pre.target.log
  - systemctl -l status sysinit.target  > sysinit.target.log
  - systemctl -l status zfs-fuse.service  > zfs-fuse.service.log
  - systemctl -l status open-iscsi.service  > open-iscsi.service.log
  - systemctl -l status iscsid.service  > iscsid.service.log

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1582986/+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 1517387] Re: Adobe flash player issue

2016-10-24 Thread Nathanaël Naeri

** Changed in: flashplugin-nonfree (Ubuntu)
   Status: New => Incomplete

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

Title:
  Adobe flash player issue

Status in flashplugin-nonfree package in Ubuntu:
  Incomplete

Bug description:
  There seems to be an issue with flash player in chromium.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/1517387/+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 1544684] Re: package flashplugin-installer 11.2.202.569ubuntu0.14.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before a

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

** Changed in: flashplugin-nonfree (Ubuntu)
   Status: New => Confirmed

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

Title:
  package flashplugin-installer 11.2.202.569ubuntu0.14.04.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting a removal

Status in flashplugin-nonfree package in Ubuntu:
  Confirmed

Bug description:
  install errors with Adobe Flash Player  appears to be a known issue

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: flashplugin-installer 11.2.202.569ubuntu0.14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-lowlatency 3.19.8-ckt12
  Uname: Linux 3.19.0-49-lowlatency x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  AptOrdering: flashplugin-installer: Remove
  Architecture: amd64
  Date: Wed Feb 10 17:57:44 2016
  Dependencies:
   
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
  InstallationDate: Installed on 2015-11-30 (72 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.5
   apt  1.0.1ubuntu2.11
  SourcePackage: flashplugin-installer
  Title: package flashplugin-installer 11.2.202.569ubuntu0.14.04.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/1544684/+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 1118903] Re: [enhancement] Mir lacks a software rendering backend (and doesn't work in virtual machines)

2016-10-24 Thread Bryan Quigley

I've found I can get Unity8 to render in virt-manager (Qemu/KVM) with
Display set to Spice and Video: QXL.

That might be a faster target (for QA) then getting full software
rendering.  The only showstopper is the mouse doesn't let me go across
the entire screen. It seems what Mir says is the screen is different
than what the virt-viewer thinks.

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

Title:
  [enhancement] Mir lacks a software rendering backend (and doesn't work
  in virtual machines)

Status in Canonical System Image:
  New
Status in Mir:
  Triaged
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Triaged

Bug description:
  As always, it's a critical requirement for Ubuntu to be able to render
  the same thing on any machine (metal or virtual), regardless of the
  availability of hardware acceleration.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1118903/+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 1539552] Re: package flashplugin-installer 11.2.202.554ubuntu0.15.10.1 failed to install/upgrade: pakket bevindt zich in een erg slechte en inconsistente staat; u zou het opni

2016-10-24 Thread Nathanaël Naeri

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

** This bug has been marked a duplicate of bug 1544684
   package flashplugin-installer 11.2.202.569ubuntu0.14.04.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal

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

Title:
  package flashplugin-installer 11.2.202.554ubuntu0.15.10.1 failed to
  install/upgrade: pakket bevindt zich in een erg slechte en
  inconsistente staat; u zou het  opnieuw moeten installeren alvorens
  het te proberen verwijderen.

Status in flashplugin-nonfree package in Ubuntu:
  New

Bug description:
  could not install flashplugin-installer bcse of bad state of package
  could not remove is either with apt-get remove.
  still get message that flash plug in is not completely installed

  dpkg did not repair  the issue

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: flashplugin-installer 11.2.202.554ubuntu0.15.10.1
  ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6
  Uname: Linux 4.2.0-22-generic i686
  ApportVersion: 2.19.1-0ubuntu5
  AptOrdering:
   flashplugin-installer: Remove
   NULL: ConfigurePending
  Architecture: i386
  Date: Fri Jan 29 12:40:00 2016
  DpkgTerminalLog:
   dpkg: fout bij verwerken van pakket flashplugin-installer (--remove):
pakket bevindt zich in een erg slechte en inconsistente staat; u zou het
opnieuw moeten installeren alvorens het te proberen verwijderen.
  DuplicateSignature: 
package:flashplugin-installer:11.2.202.554ubuntu0.15.10.1:pakket bevindt zich 
in een erg slechte en inconsistente staat; u zou het  opnieuw moeten 
installeren alvorens het te proberen verwijderen.
  ErrorMessage: pakket bevindt zich in een erg slechte en inconsistente staat; 
u zou het  opnieuw moeten installeren alvorens het te proberen verwijderen.
  InstallationDate: Installed on 2014-06-01 (606 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5.1
   apt  1.0.10.2ubuntu1
  SourcePackage: flashplugin-nonfree
  Title: package flashplugin-installer 11.2.202.554ubuntu0.15.10.1 failed to 
install/upgrade: pakket bevindt zich in een erg slechte en inconsistente staat; 
u zou het  opnieuw moeten installeren alvorens het te proberen verwijderen.
  UpgradeStatus: Upgraded to wily on 2015-11-20 (69 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/1539552/+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 1625438] Re: package flashplugin-installer 11.2.202.635ubuntu0.16.04.1 failed to install/upgrade: problemas de dependencias - se deja sin configurar

2016-10-24 Thread Nathanaël Naeri

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

** This bug has been marked a duplicate of bug 1581874
   package flashplugin-installer 11.2.202.621ubuntu0.16.04.1 failed to 
install/upgrade: dependency problems - leaving unconfigured

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

Title:
  package flashplugin-installer 11.2.202.635ubuntu0.16.04.1 failed to
  install/upgrade: problemas de dependencias - se deja sin configurar

Status in flashplugin-nonfree package in Ubuntu:
  New

Bug description:
  ...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: flashplugin-installer 11.2.202.635ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Mon Sep 19 22:35:56 2016
  ErrorMessage: problemas de dependencias - se deja sin configurar
  InstallationDate: Installed on 2016-07-25 (56 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: flashplugin-nonfree
  Title: package flashplugin-installer 11.2.202.635ubuntu0.16.04.1 failed to 
install/upgrade: problemas de dependencias - se deja sin configurar
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/1625438/+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 1581874] Re: package flashplugin-installer 11.2.202.621ubuntu0.16.04.1 failed to install/upgrade: dependency problems - leaving unconfigured

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

** Changed in: flashplugin-nonfree (Ubuntu)
   Status: New => Confirmed

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

Title:
  package flashplugin-installer 11.2.202.621ubuntu0.16.04.1 failed to
  install/upgrade: dependency problems - leaving unconfigured

Status in flashplugin-nonfree package in Ubuntu:
  Confirmed

Bug description:
  actualitation problem.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: flashplugin-installer 11.2.202.621ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat May 14 22:29:02 2016
  ErrorMessage: dependency problems - leaving unconfigured
  InstallationDate: Installed on 2016-05-05 (8 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.10ubuntu1
  SourcePackage: flashplugin-nonfree
  Title: package flashplugin-installer 11.2.202.621ubuntu0.16.04.1 failed to 
install/upgrade: dependency problems - leaving unconfigured
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/1581874/+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 1270410] Re: package tex-common 4.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-10-24 Thread Edvin Lindström

This bug affects me on 14.04.  Would it be dangerous to endeavour an
upgrade from 14.04 to 16.04 without taking care of this issue first?

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

Title:
  package tex-common 4.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in tex-common package in Ubuntu:
  Fix Released

Bug description:
  This was generated while doing upgrade to newest ubuntu, upgrader
  stopped unity crashed and I had to cntrl/alt f2 to get a terminal and
  had to "sudo killall dpkg" and then "sudo dpkg --configure -a" several
  times to complete the upgrade to the point it was safe to reboot into
  a stable environment.

  ProblemType: Package
  DistroRelease: Ubuntu 13.10
  Package: tex-common 4.04
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Sat Jan 18 05:00:25 2014
  DuplicateSignature: package:tex-common:4.04:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2011-05-07 (986 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: tex-common
  Title: package tex-common 4.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to saucy on 2014-01-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1270410/+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 1612343] Re: Unable to delete large folders in Trash

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

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

Title:
  Unable to delete large folders in Trash

Status in gvfs:
  Incomplete
Status in Ubuntu GNOME:
  Confirmed
Status in gvfs package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  I have found that since the indicator of file operations was replaced
  with the notification coming from the right of the top bar rather than
  a popup window, that I am unable to delete large folders from Trash.
  Placing them in Trash sometimes means that other items (even really
  small ones) can't be deleted until the large folders have been moved
  from Trash to another location, though on other occasions all, or at
  least half, of the other files will be seemingly successfully deleted,
  though not the large folder(s).

  For instance I have a folder with many sub-folders, which each have
  many sub-sub-folders etc and lots of files... The folder's file size
  is about 1.7GB. I tried creating a tar of the file which was 1.8GB, I
  moved that into Trash and it was deleted within about a second with no
  trouble at all so it seems only to be folders.

  I looked at the properties for a large folder I placed in Trash by
  itself, and even though I had clicked the Empty Trash button many
  times now, it was staying at the same size.

  I find that the indicator which is meant to be indicating how it's
  doing to me is always just stuck at "Preparing", even when it actually
  deletes stuff it only ever really shows that so is not very useful.

  I am running Ubuntu GNOME 16.04 with GNOME 3.20, but I believe this
  was also present in 3.18, though not to such a bad degree (pressing
  the Empty Trash button many times in some cases eventually worked on
  3.18, but on 3.20 I can't seem to do anything to delete the folder
  without first splitting it up).

  One thing to note though is that if I am to use the right-click option
  to permanently delete files and folders (which can be enabled in the
  Preferences) then it deletes them just fine apart from showing a huge
  and negative amount of files per seconds, but that is for another bug
  report.

  I have only tested this in Nautilus, I have not yet tested if it works
  better in a different file manager, I will comment when I have tested
  it with a different file manager.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/1612343/+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 1615408] Re: Theming issues with yakkety gnome-calculator in Unity

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

** Changed in: gnome-calculator (Ubuntu)
   Status: New => Confirmed

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

Title:
  Theming issues with yakkety gnome-calculator in Unity

Status in gnome-calculator package in Ubuntu:
  Confirmed

Bug description:
  There are some UI problems with yakkety's gnome-calculator. I'm
  attaching a screenshot taken with yesterday's daily live Ubuntu image.

  1. The title bar says 'gnome-calculator' but it should say Calculator
  2. The Mode menu has an ugly light-colored border around it instead of being 
integrated into either the title bar (like gnome-calculator 3.18.3 in Ubuntu 
16.04 LTS) or in to Unity's menu bar.

  These issues affect both gnome-calculator 1:3.20.1-0ubuntu1 and
  1:3.21.90-0ubuntu1 but do not affect 1:3.18.3-0ubuntu1 on yakkety.

  I think this was caused by the refresh of
  debian/patches/git_no_headerbars_in_unity.patch in the 3.20 update.

  Screenshots attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1615408/+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 1615408] Re: Theming issues with yakkety gnome-calculator in Unity

2016-10-24 Thread David R. Hedges

I have these two problems on two machines as well (both after upgrading
to 16.10). One machine exhibits *just* the two symptoms you describe,
while another also has an odd bug making the numeric/formula entry text
box transparent (see attached).

Interestingly (/frustratingly, confusingly), the menu and transparency
issues are not present when running a guest session on that machine, but
the menu remains an issue in the guest session on the other machine.

** Attachment added: "20161021-2315-transparent-gnome-calculator.png"

https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1615408/+attachment/4766645/+files/20161021-2315-transparent-gnome-calculator.png

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

Title:
Theming issues with yakkety gnome-calculator in Unity

Status in gnome-calculator package in Ubuntu:
Confirmed

Bug description:
There are some UI problems with yakkety's gnome-calculator. I'm
attaching a screenshot taken with yesterday's daily live Ubuntu image.

1. The title bar says 'gnome-calculator' but it should say Calculator
2. The Mode menu has an ugly light-colored border around it instead of being
integrated into either the title bar (like gnome-calculator 3.18.3 in Ubuntu
16.04 LTS) or in to Unity's menu bar.

These issues affect both gnome-calculator 1:3.20.1-0ubuntu1 and
1:3.21.90-0ubuntu1 but do not affect 1:3.18.3-0ubuntu1 on yakkety.

I think this was caused by the refresh of
debian/patches/git_no_headerbars_in_unity.patch in the 3.20 update.

Screenshots attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1615408/+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 1517991] Re: Arithmetical errors

This was fixed in gnome-calculator 3.18.3 which is available in Ubuntu
16.04 LTS.

I was unable to duplicate this bug in Ubuntu 14.04 LTS.

** Changed in: gnome-calculator (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Arithmetical errors

Status in GNOME Calculator:
  Fix Released
Status in gnome-calculator package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu release: 15.10
  Package version: 1:3.16.2-1ubuntu1

  Enter:
  1^(−0.5)

  Result:
  1.071508607×10³⁰¹

  Expected result:
  1

  Upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=756960

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-calculator/+bug/1517991/+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 1169437] Re: network-manager does not configure local resolver or dnsmasq to use the nameserver addresses received from the VPN server

2016-10-24 Thread QkiZ

Ubuntu 16.10 has still this issue.

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

Title:
  network-manager does not configure local resolver or dnsmasq to use
  the nameserver addresses received from the VPN server

Status in network-manager-openvpn package in Ubuntu:
  Fix Released

Bug description:
  NetworkManager/dnsmasq does not set the DNS servers given by the
  OpenVPN server when I connect. I can see in my syslog that I do
  receive the name server addresses correctly along with all the routes:

  Apr 16 08:14:09 homer NetworkManager[4014]:Internal DNS: 
192.168.11.90
  Apr 16 08:14:09 homer NetworkManager[4014]:Internal DNS: 
192.168.11.190

  However, they are not used:

  oscar@homer:~$ nmcli -f IP4 dev list | grep DNS
  IP4.DNS[1]: 192.168.0.1
  oscar@homer:~$

  (That is my default DNS/Gateway and it should still be queried for all
  DNS queries outside of VPN network)

  If I comment out dns=dnsmasq in
  /etc/NetworkManager/NetworkManager.conf and restart NetworkManager
  then DNS starts to work properly again, VPN nameservers are used for
  domain names on the VPN network and others through my default
  nameserver. Let me know if I kan provide further info about this
  issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: network-manager 0.9.6.0-0ubuntu7
  ProcVersionSignature: Ubuntu 3.5.0-28.47-generic 3.5.7.9
  Uname: Linux 3.5.0-28-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Tue Apr 16 08:16:42 2013
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2012-11-22 (144 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  IpRoute:
   default via 192.168.0.1 dev eth1  proto static
   192.168.0.0/24 dev eth1  proto kernel  scope link  src 192.168.0.44  metric 9
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2013-04-16T08:12:17.691993
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH
   Wired connection 1179bc6d7-cd13-4cfb-b73f-e8da8362a511   
802-3-ethernet1364485020   tor 28 mar 2013 16:37:00   yes   
no /org/freedesktop/NetworkManager/Settings/2
   Wiggum2a818c4e-494c-4b91-be56-630636608f07   
802-11-wireless   1366092808   tis 16 apr 2013 08:13:28   yes   
no /org/freedesktop/NetworkManager/Settings/1
     81e14bde-0b0b-42be-8b56-3bfda6ca60fc   vpn   
1366092850   tis 16 apr 2013 08:14:10   yes   no 
/org/freedesktop/NetworkManager/Settings/0
      aad98317-a8e1-4ff7-b3b5-7c43c1bcfd32   802-11-wireless   
1358879064   tis 22 jan 2013 19:24:24   yes   no 
/org/freedesktop/NetworkManager/Settings/3
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH
   eth1   802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN
   running 0.9.6.0connected   enabled   enabled 
enabledenabled disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1169437/+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 1633408] Re: 3.22.0 wont allow cut&paste in history pane

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

** Changed in: gnome-calculator (Ubuntu)
   Status: New => Confirmed

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

Title:
  3.22.0 wont allow cut&paste in history pane

Status in gnome-calculator package in Ubuntu:
  Confirmed

Bug description:
  The calculator's history, in 3.22.0  is now non-selected-able, in 3.18.x this 
use to be possible was the change  intentional?
  If not can the change be reverted.

  
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-03-01 (227 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: gnome-calculator 1:3.22.0-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Tags:  yakkety
  Uname: Linux 4.8.0-22-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev pulse pulse-access sambashare 
sudo vboxusers video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1633408/+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 1633408] Re: 3.22.0 wont allow cut&paste in history pane

The issue you are reporting is an upstream one and it would be nice if
somebody having it could send the bug to the developers of the software
by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

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

Title:
  3.22.0 wont allow cut&paste in history pane

Status in gnome-calculator package in Ubuntu:
  Confirmed

Bug description:
  The calculator's history, in 3.22.0  is now non-selected-able, in 3.18.x this 
use to be possible was the change  intentional?
  If not can the change be reverted.

  
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-03-01 (227 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: gnome-calculator 1:3.22.0-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Tags:  yakkety
  Uname: Linux 4.8.0-22-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev pulse pulse-access sambashare 
sudo vboxusers video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1633408/+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 1584740] Re: Libreoffice impress hanging and high cpu on slide operations

2016-10-24 Thread Hernan Asorey

I can confirm that I experienced same problem in Lenovo i5 with 8GB RAM,
running with up-to-date Ubuntu 16.04.01 using LibreOffice 5.1.4.2
10m0(Build:2). The problem was solved after remove libreoffice-gtk* as
@mcnichol suggested.

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

Title:
  Libreoffice impress hanging and high cpu on slide operations

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  - Create a presentation in libreoffice impress, 30-100 slides with or without 
images
  - Add, copy or delete slides
  - On those operations LO Impress hangs a lot; sometimes 5 mins or more
  - Opening and saving works quick

  Tested on 2 different laptops, both had the same issue. Both did have
  Intel Graphics, but different  ones.  It works fine on the same laptop
  with LO 5.1 on Ubuntu 14.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-impress 1:5.1.2-0ubuntu1
  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: Mon May 23 12:55:08 2016
  InstallationDate: Installed on 2016-04-29 (23 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1584740/+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 1560162] [ubiquity/xenial] possible regression found

2016-10-24 Thread Ubuntu Foundations Team Bug Bot

As a part of the Stable Release Updates quality process a search for
Launchpad bug reports using the version of ubiquity from xenial-proposed
was performed and bug 1631652 was found.  Please investigate this bug
report to ensure that a regression will not be created by this SRU. In
the event that this is not a regression remove the "verification-failed"
tag from this bug report and add the tag "bot-stop-nagging" to bug
1631652 (not this bug). Thanks!

** Tags added: verification-failed

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

Title:
  Xenial: scaling is horribly out on xps13 install session

Status in OEM Priority Project:
  New
Status in metacity package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in metacity source package in Xenial:
  Fix Released
Status in ubiquity source package in Xenial:
  Fix Committed

Bug description:
  STEPS:
  Requirements laptop desktop with a hidpi screen (Here xps 13)
  1. Grab the latest daily image and trigger an install
  2. On the first page notice the of centre and over scaled window

  EXPECTED:
  I expect to see something resembling a normal scaled desktop install

  ACTUAL:
  Things are not quite correct see attached screenshots

  ubiquity/xenial 2.21.49 amd64

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1560162/+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 1417470] Re: PDF+Latex export creates multipage pdf, pages missing

2016-10-24 Thread Florian Toth

A quick fix to get the svg+tex > pdflatex pipline working again is to
use eps-export and convert to pdf:

inkscape -z -D --file=#1.svg --export-eps=#1.eps --export-latex
epstopdf #1.eps
sed "s/[.]eps/.pdf/g" #1.eps_tex > #1.pdf_tex

where #1 is your inkscape file.

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

Title:
  PDF+Latex export creates multipage pdf, pages missing

Status in Inkscape:
  Confirmed
Status in inkscape package in Ubuntu:
  Confirmed
Status in inkscape package in Debian:
  Confirmed

Bug description:
  In 0.91 the z-order information in svg is used to create multipage
  PDF+LaTeX documents as per bug 771957. However, for the SVGs I have
  been converting to PDF+LaTeX in this way, the TeX-file instructs to
  load more pages than the PDF has, for example the PDF has only three
  pages and the TeX file also includes page=4. This basically breaks the
  PDF+LaTeX export for me and I have to use EPS+LaTeX + epstopdf
  package.

  The bug occurs on OpenSuse 13.1 and Windows 8.1.

  Attached a zip file with two svg files and their broken PDF+LaTeX
  counterparts.

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/1417470/+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 418242] Re: Incorrect call to output plugins (with persistent error message) on copy

2016-10-24 Thread sgmanohar

** Description changed:

  UPDATE: After further investigation it turned out to be a problem related to 
the copy operation, in combination with a totally unrelated running Java 
program (FreeRapid).
- Reading some followups and other bug reports, it seems to be caused by the 
new clipboard management system (introduced as a fix for the bug #170185), as 
reported in bug #421597. 
+ Reading some followups and other bug reports, it seems to be caused by the 
new clipboard management system (introduced as a fix for the bug #170185), as 
reported in bug #421597.
  
  The routine ClipboardManagerImpl::_onGet is called repeatedly by an
  external program, with different possible clipboard formats, causing
  Inkscape to try and export the copied data every few seconds, in
  multiple formats.
  
  So far these applications are known to randomly trigger an input/output 
extension (on linux):
  - FreeRapid Downloader
  - jDownloader
  - xfce4-clipman-plugin 1.1.3
  - Netbeans
  - xfce4-settings-helper (Xfce 4.8)
  - Team Viewer (teamviewerd 10.0.36)
  
+ Workaround - disable offending output/export plugins (comment #87)
  -
  
  The original report was this:
  I'm getting this error when I try to edit a text object created previously 
with a font that's not available in this system.
  It looks like Inkscape has problems to resolve the font substitution and 
displays the error message in a popup window that keeps appearing again and 
again, leaving no other remedy than closing inkscape and reopening it.
  
  The error message is attached.

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

Title:
  Incorrect call to output plugins (with persistent error message) on
  copy

Status in Inkscape:
  Triaged
Status in inkscape package in Ubuntu:
  Triaged
Status in inkscape package in Arch Linux:
  New
Status in inkscape package in Debian:
  Confirmed
Status in Gentoo Linux:
  Unknown

Bug description:
  UPDATE: After further investigation it turned out to be a problem related to 
the copy operation, in combination with a totally unrelated running Java 
program (FreeRapid).
  Reading some followups and other bug reports, it seems to be caused by the 
new clipboard management system (introduced as a fix for the bug #170185), as 
reported in bug #421597.

  The routine ClipboardManagerImpl::_onGet is called repeatedly by an
  external program, with different possible clipboard formats, causing
  Inkscape to try and export the copied data every few seconds, in
  multiple formats.

  So far these applications are known to randomly trigger an input/output 
extension (on linux):
  - FreeRapid Downloader
  - jDownloader
  - xfce4-clipman-plugin 1.1.3
  - Netbeans
  - xfce4-settings-helper (Xfce 4.8)
  - Team Viewer (teamviewerd 10.0.36)

  Workaround - disable offending output/export plugins (comment #87)
  -

  The original report was this:
  I'm getting this error when I try to edit a text object created previously 
with a font that's not available in this system.
  It looks like Inkscape has problems to resolve the font substitution and 
displays the error message in a popup window that keeps appearing again and 
again, leaving no other remedy than closing inkscape and reopening it.

  The error message is attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/418242/+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 1636290] [NEW] package xserver-xorg-input-wacom 1:0.25.0-0ubuntu1.1 failed to install/upgrade: unable to move aside `./lib/udev/rules.d/69-wacom.rules' to install new version:

2016-10-24 Thread Daniel Ellerbrock

Public bug reported:

happens after apt-get upgrade

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: xserver-xorg-input-wacom 1:0.25.0-0ubuntu1.1
Uname: Linux 4.4.22v7-aufs armv7l
ApportVersion: 2.17.2-0ubuntu1.8
Architecture: armhf
Date: Mon Oct 17 15:02:08 2016
DuplicateSignature: package:xserver-xorg-input-wacom:1:0.25.0-0ubuntu1.1:unable 
to move aside `./lib/udev/rules.d/69-wacom.rules' to install new version: 
Invalid cross-device link
ErrorMessage: unable to move aside `./lib/udev/rules.d/69-wacom.rules' to 
install new version: Invalid cross-device link
RelatedPackageVersions:
 dpkg 1.17.25ubuntu1.1
 apt  1.0.9.7ubuntu4.2
SourcePackage: xf86-input-wacom
Title: package xserver-xorg-input-wacom 1:0.25.0-0ubuntu1.1 failed to 
install/upgrade: unable to move aside `./lib/udev/rules.d/69-wacom.rules' to 
install new version: Invalid cross-device link
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: xf86-input-wacom (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package armhf need-duplicate-check vivid

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

Title:
  package xserver-xorg-input-wacom 1:0.25.0-0ubuntu1.1 failed to
  install/upgrade: unable to move aside
  `./lib/udev/rules.d/69-wacom.rules' to install new version: Invalid
  cross-device link

Status in xf86-input-wacom package in Ubuntu:
  New

Bug description:
  happens after apt-get upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-input-wacom 1:0.25.0-0ubuntu1.1
  Uname: Linux 4.4.22v7-aufs armv7l
  ApportVersion: 2.17.2-0ubuntu1.8
  Architecture: armhf
  Date: Mon Oct 17 15:02:08 2016
  DuplicateSignature: 
package:xserver-xorg-input-wacom:1:0.25.0-0ubuntu1.1:unable to move aside 
`./lib/udev/rules.d/69-wacom.rules' to install new version: Invalid 
cross-device link
  ErrorMessage: unable to move aside `./lib/udev/rules.d/69-wacom.rules' to 
install new version: Invalid cross-device link
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1.1
   apt  1.0.9.7ubuntu4.2
  SourcePackage: xf86-input-wacom
  Title: package xserver-xorg-input-wacom 1:0.25.0-0ubuntu1.1 failed to 
install/upgrade: unable to move aside `./lib/udev/rules.d/69-wacom.rules' to 
install new version: Invalid cross-device link
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1636290/+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 1636282] Re: network-manager after suspend showing arrow icon instead of wifi icon and showing no wifi networks

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

Title:
  network-manager after suspend showing arrow icon instead of wifi icon
  and showing no wifi networks

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  As requested by Mathieu Trudel-Lapierre (cyphermox) in bug #1589401
  I'm creating my own bug report.

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  $ apt-cache policy network-manager
  network-manager:
Installiert:   1.2.2-0ubuntu0.16.04.3
Installationskandidat: 1.2.2-0ubuntu0.16.04.3
Versionstabelle:
   *** 1.2.2-0ubuntu0.16.04.3 500
  500 http://ch.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.1.93-0ubuntu4 500
  500 http://ch.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  3) What you expected to happen
  I'm connected by WiFi only, not by a wired connection. I expect to see the 
WiFi icon anytime while being connected to my WiFi network. Also, I expect to 
see all the WiFi networks around me (at least one other network with good 
reception and about 3 with bad reception).

  4) What happened instead
  After waking up the laptop from suspend, there appears the ethernet icon 
(arrow symbols) instead of the WiFi icon.
  Also, in this state there are no other WiFi networks visible in the 
network-manager.
  However, the laptop is still connected with my WiFi and the connection works 
as usual.
  Using "service network-manager restart" in the console I can get the wireless 
icon back and all the other networks around me are visible again.
  This can be reproduced anytime and with 100% "success rate". The problem 
appeared with Ubuntu 16.10 and was persistent since.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 24 20:06:09 2016
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-05-15 (161 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.1.1 dev wlo1  proto static  metric 600 
   169.254.0.0/16 dev wlo1  scope link  metric 1000 
   192.168.1.0/24 dev wlo1  proto kernel  scope link  src 192.168.1.244  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlo1wifi  connected/org/freedesktop/NetworkManager/Devices/2  
WiNet 2 162de978-4466-46b0-957b-5f9c141d702a  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   eno1ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/0  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1636282/+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 1636285] [NEW] web radio site request a plugin to show chatbox and there is no sound

2016-10-24 Thread christos

Public bug reported:

i have sound generally but not in this site
http://www.musicartclub.gr/player/ and on the chat box's place it shows
the message "a plugin is needed to display this content"

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: firefox 41.0.2+build2-0ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic i686
AddonCompatCheckDisabled: False
ApportVersion: 2.19.1-0ubuntu3
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  christos812 F lxpanel
BuildID: 20151016093451
Channel: Unavailable
CurrentDesktop: LXDE
Date: Mon Oct 24 21:35:58 2016
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2016-10-24 (0 days ago)
InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
IpRoute:
 default via 192.168.1.1 dev enp1s12  proto static  metric 100 
 192.168.1.0/24 dev enp1s12  proto kernel  scope link  src 192.168.1.67  metric 
100
IwConfig:
 lono wireless extensions.
 
 enp1s12   no wireless extensions.
Locales: extensions.sqlite corrupt or missing
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=41.0.2/20151016093451 (In use)
RfKill:
 
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/24/2002
dmi.bios.vendor: Dell Computer Corporation
dmi.bios.version: A03
dmi.board.name: 02X378
dmi.board.vendor: Dell Computer Corp.
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Computer Corporation
dmi.modalias: 
dmi:bvnDellComputerCorporation:bvrA03:bd09/24/2002:svnDellComputerCorporation:pnOptiPlexGX260:pvr:rvnDellComputerCorp.:rn02X378:rvr:cvnDellComputerCorporation:ct3:cvr:
dmi.product.name: OptiPlex GX260
dmi.sys.vendor: Dell Computer Corporation

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


** Tags: apport-bug i386 wily

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

Title:
  web radio site request a plugin to show chatbox and there is no sound

Status in firefox package in Ubuntu:
  New

Bug description:
  i have sound generally but not in this site
  http://www.musicartclub.gr/player/ and on the chat box's place it
  shows the message "a plugin is needed to display this content"

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: firefox 41.0.2+build2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic i686
  AddonCompatCheckDisabled: False
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  christos812 F lxpanel
  BuildID: 20151016093451
  Channel: Unavailable
  CurrentDesktop: LXDE
  Date: Mon Oct 24 21:35:58 2016
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2016-10-24 (0 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
  IpRoute:
   default via 192.168.1.1 dev enp1s12  proto static  metric 100 
   192.168.1.0/24 dev enp1s12  proto kernel  scope link  src 192.168.1.67  
metric 100
  IwConfig:
   lono wireless extensions.
   
   enp1s12   no wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=41.0.2/20151016093451 (In use)
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/24/2002
  dmi.bios.vendor: Dell Computer Corporation
  dmi.bios.version: A03
  dmi.board.name: 02X378
  dmi.board.vendor: Dell Computer Corp.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Computer Corporation
  dmi.modalias: 
dmi:bvnDellComputerCorporation:bvrA03:bd09/24/2002:svnDellComputerCorporation:pnOptiPlexGX260:pvr:rvnDellComputerCorp.:rn02X378:rvr:cvnDellComputerCorporation:ct3:cvr:
  dmi.product.name: OptiPlex GX260
  dmi.sys.vendor: Dell Computer Corporation

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

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

[Desktop-packages] [Bug 1606319] Re: Nautilus executing "folder up" command subsequently inside NFS mounted folders

2016-10-24 Thread rjb

I'm surprised nobody else got this problem with nautilus automatically browsing 
back inside NFS mounted folders?
I just checked today with current nautilus 1:3.18.4.is.3.14.3-0ubuntu5 and I 
still can reproduce the problem.

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

Title:
  Nautilus executing "folder up" command subsequently inside NFS mounted
  folders

Status in nautilus package in Ubuntu:
  New

Bug description:
  I've got automounted several NFS folders using this kind of command in fstab:
  192.168.1.10:/Pictures/mnt/Pictures nfs 
noauto,x-systemd.automount,x-systemd.device-timeout=10,x-systemd.idle-timeout=1min
 0 0

  These mounts are linked to the default home folders using this kind of 
command:
  ln -s /mnt/Pictures/ /home/my_pc/

  If I browse into a folder which is physically there (e.g. "Downloads"), 
everything is fine.
  If I browse into one of the mounted/linked folders, nautilus navigates 
subsequently back to the home folder. It navigates in the tree up folder by 
folder in about one folder per minute. I can even minimize the Nautilus window 
and do something else and when I open the window again it made several steps 
back. Therefore any strange commands coming from input devices can be excluded.

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  nautilus:
Installiert:   1:3.18.4.is.3.14.3-0ubuntu4
Installationskandidat: 1:3.18.4.is.3.14.3-0ubuntu4
Versionstabelle:
   *** 1:3.18.4.is.3.14.3-0ubuntu4 500
  500 http://ch.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen
  nothing should happen

  4) What happened instead
  Nautilus subsequently browses back to the home folder if you navigated into a 
folder that is mounted by NFS.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jul 25 18:27:51 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-05-15 (70 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1606319/+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 1636283] [NEW] Sets up "managed" mode for new interface despite "ibss" type is explicitly asked to set to.

2016-10-24 Thread kamiccolo

Public bug reported:

To reproduce:

$ iw phy phy0 interface add ah0 type ibss
$ iw dev

> phy#0
Interface ah0
wddev 0x5
addr xx.xx.xx.xx.xx.xx.xx
type managed

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

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

Title:
  Sets up "managed" mode for new interface despite "ibss" type is
  explicitly asked to set to.

Status in iw package in Ubuntu:
  New

Bug description:
  To reproduce:

  $ iw phy phy0 interface add ah0 type ibss
  $ iw dev

  > phy#0
  Interface ah0
  wddev 0x5
  addr xx.xx.xx.xx.xx.xx.xx
  type managed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iw/+bug/1636283/+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 1590244] Re: Upgrading upower package caused forced reboot

2016-10-24 Thread Timo Aaltonen

not a single comment on the upstream bug, so guess not

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

Title:
  Upgrading upower package caused forced reboot

Status in Upower:
  Unknown
Status in upower package in Ubuntu:
  Confirmed

Bug description:
  When upower was updated, the system claimed that my UPS was empty.
  The system then proceeded to shut down.  On reboot, the UPS was fully
  charged as expected.

  This is a major data loss concern.  The system shut down while
  upgrading packages.  Perhaps the bug is in the handling of my specific
  UPS but it's still important.

  jlquinn@cerberus:~$ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  jlquinn@cerberus:~$ apt-cache policy upower
  upower:
Installed: 0.99.4-2ubuntu0.2
Candidate: 0.99.4-2ubuntu0.2
Version table:
   *** 0.99.4-2ubuntu0.2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   0.99.4-2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  output of lsusb -v for my UPS

  Bus 003 Device 002: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS
  Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB   1.10
bDeviceClass0 (Defined at Interface level)
bDeviceSubClass 0 
bDeviceProtocol 0 
bMaxPacketSize0 8
idVendor   0x0764 Cyber Power System, Inc.
idProduct  0x0501 CP1500 AVR UPS
bcdDevice0.01
iManufacturer   3 CPS
iProduct1 CP625HGa
iSerial 0 
bNumConfigurations  1
Configuration Descriptor:
  bLength 9
  bDescriptorType 2
  wTotalLength   34
  bNumInterfaces  1
  bConfigurationValue 1
  iConfiguration  0 
  bmAttributes 0x80
(Bus Powered)
  MaxPower   50mA
  Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber0
bAlternateSetting   0
bNumEndpoints   1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass  0 No Subclass
bInterfaceProtocol  0 None
iInterface  0 
  HID Device Descriptor:
bLength 9
bDescriptorType33
bcdHID   1.10
bCountryCode   33 US
bNumDescriptors 1
bDescriptorType34 Report
wDescriptorLength 410
   Report Descriptors: 
 ** UNAVAILABLE **
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x81  EP 1 IN
  bmAttributes3
Transfer TypeInterrupt
Synch Type   None
Usage Type   Data
  wMaxPacketSize 0x0008  1x 8 bytes
  bInterval  10
  Device Status: 0x
(Bus Powered)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: upower 0.99.4-2ubuntu0.2
  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.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jun  8 00:27:23 2016
  InstallationDate: Installed on 2016-05-30 (8 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: upower
  UpgradeStatus: Upgraded to xenial on 2016-05-31 (7 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/upower/+bug/1590244/+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 1589401] Re: cannot view wifi networks after re-enabling wifi

2016-10-24 Thread rjb

As requested by Mathieu Trudel-Lapierre (cyphermox) I have filed my own
bug report in bug #1636282

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

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1589401/+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 1636282] [NEW] network-manager after suspend showing arrow icon instead of wifi icon and showing no wifi networks

2016-10-24 Thread rjb

Public bug reported:

As requested by Mathieu Trudel-Lapierre (cyphermox) in bug #1589401 I'm
creating my own bug report.

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
$ lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04

2) The version of the package you are using, via 'apt-cache policy pkgname' or 
by checking in Software Center
$ apt-cache policy network-manager
network-manager:
  Installiert:   1.2.2-0ubuntu0.16.04.3
  Installationskandidat: 1.2.2-0ubuntu0.16.04.3
  Versionstabelle:
 *** 1.2.2-0ubuntu0.16.04.3 500
500 http://ch.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1.1.93-0ubuntu4 500
500 http://ch.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

3) What you expected to happen
I'm connected by WiFi only, not by a wired connection. I expect to see the WiFi 
icon anytime while being connected to my WiFi network. Also, I expect to see 
all the WiFi networks around me (at least one other network with good reception 
and about 3 with bad reception).

4) What happened instead
After waking up the laptop from suspend, there appears the ethernet icon (arrow 
symbols) instead of the WiFi icon.
Also, in this state there are no other WiFi networks visible in the 
network-manager.
However, the laptop is still connected with my WiFi and the connection works as 
usual.
Using "service network-manager restart" in the console I can get the wireless 
icon back and all the other networks around me are visible again.
This can be reproduced anytime and with 100% "success rate". The problem 
appeared with Ubuntu 16.10 and was persistent since.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.2.2-0ubuntu0.16.04.3
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Oct 24 20:06:09 2016
EcryptfsInUse: Yes
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-05-15 (161 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
IpRoute:
 default via 192.168.1.1 dev wlo1  proto static  metric 600 
 169.254.0.0/16 dev wlo1  scope link  metric 1000 
 192.168.1.0/24 dev wlo1  proto kernel  scope link  src 192.168.1.244  metric 
600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 wlo1wifi  connected/org/freedesktop/NetworkManager/Devices/2  
WiNet 2 162de978-4466-46b0-957b-5f9c141d702a  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 eno1ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/0  --   
   ---- 

 lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  --   
   ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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

Title:
  network-manager after suspend showing arrow icon instead of wifi icon
  and showing no wifi networks

Status in network-manager package in Ubuntu:
  New

Bug description:
  As requested by Mathieu Trudel-Lapierre (cyphermox) in bug #1589401
  I'm creating my own bug report.

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  $ apt-cache policy network-manager
  network-manager:
Installiert:   1.2.2-0ubuntu0.16.04.3
Installationskandidat: 1.2.2-0ubuntu0.16.04.3
Versionstabelle:
   *** 1.2.2-0ubuntu0.16.04.3 500
  500 http://ch.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.1.93-0ubuntu4 500
  500 http://ch.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  3) What you expected to happen
  I'm connected by WiFi only, not by a wired connection. I expect to see the 
WiFi icon anytime while being connected to my

[Desktop-packages] [Bug 1577197] Re: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized

2016-10-24 Thread Vahid Mardani

The original gist updated to work with 16.10 also:

 https://gist.github.com/pylover/d68be364adac5f946887b85e6ed6e7ae#file-
a2dp-py

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

Title:
  Pulseaudio bluez5-util.c: TryAcquire() failed  - Operation Not
  Authorized

Status in bluez package in Ubuntu:
  Confirmed
Status in indicator-sound package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pulseaudio outright stops audio via Bluetooth after sleep or prolonged period 
of time. Only restart fixes the issue. This started early 2016 in 15.10.
  Issue is discussed here as well 
http://askubuntu.com/questions/763539/bluetooth-speaker-no-sound-in-ubuntu-16-04
 and mentioned in other unrelated bugs.

  Ubuntu Xenial 16.04 LTS

  The log below:

  May  1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] 
module-bluez5-device.c: Default profile not connected, selecting off profile
  May  1 17:18:07 jalexoidmobile bluetoothd[7349]: 
/org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4: fd(35) ready
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 3 threads of 1 
processes of 1 users.
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Successfully made thread 
10967 of process 2884 (n/a) owned by '1000' RT at priority 5.
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 4 threads of 1 
processes of 1 users.
  May  1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] bluez5-util.c: 
Transport TryAcquire() failed for transport 
/org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4 (Operation Not Authorized)
  May  1 17:18:07 jalexoidmobile kernel: [20583.032442] input: 
00:02:3C:05:99:F2 as /devices/virtual/input/input24
  May  1 17:18:19 jalexoidmobile pulseaudio[2884]: [pulseaudio] sink-input.c: 
Failed to create sink input: sink is suspended.


  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 006: ID 04f2:b2da Chicony Electronics Co., Ltd thinkpad t430s 
camera
  Bus 001 Device 008: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 
[ThinkPad]
  Bus 001 Device 004: ID 147e:2020 Upek TouchChip Fingerprint Coprocessor (WBF 
advanced mode)
  Bus 001 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  [20388.983474] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [20389.070114] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6
  [20389.070120] usb 1-1.4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [20389.070122] usb 1-1.4: Product: BCM20702A0
  [20389.070124] usb 1-1.4: Manufacturer: Broadcom Corp
  [20389.070126] usb 1-1.4: SerialNumber: 446D578686DD
  [20389.076232] Bluetooth: hci0: BCM: chip id 63
  [20389.092220] Bluetooth: hci0: BCM20702A
  [20389.093225] Bluetooth: hci0: BCM20702A1 (001.002.014) build 
  [20389.551476] wlan0: authenticate with a0:63:91:2f:3f:ed
  [20389.554391] wlan0: send auth to a0:63:91:2f:3f:ed (try 1/3)
  [20389.557790] wlan0: authenticated
  [20389.558339] wlan0: associate with a0:63:91:2f:3f:ed (try 1/3)
  [20389.562209] wlan0: RX AssocResp from a0:63:91:2f:3f:ed (capab=0x1411 
status=0 aid=2)
  [20389.581260] wlan0: associated
  [20389.581369] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [20389.830185] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1669
  [20389.846186] Bluetooth: hci0: Broadcom Bluetooth Device
  [20418.269466] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input23
  [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1577197/+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 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial

2016-10-24 Thread Tamir

For yak actuality

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

Title:
  [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial

Status in PulseAudio:
  Unknown
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in bluez source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Vivid:
  Won't Fix

Bug description:
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

  The bug is still present in 16.04 LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1438510/+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 1636262] [NEW] package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2016-10-24 Thread John Bauer

Public bug reported:

Upon upgrade from 16.04 to 16.10 this error started occurring. I was
upgrading via the integrated updater.

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: cracklib-runtime 2.9.2-3
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Sat Oct 22 20:43:28 2016
ErrorMessage: dependency problems - leaving triggers unprocessed
InstallationDate: Installed on 2016-08-29 (56 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.1
SourcePackage: cracklib2
Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
UpgradeStatus: Upgraded to yakkety on 2016-10-23 (1 days ago)

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


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

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

Title:
  package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in cracklib2 package in Ubuntu:
  New

Bug description:
  Upon upgrade from 16.04 to 16.10 this error started occurring. I was
  upgrading via the integrated updater.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: cracklib-runtime 2.9.2-3
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Sat Oct 22 20:43:28 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-08-29 (56 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: cracklib2
  Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2016-10-23 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cracklib2/+bug/1636262/+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 1567578] Re: libnl should be updated to support up to 63 VFs per single PF

2016-10-24 Thread Brian Murray

Hello Lorenzo, or anyone else affected,

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

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

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

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

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

** Tags added: verification-needed

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

Title:
   libnl should be updated to support up to 63 VFs per single PF

Status in libnl3 package in Ubuntu:
  Fix Released
Status in libnl3 source package in Precise:
  New
Status in libnl3 source package in Trusty:
  Fix Committed

Bug description:
  [Description]

  Ubuntu 14.04.4 and SRIOV settings.

  As already documented in https://bugs.launchpad.net/mos/+bug/1501738
  there is a bug in the default libnl library release installed on
  Ubuntu 14.04.4

  When trying to enable a guest with more than 30 VFs attached, the
  following error is returned:

  error: Failed to start domain guest1
  error: internal error: missing IFLA_VF_INFO in netlink response

  [Impact]

  The library release is the 3.2.21-1 the bug is impacting on the
  maximum VFs number that can be enabled (up to 30) even if the PF
  supports up to 63 VFs in an Openstack SRIOV configuration

  [Test Case]

  The sequence to reproduce this bug is:

  1) Edit /etc/default/grub

  GRUB_CMDLINE_LINUX="intel_iommu=on ixgbe.max_vfs=63"

  2) $ sudo update-grub

  ### Reboot the machine.

  3) Check that the virtual functions are available:

  $ sudo lspci|grep -i eth | grep -i virtual | wc -l
  126

  4) Create a KVM guest

  $ sudo uvt-kvm create guest1 release=trusty

  5) List the VF devices :

  $ sudo lspci|grep -i eth | grep -i virtual | awk '{print $1}' | sed
  's/\:/\_/g' | sed 's/\./\_/g' > devices.txt

  6) Get the libvirt node device:

  $ sudo for device in $(cat ./devices.txt); do virsh nodedev-list |
  grep $device; done > pci_devices.txt

  7) Generate the XML config for each device:

  $ sudo mkdir devices && for d in $(cat pci_devices.txt); do virsh
  nodedev-dumpxml $d > devices/$d.xml; done

  8) Save and Run the following script
  (http://pastebin.ubuntu.com/23374186/)

  $ sudo python generate-interfaces.py |grep address | wc -l

  9) Finally attach the devices to the guest.

  $ sudo for i in $(seq 0 63); do virsh attach-device guest1 
./interfaces/$i.xml --config; done
  Device attached successfully
  [...]

  Device attached successfully
  Device attached successfully

  10) Then destroy/start the guest again, at this point the error is
  reproduced.

  $ sudo virsh destroy guest1
  Domain guest1 destroyed

  $ sudo virsh start guest1

  error: Failed to start domain guest1
  error: internal error: missing IFLA_VF_INFO in netlink response

   * detailed instructions how to reproduce the bug

   * these should allow someone who is not familiar with the affected
 package to reproduce the bug and verify that the updated package fixes
 the problem.

  [Regression Potential]

   ** None identified.

  [Other Info]

  - Redhat Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1040626

  [Workaround]

  The workaround is to install a newer library release, the 3.2.24-2:

  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-3-200_3.2.24-2_amd64.deb
  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-genl-3-200_3.2.24-2_amd64.deb
  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-route-3-200_3.2.24-2_amd64.deb
  dpkg -i libnl-3-200_3.2.24-2_amd64.deb
  dpkg -i libnl-genl-3-200_3.2.24-2_amd64.deb
  dpkg -i libnl-route-3-200_3.2.24-2_amd64.deb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1567578/+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 1635638] Re: nvidia-367 367.57-0ubuntu3: nvidia-367 kernel module failed to build

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

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

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

Title:
  nvidia-367 367.57-0ubuntu3: nvidia-367 kernel module failed to build

Status in nvidia-graphics-drivers-367 package in Ubuntu:
  Confirmed

Bug description:
  Doing a straight upgrade ..

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: nvidia-367 367.57-0ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-22.24-lowlatency 4.8.0
  Uname: Linux 4.8.0-22-lowlatency x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  DKMSKernelVersion: 4.8.0-26-lowlatency
  Date: Fri Oct 21 07:33:44 2016
  InstallationDate: Installed on 2016-10-18 (2 days ago)
  InstallationMedia: budgie-remix 16.10 "Budgie-remix" -  amd64 (20161013)
  PackageVersion: 367.57-0ubuntu3
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: nvidia-graphics-drivers-367
  Title: nvidia-367 367.57-0ubuntu3: nvidia-367 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1635638/+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 1636255] [NEW] The "restore-missing" functionality is not working as expected

2016-10-24 Thread Nicola Jelmorini

Public bug reported:

I have found out that the "--restore-missing" functionality is not working as 
expected.
I have set up déja-dup to backup some folders every day.

If I delete some files today, and then I use the "restore-missing"
functionality the same day (today in my example), déja-dup shows me the
list of missing files as expected.

The problem is that if I use the "restore-missing" functionality from tomorrow 
on, no files are listed anymore. It seems that "restore-missing" seeks the 
missing files only if the backup is made the same day that I deleted the files.
The behavior I expected is that "restore-missing" should search the entire 
backup series, and create a list of all missing files since the first backup 
was made.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: deja-dup 34.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Oct 24 18:09:40 2016
InstallationDate: Installed on 2014-04-23 (914 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
SourcePackage: deja-dup
UpgradeStatus: Upgraded to xenial on 2016-07-31 (85 days ago)

** Affects: deja-dup (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  The "restore-missing" functionality is not working as expected

Status in deja-dup package in Ubuntu:
  New

Bug description:
  I have found out that the "--restore-missing" functionality is not working as 
expected.
  I have set up déja-dup to backup some folders every day.

  If I delete some files today, and then I use the "restore-missing"
  functionality the same day (today in my example), déja-dup shows me
  the list of missing files as expected.

  The problem is that if I use the "restore-missing" functionality from 
tomorrow on, no files are listed anymore. It seems that "restore-missing" seeks 
the missing files only if the backup is made the same day that I deleted the 
files.
  The behavior I expected is that "restore-missing" should search the entire 
backup series, and create a list of all missing files since the first backup 
was made.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: deja-dup 34.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 24 18:09:40 2016
  InstallationDate: Installed on 2014-04-23 (914 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to xenial on 2016-07-31 (85 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1636255/+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 1636249] [NEW] Drop patches from 3.22.0-1ubuntu1 that aren't needed with GNOME 3.22

2016-10-24 Thread Iain Lane

Public bug reported:

There are two patches

  git_revert_gtksourceview322.patch

and

  git_revert_gtk322.patch

that revert upstream changes to depend on parts of new GNOME.

We have those parts in Zesty now, so the patches can probably be
dropped.

Investigate if that is true and provide a branch which does this, after
testing the packages.

** Affects: gedit (Ubuntu)
 Importance: Undecided
 Assignee: F.J Kong (fjkong)
 Status: New

** Changed in: gedit (Ubuntu)
 Assignee: (unassigned) => F.J Kong (fjkong)

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

Title:
  Drop patches from 3.22.0-1ubuntu1 that aren't needed with GNOME 3.22

Status in gedit package in Ubuntu:
  New

Bug description:
  There are two patches

git_revert_gtksourceview322.patch

  and

git_revert_gtk322.patch

  that revert upstream changes to depend on parts of new GNOME.

  We have those parts in Zesty now, so the patches can probably be
  dropped.

  Investigate if that is true and provide a branch which does this,
  after testing the packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1636249/+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 1636248] [NEW] totem not running videos at all, actually crashing

2016-10-24 Thread Antonio Mihovilovic

Public bug reported:

Totem not opening videos at all. Attempts to open it but nothing
happens.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: totem 3.10.1-1ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-45.66~14.04.1-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Oct 24 18:24:17 2016
InstallationDate: Installed on 2015-10-05 (384 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
SourcePackage: totem
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

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

Title:
  totem not running videos at all, actually crashing

Status in totem package in Ubuntu:
  New

Bug description:
  Totem not opening videos at all. Attempts to open it but nothing
  happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: totem 3.10.1-1ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-45.66~14.04.1-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 24 18:24:17 2016
  InstallationDate: Installed on 2015-10-05 (384 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1636248/+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 1567578] Re: libnl should be updated to support up to 63 VFs per single PF

2016-10-24 Thread Louis Bouchard

** Tags added: sts-sru

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

Title:
   libnl should be updated to support up to 63 VFs per single PF

Status in libnl3 package in Ubuntu:
  Fix Released
Status in libnl3 source package in Precise:
  New
Status in libnl3 source package in Trusty:
  In Progress

Bug description:
  [Description]

  Ubuntu 14.04.4 and SRIOV settings.

  As already documented in https://bugs.launchpad.net/mos/+bug/1501738
  there is a bug in the default libnl library release installed on
  Ubuntu 14.04.4

  When trying to enable a guest with more than 30 VFs attached, the
  following error is returned:

  error: Failed to start domain guest1
  error: internal error: missing IFLA_VF_INFO in netlink response

  [Impact]

  The library release is the 3.2.21-1 the bug is impacting on the
  maximum VFs number that can be enabled (up to 30) even if the PF
  supports up to 63 VFs in an Openstack SRIOV configuration

  [Test Case]

  The sequence to reproduce this bug is:

  1) Edit /etc/default/grub

  GRUB_CMDLINE_LINUX="intel_iommu=on ixgbe.max_vfs=63"

  2) $ sudo update-grub

  ### Reboot the machine.

  3) Check that the virtual functions are available:

  $ sudo lspci|grep -i eth | grep -i virtual | wc -l
  126

  4) Create a KVM guest

  $ sudo uvt-kvm create guest1 release=trusty

  5) List the VF devices :

  $ sudo lspci|grep -i eth | grep -i virtual | awk '{print $1}' | sed
  's/\:/\_/g' | sed 's/\./\_/g' > devices.txt

  6) Get the libvirt node device:

  $ sudo for device in $(cat ./devices.txt); do virsh nodedev-list |
  grep $device; done > pci_devices.txt

  7) Generate the XML config for each device:

  $ sudo mkdir devices && for d in $(cat pci_devices.txt); do virsh
  nodedev-dumpxml $d > devices/$d.xml; done

  8) Save and Run the following script
  (http://pastebin.ubuntu.com/23374186/)

  $ sudo python generate-interfaces.py |grep address | wc -l

  9) Finally attach the devices to the guest.

  $ sudo for i in $(seq 0 63); do virsh attach-device guest1 
./interfaces/$i.xml --config; done
  Device attached successfully
  [...]

  Device attached successfully
  Device attached successfully

  10) Then destroy/start the guest again, at this point the error is
  reproduced.

  $ sudo virsh destroy guest1
  Domain guest1 destroyed

  $ sudo virsh start guest1

  error: Failed to start domain guest1
  error: internal error: missing IFLA_VF_INFO in netlink response

   * detailed instructions how to reproduce the bug

   * these should allow someone who is not familiar with the affected
 package to reproduce the bug and verify that the updated package fixes
 the problem.

  [Regression Potential]

   ** None identified.

  [Other Info]

  - Redhat Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1040626

  [Workaround]

  The workaround is to install a newer library release, the 3.2.24-2:

  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-3-200_3.2.24-2_amd64.deb
  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-genl-3-200_3.2.24-2_amd64.deb
  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-route-3-200_3.2.24-2_amd64.deb
  dpkg -i libnl-3-200_3.2.24-2_amd64.deb
  dpkg -i libnl-genl-3-200_3.2.24-2_amd64.deb
  dpkg -i libnl-route-3-200_3.2.24-2_amd64.deb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1567578/+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 1635831] Re: How to turn bluetooth off by default

2016-10-24 Thread Gunnar Hjalmarsson

That's not how it's supposed to work AFAICT, and I can't reproduce it,
so this is reasonably not a documentation matter.

Changed the affected package to unity-control-center and reworded the
title.

** Package changed: ubuntu-docs (Ubuntu) => unity-control-center
(Ubuntu)

** Changed in: unity-control-center (Ubuntu)
   Status: Incomplete => New

** Summary changed:

- How to turn bluetooth off by default
+ Bluetooth does not stay turned off after reboot

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

Title:
  Bluetooth does not stay turned off after reboot

Status in unity-control-center package in Ubuntu:
  New

Bug description:
  I want to turn bluetooth off by default, because it is a very rare use
  case that I need it.

  I go and look at the bluetooth documentation to find out how to do
  this.

  The bluetooth documentation does not contain instructions on how to
  turn bluetooth off by default.

  https://help.ubuntu.com/stable/ubuntu-help/bluetooth-turn-on-off.html

  I do understand how to click an on/off button, but not how to turn it
  off by default, I would expect instructions on how to do that. The
  docs itself hint that it is a smart thing to turn bluetooth off to
  conserve power.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1635831/+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 1635831] [NEW] How to turn bluetooth off by default

You have been subscribed to a public bug:

I want to turn bluetooth off by default, because it is a very rare use
case that I need it.

I go and look at the bluetooth documentation to find out how to do this.

The bluetooth documentation does not contain instructions on how to turn
bluetooth off by default.

https://help.ubuntu.com/stable/ubuntu-help/bluetooth-turn-on-off.html

I do understand how to click an on/off button, but not how to turn it
off by default, I would expect instructions on how to do that. The docs
itself hint that it is a smart thing to turn bluetooth off to conserve
power.

** Affects: unity-control-center (Ubuntu)
 Importance: Undecided
 Status: New

-- 
How to turn bluetooth off by default
https://bugs.launchpad.net/bugs/1635831
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to unity-control-center 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 1560162] Re: Xenial: scaling is horribly out on xps13 install session

2016-10-24 Thread Mathieu Trudel-Lapierre

This still needs verification. You would want to use 'break=bottom' on
the command-line when booting to stop before ubiquity starts, then
chroot into the system and apt-get install the new ubiquity to test
this.

The bug that was automatically found isn't a regression of this fix but
an issue with debconf-apt-progress unrelated to the problem at hand.

** Tags removed: verification-failed

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

Title:
  Xenial: scaling is horribly out on xps13 install session

Status in OEM Priority Project:
  New
Status in metacity package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in metacity source package in Xenial:
  Fix Released
Status in ubiquity source package in Xenial:
  Fix Committed

Bug description:
  STEPS:
  Requirements laptop desktop with a hidpi screen (Here xps 13)
  1. Grab the latest daily image and trigger an install
  2. On the first page notice the of centre and over scaled window

  EXPECTED:
  I expect to see something resembling a normal scaled desktop install

  ACTUAL:
  Things are not quite correct see attached screenshots

  ubiquity/xenial 2.21.49 amd64

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1560162/+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 1636222] [NEW] unrecognized disk space

2016-10-24 Thread Carlos

Public bug reported:

The system cannot see 497 GB of disk space and displays a no space
message. This is not true, most of the SSD is unused.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Oct 24 10:42:17 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660G] [1002:9900] 
(prog-if 00 [VGA controller])
   Subsystem: Toshiba America Info Systems Trinity [Radeon HD 7660G] [1179:fb43]
InstallationDate: Installed on 2016-07-02 (114 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: TOSHIBA Satellite L875D
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/02/2012
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 6.10
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: PLCSC8
dmi.board.vendor: AMD
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.10:bd10/02/2012:svnTOSHIBA:pnSatelliteL875D:pvrPSKFQU-008003:rvnAMD:rnPLCSC8:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: Satellite L875D
dmi.product.version: PSKFQU-008003
dmi.sys.vendor: TOSHIBA
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
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.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Mon Oct 24 10:36:37 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.1
xserver.video_driver: radeon

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


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

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

Title:
  unrecognized disk space

Status in xorg package in Ubuntu:
  New

Bug description:
  The system cannot see 497 GB of disk space and displays a no space
  message. This is not true, most of the SSD is unused.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Oct 24 10:42:17 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660G] [1002:9900] 
(prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Trinity [Radeon HD 7660G] 
[1179:fb43]
  InstallationDate: Installed on 2016-07-02 (114 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: TOSHIBA Satellite L875D
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/02/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.10
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: PLCSC8
  dmi.board.vendor: AMD
  dmi.board.version: Base Board Ve

[Desktop-packages] [Bug 1630453] Re: [Yakkety +1] Sync lirc 0.9.4b-0.1 (main) from Debian experimental (main)

2016-10-24 Thread LocutusOfBorg

Graham syncd it, and it built correctly

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

Title:
  [Yakkety +1] Sync lirc 0.9.4b-0.1 (main) from Debian experimental
  (main)

Status in lirc package in Ubuntu:
  Fix Released

Bug description:
  [Yakkety +1] Please sync lirc 0.9.4b-0.1 (main) from Debian
  experimental (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* Multiarchify the library packages.
* Multiarchify the library packages.
* debian/lirc.postinst, debian/lirc.templates, debian/po: drop a number of
  debconf templates that are no longer being prompted for at all due to
  the dropping of the lirc-modules-source package and the lirc.config some
  time ago.
* debian/lirc.postinst: clean up the remaining debconf handling to not
  override settings in /etc/lirc/hardware.conf.
* debian/lirc.postinst: drop code for removing /var/log/lircd, which has
  been gone for more than a decade.
* fix blacklist handling, which creates files not used by modprobe, and
  doesn't put all the contents in a single file.
* drop obsolete Ubuntu migration code that dates from jaunty and lucid.
* fix a bug that causes transmitter device/driver settings to always be
  cleared on config change.
* Adjust lircd handling for multiple devices so that events for all of
  them will appear on /dev/lircd as intended.  Thanks to Joel Ebel for
  the patch.  LP: #697999.
* Use /run/lirc, the canonical name for /var/run/lirc.  LP: #474701.
* Fix the init script to not report failures when stopping an
  already-stopped daemon.
* debian/lirc.postinst, debian/lirc.templates, debian/po: drop a number of
  debconf templates that are no longer being prompted for at all due to
  the dropping of the lirc-modules-source package and the lirc.config some
  time ago.
* debian/lirc.postinst: clean up the remaining debconf handling to not
  override settings in /etc/lirc/hardware.conf.
* debian/lirc.postinst: drop code for removing /var/log/lircd, which has
  been gone for more than a decade.
* fix blacklist handling, which creates files not used by modprobe, and
  doesn't put all the contents in a single file.
* drop obsolete Ubuntu migration code that dates from jaunty and lucid.
* fix a bug that causes transmitter device/driver settings to always be
  cleared on config change.
* Adjust lircd handling for multiple devices so that events for all of
  them will appear on /dev/lircd as intended.  Thanks to Joel Ebel for
  the patch.  LP: #697999.
* Use /run/lirc, the canonical name for /var/run/lirc.  LP: #474701.
* Fix the init script to not report failures when stopping an
  already-stopped daemon.
* debian/lirc.postinst, debian/lirc.templates, debian/po: drop a number of
  debconf templates that are no longer being prompted for at all due to
  the dropping of the lirc-modules-source package and the lirc.config some
  time ago.
* debian/lirc.postinst: clean up the remaining debconf handling to not
  override settings in /etc/lirc/hardware.conf.
* debian/lirc.postinst: drop code for removing /var/log/lircd, which has
  been gone for more than a decade.
* fix blacklist handling, which creates files not used by modprobe, and
  doesn't put all the contents in a single file.
* drop obsolete Ubuntu migration code that dates from jaunty and lucid.
* fix a bug that causes transmitter device/driver settings to always be
  cleared on config change.
* Adjust lircd handling for multiple devices so that events for all of
  them will appear on /dev/lircd as intended.  Thanks to Joel Ebel for
  the patch.  LP: #697999.
* Use /run/lirc, the canonical name for /var/run/lirc.  LP: #474701.
* Fix the init script to not report failures when stopping an
  already-stopped daemon.
* debian/lirc.postinst, debian/lirc.templates, debian/po: drop a number of
  debconf templates that are no longer being prompted for at all due to
  the dropping of the lirc-modules-source package and the lirc.config some
  time ago.
* debian/lirc.postinst: clean up the remaining debconf handling to not
  override settings in /etc/lirc/hardware.conf.
* debian/lirc.postinst: drop code for removing /var/log/lircd, which has
  been gone for more than a decade.
* fix blacklist handling, which creates files not used by modprobe, and
  doesn't put all the contents in a single file.
* drop obsolete Ubuntu migration code that dates from jaunty and lucid.
* fix a bug that causes transmitter device/driver settings to always be
  cleared on config change.
* Adjust lircd handling for multiple devices so that events for all of
  them will appear on /dev/lircd as intended.  Thanks to

[Desktop-packages] [Bug 1612343] Re: Unable to delete large folders in Trash

2016-10-24 Thread Nikita Yerenkov-Scott

** Changed in: ubuntu-gnome
   Status: New => Confirmed

** Tags added: yakkety

** Project changed: nautilus => gvfs

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

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

Title:
  Unable to delete large folders in Trash

Status in gvfs:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in gvfs package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  I have found that since the indicator of file operations was replaced
  with the notification coming from the right of the top bar rather than
  a popup window, that I am unable to delete large folders from Trash.
  Placing them in Trash sometimes means that other items (even really
  small ones) can't be deleted until the large folders have been moved
  from Trash to another location, though on other occasions all, or at
  least half, of the other files will be seemingly successfully deleted,
  though not the large folder(s).

  For instance I have a folder with many sub-folders, which each have
  many sub-sub-folders etc and lots of files... The folder's file size
  is about 1.7GB. I tried creating a tar of the file which was 1.8GB, I
  moved that into Trash and it was deleted within about a second with no
  trouble at all so it seems only to be folders.

  I looked at the properties for a large folder I placed in Trash by
  itself, and even though I had clicked the Empty Trash button many
  times now, it was staying at the same size.

  I find that the indicator which is meant to be indicating how it's
  doing to me is always just stuck at "Preparing", even when it actually
  deletes stuff it only ever really shows that so is not very useful.

  I am running Ubuntu GNOME 16.04 with GNOME 3.20, but I believe this
  was also present in 3.18, though not to such a bad degree (pressing
  the Empty Trash button many times in some cases eventually worked on
  3.18, but on 3.20 I can't seem to do anything to delete the folder
  without first splitting it up).

  One thing to note though is that if I am to use the right-click option
  to permanently delete files and folders (which can be enabled in the
  Preferences) then it deletes them just fine apart from showing a huge
  and negative amount of files per seconds, but that is for another bug
  report.

  I have only tested this in Nautilus, I have not yet tested if it works
  better in a different file manager, I will comment when I have tested
  it with a different file manager.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/1612343/+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 1612380] Re: Huge unrealistic amount of hours to go shown after successfully moving file/folder

2016-10-24 Thread Nikita Yerenkov-Scott

** Changed in: ubuntu-gnome
   Status: New => Confirmed

** Tags added: yakkety

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

Title:
  Huge unrealistic amount of hours to go shown after successfully moving
  file/folder

Status in Nautilus:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  For instance I was moving a folder today using Nautilus which told me
  it would take 5 minutes to move, and it did, the time to completion
  was actually very accurate, until it finished, at which point it
  suddenly jumped to this even though it had already succeed in moving
  the folder in the time it had promised. I see this happen reasonably
  often. I am running Ubuntu GNOME 16.04 with GNOME 3.20.

  I have attached a screenshot of what I mean.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1612380/+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 1567578] Re: libnl should be updated to support up to 63 VFs per single PF

** Patch added: "fix-1567578-trusty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1567578/+attachment/4766476/+files/fix-1567578-trusty.debdiff

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

Title:
   libnl should be updated to support up to 63 VFs per single PF

Status in libnl3 package in Ubuntu:
  Fix Released
Status in libnl3 source package in Precise:
  New
Status in libnl3 source package in Trusty:
  In Progress

Bug description:
  [Description]

  Ubuntu 14.04.4 and SRIOV settings.

  As already documented in https://bugs.launchpad.net/mos/+bug/1501738
  there is a bug in the default libnl library release installed on
  Ubuntu 14.04.4

  When trying to enable a guest with more than 30 VFs attached, the
  following error is returned:

  error: Failed to start domain guest1
  error: internal error: missing IFLA_VF_INFO in netlink response

  [Impact]

  The library release is the 3.2.21-1 the bug is impacting on the
  maximum VFs number that can be enabled (up to 30) even if the PF
  supports up to 63 VFs in an Openstack SRIOV configuration

  [Test Case]

  The sequence to reproduce this bug is:

  1) Edit /etc/default/grub

  GRUB_CMDLINE_LINUX="intel_iommu=on ixgbe.max_vfs=63"

  2) $ sudo update-grub

  ### Reboot the machine.

  3) Check that the virtual functions are available:

  $ sudo lspci|grep -i eth | grep -i virtual | wc -l
  126

  4) Create a KVM guest

  $ sudo uvt-kvm create guest1 release=trusty

  5) List the VF devices :

  $ sudo lspci|grep -i eth | grep -i virtual | awk '{print $1}' | sed
  's/\:/\_/g' | sed 's/\./\_/g' > devices.txt

  6) Get the libvirt node device:

  $ sudo for device in $(cat ./devices.txt); do virsh nodedev-list |
  grep $device; done > pci_devices.txt

  7) Generate the XML config for each device:

  $ sudo mkdir devices && for d in $(cat pci_devices.txt); do virsh
  nodedev-dumpxml $d > devices/$d.xml; done

  8) Save and Run the following script
  (http://pastebin.ubuntu.com/23374186/)

  $ sudo python generate-interfaces.py |grep address | wc -l

  9) Finally attach the devices to the guest.

  $ sudo for i in $(seq 0 63); do virsh attach-device guest1 
./interfaces/$i.xml --config; done
  Device attached successfully
  [...]

  Device attached successfully
  Device attached successfully

  10) Then destroy/start the guest again, at this point the error is
  reproduced.

  $ sudo virsh destroy guest1
  Domain guest1 destroyed

  $ sudo virsh start guest1

  error: Failed to start domain guest1
  error: internal error: missing IFLA_VF_INFO in netlink response

   * detailed instructions how to reproduce the bug

   * these should allow someone who is not familiar with the affected
 package to reproduce the bug and verify that the updated package fixes
 the problem.

  [Regression Potential]

   ** None identified.

  [Other Info]

  - Redhat Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1040626

  [Workaround]

  The workaround is to install a newer library release, the 3.2.24-2:

  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-3-200_3.2.24-2_amd64.deb
  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-genl-3-200_3.2.24-2_amd64.deb
  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-route-3-200_3.2.24-2_amd64.deb
  dpkg -i libnl-3-200_3.2.24-2_amd64.deb
  dpkg -i libnl-genl-3-200_3.2.24-2_amd64.deb
  dpkg -i libnl-route-3-200_3.2.24-2_amd64.deb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1567578/+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 1567578] Re: libnl should be updated to support up to 63 VFs per single PF

Hello,

After running a bisect between tags libnl3_2_21 and libnl3_2_22 I identified
the fixer commit to be 807fddc nl: Increase receive buffer size to 4 pages

commit 807fddc4cd9ecb12ba64e1b7fa26d86b6c2f19b0
Author: Thomas Graf 
Date:   Wed May 8 13:52:27 2013 +0200

nl: Increase receive buffer size to 4 pages

Assuming that the kernel does not send more than a page is no longer valid,
and enabling MSG_PEEK'ing by default to figure out the exact message buffer
requirements can have a negative influence on the performance of existing
applications. Bumping the default receive buffer space to 4 pages seems
a sane default.

Signed-off-by: Thomas Graf 

---

After applying this patch on top of the current trusty-updates this problem
is not longer exhibited and I can attach the full 128 VFs to the guest.

I am proposing this patch for SRU, and I already updated the description
with the reproduction steps.

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

Title:
   libnl should be updated to support up to 63 VFs per single PF

Status in libnl3 package in Ubuntu:
  Fix Released
Status in libnl3 source package in Precise:
  New
Status in libnl3 source package in Trusty:
  In Progress

Bug description:
  [Description]

  Ubuntu 14.04.4 and SRIOV settings.

  As already documented in https://bugs.launchpad.net/mos/+bug/1501738
  there is a bug in the default libnl library release installed on
  Ubuntu 14.04.4

  When trying to enable a guest with more than 30 VFs attached, the
  following error is returned:

  error: Failed to start domain guest1
  error: internal error: missing IFLA_VF_INFO in netlink response

  [Impact]

  The library release is the 3.2.21-1 the bug is impacting on the
  maximum VFs number that can be enabled (up to 30) even if the PF
  supports up to 63 VFs in an Openstack SRIOV configuration

  [Test Case]

  The sequence to reproduce this bug is:

  1) Edit /etc/default/grub

  GRUB_CMDLINE_LINUX="intel_iommu=on ixgbe.max_vfs=63"

  2) $ sudo update-grub

  ### Reboot the machine.

  3) Check that the virtual functions are available:

  $ sudo lspci|grep -i eth | grep -i virtual | wc -l
  126

  4) Create a KVM guest

  $ sudo uvt-kvm create guest1 release=trusty

  5) List the VF devices :

  $ sudo lspci|grep -i eth | grep -i virtual | awk '{print $1}' | sed
  's/\:/\_/g' | sed 's/\./\_/g' > devices.txt

  6) Get the libvirt node device:

  $ sudo for device in $(cat ./devices.txt); do virsh nodedev-list |
  grep $device; done > pci_devices.txt

  7) Generate the XML config for each device:

  $ sudo mkdir devices && for d in $(cat pci_devices.txt); do virsh
  nodedev-dumpxml $d > devices/$d.xml; done

  8) Save and Run the following script
  (http://pastebin.ubuntu.com/23374186/)

  $ sudo python generate-interfaces.py |grep address | wc -l

  9) Finally attach the devices to the guest.

  $ sudo for i in $(seq 0 63); do virsh attach-device guest1 
./interfaces/$i.xml --config; done
  Device attached successfully
  [...]

  Device attached successfully
  Device attached successfully

  10) Then destroy/start the guest again, at this point the error is
  reproduced.

  $ sudo virsh destroy guest1
  Domain guest1 destroyed

  $ sudo virsh start guest1

  error: Failed to start domain guest1
  error: internal error: missing IFLA_VF_INFO in netlink response

   * detailed instructions how to reproduce the bug

   * these should allow someone who is not familiar with the affected
 package to reproduce the bug and verify that the updated package fixes
 the problem.

  [Regression Potential]

   ** None identified.

  [Other Info]

  - Redhat Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1040626

  [Workaround]

  The workaround is to install a newer library release, the 3.2.24-2:

  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-3-200_3.2.24-2_amd64.deb
  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-genl-3-200_3.2.24-2_amd64.deb
  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-route-3-200_3.2.24-2_amd64.deb
  dpkg -i libnl-3-200_3.2.24-2_amd64.deb
  dpkg -i libnl-genl-3-200_3.2.24-2_amd64.deb
  dpkg -i libnl-route-3-200_3.2.24-2_amd64.deb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1567578/+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 1635973] Re: "Disks" can't erase data in a Memory Card

2016-10-24 Thread MadhuSoodanan

** Changed in: gnome-disk-utility (Ubuntu)
   Status: Confirmed => Opinion

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

Title:
  "Disks" can't erase data in a Memory Card

Status in gnome-disk-utility package in Ubuntu:
  Opinion

Bug description:
  I couldn't see the collected report for this bug. So sending this
  duplicate.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-disk-utility 3.18.3.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic i686
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sun Oct 23 19:45:14 2016
  InstallationDate: Installed on 2016-10-15 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  SourcePackage: gnome-disk-utility
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1635973/+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

Re: [Desktop-packages] [Bug 1636005] Re: Writer does not perform spelling checking of documents

2016-10-24 Thread Ian Bruntlett

Using a DVD-R of Ubuntu 16.04 LTS 64-bit, I installed the operating system
on evesham tower PC.

Used LibreOffice Writer - spelling checking not working.
Ran Software Updater.
Used LibreOffice Writer - spelling checking not working.
Installed hunspell-en-gb
Used LibreOffice Writer - spelling checking now working.

-- 
-- ACCU - Professionalism in programming - http://www.accu.org
-- My writing - https://sites.google.com/site/ianbruntlett/
-- Free Software page -
https://sites.google.com/site/ianbruntlett/home/free-software

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

Title:
  Writer does not perform spelling checking of documents

Status in libreoffice package in Ubuntu:
  Invalid

Bug description:
  Not sure what caused this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-writer 1:5.1.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 23 19:38:10 2016
  InstallationDate: Installed on 2016-04-28 (178 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1636005/+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 1636204] Re: GTK 3.22 is incompatible with Nautilus 3.20

After testing nautilus 3.20.3 with GTK 3.22, things work ok. I guess it
was just caja 1.14 that had this problem but we have caja 1.16 now.

** Changed in: gtk+3.0 (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  GTK 3.22 is incompatible with Nautilus 3.20

Status in gtk+3.0 package in Ubuntu:
  Invalid

Bug description:
  Nautilus 3.20 will crash with GTK 3.22 because it uses internal
  unstable GTK API as I understand it. We either need to upload Nautilus
  3.22 ( see bug 1635988 ) or backport the GTK 3.22 compatibility
  commits.

  For now, I'm setting block-proposed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1636204/+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 1636204] [NEW] GTK 3.22 is incompatible with Nautilus 3.20

Public bug reported:

Nautilus 3.20 will crash with GTK 3.22 because it uses internal unstable
GTK API as I understand it. We either need to upload Nautilus 3.22 ( see
bug 1635988 ) or backport the GTK 3.22 compatibility commits.

For now, I'm setting block-proposed.

** Affects: gtk+3.0 (Ubuntu)
 Importance: Critical
 Status: Invalid


** Tags: block-proposed zesty

** Description changed:

- Nautilus 3.20 will crash with GTK 3.22. We either need to upload
- Nautilus 3.22 ( see bug 1635988 ) or backport the GTK 3.22 compatibility
- commits.
+ Nautilus 3.20 will crash with GTK 3.22 because it uses internal unstable
+ GTK API as I understand it. We either need to upload Nautilus 3.22 ( see
+ bug 1635988 ) or backport the GTK 3.22 compatibility commits.
  
  For now, I'm setting block-proposed.

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

Title:
  GTK 3.22 is incompatible with Nautilus 3.20

Status in gtk+3.0 package in Ubuntu:
  Invalid

Bug description:
  Nautilus 3.20 will crash with GTK 3.22 because it uses internal
  unstable GTK API as I understand it. We either need to upload Nautilus
  3.22 ( see bug 1635988 ) or backport the GTK 3.22 compatibility
  commits.

  For now, I'm setting block-proposed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1636204/+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 1478319] Re: Wifi doesn't reconnect to AP if it uses the same SSID than another AP

2016-10-24 Thread Alfonso Sanchez-Beato

Reproduced on bq 4.5, OTA13. I created two APs with SSID "Ubuntu", same
password, same authentication. I connected to one of them:

phablet@ubuntu-phablet:~$ nmcli d wifi
*  SSIDMODE   CHAN  RATE   SIGNAL  BARS  SECURITY   
  
   Ubuntu  Infra  1 54 Mbit/s  100   WPA2
*  Ubuntu  Infra  1154 Mbit/s  91    WPA2

phablet@ubuntu-phablet:~$ ifconfig wlan0
wlan0 Link encap:Ethernet  direcciónHW b8:64:91:47:21:b6  
  Direc. inet:192.168.43.189  Difus.:192.168.43.255  Másc:255.255.255.0
  ...

Then I removed the AP in channel 11. After waiting for some minutes to
make sure we had re-scanned:

phablet@ubuntu-phablet:~$ nmcli d wifi
*  SSID   MODE   CHAN  RATE   SIGNAL  BARS  SECURITY  
*  Ubuntu Infra  1 54 Mbit/s  88    WPA2  

It looks like the connection has moved to the other Ubuntu AP, but ping
does not work, and the interface address has not changed:

phablet@ubuntu-phablet:~$ ifconfig wlan0
wlan0 Link encap:Ethernet  direcciónHW b8:64:91:47:21:b6  
  Direc. inet:192.168.43.189  Difus.:192.168.43.255  Másc:255.255.255.0
  ...

Apparently the IP configuration has not completed properly. I was able
to return to a working state by doing

phablet@ubuntu-phablet:~$ nmcli d wifi connect Ubuntu

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

Title:
  Wifi doesn't reconnect to AP if it uses the same SSID than another AP

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

Bug description:
  current build number: 68
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-07-24 08:00:20
  version version: 68
  version ubuntu: 20150724
  version device: 20150709-8965e37
  version custom: 20150716-819-8-42

  My ISP (Free in France) provides a hotspot service so that customers
  can use the connection of any other customer using a generic open Wifi
  connection (for reference http://www.free.fr/assistance/2303.html - in
  French)

  The SSID is called 'FreeWifi' on all the boxes but obviously APs are
  all different since it's customers' DSL routers.

  When I connect  to one of this access point, suspend the phone and
  resume it in another location where the SSID is available but from a
  different AP, the phone doesn't connect to this AP and the list of
  networks in the network-indicator doesn't refresh and still show the
  list of network from the previous location. I have to forget the
  network called 'FreeWifi' and reconnect in order to refresh the list
  and make it work.

  It's 100% reproducible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1478319/+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 1118903] Re: [enhancement] Mir lacks a software rendering backend (and doesn't work in virtual machines)

2016-10-24 Thread Emanuele Antonio Faraone

News?

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

Title:
  [enhancement] Mir lacks a software rendering backend (and doesn't work
  in virtual machines)

Status in Canonical System Image:
  New
Status in Mir:
  Triaged
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Triaged

Bug description:
  As always, it's a critical requirement for Ubuntu to be able to render
  the same thing on any machine (metal or virtual), regardless of the
  availability of hardware acceleration.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1118903/+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 1518595] Re: support host-uniq tag

2016-10-24 Thread Matteo Croce

Actually it's merged into Debian, you can simply update the package:

  * PPPoE: permit setting an arbitrary Host-Uniq field value:
add patch pr-28-pppoe-custom-host-uniq-tag.patch (Closes: #828968)

http://metadata.ftp-
master.debian.org/changelogs/main/p/ppp/ppp_2.4.7-1+3_changelog

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

Title:
  support host-uniq tag

Status in ppp package in Ubuntu:
  New

Bug description:
  This patch is needed to connect to some ISPs that require a specific
  tag to connect,

  please merge

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ppp/+bug/1518595/+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 861642] Re: upowerd uses 100% cpu till killed

2016-10-24 Thread flo-54321

I can confirm the observation of ally (#8).

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

Title:
  upowerd uses 100% cpu till killed

Status in upower package in Ubuntu:
  Confirmed

Bug description:
  top - 12:57:54 up  2:56,  3 users,  load average: 1.06, 1.12, 1.35
  Tasks: 219 total,   2 running, 216 sleeping,   0 stopped,   1 zombie
  Cpu0  : 70.2%us, 29.8%sy,  0.0%ni,  0.0%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
  Cpu1  :  2.3%us,  1.3%sy,  0.0%ni, 96.4%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
  Cpu2  :  1.0%us,  0.3%sy,  0.0%ni, 98.7%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
  Cpu3  :  0.7%us,  1.6%sy,  0.0%ni, 97.7%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
  Cpu4  :  0.0%us,  0.3%sy,  0.0%ni, 99.7%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
  Cpu5  :  0.0%us,  0.3%sy,  0.0%ni, 98.3%id,  1.4%wa,  0.0%hi,  0.0%si,  0.0%st
  Mem:   5994176k total,  4198260k used,  1795916k free,63308k buffers
  Swap:  8193144k total,   355188k used,  7837956k free,   334316k cached

PID USER  PR  NI  VIRT  RES  SHR S %CPU %MEMTIME+  COMMAND  
  
   2268 root  20   0  148m 1572  680 R  100  0.0 111:08.37 upowerd

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: upower 0.9.9-4
  ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8
  Uname: Linux 2.6.38-11-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Wed Sep 28 12:53:23 2011
  ExecutablePath: /usr/lib/upower/upowerd
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  ProcEnviron:
   
  SourcePackage: upower
  UpgradeStatus: Upgraded to natty on 2011-04-06 (175 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/861642/+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 1478319] Re: Wifi doesn't reconnect to AP if it uses the same SSID than another AP

2016-10-24 Thread Alfonso Sanchez-Beato

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

** Changed in: network-manager (Ubuntu)
   Status: Expired => 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/1478319

Title:
  Wifi doesn't reconnect to AP if it uses the same SSID than another AP

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

Bug description:
  current build number: 68
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-07-24 08:00:20
  version version: 68
  version ubuntu: 20150724
  version device: 20150709-8965e37
  version custom: 20150716-819-8-42

  My ISP (Free in France) provides a hotspot service so that customers
  can use the connection of any other customer using a generic open Wifi
  connection (for reference http://www.free.fr/assistance/2303.html - in
  French)

  The SSID is called 'FreeWifi' on all the boxes but obviously APs are
  all different since it's customers' DSL routers.

  When I connect  to one of this access point, suspend the phone and
  resume it in another location where the SSID is available but from a
  different AP, the phone doesn't connect to this AP and the list of
  networks in the network-indicator doesn't refresh and still show the
  list of network from the previous location. I have to forget the
  network called 'FreeWifi' and reconnect in order to refresh the list
  and make it work.

  It's 100% reproducible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1478319/+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 1635050] Re: Some panel icons disappear after turning display off/on

2016-10-24 Thread Gaston

I have the same problem with the Mega icon.

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

Title:
  Some panel icons disappear after turning display off/on

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When I boot into Ubuntu all panel icons are ok, but after turning the
  screen off (closing lid) and on again some icons disappear and get
  replaced with some generic "missing" icons.

  This happens with Mega and Bitmask icons but the applications still
  work. And if i quit one of those two apps the icon of another appears
  again.

  before:
  https://drive.google.com/open?id=0B4b2sRiO8XlMUkJDWTR0a0ptcFk

  after:
  https://drive.google.com/open?id=0B4b2sRiO8XlMcHRMQzJmbm90azQ

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:04:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.57  Mon Oct  3 20:37:01 
PDT 2016
   GCC version:  gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Oct 19 23:09:11 2016
  DistUpgraded: 2016-10-18 09:22:45,469 DEBUG icon theme changed, re-reading
  DistroCodename: yakkety
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics 
Controller [1043:13ad]
 Subsystem: ASUSTeK Computer Inc. GeForce GT 730M [1043:13ad]
  InstallationDate: Installed on 2015-08-20 (426 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: ASUSTeK COMPUTER INC. UX302LG
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-22-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to yakkety on 2016-10-18 (1 days ago)
  dmi.bios.date: 06/16/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX302LG.210
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX302LG
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX302LG.210:bd06/16/2014:svnASUSTeKCOMPUTERINC.:pnUX302LG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX302LG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX302LG
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Wed Oct 19 19:43:23 2016
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1635050/+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 1636190] [NEW] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] ERROR CPU pipe A FIFO underrun

2016-10-24 Thread Felix Oxley

Public bug reported:

Hi,

since upgrading to Yakety I have been experiencing occasional loss of
display (black screen) lasting for usually 2 seconds (although yesterday
(23rd Oct) the display did not return).

Today, I found the following message in my syslog shortly after the
incident.

[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO
underrun

I have experienced this issue on my installed OS and also with a live cd.
Issue has occurred with both HDMI & DP connection to monitor.

Hardware is Intel i5-6600 with HD Graphics 530 (Skylake GT2)
Display is 27" 2560x1440.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
BootLog: /dev/sda3: clean, 489873/2501856 files, 3817177/1128 blocks
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Mon Oct 24 13:35:32 2016
DistUpgraded: 2016-10-15 14:21:59,278 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
DistroCodename: yakkety
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: ASRock Incorporation HD Graphics 530 [1849:1912]
InstallationDate: Installed on 2015-10-16 (373 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20151016)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-26-generic.efi.signed 
root=UUID=385391c1-3d07-42b8-9747-e10f79512db8 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to yakkety on 2016-10-15 (8 days ago)
dmi.bios.date: 07/25/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.30
dmi.board.name: Z170 Gaming-ITX/ac
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.:bvrP2.30:bd07/25/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ170Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
xserver.bootTime: Thu Apr 21 23:53:21 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.17.2-1ubuntu9.1

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


** Tags: amd64 apport-bug ubuntu yakkety

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

Title:
  [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A
  FIFO underrun

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi,

  since upgrading to Yakety I have been experiencing occasional loss of
  display (black screen) lasting for usually 2 seconds (although
  yesterday (23rd Oct) the display did not return).

  Today, I found the following message in my syslog shortly after the
  incident.

  [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A
  FIFO underrun

  I have experienced this issue on my installed OS and also with a live cd.
  Issue has occurred with both HDMI & DP connection to monitor.

  Hardware is Intel i5-6600 with HD Graphics 530 (Skylake GT2)
  Display is 27" 2560x1440.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  BootLog: /dev/sda3: clean, 489873/2501856 files, 3817177/1128 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None

[Desktop-packages] [Bug 1635050] Re: Some panel icons disappear after turning display off/on

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

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

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

Title:
  Some panel icons disappear after turning display off/on

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When I boot into Ubuntu all panel icons are ok, but after turning the
  screen off (closing lid) and on again some icons disappear and get
  replaced with some generic "missing" icons.

  This happens with Mega and Bitmask icons but the applications still
  work. And if i quit one of those two apps the icon of another appears
  again.

  before:
  https://drive.google.com/open?id=0B4b2sRiO8XlMUkJDWTR0a0ptcFk

  after:
  https://drive.google.com/open?id=0B4b2sRiO8XlMcHRMQzJmbm90azQ

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:04:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.57  Mon Oct  3 20:37:01 
PDT 2016
   GCC version:  gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Oct 19 23:09:11 2016
  DistUpgraded: 2016-10-18 09:22:45,469 DEBUG icon theme changed, re-reading
  DistroCodename: yakkety
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics 
Controller [1043:13ad]
 Subsystem: ASUSTeK Computer Inc. GeForce GT 730M [1043:13ad]
  InstallationDate: Installed on 2015-08-20 (426 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: ASUSTeK COMPUTER INC. UX302LG
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-22-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to yakkety on 2016-10-18 (1 days ago)
  dmi.bios.date: 06/16/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX302LG.210
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX302LG
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX302LG.210:bd06/16/2014:svnASUSTeKCOMPUTERINC.:pnUX302LG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX302LG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX302LG
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Wed Oct 19 19:43:23 2016
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1635050/+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 1636142] Re: toolbox.py assert failure: * buffer overflow detected *: /usr/bin/python3 terminated

2016-10-24 Thread Till Kamppeter

** Information type changed from Private to Public

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

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

Title:
  toolbox.py assert failure: *** buffer overflow detected ***:
  /usr/bin/python3 terminated

Status in HPLIP:
  New
Status in hplip package in Ubuntu:
  New

Bug description:
  Just launched the HPLip Toolbox under gnome 3 and it crashed. The
  result is the same using the graphical interface launcher or using a
  terminal.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: hplip-data 3.16.7+repack0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AssertionMessage: *** buffer overflow detected ***: /usr/bin/python3 
terminated
  CurrentDesktop: GNOME
  Date: Mon Oct 24 12:10:32 2016
  Dependencies:
   gcc-6-base 6.2.0-5ubuntu12
   libc6 2.24-3ubuntu1
   libgcc1 1:6.2.0-5ubuntu12
   liblzma5 5.1.1alpha+20120614-2.1ubuntu1
   xz-utils 5.1.1alpha+20120614-2.1ubuntu1
  ExecutablePath: /usr/share/hplip/toolbox.py
  InstallationDate: Installed on 2015-06-15 (496 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  InterpreterPath: /usr/bin/python3.5
  MachineType: LENOVO 20BSCTO1WW
  PackageArchitecture: all
  Papersize: a4
  ProcCmdline: /usr/bin/python3 /usr/bin/hp-toolbox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic.efi.signed 
root=UUID=b5bda038-97c0-40f3-b9ba-67c06b05ae03 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: hplip
  StacktraceTop:
   __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7fb3450a88ec "*** 
%s ***: %s terminated\n") at ../sysdeps/posix/libc_fatal.c:175
   __GI___fortify_fail (msg=, msg@entry=0x7fb3450a887d "buffer 
overflow detected") at fortify_fail.c:37
   __GI___chk_fail () at chk_fail.c:28
   __strcpy_chk (dest=0x55b8db89c920 "", src=0x55b8db9c6f44 "HP Designjet T520 
36in ", '\\' ..., destlen=128) at strcpy_chk.c:30
   __parsePrinterAttributes () from /usr/lib/x86_64-linux-gnu/libhpipp.so.0
  Title: toolbox.py assert failure: *** buffer overflow detected ***: 
/usr/bin/python3 terminated
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (9 days ago)
  UserGroups: adm cdrom dip kismet lpadmin plugdev sambashare sudo
  dmi.bios.date: 05/08/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET29W (1.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET29W(1.07):bd05/08/2015:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BSCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1636142/+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 1567578] Re: libnl should be updated to support up to 63 VFs per single PF

Hello,

I am able to reproduce this bug consistently on a Trusty (3.19.0-73-generic) 
machine
equipped with 2 ixgbe 10GbE cards:

04:00.0 Ethernet controller: Intel Corporation Ethernet Controller 10-Gigabit 
X540-AT2 (rev 01)
04:00.1 Ethernet controller: Intel Corporation Ethernet Controller 10-Gigabit 
X540-AT2 (rev 01)

The sequence to reproduce this bug is:

1)  Edit /etc/default/grub

GRUB_CMDLINE_LINUX="intel_iommu=on ixgbe.max_vfs=63"

2) $ sudo update-grub

### Reboot the machine.

3) Check that  the virtual functions are available:

$ sudo lspci|grep -i eth | grep -i virtual | wc -l
126

4) Create a KVM guest

$ sudo uvt-kvm create guest1 release=trusty

5) List the VF devices :

$ sudo lspci|grep -i eth | grep -i virtual | awk '{print $1}' | sed
's/\:/\_/g' | sed 's/\./\_/g' > devices.txt

6) Get the libvirt node device:

$ sudo for device in $(cat ./devices.txt); do virsh nodedev-list | grep
$device; done  > pci_devices.txt

7) Generate the XML config for each device:

$ sudo mkdir devices && for d in $(cat pci_devices.txt); do virsh
nodedev-dumpxml $d > devices/$d.xml; done

8) Save and Run the following script
(http://pastebin.ubuntu.com/23374186/)

$ sudo python generate-interfaces.py |grep address | wc -l

9) Finally attach the devices to the guest.

$ sudo for i in $(seq 0 63); do virsh attach-device guest1 ./interfaces/$i.xml 
--config; done
Device attached successfully
[...]

Device attached successfully
Device attached successfully

10) Then destroy/start the guest again, at this point the error is
reproduced.

$ sudo virsh destroy guest1
Domain guest1 destroyed

$ sudo virsh start guest1

error: Failed to start domain guest1
error: internal error: missing IFLA_VF_INFO in netlink response

Please note that this error is not reproducible using libnl3_2_22. I am 
currently 
working to bisect and identify the offending commit and propose a backport to 
Ubuntu Trusty.



** Description changed:

+ [Description]
+ 
  Ubuntu 14.04.4 and SRIOV settings.
  
  As already documented in https://bugs.launchpad.net/mos/+bug/1501738
  there is a bug in the default libnl library release installed on Ubuntu
  14.04.4
  
- The library release is the 3.2.21-1 and the bug is impacting on the
- maximum VFs number that can be enabled (up to 30) even if the PF
- supports up to 63 VFs in an Openstack SRIOV configuration
+ When trying to enable a guest with more than 30 VFs attached, the
+ following error is returned:
+ 
+ error: Failed to start domain guest1
+ error: internal error: missing IFLA_VF_INFO in netlink response
+ 
+ [Impact]
+ 
+ The library release is the 3.2.21-1 the bug is impacting on the maximum
+ VFs number that can be enabled (up to 30) even if the PF supports up to
+ 63 VFs in an Openstack SRIOV configuration
+ 
+ [Test Case]
+ 
+ The sequence to reproduce this bug is:
+ 
+ 1) Edit /etc/default/grub
+ 
+ GRUB_CMDLINE_LINUX="intel_iommu=on ixgbe.max_vfs=63"
+ 
+ 2) $ sudo update-grub
+ 
+ ### Reboot the machine.
+ 
+ 3) Check that the virtual functions are available:
+ 
+ $ sudo lspci|grep -i eth | grep -i virtual | wc -l
+ 126
+ 
+ 4) Create a KVM guest
+ 
+ $ sudo uvt-kvm create guest1 release=trusty
+ 
+ 5) List the VF devices :
+ 
+ $ sudo lspci|grep -i eth | grep -i virtual | awk '{print $1}' | sed
+ 's/\:/\_/g' | sed 's/\./\_/g' > devices.txt
+ 
+ 6) Get the libvirt node device:
+ 
+ $ sudo for device in $(cat ./devices.txt); do virsh nodedev-list | grep
+ $device; done > pci_devices.txt
+ 
+ 7) Generate the XML config for each device:
+ 
+ $ sudo mkdir devices && for d in $(cat pci_devices.txt); do virsh
+ nodedev-dumpxml $d > devices/$d.xml; done
+ 
+ 8) Save and Run the following script
+ (http://pastebin.ubuntu.com/23374186/)
+ 
+ $ sudo python generate-interfaces.py |grep address | wc -l
+ 
+ 9) Finally attach the devices to the guest.
+ 
+ $ sudo for i in $(seq 0 63); do virsh attach-device guest1 
./interfaces/$i.xml --config; done
+ Device attached successfully
+ [...]
+ 
+ Device attached successfully
+ Device attached successfully
+ 
+ 10) Then destroy/start the guest again, at this point the error is
+ reproduced.
+ 
+ $ sudo virsh destroy guest1
+ Domain guest1 destroyed
+ 
+ $ sudo virsh start guest1
+ 
+ error: Failed to start domain guest1
+ error: internal error: missing IFLA_VF_INFO in netlink response
+ 
+  * detailed instructions how to reproduce the bug
+ 
+  * these should allow someone who is not familiar with the affected
+package to reproduce the bug and verify that the updated package fixes
+the problem.
+ 
+ [Regression Potential]
+ 
+  ** None identified.
+ 
+ [Other Info]
+ 
+ - Redhat Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1040626
+ 
+ [Workaround]
  
  The workaround is to install a newer library release, the 3.2.24-2:
  
  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-3-200_3.2.24-2_amd64.deb
  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-genl-3-200_3.2.24-2_amd64.deb
  wget 
https://launchpad.net/u

[Desktop-packages] [Bug 1636144] Re: Nautilus needs to be restarted to record top level "item" changes not done through Nautilus

** Changed in: nautilus
   Status: Unknown => Confirmed

** Changed in: nautilus
   Importance: Unknown => Medium

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

Title:
  Nautilus needs to be restarted to record top level "item" changes not
  done through Nautilus

Status in Nautilus:
  Confirmed
Status in Ubuntu GNOME:
  New
Status in nautilus package in Ubuntu:
  New

Bug description:
  I have recently found that after upgrading from Ubuntu GNOME 16.04.1
  with GNOME 3.20 to Ubuntu GNOME 16.10 with GNOME 3.22 that in Nautilus
  the little indicator of how many "items" there are in the top level of
  the selected directory does not get updated when Nautilus is open if
  another program creates an item in the directory, though Nautilus will
  update the indicator if it makes the changes.

  For instance I launched Nautilus, then I created a directory which had
  no items currently in it so it was displayed as ""test" selected
  (containing 0 item)". Then I opened Terminal, cded into the right
  directory, and executed "touch t.txt". The indicator in Nautilus, no
  matter what I did, whether I went into the folder and saw that the
  item was there, or I clicked "Properties" in the right-click menu and
  got an accurate result, it didn't show the update in items count in
  the little indicator in the bottom-right-hand corner of Nautilus until
  I restarted Nautilus.

  This is the same for creating directories in the directory, not just
  files.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.22.1-1ubuntu0~yakkety2 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 24 11:56:11 2016
  InstallationDate: Installed on 2016-05-15 (161 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to yakkety on 2016-10-19 (4 days ago)
  usr_lib_nautilus:
   dropbox2015.10.28
   gnome-terminal 3.20.2-1ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1636144/+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 1636144] Re: Nautilus needs to be restarted to record top level "item" changes not done through Nautilus

2016-10-24 Thread Nikita Yerenkov-Scott

** Bug watch added: GNOME Bug Tracker #768455
   https://bugzilla.gnome.org/show_bug.cgi?id=768455

** Changed in: nautilus
   Importance: Medium => Unknown

** Changed in: nautilus
   Status: Confirmed => Unknown

** Changed in: nautilus
 Remote watch: GNOME Bug Tracker #773416 => GNOME Bug Tracker #768455

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

Title:
  Nautilus needs to be restarted to record top level "item" changes not
  done through Nautilus

Status in Nautilus:
  Unknown
Status in Ubuntu GNOME:
  New
Status in nautilus package in Ubuntu:
  New

Bug description:
  I have recently found that after upgrading from Ubuntu GNOME 16.04.1
  with GNOME 3.20 to Ubuntu GNOME 16.10 with GNOME 3.22 that in Nautilus
  the little indicator of how many "items" there are in the top level of
  the selected directory does not get updated when Nautilus is open if
  another program creates an item in the directory, though Nautilus will
  update the indicator if it makes the changes.

  For instance I launched Nautilus, then I created a directory which had
  no items currently in it so it was displayed as ""test" selected
  (containing 0 item)". Then I opened Terminal, cded into the right
  directory, and executed "touch t.txt". The indicator in Nautilus, no
  matter what I did, whether I went into the folder and saw that the
  item was there, or I clicked "Properties" in the right-click menu and
  got an accurate result, it didn't show the update in items count in
  the little indicator in the bottom-right-hand corner of Nautilus until
  I restarted Nautilus.

  This is the same for creating directories in the directory, not just
  files.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.22.1-1ubuntu0~yakkety2 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 24 11:56:11 2016
  InstallationDate: Installed on 2016-05-15 (161 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to yakkety on 2016-10-19 (4 days ago)
  usr_lib_nautilus:
   dropbox2015.10.28
   gnome-terminal 3.20.2-1ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1636144/+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 1568604] Re: Mouse cursor lost when unlocking with Intel graphics

2016-10-24 Thread Guillaume Gauffre

I'm with ElementaryOS Freya.
Bug is still there

Is it because the fix is only available on xenial-updates, and still not
present in trusty-updates?

The package currently installed on my laptop is xserver-xorg-video-
intel-lts-xenial 2:2.99.917+git20160325-1ubuntu1

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

Title:
  Mouse cursor lost when unlocking with Intel graphics

Status in elementary OS:
  Fix Released
Status in xf86-video-intel:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-intel-lts-xenial package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel source package in Xenial:
  Fix Released
Status in xserver-xorg-video-intel package in Debian:
  Fix Released

Bug description:
  [Relevant details]
  This bug also affects Trusty and all distributions based on it, like 
Elementary OS Freya.

  
  [Impact]
  Mouse cursor is no longer visible after VT-switch for systems with Intel 
graphics.

  Switching VTs again may cause the cursor to become visible again.
  - Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7)

  This is often observed in systems that lock the session and return to
  the greeter (including at least Xubuntu, Ubuntu Mate, and elementary
  OS).

  [Test Case]
  (Requires a lightdm-based screen locking solution)
  1. Start a new session.
  2. Lock your screen.
  2a. You are redirected to the lightdm greeter.
  3. Login/Unlock your session.
  4. Cursor is no longer visible.

  [Regression Potential]
  remains to be seen

  ===

  [Original Report]
  Cursor is visible at unlock screen either after returning from suspend or 
just locking.

  After unlocking screen cursor is invisible.

  Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) cursor
  returns

  

  no matter if you suspend or sleep, to swap or disk when you return
  from it, the mouse cursor is missing.you can still move the mouse
  and you can see (because it highlights the window) as you move it
  around.   But the cursor is not displayed on the screen.

  i am using a lenovo W540 laptop.   I downloaded the latest beta on
  april 8 2016.

  this is xubuntu using the xfce window manager.

  the cursor does return if i log off and log back in, but that actually 
defeats the purpose of going to sleep.
  ---
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-08 (2 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: light-locker 1.7.0-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/elementaryos/+bug/1568604/+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 1589401] Re: cannot view wifi networks after re-enabling wifi

2016-10-24 Thread Hansen

No, nothing i know of is happening to solve this bug.
The bug report on bugzilla seems to wait on this bug report and nobody are 
working in it here.
I have tried to contact a couple of people to get some attention to it but to 
no avail.
If anybody know of any way to draw attention to this bug please help.

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

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1589401/+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 1636155] [NEW] Nautilus does not show mounts

2016-10-24 Thread Silvio Bierman

Public bug reported:

I use SSHFS to mount a number of directories on remote servers.
Normally, when I create the mounts all Nautilus windows immediately show
them in the sidebar and Nautilus also displays desktop icons for them.

Since my upgrade to Ubuntu 16.10 this no longer works properly. The
mounts are not displayed in either the sidebar and on the desktop. After
a certain time (at least minutes) the mounts sometimes appear but this
seems inconsistent.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: nautilus 1:3.20.3-1ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Oct 24 13:53:02 2016
InstallationDate: Installed on 2016-10-13 (10 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

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


** Tags: amd64 apport-bug yakkety

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

Title:
  Nautilus does not show mounts

Status in nautilus package in Ubuntu:
  New

Bug description:
  I use SSHFS to mount a number of directories on remote servers.
  Normally, when I create the mounts all Nautilus windows immediately
  show them in the sidebar and Nautilus also displays desktop icons for
  them.

  Since my upgrade to Ubuntu 16.10 this no longer works properly. The
  mounts are not displayed in either the sidebar and on the desktop.
  After a certain time (at least minutes) the mounts sometimes appear
  but this seems inconsistent.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 24 13:53:02 2016
  InstallationDate: Installed on 2016-10-13 (10 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1636155/+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 1581713] Re: Ubuntu Software asks for an Ubuntu Single Sign-On account to install/remove a snap

2016-10-24 Thread corrado venturini

Same problem on Yakkety ... and Zesty.I'm registered on Ubuntu One and
Launchpad but I receive the message 'password invalid' and so I'm unable
to logon.

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

Title:
  Ubuntu Software asks for an Ubuntu Single Sign-On account to
  install/remove a snap

Status in Ubuntu GNOME:
  Triaged
Status in gnome-software package in Ubuntu:
  Triaged
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  If I try to uninstall a snap using Ubuntu Software, it asks for an Ubuntu 
Single Sign-On account. It seems strange since if I use a terminal and do:
  $ sudo snap remove john-the-ripper

  Everything works as expected.

  BTW: Ubuntu Software takes ages to find out the size of the snap
  package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1581713/+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 1589401] Re: cannot view wifi networks after re-enabling wifi

2016-10-24 Thread Larabi

Is Ubuntu working on this bug? It's not the first release this problem
happens. I have the same problem with a RTL8723be.

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

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1589401/+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 1636144] Re: Nautilus needs to be restarted to record top level "item" changes not done through Nautilus