date:20170216

** Branch linked: lp:~henn/ubuntu/yakkety/firefox/fix-for-1665535

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

Title:
  WebRTC webcam support broken in firefox due to apparmor

Status in firefox package in Ubuntu:
  New

Bug description:
  In order to use sites that make use of WebRTC's webcam support,
  firefox needs access to the /dev/videoN device. When I applied the
  latest firefox update over the last week, apparmor was set to
  enforcing mode, which broke sites that use WebRTC, like
  https://talky.io.

  $ lsb_release -rd
  Description:  Ubuntu 16.10
  Release:  16.10
  $ apt-cache policy firefox
  firefox:
Installed: 51.0.1+build2-0ubuntu0.16.10.2
Candidate: 51.0.1+build2-0ubuntu0.16.10.2
Version table:
   *** 51.0.1+build2-0ubuntu0.16.10.2 500
  500 http://us.archive.ubuntu.com/ubuntu yakkety-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu yakkety-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   49.0+build4-0ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1665535/+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 1665535] [NEW] WebRTC webcam support broken in firefox due to apparmor

2017-02-16 Thread Jay Hennessey

Public bug reported:

In order to use sites that make use of WebRTC's webcam support, firefox
needs access to the /dev/videoN device. When I applied the latest
firefox update over the last week, apparmor was set to enforcing mode,
which broke sites that use WebRTC, like https://talky.io.

$ lsb_release -rd
Description:Ubuntu 16.10
Release:16.10
$ apt-cache policy firefox
firefox:
  Installed: 51.0.1+build2-0ubuntu0.16.10.2
  Candidate: 51.0.1+build2-0ubuntu0.16.10.2
  Version table:
 *** 51.0.1+build2-0ubuntu0.16.10.2 500
500 http://us.archive.ubuntu.com/ubuntu yakkety-updates/main amd64 
Packages
500 http://us.archive.ubuntu.com/ubuntu yakkety-security/main amd64 
Packages
100 /var/lib/dpkg/status
 49.0+build4-0ubuntu2 500
500 http://us.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages

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

** Package changed: apparmor (Ubuntu) => firefox (Ubuntu)

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

Title:
  WebRTC webcam support broken in firefox due to apparmor

Status in firefox package in Ubuntu:
  New

Bug description:
  In order to use sites that make use of WebRTC's webcam support,
  firefox needs access to the /dev/videoN device. When I applied the
  latest firefox update over the last week, apparmor was set to
  enforcing mode, which broke sites that use WebRTC, like
  https://talky.io.

  $ lsb_release -rd
  Description:  Ubuntu 16.10
  Release:  16.10
  $ apt-cache policy firefox
  firefox:
Installed: 51.0.1+build2-0ubuntu0.16.10.2
Candidate: 51.0.1+build2-0ubuntu0.16.10.2
Version table:
   *** 51.0.1+build2-0ubuntu0.16.10.2 500
  500 http://us.archive.ubuntu.com/ubuntu yakkety-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu yakkety-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   49.0+build4-0ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1665535/+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 1650874] Re: Bug

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

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

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

Title:
  Bug

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Que dois je faire ?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.4
  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: Sun Dec 18 11:26:34 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9802] 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Wrestler [Radeon HD 6310] [1025:0602]
  InstallationDate: Installed on 2016-12-18 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Acer Aspire 5250
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-53-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/17/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: HMA51-BZ
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.06
  dmi.modalias: 
dmi:bvnAcer:bvrV1.06:bd11/17/2011:svnAcer:pnAspire5250:pvrV1.06:rvnAcer:rnHMA51-BZ:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.06:
  dmi.product.name: Aspire 5250
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer
  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.2
  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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Dec 18 11:06:17 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.2
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1650874/+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 1650842] Re: dont know

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

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

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

Title:
  dont know

Status in xorg package in Ubuntu:
  Expired

Bug description:
  i dont understand

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  .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
  Date: Sun Dec 18 06:29:59 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV610/M74 [Mobility Radeon HD 2400 
XT] [1002:94c8] (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. RV610/M74 [Mobility Radeon HD 2400 XT] [106b:0084]
  InstallationDate: Installed on 2016-11-26 (21 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Apple Inc. iMac8,1
  ProcEnviron:
   LANGUAGE=sv
   PATH=(custom, no user)
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-30-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/09/08
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: IM81.88Z.00C1.B00.0802091538
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F226BEC8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F226BEC8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrIM81.88Z.00C1.B00.0802091538:bd02/09/08:svnAppleInc.:pniMac8,1:pvr1.0:rvnAppleInc.:rnMac-F226BEC8:rvrPVT:cvnAppleInc.:ct13:cvrMac-F226BEC8:
  dmi.product.name: iMac8,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple 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.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
  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: Sun Dec 18 00:15:19 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6.1
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1650842/+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 1665535] [NEW] WebRTC webcam support broken in firefox due to apparmor

You have been subscribed to a public bug:

In order to use sites that make use of WebRTC's webcam support, firefox
needs access to the /dev/videoN device. When I applied the latest
firefox update over the last week, apparmor was set to enforcing mode,
which broke sites that use WebRTC, like https://talky.io.

$ lsb_release -rd
Description:Ubuntu 16.10
Release:16.10
$ apt-cache policy firefox
firefox:
  Installed: 51.0.1+build2-0ubuntu0.16.10.2
  Candidate: 51.0.1+build2-0ubuntu0.16.10.2
  Version table:
 *** 51.0.1+build2-0ubuntu0.16.10.2 500
500 http://us.archive.ubuntu.com/ubuntu yakkety-updates/main amd64 
Packages
500 http://us.archive.ubuntu.com/ubuntu yakkety-security/main amd64 
Packages
100 /var/lib/dpkg/status
 49.0+build4-0ubuntu2 500
500 http://us.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages

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

-- 
WebRTC webcam support broken in firefox due to apparmor
https://bugs.launchpad.net/bugs/1665535
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to firefox 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 1665018] Re: client tools ignore -h option without port number

2017-02-16 Thread Mathew Hodson

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

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

Title:
  client tools ignore -h option without port number

Status in cups package in Ubuntu:
  New
Status in cups source package in Trusty:
  New

Bug description:
  [Impact]
  Prevents user from overriding default print server on cmdline if he's not 
aware of the fact that this bug may be overriden by giving a port number.

  [Test Case]
  1. Setup 2 cups servers with a shared printer set as default destination: 
server1, server2.
  2. On a trusty client try:
  export CUPS_SERVER=server1
  lpstat -h server2 -H
  3. Expected result:
  server2:631
  4. Actual result:
  server1:631
  (server given by CUPS_SERVER is used instead of the one given by -h option).

  [Regression Potential]
  Minimal. ipp_port is initialized to default value if not given explicitly. 
Fix is a backport from Xenial version and already present in upstream release.

  [Other Info]
   
  * Original bug description:

  Some commandline tools (e.g. lp, lpstat) ignore -h option if no port number 
is given.
  This version affects Trusty with cups-client 1.7.2-0ubuntu1.7. Xenial works 
fine.

  Test to reproduce:
  1. Setup 2 cups servers with a shared printer set as default destination: 
server1, server2.
  2. On a trusty client try:
  export CUPS_SERVER=server1
  lpstat -h server2 -H

  3. Expected result:
  server2:631

  4. Actual result:
  server1:631
  (server given by CUPS_SERVER is used instead of the one given by -h option).

  If a port number is given (e.g. server2:631) the commands work as
  expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1665018/+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 1637024] Re: fwupd consuming very high cpu after startup/login

2017-02-16 Thread Graham Mitchell

I'm seeing the same behavior after a reboot. Two fwupd processes
consuming 100% CPU each.

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

Title:
  fwupd consuming very high cpu after startup/login

Status in appstream-glib package in Ubuntu:
  Confirmed
Status in fwupd package in Ubuntu:
  Invalid

Bug description:
  I believe this may be a regression (relapse of Bug #1591868 ).  I
  upgraded to yakkety the other day without major incident and have all
  "updates" checked in the Software and Sources GUI. But after booting
  and logging in just now, I see fwupd consuming two full cores without
  letup.

  In kern.log I see this line:

  fwupd[6242]: Failed to coldplug: UEFI firmware updating not supported

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: fwupd 0.7.2-0ubuntu1
  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: Wed Oct 26 19:49:20 2016
  InstallationDate: Installed on 2016-07-03 (115 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: fwupd
  UpgradeStatus: Upgraded to yakkety on 2016-10-25 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1637024/+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 1637024] Re: fwupd consuming very high cpu after startup/login

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

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

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

Title:
  fwupd consuming very high cpu after startup/login

Status in appstream-glib package in Ubuntu:
  Confirmed
Status in fwupd package in Ubuntu:
  Invalid

Bug description:
  I believe this may be a regression (relapse of Bug #1591868 ).  I
  upgraded to yakkety the other day without major incident and have all
  "updates" checked in the Software and Sources GUI. But after booting
  and logging in just now, I see fwupd consuming two full cores without
  letup.

  In kern.log I see this line:

  fwupd[6242]: Failed to coldplug: UEFI firmware updating not supported

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: fwupd 0.7.2-0ubuntu1
  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: Wed Oct 26 19:49:20 2016
  InstallationDate: Installed on 2016-07-03 (115 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: fwupd
  UpgradeStatus: Upgraded to yakkety on 2016-10-25 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1637024/+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 1013386] Re: unity 2d dash doesn't open office files

2017-02-16 Thread Naël

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

** Changed in: unity-2d (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-2d in Ubuntu.
Matching subscriptions: dp-unity2d
https://bugs.launchpad.net/bugs/1013386

Title:
  unity 2d dash doesn't open office files

Status in unity-2d package in Ubuntu:
  Fix Released

Bug description:
  When i click within the dash - either on the home lens, or on the
  files lens on a LibreOffice type of file (.doc file, in this case) -
  the file doesn't open.

  Opening the file from within Nautilus works fine.

  Within Unity-3d this does NOT occur. Everything works flawlessly in
  this matter.

  cheers

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.12-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18
  Uname: Linux 3.2.0-25-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Thu Jun 14 23:25:34 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/1013386/+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 992717] Re: Opening files from the Dash randomly doesn't work

2017-02-16 Thread Naël

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

** Changed in: unity-2d (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-2d in Ubuntu.
Matching subscriptions: dp-unity2d
https://bugs.launchpad.net/bugs/992717

Title:
  Opening files from the Dash randomly doesn't work

Status in unity-2d package in Ubuntu:
  Fix Released

Bug description:
  My problem is really simple: if I click on a file in the dash (either an 
exact search result or a recent file), sometimes nothing happens. But in some 
cases, it works. I can't say that it has a problem with file types - for 
example, I can open a .jpeg file that's on my desktop, but neither can I open a 
.JPG that's in my pictures folder, nor one that's on an external HDD, nor one 
that's _also_ on the desktop.
  This problem doesn't come up when using 3D unity.
  If needed, I can try a live cd/fresh install, but my network connection is 
really slow so I would only do that if that's the only solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity-2d 5.12.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
  Uname: Linux 3.2.0-24-generic-pae i686
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: i386
  Date: Tue May  1 18:34:14 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120112)
  PackageArchitecture: all
  SourcePackage: unity-2d
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/992717/+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 1663062] Re: [regression] Software clients of nested servers with size >=480x480 are all black in Mir 0.25.0 and later (or stretched and distorted under Unity8)

2017-02-16 Thread Daniel van Vugt

** Changed in: mir/0.26
   Status: Fix Committed => Fix Released

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

Title:
  [regression] Software clients of nested servers with size >=480x480
  are all black in Mir 0.25.0 and later (or stretched and distorted
  under Unity8)

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Committed
Status in Mir 0.25 series:
  Won't Fix
Status in Mir 0.26 series:
  Fix Released
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  GPU apps seem to work.

  CPU apps all get black screen.

  To repro :
  Under unity7 using mir-on-x:

  1- In a terminal, run :
  mir_demo_server -f /tmp/mysock

  2- In another terminal, run :
  mir_demo_server --host-socket /tmp/mysock

  3- In another terminal, run :
  mir_demo_client_progressbar

  Under Unity8 :
  In another terminal, run :
  mir_demo_client_progressbar

  Observe that, the window is black.

  Whereas, egl clients run fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1663062/+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 1393578] Re: Subpixel order not included in Mir display information

2017-02-16 Thread Daniel van Vugt

The subpixel information has never yet worked for me. My desktop reports
"unknown" subpixel order for a pretty common monitor:

$ sudo mirout
...
Output 48: DisplayPort, connected, "DELL U2413", 1920x1200+0+0, enabled, on, 
520mm x 320mm (24.0"), normal, 1.00x, unknown, monitor

"unknown" sounds like a bug. And that's without nesting.

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

Title:
  Subpixel order not included in Mir display information

Status in Mir:
  In Progress
Status in QtMir:
  Triaged
Status in qtubuntu:
  Triaged
Status in mir package in Ubuntu:
  Triaged
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  Just capturing something mentioned by Trevinho on IRC this morning.
  MirDisplayOutput does not include subpixel ordering, it could and
  should though. The information is exposed on the drm side
  (drmModeSubPixel). Marking as wishlist in absence of other
  information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1393578/+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 1665501] [NEW] file transfer in nautilus slows grossly over a couple of minutes

2017-02-16 Thread Graham Bartlett

Public bug reported:

I have found that kswapd0 is running at 100%.  If i run  ' echo 3 > 
/proc/sys/vm/drop_caches' the transfer of data improves but not to initial 
levels.  If that is not done more than a few times the system eventually grinds 
to a halt and reboot is required. The file transfer is usually between external 
usb drives. Beginning of xfer speeds are usually 17 - 20 mbit but will slow to 
less than 1mbit.  This hasn't previously been a problem but i have tried 
rebooting with 3 or 4 older kernels and same problem exists. Older kernels wont 
start for some reason !  That timing coincides with a new graphics board i 
installed.  Not relevant to the issue but may explain earlier than .30 kernels 
not allowing me to login !  As it is the system is unusable for any major file 
transfers.  I have been patching all relevant patches on to my system which is 
running 16.10 
root@GrahamsPC:~# apt-cache policy nautilus
nautilus:
  Installed: 1:3.20.3-1ubuntu3.1
  Candidate: 1:3.20.3-1ubuntu3.1
  Version table:
 *** 1:3.20.3-1ubuntu3.1 500
500 http://archive.ubuntu.com/ubuntu yakkety-updates/main i386 Packages
100 /var/lib/dpkg/status
 1:3.20.3-1ubuntu3 500
500 http://archive.ubuntu.com/ubuntu yakkety/main i386 Packages

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: nautilus 1:3.20.3-1ubuntu3.1
ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
Uname: Linux 4.8.0-37-generic i686
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: i386
Date: Fri Feb 17 11:46:41 2017
GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'890x548+224+414'"
InstallationDate: Installed on 2016-07-12 (219 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
SourcePackage: nautilus
UpgradeStatus: Upgraded to yakkety on 2016-10-14 (125 days ago)
usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

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


** Tags: apport-bug i386 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/1665501

Title:
  file transfer in nautilus slows grossly over a couple of minutes

Status in nautilus package in Ubuntu:
  New

Bug description:
  I have found that kswapd0 is running at 100%.  If i run  ' echo 3 > 
/proc/sys/vm/drop_caches' the transfer of data improves but not to initial 
levels.  If that is not done more than a few times the system eventually grinds 
to a halt and reboot is required. The file transfer is usually between external 
usb drives. Beginning of xfer speeds are usually 17 - 20 mbit but will slow to 
less than 1mbit.  This hasn't previously been a problem but i have tried 
rebooting with 3 or 4 older kernels and same problem exists. Older kernels wont 
start for some reason !  That timing coincides with a new graphics board i 
installed.  Not relevant to the issue but may explain earlier than .30 kernels 
not allowing me to login !  As it is the system is unusable for any major file 
transfers.  I have been patching all relevant patches on to my system which is 
running 16.10 
  root@GrahamsPC:~# apt-cache policy nautilus
  nautilus:
Installed: 1:3.20.3-1ubuntu3.1
Candidate: 1:3.20.3-1ubuntu3.1
Version table:
   *** 1:3.20.3-1ubuntu3.1 500
  500 http://archive.ubuntu.com/ubuntu yakkety-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   1:3.20.3-1ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu yakkety/main i386 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3.1
  ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
  Uname: Linux 4.8.0-37-generic i686
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: i386
  Date: Fri Feb 17 11:46:41 2017
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'890x548+224+414'"
  InstallationDate: Installed on 2016-07-12 (219 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (125 days ago)
  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/1665501/+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 1600136] Re: App indicator does not show icon for Qt apps or with custom icons

** Branch linked: lp:~ci-train-bot/sni-qt/sni-qt-ubuntu-xenial-2488.1

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

Title:
  App indicator does not show icon for Qt apps or with custom icons

Status in Qt:
  In Progress
Status in Snappy:
  New
Status in appmenu-qt5 package in Ubuntu:
  Fix Released
Status in libappindicator package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in snapd package in Ubuntu:
  In Progress
Status in sni-qt package in Ubuntu:
  Fix Released

Bug description:
  Snaps that use the app indicator area via Qt can't display their icon
  there.

  Steps to reproduce and screenshot:
  https://github.com/nuttyartist/notes/pull/77

  Some research:

  - Uses http://doc.qt.io/qt-5/qsystemtrayicon.html
  - The indicator icon is created under /tmp under a randomly generated 
directory name

  didrocks mentions also:

  1. The application says "this is my menu, and here is my icon at that 
address", the address being /tmp/blablabla
  2. appindicator receives the bus messages
  3. and says "let's have a look at this icon at that address"
  4. BUT! /tmp in the snap is different form system /tmp

  


  SRU bug for libappindicator:

  [Impact]

  Indicator icons pointing to a position inside the snap aren't properly
  found by unity, that shows a "missing icon" emblem

  [Test case]

  * Download this yaml file http://pastebin.com/raw/FpEvQYGN and save it as 
snapcraft.yaml
    in any folder you want
  * Run:
    - snapcraft prime
    - sudo snap try prime
    - snap run gtk3-appindicator

  An indicator should open (with proper icon), then if you select "Set
  icon with Full Path" and/or "Enable Local Theme" from its menu, you
  should see a proper icon.

  When snaps are generated in non updated systems, the icon will be
  still missing.

  [Regression potential]

  If $SNAP is defined for an app not running in snap confinement the
  icons couldn't be properly visible

  


  SRU bug for appmenu-qt5:

  [Impact]

  Indicator icons pointing to a position inside the snap aren't properly
  found by unity, that shows a "missing icon" emblem

  [Test case]

  * Download this yaml file http://pastebin.com/raw/KeZ1udjW and save it as 
snapcraft.yaml
    in any folder you want
  * Run:
    - snapcraft prime
    - sudo snap try prime
    - snap run qt5-systray

  An indicator should open, with the proper icon showin. From the window
  you can change the icon type, and all the types should work.

  When snaps are generated in non updated systems, the icons (except the
  Themed one) will be still missing.

  [Regression potential]

  If $SNAP env variable is defined for an app not running in snap
  confinement the icons couldn't be properly visible

  


  SRU bug for sni-qt:

  [Impact]

  Indicator icons pointing to a position inside the snap aren't properly
  found by unity, that shows a "missing icon" emblem

  [Test case]

  * Download this yaml file http://pastebin.com/raw/EZjQS5CH and save it as 
snapcraft.yaml
in any folder you want
  * Run:
- snapcraft prime
- sudo snap try prime
- snap run qt4-systray

  An indicator should open, with the proper icon showin. From the window
  you can change the icon type, and all the types should work.

  When snaps are generated in non updated systems, the icons (except the
  Themed one) will be still missing.

  [Regression potential]

  If $SNAP env variable is defined for an app not running in snap
  confinement the icons couldn't be properly visible

To manage notifications about this bug go to:
https://bugs.launchpad.net/qt/+bug/1600136/+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 1600136] Re: App indicator does not show icon for Qt apps or with custom icons

2017-02-16 Thread Treviño

** Description changed:

  Snaps that use the app indicator area via Qt can't display their icon
  there.
  
  Steps to reproduce and screenshot:
  https://github.com/nuttyartist/notes/pull/77
  
  Some research:
  
  - Uses http://doc.qt.io/qt-5/qsystemtrayicon.html
  - The indicator icon is created under /tmp under a randomly generated 
directory name
  
  didrocks mentions also:
  
  1. The application says "this is my menu, and here is my icon at that 
address", the address being /tmp/blablabla
  2. appindicator receives the bus messages
  3. and says "let's have a look at this icon at that address"
  4. BUT! /tmp in the snap is different form system /tmp
  
  

  
  SRU bug for libappindicator:
  
  [Impact]
  
  Indicator icons pointing to a position inside the snap aren't properly
  found by unity, that shows a "missing icon" emblem
  
  [Test case]
  
  * Download this yaml file http://pastebin.com/raw/FpEvQYGN and save it as 
snapcraft.yaml
    in any folder you want
  * Run:
    - snapcraft prime
    - sudo snap try prime
    - snap run gtk3-appindicator
  
  An indicator should open (with proper icon), then if you select "Set
  icon with Full Path" and/or "Enable Local Theme" from its menu, you
  should see a proper icon.
  
  When snaps are generated in non updated systems, the icon will be still
  missing.
  
  [Regression potential]
  
  If $SNAP is defined for an app not running in snap confinement the icons
  couldn't be properly visible
  
  

  
  SRU bug for appmenu-qt5:
  
  [Impact]
  
  Indicator icons pointing to a position inside the snap aren't properly
  found by unity, that shows a "missing icon" emblem
  
  [Test case]
  
  * Download this yaml file http://pastebin.com/raw/KeZ1udjW and save it as 
snapcraft.yaml
-   in any folder you want
+   in any folder you want
  * Run:
-   - snapcraft prime
-   - sudo snap try prime
-   - snap run qt5-systray
+   - snapcraft prime
+   - sudo snap try prime
+   - snap run qt5-systray
  
  An indicator should open, with the proper icon showin. From the window
  you can change the icon type, and all the types should work.
  
  When snaps are generated in non updated systems, the icons (except the
  Themed one) will be still missing.
  
  [Regression potential]
  
  If $SNAP env variable is defined for an app not running in snap
  confinement the icons couldn't be properly visible
+ 
+ 

+ 
+ SRU bug for sni-qt:
+ 
+ [Impact]
+ 
+ Indicator icons pointing to a position inside the snap aren't properly
+ found by unity, that shows a "missing icon" emblem
+ 
+ [Test case]
+ 
+ * Download this yaml file http://pastebin.com/raw/EZjQS5CH and save it as 
snapcraft.yaml
+   in any folder you want
+ * Run:
+   - snapcraft prime
+   - sudo snap try prime
+   - snap run qt4-systray
+ 
+ An indicator should open, with the proper icon showin. From the window
+ you can change the icon type, and all the types should work.
+ 
+ When snaps are generated in non updated systems, the icons (except the
+ Themed one) will be still missing.
+ 
+ [Regression potential]
+ 
+ If $SNAP env variable is defined for an app not running in snap
+ confinement the icons couldn't be properly visible

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

Title:
  App indicator does not show icon for Qt apps or with custom icons

Status in Qt:
  In Progress
Status in Snappy:
  New
Status in appmenu-qt5 package in Ubuntu:
  Fix Released
Status in libappindicator package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in snapd package in Ubuntu:
  In Progress
Status in sni-qt package in Ubuntu:
  Fix Released

Bug description:
  Snaps that use the app indicator area via Qt can't display their icon
  there.

  Steps to reproduce and screenshot:
  https://github.com/nuttyartist/notes/pull/77

  Some research:

  - Uses http://doc.qt.io/qt-5/qsystemtrayicon.html
  - The indicator icon is created under /tmp under a randomly generated 
directory name

  didrocks mentions also:

  1. The application says "this is my menu, and here is my icon at that 
address", the address being /tmp/blablabla
  2. appindicator receives the bus messages
  3. and says "let's have a look at this icon at that address"
  4. BUT! /tmp in the snap is different form system /tmp

  


  SRU bug for libappindicator:

  [Impact]

  Indicator icons pointing to a position inside the snap aren't properly
  found by unity, that shows a "missing icon" emblem

  [Test case]

  * Download this yaml file

[Desktop-packages] [Bug 1600136] Re: App indicator does not show icon for Qt apps or with custom icons

** Branch linked: lp:~ci-train-bot/sni-qt/sni-qt-ubuntu-zesty-2488

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

Title:
  App indicator does not show icon for Qt apps or with custom icons

Status in Qt:
  In Progress
Status in Snappy:
  New
Status in appmenu-qt5 package in Ubuntu:
  Fix Released
Status in libappindicator package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in snapd package in Ubuntu:
  In Progress
Status in sni-qt package in Ubuntu:
  Fix Released

Bug description:
  Snaps that use the app indicator area via Qt can't display their icon
  there.

  Steps to reproduce and screenshot:
  https://github.com/nuttyartist/notes/pull/77

  Some research:

  - Uses http://doc.qt.io/qt-5/qsystemtrayicon.html
  - The indicator icon is created under /tmp under a randomly generated 
directory name

  didrocks mentions also:

  1. The application says "this is my menu, and here is my icon at that 
address", the address being /tmp/blablabla
  2. appindicator receives the bus messages
  3. and says "let's have a look at this icon at that address"
  4. BUT! /tmp in the snap is different form system /tmp

  


  SRU bug for libappindicator:

  [Impact]

  Indicator icons pointing to a position inside the snap aren't properly
  found by unity, that shows a "missing icon" emblem

  [Test case]

  * Download this yaml file http://pastebin.com/raw/FpEvQYGN and save it as 
snapcraft.yaml
    in any folder you want
  * Run:
    - snapcraft prime
    - sudo snap try prime
    - snap run gtk3-appindicator

  An indicator should open (with proper icon), then if you select "Set
  icon with Full Path" and/or "Enable Local Theme" from its menu, you
  should see a proper icon.

  When snaps are generated in non updated systems, the icon will be
  still missing.

  [Regression potential]

  If $SNAP is defined for an app not running in snap confinement the
  icons couldn't be properly visible

  


  SRU bug for appmenu-qt5:

  [Impact]

  Indicator icons pointing to a position inside the snap aren't properly
  found by unity, that shows a "missing icon" emblem

  [Test case]

  * Download this yaml file http://pastebin.com/raw/KeZ1udjW and save it as 
snapcraft.yaml
    in any folder you want
  * Run:
    - snapcraft prime
    - sudo snap try prime
    - snap run qt5-systray

  An indicator should open, with the proper icon showin. From the window
  you can change the icon type, and all the types should work.

  When snaps are generated in non updated systems, the icons (except the
  Themed one) will be still missing.

  [Regression potential]

  If $SNAP env variable is defined for an app not running in snap
  confinement the icons couldn't be properly visible

  


  SRU bug for sni-qt:

  [Impact]

  Indicator icons pointing to a position inside the snap aren't properly
  found by unity, that shows a "missing icon" emblem

  [Test case]

  * Download this yaml file http://pastebin.com/raw/EZjQS5CH and save it as 
snapcraft.yaml
in any folder you want
  * Run:
- snapcraft prime
- sudo snap try prime
- snap run qt4-systray

  An indicator should open, with the proper icon showin. From the window
  you can change the icon type, and all the types should work.

  When snaps are generated in non updated systems, the icons (except the
  Themed one) will be still missing.

  [Regression potential]

  If $SNAP env variable is defined for an app not running in snap
  confinement the icons couldn't be properly visible

To manage notifications about this bug go to:
https://bugs.launchpad.net/qt/+bug/1600136/+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 1600136] Re: App indicator does not show icon for Qt apps or with custom icons

** Branch linked: lp:~3v1n0/sni-qt/xenial-sru1

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

Title:
  App indicator does not show icon for Qt apps or with custom icons

Status in Qt:
  In Progress
Status in Snappy:
  New
Status in appmenu-qt5 package in Ubuntu:
  Fix Released
Status in libappindicator package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in snapd package in Ubuntu:
  In Progress
Status in sni-qt package in Ubuntu:
  Fix Released

Bug description:
  Snaps that use the app indicator area via Qt can't display their icon
  there.

  Steps to reproduce and screenshot:
  https://github.com/nuttyartist/notes/pull/77

  Some research:

  - Uses http://doc.qt.io/qt-5/qsystemtrayicon.html
  - The indicator icon is created under /tmp under a randomly generated 
directory name

  didrocks mentions also:

  1. The application says "this is my menu, and here is my icon at that 
address", the address being /tmp/blablabla
  2. appindicator receives the bus messages
  3. and says "let's have a look at this icon at that address"
  4. BUT! /tmp in the snap is different form system /tmp

  


  SRU bug for libappindicator:

  [Impact]

  Indicator icons pointing to a position inside the snap aren't properly
  found by unity, that shows a "missing icon" emblem

  [Test case]

  * Download this yaml file http://pastebin.com/raw/FpEvQYGN and save it as 
snapcraft.yaml
    in any folder you want
  * Run:
    - snapcraft prime
    - sudo snap try prime
    - snap run gtk3-appindicator

  An indicator should open (with proper icon), then if you select "Set
  icon with Full Path" and/or "Enable Local Theme" from its menu, you
  should see a proper icon.

  When snaps are generated in non updated systems, the icon will be
  still missing.

  [Regression potential]

  If $SNAP is defined for an app not running in snap confinement the
  icons couldn't be properly visible

  


  SRU bug for appmenu-qt5:

  [Impact]

  Indicator icons pointing to a position inside the snap aren't properly
  found by unity, that shows a "missing icon" emblem

  [Test case]

  * Download this yaml file http://pastebin.com/raw/KeZ1udjW and save it as 
snapcraft.yaml
    in any folder you want
  * Run:
    - snapcraft prime
    - sudo snap try prime
    - snap run qt5-systray

  An indicator should open, with the proper icon showin. From the window
  you can change the icon type, and all the types should work.

  When snaps are generated in non updated systems, the icons (except the
  Themed one) will be still missing.

  [Regression potential]

  If $SNAP env variable is defined for an app not running in snap
  confinement the icons couldn't be properly visible

  


  SRU bug for sni-qt:

  [Impact]

  Indicator icons pointing to a position inside the snap aren't properly
  found by unity, that shows a "missing icon" emblem

  [Test case]

  * Download this yaml file http://pastebin.com/raw/EZjQS5CH and save it as 
snapcraft.yaml
in any folder you want
  * Run:
- snapcraft prime
- sudo snap try prime
- snap run qt4-systray

  An indicator should open, with the proper icon showin. From the window
  you can change the icon type, and all the types should work.

  When snaps are generated in non updated systems, the icons (except the
  Themed one) will be still missing.

  [Regression potential]

  If $SNAP env variable is defined for an app not running in snap
  confinement the icons couldn't be properly visible

To manage notifications about this bug go to:
https://bugs.launchpad.net/qt/+bug/1600136/+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 1600136] Re: App indicator does not show icon for Qt apps or with custom icons

2017-02-16 Thread Treviño

** Description changed:

  Snaps that use the app indicator area via Qt can't display their icon
  there.
  
  Steps to reproduce and screenshot:
  https://github.com/nuttyartist/notes/pull/77
  
  Some research:
  
  - Uses http://doc.qt.io/qt-5/qsystemtrayicon.html
  - The indicator icon is created under /tmp under a randomly generated 
directory name
  
  didrocks mentions also:
  
  1. The application says "this is my menu, and here is my icon at that 
address", the address being /tmp/blablabla
  2. appindicator receives the bus messages
  3. and says "let's have a look at this icon at that address"
  4. BUT! /tmp in the snap is different form system /tmp
  
  

  
  SRU bug for libappindicator:
  
  [Impact]
  
  Indicator icons pointing to a position inside the snap aren't properly
  found by unity, that shows a "missing icon" emblem
  
  [Test case]
  
  * Download this yaml file http://pastebin.com/raw/FpEvQYGN and save it as 
snapcraft.yaml
    in any folder you want
  * Run:
    - snapcraft prime
    - sudo snap try prime
    - snap run gtk3-appindicator
  
  An indicator should open (with proper icon), then if you select "Set
  icon with Full Path" and/or "Enable Local Theme" from its menu, you
  should see a proper icon.
  
  When snaps are generated in non updated systems, the icon will be still
  missing.
  
  [Regression potential]
  
  If $SNAP is defined for an app not running in snap confinement the icons
  couldn't be properly visible
+ 
+ 

+ 
+ SRU bug for appmenu-qt5:
+ 
+ [Impact]
+ 
+ Indicator icons pointing to a position inside the snap aren't properly
+ found by unity, that shows a "missing icon" emblem
+ 
+ [Test case]
+ 
+ * Download this yaml file http://pastebin.com/raw/KeZ1udjW and save it as 
snapcraft.yaml
+   in any folder you want
+ * Run:
+   - snapcraft prime
+   - sudo snap try prime
+   - snap run qt5-systray
+ 
+ An indicator should open, with the proper icon showin. From the window
+ you can change the icon type, and all the types should work.
+ 
+ When snaps are generated in non updated systems, the icons (except the
+ Themed one) will be still missing.
+ 
+ [Regression potential]
+ 
+ If $SNAP env variable is defined for an app not running in snap
+ confinement the icons couldn't be properly visible

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

Title:
  App indicator does not show icon for Qt apps or with custom icons

Status in Qt:
  In Progress
Status in Snappy:
  New
Status in appmenu-qt5 package in Ubuntu:
  Fix Released
Status in libappindicator package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in snapd package in Ubuntu:
  In Progress
Status in sni-qt package in Ubuntu:
  Fix Released

Bug description:
  Snaps that use the app indicator area via Qt can't display their icon
  there.

  Steps to reproduce and screenshot:
  https://github.com/nuttyartist/notes/pull/77

  Some research:

  - Uses http://doc.qt.io/qt-5/qsystemtrayicon.html
  - The indicator icon is created under /tmp under a randomly generated 
directory name

  didrocks mentions also:

  1. The application says "this is my menu, and here is my icon at that 
address", the address being /tmp/blablabla
  2. appindicator receives the bus messages
  3. and says "let's have a look at this icon at that address"
  4. BUT! /tmp in the snap is different form system /tmp

  


  SRU bug for libappindicator:

  [Impact]

  Indicator icons pointing to a position inside the snap aren't properly
  found by unity, that shows a "missing icon" emblem

  [Test case]

  * Download this yaml file http://pastebin.com/raw/FpEvQYGN and save it as 
snapcraft.yaml
    in any folder you want
  * Run:
    - snapcraft prime
    - sudo snap try prime
    - snap run gtk3-appindicator

  An indicator should open (with proper icon), then if you select "Set
  icon with Full Path" and/or "Enable Local Theme" from its menu, you
  should see a proper icon.

  When snaps are generated in non updated systems, the icon will be
  still missing.

  [Regression potential]

  If $SNAP is defined for an app not running in snap confinement the
  icons couldn't be properly visible

  


  SRU bug for appmenu-qt5:

  [Impact]

  Indicator icons pointing to a position inside the snap aren't properly
  found by unity, that shows a "missing icon" emblem

  [Test case]

  * Download this yaml file http://pastebin.com/raw/KeZ1udjW and save it as 
snapcraft.yaml
in any folder you want
  * Run:
- snapcraft prime
- sudo snap try

[Desktop-packages] [Bug 1663989] Re: Screen flickering

2017-02-16 Thread Dave Long

Sorry I should have explained better, I also have a Lenovo Edge E540
which is how I initially found this bug report via Google, but mine does
not have the nvidia chipset, only Intel, so I didn't see how this could
be caused by the nvidia driver.

I will try to test the newer upstream kernel when I get time.

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

Title:
  Screen flickering

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

Bug description:
  Since upgrading from ubuntu 16.04 to 16.10 the screen (backlight?) is
  flickering irregularly. It only happens with kernel 4.8.x. No
  flickering problems when manually switching back to kernel versions
  4.4.x at boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
  Uname: Linux 4.8.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:01: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.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Feb 12 11:29:15 2017
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:502a]
 Subsystem: Lenovo GK208M [GeForce GT 740M] [17aa:502a]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:07dc Intel Corp. 
   Bus 001 Device 004: ID 04f2:b398 Chicony Electronics Co., Ltd 
   Bus 001 Device 003: ID 138a:0011 Validity Sensors, Inc. VFS5011 Fingerprint 
Reader
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20C600JAGE
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-37-generic.efi.signed 
root=UUID=1728272d-15ec-4b09-b728-f2f4878b5120 ro net.ifnames=0 biosdevname=0 
quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/04/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J9ET98WW (2.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C600JAGE
  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: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ9ET98WW(2.18):bd03/04/2015:svnLENOVO:pn20C600JAGE:pvrThinkPadEdgeE540:rvnLENOVO:rn20C600JAGE:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C600JAGE
  dmi.product.version: ThinkPad Edge E540
  dmi.sys.vendor: LENOVO
  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.1
  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: Sun Feb 12 11:28:27 2017
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1663989/+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 1590417] Re: Feature Request: Ubuntu Bluetooth switch audio output device automatically

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

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

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

Title:
  Feature Request: Ubuntu Bluetooth switch audio output device
  automatically

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

Bug description:
  Dear all,

  I would like to request a feature that would make it possible to
  automatically switch to an A2DP audio source.

  This feature would be very useful for headsets for which you currently
  have to switch to the A2DP source manually every time you connect your
  headset. The setting is just not being remembered.

  I also tried to describe the feature in this screencast:

  https://www.youtube.com/watch?v=PeqHq8ddVpQ

  What do you think?

  Thankfully,

  ~Robert

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1590417/+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 1590417] Re: Feature Request: Ubuntu Bluetooth switch audio output device automatically

2017-02-16 Thread Ryan Lee Sipes

Agreed, detailed in my comment on this bug:
https://bugs.launchpad.net/ubuntu/+source/unity-control-
center/+bug/1409325

It selects based on the literal order of audio sinks in this file:
"bluetooth-client.c" in unity-control-center. By moving HSP below
AudioSource/AudioSink, it selects the proper sink type. There is a
problem, however, in that even when it defaults to the correct sink
(A2DP), it requires me to restart the headset for audio to properly
output to it. I think this is a pulseaudio thing as popping up a
terminal shows it behaving properly all the way up to pulseaudio taking
over, but I'm not sure why a power-cycle of the device helps.

This is on my wishlist, whomever fixes this will receive a special
prize.

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

Title:
  Feature Request: Ubuntu Bluetooth switch audio output device
  automatically

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

Bug description:
  Dear all,

  I would like to request a feature that would make it possible to
  automatically switch to an A2DP audio source.

  This feature would be very useful for headsets for which you currently
  have to switch to the A2DP source manually every time you connect your
  headset. The setting is just not being remembered.

  I also tried to describe the feature in this screencast:

  https://www.youtube.com/watch?v=PeqHq8ddVpQ

  What do you think?

  Thankfully,

  ~Robert

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1590417/+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 1619354] Re: [SRU] Upgrade network-manager-applet to latest point release

Hello Aron, or anyone else affected,

Accepted network-manager-applet into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/network-manager-applet/1.2.6-0ubuntu0.16.04.1 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 on 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: network-manager-applet (Ubuntu Xenial)
   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 network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1619354

Title:
  [SRU] Upgrade network-manager-applet to latest point release

Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager-applet source package in Xenial:
  Fix Committed
Status in network-manager-applet source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  Several defects in network-manager-applet can lead to crashes under
  certain circumstance as tracked in errors.ubuntu.com, upstream stable
  bug fix release 1.2.6 should fix a big portion of the bugs while no
  feature is being added or changed.

  [Test Case]

  After upgrading to 1.2.6, crash cases should be lesser than previous,
  and no functional regression should be observed.

  [Regression Potential]

  Potential of causing regression is minimal as upstream fixes aren't
  significant in this small package during the stable branch
  maintenance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1619354/+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 1409325] Re: Ubuntu chooses worst quality when connecting to bluetooth headset

2017-02-16 Thread Ryan Lee Sipes

This is still a problem. There is more than one facet to this bug. The
first is that in bluetooth-client.c it tries to connect via the order in
which the connection types are listed. 'HSP' is the first type and so it
is selected. This should be changed and 'HSP', which is the lower
quality setting, should be moved down the list.

The other, interested side of this bug (which is probably PulseAudio's
fault), is that in my experience the headset has to be power-cycled in
order to properly receive audio even when the correct audio sync is
selected by default.

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

Title:
Ubuntu chooses worst quality when connecting to bluetooth headset

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

Bug description:
I have a set of bluetooth headphones, model Arctic P311. When I
connect to these with Ubuntu, the selected mode is Telephony Duplex
(HSP/HFP). I always want High Fidelity Playback (A2DP). My Android
phone and my Windows computer both select the best mode (A2DP), in my
experience. At least I don't need to fiddle about to change the mode
when using either of those systems.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity-control-center 14.04.3+14.04.20140922-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
Uname: Linux 3.13.0-43-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Jan 10 21:14:12 2015
InstallationDate: Installed on 2014-10-19 (83 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64
(20140722.2)
SourcePackage: unity-control-center
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_unity-control-center:
activity-log-manager 0.9.7-0ubuntu14
deja-dup 30.0-0ubuntu4
gnome-control-center 1:3.6.3-0ubuntu56.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1409325/+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 1651019] Re: [SRU]nm-applet not show wwan options on menu after logout/in

Hello Alex, or anyone else affected,

Accepted network-manager-applet into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/network-manager-applet/1.2.6-0ubuntu0.16.04.1 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 on 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: network-manager-applet (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags removed: verification-done

** Tags added: verification-needed

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

Title:
  [SRU]nm-applet not show wwan options on menu after logout/in

Status in Network Manager Applet:
  Fix Released
Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager-applet source package in Xenial:
  Fix Committed
Status in network-manager-applet source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  With DW5811e(EM7455), mobile data connection not show on nm indicator
  after logout -> login.

  packages which be used:
  network-manager: network-manager_1.2.2-0ubuntu0.16.04.3_amd64
  nm-applet: network-manager-gnome_1.2.0-0ubuntu0.16.04.4_amd64

  Steps to reproduce:
  1. boot device with 4G sim card + DW5811e(EM7455) wwan card
  2. check nm-applet indicator then "Mobile Braodband" could be found in menu 
in normal cases.
  3. logout then login
  4. check nm-applet indicator then "Mobile Braodband" not shows in menu 
anymore.
  5. but still could connect to wwan by nmcli, so looks device and 
networkmanager work fine.

  [Test Case]

  After upgrading to 1.2.6, using the previous "Steps to reproduce"
  should not be able to reproduce the bug any more

  [Regression Potential]

  Potential of causing regression is minimal as upstream fixes aren't
  significant enough.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1651019/+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 1655839] Re: [FTBFS] amd64 build of heimdal 7.1.0+dfsg-9 FAIL: test_rfc3961

This bug was fixed in the package heimdal - 7.1.0+dfsg-9ubuntu1

---
heimdal (7.1.0+dfsg-9ubuntu1) zesty; urgency=medium

  * debian/patches/fix_ld_library_path: Fix FTBFS due to LD_LIBRARY_PATH
in test script wrappers.  Closes LP: #1655839. Apply this via
d/rules, as we regenerate the libtool environment during the build.

 -- Nishanth Aravamudan   Thu, 16 Feb
2017 09:56:03 -0800

** Changed in: heimdal (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  [FTBFS] amd64 build of heimdal 7.1.0+dfsg-9  FAIL: test_rfc3961

Status in heimdal package in Ubuntu:
  Fix Released
Status in libtool package in Ubuntu:
  New

Bug description:
  A few builds have failed: amd64, ppc64el & s390x for Zesty proposed

  for example amd64 fails on test_rfc3961

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1655839/+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 1537308] Re: [HP Pavilion Notebook - 15-ab153nr (ENERGY STAR)] System sends Control, Alt and Shift events without input.

2017-02-16 Thread Robert Stolorz

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

I had the same issue, it's a problem with the BIOS.

Sadly you can only update this through Windows.

http://support.hp.com/ph-en/drivers/selfservice/hp-pavilion-15-ab100
-notebook-pc-series/8499302/model/8857403#Z7_3054ICK0K8UDA0AQC11TA930O2

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

Title:
  [HP Pavilion Notebook - 15-ab153nr (ENERGY STAR)] System sends
  Control, Alt and Shift events without input.

Status in xorg package in Ubuntu:
  Triaged

Bug description:
  I noticed strange behavior from my Ubuntu system.  While left idle,
  the screensaver would shut off with no interaction with the machine.
  While using the machine, webpages would zoom in or out when trying to
  scroll, and command windows would open while typing.

  Using xev, I found that these events corresponded with ALt_L,
  Control_L and Shift_R events, even though those buttons were not being
  pressed.  I'm attaching a xev log, searching for _L will show the
  events.  ((Shift_R events are, for some reason, much rarer and do not
  occur in the particular log I'm adding.)  In many (but not all)
  incidents, the KeyRelease event occurs without a preceding KeyPress
  event.  This problem starts a variable period of time after booting
  the machine; generally within 4 hours.  Once it starts, it persists
  until a reboot.

  Disabling the trackpad with xinput will stop the problem for several
  hours, but eventually something re-enables the trackpad and the
  problem reappears.

  WORKAROUND: Use kernel parameter:
  i8042.dumbkbd

  Running memtest on the box generates an error when one specific core
  runs one specific test, but I cannot rule out that being related to
  memtest's problems with UEFI systems.  (See
  passmark.com/forum/showthread.php?5638 for info on my memtest results
  and the UEFI issues.) I returned the machine to HP for service.  They
  replaced the keyboard, trackpad and memory.  This did not resolve the
  problem.

  I've recreated the problem in UbuntuMate, Ubuntu, and Debian, on both
  3.x and 4.x kernels.  I cannot reliably reproduce the issue on the
  Windows partition on the same box; I think I might have seen it once
  or twice while working on the machine, but can't rule out accidental
  keypresses by me at those times.  Leaving a keylogger running for over
  24 hours on the Windows partition did not show any unexpected keyboard
  events.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-43.49-generic 3.19.8-ckt10
  Uname: Linux 3.19.0-43-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.17.2-0ubuntu1.8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Fri Jan 22 21:36:14 2016
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   fglrx-core, 15.200, 3.19.0-32-generic, x86_64: installed
   fglrx-core, 15.200, 3.19.0-33-generic, x86_64: installed
   fglrx-core, 15.200, 3.19.0-42-generic, x86_64: installed
   fglrx-core, 15.200, 3.19.0-43-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:9874] (rev c5) (prog-if 
00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:80af]
  InstallationDate: Installed on 2015-10-30 (84 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:938): WARNING **: [PIDs] Failed to execute command: 
upstart

   ** (lightdm-gtk-greeter:938): WARNING **: Failed to load user image: Failed 
to open file '/home/jbhelfrich/.face': No such file or directory
  LightdmGreeterLogOld:
   ** (lightdm-gtk-greeter:1191): WARNING **: [PIDs] Failed to execute command: 
upstart

   ** (lightdm-gtk-greeter:1191): WARNING **: Failed to load user image: Failed 
to open file '/home/jbhelfrich/.face': No such file or directory
  MachineType: HP HP Pavilion Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-43-generic.efi.signed 
root=UUID=613f6223-b665-4289-9dfa-7b003124dfdf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 80AF
  dmi.board.vendor: HP
  dmi.board.version: 81.28
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias:

[Desktop-packages] [Bug 1663989] Re: Screen flickering

2017-02-16 Thread Timo Aaltonen

Now that I had another look i-mail-3 has a hybrid system, so test the
mainline kernel first and if it does fix the flickering then move back
to linux.

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

Title:
  Screen flickering

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

Bug description:
  Since upgrading from ubuntu 16.04 to 16.10 the screen (backlight?) is
  flickering irregularly. It only happens with kernel 4.8.x. No
  flickering problems when manually switching back to kernel versions
  4.4.x at boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
  Uname: Linux 4.8.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:01: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.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Feb 12 11:29:15 2017
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:502a]
 Subsystem: Lenovo GK208M [GeForce GT 740M] [17aa:502a]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:07dc Intel Corp. 
   Bus 001 Device 004: ID 04f2:b398 Chicony Electronics Co., Ltd 
   Bus 001 Device 003: ID 138a:0011 Validity Sensors, Inc. VFS5011 Fingerprint 
Reader
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20C600JAGE
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-37-generic.efi.signed 
root=UUID=1728272d-15ec-4b09-b728-f2f4878b5120 ro net.ifnames=0 biosdevname=0 
quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/04/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J9ET98WW (2.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C600JAGE
  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: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ9ET98WW(2.18):bd03/04/2015:svnLENOVO:pn20C600JAGE:pvrThinkPadEdgeE540:rvnLENOVO:rn20C600JAGE:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C600JAGE
  dmi.product.version: ThinkPad Edge E540
  dmi.sys.vendor: LENOVO
  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.1
  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: Sun Feb 12 11:28:27 2017
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1663989/+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 1663989] Re: Screen flickering

2017-02-16 Thread Timo Aaltonen

Dave, don't hijack bugs, this was originally filed on a system with
nvidia, your bug is not the same.

** Package changed: linux (Ubuntu) => nvidia-graphics-drivers (Ubuntu)

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

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

Title:
  Screen flickering

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

Bug description:
  Since upgrading from ubuntu 16.04 to 16.10 the screen (backlight?) is
  flickering irregularly. It only happens with kernel 4.8.x. No
  flickering problems when manually switching back to kernel versions
  4.4.x at boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
  Uname: Linux 4.8.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:01: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.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Feb 12 11:29:15 2017
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:502a]
 Subsystem: Lenovo GK208M [GeForce GT 740M] [17aa:502a]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:07dc Intel Corp. 
   Bus 001 Device 004: ID 04f2:b398 Chicony Electronics Co., Ltd 
   Bus 001 Device 003: ID 138a:0011 Validity Sensors, Inc. VFS5011 Fingerprint 
Reader
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20C600JAGE
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-37-generic.efi.signed 
root=UUID=1728272d-15ec-4b09-b728-f2f4878b5120 ro net.ifnames=0 biosdevname=0 
quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/04/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J9ET98WW (2.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C600JAGE
  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: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ9ET98WW(2.18):bd03/04/2015:svnLENOVO:pn20C600JAGE:pvrThinkPadEdgeE540:rvnLENOVO:rn20C600JAGE:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C600JAGE
  dmi.product.version: ThinkPad Edge E540
  dmi.sys.vendor: LENOVO
  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.1
  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: Sun Feb 12 11:28:27 2017
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1663989/+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 1663555] Re: Repeated suspend and splash screen freeze after upgrading to 16.04

2017-02-16 Thread Timo Aaltonen

** Project changed: nvidia-drivers-ubuntu => nvidia-graphics-drivers
(Ubuntu)

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

Title:
  Repeated suspend and splash screen freeze after upgrading to 16.04

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

Bug description:
  Previously using nvidia-367 with Ubuntu 14.04. Now Ubuntu 16.04 with
  nvidia-367.57-0ubuntu0.16.04.1

  After upgrade two problems have occurred.
  1) Splash screen at startup that prompts for LUKS passphrase has really low 
resolution and does not accept input to decrypt the filesystem. Booting is 
currently only possible with the 'nomodeset' option.
  Kernel version does not affect this.
  This affects at least
   * nvidia-367.57
   * nvidia-375.26 (from PPA)
  Older version nvidia-340.101 is NOT affected.

  2) When booting with two monitors & extended desktop the computer will go to 
suspend mode. Sometimes it will go into suspend repeatedly.
  This happens 'most of the time' when the laptops lid is closed and with all 
driver versions. Probably unrelated to graphics driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01: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 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Feb 10 12:48:59 2017
  DistUpgraded: 2017-02-08 10:35:37,423 DEBUG got a conffile-prompt from dpkg 
for file: '/etc/gnome/defaults.list'
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 3.13.0-108-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-62-generic, x86_64: installed
   nvidia-367, 367.57, 4.4.0-62-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Dell GK106GLM [Quadro K2100M] [1028:05cc]
  InstallationDate: Installed on 2014-09-24 (870 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Precision M4800
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-62-generic 
root=/dev/mapper/vgcrypt-lvcryptoroot ro 
cryptopts=target=cryptvol,source=/dev/disk/by-uuid/31fbd5c5-dcfb-4904-aec8-1c69025870a0,lvm=vgcrypt
 nomodeset
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-02-08 (2 days ago)
  dmi.bios.date: 05/02/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0FVDR2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd05/02/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn0FVDR2:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision M4800
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Feb 10 12:44:57 2017
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.18.4-0ubuntu0.2

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

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

[Desktop-packages] [Bug 1664746] Re: Request for sponsorship for new upstream release (zesty deb provided)

I set the block-proposed tag so we can keep the new version in zesty-
proposed until after Beta 1 so flavors can have time to try out the
updated onboard version and see what settings change they want to make.

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

Title:
  Request for sponsorship for new upstream release (zesty deb provided)

Status in onboard package in Ubuntu:
  Fix Committed

Bug description:
  Version 1.4.0 of Onboard has been released upstream several hours ago.
  I am proposing here a debianisation of the new version, based on
  onboard version currently shipping in the Ubuntu main repository.
  These are the main changes of the new Onboard version, copied from the
  relevant part of the debian/changelog:

    * Request for sponsorship for new upstream release (LP: #1664746)
    * debian/control:
  - Add libudev-dev to Build-Depends
    * debian/copyright.in:
  - Replaced by a more accurate, manually adjusted copyright file
    * debian/onboard.install:
  - Remove settings_auto_show_dialog.ui entry
    * debian/patches/add_defaults_for_ubuntu.patch:
  - Update system-theme-associations example key
  - Add DEP3 tag
  - Refresh
    * debian/source.lintian-overrides:
  - Create file
  - Override 2 missing-license-paragraph-in-dep5-copyright entries
    * Tablet-mode: (LP: #1366421)
  - Add detection based on acpid reporting the SW_TABLET_MODE switch
  - Add detection based on hotkey events from XInput
  - Add detection by reading tablet-mode state from a few known sysfs paths
  - Add option to the Auto-show page to auto-show Onboard only in 
tablet-mode
  - Only run GlobalKeyListener when necessary
  - Add tablet-mode settings to Preferences->Auto-show->Convertibles
    * GNOME Shell:
  - Add edge-drag gesture to show the keyboard in GNOME Shell
  - Add option to gnome-shell-extension-prefs to disable edge-drag
  - Enable auto-show only on first start (LP: #1650810)
  - Fix setup.py to have distutils-extra not open extension dir as a file
  - Stop the legacy icon panel from sliding in and out all the time
  - Add license and copyright header to gschema.xml
  - Fix broken string in prefs.js
  - Fix copyright information in prefs.js
  - Clean up prefs.js
  - Remove debug output
    * Auto-show:
  - Refactor settings_auto_show_dialog.ui into new Auto-show preferences 
page
  - Improve reliability in Unity Dash by reacting only to crucial events
  - Add D-Bus property AutoShowPaused for convertible devices (LP: #1366421)
  - Allow to block auto-show while external keyboards are connected
  - Don't auto-hide while keys are still pressed.
    * External keyboard detection:
  - Detect keyboards with udev
  - Add new preference subpage Preferences->Auto-show->External Keyboards
  - Allow devices to be ignored; e.g. always connected keyboard
    * onboard-autostart.desktop: (LP #1656779)
  - Rename it to onboard-autostart.desktop.in
  - Add _GenericName, _Comment and Icon keys
  - Make it translatable
    * Move listening for global key presses to new GlobalKeyListener.py file
    * Have separate resize protection preference for floating icon and keyboard
    * Add scale for label popup size to Preferences->Keyboard
    * Switch position of "play sound" and "label popups" in Preferences-Keyboard
    * Add MATE'S ContrastHighInverse to the map of known accessibility themes
    * Replace deprecated GdkScreen.get_monitor_workarea()
    * Delay visibility change via D-Bus until all keys are released (LP: 
#1648543)
    * Indicate in log when Onboard has been started from the project directory
    * Rename tools/socket.py to tools/xembed_socket.py to avoid name collision
    * Reorganize AtspiStateTracker for saner handling of multiple accessibles
    * Update licensing tool for gnome shell extension
    * Explicitely clean up Applndicator status icon on exit
    * Improve error handling when opening layouts files
    * Work around firefox 50 urlbar losing focus and giving wrong caret position
    * Work around broken transparency with Gtk 3.22 (Lp: #1636252)
    * Work around byobu not reporting trailing spaces
    * Fix -Wstrict-prototypes warning when building C++ extension lm
    * Fix negative keyboard window size when screen says zero size (LP: 
#1633284)
    * Fix geometry hints for minimum size calculation error on startup
    * Fix startup failure on Arch Linux when libdbus-glib isn't installed
    * Fix signed/unsigned comparison warnings when building in Arch Linux
    * Make sure to hide label popups when the keyboard is hidden
    * Ease adjustment of aspect ratio with more handles when docked and expanded
    * Keep more distance when auto-positioning to the Dash search entry
    * Enable docking by default in

[Desktop-packages] [Bug 1664746] Re: Request for sponsorship for new upstream release (zesty deb provided)

Ok, I pushed the packaging change except the copyright change to Debian's git 
repo
https://anonscm.debian.org/git/pkg-mate/onboard.git?h=debian%2Fexperimental

The Debian maintainer Mike is going to take care of updating the
copyright.

It includes marmuta's commit.

I added the gsettings to ubuntu-settings:
https://launchpad.net/ubuntu/+source/ubuntu-settings/17.04.0

I will contact the other official Ubuntu flavors to see if they want to
add those overrides (or different) to their distro settings.

We should be good to sync from Debian from now on.

If onboard isn't in Debian experimental by this weekend, I'll probably
just upload to zesty directly and we can sync later.

I am going to go ahead and unsubscribe ubuntu-sponsors now. Feel fee to
re-subscribe if this bug seems stuck or there's something else you need
sponsored.

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

Title:
  Request for sponsorship for new upstream release (zesty deb provided)

Status in onboard package in Ubuntu:
  Fix Committed

Bug description:
  Version 1.4.0 of Onboard has been released upstream several hours ago.
  I am proposing here a debianisation of the new version, based on
  onboard version currently shipping in the Ubuntu main repository.
  These are the main changes of the new Onboard version, copied from the
  relevant part of the debian/changelog:

    * Request for sponsorship for new upstream release (LP: #1664746)
    * debian/control:
  - Add libudev-dev to Build-Depends
    * debian/copyright.in:
  - Replaced by a more accurate, manually adjusted copyright file
    * debian/onboard.install:
  - Remove settings_auto_show_dialog.ui entry
    * debian/patches/add_defaults_for_ubuntu.patch:
  - Update system-theme-associations example key
  - Add DEP3 tag
  - Refresh
    * debian/source.lintian-overrides:
  - Create file
  - Override 2 missing-license-paragraph-in-dep5-copyright entries
    * Tablet-mode: (LP: #1366421)
  - Add detection based on acpid reporting the SW_TABLET_MODE switch
  - Add detection based on hotkey events from XInput
  - Add detection by reading tablet-mode state from a few known sysfs paths
  - Add option to the Auto-show page to auto-show Onboard only in 
tablet-mode
  - Only run GlobalKeyListener when necessary
  - Add tablet-mode settings to Preferences->Auto-show->Convertibles
    * GNOME Shell:
  - Add edge-drag gesture to show the keyboard in GNOME Shell
  - Add option to gnome-shell-extension-prefs to disable edge-drag
  - Enable auto-show only on first start (LP: #1650810)
  - Fix setup.py to have distutils-extra not open extension dir as a file
  - Stop the legacy icon panel from sliding in and out all the time
  - Add license and copyright header to gschema.xml
  - Fix broken string in prefs.js
  - Fix copyright information in prefs.js
  - Clean up prefs.js
  - Remove debug output
    * Auto-show:
  - Refactor settings_auto_show_dialog.ui into new Auto-show preferences 
page
  - Improve reliability in Unity Dash by reacting only to crucial events
  - Add D-Bus property AutoShowPaused for convertible devices (LP: #1366421)
  - Allow to block auto-show while external keyboards are connected
  - Don't auto-hide while keys are still pressed.
    * External keyboard detection:
  - Detect keyboards with udev
  - Add new preference subpage Preferences->Auto-show->External Keyboards
  - Allow devices to be ignored; e.g. always connected keyboard
    * onboard-autostart.desktop: (LP #1656779)
  - Rename it to onboard-autostart.desktop.in
  - Add _GenericName, _Comment and Icon keys
  - Make it translatable
    * Move listening for global key presses to new GlobalKeyListener.py file
    * Have separate resize protection preference for floating icon and keyboard
    * Add scale for label popup size to Preferences->Keyboard
    * Switch position of "play sound" and "label popups" in Preferences-Keyboard
    * Add MATE'S ContrastHighInverse to the map of known accessibility themes
    * Replace deprecated GdkScreen.get_monitor_workarea()
    * Delay visibility change via D-Bus until all keys are released (LP: 
#1648543)
    * Indicate in log when Onboard has been started from the project directory
    * Rename tools/socket.py to tools/xembed_socket.py to avoid name collision
    * Reorganize AtspiStateTracker for saner handling of multiple accessibles
    * Update licensing tool for gnome shell extension
    * Explicitely clean up Applndicator status icon on exit
    * Improve error handling when opening layouts files
    * Work around firefox 50 urlbar losing focus and giving wrong caret position
    * Work around broken transparency with Gtk 3.22 (Lp: #1636252)
    * Work around byobu not reporting trailing spaces
    * Fix

[Desktop-packages] [Bug 1663989] [NEW] Screen flickering

You have been subscribed to a public bug:

Since upgrading from ubuntu 16.04 to 16.10 the screen (backlight?) is
flickering irregularly. It only happens with kernel 4.8.x. No flickering
problems when manually switching back to kernel versions 4.4.x at boot.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
Uname: Linux 4.8.0-37-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:01: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.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sun Feb 12 11:29:15 2017
DistUpgraded: Fresh install
DistroCodename: yakkety
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:502a]
   Subsystem: Lenovo GK208M [GeForce GT 740M] [17aa:502a]
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 8087:07dc Intel Corp. 
 Bus 001 Device 004: ID 04f2:b398 Chicony Electronics Co., Ltd 
 Bus 001 Device 003: ID 138a:0011 Validity Sensors, Inc. VFS5011 Fingerprint 
Reader
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20C600JAGE
ProcEnviron:
 LANGUAGE=de_DE
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-37-generic.efi.signed 
root=UUID=1728272d-15ec-4b09-b728-f2f4878b5120 ro net.ifnames=0 biosdevname=0 
quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/04/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: J9ET98WW (2.18 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20C600JAGE
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: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrJ9ET98WW(2.18):bd03/04/2015:svnLENOVO:pn20C600JAGE:pvrThinkPadEdgeE540:rvnLENOVO:rn20C600JAGE:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20C600JAGE
dmi.product.version: ThinkPad Edge E540
dmi.sys.vendor: LENOVO
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.1
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: Sun Feb 12 11:28:27 2017
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu6.1

** Affects: nvidia-graphics-drivers (Ubuntu)
 Importance: Medium
 Status: New


** Tags: amd64 apport-bug compiz-0.9 kernel-da-key ubuntu yakkety
-- 
Screen flickering
https://bugs.launchpad.net/bugs/1663989
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to nvidia-graphics-drivers 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 1663555] [NEW] Repeated suspend and splash screen freeze after upgrading to 16.04

You have been subscribed to a public bug:

Previously using nvidia-367 with Ubuntu 14.04. Now Ubuntu 16.04 with
nvidia-367.57-0ubuntu0.16.04.1

After upgrade two problems have occurred.
1) Splash screen at startup that prompts for LUKS passphrase has really low 
resolution and does not accept input to decrypt the filesystem. Booting is 
currently only possible with the 'nomodeset' option.
Kernel version does not affect this.
This affects at least
 * nvidia-367.57
 * nvidia-375.26 (from PPA)
Older version nvidia-340.101 is NOT affected.

2) When booting with two monitors & extended desktop the computer will go to 
suspend mode. Sometimes it will go into suspend repeatedly.
This happens 'most of the time' when the laptops lid is closed and with all 
driver versions. Probably unrelated to graphics driver.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
Uname: Linux 4.4.0-62-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01: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 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
.tmp.unity_support_test.0:

ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Fri Feb 10 12:48:59 2017
DistUpgraded: 2017-02-08 10:35:37,423 DEBUG got a conffile-prompt from dpkg for 
file: '/etc/gnome/defaults.list'
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 3.13.0-108-generic, x86_64: installed
 bbswitch, 0.8, 4.4.0-62-generic, x86_64: installed
 nvidia-367, 367.57, 4.4.0-62-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Dell GK106GLM [Quadro K2100M] [1028:05cc]
InstallationDate: Installed on 2014-09-24 (870 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: Dell Inc. Precision M4800
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-62-generic 
root=/dev/mapper/vgcrypt-lvcryptoroot ro 
cryptopts=target=cryptvol,source=/dev/disk/by-uuid/31fbd5c5-dcfb-4904-aec8-1c69025870a0,lvm=vgcrypt
 nomodeset
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2017-02-08 (2 days ago)
dmi.bios.date: 05/02/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 0FVDR2
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd05/02/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn0FVDR2:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Precision M4800
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
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.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Fri Feb 10 12:44:57 2017
xserver.configfile: default
xserver.errors: open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:

xserver.version: 2:1.18.4-0ubuntu0.2

** Affects: nvidia-graphics-drivers (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial
-- 
Repeated suspend and splash screen freeze after upgrading to 16.04
https://bugs.launchpad.net/bugs/1663555
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to nvidia-graphics-drivers 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 1664746] Re: Request for sponsorship for new upstream release (zesty deb provided)

** Tags added: block-proposed upgrade-software-version

** Changed in: onboard (Ubuntu)
   Status: Incomplete => Fix Committed

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

Title:
  Request for sponsorship for new upstream release (zesty deb provided)

Status in onboard package in Ubuntu:
  Fix Committed

Bug description:
  Version 1.4.0 of Onboard has been released upstream several hours ago.
  I am proposing here a debianisation of the new version, based on
  onboard version currently shipping in the Ubuntu main repository.
  These are the main changes of the new Onboard version, copied from the
  relevant part of the debian/changelog:

    * Request for sponsorship for new upstream release (LP: #1664746)
    * debian/control:
  - Add libudev-dev to Build-Depends
    * debian/copyright.in:
  - Replaced by a more accurate, manually adjusted copyright file
    * debian/onboard.install:
  - Remove settings_auto_show_dialog.ui entry
    * debian/patches/add_defaults_for_ubuntu.patch:
  - Update system-theme-associations example key
  - Add DEP3 tag
  - Refresh
    * debian/source.lintian-overrides:
  - Create file
  - Override 2 missing-license-paragraph-in-dep5-copyright entries
    * Tablet-mode: (LP: #1366421)
  - Add detection based on acpid reporting the SW_TABLET_MODE switch
  - Add detection based on hotkey events from XInput
  - Add detection by reading tablet-mode state from a few known sysfs paths
  - Add option to the Auto-show page to auto-show Onboard only in 
tablet-mode
  - Only run GlobalKeyListener when necessary
  - Add tablet-mode settings to Preferences->Auto-show->Convertibles
    * GNOME Shell:
  - Add edge-drag gesture to show the keyboard in GNOME Shell
  - Add option to gnome-shell-extension-prefs to disable edge-drag
  - Enable auto-show only on first start (LP: #1650810)
  - Fix setup.py to have distutils-extra not open extension dir as a file
  - Stop the legacy icon panel from sliding in and out all the time
  - Add license and copyright header to gschema.xml
  - Fix broken string in prefs.js
  - Fix copyright information in prefs.js
  - Clean up prefs.js
  - Remove debug output
    * Auto-show:
  - Refactor settings_auto_show_dialog.ui into new Auto-show preferences 
page
  - Improve reliability in Unity Dash by reacting only to crucial events
  - Add D-Bus property AutoShowPaused for convertible devices (LP: #1366421)
  - Allow to block auto-show while external keyboards are connected
  - Don't auto-hide while keys are still pressed.
    * External keyboard detection:
  - Detect keyboards with udev
  - Add new preference subpage Preferences->Auto-show->External Keyboards
  - Allow devices to be ignored; e.g. always connected keyboard
    * onboard-autostart.desktop: (LP #1656779)
  - Rename it to onboard-autostart.desktop.in
  - Add _GenericName, _Comment and Icon keys
  - Make it translatable
    * Move listening for global key presses to new GlobalKeyListener.py file
    * Have separate resize protection preference for floating icon and keyboard
    * Add scale for label popup size to Preferences->Keyboard
    * Switch position of "play sound" and "label popups" in Preferences-Keyboard
    * Add MATE'S ContrastHighInverse to the map of known accessibility themes
    * Replace deprecated GdkScreen.get_monitor_workarea()
    * Delay visibility change via D-Bus until all keys are released (LP: 
#1648543)
    * Indicate in log when Onboard has been started from the project directory
    * Rename tools/socket.py to tools/xembed_socket.py to avoid name collision
    * Reorganize AtspiStateTracker for saner handling of multiple accessibles
    * Update licensing tool for gnome shell extension
    * Explicitely clean up Applndicator status icon on exit
    * Improve error handling when opening layouts files
    * Work around firefox 50 urlbar losing focus and giving wrong caret position
    * Work around broken transparency with Gtk 3.22 (Lp: #1636252)
    * Work around byobu not reporting trailing spaces
    * Fix -Wstrict-prototypes warning when building C++ extension lm
    * Fix negative keyboard window size when screen says zero size (LP: 
#1633284)
    * Fix geometry hints for minimum size calculation error on startup
    * Fix startup failure on Arch Linux when libdbus-glib isn't installed
    * Fix signed/unsigned comparison warnings when building in Arch Linux
    * Make sure to hide label popups when the keyboard is hidden
    * Ease adjustment of aspect ratio with more handles when docked and expanded
    * Keep more distance when auto-positioning to the Dash search entry
    * Enable docking by default in onboard-defaults.conf.example
    * Update build instructions in README for Arch and Mageia
    * Improve

[Desktop-packages] [Bug 1664138] Re: soffice.bin crashed with SIGSEGV in ResMgr::GetLong()

2017-02-16 Thread domi

crashed with 2.5 while launching libreoffice
after it ask to recover an old crashed file "without name.odt"
my answer was yes 

stupid of me i made 2 changes before trying again  (and not only one by one)
- install 5.3.0 RC3 from PPA
- answer "no" about recovering the lost file  "without name.odt"

==> all went fine without crash

it seems that #7 from russianneuromancer is right

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

Title:
  soffice.bin crashed with SIGSEGV in ResMgr::GetLong()

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  soffice.bin crashed with SIGSEGV in ResMgr::GetLong()

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: libreoffice-core 1:5.2.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Mon Feb 13 09:03:51 2017
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2016-10-13 (122 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --splash-pipe=5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
   LD_LIBRARY_PATH=
  SegvAnalysis:
   Segfault happened at: 0x7f2ab939adf0 <_ZN6ResMgr7GetLongEPv>:mov
(%rdi),%eax
   PC (0x7f2ab939adf0) ok
   source "(%rdi)" (0x55f1c6756d4b) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: libreoffice
  StacktraceTop:
   ResMgr::GetLong(void*) () from /usr/lib/libreoffice/program/libmergedlo.so
   ResMgr::ReadLong() () from /usr/lib/libreoffice/program/libmergedlo.so
   ImageList::ImageList(ResId const&) () from 
/usr/lib/libreoffice/program/libmergedlo.so
   ?? () from /usr/lib/libreoffice/program/libmergedlo.so
   SvFileInformationManager::GetFileImage(INetURLObject const&) () from 
/usr/lib/libreoffice/program/libmergedlo.so
  Title: soffice.bin crashed with SIGSEGV in ResMgr::GetLong()
  UpgradeStatus: Upgraded to zesty on 2017-01-16 (27 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1664138/+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 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

2017-02-16 Thread Barry Warsaw

I'll cherry pick back 98974a88 and 47c16359 now.

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

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  $ systemd-resolve www.freedesktop.org
  www.freedesktop.org: 131.252.210.176
   2610:10:20:722:a800:ff:feda:470f
   (annarchy.freedesktop.org)

  -- Information acquired via protocol DNS in 673.6ms.
  -- Data is authenticated: no
  $ ping www.freedesktop.org
  ping: www.freedesktop.org: Name or service not known
  $ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  $ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  7146IN  CNAME   annarchy.freedesktop.org.
  $ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  14399   IN  CNAME   annarchy.freedesktop.org.
  annarchy.freedesktop.org. 14399   IN  A   131.252.210.176

  I trust it needn’t be explained why this makes the internet almost
  completely useless in zesty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1647031/+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 1616943] Re: Can't auth against U1 in g-s

2017-02-16 Thread sandor

no puedo instalar programas en ubuntu 16.10 porque me pide los datos de
mi cuenta de ubuntu one y cuando le pongo mi direccion de correo y
contrasenas dice que no es correcta

** Changed in: gnome-software (Ubuntu Yakkety)
 Assignee: Robert Ancell (robert-ancell) => (unassigned)

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

Title:
  Can't auth against U1 in g-s

Status in gnome-software package in Ubuntu:
  Fix Released
Status in snapd-glib package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released
Status in snapd-glib source package in Xenial:
  Fix Released
Status in gnome-software source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  Authentication using Ubuntu One credentials to install/remove snaps always  
fails. This is due to a behaviour change in snapd (no longer accepts login 
requests from non-root users). Existing credentials continue to work.

  [Test Case]
  1. Delete any existing credentials by deleting passwords marked 
"com.ubuntu.UbuntuOne.GnomeSoftware" using Seahorse.
  2. Start GNOME Software
  3. Search for a snap (e.g. "moon-buggy")
  4. Install Snap
  5. Enter Ubuntu One credentials when prompted

  Observed result:
  Dialog says "Incorrect email or password".

  Expected result:
  Authentication completes and the snap is installed.

  [Regression Potential]
  The solution is to use a new D-Bus service (snapd-login-service) and new 
library (snapd-glib) to get the Macaroon from snapd. This has some risk of 
introducing new bugs. The change is minimised (other snapd code paths 
unchanged) and the alternative is login to be impossible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1616943/+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 1406538] Re: Screenshot contains selected area highlight

2017-02-16 Thread e633

I'd say #743176 is the same bug, only worse.

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

Title:
  Screenshot contains selected area highlight

Status in Linux Mint:
  Confirmed
Status in gnome-screenshot package in Ubuntu:
  Confirmed
Status in mate-utils package in Ubuntu:
  Fix Committed

Bug description:
  mate-utils_1.8.1-0+rebecca_amd64
  If i choose "select area to grab" i almost constantly get an annoying green 
overlay which is what i just used to highlight the area that i wanted to grab.
  See attached example.
  I'm using Mint MATE x64 17.1, software compositing window manager enabled, 
compiz disabled, VGA AMD radeon 6370M, drivers "xserver-xorg-video-ati" 
7.3.0-1-ubuntu3.1, kernel 3.13.0-37-generic x86_64. 
  I remember this happening since mint 13 or so.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linuxmint/+bug/1406538/+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 1665469] Re: gnome-system-monitor crashed with SIGSEGV in GI_libc_free()

2017-02-16 Thread Apport retracing service

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

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1665209
   gnome-system-monitor crash on 17.04

** Tags removed: need-amd64-retrace

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

Title:
  gnome-system-monitor crashed with SIGSEGV in __GI___libc_free()

Status in gnome-system-monitor package in Ubuntu:
  New

Bug description:
  Got that crash, by:
  - right-clicking the mem icon in the systray
  - hitting "system monitor ..."

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: gnome-system-monitor 3.23.90-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Feb 16 22:41:21 2017
  ExecutablePath: /usr/bin/gnome-system-monitor
  ProcCmdline: gnome-system-monitor
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f4917a25162 <__GI___libc_free+34>:  mov
-0x8(%rdi),%rax
   PC (0x7f4917a25162) ok
   source "-0x8(%rdi)" (0x55c0fff8) not located in a known VMA region 
(needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-system-monitor
  StacktraceTop:
   __GI___libc_free (mem=0x55c1) at malloc.c:2963
   get_process_cgroup_info(ProcInfo&) ()
   proctable_update(GsmApplication*) ()
   update_page_activities(GsmApplication*) ()
   create_main_window(GsmApplication*) ()
  Title: gnome-system-monitor crashed with SIGSEGV in __GI___libc_free()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom colord dip lpadmin nvidia-persistenced plugdev 
sambashare sudo users

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1665469/+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 1665209] Re: gnome-system-monitor crash on 17.04

2017-02-16 Thread Bug Watch Updater

** Changed in: gnome-system-monitor
   Status: Unknown => In Progress

** Changed in: gnome-system-monitor
   Importance: Unknown => Critical

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

Title:
  gnome-system-monitor crash on 17.04

Status in Gnome System Monitor:
  In Progress
Status in gnome-system-monitor package in Ubuntu:
  Triaged

Bug description:
  crash after update

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: gnome-system-monitor 3.23.90-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 15 21:53:47 2017
  ExecutablePath: /usr/bin/gnome-system-monitor
  InstallationDate: Installed on 2017-01-26 (20 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  ProcCmdline: gnome-system-monitor
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: gnome-system-monitor
  UpgradeStatus: Upgraded to zesty on 2017-01-27 (19 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-system-monitor/+bug/1665209/+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 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

This bug was fixed in the package systemd - 232-17ubuntu1

---
systemd (232-17ubuntu1) zesty; urgency=medium

  * debian/patches/0001-resolved-follow-CNAMES-for-DNS-stub-
replies.patch: cherry-pick upstream fix for following CNAMEs in DNS
stub replies.  Closes LP: #1647031.

 -- Steve Langasek   Sun, 12 Feb 2017
22:54:55 -0800

** Changed in: systemd (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  $ systemd-resolve www.freedesktop.org
  www.freedesktop.org: 131.252.210.176
   2610:10:20:722:a800:ff:feda:470f
   (annarchy.freedesktop.org)

  -- Information acquired via protocol DNS in 673.6ms.
  -- Data is authenticated: no
  $ ping www.freedesktop.org
  ping: www.freedesktop.org: Name or service not known
  $ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  $ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  7146IN  CNAME   annarchy.freedesktop.org.
  $ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  14399   IN  CNAME   annarchy.freedesktop.org.
  annarchy.freedesktop.org. 14399   IN  A   131.252.210.176

  I trust it needn’t be explained why this makes the internet almost
  completely useless in zesty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1647031/+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 1665469] [NEW] gnome-system-monitor crashed with SIGSEGV in GI_libc_free()

2017-02-16 Thread dino99

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

Public bug reported:

Got that crash, by:
- right-clicking the mem icon in the systray
- hitting "system monitor ..."

ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: gnome-system-monitor 3.23.90-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
Uname: Linux 4.10.0-8-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Feb 16 22:41:21 2017
ExecutablePath: /usr/bin/gnome-system-monitor
ProcCmdline: gnome-system-monitor
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f4917a25162 <__GI___libc_free+34>:mov
-0x8(%rdi),%rax
 PC (0x7f4917a25162) ok
 source "-0x8(%rdi)" (0x55c0fff8) not located in a known VMA region (needed 
readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-system-monitor
StacktraceTop:
 __GI___libc_free (mem=0x55c1) at malloc.c:2963
 get_process_cgroup_info(ProcInfo&) ()
 proctable_update(GsmApplication*) ()
 update_page_activities(GsmApplication*) ()
 create_main_window(GsmApplication*) ()
Title: gnome-system-monitor crashed with SIGSEGV in __GI___libc_free()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom colord dip lpadmin nvidia-persistenced plugdev sambashare 
sudo users

** Affects: gnome-system-monitor (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash third-party-packages zesty

** Information type changed from Private to Public

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

Title:
  gnome-system-monitor crashed with SIGSEGV in __GI___libc_free()

Status in gnome-system-monitor package in Ubuntu:
  New

Bug description:
  Got that crash, by:
  - right-clicking the mem icon in the systray
  - hitting "system monitor ..."

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: gnome-system-monitor 3.23.90-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Feb 16 22:41:21 2017
  ExecutablePath: /usr/bin/gnome-system-monitor
  ProcCmdline: gnome-system-monitor
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f4917a25162 <__GI___libc_free+34>:  mov
-0x8(%rdi),%rax
   PC (0x7f4917a25162) ok
   source "-0x8(%rdi)" (0x55c0fff8) not located in a known VMA region 
(needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-system-monitor
  StacktraceTop:
   __GI___libc_free (mem=0x55c1) at malloc.c:2963
   get_process_cgroup_info(ProcInfo&) ()
   proctable_update(GsmApplication*) ()
   update_page_activities(GsmApplication*) ()
   create_main_window(GsmApplication*) ()
  Title: gnome-system-monitor crashed with SIGSEGV in __GI___libc_free()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom colord dip lpadmin nvidia-persistenced plugdev 
sambashare sudo users

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1665469/+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 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2017-02-16 Thread andrew buffa

Brian:

how do I fix with no internet connection

the last update disconnected it

Andrew
On 2/16/2017 2:43 PM, Brian Murray wrote:
> Hello Mark, or anyone else affected,
>
> Accepted cups into xenial-proposed. The package will build now and be
> available at https://launchpad.net/ubuntu/+source/cups/2.1.3-4ubuntu0.2
> in a few hours, and then in the -proposed repository.
>
> Please help us by testing this new package.  See
> https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
> enable and use -proposed.  Your feedback will aid us getting this update
> out to other Ubuntu users.
>
> If this package fixes the bug for you, please add a comment to this bug,
> mentioning the version of the package you tested, and change the tag
> from verification-needed to verification-done. If it does not fix the
> bug for you, please add a comment stating that, and change the tag to
> verification-failed.  In either case, details of your testing will help
> us make a better decision.
>
> Further information regarding the verification process can be found at
> https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
> advance!
>
> ** Changed in: cups (Ubuntu Xenial)
> Status: Triaged => Fix Committed
>

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  Fix Committed
Status in cups source package in Yakkety:
  Fix Committed
Status in cups source package in Zesty:
  Fix Released

Bug description:
  This is in xenial-proposed, please block release to -updates
  accordingly :)

  [Impact]
  * fail to upgrade

  [testcase]
  Root cause is believed to be reproducible with:

  #!/bin/bash
  systemctl stop cups.path cups.service
  rm /var/cache/cups/org.cups.cupsd
  systemctl start cups.path
  touch /var/cache/cups/org.cups.cupsd
  sleep 1
  rm /var/cache/cups/org.cups.cupsd
  sleep 1
  systemctl stop cups.service
  echo $?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:

  Date: Fri Nov 18 11:13:15 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-05-02 (200 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: device for mallards-officejet-pro-8600: 
dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461
  MachineType: Dell Inc. XPS 15 9550
  Papersize: a4
  PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/+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 1434986] Re: Not working network connection after boot

2017-02-16 Thread Erwin van Diermen

Same problem after upgrade from 14.04 to 16.04. (Dell Precision M4700)
After reboot, ifconfig displays IP address and all seems well. Connecting to 
local IP works, but internet fails.
I found another workaround by adding eth0 configuration to the 
/etc/network/interfaces, then, after reboot I stop the network manager: service 
network-manager stop
then: ifdown eth0
then: ifup eth0
and internet works. So, seems indeed a DNS problem.

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

Title:
  Not working network connection after boot

Status in NetworkManager:
  Expired
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Directly after boot the network connections are not working. I am
  connected and have an IP address, but I cannot establish a connection
  with any Internet server.

  I have the impression it is related to thee DNS lookup, which waits
  forever for a result.

  Cycling the connection (disconnect->reconnect) seems to fix the
  problem for some time.

  I am reporting this against network-manager, but I am not sure if it is 
directly in network manager or if it is systemd related.
  With 14.10 everything worked perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Mar 22 12:38:26 2015
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-01-30 (50 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static  metric 1024 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.26 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.29
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago)
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-02-16T00:14:50.662693
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION CON-UUID  CON-PATH   

   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Kabelnetzwerkverbindung 1  4a581685-6002-4401-a993-49aa649667eb  
/org/freedesktop/NetworkManager/ActiveConnection/4 
   wlan0   wifi  connected  /org/freedesktop/NetworkManager/Devices/1  
4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1434986/+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 1665418] Re: package libcairo-perl 1.106-1build1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuratio

2017-02-16 Thread Florian Schlichting

unfortunately, apport didn't include much info about why this error
occurs; could you try running 'sudo apt-get install -f', or any of the
solutions mentioned at http://askubuntu.com/questions/148715/how-to-fix-
package-is-in-a-very-bad-inconsistent-state-error

** Changed in: libcairo-perl (Ubuntu)
   Status: New => Incomplete

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

Title:
  package libcairo-perl 1.106-1build1 failed to install/upgrade: package
  is in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in libcairo-perl package in Ubuntu:
  Incomplete

Bug description:
  tried to update the package using ubuntu software updater

  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  libcairo-perl:
Installed: 1.106-1build1
Candidate: 1.106-1build1
Version table:
   *** 1.106-1build1 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libcairo-perl 1.106-1build1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Feb 16 18:49:21 2017
  DpkgHistoryLog:
   Start-Date: 2017-02-16  18:49:05
   Commandline: aptdaemon role='role-commit-packages' sender=':1.64'
   Install: snap-confine:amd64 (2.21, automatic)
   Upgrade: ubuntu-core-launcher:amd64 (1.0.27.1, 2.21)
  DuplicateSignature:
   package:libcairo-perl:1.106-1build1
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package libcairo-perl (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-08-10 (190 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: libcairo-perl
  Title: package libcairo-perl 1.106-1build1 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcairo-perl/+bug/1665418/+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 743176] Re: Pink layer on taken screenshots (gnome-screenshot)

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

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

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

Title:
  Pink layer on taken screenshots (gnome-screenshot)

Status in gnome-flashback package in Ubuntu:
  New
Status in gnome-screenshot package in Ubuntu:
  New
Status in gnome-utils package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: gnome-utils

  After having taken a screenshot of a part of my screen (gnome-
  screenshot) which is marked/shown by a pink layer, this pink layer can
  be seen on the screenshot itself.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: gnome-screenshot 2.32.0-0ubuntu4
  ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
  Uname: Linux 2.6.38-7-generic x86_64
  Architecture: amd64
  Date: Sat Mar 26 16:19:48 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110316)
  ProcEnviron:
   LANGUAGE=de_DE:en
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/743176/+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 1089069] Re: When taking a screenshot sometimes the image will look orange-colored

Is this a duplicate of #743176?

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

Title:
  When taking a screenshot sometimes the image will look orange-colored

Status in gnome-screenshot package in Ubuntu:
  Confirmed

Bug description:
  When taking a screenshot (and specially when taking a "selective"
  screenshot trough Shift+PrtScr) the resulting image will have this
  orange filter over it (the one that shows when one makes a screenshot
  of a part of the screen)

  I repeat: this will happen when taking a screenshot of a selection of
  the screen but also when taking a screenshot of the full screen.

  Shutter on the other hand displays no such behavior.

  I'm using Ubuntu 12.04.

  Regards.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1089069/+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 1655839] Re: [FTBFS] amd64 build of heimdal 7.1.0+dfsg-9 FAIL: test_rfc3961

2017-02-16 Thread Nish Aravamudan

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

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

Title:
  [FTBFS] amd64 build of heimdal 7.1.0+dfsg-9  FAIL: test_rfc3961

Status in heimdal package in Ubuntu:
  Confirmed
Status in libtool package in Ubuntu:
  New

Bug description:
  A few builds have failed: amd64, ppc64el & s390x for Zesty proposed

  for example amd64 fails on test_rfc3961

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1655839/+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 1664746] Re: Request for sponsorship for new upstream release (zesty deb provided)

2017-02-16 Thread Francesco Fumanti

** Attachment removed: "onboard-defaults.conf"
   
https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1664746/+attachment/4820415/+files/onboard-defaults.conf

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

Title:
  Request for sponsorship for new upstream release (zesty deb provided)

Status in onboard package in Ubuntu:
  Incomplete

Bug description:
  Version 1.4.0 of Onboard has been released upstream several hours ago.
  I am proposing here a debianisation of the new version, based on
  onboard version currently shipping in the Ubuntu main repository.
  These are the main changes of the new Onboard version, copied from the
  relevant part of the debian/changelog:

    * Request for sponsorship for new upstream release (LP: #1664746)
    * debian/control:
  - Add libudev-dev to Build-Depends
    * debian/copyright.in:
  - Replaced by a more accurate, manually adjusted copyright file
    * debian/onboard.install:
  - Remove settings_auto_show_dialog.ui entry
    * debian/patches/add_defaults_for_ubuntu.patch:
  - Update system-theme-associations example key
  - Add DEP3 tag
  - Refresh
    * debian/source.lintian-overrides:
  - Create file
  - Override 2 missing-license-paragraph-in-dep5-copyright entries
    * Tablet-mode: (LP: #1366421)
  - Add detection based on acpid reporting the SW_TABLET_MODE switch
  - Add detection based on hotkey events from XInput
  - Add detection by reading tablet-mode state from a few known sysfs paths
  - Add option to the Auto-show page to auto-show Onboard only in 
tablet-mode
  - Only run GlobalKeyListener when necessary
  - Add tablet-mode settings to Preferences->Auto-show->Convertibles
    * GNOME Shell:
  - Add edge-drag gesture to show the keyboard in GNOME Shell
  - Add option to gnome-shell-extension-prefs to disable edge-drag
  - Enable auto-show only on first start (LP: #1650810)
  - Fix setup.py to have distutils-extra not open extension dir as a file
  - Stop the legacy icon panel from sliding in and out all the time
  - Add license and copyright header to gschema.xml
  - Fix broken string in prefs.js
  - Fix copyright information in prefs.js
  - Clean up prefs.js
  - Remove debug output
    * Auto-show:
  - Refactor settings_auto_show_dialog.ui into new Auto-show preferences 
page
  - Improve reliability in Unity Dash by reacting only to crucial events
  - Add D-Bus property AutoShowPaused for convertible devices (LP: #1366421)
  - Allow to block auto-show while external keyboards are connected
  - Don't auto-hide while keys are still pressed.
    * External keyboard detection:
  - Detect keyboards with udev
  - Add new preference subpage Preferences->Auto-show->External Keyboards
  - Allow devices to be ignored; e.g. always connected keyboard
    * onboard-autostart.desktop: (LP #1656779)
  - Rename it to onboard-autostart.desktop.in
  - Add _GenericName, _Comment and Icon keys
  - Make it translatable
    * Move listening for global key presses to new GlobalKeyListener.py file
    * Have separate resize protection preference for floating icon and keyboard
    * Add scale for label popup size to Preferences->Keyboard
    * Switch position of "play sound" and "label popups" in Preferences-Keyboard
    * Add MATE'S ContrastHighInverse to the map of known accessibility themes
    * Replace deprecated GdkScreen.get_monitor_workarea()
    * Delay visibility change via D-Bus until all keys are released (LP: 
#1648543)
    * Indicate in log when Onboard has been started from the project directory
    * Rename tools/socket.py to tools/xembed_socket.py to avoid name collision
    * Reorganize AtspiStateTracker for saner handling of multiple accessibles
    * Update licensing tool for gnome shell extension
    * Explicitely clean up Applndicator status icon on exit
    * Improve error handling when opening layouts files
    * Work around firefox 50 urlbar losing focus and giving wrong caret position
    * Work around broken transparency with Gtk 3.22 (Lp: #1636252)
    * Work around byobu not reporting trailing spaces
    * Fix -Wstrict-prototypes warning when building C++ extension lm
    * Fix negative keyboard window size when screen says zero size (LP: 
#1633284)
    * Fix geometry hints for minimum size calculation error on startup
    * Fix startup failure on Arch Linux when libdbus-glib isn't installed
    * Fix signed/unsigned comparison warnings when building in Arch Linux
    * Make sure to hide label popups when the keyboard is hidden
    * Ease adjustment of aspect ratio with more handles when docked and expanded
    * Keep more distance when auto-positioning to the Dash search entry
    * Enable docking by default in onboard-defaults.conf.example
    * Update build instructions in README for

[Desktop-packages] [Bug 1664746] Re: Request for sponsorship for new upstream release (zesty deb provided)

2017-02-16 Thread marmuta

OK, done from my side, I believe. All essential keys are in gsettings now and a 
few issues without system defaults file are fixed. You're free to use gsettings 
overrides only. Changes here:
http://bazaar.launchpad.net/~onboard/onboard/trunk/revision/2251

@Francesco, better don't use onboard-defaults.conf as a guide anymore. I
made some of the values project defaults and one has to take care of
slight differences in the syntax between onboard-defaults.conf and
override files. Also "superkey-label" and "superkey-label-independent-
size" have to be replaced with the "key-label-overrides".

I recommend taking this new example as a guide:
https://bazaar.launchpad.net/~onboard/onboard/trunk/view/head:/onboard-default-settings.gschema.override.example

You should be able to paste its contents right into e.g. ubuntu-settings
.gsettings-override.

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

Title:
  Request for sponsorship for new upstream release (zesty deb provided)

Status in onboard package in Ubuntu:
  Incomplete

Bug description:
  Version 1.4.0 of Onboard has been released upstream several hours ago.
  I am proposing here a debianisation of the new version, based on
  onboard version currently shipping in the Ubuntu main repository.
  These are the main changes of the new Onboard version, copied from the
  relevant part of the debian/changelog:

    * Request for sponsorship for new upstream release (LP: #1664746)
    * debian/control:
  - Add libudev-dev to Build-Depends
    * debian/copyright.in:
  - Replaced by a more accurate, manually adjusted copyright file
    * debian/onboard.install:
  - Remove settings_auto_show_dialog.ui entry
    * debian/patches/add_defaults_for_ubuntu.patch:
  - Update system-theme-associations example key
  - Add DEP3 tag
  - Refresh
    * debian/source.lintian-overrides:
  - Create file
  - Override 2 missing-license-paragraph-in-dep5-copyright entries
    * Tablet-mode: (LP: #1366421)
  - Add detection based on acpid reporting the SW_TABLET_MODE switch
  - Add detection based on hotkey events from XInput
  - Add detection by reading tablet-mode state from a few known sysfs paths
  - Add option to the Auto-show page to auto-show Onboard only in 
tablet-mode
  - Only run GlobalKeyListener when necessary
  - Add tablet-mode settings to Preferences->Auto-show->Convertibles
    * GNOME Shell:
  - Add edge-drag gesture to show the keyboard in GNOME Shell
  - Add option to gnome-shell-extension-prefs to disable edge-drag
  - Enable auto-show only on first start (LP: #1650810)
  - Fix setup.py to have distutils-extra not open extension dir as a file
  - Stop the legacy icon panel from sliding in and out all the time
  - Add license and copyright header to gschema.xml
  - Fix broken string in prefs.js
  - Fix copyright information in prefs.js
  - Clean up prefs.js
  - Remove debug output
    * Auto-show:
  - Refactor settings_auto_show_dialog.ui into new Auto-show preferences 
page
  - Improve reliability in Unity Dash by reacting only to crucial events
  - Add D-Bus property AutoShowPaused for convertible devices (LP: #1366421)
  - Allow to block auto-show while external keyboards are connected
  - Don't auto-hide while keys are still pressed.
    * External keyboard detection:
  - Detect keyboards with udev
  - Add new preference subpage Preferences->Auto-show->External Keyboards
  - Allow devices to be ignored; e.g. always connected keyboard
    * onboard-autostart.desktop: (LP #1656779)
  - Rename it to onboard-autostart.desktop.in
  - Add _GenericName, _Comment and Icon keys
  - Make it translatable
    * Move listening for global key presses to new GlobalKeyListener.py file
    * Have separate resize protection preference for floating icon and keyboard
    * Add scale for label popup size to Preferences->Keyboard
    * Switch position of "play sound" and "label popups" in Preferences-Keyboard
    * Add MATE'S ContrastHighInverse to the map of known accessibility themes
    * Replace deprecated GdkScreen.get_monitor_workarea()
    * Delay visibility change via D-Bus until all keys are released (LP: 
#1648543)
    * Indicate in log when Onboard has been started from the project directory
    * Rename tools/socket.py to tools/xembed_socket.py to avoid name collision
    * Reorganize AtspiStateTracker for saner handling of multiple accessibles
    * Update licensing tool for gnome shell extension
    * Explicitely clean up Applndicator status icon on exit
    * Improve error handling when opening layouts files
    * Work around firefox 50 urlbar losing focus and giving wrong caret position
    * Work around broken transparency with Gtk 3.22 (Lp: #1636252)
    * Work around byobu not reporting trailing spaces
    * Fix

[Desktop-packages] [Bug 1406538] Re: Screenshot contains selected area highlight

Is this different from #743176?

I considered marking it as a duplicate, but there seems to be more
recent development work here.

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

Title:
  Screenshot contains selected area highlight

Status in Linux Mint:
  Confirmed
Status in gnome-screenshot package in Ubuntu:
  Confirmed
Status in mate-utils package in Ubuntu:
  Fix Committed

Bug description:
  mate-utils_1.8.1-0+rebecca_amd64
  If i choose "select area to grab" i almost constantly get an annoying green 
overlay which is what i just used to highlight the area that i wanted to grab.
  See attached example.
  I'm using Mint MATE x64 17.1, software compositing window manager enabled, 
compiz disabled, VGA AMD radeon 6370M, drivers "xserver-xorg-video-ati" 
7.3.0-1-ubuntu3.1, kernel 3.13.0-37-generic x86_64. 
  I remember this happening since mint 13 or so.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linuxmint/+bug/1406538/+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 762241] Re: gnome-screenshot does not get rid of (orange) selection window in final "Select area to grab" screenshots

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

** This bug has been marked a duplicate of bug 743176
   Pink layer on taken screenshots (gnome-screenshot)

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

Title:
  gnome-screenshot does not get rid of (orange) selection window in
  final "Select area to grab" screenshots

Status in gnome-utils package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gnome-utils

  When I use the "Select area to grab" option to take a screenshot, the
  final saved screenshot still has the orange selection window in it.
  (See screenshot.)

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: gnome-screenshot 2.32.0-0ubuntu4
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Fri Apr 15 18:02:08 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110329.1)
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-utils/+bug/762241/+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 1598300] Re: CUPS web interface stops responding after a while

I've let the new version of cups which fixes bug 1642966, into the
-proposed pocket for Xenial. My thought was that people would be
upgrading from 2.1.3-4 to 2.1.3-4ubuntu0.2 which contains the fix for
both bugs.

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

Title:
  CUPS web interface stops responding after a while

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

Bug description:
  after 6 minutes or so, cups is not responding.
  it do not produce error on the log, just stop working, worse, it exit with 0

  
⌌—⌍
  |root@cupsmachine :~# systemctl status cups   
|
  |● cups.service - CUPS Scheduler  
|
  |   Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: 
enabled)|
  |   Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago 
|
  | Docs: man:cupsd(8)  
|
  |  Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, 
status=0/SUCCESS)|
  | Main PID: 28686 (code=exited, status=0/SUCCESS) 
|
  | 
|
  |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler.   
|
  
⌎—⌏

  I got to launch it again, so I have finish with a cron job like
  */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && 
systemctl start cups

  but it is a dirty solution. I have no idea of what make it stop.
  NB: I have seen problems related to apparmor, this machine has no apparmor 
package.

  [Impact]

  If you want to use the CUPS web interface in Xenial and therefore set
  "WebInterface Yes" in /etc/cups/cupsd.conf, CUPS could auto-shutdown
  when it is idle and then an attempt to access http://localhost:631/
  via a web browser fails. People get confused as other access to CUPS

  [Testcase]

  Take a CUPS setup on Xenial with no shared print queues and CUPS only
  listening on the domain socket. Activate the web interface via

  cupsctl WebInterface=Yes

  Now you are able to access the web interface via
  http://localhost:631/. Wait for some minutes without accessing CUPS
  until the CUPS daemon shuts down automatically. Try to open the web
  interface again and it will not work.

  With the fixed CUPS package CUPS will not auto-shutdown when the web
  interface is activated.

  [Regression Potential]

  Low, as we are removing a simple distro patch to get back to the
  original, upstream behavior.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1598300/+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 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

Hello Mark, or anyone else affected,

Accepted cups into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/cups/2.1.3-4ubuntu0.2
in a few hours, and then in the -proposed repository.

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

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

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

** Changed in: cups (Ubuntu Xenial)
   Status: Triaged => Fix Committed

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  Fix Committed
Status in cups source package in Yakkety:
  Fix Committed
Status in cups source package in Zesty:
  Fix Released

Bug description:
  This is in xenial-proposed, please block release to -updates
  accordingly :)

  [Impact]
  * fail to upgrade

  [testcase]
  Root cause is believed to be reproducible with:

  #!/bin/bash
  systemctl stop cups.path cups.service
  rm /var/cache/cups/org.cups.cupsd
  systemctl start cups.path
  touch /var/cache/cups/org.cups.cupsd
  sleep 1
  rm /var/cache/cups/org.cups.cupsd
  sleep 1
  systemctl stop cups.service
  echo $?

  
  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:

  Date: Fri Nov 18 11:13:15 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-05-02 (200 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: device for mallards-officejet-pro-8600: 
dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461
  MachineType: Dell Inc. XPS 15 9550
  Papersize: a4
  PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/+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 1621971] Please test proposed package

Hello Jeremy, or anyone else affected,

Accepted gnome-software into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.20.1+git20170208.0.a34b091-0ubuntu1~xenial1 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!

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

Title:
  Add handler for snap: URLs

Status in gnome-software package in Ubuntu:
  Triaged
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  We want GNOME Software to be able to open snap:// URLs. This allows us to 
embed links in webpages to snaps (like apt://).

  [Test Case]
  1. Run xdg-open snap://moon-buggy

  Observed result:
  Get error about unknown URL.

  Expected result:
  GNOME Software is opened showing the information for moon-buggy and ability 
to install.

  [Regression Potential]
  Backported change from master has potential to break other URL handling. 
Other URLs tested (apt:// appstream://) to confirm they still work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1621971/+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 1621971] Re: Add handler for snap: URLs

Hello Jeremy, or anyone else affected,

Accepted gnome-software into yakkety-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.20.1+git20170208.0.a34b091-0ubuntu1 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 on 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: gnome-software (Ubuntu Yakkety)
   Status: Triaged => Fix Committed

** Tags added: verification-needed

** Changed in: gnome-software (Ubuntu Xenial)
   Status: Triaged => Fix Committed

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

Title:
  Add handler for snap: URLs

Status in gnome-software package in Ubuntu:
  Triaged
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  We want GNOME Software to be able to open snap:// URLs. This allows us to 
embed links in webpages to snaps (like apt://).

  [Test Case]
  1. Run xdg-open snap://moon-buggy

  Observed result:
  Get error about unknown URL.

  Expected result:
  GNOME Software is opened showing the information for moon-buggy and ability 
to install.

  [Regression Potential]
  Backported change from master has potential to break other URL handling. 
Other URLs tested (apt:// appstream://) to confirm they still work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1621971/+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 1662749] Re: GNOME Software has entry in Startup Applications

Hello Robert, or anyone else affected,

Accepted gnome-software into yakkety-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.20.1+git20170208.0.a34b091-0ubuntu1 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 on 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: gnome-software (Ubuntu Yakkety)
   Status: Triaged => Fix Committed

** Tags added: verification-needed

** Changed in: gnome-software (Ubuntu Xenial)
   Status: Triaged => Fix Committed

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

Title:
  GNOME Software has entry in Startup Applications

Status in GNOME Software:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  GNOME Software shows in the startup applications list and can be disabled. 
This is a feature that should not be easily disabled by the user.

  [Test Case]
  1. Open Startup Applications

  Expected result:
  GNOME Software is not shown

  Observed result:
  GNOME Software is shown and can be disabled.

  [Regression Potential]
  Low - this just hides this entry.

  If a user had disabled the gnome-software service from automatically starting 
in the background, it will now be more difficult to re-enable it.
  rm ~/.config/autostart/gnome-software-service.desktop

  The gnome-software service is a bit heavy (LP: #1592678) so some users
  do disable it. The downside is that by disabling it, the Software app
  takes much longer to start.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1662749/+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 1662750] Re: Remove 3rd party / non-free license warnings and just show license as Unknown

Hello Robert, or anyone else affected,

Accepted gnome-software into yakkety-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.20.1+git20170208.0.a34b091-0ubuntu1 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 on 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: gnome-software (Ubuntu Yakkety)
   Status: Triaged => Fix Committed

** Tags added: verification-needed

** Changed in: gnome-software (Ubuntu Xenial)
   Status: Triaged => Fix Committed

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

Title:
  Remove 3rd party / non-free license warnings and just show license as
  Unknown

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  GNOME Software currently shows a large warning about software being 3rd party 
/ non-free when the license information is shown. This is occurring for all 
snaps due to bug 167. This is misleading and would be simpler to just state 
the license is "Unknown".

  [Test Case]
  1. Open GNOME Software and select a snap (e.g. moon-buggy)

  Expected result:
  moon-buggy is shown with an unknown license.

  Observed result:
  A large warning is shown about it being 3rd party / non-free.

  [Regression potential]
  Low. We now hide the warning and show the license field even when it is 
unkown.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1662750/+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 1662749] Please test proposed package

Hello Robert, or anyone else affected,

Accepted gnome-software into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.20.1+git20170208.0.a34b091-0ubuntu1~xenial1 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!

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

Title:
  GNOME Software has entry in Startup Applications

Status in GNOME Software:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  GNOME Software shows in the startup applications list and can be disabled. 
This is a feature that should not be easily disabled by the user.

  [Test Case]
  1. Open Startup Applications

  Expected result:
  GNOME Software is not shown

  Observed result:
  GNOME Software is shown and can be disabled.

  [Regression Potential]
  Low - this just hides this entry.

  If a user had disabled the gnome-software service from automatically starting 
in the background, it will now be more difficult to re-enable it.
  rm ~/.config/autostart/gnome-software-service.desktop

  The gnome-software service is a bit heavy (LP: #1592678) so some users
  do disable it. The downside is that by disabling it, the Software app
  takes much longer to start.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1662749/+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 1662750] Please test proposed package

Hello Robert, or anyone else affected,

Accepted gnome-software into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.20.1+git20170208.0.a34b091-0ubuntu1~xenial1 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!

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

Title:
  Remove 3rd party / non-free license warnings and just show license as
  Unknown

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  GNOME Software currently shows a large warning about software being 3rd party 
/ non-free when the license information is shown. This is occurring for all 
snaps due to bug 167. This is misleading and would be simpler to just state 
the license is "Unknown".

  [Test Case]
  1. Open GNOME Software and select a snap (e.g. moon-buggy)

  Expected result:
  moon-buggy is shown with an unknown license.

  Observed result:
  A large warning is shown about it being 3rd party / non-free.

  [Regression potential]
  Low. We now hide the warning and show the license field even when it is 
unkown.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1662750/+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 1664746] Re: Request for sponsorship for new upstream release (zesty deb provided)

2017-02-16 Thread Francesco Fumanti

The onboard-defaults.conf file I just uploaded is the file that the
patch of the debianisation for ubuntu uploaded here adds to the onboard
installation. It can be used to extract the values for the ubuntu-
settings package.

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

Title:
  Request for sponsorship for new upstream release (zesty deb provided)

Status in onboard package in Ubuntu:
  Incomplete

Bug description:
  Version 1.4.0 of Onboard has been released upstream several hours ago.
  I am proposing here a debianisation of the new version, based on
  onboard version currently shipping in the Ubuntu main repository.
  These are the main changes of the new Onboard version, copied from the
  relevant part of the debian/changelog:

    * Request for sponsorship for new upstream release (LP: #1664746)
    * debian/control:
  - Add libudev-dev to Build-Depends
    * debian/copyright.in:
  - Replaced by a more accurate, manually adjusted copyright file
    * debian/onboard.install:
  - Remove settings_auto_show_dialog.ui entry
    * debian/patches/add_defaults_for_ubuntu.patch:
  - Update system-theme-associations example key
  - Add DEP3 tag
  - Refresh
    * debian/source.lintian-overrides:
  - Create file
  - Override 2 missing-license-paragraph-in-dep5-copyright entries
    * Tablet-mode: (LP: #1366421)
  - Add detection based on acpid reporting the SW_TABLET_MODE switch
  - Add detection based on hotkey events from XInput
  - Add detection by reading tablet-mode state from a few known sysfs paths
  - Add option to the Auto-show page to auto-show Onboard only in 
tablet-mode
  - Only run GlobalKeyListener when necessary
  - Add tablet-mode settings to Preferences->Auto-show->Convertibles
    * GNOME Shell:
  - Add edge-drag gesture to show the keyboard in GNOME Shell
  - Add option to gnome-shell-extension-prefs to disable edge-drag
  - Enable auto-show only on first start (LP: #1650810)
  - Fix setup.py to have distutils-extra not open extension dir as a file
  - Stop the legacy icon panel from sliding in and out all the time
  - Add license and copyright header to gschema.xml
  - Fix broken string in prefs.js
  - Fix copyright information in prefs.js
  - Clean up prefs.js
  - Remove debug output
    * Auto-show:
  - Refactor settings_auto_show_dialog.ui into new Auto-show preferences 
page
  - Improve reliability in Unity Dash by reacting only to crucial events
  - Add D-Bus property AutoShowPaused for convertible devices (LP: #1366421)
  - Allow to block auto-show while external keyboards are connected
  - Don't auto-hide while keys are still pressed.
    * External keyboard detection:
  - Detect keyboards with udev
  - Add new preference subpage Preferences->Auto-show->External Keyboards
  - Allow devices to be ignored; e.g. always connected keyboard
    * onboard-autostart.desktop: (LP #1656779)
  - Rename it to onboard-autostart.desktop.in
  - Add _GenericName, _Comment and Icon keys
  - Make it translatable
    * Move listening for global key presses to new GlobalKeyListener.py file
    * Have separate resize protection preference for floating icon and keyboard
    * Add scale for label popup size to Preferences->Keyboard
    * Switch position of "play sound" and "label popups" in Preferences-Keyboard
    * Add MATE'S ContrastHighInverse to the map of known accessibility themes
    * Replace deprecated GdkScreen.get_monitor_workarea()
    * Delay visibility change via D-Bus until all keys are released (LP: 
#1648543)
    * Indicate in log when Onboard has been started from the project directory
    * Rename tools/socket.py to tools/xembed_socket.py to avoid name collision
    * Reorganize AtspiStateTracker for saner handling of multiple accessibles
    * Update licensing tool for gnome shell extension
    * Explicitely clean up Applndicator status icon on exit
    * Improve error handling when opening layouts files
    * Work around firefox 50 urlbar losing focus and giving wrong caret position
    * Work around broken transparency with Gtk 3.22 (Lp: #1636252)
    * Work around byobu not reporting trailing spaces
    * Fix -Wstrict-prototypes warning when building C++ extension lm
    * Fix negative keyboard window size when screen says zero size (LP: 
#1633284)
    * Fix geometry hints for minimum size calculation error on startup
    * Fix startup failure on Arch Linux when libdbus-glib isn't installed
    * Fix signed/unsigned comparison warnings when building in Arch Linux
    * Make sure to hide label popups when the keyboard is hidden
    * Ease adjustment of aspect ratio with more handles when docked and expanded
    * Keep more distance when auto-positioning to the Dash search entry
    * Enable docking by default in

[Desktop-packages] [Bug 1664746] Re: Request for sponsorship for new upstream release (zesty deb provided)

2017-02-16 Thread Francesco Fumanti

** Attachment added: "onboard-defaults.conf"
   
https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1664746/+attachment/4820415/+files/onboard-defaults.conf

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

Title:
  Request for sponsorship for new upstream release (zesty deb provided)

Status in onboard package in Ubuntu:
  Incomplete

Bug description:
  Version 1.4.0 of Onboard has been released upstream several hours ago.
  I am proposing here a debianisation of the new version, based on
  onboard version currently shipping in the Ubuntu main repository.
  These are the main changes of the new Onboard version, copied from the
  relevant part of the debian/changelog:

    * Request for sponsorship for new upstream release (LP: #1664746)
    * debian/control:
  - Add libudev-dev to Build-Depends
    * debian/copyright.in:
  - Replaced by a more accurate, manually adjusted copyright file
    * debian/onboard.install:
  - Remove settings_auto_show_dialog.ui entry
    * debian/patches/add_defaults_for_ubuntu.patch:
  - Update system-theme-associations example key
  - Add DEP3 tag
  - Refresh
    * debian/source.lintian-overrides:
  - Create file
  - Override 2 missing-license-paragraph-in-dep5-copyright entries
    * Tablet-mode: (LP: #1366421)
  - Add detection based on acpid reporting the SW_TABLET_MODE switch
  - Add detection based on hotkey events from XInput
  - Add detection by reading tablet-mode state from a few known sysfs paths
  - Add option to the Auto-show page to auto-show Onboard only in 
tablet-mode
  - Only run GlobalKeyListener when necessary
  - Add tablet-mode settings to Preferences->Auto-show->Convertibles
    * GNOME Shell:
  - Add edge-drag gesture to show the keyboard in GNOME Shell
  - Add option to gnome-shell-extension-prefs to disable edge-drag
  - Enable auto-show only on first start (LP: #1650810)
  - Fix setup.py to have distutils-extra not open extension dir as a file
  - Stop the legacy icon panel from sliding in and out all the time
  - Add license and copyright header to gschema.xml
  - Fix broken string in prefs.js
  - Fix copyright information in prefs.js
  - Clean up prefs.js
  - Remove debug output
    * Auto-show:
  - Refactor settings_auto_show_dialog.ui into new Auto-show preferences 
page
  - Improve reliability in Unity Dash by reacting only to crucial events
  - Add D-Bus property AutoShowPaused for convertible devices (LP: #1366421)
  - Allow to block auto-show while external keyboards are connected
  - Don't auto-hide while keys are still pressed.
    * External keyboard detection:
  - Detect keyboards with udev
  - Add new preference subpage Preferences->Auto-show->External Keyboards
  - Allow devices to be ignored; e.g. always connected keyboard
    * onboard-autostart.desktop: (LP #1656779)
  - Rename it to onboard-autostart.desktop.in
  - Add _GenericName, _Comment and Icon keys
  - Make it translatable
    * Move listening for global key presses to new GlobalKeyListener.py file
    * Have separate resize protection preference for floating icon and keyboard
    * Add scale for label popup size to Preferences->Keyboard
    * Switch position of "play sound" and "label popups" in Preferences-Keyboard
    * Add MATE'S ContrastHighInverse to the map of known accessibility themes
    * Replace deprecated GdkScreen.get_monitor_workarea()
    * Delay visibility change via D-Bus until all keys are released (LP: 
#1648543)
    * Indicate in log when Onboard has been started from the project directory
    * Rename tools/socket.py to tools/xembed_socket.py to avoid name collision
    * Reorganize AtspiStateTracker for saner handling of multiple accessibles
    * Update licensing tool for gnome shell extension
    * Explicitely clean up Applndicator status icon on exit
    * Improve error handling when opening layouts files
    * Work around firefox 50 urlbar losing focus and giving wrong caret position
    * Work around broken transparency with Gtk 3.22 (Lp: #1636252)
    * Work around byobu not reporting trailing spaces
    * Fix -Wstrict-prototypes warning when building C++ extension lm
    * Fix negative keyboard window size when screen says zero size (LP: 
#1633284)
    * Fix geometry hints for minimum size calculation error on startup
    * Fix startup failure on Arch Linux when libdbus-glib isn't installed
    * Fix signed/unsigned comparison warnings when building in Arch Linux
    * Make sure to hide label popups when the keyboard is hidden
    * Ease adjustment of aspect ratio with more handles when docked and expanded
    * Keep more distance when auto-positioning to the Dash search entry
    * Enable docking by default in onboard-defaults.conf.example
    * Update build instructions in README for

[Desktop-packages] [Bug 1619354] Re: [SRU] Upgrade network-manager-applet to latest point release

The Xenial upload has a bug number typo'ed in the changelog.

"Add patches showing wwan options after logout/in (LP: #165019)"

That's missing a 1 i.e. 1651019.

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

Title:
  [SRU] Upgrade network-manager-applet to latest point release

Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager-applet source package in Xenial:
  In Progress
Status in network-manager-applet source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  Several defects in network-manager-applet can lead to crashes under
  certain circumstance as tracked in errors.ubuntu.com, upstream stable
  bug fix release 1.2.6 should fix a big portion of the bugs while no
  feature is being added or changed.

  [Test Case]

  After upgrading to 1.2.6, crash cases should be lesser than previous,
  and no functional regression should be observed.

  [Regression Potential]

  Potential of causing regression is minimal as upstream fixes aren't
  significant in this small package during the stable branch
  maintenance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1619354/+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 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

Hello Mark, or anyone else affected,

Accepted cups into yakkety-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/cups/2.2.0-2ubuntu0.1
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 on 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: cups (Ubuntu Yakkety)
   Status: Triaged => Fix Committed

** Tags added: verification-needed

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  Triaged
Status in cups source package in Yakkety:
  Fix Committed
Status in cups source package in Zesty:
  Fix Released

Bug description:
  This is in xenial-proposed, please block release to -updates
  accordingly :)

  [Impact]
  * fail to upgrade

  [testcase]
  Root cause is believed to be reproducible with:

  #!/bin/bash
  systemctl stop cups.path cups.service
  rm /var/cache/cups/org.cups.cupsd
  systemctl start cups.path
  touch /var/cache/cups/org.cups.cupsd
  sleep 1
  rm /var/cache/cups/org.cups.cupsd
  sleep 1
  systemctl stop cups.service
  echo $?

  
  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:

  Date: Fri Nov 18 11:13:15 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-05-02 (200 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: device for mallards-officejet-pro-8600: 
dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461
  MachineType: Dell Inc. XPS 15 9550
  Papersize: a4
  PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/+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 1619354] Update Released

The verification of the Stable Release Update for network-manager-applet
has completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [SRU] Upgrade network-manager-applet to latest point release

Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager-applet source package in Xenial:
  In Progress
Status in network-manager-applet source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  Several defects in network-manager-applet can lead to crashes under
  certain circumstance as tracked in errors.ubuntu.com, upstream stable
  bug fix release 1.2.6 should fix a big portion of the bugs while no
  feature is being added or changed.

  [Test Case]

  After upgrading to 1.2.6, crash cases should be lesser than previous,
  and no functional regression should be observed.

  [Regression Potential]

  Potential of causing regression is minimal as upstream fixes aren't
  significant in this small package during the stable branch
  maintenance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1619354/+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 1619354] Re: [SRU] Upgrade network-manager-applet to latest point release

This bug was fixed in the package network-manager-applet -
1.2.6-0ubuntu1

---
network-manager-applet (1.2.6-0ubuntu1) yakkety; urgency=medium

  * Rebase to upstream 1.2.6 release (LP: #1619354)
  * Refreshed patches. Merged upstream and dropped:
- applet-fix-handling-of-802.1x-secrets-for-ethernet-c.patch
  * Add patches to fix showing wwan option after logout/in (LP: #1651019)
   - applet-re-add-broadband-devices-when-MM-becomes-avai.patch
   - device-broadband-check-that-the-ModemManager-is-actu.patch
   - device-broadband-use-define-for-devinfo-tag.patch

 -- Aron Xu   Thu, 12 Jan 2017 19:18:13 +0800

** Changed in: network-manager-applet (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] Upgrade network-manager-applet to latest point release

Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager-applet source package in Xenial:
  In Progress
Status in network-manager-applet source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  Several defects in network-manager-applet can lead to crashes under
  certain circumstance as tracked in errors.ubuntu.com, upstream stable
  bug fix release 1.2.6 should fix a big portion of the bugs while no
  feature is being added or changed.

  [Test Case]

  After upgrading to 1.2.6, crash cases should be lesser than previous,
  and no functional regression should be observed.

  [Regression Potential]

  Potential of causing regression is minimal as upstream fixes aren't
  significant in this small package during the stable branch
  maintenance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1619354/+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 1651019] Update Released

The verification of the Stable Release Update for network-manager-applet
has completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [SRU]nm-applet not show wwan options on menu after logout/in

Status in Network Manager Applet:
  Fix Released
Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager-applet source package in Xenial:
  In Progress
Status in network-manager-applet source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  With DW5811e(EM7455), mobile data connection not show on nm indicator
  after logout -> login.

  packages which be used:
  network-manager: network-manager_1.2.2-0ubuntu0.16.04.3_amd64
  nm-applet: network-manager-gnome_1.2.0-0ubuntu0.16.04.4_amd64

  Steps to reproduce:
  1. boot device with 4G sim card + DW5811e(EM7455) wwan card
  2. check nm-applet indicator then "Mobile Braodband" could be found in menu 
in normal cases.
  3. logout then login
  4. check nm-applet indicator then "Mobile Braodband" not shows in menu 
anymore.
  5. but still could connect to wwan by nmcli, so looks device and 
networkmanager work fine.

  [Test Case]

  After upgrading to 1.2.6, using the previous "Steps to reproduce"
  should not be able to reproduce the bug any more

  [Regression Potential]

  Potential of causing regression is minimal as upstream fixes aren't
  significant enough.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1651019/+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 1651019] Re: [SRU]nm-applet not show wwan options on menu after logout/in

This bug was fixed in the package network-manager-applet -
1.2.6-0ubuntu1

---
network-manager-applet (1.2.6-0ubuntu1) yakkety; urgency=medium

  * Rebase to upstream 1.2.6 release (LP: #1619354)
  * Refreshed patches. Merged upstream and dropped:
- applet-fix-handling-of-802.1x-secrets-for-ethernet-c.patch
  * Add patches to fix showing wwan option after logout/in (LP: #1651019)
   - applet-re-add-broadband-devices-when-MM-becomes-avai.patch
   - device-broadband-check-that-the-ModemManager-is-actu.patch
   - device-broadband-use-define-for-devinfo-tag.patch

 -- Aron Xu   Thu, 12 Jan 2017 19:18:13 +0800

** Changed in: network-manager-applet (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU]nm-applet not show wwan options on menu after logout/in

Status in Network Manager Applet:
  Fix Released
Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager-applet source package in Xenial:
  In Progress
Status in network-manager-applet source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  With DW5811e(EM7455), mobile data connection not show on nm indicator
  after logout -> login.

  packages which be used:
  network-manager: network-manager_1.2.2-0ubuntu0.16.04.3_amd64
  nm-applet: network-manager-gnome_1.2.0-0ubuntu0.16.04.4_amd64

  Steps to reproduce:
  1. boot device with 4G sim card + DW5811e(EM7455) wwan card
  2. check nm-applet indicator then "Mobile Braodband" could be found in menu 
in normal cases.
  3. logout then login
  4. check nm-applet indicator then "Mobile Braodband" not shows in menu 
anymore.
  5. but still could connect to wwan by nmcli, so looks device and 
networkmanager work fine.

  [Test Case]

  After upgrading to 1.2.6, using the previous "Steps to reproduce"
  should not be able to reproduce the bug any more

  [Regression Potential]

  Potential of causing regression is minimal as upstream fixes aren't
  significant enough.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1651019/+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 1665382] Re: File operation progress does not complete properly

2017-02-16 Thread Khurshid Alam

Ubuntu 16.10 uses nautilus 3.20 which is obsolete at upstream. Hell,
even 3.22 is going to be obsolete soon. Upstream never back-port fixes
to older version and newer version can not be compiled with older gtk
version on Ubuntu.

That's the problem users have to face as Ubuntu doesn't synchronize with
Gnome cycle (saying it's unstable) and lag 6 months behind!

I suggest you take it to the upstream if you can make them to provide a
patch for 3.20.

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

Title:
  File operation progress does not complete properly

Status in nautilus package in Ubuntu:
  New

Bug description:
  When copying files, a progress indicator button appears in the toolbar
  (round "cake" diagram). It also opens a popover that lists all file
  operations with a progress bar each.

  Unfortunately the popover 1) covers a huge part of the window, 2) it
  is opened on all nautilus windows on all workspaces, 3) the progress
  popover does not close on its own when the operations are completed
  (circle diagram shows full, but does not disappear) and 4) the unity
  launcher icon and alt-tab switcher continue displaying the full
  progress bar.

  Furthermore, the unconscious need to remove what covers your sight
  seduces the user to click the nearest "X" to close the popover.
  However, the "X" aborts file operations leading to corrupted,
  incompletely copied files. The correct way is to toggle the progress
  button. However, the toggle-off action is unintuitive because the user
  did not manually toggle it on.

  Expected behavior:
  Popover window opens when the user clicks the progress indicator button, and 
it only opens on the current workspace. After file operations complete, it 
closes on its own and the progress bar on the launcher icon disappears.

  Actual behavior:
  Popover window opens on all nautilus windows. After file operations complete, 
they do not close.

  Ubuntu 16.10
  nautilus 1:3.20.3-1ubuntu3.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1665382/+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 1665384] Re: OEM switch to end user results in wifi not being available.

2017-02-16 Thread Mathieu Trudel-Lapierre

This is most likely a ubiquity bug; where the connection is created with
the wrong permission settings.

** Package changed: network-manager (Ubuntu) => ubiquity (Ubuntu)

** Changed in: ubiquity (Ubuntu)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

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

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

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

Title:
  OEM switch to end user results in wifi not being available.

Status in ubiquity package in Ubuntu:
  Triaged

Bug description:
  STEPS:
  1. Grab the latest xenial iso from 
http://cdimages.ubuntu.com/xenial/daily-live/current/
  2. Install in oem mode
  3. In the OEM desktop double click on Prepare for end user type in your 
password and reboot
  4. Run through the end user wizard setting up wifi as you go
  5. Login to the end user session
  6. Note the empty Wifi symbol in indicator
  7. Run nmcli d and see something like
  DEVICE  TYPE  STATE CONNECTION
  enp3s0  ethernet  Unavailable   --
  wlo1wifi  Unavailable   --
  lo  loopback  Unmanagaed--

  WORKAROUND:
  reboot
  After reboot everything works as expected and the system autoconnects as 
expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1665384/+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 1029289] Re: Need to authorize my google account each time I boot the computer

2017-02-16 Thread PabloRQ

Hi! I can confirm that the issue appears when the 'Access your Google
Calendar' option is on.

Alberto, do you need a new bug to be filled when it seems to be a
regression?

Regards...

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

Title:
  Need to authorize my google account each time I boot the computer

Status in Online Accounts: Account plugins:
  Fix Released
Status in Online Accounts: Sign-on UI:
  Fix Released
Status in account-plugins package in Ubuntu:
  Fix Released
Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in signon-plugin-oauth2 package in Ubuntu:
  Fix Released
Status in account-plugins source package in Quantal:
  Fix Released
Status in signon-plugin-oauth2 source package in Quantal:
  Fix Released
Status in account-plugins source package in Trusty:
  Fix Released
Status in evolution-data-server source package in Trusty:
  Fix Released
Status in signon-plugin-oauth2 source package in Trusty:
  Fix Released

Bug description:
  [Impact] Google calendar integration is broken, and users are
  requested to re-enter their Google password everytime they log in, or
  everytime they enable/disable their Google account from the System
  Settings.

  [Test Case] Disable/re-enable your Google account. When affected by
  this bug, a notification will appear and you'll be asked to enter your
  Google password in the Online Accounts panel in System Settings.

  [Regression Potential] Minimal: the fix is a backport of a patch from
  the evolution-data-server code which is already in 14.10, and which
  only touches the calendar code (which is currently broken).


  Old description
  ===

  [Test Case] Sometimes after one day, sometimes after one week, the
  system indicator will turn red and the Google account will be marked
  as needing reauthentication. Time can vary, but any period shorter
  than one month is a symptom of the bug.

  [Regression Potential] Minimal: the change to the Google plugin (in
  account-plugins) simply changes the authentication method, in a way
  that is well-documented. The change in signon-plugin-oauth2 affects
  only those accounts/providers which use the OAuth refresh tokens --
  which is only Google, at the moment -- and in a way that can't
  possibly break any existing functionality; if the new code had some
  mistake, the refresh token would be unusable and the system would
  automatically fall back to requesting a new access token (which is
  exactly what happens now, with this bug).

  I'll try to find why the account-plugins package was not uploaded;
  indeed, both are required in order to fix this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/account-plugins/+bug/1029289/+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 1665432] [NEW] Error with cups-daemon package when reinstalling many packages to recover wireless connection with QCA9377

2017-02-16 Thread Leonardo Müller

Public bug reported:

I had a issue with my Wireless and Bluetooth card, Qualcomm Atheros
Device [168c:0042] (rev 30), which appears on Windows 10 as QCA9377, and
to solve it I have searched and tried different alternatives. The one
that worked was to reinstall many packages, all the ones I have found
when searching for, firstly, "wireless", then "wifi" and then
"internet", on synaptic. When doing the "internet" reinstall, a error
happened on cups-daemon and it crashed. When I tried again, it worked. I
rebooted the computer and the Wireless is functioning again (Bluetooth
was already OK).

I am using the Kernel 4.9.10-040910-generic from
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9.10/ because I was
trying to solve this issue and because the official Kernles 4.4 and 4.8
don't eject external HDDs from the USB 3.0 correctly. The notebook model
is Lenovo Ideapad 310-14ISK.

While this window to report the bug appeared saying cups is the culprit,
all this only happened because the wireless device QCA9377 was not
working.

usuario@usuario-Lenovo-ideapad-310-14ISK:~$ lsb_release -rd
Description:Ubuntu 16.04.2 LTS
Release:16.04

usuario@usuario-Lenovo-ideapad-310-14ISK:~$ uname -a
Linux usuario-Lenovo-ideapad-310-14ISK 4.9.10-040910-generic #201702141931 SMP 
Wed Feb 15 00:33:24 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

I hope this information may be helpful.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: cups-daemon 2.1.3-4
Uname: Linux 4.9.10-040910-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CupsErrorLog: W [16/Feb/2017:14:42:01 -0200] Notifier for subscription 298 
(dbus://) went away, retrying!
Date: Thu Feb 16 16:05:14 2017
ErrorMessage: sub-processo novo script pre-removal retornou estado de saída de 
erro 1
InstallationDate: Installed on 2016-12-31 (47 days ago)
InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lpstat: device for Deskjet-2050-J510-series: 
hp:/usb/Deskjet_2050_J510_series?serial=BR1C1FK1K005D1
MachineType: LENOVO 80UG
Papersize: a4
PpdFiles: Deskjet-2050-J510-series: HP Deskjet 2050 j510 Series, hpcups 3.16.3
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.9.10-040910-generic 
root=UUID=0fbb0f28-6764-4447-a890-dc966d1f8adf ro
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.10-040910-generic 
root=UUID=0fbb0f28-6764-4447-a890-dc966d1f8adf ro
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: cups
Title: package cups-daemon 2.1.3-4 failed to install/upgrade: sub-processo novo 
script pre-removal retornou estado de saída de erro 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/03/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: 0XCN37WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Toronto 4A2
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40679 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 310-14ISK
dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN37WW:bd10/03/2016:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
dmi.product.name: 80UG
dmi.product.version: Lenovo ideapad 310-14ISK
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-package xenial

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

Title:
  Error with cups-daemon package when reinstalling many packages to
  recover wireless connection with QCA9377

Status in cups package in Ubuntu:
  New

Bug description:
  I had a issue with my Wireless and Bluetooth card, Qualcomm Atheros
  Device [168c:0042] (rev 30), which appears on Windows 10 as QCA9377,
  and to solve it I have searched and tried different alternatives. The
  one that worked was to reinstall many packages, all the ones I have
  found when searching for, firstly, "wireless", then "wifi" and then
  "internet", on synaptic. When doing the "internet" reinstall, a error
  happened on cups-daemon and it crashed. When I tried again, it worked.
  I rebooted the computer and the Wireless is functioning again
  (Bluetooth was already OK).

  I am using the Kernel 4.9.10-040910-generic from
  http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9.10/ because I was
  trying to solve this issue and because the official Kernles 4.4 and
  4.8 don't eject external HDDs from the USB 3.0 correctly. The notebook
  model is Lenovo Ideapad 310-14ISK.

  While this window to report the bug appeared saying cups is the
  culprit, all this only happened because the wireless device QCA9377
  was not working.

  usuario@usuario-Lenovo-ideapad-310-14ISK:~$ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  usuario@usuario-Lenovo-ideapad-310-14ISK:~$ uname -a
  Linux usuario-Lenovo-ideapad-310-14ISK 4.9.10-040910-generic

[Desktop-packages] [Bug 1645698] Re: [SRU] Upgrade network-manager to latest point release

This bug was fixed in the package network-manager - 1.2.6-0ubuntu1

---
network-manager (1.2.6-0ubuntu1) yakkety; urgency=medium

  * Rebase to upstream point release 1.2.6 (LP: #1645698)
  * Refreshing patches, dropped ones that are merged upstream:
- wifi-clear-WiFi-requested_scan-if-suppl-exits.patch
- wifi-clear-WiFi-requested_scan-if-suppl-goes-INACTIV.patch

 -- Aron Xu   Tue, 20 Dec 2016 00:54:10 +0800

** Changed in: network-manager (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] Upgrade network-manager to latest point release

Status in OEM Priority Project:
  Triaged
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  This SRU would try to have the latest well-tested upstream point
  release (1.2.6) of 1.2.x land in Xenial, which is the successor of the
  current 1.2.2 version, fixing quite some bugs that's suitable to land
  in the stable branch.

  https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS?h=nm-1-2

  [Test Case]

  After installing the updated version, users should be able to avoid
  some mem leaks in some cases and have generally improved DNS related
  experiences.

  Also, as this is a general point release update, cases described in
  https://wiki.ubuntu.com/NetworkManager/DistroTesting should be used
  for smoke testing.

  [Regression Potential]

  This is a bug/regression fix for 1.2.2 and 1.2.4, which is quite
  complete.

  [Other Info]
  The first attempt at SRUing this to xenial was for 1.2.4 but it failed 
verification. This second attempt matches yakkety with 1.2.6.

  Parallel building was enabled in xenial to keep the diff between
  xenial and yakkety minimal since they are basically in sync now.
  Parallel building was enabled in the yakkety package in May 2016 so
  it's been working fine for a while.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1645698/+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 1645698] Update Released

The verification of the Stable Release Update for network-manager has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [SRU] Upgrade network-manager to latest point release

Status in OEM Priority Project:
  Triaged
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  This SRU would try to have the latest well-tested upstream point
  release (1.2.6) of 1.2.x land in Xenial, which is the successor of the
  current 1.2.2 version, fixing quite some bugs that's suitable to land
  in the stable branch.

  https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS?h=nm-1-2

  [Test Case]

  After installing the updated version, users should be able to avoid
  some mem leaks in some cases and have generally improved DNS related
  experiences.

  Also, as this is a general point release update, cases described in
  https://wiki.ubuntu.com/NetworkManager/DistroTesting should be used
  for smoke testing.

  [Regression Potential]

  This is a bug/regression fix for 1.2.2 and 1.2.4, which is quite
  complete.

  [Other Info]
  The first attempt at SRUing this to xenial was for 1.2.4 but it failed 
verification. This second attempt matches yakkety with 1.2.6.

  Parallel building was enabled in xenial to keep the diff between
  xenial and yakkety minimal since they are basically in sync now.
  Parallel building was enabled in the yakkety package in May 2016 so
  it's been working fine for a while.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1645698/+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 1665418] Re: package libcairo-perl 1.106-1build1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuratio

2017-02-16 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package libcairo-perl 1.106-1build1 failed to install/upgrade: package
  is in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in libcairo-perl package in Ubuntu:
  New

Bug description:
  tried to update the package using ubuntu software updater

  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  libcairo-perl:
Installed: 1.106-1build1
Candidate: 1.106-1build1
Version table:
   *** 1.106-1build1 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libcairo-perl 1.106-1build1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Feb 16 18:49:21 2017
  DpkgHistoryLog:
   Start-Date: 2017-02-16  18:49:05
   Commandline: aptdaemon role='role-commit-packages' sender=':1.64'
   Install: snap-confine:amd64 (2.21, automatic)
   Upgrade: ubuntu-core-launcher:amd64 (1.0.27.1, 2.21)
  DuplicateSignature:
   package:libcairo-perl:1.106-1build1
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package libcairo-perl (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-08-10 (190 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: libcairo-perl
  Title: package libcairo-perl 1.106-1build1 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcairo-perl/+bug/1665418/+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 1665418] [NEW] package libcairo-perl 1.106-1build1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurat

2017-02-16 Thread David

Public bug reported:

tried to update the package using ubuntu software updater

Description:Ubuntu 16.04.1 LTS
Release:16.04

libcairo-perl:
  Installed: 1.106-1build1
  Candidate: 1.106-1build1
  Version table:
 *** 1.106-1build1 500
500 http://nl.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libcairo-perl 1.106-1build1
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Thu Feb 16 18:49:21 2017
DpkgHistoryLog:
 Start-Date: 2017-02-16  18:49:05
 Commandline: aptdaemon role='role-commit-packages' sender=':1.64'
 Install: snap-confine:amd64 (2.21, automatic)
 Upgrade: ubuntu-core-launcher:amd64 (1.0.27.1, 2.21)
DuplicateSignature:
 package:libcairo-perl:1.106-1build1
 Processing triggers for man-db (2.7.5-1) ...
 dpkg: error processing package libcairo-perl (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2016-08-10 (190 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: libcairo-perl
Title: package libcairo-perl 1.106-1build1 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: libcairo-perl (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package libcairo-perl 1.106-1build1 failed to install/upgrade: package
  is in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in libcairo-perl package in Ubuntu:
  New

Bug description:
  tried to update the package using ubuntu software updater

  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  libcairo-perl:
Installed: 1.106-1build1
Candidate: 1.106-1build1
Version table:
   *** 1.106-1build1 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libcairo-perl 1.106-1build1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Feb 16 18:49:21 2017
  DpkgHistoryLog:
   Start-Date: 2017-02-16  18:49:05
   Commandline: aptdaemon role='role-commit-packages' sender=':1.64'
   Install: snap-confine:amd64 (2.21, automatic)
   Upgrade: ubuntu-core-launcher:amd64 (1.0.27.1, 2.21)
  DuplicateSignature:
   package:libcairo-perl:1.106-1build1
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package libcairo-perl (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-08-10 (190 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: libcairo-perl
  Title: package libcairo-perl 1.106-1build1 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcairo-perl/+bug/1665418/+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 1628792] Re: Add carddav scope to google-contacts.service (Zesty)

2017-02-16 Thread Khurshid Alam

Upstream-Bug: https://bugzilla.gnome.org/show_bug.cgi?id=778775

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

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

Title:
  Add carddav scope to google-contacts.service (Zesty)

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  It seems google-contacts.service file Google Contacts API (Gdata)
  https://www.google.com/m8/feeds/ which is NOT same as CardDav. As a
  result when some application( ex. Syncevolution) tries to access it
  (through oauth2), it gives “authentication failed error”.

  For example, running following command:

  '''

  SYNCEVOLUTION_DEBUG=1 syncevolution --print-databases –daemon=no\

  loglevel=2 backend=carddav username=uoa:3,google-contacts\

  syncURL=https://www.googleapis.com/.well-known/carddav

  '''
  gives following error:

   “헣헥헢헣헙헜헡헗: 헡헲헼헻 헲헿헿헼헿 헰헼헱헲 ퟭ: ퟰퟬퟯ 헙헼헿헯헶헱헱헲헻, 헺혂혀혁 헻헼혁 헿헲혁헿혆”

  Adding the carddav scope solves the issue.
  'https://www.googleapis.com/auth/carddav'

  evolution-data-server-online-accounts provides these files.

  Patch:

  --- a/modules/ubuntu-online-accounts/google-contacts.service.in.in
  +++ b/modules/ubuntu-online-accounts/google-contacts.service.in.in
  @@ -17,7 +17,7 @@
     https://localhost/
     796629365126-a2o58ak3l6nuk9bto6sr5aoku0vh5enc.apps.googleusercontent.com
     YVigZ5Po5p83_CrwQk-p5SwP
  -  ['https://www.googleapis.com/auth/userinfo.email','https://mail.google.com/','https://www.google.com/m8/feeds/','https://www.googleapis.com/auth/calendar']
  +  ['https://www.googleapis.com/auth/userinfo.email','https://mail.google.com/','https://www.google.com/m8/feeds/','https://www.googleapis.com/auth/calendar','https://www.googleapis.com/auth/carddav']]
   
     
   

  Note:

  1. Ubuntu already enabled carddav in google developer console
  (lp:1433943)

  2. It requires to grant access twice; one for UOA and one for
  Evolution (server side). Then only it works
  (https://bugs.launchpad.net/ubuntu/+source/unity-control-
  center/+bug/1522360)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1628792/+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 1393578] Re: Subpixel order not included in Mir display information

2017-02-16 Thread Gerry Boland

I've hacked qtmir to print the subpixel hint that Mir is supplying.

http://pastebin.ubuntu.com/24007971/ is my output. First I run a simple
qml demo shell as nested server under USC, get "0" hint.

Then I run again as host server, get a hint "1 = RGB".

The "Subpixel hint" output of the 2 cases do not match for me, hence the
complaint.

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

Title:
  Subpixel order not included in Mir display information

Status in Mir:
  In Progress
Status in QtMir:
  Triaged
Status in qtubuntu:
  Triaged
Status in mir package in Ubuntu:
  Triaged
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  Just capturing something mentioned by Trevinho on IRC this morning.
  MirDisplayOutput does not include subpixel ordering, it could and
  should though. The information is exposed on the drm side
  (drmModeSubPixel). Marking as wishlist in absence of other
  information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1393578/+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 1662617] Re: gnome-calculator with transparent formula entry box

2017-02-16 Thread SilvioBandeira

** Summary changed:

- gnome-calculator with formula entry box transparent
+ gnome-calculator with transparent formula entry box

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

Title:
  gnome-calculator with transparent formula entry box

Status in gnome-calculator package in Ubuntu:
  New

Bug description:
  I have a notebook and desktop running Ubuntu 16.10 with Unity... in both 
machines the gnome-calculator shows a transparent formula entry box.
  Installing the new version 2.23.4 solved the issue in the notebook but not in 
the desktop. 

  Desktop Graphic Card:

*-display
   description: VGA compatible controller
   product: Xeon E3-1200 v2/3rd Gen Core processor Graphics 
Controller
   vendor: Intel Corporation
   physical id: 2
   bus info: pci@:00:02.0
   version: 09
   width: 64 bits
   clock: 33MHz
   capabilities: vga_controller bus_master cap_list rom
   configuration: driver=i915 latency=0
   resources: irq:29 memory:f780-f7bf 
memory:e000-efff ioport:f000(size=64) memory:c-d

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1662617/+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 1665394] Re: DNS resolution of irc.freenode.net or chat.freenode.net fails

2017-02-16 Thread Schiggn

iputils/ping was wrong.

On machines with this bug a "getent hosts chat.freenode.net" results in
no output! Perhaps we have to look at getaddrinfo()!

Thanks to the french ubuntu-channel #ubuntu-fr for this hint :)

** No longer affects: iputils (Ubuntu)

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

Title:
  DNS resolution of irc.freenode.net or chat.freenode.net fails

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I am running Ubuntu 16.10 (from a base install upgraded several
  times), with proposed-updates enabled. Recently, I started having
  problems where I am unable to resolve irc.freenode.net.

  This is unrelated to the networks. I have been able to confirm that
  systemd-resolved is able to perform the name resolution. Yet,
  getaddrinfo() call returns -EAI_AGAIN error.

  This can be reproduced using getent:
  > $ getent ahosts irc.freenode.net
  > $

  While testing v4 or v6 directly returns something valid:
  > $ getent ahostsv4 irc.freenode.net
  > 38.229.70.22STREAM chat.freenode.net
  > 38.229.70.22DGRAM  
  > 38.229.70.22RAW
  > 130.239.18.119  STREAM 
  > 130.239.18.119  DGRAM  
  > 130.239.18.119  RAW
  [...]
  > $

  > $ getent ahostsv6 irc.freenode.net
  > 2001:5a0:3604:1:64:86:243:181 STREAM chat.freenode.net
  > 2001:5a0:3604:1:64:86:243:181 DGRAM  
  > 2001:5a0:3604:1:64:86:243:181 RAW
  > 2001:6b0:e:2a18::118 STREAM 
  > 2001:6b0:e:2a18::118 DGRAM  
  > 2001:6b0:e:2a18::118 RAW
  [...]
  > $

  dpkg.log shows there has been some upgrade of systemd recently, though
  I cannot tell for sure if that directly relates to the problem, I do
  use suspend-to-ram a lot and reboot not that often.

  > $ lsb_release -a
  > LSB Version:
core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:printing-9.20160110ubuntu5-amd64:printing-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
  > Distributor ID: Ubuntu
  > Description:Ubuntu 16.10
  > Release:16.10
  > Codename:   yakkety

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1665394/+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 1647283] Re: WiFi being detected as ethernet when race condition on renaming for persistent name

This bug was fixed in the package network-manager - 1.4.4-1ubuntu1

---
network-manager (1.4.4-1ubuntu1) zesty; urgency=medium

  * Rebase to upstream 1.4.4 release, base on Debian 1.4.4-1 (LP: #1647283)
  * Refresh patches, dropping ones that are included upstream:
- manager-fix-state-transition-on-resuming-from-sleep.patch
- wifi-notify-the-AccessPoint-change-after-an-AP-is-removed.patch
  * Updated patch:
- Ignore-p2p0-wifi-devices-from-android.patch:
  LOGD_HW is now LOGD_PLATFORM

 -- Aron Xu   Thu, 16 Feb 2017 18:35:11 +0800

** Changed in: network-manager (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  WiFi being detected as ethernet when race condition on renaming for
  persistent name

Status in HWE Next:
  New
Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project xenial series:
  New
Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  Forwarded https://bugzilla.gnome.org/show_bug.cgi?id=775613

  Version: NetworkManager 1.4.2

  This bug happens after power-on with probability about 1/50.
  That means we need to reboot about 50 times to get into the buggy situation.
  "nmcli d" shows the device type is ethernet:

  DEVICE   TYPE  STATECONNECTION
  wlp1s0   ethernet  unavailable  --
  lo   loopback  unmanaged--

  The bug starts from a race condition. But it is not the root cause.
  I've also attach 2 logs. One is in good situation. Another is in bad 
situation.
  This log is generated by applying a "log patch" to network-manager 1.4.2 so 
we can see more stuff.

  In the bad situation. The bug starts with race condition. But the race 
condition is not the root cause. The race condition is:
   * During the renaming from "wlan0" to "wlp1s0". "wlan0" disappeared.
   * Inside the NM, it is still using "wlan0" in "_linktype_get_type()".
   * Since /sys/class/net/wlan0/uevent is disappeared. so the type matching 
failed in _linktype_get_type().
   * Also wifi_utils_is_wifi() failed to because /sys/class/net/wlan0 
disappeared.
   * And finally, devtype and kind are both NULL, so it returns 
NM_LINK_TYPE_ETHERNET for wlan0.

  Later, wlan0 is renamed to wlp1s0, and it seems to me that the Object inherit 
the type so it is still type ethernet.
  But from the log, I saw _linktype_get_type() is called several times later 
and return the correct type (wifi). But just, "nmcli d" still shows type 
ethernet.

  I'm wondering if we are missing to update the type in the Object
  created after renaming and re-detecting the type.

  fix need landing LP: #1645698

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1647283/+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 1663062] Re: [regression] Software clients of nested servers with size >=480x480 are all black in Mir 0.25.0 and later (or stretched and distorted under Unity8)

This bug was fixed in the package mir - 0.26.1+17.04.20170209.1-0ubuntu1

---
mir (0.26.1+17.04.20170209.1-0ubuntu1) zesty; urgency=medium

  * New upstream release 0.26.1 (https://launchpad.net/mir/+milestone/0.26.1)
- ABI summary:
  . mirclient ABI unchanged at 9
  . mirserver ABI unchanged at 43
  . mircommon ABI unchanged at 7
  . mirplatform ABI bumped to 15
  . mirprotobuf ABI unchanged at 3
  . mirplatformgraphics ABI bumped to 12
  . mirclientplatform ABI unchanged at 5
  . mirinputplatform ABI unchanged at 6
  . mircore ABI unchanged at 1
- Enhancements:
  . Support for MirBuffer API that allows for better management of
hardware/software buffers.
  . Support for MirPresentationChain API that allows better control
over {de}queueing of individual buffers {from}to the server.
  . Interim support for MirRenderSurface API that provides a unit of
renderable for lower level content such as MirBufferStreams and
MirPresentationChains, etc.. MirRenderSurface API is marked
deprecated as it (and the relevant entry points) will be renamed to
MirSurface before general availability. It will initially be used for
revamping support for EGL drivers.
  . Synchronous version of mir_prompt_session_new_fds_for_prompt_providers()
API (mir_prompt_session_new_fds_for_prompt_providers_sync()) added for
convenience.
  . Better name for MirPersistentId-->MirWindowId. MirPersistentId has now
been deprecated.
- Bugs fixed:
  . [regression] Unity8 stutters constantly (like half frame rate).
(LP: #1661128)
  . mir 0.26 - spinner loading animation, minimize, maximize too fast.
(LP: #1661072)
  . [regression] Nested server segfaults or rapidly logs exceptions when a
fullscreen client starts [in mir_presentation_chain_set_dropping_mode
... std::exception::what: Operation not permitted] (LP: #1661508)
  . mir_window_request_persistent_id_sync seg faults when called twice.
(LP: #1661704)
  . [regression] Windowed clients of nested servers are all black.
(LP: #1661521)
  . Mir graphics platform ABI broke in series 0.26 but sonames never
changed (LP: #1662455)
  . Fixes for 0.26 changelog.
  . [regression] mirscreencast hangs during screencast creation. (LP: 
#1662997)
  . libmirclient-dev missing build dependency on libmircore-dev. (LP: 
#1662942)
  . mir_window_spec_set_cursor_name() doesn't trigger
mir::scene::SurfaceObserver::cursor_image_set_to. (LP: #1663197)
  . [regression] Software clients of nested servers are all black in Mir 
0.25.0
and later. (LP: #1663062)

 -- Cemil Azizoglu   Thu, 09 Feb 2017
21:46:32 +

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

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

Title:
  [regression] Software clients of nested servers with size >=480x480
  are all black in Mir 0.25.0 and later (or stretched and distorted
  under Unity8)

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Committed
Status in Mir 0.25 series:
  Won't Fix
Status in Mir 0.26 series:
  Fix Committed
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  GPU apps seem to work.

  CPU apps all get black screen.

  To repro :
  Under unity7 using mir-on-x:

  1- In a terminal, run :
  mir_demo_server -f /tmp/mysock

  2- In another terminal, run :
  mir_demo_server --host-socket /tmp/mysock

  3- In another terminal, run :
  mir_demo_client_progressbar

  Under Unity8 :
  In another terminal, run :
  mir_demo_client_progressbar

  Observe that, the window is black.

  Whereas, egl clients run fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1663062/+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 1665209] Re: gnome-system-monitor crash on 17.04

** Attachment removed: "JournalErrors.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1665209/+attachment/4819875/+files/JournalErrors.txt

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

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

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

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

Title:
  gnome-system-monitor crash on 17.04

Status in Gnome System Monitor:
  Unknown
Status in gnome-system-monitor package in Ubuntu:
  Triaged

Bug description:
  crash after update

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: gnome-system-monitor 3.23.90-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 15 21:53:47 2017
  ExecutablePath: /usr/bin/gnome-system-monitor
  InstallationDate: Installed on 2017-01-26 (20 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  ProcCmdline: gnome-system-monitor
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: gnome-system-monitor
  UpgradeStatus: Upgraded to zesty on 2017-01-27 (19 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-system-monitor/+bug/1665209/+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 1665409] [NEW] nvidia-settings

2017-02-16 Thread Мария

Public bug reported:

When i switch in Nvidia X Server Settings - PRIME Profiles GPU From
"Power Saving Mode" to "Performance Mode" and log out it isn t switch,
when i log in again.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
Uname: Linux 4.8.0-37-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..08.00.0: Error: [Errno 21] Это каталог: 
'/proc/driver/nvidia/gpus/:08: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.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Thu Feb 16 19:28:23 2017
DistUpgraded: 2016-10-23 15:15:10,170 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Не удалось выполнить 
процесс-потомок «./xorg_fix_proprietary.py» (No such file or directory) (8))
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-20140620-0
DistroCodename: yakkety
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
   Subsystem: Dell HD Graphics 5500 [1028:06b0]
   Subsystem: Dell GK208M [GeForce 920M] [1028:06b0]
InstallationDate: Installed on 2016-10-22 (116 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
MachineType: Dell Inc. Inspiron 3558
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-37-generic 
root=UUID=cbe7da08-b9c3-4cb1-833c-df5b80cdbffa ro locale=ru_RU quiet splash 
video.use_native_backlight=1 vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to yakkety on 2016-10-23 (116 days ago)
dmi.bios.date: 04/22/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: 0G1TDD
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd04/22/2016:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0G1TDD:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Inspiron 3558
dmi.sys.vendor: Dell 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.1
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

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


** Tags: amd64 apport-bug compiz-0.9 false-gpu-hang freeze 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/1665409

Title:
  nvidia-settings

Status in xorg package in Ubuntu:
  New

Bug description:
  When i switch in Nvidia X Server Settings - PRIME Profiles GPU From
  "Power Saving Mode" to "Performance Mode" and log out it isn t switch,
  when i log in again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
  Uname: Linux 4.8.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..08.00.0: Error: [Errno 21] Это каталог: 
'/proc/driver/nvidia/gpus/:08: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.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Feb 16 19:28:23 2017
  DistUpgraded: 2016-10-23

[Desktop-packages] [Bug 1664447] Re: Mouse Flickering on Built-in display after connecting to external monitor

2017-02-16 Thread Kanishk Dudeja

Can i get an update on this bug? Atleast if the bug can be acknowledged
or some more debugging information is needed?

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

Title:
  Mouse Flickering on Built-in display after connecting to external
  monitor

Status in xorg package in Ubuntu:
  New

Bug description:
  When I connect my Dell XPS 9350 to an 1080p external Dell display, the
  mouse keeps flickering on my Dell XPS 9350.

  The mouse flickering is much more pronounced when i scroll pages in
  Chrome or some other application.

  I had followed these instructions to set up different DPI on both the
  screens:

  https://gist.github.com/DevNiall/3dcd04f4e12b1e75910f53acb1b965cd

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.9.9-040909-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Feb 14 11:00:13 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
     Subsystem: Dell Skylake Integrated Graphics [1028:0704]
  InstallationDate: Installed on 2016-12-15 (60 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. XPS 13 9350
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.9-040909-generic 
root=UUID=360d680b-827b-4265-a822-21c8d6a5a9a3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.10
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.10:bd10/12/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  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 N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1664447/+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 1665402] Re: Own shortcut not working

2017-02-16 Thread Felix K.

** Package changed: gnome-panel (Ubuntu) => ubuntu

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

Title:
  Own shortcut not working

Status in Ubuntu:
  New

Bug description:
  I do not know why the own-shortcuts not working. The only what i had
  done in the system is removing the unity-webapps-common and a
  autoremove after that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1665402/+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 1665209] Re: gnome-system-monitor crash on 17.04